Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!mailrus!accuvax.nwu.edu!nucsrl!telecom-request From: merlyn@iwarp.intel.com (Randal Schwartz) Newsgroups: comp.dcom.telecom Subject: Re: Knowing You're a Call Waiting Beep Message-ID: <10758@accuvax.nwu.edu> Date: 12 Aug 90 05:17:25 GMT Sender: news@accuvax.nwu.edu Reply-To: Randal Schwartz Organization: Stonehenge; netaccess via Intel, Beaverton, Oregon, USA Lines: 31 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 563, Message 2 of 12 In article <10716@accuvax.nwu.edu>, yazz@devnet (Bob Yasi) writes: [about the difference in ring to the calling party if calling party is call-waiting a conversation in progress] I notice that calls to local GTE and US West (Bell-like) numbers in this area will ring a "long" ring for the first ring if I'm interrupting someone else's call in progress. It spooks them when I ask "who were you talking to?" after they pick me up (either by putting the other call on hold or losing them). I thought that was pretty much inherent in the "standard" call-waiting package, but maybe that's a localism? Other datapoints? Randal L. Schwartz, Stonehenge Consulting Services (503)777-0095 on contract to Intel's iWarp project, Beaverton, Oregon, USA, Sol III merlyn@iwarp.intel.com ...!any-MX-mailer-like-uunet!iwarp.intel.com!merlyn [Moderator's Note: Although the very experienced ear can tell the difference when calling someone here (slight differences in the clicks, etc), IBT says they don't intend to change the rings or otherwise make an obvious response to the caller about the status of the other person's phone. Why? They say it is none of your business if the person you are calling is already on the phone. Obviously, a busy signal tells you, but that's a completely different matter. If someone has call-waiting, it is up to them to let you know if they are on another call. PAT]