Re: [hylafax-users] Problems receiving a fax

[Dmitry Bely <dbely@mail.ru>]

"Bernd Proissl" <lists@proissl.de> writes:

> To the fax protocol gurus!
> Please, can someone explain the follwing log.

:-) May I try? :-)

> It comes from a USR in Class 2.0
> HF version is HylaFAX (tm) Version 4.1beta44
> Some other test faxes worked well.
> 
> Thanks again!
> 
> Bernd
> 
> 
> --------------------------------------------------------------------------
> recvq/fax00032.tif:
> Could not open recvq/fax00032.tif; either not TIFF or corrupted.

 Hylafax does not remove .tif file if the session fails? If so, it's the
bug.

> The full document was not received because:
> 
>     RSPREC invalid response received
> 
>     ---- Transcript of session follows ----
> Sep 27 22:54:12.91: [ 2349]: SESSION BEGIN 00000040 4971619531020
> Sep 27 22:54:12.98: [ 2349]: <-- [4:ATA\r]
> Sep 27 22:54:20.54: [ 2349]: --> [4:+FCO]
> Sep 27 22:54:20.54: [ 2349]: ANSWER: FAX CONNECTION
> Sep 27 22:54:20.54: [ 2349]: STATE CHANGE: ANSWERING -> RECEIVING
> Sep 27 22:54:20.54: [ 2349]: MODEM input buffering enabled
> Sep 27 22:54:20.55: [ 2349]: RECV FAX: begin
> Sep 27 22:54:22.57: [ 2349]: --> [27:+FTI:"                    "]
> Sep 27 22:54:22.57: [ 2349]: REMOTE TSI ""
> Sep 27 22:54:22.57: [ 2349]: --> [20:+FCS:0,5,0,2,0,0,0,0]
> Sep 27 22:54:22.57: [ 2349]: REMOTE wants 14400 bit/s
> Sep 27 22:54:22.57: [ 2349]: REMOTE wants page width 1728 pixels in 215 mm
> Sep 27 22:54:22.58: [ 2349]: REMOTE wants unlimited page length
> Sep 27 22:54:22.58: [ 2349]: REMOTE wants 3.85 line/mm
> Sep 27 22:54:22.58: [ 2349]: REMOTE wants 1-D MR
> Sep 27 22:54:22.58: [ 2349]: --> [2:OK]
> Sep 27 22:54:22.58: [ 2349]: <-- [7:AT+FDR\r]
> Sep 27 22:54:27.94: [ 2349]: --> [7:CONNECT]

Harald Pollack already commented this 5 second delay between AT+FDR and
CONNECT in -devel list. The modems firmware has already failed at this
point and it is useless to the continue the session. But we do ...

> Sep 27 22:54:27.94: [ 2349]: RECV: begin page
> Sep 27 22:54:27.94: [ 2349]: RECV: send trigger 022
> Sep 27 22:54:27.94: [ 2349]: <-- data [1]

Start of Phase C (receiving the image data itself). In fact we are
completely out of sync and will get only a garbage...

> Sep 27 22:54:28.02: [ 2349]: RECV/CQ: Bad 1D pixel count, row 0, got 2267,
> expected 1728
> Sep 27 22:54:28.02: [ 2349]: RECV/CQ: Bad 1D pixel count, row 1, got 3441,
> expected 1728
> Sep 27 22:54:29.00: [ 2349]: RECV/CQ: Adjusting for trailing noise (2 run)
> Sep 27 22:54:29.00: [ 2349]: RECV: 0 total lines, 0 bad lines, 0 consecutive
> bad lines
> Sep 27 22:54:29.00: [ 2349]: --> [14:+FPS:1,2,0,0,0]

The whole "Phase C" was just 1 second! But the modem still does not care
and tries to get post-page message...

> Sep 27 22:54:39.35: [ 2349]: --> [7:+FHS:A1]
> Sep 27 22:54:39.35: [ 2349]: REMOTE HANGUP: RSPREC invalid response received
> (code A1)

And only now it wonders why there is no post-page message ... Such a
surprise! :-)

> Sep 27 22:54:39.48: [ 2349]: --> [2:OK]
> Sep 27 22:54:39.49: [ 2349]: RECV FAX (00000040): recvq/fax00032.tif from ,
> route to <unspecified>, 0 pages in 0:19
> Sep 27 22:54:39.55: [ 2349]: RECV FAX: RSPREC invalid response received
> Sep 27 22:54:39.55: [ 2349]: RECV FAX (00000040): session with  terminated
> abnormally: RSPREC invalid response received
> Sep 27 22:54:39.55: [ 2349]: RECV FAX: bin/faxrcvd "recvq/fax00032.tif"
> "ttyS0" "00000040" "RSPREC invalid response received"

More accurate diagnostics would be "Buggy Class2/2.0 modem detected --
switch it to Class1 or throw into the trash can" :-)

Hope to hear from you soon,
Dmitry




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