Path: utzoo!telecom-request Date: 10 Apr 91 17:10:26 GMT From: Paul Elliott x225 Newsgroups: comp.dcom.telecom Subject: Re: Caller*ID Specifications Needed Message-ID: Organization: Optilink Corporation, Petaluma, CA Sender: Telecom@eecs.nwu.edu Approved: Telecom@eecs.nwu.edu X-Submissions-To: telecom@eecs.nwu.edu X-Administrivia-To: telecom-request@eecs.nwu.edu X-Telecom-Digest: Volume 11, Issue 286, Message 9 of 10 Lines: 54 In article , @comspec.uucp (David Berman) writes: > And I also believe that the Caller*ID transmissions from the phone > company are kind of standardized. I think. > Question: Does anyone reading know what is sent out? How the phone > number or alpha information is encoded on the ring cycle? Has it been > done in a reasonable way so that decoding is sensible? (etc) Addresses > the future? > Or: Does anyone know where such information is published for > reference? I have in front of me two Bellcore specs that I *think* are appropriate. They are: CLASSsm Feature: Calling Number Delivery Technical Reference TR-TSY-000031 Issue 3, January 1990 (This describes the encoding, bit rate, etc.) and SPCS Customer Premises Equipment Data Interface Technical Reference TR-TSY-000030 Issue 1, November 1988 (This provides some protocol information.) What I don't know is if this is really CALLER ID, or some other variant scheme. The protocol description is a bit too vague for me to be able to figure out how one would encode or decode an actual phone number. Anyone have any additional or better information? I would like to know, also. To contact Bellcore: Information Exchange Management Bellcore 445 South Street, Room 2J-125 P.O. Box 1910 Morristown, NJ 07692-1910 (201) 829-4785 Paul Elliott - DSC Optilink - {uunet,pyramid,pixar,tekbspa}!optilink!elliott