Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!killer!vector!telecom-gateway From: westmark!dave@rutgers.edu (Dave Levenson) Newsgroups: comp.dcom.telecom Subject: Re: Calling party ID Message-ID: Date: 15 Mar 89 04:16:07 GMT Sender: news@vector.UUCP Organization: Westmark, Inc., Warren, NJ, USA Lines: 27 Approved: telecom-request@vector.uucp X-Submissions-To: telecom@eecs.nwu.edu X-Administrivia-To: telecom-request@vector.uucp X-TELECOM-Digest: volume 9, issue 89, message 2 of 8 In article , ulysses!smb@research.att.com writes: > N.J. Bell is now offering calling party ID. How complete is the CCIS network > needed to support this? What are the odds on getting the number on an > inter-LATA call? An intra-LATA call but from a different switch? Also, > how is the number communicated? Does the ring signal carry some sort of > extra modulation? We just got CLASS(sm) Caller*Id Service from NJ Bell. The calling number is currently delivered only on intra-lata calls, and not from all central offices in our lata. The calling number is communicated in a burst of FSK-encoded data, sent simplex (i.e. no ACK expected) at 1200 bps between the first and second rings. The data burst includes the date and time, the calling number, or an indication that the calling number is not available. If you answer during the first ring, no data are received. Now, can someone (perhaps at NJ Bell) tell me what *62 is supposed to do? It results in a confirmation tone, but I can't seem to discover what it's confirming! -- Dave Levenson Westmark, Inc. The Man in the Mooney Warren, NJ USA {rutgers | att}!westmark!dave