Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!accuvax.nwu.edu!nucsrl!telecom-request From: "DOUGLAS SCOTT REUBEN)" Newsgroups: comp.dcom.telecom Subject: Re: CLASSPLUS Service Message-ID: <12428@accuvax.nwu.edu> Date: 23 Sep 90 03:07:27 GMT Sender: news@accuvax.nwu.edu Organization: TELECOM Digest Lines: 27 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 666, Message 1 of 11 Hi- I saw that William Degnan in his post on new "CLASSPLUS" services mentioned that one of these new services would allow customers with Call-Waiting to get a display of a third party calling via Call-Waiting. This is indeed interesting, but a bit troublesome. I thought that the data for Caller*ID was sent between the first and second rings, ie, before the phone is picked up. How is it possible then to send the Caller*ID signal while a call is allready in progress? I am presently working on a few devices which utilize Caller*ID, so it would be a real pain if Call-Waiting type Caller*ID is not compatible with the "standard" type of Caller*ID (ie, the kind Bellcore describes in their literature.) Do they verebally tell you the calling number after the Call-Waiting beep, as in: (or CLICK CLICK for older machines) You have a call from 555-1212. Flash once to answer." Nah ... would take too long ... oh well, sounds interesting to me, nevertheless. Doug dreuben@eagle.wesleyan.edu dreuben@wesleyan.bitnet