Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!usc!zaphod.mps.ohio-state.edu!casbah.acns.nwu.edu!accuvax.nwu.edu!nucsrl!telecom-request From: Michael_Perka@next.com Newsgroups: comp.dcom.telecom Subject: Re: Caller ID and Call Waiting Message-ID: <15838@accuvax.nwu.edu> Date: 7 Jan 91 05:45:25 GMT Sender: news@accuvax.nwu.edu Organization: NeXT Computer, Inc. Lines: 35 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 12, Message 5 of 11 In article <15797@accuvax.nwu.edu> the Moderator writes: >[Moderator's Note: I've wondered about this myself. How does the >Caller IB box get anything to dislay when the calls comes in via >call-waiting? If you hang up and let the new call actually ring in, >does the information pass at that time, or not? Likewise, when your >phone is forwarded, we all know there is a single ring to remind you >of the forwarding, but you cannot actually receive the call no matter >how fast you pick up the receiver. Is the Caller ID sent to you on >those calls, or not? PAT] The interactions of the Calling Number Delivery (CND) CLASS service with other services such as Custom Calling are noted in the Bellcore Technical Reference TR-TSY-000031, "CLASS Feature: Calling Number Delivery". Under section 3.8, Interactions: "A. Call Waiting CND data should not be transmitted duing of after a Call Waiting (CW) tone. Similarly, CND data should not be transmitted during or after any switchhook flashes that may occur in response to the CW tone. Also, CND should not occur during ringback that results from the customer going on-hook in response to a CW tone." Subsections B through J describe interactions with Multiparty Lines, Three-Way Calling, various types of call forwarding, Distinctive Ringing, Auto Callback/Recall, and Calling Number Delivery Blocking. Ordering info for this TR has already appeared in TELECOM Digest. Mike