Re: [hylafax-users] Incoming Fax always drops from Panasonic fax machine

[Lee Howard <faxguy@howardsilvan.com>]

On 2003.05.26 03:39 John Williamson wrote:
> I have installed Hylafax version 4.1.5-1 from a Mandrake 9.1 binary
> distribution. I am using a zoom external V92 3049 modem which supports
> class 1 & 2 fax protocols. I have it set up as a class 1 fax. I can
> receive faxes perfectly from any fax machine bar my brother's which is
> a
> Panasonic  KX F90. To date it has never succeeded and having gone
> through the logs and the FAQ and mailing archives for the past few
> months, I am stuck. In enclose my config file and log and would be
> grateful for any suggestions.

You should be using config/lucent (selected by faxaddmodem, hopefully), 
probably, but I don't think that's the problem.

> May 25 11:54:51.50: [ 2894]: SESSION BEGIN 00000028 441623400898
> May 25 11:54:51.50: [ 2894]: HylaFAX (tm) Version 4.1.5
> May 25 11:54:51.50: [ 2894]: MODEM set XON/XOFF/FLUSH: input ignored,
> output disabled
> May 25 11:54:51.50: [ 2894]: <-- [4:ATA\r]
> May 25 11:55:00.80: [ 2894]: --> [7:CONNECT]
> May 25 11:55:00.80: [ 2894]: MODEM input buffering enabled
> May 25 11:55:00.80: [ 2894]: RECV FAX: begin
> May 25 11:55:00.80: [ 2894]: MODEM input buffering disabled
> May 25 11:55:00.80: [ 2894]: <-- HDLC<23:FF C0 02 CE B6 86 96 36 36 96
> EA 04 74 A2 74 22 04 64 04 74 4A 74 52>
> May 25 11:55:00.80: [ 2894]: <-- data [23]

Here you send TSI which looks okay.

> May 25 11:55:00.80: [ 2894]: <-- data [2]
> May 25 11:55:00.83: [ 2894]: --> [7:CONNECT]
> May 25 11:55:00.83: [ 2894]: <-- HDLC<10:FF C8 01 00 77 5F 01 79 03
> C0>
> May 25 11:55:00.83: [ 2894]: <-- data [10]

Here you send DIS reporting capabilities of V.17, high res, 2D-MR, 
unlimited page length, and 0ms scanline time.

> May 25 11:55:00.83: [ 2894]: <-- data [2]
> May 25 11:55:02.04: [ 2894]: --> [2:OK]
> May 25 11:55:02.04: [ 2894]: <-- [9:AT+FRH=3\r]
> May 25 11:55:02.59: [ 2894]: --> [7:CONNECT]
> May 25 11:55:04.27: [ 2894]: --> HDLC<25:FF C0 C2 EC 6C 4C EC 1C AC 04
> 2C EC 4C 8C 0C 04 04 04 04 18 08 08 09 11 06>
> May 25 11:55:04.28: [ 2894]: --> [5:ERROR]
> May 25 11:55:04.28: [ 2894]: MODEM Command error
> May 25 11:55:04.28: [ 2894]: FCS error

Here you get a frame from the transmitter indicating its CSI of 
"<0x90><DLE><DLE><CAN>    01274 587267" which seems highly unlikely to 
be correct given the embedded high-bit ASCII and control characters.  
The ERROR occurs because the modem uses the last two bytes (11 06), 
known as FCS, to check the validity of the previously received HDLC 
frame (in this case the CSI I translated), and the check fails... 
meaning that the TSI frame was incorrectly received.

> May 25 11:55:04.28: [ 2894]: DELAY 1500 ms

So although we may have been able to proceed without a valid CSI, we 
pause and start over...

> May 25 11:55:05.78: [ 2894]: <-- [9:AT+FTH=3\r]
> May 25 11:55:06.65: [ 2894]: --> [7:CONNECT]
> May 25 11:55:06.65: [ 2894]: <-- HDLC<23:FF C0 02 CE B6 86 96 36 36 96
> EA 04 74 A2 74 22 04 64 04 74 4A 74 52>
> May 25 11:55:06.65: [ 2894]: <-- data [23]
> May 25 11:55:06.65: [ 2894]: <-- data [2]
> May 25 11:55:06.68: [ 2894]: --> [7:CONNECT]
> May 25 11:55:06.68: [ 2894]: <-- HDLC<10:FF C8 01 00 77 5F 01 79 03
> C0>
> May 25 11:55:06.68: [ 2894]: <-- data [10]
> May 25 11:55:06.68: [ 2894]: <-- data [2]
> May 25 11:55:07.89: [ 2894]: --> [2:OK]

We sent TSI and DIS again...

