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: kityss@ihlpf.att.com
Newsgroups: comp.dcom.telecom
Subject: Forwarded Calls and CallerID
Message-ID: <15083@accuvax.nwu.edu>
Date: 28 Nov 90 16:25:00 GMT
Sender: news@accuvax.nwu.edu
Organization: TELECOM Digest
Lines: 44
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 854, Message 9 of 10


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.

Matt Funkchick responds - 

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

And our Moderator Notes -

>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? 

The answer to all the above is that the original calling parties
number is what is passed in any chain of call forwarding.  Example: A
calls B, B is forwarded to C (so A's call rings at C) - for any of the
CLASS services C's memory space will contain A's phone number.  So
CallerID, Return*Call, or any of the screening features will work with
A's number.  (Need I mention this is only if there is complete SS7
connectivity between all the COs involved - and that all three parties
are in the same LATA.)

The only time B's memory space will be updated is if they have Call
Forwarding Don't Answer - then their memory space will contain A's
phone number (as will C's).

So the original poster's problem either was caused by the person who
answered their Return*Call being in on the "joke", or by the person
being unaware that an outgoing call had been made from that location.


Arnette Baker
kityss@ihlpf.att.com