Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!zaphod.mps.ohio-state.edu!casbah.acns.nwu.edu!accuvax.nwu.edu!nucsrl!telecom-request
From: ole@csli.stanford.edu (Ole J. Jacobsen)
Newsgroups: comp.dcom.telecom
Subject: Hunting and Busy Call Forwarding
Message-ID: <16448@accuvax.nwu.edu>
Date: 25 Jan 91 19:02:59 GMT
Sender: news@accuvax.nwu.edu
Organization: TELECOM Digest
Lines: 26
Approved: Telecom@eecs.nwu.edu
X-Submissions-To: telecom@eecs.nwu.edu
X-Administrivia-To: telecom-request@eecs.nwu.edu
X-Telecom-Digest: Volume 11, Issue 69, Message 6 of 7


I am happy to report a definite "yes you can do it" to a question that
I have been wondering about for some time.  Special thanks to Pete
Ahrens of Pac*Bell for clarifying this.

I have two lines, A and B, in "circular hunt" or "series completion".
This means that if you call A and it is busy, B will ring. If you call
B and it is busy, A will ring. So far, pretty basic stuff.

I decided to add a third line C, which would be my "spillover" and
allow me to receive a third call placed to either A or B when *both*
were busy. This is accomplished quite readily by adding "busy call
forwarding" to both A and B pointing to C.  It turns out that the
hunting is attempted *before* busy call forwarding is activated, and
so the two services work nicely in conjunction.

Another solution would have been to put A, B and C all in circular
hunt, but the result would not have been quite the same, as a call to
B would hunt to C before hunting to A.

Thought you'd like to know.  (And Higdon said it could not be done.  :-)


Ole J Jacobsen, Editor & Publisher ConneXions--The Interoperability Report 
Interop, Inc., 480 San Antonio Road, Suite 100, Mountain View, CA 94040, USA
Phone: (415) 941-3399  FAX: (415) 949-1779  Email: ole@csli.stanford.edu