> May 25 11:55:07.89: [ 2894]: <-- [9:AT+FRH=3\r]
> May 25 11:55:08.16: [ 2894]: --> [7:CONNECT]
> May 25 11:55:08.94: [ 2894]: --> HDLC<25:FF C0 02 1C 9C 1C 0C 0C 2C 04
> CC 4C 6C 8C 04 04 2C 2C 04 0C 04 04 04 EF A9>
> May 25 11:55:08.94: [ 2894]: --> [2:OK]

This time we get a valid CSI frame, saying "   0 44 1623 400898".  Is 
this an international call?

> May 25 11:55:08.94: [ 2894]: <-- [9:AT+FRH=3\r]
> May 25 11:55:08.96: [ 2894]: --> [7:CONNECT]
> May 25 11:55:09.37: [ 2894]: --> HDLC<15:FF C8 01 04 77 1F 23 01 49 01
> 01 19 00 97 91>
> May 25 11:55:09.37: [ 2894]: --> [2:OK]

But strangely it sends us a DIS (receiving) signal rather than DCS 
(transmitting).  That "FF C8 01" should be "FF C8 C1", which amounts to 
a two-bit difference, so it could be blamed on a transmission error 
again, but the FCS checks out, which almost indicates that it is 
intentional.  That is bizarre.

> May 25 11:55:09.37: [ 2894]: DELAY 1500 ms

So we pause and start over.

> May 25 11:55:10.87: [ 2894]: <-- [9:AT+FTH=3\r]
> May 25 11:55:11.74: [ 2894]: --> [7:CONNECT]
> May 25 11:55:11.74: [ 2894]: <-- HDLC<23:FF C0 02 CE B6 86 96 36 36 96
> EA 04 74 A2 74 22 04 64 04 74 4A 74 52>
> May 25 11:55:11.74: [ 2894]: <-- data [23]
> May 25 11:55:11.74: [ 2894]: <-- data [2]
> May 25 11:55:11.77: [ 2894]: --> [7:CONNECT]
> May 25 11:55:11.77: [ 2894]: <-- HDLC<10:FF C8 01 00 77 5F 01 79 03
> C0>
> May 25 11:55:11.77: [ 2894]: <-- data [10]
> May 25 11:55:11.77: [ 2894]: <-- data [2]
> May 25 11:55:12.98: [ 2894]: --> [2:OK]

Again, we send TSI and DIS...

> May 25 11:55:12.98: [ 2894]: <-- [9:AT+FRH=3\r]
> May 25 11:55:13.02: [ 2894]: --> [7:CONNECT]
> May 25 11:55:13.48: [ 2894]: --> [5:00 36 E6 10 03]

And we get junk... probably binary TCF signals.

> May 25 11:55:13.49: [ 2894]: --> [5:ERROR]
> May 25 11:55:13.49: [ 2894]: MODEM Command error
> May 25 11:55:13.49: [ 2894]: FCS error

And of course, FCS doesn't check.

> May 25 11:55:13.49: [ 2894]: DELAY 1500 ms
> May 25 11:55:14.99: [ 2894]: <-- [9:AT+FTH=3\r]
> May 25 11:55:15.86: [ 2894]: --> [7:CONNECT]
> May 25 11:55:15.86: [ 2894]: <-- HDLC<23:FF C0 02 CE B6 86 96 36 36 96
> EA 04 74 A2 74 22 04 64 04 74 4A 74 52>
> May 25 11:55:15.86: [ 2894]: <-- data [23]
> May 25 11:55:15.86: [ 2894]: <-- data [2]
> May 25 11:55:15.89: [ 2894]: --> [7:CONNECT]
> May 25 11:55:15.89: [ 2894]: <-- HDLC<10:FF C8 01 00 77 5F 01 79 03
> C0>
> May 25 11:55:15.89: [ 2894]: <-- data [10]
> May 25 11:55:15.89: [ 2894]: <-- data [2]
> May 25 11:55:17.10: [ 2894]: --> [2:OK]

You send TSI and DIS yet again...

> May 25 11:55:17.10: [ 2894]: <-- [9:AT+FRH=3\r]
> May 25 11:55:17.19: [ 2894]: --> [7:CONNECT]
> May 25 11:55:18.42: [ 2894]: --> HDLC<5:FF C8 DF 59 6F>
> May 25 11:55:18.42: [ 2894]: --> [2:OK]
> May 25 11:55:18.42: [ 2894]: RECV FAX: RSPREC error/got DCN

And the remote sends DCN (disconnect).

> May 25 11:55:18.42: [ 2894]: RECV FAX: end
> May 25 11:55:18.42: [ 2894]: SESSION END

Is this log 100% (especially the DIS signal when we should get DCS) 
reproducible?  If so, have you tried using the modem in Class 2?

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@hylafax.org < /dev/null
  *To learn about commercial HylaFAX(tm) support, mail sales@hylafax.org.*