Path: utzoo!utgpu!watserv1!watmath!att!cbnewsl!rl
From: rl@cbnewsl.att.com (roger.h.levy)
Newsgroups: comp.dcom.modems
Subject: PROCOMM FAILING ON LONG DISTANCE
Keywords: procomm
Message-ID: <1990Aug23.115248.29671@cbnewsl.att.com>
Date: 23 Aug 90 11:52:48 GMT
Organization: AT&T Bell Laboratories
Lines: 16

I have used PROCOMM (2.4.1) for a couple of years and until now have
not had any problems.  However, recently I find that Procomm usually
fails only when I make long distance calls.  The failure scenario is:
	1. Long distance modem answers
	2. Carrier tone briefly heard
	3. Get NO CARRIER, call dropped
This doesn't happen with local calls, didn't happen with any calls
until recently and doesn't happen with two other communications pro-
grams I've tried (Windows 3.0 Terminal and AT&T Softcall).  I tried
to increase the S7 value and Procomm's Redial Timeout Delay to no
avail.  I've also changed the modem initialization string to the same
one that works successfully in Windows to no avail.  Generally, all
my Procomm settings are as they were out of the box.  What am I missing?

Roger Levy
rl@groucho.att.com