Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!sun-barr!apple!bionet!hayes.ims.alaska.edu!accuvax.nwu.edu!nucsrl!telecom-request
From: vances@xenitec.on.ca (Vance Shipley)
Newsgroups: comp.dcom.telecom
Subject: Re: Logistics of Setting up a Modem Hunt Group
Message-ID: <14335@accuvax.nwu.edu>
Date: 4 Nov 90 19:25:01 GMT
Sender: news@accuvax.nwu.edu
Organization: SwitchView - The Linton Technology Group
Lines: 19
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 790, Message 11 of 13


In article <14273@accuvax.nwu.edu> James Deibele <jamesd@techbook.com>
writes:

>if I call X+1 and it's busy, I will not get X+2.  Is this a reasonable
>conclusion, or have I somehow made a mistake while testing?

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.


vance


[Moderator's Note: I don't think you are correct. I think anywhere you
enter the loop if that line is busy (i.e. you are in fact calling from
it) the incoming call will continue forward in the hunt group.  The
exception would be as Mr. Levenson points out in the next message.  PAT]