Re: flexfax: FW: facsimile not received

[Dmitry Bely <dbely@mail.ru>]

"Rimantas Zylius" <r.zylius@lrvk.lt> writes:

> i was using hylafax 4.0pl2 + Courier V-Everything, for pretty long with
> great success on mandrake6.0, box pentiumII.
> 
> for some reasons i had to make fresh install, and so i installed redhat6.2
> with hylafax 4.1beta.
> 
> all goes well, but i am unable receive faxes (i should note - on the same
> hardware) - look at the log. fax machine, that send fax thinks that all goes
> well, page is transmitted. but after page is sent some negotiations takes
> place, and fax machine indicates "Line error".
> 
> what is it all about?

Everything is wrong (see below) :-)

> rimantas
> 
> > > From: 	The HylaFAX Receive Agent
> > > Sent: 	2000 m. Gegužė 1 d. 16:27
> > > To: 	FAXMASTER
> > > Subject: 	facsimile not received
> > >
> > > An attempt to receive facsimile on ttyS2 failed because:
> > >
> > >     Normal and proper end of connection

:-)))

> > >     ---- Transcript of session follows ----
> > >
> > > May 01 20:26:03.50: [  773]: SESSION BEGIN 00000010 3702395067
> > > May 01 20:26:03.50: [  773]: <-- [4:ATA\r]
> > > May 01 20:26:13.10: [  773]: --> [5:+FCON]
> > > May 01 20:26:13.10: [  773]: ANSWER: FAX CONNECTION
> > > May 01 20:26:13.10: [  773]: RECV FAX: begin
> > > May 01 20:26:27.14: [  773]: --> [5:+FCON]
> > > May 01 20:26:29.39: [  773]: --> [32:+FTSI: "          +370 2 395067"]
> > > May 01 20:26:29.39: [  773]: REMOTE TSI "+370 2 395067"
> > > May 01 20:26:29.66: [  773]: --> [21:+FDCS:0,3,0,2,0,0,0,5]

This log was not produced by Courier modem -- it only supports Class 2.0,
but the log is obviously from Class 2 device.

> > > May 01 20:26:29.66: [  773]: REMOTE wants 9600 bit/s
> > > May 01 20:26:29.66: [  773]: REMOTE wants page width 1728 pixels in
> > > 215 mm
> > > May 01 20:26:29.66: [  773]: REMOTE wants unlimited page length
> > > May 01 20:26:29.66: [  773]: REMOTE wants 3.85 line/mm
> > > May 01 20:26:29.66: [  773]: REMOTE wants 1-D MR
> > > May 01 20:26:31.79: [  773]: --> [2:OK]
> > > May 01 20:26:31.79: [  773]: <-- [7:AT+FDR\r]
> > > May 01 20:26:31.90: [  773]: --> [5:+FCFR]
> > > May 01 20:26:33.16: [  773]: --> [7:CONNECT]
> > > May 01 20:26:33.16: [  773]: RECV: begin page
> > > May 01 20:26:33.16: [  773]: RECV: send trigger 021
> > > May 01 20:27:01.20: [  773]: RECV: 213 total lines, 212 bad lines, 93
> > > consecutive bad lines

means that syncronization had been lost (don't you think that 212 bad lines 
of 213 total are too much? :-))) You should check your Hylafax settings
(flow control etc.) Also note that Class 2.0 implementation in USR modems is
extremely buggy. If you cannot use other modem for faxing, try Class1
instead.

> > > May 01 20:27:01.20: [  773]: --> [8:+FPTS:1 ]
> > > May 01 20:27:02.37: [  773]: --> [7:+FET:2 ]
> > > May 01 20:27:02.37: [  773]: RECV recv EOP (no more pages or
> > > documents)
> > > May 01 20:27:02.37: [  773]: --> [2:OK]
> > > May 01 20:27:02.37: [  773]: RECV: REJECT page quality, 0% good lines
> > > (95% required)
> > > May 01 20:27:02.37: [  773]: RECV send RTN (retrain negative)

No surprise. Receiving modem reported that the page quality was
unacceptable...

> > > May 01 20:27:02.37: [  773]: <-- [10:AT+FPTS=2\r]
> > > May 01 20:27:02.49: [  773]: --> [2:OK]
> > > May 01 20:27:02.49: [  773]: <-- [7:AT+FDR\r]
> > > May 01 20:27:06.24: [  773]: --> [8:+FHNG:0 ]
> > > May 01 20:27:06.24: [  773]: REMOTE HANGUP: Normal and proper end of
> > > connection (code 0)

... but the remote just ignored this information and hung up.

> > > May 01 20:27:06.24: [  773]: RECV FAX (00000010): recvq/fax00010.tif
> > > from +370 2 395067, route to <unspecified>, 0 pages in 0:53
> > > May 01 20:27:06.25: [  773]: RECV FAX: Normal and proper end of
> > > connection
> > > May 01 20:27:06.25: [  773]: RECV FAX (00000010): session with +370 2
> > > 395067 terminated abnormally: Normal and proper end of connection
> > > May 01 20:27:06.25: [  773]: RECV FAX: bin/faxrcvd
> > > "recvq/fax00010.tif" "ttyS2" "00000010" "Normal and proper end of
> > > connection"

Don't believe -- the end of connection was neither normal nor proper :-)

Hope to hear from you soon,
Dmitry