Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!wuarchive!mit-eddie!uw-beaver!Teknowledge.COM!unix!synoptics!bionet!hayes.ims.alaska.edu!accuvax.nwu.edu!nucsrl!telecom-request
From: varney@ihlpf.att.com (Al L Varney)
Newsgroups: comp.dcom.telecom
Subject: Re: Ancient ANI
Message-ID: <13950@accuvax.nwu.edu>
Date: 23 Oct 90 20:42:44 GMT
Sender: news@accuvax.nwu.edu
Organization: AT&T Bell Laboratories
Lines: 34
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 757, Message 7 of 10


In article <13899@accuvax.nwu.edu>, john@bovine.ati.com (John Higdon)
writes:

> On Oct 21 at 19:05, Peter da Silva writes:

> > We get the message. ANI is not CID. Fine. So what is the *external*
> > difference between ANI and CID?

> Well, yes, there is a considerable difference, ...
> [besides] the proper terminology when discussing technical topics ...

> Caller-ID is always delivered to an end user. ANI is typically delivered
> to a "brother in the cloth" common carrier 

> ANI is industrial; CID is consumer.

Two other differences: 1) ANI can be sent in 7 and 10 digit versions,
depending on who's sending/receiving, and identifies the number
CHARGED for this part of the call.  May not be a valid number or the
number actually assigned to the caller.  CallerID is (so far) always
10 digits.

2) While the above description doesn't sound like a big difference for
most callers, look at a call that involves Call Forwarding.  Any ANI
sent on the "forwarded" leg of the call identifies the Billing Number
of the forwarding station.  Any CallerID delivered to the terminating
telephone identifies the original calling telephone.

Haven't heard anyone say that CallerID can't be used by other than end
user.


Al Varney, AT&T Network Systems, Lisle, IL