Re: [hylafax-users] some error logs

[Dmitry Bely <dbely@mail.ru>]

Lee Howard <faxguy@deanox.com> writes:

> Okay, I still didn't get it completely right.  Can somebody enlighten me as
> to where the "MODEM Command error" is coming from in the session log below?
>  I'm using a USR Sportster modem in Class 2.0.  This error only happens a
> couple times per week.  Maybe it's caused by line noise or it's somebody's
> data modem calling my fax line?
> 
> Thanks.
> 
> Lee Howard
> 
> Sep 19 00:47:02.17: [  701]: SESSION BEGIN 00000813 14354357550959
> Sep 19 00:47:02.17: [  701]: <-- [4:ATA\r]
> Sep 19 00:47:10.60: [  701]: --> [4:+FCO]
> Sep 19 00:47:10.60: [  701]: ANSWER: FAX CONNECTION
> Sep 19 00:47:10.60: [  701]: STATE CHANGE: ANSWERING -> RECEIVING
> Sep 19 00:47:10.60: [  701]: MODEM input buffering enabled
> Sep 19 00:47:10.60: [  701]: RECV FAX: begin
> Sep 19 00:47:12.74: [  701]: --> [27:+FTI:"         240 3768629"]
> Sep 19 00:47:12.74: [  701]: REMOTE TSI "240 3768629"
> Sep 19 00:47:12.74: [  701]: --> [20:+FCS:0,5,0,2,0,0,0,0]
> Sep 19 00:47:12.74: [  701]: REMOTE wants 14400 bit/s
> Sep 19 00:47:12.74: [  701]: REMOTE wants page width 1728 pixels in 215 mm
> Sep 19 00:47:12.74: [  701]: REMOTE wants unlimited page length 
> Sep 19 00:47:12.74: [  701]: REMOTE wants 3.85 line/mm
> Sep 19 00:47:12.74: [  701]: REMOTE wants 1-D MR
> Sep 19 00:47:12.74: [  701]: --> [2:OK]
> Sep 19 00:47:12.74: [  701]: <-- [7:AT+FDR\r]
> Sep 19 00:47:18.25: [  701]: --> [7:CONNECT]
> Sep 19 00:47:18.25: [  701]: RECV: begin page
> Sep 19 00:47:18.25: [  701]: RECV: send trigger 022
> Sep 19 00:47:18.25: [  701]: <-- data [1]
> Sep 19 00:47:18.71: [  701]: RECV/CQ: Bad 1D pixel count, row 12, got 2386,
> expected 1728
> Sep 19 00:47:18.87: [  701]: RECV/CQ: Bad 1D pixel count, row 13, got 1809,
> expected 1728
> Sep 19 00:47:19.30: [  701]: RECV/CQ: Adjusting for trailing noise (2 run)
> Sep 19 00:47:19.30: [  701]: RECV: 12 total lines, 0 bad lines, 0
> consecutive bad lines
> Sep 19 00:47:19.30: [  701]: --> [15:+FPS:1,15,0,0,0]

Looks like the USR's firmware bug. According to Class2/2.0 specs +FET
should be present, but it does not. Not having +FET after +FPS Hylafax
gives up here.

> Sep 19 00:47:23.40: [  701]: --> [5:ERROR]
> Sep 19 00:47:23.40: [  701]: MODEM Command error

If +FET had been found, Hylafax would have interpreted this ERROR as RTN
signal. But now it just prints the default error message.

> Sep 19 00:47:23.40: [  701]: REMOTE HANGUP: Unspecified Phase C error,
> including too much delay between TCF and +FDR command (code 90)
> Sep 19 00:47:23.40: [  701]: RECV FAX (00000813): recvq/fax00477.tif from
> 240 3768629, route to <unspecified>, 0 pages in 0:13
> Sep 19 00:47:23.40: [  701]: RECV FAX: Unspecified Phase C error, including
> too much delay between TCF and +FDR command
> Sep 19 00:47:23.40: [  701]: <-- [7:AT+FKS\r]
> Sep 19 00:47:23.64: [  701]: --> [2:OK]
> Sep 19 00:47:23.64: [  701]: RECV FAX (00000813): session with 240 3768629
> terminated abnormally: Unspecified Phase C error, including too much delay
> between TCF and +FDR command
> Sep 19 00:47:23.64: [  701]: RECV FAX: bin/faxrcvd "recvq/fax00477.tif"
> "ttyS1" "00000813" "Unspecified Phase C error, including too much delay
> between TCF and +FDR command"

Are you still sure that USR's Class2 is excellent? :-)

Hope to hear from you soon,
Dmitry




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