Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!apple!bionet!hayes.ims.alaska.edu!accuvax.nwu.edu!nucsrl!telecom-request
From: BRUCE@ccavax.camb.com (Barton F. Bruce)
Newsgroups: comp.dcom.telecom
Subject: Re: Logistics of Setting up a Modem Hunt Group
Message-ID: <14519@accuvax.nwu.edu>
Date: 9 Nov 90 17:53:45 GMT
Sender: news@accuvax.nwu.edu
Organization: Cambridge Computer Associates, Inc.
Lines: 10
Approved: Telecom@eecs.nwu.edu
X-Submissions-To: telecom@eecs.nwu.edu
X-Administrivia-To: telecom-request@eecs.nwu.edu
X-Telecom-Digest: Volume 10, Issue 803, Message 11 of 13


In article <14335@accuvax.nwu.edu>, vances@xenitec.on.ca (Vance
Shipley) writes:

> One common mistake made when testing hunt groups is to use a member of
> the hunt group to make the test calls.  If you call line X from line X
> you will get a busy, it will not hunt.

You may have observed this on a #5 x-bar. The LDN, even, dialing itself will
get a busy, so it is not a night answer issue in this case.