Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!accuvax.nwu.edu!nucsrl!telecom-request From: Heath Roberts Newsgroups: comp.dcom.telecom Subject: Re: Call Trace Question Message-ID: <6279@accuvax.nwu.edu> Date: 11 Apr 90 15:53:24 GMT Sender: news@accuvax.nwu.edu Reply-To: Heath Roberts Organization: NCSU Computing Center Lines: 27 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 248, Message 1 of 7 In article <6246@accuvax.nwu.edu> smk@attunix.att.com (S M Krieger) writes: >Along with the Caller ID feature, NJ Bell quietly implemented a Call >Trace feature. By pushing a certain code (I think it's *79), the last >number that called will be saved and provided to the police; each >trace costs $1.00. >Now for my question: if the originating exchange does not support >Caller ID, etc., does anybody know what number will be provided if >Call Trace is activiated? Obviously it can't be the phone number that >just called, but will it be a "blank", or will it be the last number >for which a trace was available (and if it is, I don't even want to >think about the legal implications of the telco reporting the wrong >originating number to the police)? Northern Telecom's software reports an error code if it's not able to query the originating switch regarding Caller Trace or ID. This (currently) shows up as asterisks on your display. I'm not sure how AT&T switches handle this (I'm not even sure then can supply CLID, but I'm sure they'll be able to soon). Heath Roberts NCSU Computer and Technologies Theme Program heath@shumv1.ncsu.edu