Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!accuvax.nwu.edu!nucsrl!telecom-request
From: westmark!dave@uunet.uu.net (Dave Levenson)
Newsgroups: comp.dcom.telecom
Subject: Re: Caller ID Question
Message-ID: <2063@accuvax.nwu.edu>
Date: 12 Dec 89 00:56:04 GMT
Sender: news@accuvax.nwu.edu
Organization: Westmark, Inc., Warren, NJ, USA
Lines: 20
Approved: Telecom@eecs.nwu.edu
X-Submissions-To: telecom@eecs.nwu.edu
X-Administrivia-To: telecom-request@eecs.nwu.edu
X-Telecom-Digest: Volume 9, Issue 568, message 8 of 13


In article <2019@accuvax.nwu.edu>, GREEN@wharton.upenn.edu (Scott D. Green) 
writes:

 ... regarding Caller*ID and Call-Waiting...

> What is the interaction with Call Waiting?  Now *that* would be
> useful: To know who was interrupting you before you actually
> interrupted the call-in-progress...

Sorry, but Caller*ID does not function on calls waiting.  Because
the information is only sent between rings, and because your
telephone does not ring when the call-waiting signal is sent, no
Caller*ID information is sent.


Dave Levenson                Voice: (201) 647 0900
Westmark, Inc.               Internet: dave@westmark.uu.net
Warren, NJ, USA              UUCP: {uunet | rutgers | att}!westmark!dave
[The Man in the Mooney]      AT&T Mail: !westmark!dave