Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!mailrus!accuvax.nwu.edu!nucsrl!telecom-request
From: nvuxr!deej@bellcore.bellcore.com (David Lewis)
Newsgroups: comp.dcom.telecom
Subject: Re: Two Questions About Caller ID
Message-ID: <2785@accuvax.nwu.edu>
Date: 10 Jan 90 17:37:15 GMT
Sender: news@accuvax.nwu.edu
Organization: Bellcore, Livingston, NJ
Lines: 26
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 20, message 8 of 9


[What was it you said, Patrick?  Two weeks before we start up again?]

In article <2584@accuvax.nwu.edu>, STEVEF%WALKER_RICHER_QUINN@mcimail.com 
(Steve Forrette) writes:
 
> 1) Long distance and Caller ID
 
> How well does Caller ID work with incoming long distance calls?

It doesn't.  [Inasmuch as "long distance" is defined as inter-LATA.]
None of the CLASS service package, of which Caller ID is one service,
will work in any way with inter-LATA calls.

However, some certain 800 calls will result in the billing number
(which, in 99% of residential applications, is the same as the calling
number) being delivered to the called party.  AT&T offers billing number
delivery (a.k.a. ANI delivery) over an ISDN BRI from their 4ESS to a
customer's PBX; MCI is shortly going to begin delivery of billing number
(ANI) via MF signaling to customers.  Both of these are, so far as I
know, offered only in conjunction with 800 service.


David G Lewis					...!bellcore!nvuxr!deej
	(@ Bellcore Navesink Research & Engineering Center)
			"If this is paradise, I wish I had a lawnmower."