Path: utzoo!attcan!uunet!samsung!zaphod.mps.ohio-state.edu!wuarchive!decwrl!hayes.ims.alaska.edu!accuvax.nwu.edu!nucsrl!telecom-request
From: alai@oucsace.cs.ohiou.edu (Alex Lai)
Newsgroups: comp.dcom.telecom
Subject: Re: Advice on ANI Hardware Wanted
Message-ID: <13767@accuvax.nwu.edu>
Date: 17 Oct 90 07:54:29 GMT
Sender: news@accuvax.nwu.edu
Organization: TELECOM Digest
Lines: 28
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 743, Message 8 of 11


In a previous article, john@bovine.ati.com (John Higdon) writes:
 
> Any switch on the face of
> the planet can be adapted for ANI.
 
Then why haven't they? Why haven't they offer ANI service as
they have done with call-waiting, call-forwarding, and etc?
 
> CLASS, on the other hand, is relatively new technology requiring SS#7
> signaling between participating offices. Among its many features is
> the infamous Caller-ID.
 
Could you please elaborate on CLASS?
 
> While there has been some interchanging of these terms on this forum,
> it would be well to realize that ANI and Caller-ID are not one and the
> same.
 
What's the difference between ANI and Caller-ID?


Alex  Lai                            
Ohio University                     
Communication Systems Management   
Athens, Ohio                    
Internet: alai@oucsace.cs.ohiou.edu 
ad094@cleveland.freenet.edu