Re: [hylafax-users] help to solve T.30 T1 timeout

[Lee Howard <faxguy@xxxxxxxxxxxxxxxx>]

On 2005.02.14 10:09 Alexandre Biancalana wrote:
> Hi Lee and List !
>
> I set the SessionTracing to 0xFFF and get the following log off an
> transaction that the problem ocurred:

> Feb 14 15:58:49.96: [10753]: <-- [9:AT+FRH=3\r]
> Feb 14 15:58:53.07: [10753]: --> [0:]
> Feb 14 15:58:53.07: [10753]: MODEM <Empty line>
> Feb 14 15:58:53.07: [10753]: MODEM TIMEOUT: waiting for v.21 carrier
> Feb 14 15:58:53.07: [10753]: <-- data [1]
> Feb 14 15:58:53.28: [10753]: MODEM TIMEOUT: reading line from modem
> Feb 14 15:58:53.28: [10753]: MODEM <Timeout>
> Feb 14 15:58:53.28: [10753]: DELAY 8500 ms
> Feb 14 15:59:01.79: [10753]: <-- [9:AT+FTH=3\r]
> Feb 14 15:59:01.79: [10753]: --> [2:OK]

The fact that the sender did not respond outright to your prologue 
isn't unusual.  Sometimes senders do not respond right away and it 
takes a cycle or two more.

Notice, however, that there was no "OK" response to <CAN> issued from 
the modem (the "<-- data [1]") which was supposed to take it back to 
command-mode (resulting in an OK), but it didn't, and the OK response 
didn't come until later, after the next AT command.  This lack of 
response to <CAN> is pretty much a violation of T.31, so you should 
probably look to your modem manufacturer for a fix there, but HylaFAX 
does have a workaround:

  Class1RecvAbortOK: 0

in your modem config file.

> Feb 14 15:59:01.79: [10753]: DELAY 8500 ms

By this point all hope is lost, surely.


> Feb 14 15:59:12.83: [10753]: <-- [9:AT+FRH=3\r]
> Feb 14 15:59:15.94: [10753]: --> [0:]
> Feb 14 15:59:15.94: [10753]: MODEM <Empty line>
> Feb 14 15:59:15.94: [10753]: MODEM TIMEOUT: waiting for v.21 carrier
> Feb 14 15:59:15.94: [10753]: <-- data [1]
> Feb 14 15:59:16.15: [10753]: MODEM TIMEOUT: reading line from modem
> Feb 14 15:59:16.15: [10753]: MODEM <Timeout>
> Feb 14 15:59:16.15: [10753]: DELAY 8500 ms
> Feb 14 15:59:24.66: [10753]: <-- [9:AT+FTH=3\r]
> Feb 14 15:59:24.66: [10753]: --> [2:OK]

You see, it's a chronic problem.

Lee.

____________________ HylaFAX(tm) Users Mailing List _______________________
 To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi
On UNIX: mail -s unsubscribe hylafax-users-request@xxxxxxxxxxx < /dev/null
 *To learn about commercial HylaFAX(tm) support, mail sales@xxxxxxxxx*