Path: utzoo!utgpu!watserv1!watmath!iuvax!mailrus!accuvax.nwu.edu!nucsrl!telecom-request
From: judice@sulaco.enet.dec.com (Lou Judice @KYO / DTN 323-4103)
Newsgroups: comp.dcom.telecom
Subject: Two CLASS Calling Services Questions...
Message-ID: <4345@accuvax.nwu.edu>
Date: 25 Feb 90 04:31:33 GMT
Sender: news@accuvax.nwu.edu
Organization: TELECOM Digest
Lines: 31
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 127, Message 5 of 7


How exactly does the Caller*ID box behave when calls are received from
outside the area code and/or exchanges that do not transmit the ANI
information? Eventually, will Caller*ID work across area codes???

For those states with per-call Caller*ID blocking, is the Caller*ID
box display disabled or is the ANI not transmitted at all? Ie., is
Call*Trace and Return*Call disabled as well???  [If not, then it would
seem easy to get the caller's # by returning their call, and checking
the number on your next bill.]

Ooops, more than two questions!


Thanks,
Lou Judice
Digital Equipment Corp.
Piscataway, NJ
(201 | 908) 562-4103


[Moderator's Note: Also please note the special issue Saturday on
CPID/ANI.  Although sending a blocking code can be done, as Vic Toth
points out, you are assuming one telco will *honor* the blocking code
sent by another telco. And the word we are getting from Illinois Bell
is that (once CLASS is implemented later this year) if the number is
otherwise unavailable then attempts to 'return call' will fail.  You
will be able to store it in your list of numbers you won't accept
calls from, but when you review the file of same, while other numbers
will be spoken to you, those that had blocked ID will be termed
'private entry'.  PT]