Re: [hylafax-users] COMREC error (code 72), Normal and proper end of connection,

[Lee Howard <faxguy@xxxxxxxxxxxxxxxx>]

Giuseppe Sacco wrote:
> The log of first call is:
>
> Aug 30 09:36:07.25: [ 3464]: SESSION BEGIN 000002874 3902670YYYYY
> Aug 30 09:36:07.25: [ 3464]: HylaFAX (tm) Version 6.0.3
> Aug 30 09:36:07.25: [ 3464]: <-- [4:ATA\r]
> Aug 30 09:36:09.39: [ 3464]: --> [3:FAX]
> Aug 30 09:36:21.01: [ 3464]: --> [5:+FCON]
> Aug 30 09:36:21.01: [ 3464]: ANSWER: FAX CONNECTION  DEVICE '/dev/ttyS0'
> Aug 30 09:36:21.01: [ 3464]: STATE CHANGE: ANSWERING -> RECEIVING
> Aug 30 09:36:21.02: [ 3464]: RECV FAX: begin
> Aug 30 09:36:22.67: [ 3464]: --> [29:+FTSI: "       +3902607XXXXX"]
> Aug 30 09:36:22.67: [ 3464]: REMOTE TSI "+3902607XXXXX"
> Aug 30 09:36:23.01: [ 3464]: --> [22:+FDCS: 1,5,0,2,0,0,0,0]
> Aug 30 09:36:23.01: [ 3464]: REMOTE wants 14400 bit/s
> Aug 30 09:36:23.01: [ 3464]: REMOTE wants A4 page width (215 mm)
> Aug 30 09:36:23.01: [ 3464]: REMOTE wants unlimited page length
> Aug 30 09:36:23.01: [ 3464]: REMOTE wants 7.7 line/mm
> Aug 30 09:36:23.01: [ 3464]: REMOTE wants 1-D MH
> Aug 30 09:36:23.12: [ 3464]: --> [2:OK]
> Aug 30 09:36:23.12: [ 3464]: <-- [7:AT+FDR\r]
> Aug 30 09:36:30.51: [ 3464]: --> [29:+FTSI: "       +3902607XXXXX"]
> Aug 30 09:36:30.51: [ 3464]: REMOTE TSI "+3902607XXXXX"
> Aug 30 09:36:45.57: [ 3464]: --> [9:+FHNG: 72]
> Aug 30 09:36:45.57: [ 3464]: REMOTE HANGUP: COMREC error (code 72)
> Aug 30 09:36:46.40: [ 3464]: --> [2:OK]
> Aug 30 09:36:46.40: [ 3464]: RECV FAX (000002874): recvq/fax000001954.tif from +3902607XXXXX, route to <unspecified>, 0 pages in 0:00:25
> Aug 30 09:36:46.42: [ 3464]: RECV FAX: 
> Aug 30 09:36:46.42: [ 3464]: RECV FAX: bin/faxrcvd "recvq/fax000001954.tif" "ttyS0" "000002874" ""
> Aug 30 09:36:46.42: [ 3464]: RECV FAX: end
> Aug 30 09:36:46.42: [ 3464]: SESSION END
>   

The HylaFAX bug on this call is that it did not assign an error 
message.  So faxrcvd will think that this call was a successful fax.  
This bug is probably unique to the recent .org versions as it did not 
exist in 4.2.5...

http://article.gmane.org/gmane.comp.telephony.fax.hylafax.user/16720

The relevant code is somewhat different from what I see in HylaFAX+ 
5.4.2, so something's changed in the .org version.

As far as why the COMREC error occurred in the first place, the Class 2 
modem hides enough of the fax protocol that we really don't know what 
happened and even less do we know why.  From what I see it seems that 
the sender and the modem cannot negotiate a successful training, and 
then the sender disconnects with DCN.  So it's probably a line audio 
quality problem, but it could be a compatibility problem between the 
modem and the sender.

