Path: utzoo!attcan!uunet!cs.utexas.edu!news-server.csri.toronto.edu!umich!accuvax.nwu.edu!nucsrl!telecom-request
From: vances@xenitec.on.ca (Vance Shipley)
Newsgroups: comp.dcom.telecom
Subject: Re: Turning Off Call Waiting Remotely
Message-ID: <14082@accuvax.nwu.edu>
Date: 26 Oct 90 19:22:51 GMT
Sender: news@accuvax.nwu.edu
Reply-To: vances@ltg.UUCP (Vance Shipley)
Organization: SwitchView - The Linton Technology Group
Lines: 25
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 768, Message 8 of 11


In article <14002@accuvax.nwu.edu> hayes!tnixon@uunet.uu.net (Toby
Nixon) writes:

>It is a fairly well-known and well-documented feature that if you have
>BOTH Three-Way Calling and Call-Waiting that you can disable Call
>Waiting by doing a hook-flash, *70.

I do not have three-way calling.  The only option I have is call-waiting.
*70 works for me!


Vance


[Moderator's Note: Assuming *70 is implemented in your CO, it will
always work as the first digits dialed on a call you originate. The
trick is being able to decide to turn it on the middle of a
conversation, or during a conversation you did not originate. You
*cannot* turn it on in mid-conversation or on calls you receive unless
you have three way calling, or some other valid reason for flashing
the hook. (I don't know of any except to add another call). Instead of
adding the call, however, you can then dial *70 and be immediatly
returned to the call in progress, but with your call waiting suspended
for the duration.  PAT]