HylaFAX The world's most advanced open source fax server

[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: [hylafax-users] failed to receive all pages of multipage fax



On 2004.07.22 10:40 George Bell wrote:
Log follows for failed fax reception.
Faxmodem: MT5634ZPX-PCI
operating in Class 1 (not 1.0)
Hylafax version 4.2.0beta1

The sender was a Panasonic Fax Machine

What could have caused the T.30 T2 timeout ?

Jul 22 13:02:27.73: [ 2006]: <-- [9:AT+FTH=3\r]
Jul 22 13:02:28.68: [ 2006]: --> [7:CONNECT]
Jul 22 13:02:28.68: [ 2006]: RECV send MCF (message confirmation)
Jul 22 13:02:28.69: [ 2006]: RECV FAX (000000182): from 6098835087,
page 2 in
0:31, INF, 3.85 line/mm, 2-D MR, 14400 bit/s
Jul 22 13:02:28.69: [ 2006]: <-- HDLC<3:FF C8 31>
Jul 22 13:02:29.11: [ 2006]: --> [2:OK]
Jul 22 13:02:29.12: [ 2006]: MODEM input buffering enabled
Jul 22 13:02:29.12: [ 2006]: <-- [11:AT+FRM=146\r]
Jul 22 13:02:30.70: [ 2006]: --> [7:CONNECT]
Jul 22 13:02:30.70: [ 2006]: RECV: begin page
Jul 22 13:02:38.05: [ 2006]: RECV: 175 total lines, 3 bad lines, 1
consecutive
bad lines

Notice that 175 lines is a VERY short page (at 98 lpi that's not quite 2"). Your logging isn't turned up high enough for us to see which lines are actually corrupt, but I would suspect that at least the last line (#175) would be corrupt.


In this circumstance, I assume that some noise occurred on the line that made the modem sense a carrier drop.

Jul 22 13:02:38.06: [ 2006]: RECV: end page
Jul 22 13:02:38.06: [ 2006]: --> [10:NO CARRIER]

Indeed, the modem detected a carrier drop. However, the sender is probably still sending image data...


Jul 22 13:02:38.06: [ 2006]: <-- [9:AT+FRH=3\r]
Jul 22 13:02:38.54: [ 2006]: --> [7:CONNECT]
Jul 22 13:02:39.11: [ 2006]: --> [19:15 11 9A 1A D5 75 17 95 41 CA E4
96 AB 49
00 3F 14 10 03]
Jul 22 13:02:39.11: [ 2006]: --> [5:ERROR]
Jul 22 13:02:39.11: [ 2006]: MODEM Command error
Jul 22 13:02:39.11: [ 2006]: FCS error

Yup. Lots of this is going to happen until the sender stops sending page data. Unfortunately, if it happens for too long, then we'll hang up (which is what happened in your case, but it also looked like the sender hung up, too).


In other words, there was some line problem, or more likely, some problem with the modulator on the sender or the demodulator on the receiver, and so we got disconnected. If it is reproducible, then worry about it more. Otherwise, ignore it if you can.

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*




Project hosted by iFAX Solutions