Path: utzoo!attcan!uunet!zaphod.mps.ohio-state.edu!julius.cs.uiuc.edu!apple!bionet!hayes.ims.alaska.edu!accuvax.nwu.edu!nucsrl!telecom-request
From: dave@westmark.westmark.com (Dave Levenson)
Newsgroups: comp.dcom.telecom
Subject: Re: Logistics of Setting up a Modem Hunt Group
Message-ID: <14365@accuvax.nwu.edu>
Date: 5 Nov 90 13:41:29 GMT
Sender: news@accuvax.nwu.edu
Organization: Westmark, Inc., Warren, NJ, USA
Lines: 25
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 792, Message 3 of 10


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.

This is not always a mistake.  When I had a two-line hunt-group in
Summit, NJ, (we were then served by an elderly 5-crossbar switch,
201-273 for those who care) that was the case.  Hunting did not work
if the call was originated within the hunt-group.  In the 1AESS which
later replaced the 5-crossbar switch, hunting did work when the call
originated within the group.

I don't know whether this is a 'feature' of 5-crossbar, or a
translation option that happened to be changed along with the massive
changes that accompanied the CO cutover (back in about 1980, as I
recall).


Dave Levenson			Internet: dave@westmark.com
Westmark, Inc.			UUCP: {uunet | rutgers | att}!westmark!dave
Warren, NJ, USA			AT&T Mail: !westmark!dave
[The Man in the Mooney]		Voice: 908 647 0900  Fax: 908 647 6857