Re: [hylafax-users] T2 timeout

[Lee Howard <faxguy@xxxxxxxxxxxxxxxx>]

On 2003.11.14 14:05 Jeff Honken wrote:
> I have Hylafax 4.1.7 running on RedHat 7.3.  Some of my faxes keep
> getting a
> time-out error for certain transmitters.  Some go through fine.  I'm
> using a
> U.S. Robotics 5610B.  We don't seem to have problems with these
> transmissions from the same transmitters with our Brother Fax. Can
> anyone
> please help.  I've included a failed transmission log below alone with
> the
> conf file for the modem.

The specific problem you illustrate below (not just a T2 timeout) has 
been reported here a few times before.

http://www.hylafax.org/archive/2003-03/msg00178.php
http://www.hylafax.org/archive/2003-05/msg00216.php

It boils down to a problem with the USR firmware.  In versions <= 4.1.5 
this problem would cause faxgetty to hang (get stuck in an infinite 
loop), but that was fixed in 4.1.6.  You can follow the suggestions on 
those archives if you like, regarding contacting USR to fix the 
firmware.  If it's a really annoying problem for you, and assuming you 
get no help from USR, you'll probably need to get another modem before 
this problem goes away for you.

> Here's the last part of the log file.
>
> Nov 14 10:04:37.81: [ 1080]: RECV FAX (00000040): from <UNSPECIFIED>,
> page
> 18 in 0:31, INF, 3.85 line/mm, 2-D MR, 14400 bit/s
> Nov 14 10:04:37.81: [ 1080]: <-- data [3]
> Nov 14 10:04:37.81: [ 1080]: <-- data [2]
> Nov 14 10:04:38.98: [ 1080]: --> [2:OK]
> Nov 14 10:04:38.98: [ 1080]: <-- [11:AT+FRM=146\r]
> Nov 14 10:04:39.88: [ 1080]: --> [7:CONNECT]
> Nov 14 10:04:39.88: [ 1080]: RECV: begin page
> Nov 14 10:05:07.39: [ 1080]: RECV: 1063 total lines, 0 bad lines, 0
> consecutive bad lines
> Nov 14 10:05:07.39: [ 1080]: RECV: end page
> Nov 14 10:05:07.39: [ 1080]: --> [10:NO CARRIER]
> Nov 14 10:05:07.39: [ 1080]: <-- [9:AT+FRH=3\r]
> Nov 14 10:05:07.74: [ 1080]: --> [7:CONNECT]
> Nov 14 10:05:08.58: [ 1080]: --> [2:OK]
> Nov 14 10:05:08.58: [ 1080]: RECV recv MPS (more pages, same document)
> Nov 14 10:05:08.58: [ 1080]: <-- [9:AT+FRS=7\r]
> Nov 14 10:05:08.68: [ 1080]: --> [2:OK]
> Nov 14 10:05:08.68: [ 1080]: <-- [9:AT+FTH=3\r]
> Nov 14 10:05:38.68: [ 1080]: MODEM <Timeout>

Notice the time sequence.  At this point we can assume the modem's 
firmware is "locked up".

> Nov 14 10:05:38.68: [ 1080]: RECV send MCF (message confirmation)
> Nov 14 10:05:38.68: [ 1080]: RECV FAX (00000040): from <UNSPECIFIED>,
> page
> 19 in 1:01, INF, 3.85 line/mm, 2-D MR, 14400 bit/s
> Nov 14 10:05:38.68: [ 1080]: <-- data [3]
> Nov 14 10:05:38.68: [ 1080]: <-- data [2]

These bytes will cause the modem to reset, as it should...

> Nov 14 10:05:41.23: [ 1080]: --> [5:ÿ?]

This is garbage from the modem produced by the DCE resetting...

> Nov 14 10:05:41.23: [ 1080]: <-- [11:AT+FRM=146\r]
> Nov 14 10:05:41.35: [ 1080]: --> [10:AT+FRM=146]

And this is an illustration of the echo being "on" because of the reset.

> Nov 14 10:05:41.35: [ 1080]: RECV keeping unconfirmed page
> Nov 14 10:05:41.35: [ 1080]: RECV FAX (00000040): from <UNSPECIFIED>,
> page
> 20 in 0:03, INF, 3.85 line/mm, 2-D MR, 14400 bit/s
> Nov 14 10:05:41.35: [ 1080]: RECV FAX (00000040): recvq/fax00479.tif
> from
> <UNSPECIFIED>, route to <unspecified>, 20 pages in 9:58
> Nov 14 10:05:41.35: [ 1080]: RECV FAX: T.30 T2 timeout, expected page
> not
> received
> Nov 14 10:05:41.35: [ 1080]: <-- [9:AT+FTH=3\r]
> Nov 14 10:05:41.35: [ 1080]: --> [5:ERROR]

And, because you're off-hook now, this ERROR is what you get 
appropriately.

These kinds of problems seem to have surfaced relatively recently 
(i.e., with the 5610 models and others models that are as young).  It 
may be something that USR did in the firmware.  It also may be provoked 
by something HylaFAX now relatively recently does (like the 
AT+FTS/AT+FRS pauses) which you may be able to work around with a bit 
of configuration changes and testing... I don't really have any good 
ideas that way.

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@xxxxxxxxxxxx*