Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!usc!apple!bionet!hayes.ims.alaska.edu!casbah.acns.nwu.edu!accuvax.nwu.edu!nucsrl!telecom-request
From: yazz@prodnet.la.locus.com (Bob Yasi)
Newsgroups: comp.dcom.telecom
Subject: Re: Return*Call Humor
Message-ID: <15226@accuvax.nwu.edu>
Date: 5 Dec 90 01:41:39 GMT
Sender: news@accuvax.nwu.edu
Organization: Locus Computing Corp, Los Angeles
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 866, Message 2 of 9


I believe there remains a point to be made in the call-back-the-
annoyance-caller-but-he-used-call-forwarding-so-now-what-happens
saga.

If A is the annoyer he can 1) fwd to B, then 2) call up and annoy C.

If C returns the call with call*return, is the annoyer's call
forwarding ignored, ringing A's phone?  If not, and the return*call to
A is forwarded to B, the spleen-venting victims could *69 each other
all day!  This could be what happened to the original poster of this
dilemma.


   Bob Yazz --  yazz@lccsd.sd.Locus.com


[Moderator's Note: They'll need to fix it so that *69 overrides call
forwarding.  PAT]