Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!mips!synoptics!bionet!hayes.ims.alaska.edu!accuvax.nwu.edu!nucsrl!telecom-request
From: cybrspc!roy@cs.umn.edu (Roy M. Silvernail)
Newsgroups: comp.dcom.telecom
Subject: Re: Call-Waiting Disable
Message-ID: <14586@accuvax.nwu.edu>
Date: 11 Nov 90 18:40:36 GMT
Sender: news@accuvax.nwu.edu
Organization: Villa CyberSpace, Minneapolis, MN
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 810, Message 9 of 11


SABAHE@macalstr.edu (Arun Baheti <SABahe@Macalstr.EDU>) writes:

> I'm having trouble disabling the call waiting feature in the Twin
> Cities area.  While the standard methods (*70 and 1170) are listed in
> the phone book, and the phone company claims vehmently that these
> methods will work, I continue to receive "call not completed" messages
> whenever I try.  The normal methods work in SoCal (Pac*Tel), so I am
> beginning to wonder ... Does anyone else have experience with the Twin
> Cities system? 

I think I qualify. The line I use (which actually belongs to a
roommate, else the damnable feature wouldn't be there at all) has
Call-Waiting. It is indeed 100% fatal to a modem connection. I have no
problem, though, disabling it with *70. In fact, my outbound UUCP poll
batch file can be told whether or not the poll is 'nukeable' and will
select the dialing prefix accordingly.

Pat's note is timely ... do you _actually_ have Call-Waiting on your
line? (i.e. have you ever been C-W beeped during a conversation?) If
you are simply losing modem connections, perhaps the problem lies
elsewhere.  


Roy M. Silvernail   
now available at:   
cybrspc!roy@cs.umn.edu