Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!know!zaphod.mps.ohio-state.edu!mips!pacbell.com!decwrl!hayes.fai.alaska.edu!accuvax.nwu.edu!nucsrl!telecom-request
From: albert@endor.harvard.edu (David Albert)
Newsgroups: comp.dcom.telecom
Subject: Re: Can One Disable Call-Waiting if *70 Doesn't Work?
Message-ID: <9244@accuvax.nwu.edu>
Date: 25 Jun 90 13:47:16 GMT
Sender: news@accuvax.nwu.edu
Reply-To: albert@endor.UUCP (David Albert)
Organization: TELECOM Digest
Lines: 22
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 453, Message 8 of 15


>> Can one disable call waiting in New York if the *70 tone block feature
>> didn't work?  Is there another way, this reeks havoc on data calls, as
>> you can imagine.

>One of the easiest is to set the modem's S9 and S10 registers to a
>value that ignores the break in the data stream when the incoming call
>is sensed.  This value could be 20 or more (2 seconds).

I have the opposite problem: trying to get call waiting to work while
I'm on a data connection.  I live in a dorm where I can only get one
phone line, and since I'm on the computer several hours a day and
don't want to be cut off from calls, I deliberately set my modem's S10
register to a small value so that I *will* be cut off.  The problem is
that the switch I'm on currently sends such a short tone that even a
value of S10=3 (three-tenths of a second) is not always enough to cut
me off, while S10=2 causes my refrigerator to cut me off each time it
cycles on.  S10=3 seems to be my best bet, but sometimes I have to
manually turn off my modem when I see the distinctive eight or ten
characters that the call-waiting beep translates into.  And sometimes
the screen starts filling up with garbage -- perhaps a parity bit gets
lost or something?