Path: utzoo!telecom-request Date: 12 Apr 91 19:38:35 GMT From: Kevin Collins Newsgroups: comp.dcom.telecom Subject: Re: Caller*ID Specifications Needed Message-ID: Organization: Aspect Telecommunications, San Jose, 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 287, Message 7 of 10 Lines: 26 On 6 Apr 91 08:22:08 EDT, David Berman (daveb@comspec.UUCP) writes: [asking about how/when CallerID info is sent to the called party] > 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? As far as the future is concerned, once the local telcos get around to offering ISDN Basic Rate Interface (two data channels, one signalling channel), the calling party number will be sent from telco to the called number in the call origination message (called the SETUP message). Your (BRI-compatible) phone will have the information *before* it rings, and could easily decide whether to tell telco to proceed with the call or reject it at that time. So, if your mother calls too often, just have your phone set to reject call attempts from her number after 10 pm :-). Kevin Collins | Aspect Telecommunications USENET: ...uunet!aspect!kevinc | San Jose, CA Voice: +1 408 441 2489 | My opinions are mine alone.