Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!usc!apple!bionet!hayes.ims.alaska.edu!accuvax.nwu.edu!nucsrl!telecom-request
From: den0@midway.uchicago.edu (funky chicken)
Newsgroups: comp.dcom.telecom
Subject: Re: Return*Call Humor
Message-ID: <14984@accuvax.nwu.edu>
Date: 26 Nov 90 17:35:59 GMT
Sender: news@accuvax.nwu.edu
Organization: University of Chicago
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 10, Issue 848, Message 9 of 12


In article <14952@accuvax.nwu.edu> weave@brahms.udel.edu (Ken
Weaverling) describes how his girl friend had "Return*called" a crank
call, yelling at the caller, only to have that person return the call
and act as if she were the crank caller.  He concludes:

>We sat around puzzled for a moment, then finally figured out that
>there must be several extensions in their house and the original crank
>call must have originated, perhaps, with a child, and the child's
>Mother answered our Return*Call.

Or else the real crank caller was at another number and was forwarding
calls to another one of his/her victims.


Matt Funkchick


[Moderator's Note: This raises a good point. When a call reaches you
via forwarding through some other number, does 'return call' go to the
forwarded number or the original caller? Likewise for Call Screening
and Caller-ID: *whose* ID gets passed for the purpose of callback
and/or screening, etc?   PAT]