Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!apple!bionet!hayes.ims.alaska.edu!accuvax.nwu.edu!nucsrl!telecom-request
From: NJS@ibm.com (Nicholas J. Simicich)
Newsgroups: comp.dcom.telecom
Subject: Forwarded Calls and CallerID
Message-ID: <15112@accuvax.nwu.edu>
Date: 29 Nov 90 18:29:42 GMT
Sender: news@accuvax.nwu.edu
Reply-To: Nick Simicich <NJS@ibm.com>
Organization: TELECOM Digest
Lines: 18
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 857, Message 5 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.

Various people come up with various complicated explanations about how
the phone system might have been confused by call forwarding, or
people where the callback call was answered might have been either
without knowledge or confused, or even intentional dupes.

The simplest explanation is the one that seems to be ignored by most
people: The phone switching system simply misrouted the Return*Call,
or garbled the number it remembered.


Nick Simicich (NJS at WATSON on bitnet, njs@ibm.com)
SSI AOWI #3958, HSA #318