Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!sun-barr!apple!bionet!hayes.ims.alaska.edu!accuvax.nwu.edu!nucsrl!telecom-request
From: jamesd@techbook.com (James Deibele)
Newsgroups: comp.dcom.telecom
Subject: Re: Logistics of Setting up a Modem Hunt Group
Message-ID: <14518@accuvax.nwu.edu>
Date: 8 Nov 90 19:18:15 GMT
Sender: news@accuvax.nwu.edu
Organization: TECHbooks of Beaverton Oregon - Public Access Unix
Lines: 35
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 10 of 13


In article <14366@accuvax.nwu.edu> TERRY@spcvxa.bitnet (Terry Kennedy,
Operations Mgr) writes:

>In article <14335@accuvax.nwu.edu>, our Moderator writes:

>> [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]

>  I know of several methods of setting up "hunt groups". Not all of
>these are available on all switches:

Thanks for an informative posting on hunt groups.  Unfortunately, it
seems that GTE has what you described as "single-entry hunt" where
there's only one number per hunt group and the rest of the numbers
can't hunt.  Or that's what GTE tells me this time.  I think I'll call
back and talk to one or two more people to make sure that's correct.

It would be nice if there was a "wizard" number that you could call
and find out whether something was technically feasible or not.  I
have this nagging feeling that there's probably a way of doing what I
want, but that the first- line people aren't used to handling things
that way.  They do have a "call when busy" feature (if number X or Y
or Z is busy, call number A), but it's several dollars a line per
month while the hunt group is free.

Thanks to the people who suggested possible problems when calling from
within the hunt group.  That wasn't the situation in this case (I was
calling from another phone line), but I confess that I never would
have thought of such a thing as causing a problem.


Public Access UNIX (503) 644-8135 (1200/2400 N81) --- Read alt.books.technical