Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!accuvax.nwu.edu!nucsrl!telecom-request
From: Miguel_Cruz@ub.cc.umich.edu
Newsgroups: comp.dcom.telecom
Subject: Re: Call Waiting Question
Message-ID: <3526@accuvax.nwu.edu>
Date: 4 Feb 90 21:07:12 GMT
Sender: news@accuvax.nwu.edu
Organization: TELECOM Digest
Lines: 16
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 76, message 2 of 13


In Digest 10.75, David Daniel said something to the effect that Call
Waiting would not cause problems with protocol file transfers because
the checksums would not match and the packet would simply be resent
following the call waiting burst.
 
The problem with this is that many modems, especially on long distance
calls, simply drop carrier and hang up while the call waiting tone is
obscuring the far-end carrier.  Even if you set your modem to wait a
long time before dropping carrier, there is no guarantee that the
remote modem has been similarly adjusted.
 
So, the protocol's ability to recover is largely a moot point, as the
two modems will more likely that not have disconnected by the time the
call waiting tone's over.