> while log of call 2 is:
>
> Aug 30 09:38:30.48: [ 3464]: SESSION BEGIN 000002875 3902670YYYYY
> Aug 30 09:38:30.48: [ 3464]: HylaFAX (tm) Version 6.0.3
> Aug 30 09:38:30.48: [ 3464]: <-- [4:ATA\r]
> Aug 30 09:38:32.09: [ 3464]: --> [3:FAX]
> Aug 30 09:38:39.01: [ 3464]: --> [5:+FCON]
> Aug 30 09:38:39.01: [ 3464]: ANSWER: FAX CONNECTION  DEVICE '/dev/ttyS0'
> Aug 30 09:38:39.01: [ 3464]: STATE CHANGE: ANSWERING -> RECEIVING
> Aug 30 09:38:39.01: [ 3464]: RECV FAX: begin
> Aug 30 09:38:40.68: [ 3464]: --> [29:+FTSI: "       +3902607XXXXX"]
> Aug 30 09:38:40.68: [ 3464]: REMOTE TSI "+3902607XXXXX"
> Aug 30 09:38:40.98: [ 3464]: --> [22:+FDCS: 1,5,0,2,0,0,0,0]
> Aug 30 09:38:40.98: [ 3464]: REMOTE wants 14400 bit/s
> Aug 30 09:38:40.98: [ 3464]: REMOTE wants A4 page width (215 mm)
> Aug 30 09:38:40.98: [ 3464]: REMOTE wants unlimited page length
> Aug 30 09:38:40.98: [ 3464]: REMOTE wants 7.7 line/mm
> Aug 30 09:38:40.98: [ 3464]: REMOTE wants 1-D MH
> Aug 30 09:38:41.09: [ 3464]: --> [2:OK]
> Aug 30 09:38:41.09: [ 3464]: <-- [7:AT+FDR\r]
> Aug 30 09:38:48.61: [ 3464]: --> [29:+FTSI: "       +3902607XXXXX"]
> Aug 30 09:38:48.61: [ 3464]: REMOTE TSI "+3902607XXXXX"
> Aug 30 09:38:56.55: [ 3464]: --> [29:+FTSI: "       +3902607XXXXX"]
> Aug 30 09:38:56.55: [ 3464]: REMOTE TSI "+3902607XXXXX"
> Aug 30 09:39:04.49: [ 3464]: --> [29:+FTSI: "       +3902607XXXXX"]
> Aug 30 09:39:04.49: [ 3464]: REMOTE TSI "+3902607XXXXX"
> Aug 30 09:39:19.69: [ 3464]: --> [29:+FTSI: "       +3902607XXXXX"]
> Aug 30 09:39:19.69: [ 3464]: REMOTE TSI "+3902607XXXXX"
> Aug 30 09:39:26.28: [ 3464]: --> [8:+FHNG: 0]
> Aug 30 09:39:26.28: [ 3464]: REMOTE HANGUP: Normal and proper end of connection (code 0)
> Aug 30 09:39:27.11: [ 3464]: --> [2:OK]
> Aug 30 09:39:27.11: [ 3464]: RECV FAX (000002875): recvq/fax000001955.tif from +3902607XXXXX, route to <unspecified>, 0 pages in 0:00:48
> Aug 30 09:39:27.11: [ 3464]: RECV FAX: Normal and proper end of connection
> Aug 30 09:39:27.12: [ 3464]: RECV FAX (000002875): session with +3902607XXXXX terminated abnormally: Normal and proper end of connection
> Aug 30 09:39:27.12: [ 3464]: RECV FAX: bin/faxrcvd "recvq/fax000001955.tif" "ttyS0" "000002875" "Normal and proper end of connection"
> Aug 30 09:39:27.12: [ 3464]: RECV FAX: end
> Aug 30 09:39:27.12: [ 3464]: Normal and proper end of connection
> Aug 30 09:39:27.12: [ 3464]: SESSION END

This is basically the same thing as above, but this time the +FHNG 
message was different, and so the HylaFAX bug was apparently not 
triggered.  This time the sender apparently disconnected in a way that 
made the modem report it as "normal".

If you can switch the modem to Class 1 then do that.  If you can't, then 
you'll want to consult with the modem manufacturer or get a different modem.

Thanks,

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*