Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!mailrus!accuvax.nwu.edu!nucsrl!telecom-request From: john@zygot.ati.com (John Higdon) Newsgroups: comp.dcom.telecom Subject: Re: User Control of Feature(s) Message-ID: <2122@accuvax.nwu.edu> Date: 13 Dec 89 19:17:46 GMT Sender: news@accuvax.nwu.edu Reply-To: John Higdon Organization: Green Hills and Cows Lines: 23 Approved: Telecom@eecs.nwu.edu X-Submissions-To: telecom@eecs.nwu.edu X-Administrivia-To: telecom-request@eecs.nwu.edu X-Telecom-Digest: Volume 9, Issue 571, message 4 of 11 In article <2000@accuvax.nwu.edu> nmri!!stanley@uunet.uu.net (John Stanley) writes: >X-Telecom-Digest: Volume 9, Issue 564, message 4 of 8 >If anyone calls the old main >number while someone is still being forwarded, they don't hunt, they >get busy. Not generally true. When the forwarded call supervises (is answered) then the forwarded phone will pass another call. And so on. The reason this was done (they used to forward any number of calls, regardless of supervision status) was to prevent forwarding loops. Try it; place a call to your forwarded number and when it answers, place another--it should forward as well. An exception to this is RCF. When you set up Remote Call Forwarding (a number that you don't even get a pair for, they just forward it for you to a number of your choosing), they ask you to specify how many "forwards" are to be allowed. This number should corespond to the number of lines available at location that is receiving the calls. John Higdon | P. O. Box 7648 | +1 408 723 1395 john@zygot.ati.com | San Jose, CA 95150 | M o o !