Re: [hylafax-users] Problems receiving facsimiles, modems don't return to idle state

[Lee Howard <faxguy@xxxxxxxxxxxxxxxx>]

On 2003.11.20 07:05 Thorsten Büker wrote:

> http://www.geocrawler.com/mail/msg.php3?msg_id=9708801&list=289

Yes, this appears to be another illustration of the same problem.

> Nov 20 14:19:34.42: [21140]: <-- [7:AT+FDR\r]
> Nov 20 14:19:34.54: [21140]: --> [14:+FHT: FF 13 84]
> Nov 20 14:19:36.47: [21140]: --> [7:CONNECT]
> Nov 20 14:19:36.47: [21140]: RECV: begin page
> Nov 20 14:19:36.47: [21140]: MODEM set XON/XOFF/FLUSH: input ignored,
> output generated
> Nov 20 14:19:36.47: [21140]: RECV: send trigger 022
> Nov 20 14:19:36.47: [21140]: <-- data [1]
> Nov 20 14:19:51.64: [21140]: RECV/CQ: Bad 1D pixel count, row 1155,
> got
> 0, expected 1728
> Nov 20 14:19:51.64: [21140]: RECV/CQ: Bad 1D pixel count, row 1156,
> got
> 0, expected 1728
> Nov 20 14:19:51.64: [21140]: RECV/CQ: Bad 1D pixel count, row 1157,
> got
> 0, expected 1728
> Nov 20 14:19:51.64: [21140]: RECV/CQ: Bad 1D pixel count, row 1158,
> got
> 0, expected 1728
> Nov 20 14:19:51.64: [21140]: RECV/CQ: Bad 1D pixel count, row 1159,
> got
> 0, expected 1728
> Nov 20 14:19:51.64: [21140]: RECV: 24629 bytes of data, 1160 total
> lines
> Nov 20 14:19:51.64: [21140]: MODEM set XON/XOFF/DRAIN: input
> interpreted, output disabled

At this point HylaFAX awaits the +FPS response from the modem and will 
wait 3 minutes for it.  If there isn't a response within 3 minutes 
there should be a timeout and an error.  I assume that this is not 
happening in your case.

The code that waits (loops) and is supposed to timeout is 
ModemServer::getModemLine().  I don't see any obvious error there, and 
it seems to work fine otherwise.

The default ModemPageDoneTimeout is a rather large integer (180000).  
So it is bigger than 16-bits, so it requires a 32-bit allocation by the 
compiler. It and ModemPageStartTimeout are the only default timeout 
values that large.  You could try setting it lower, say at 60000 (one 
minute, and within a 16-bit range) to see if the size of the timeout 
value is a factor.

I can send you code patches to add some debugging info in there so that 
we can see what's actually going on.  If you can make use of them and 
want to try it out, let me know.

The catalyst to the problem, however, appears to be the lack of an 
expected modem response.  In Class 2.0 you'll need to consult the modem 
manufacturer for a firmware fix.  So HylaFAX can fix the "stuck" 
faxgetty, but the modem manufacturer must fix the modem error.

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*