Roy, at 21:53 on Jul 15 1995, you wrote to Bill Grimsley...

BG> 13 Jul 14:43:25.75 CONNECT 14400/V32/NONE

RM> When my Sweatsock gives this response, it normally means that the line was 
RM> too foul for the modems to negotiate an MNP/v42 (whatever) error 
RM> correction. After this, the modem ivariably starts receiving almost pure 
RM> junk.

Yep, that's the symptom here as well, but I'm not convinced that poor line
conditions are the cause, especially as the subsequent call works fine.

RM> I get several connections like this per year, and some time ago told the 
RM> modem to &M5 to save me the trouble of hanging up.

I actually had &M5 set at one stage too, but incredibly (and
typically), no calls failed EC during that period.  Am using the default at
the moment, as I want to see if the failed connect string includes the V32
result code.  I have a strange feeling that it doesn't, but ever since I've
been sweating on a failed connect, I haven't had one!  I dips me lid to Mr
Murphy.  :)

... 22/2 (urk!)

Regards, Bill
@EOT:

--- Msgedsq/2 3.10