Re: [hylafax-users] Failure to train remote

[Lee Howard <faxguy@deanox.com>]

At 10:55 AM 2/23/01 -0800, admin wrote:
>I've recently switched my modem to run using Class 1 to fix certain remote
>connnect problems.  However, I'm not getting a different error...many of
>the remote faxes won't train at all. I've also recently upgraded to
>HylaFAX 4.1beta2.  Should I switch back to Class 2 or 2.0?
>
>Any thoughts...

Try beta3, although I can't claim that it *will* fix the problem, I can say
that there are a number of fixes in it which deal with this type of thing.
I'd recommend staying with Class 1 over Class 2/2.0, but do whatever works
for you.

More below...

>Feb 23 08:31:16.02: [ 8050]: REMOTE best rate 9600 bit/s
....
>Feb 23 08:31:16.02: [ 8050]: REMOTE supports T.30 Annex A, ECM
>Feb 23 08:31:16.02: [ 8050]: REMOTE best 20 ms, 10 ms/scanline
>Feb 23 08:31:16.02: [ 8050]: USE 9600 bit/s
....
>Feb 23 08:31:16.02: [ 8050]: SEND training at v.29 9600 bit/s
>Feb 23 08:31:16.02: [ 8050]: <-- [9:AT+FTH=3\r]
>Feb 23 08:31:16.04: [ 8050]: --> [7:CONNECT]
>Feb 23 08:31:17.76: [ 8050]: --> [7:CONNECT]
>Feb 23 08:31:18.09: [ 8050]: --> [2:OK]
>Feb 23 08:31:18.09: [ 8050]: DELAY 75 ms
>Feb 23 08:31:18.17: [ 8050]: <-- [10:AT+FTM=96\r]
>Feb 23 08:31:18.19: [ 8050]: --> [7:CONNECT]
>Feb 23 08:31:20.21: [ 8050]: --> [2:OK]
>Feb 23 08:31:20.21: [ 8050]: <-- [9:AT+FRH=3\r]
>Feb 23 08:31:20.67: [ 8050]: --> [10:NO CARRIER]
>Feb 23 08:31:20.67: [ 8050]: MODEM No carrier
>Feb 23 08:31:20.67: [ 8050]: DELAY 1500 ms
>Feb 23 08:31:22.17: [ 8050]: SEND training at v.29 7200 bit/s
>Feb 23 08:31:22.17: [ 8050]: <-- [9:AT+FTH=3\r]
>Feb 23 08:31:22.18: [ 8050]: --> [5:ERROR]
>Feb 23 08:31:22.18: [ 8050]: Error sending T.30 prologue frames
>Feb 23 08:31:22.18: [ 8050]: SEND training at v.27ter 4800 bit/s
>Feb 23 08:31:22.18: [ 8050]: <-- [9:AT+FTH=3\r]
>Feb 23 08:31:22.19: [ 8050]: --> [5:ERROR]
>Feb 23 08:31:22.19: [ 8050]: Error sending T.30 prologue frames
>Feb 23 08:31:22.19: [ 8050]: SEND training at v.27ter fallback mode 2400
bit/s
>Feb 23 08:31:22.19: [ 8050]: <-- [9:AT+FTH=3\r]
>Feb 23 08:31:22.20: [ 8050]: --> [5:ERROR]
>Feb 23 08:31:22.20: [ 8050]: Error sending T.30 prologue frames
>Feb 23 08:31:22.20: [ 8050]: TRAINING failed
>Feb 23 08:31:22.20: [ 8050]: SEND: Failure to train remote modem at 2400

I can interpret this log for you, it's saying that when it first began
communicating with the remote system that it was told to train at 9600
baud.  Then it went to send data, and it lost the carrier on the remote, so
it then proceeded to attempt retrains at successively slower baud rates
(which weren't likely to work anyway) which all failed.

If the failure is consistent, then I'd say it's either a HylaFAX bug or a
bad modem/modem config.  Where you've switched Class already, though, I'd
say the finger points towards the modem or the modem config.

Lee.




____________________ HylaFAX(tm) Users Mailing List _______________________
 To unsub: mail -s unsubscribe hylafax-users-request@hylafax.org < /dev/null