Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!usc!apple!bionet!hayes.ims.alaska.edu!accuvax.nwu.edu!nucsrl!telecom-request From: john@bovine.ati.com (John Higdon) Newsgroups: comp.dcom.telecom Subject: Re: Forwarded Calls and CallerID Message-ID: <15152@accuvax.nwu.edu> Date: 1 Dec 90 19:08:25 GMT Sender: news@accuvax.nwu.edu Reply-To: John Higdon Organization: Green Hills and Cows 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 860, Message 6 of 11 "Nicholas J. Simicich" writes: > 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. It was probably ignored because of the virtually zero probability that it was the case. SS7 data is error-checked and garbled data would be rejected as invalid. Today's network does not "simply misroute" calls. And parity-checked RAM does not "garble" numbers that it "remembers". When I receive a wrong number, I always assume error on the part of the caller, not in the switching network. To quote a well-known radio doctor, "When you hear hoofbeats, think horses, not zebras." John Higdon | P. O. Box 7648 | +1 408 723 1395 john@bovine.ati.com | San Jose, CA 95150 | M o o !