On 03 Jan at 10:59, Hayes Support of 1:396/1 wrote to Chris Maddock:
[.....]
CM>>1. When connecting to some other sites, the Hayes calls out fine, goes 
CM>>through
CM>>its negotiation sequence and then immediately hangs up. (*Immediatly* at 
CM>>the end of the negotiation sequences !  The CD light blinks and thats 
CM>>=it=.)
CM>>If I do ATS37=29, it works. But why should I have to *force*  a lower 
speed
CM>>connect for it to connect ?? Am I doing something wrong ?
HS> Chris,
HS> Under some conditions forcing the modem to initially connect at a
HS> slower carrier speed can give you a more stable connection.  If the
HS> conditions allow it, the modem can still renegotiate to a higher carrier
HS> speed if the lines allow it.
Hi Michael,
Yes, I understand that. 
But, (isn't there always one of them ?), why should I have to *force* a lower 
speed connection. Why is this not negotiated in the negotiation period ??
CM>>2. I can't seem to get the ATS86? to work properly. Binkley has an 
CM>>"AfterCall" function whereby it allows an interogation of the modem for 
the 
CM>>cause of the last disconnection.
CM>>All the Hayes replies with is "000" every time, even though I've seen it
CM>>disconnect because of the terrible lines I'm on. I did a manual 
CM>>disconnection (pulled the phone plug from the wall) to see what the 
effect 
CM>>would be. 
CM>>"000" was the response.
CM>>Can you tell me how to get this working please ? I need ammo for our 
elco
CM>>(Tel$tra) to get off their butts and do something about the lines. Austel 
CM>>have recently changed the "required End-to-End Standard" so that the 
lines 
CM>>need only handle 2400 bps (Yes, Bits per Second !)
CM>>Along with a transmit level of -10dBM, this is a recipe for disaster here 
CM>>in Oz. +4dBM to line is far more sensible in my blunt opinion.
HS> The S86 result codes may not be supported in all models, and I do not
HS> have the specs on the non-US Hayes models.  S86 wouldn't likely give you
HS> any really useful info, it gives you result codes that tell of certain
HS> timeouts, protocol failures, etc. but nothing that you could point to
HS> and say, there, that's caused by line noise!
Agreed, however I am after enough info to be able to use the sum of it to get 
the line improved so that it is at least consistant. 
I will contact the Australian Hayes support on Monday.
[.....]
Regards,
Chris Maddock
chrism@softtech.brisnet.org.au
--- Msged/386 4.00
---------------