Re: [hylafax-users] (cvs) RTN with 2-D, ok (MCF) with 1-D

[Dmitry Bely <dbely@mail.ru>]

Giulio Orsero <giulioo@pobox.com> writes:

> Note: there's a difference in results between HylaFAX from April 2000,
> and the latest cvs (20001022)
> 
> ==================
> RECEIVING SIDE:
> - software: Win98+MSFax+MSExchange client
> - modem-fax: Trust AE1414
> 
> SENDING SIDE:
> - software: HylaFAX  cvs 20001022
> 
> - modem-fax #1: Class1, Rockwell chipset
> 	V2.083-K56_DLS / RCV56DPF L8570A Rev 47.22/47.22
> 
> - modem-fax #2: Class1, TOPIC chipset
> 	TP560 Data/Fax/Voice 56K Modem
> 	External Controller Ver1.20, CheckSum=2FF2 Date:Feb 17 18:35
> 	DSP Ver1.10 CheckSum=7A64 Date:Feb 16 09:00
> =====================
> 
> modem-fax #1 can send to the Trust with no problem whatsoever, both 1-D
> and 2-D.
> 
> modem-fax #2 can send to the Trust with no problems only in 1-D;
> 2-D causes the following:
> - RTN, ignored with RTNHandlingMethod
> - The receiving side see the fax flagged as <Partially Received> in
> MSExchange (the fax is fully received, though)
> - The tiff file created on the receiving side has all the data, but from
> below  the last line of text to to the end of the page there's a
> "barcode" effect.

hmm, probably RTC is missed by the receiving side.

> Documents are 1 page only, postscript or ascii.
> Fully reproducible, all fax-modems are "in house" so I can do all sort
> of tests.
> 
> I know the problem may be the fax-modem #2, the point is that if I use
> the same modem-fax on the same line to the same receiving fax using
> MSFax, then the fax goes through ok (fully received, not <Partially
> received>). I don't know if MSFax does 2-D, though.
> 
> Also, there are difference in behavior with HylaFAX beta2 (april 2000).
> April 2000:
> - sometimes it gets RTN, retries and is ok (so the fax completes ok in 1
> call and 2 tries in the same call); sometimes it goes through ok with 1
> try in 1 call.
> - if I place the call at 12000bps then it goes ok with 1 call and 1 try.
> Oct 2000:
> -always gets RTN and does not complete the call succesfully (unless I
> use RTNHandlingMethod).
> The config file used is the same (normal config for class1)
> 
> Fax-modem #2 can succesfully use 2-D with another fax machine.
> 
> I searched for a firmware upgrade for the "topic" chipset, but found
> nothing.
> 
> ======== 2-D
> Oct 23 18:11:41.33: [ 2892]: SENT 24305 bytes of data
> Oct 23 18:11:41.33: [ 2892]: SEND 2D RTC
> Oct 23 18:11:41.33: [ 2892]: <-- data [30]
> Oct 23 18:11:41.33: [ 2892]: <-- data [2]
> Oct 23 18:11:41.33: [ 2892]: SEND end page
> Oct 23 18:11:43.64: [ 2892]: --> [2:OK]
> Oct 23 18:11:43.64: [ 2892]: MODEM set XON/XOFF/DRAIN: input ignored,
> output disabled
> Oct 23 18:11:43.64: [ 2892]: DELAY 95 ms
> Oct 23 18:11:43.74: [ 2892]: SEND send EOP (no more pages or documents)
> Oct 23 18:11:43.74: [ 2892]: <-- [9:AT+FTH=3\r]
> Oct 23 18:11:43.79: [ 2892]: --> [7:CONNECT]
> Oct 23 18:11:43.79: [ 2892]: <-- HDLC<3:FF C8 F4>
> Oct 23 18:11:43.79: [ 2892]: <-- data [3]
> Oct 23 18:11:43.79: [ 2892]: <-- data [2]
> Oct 23 18:11:45.11: [ 2892]: --> [1:^Q]
> Oct 23 18:11:45.11: [ 2892]: --> [2:OK]
> Oct 23 18:11:45.11: [ 2892]: <-- [9:AT+FRH=3\r]
> Oct 23 18:11:45.44: [ 2892]: --> [7:CONNECT]
> Oct 23 18:11:46.53: [ 2892]: --> HDLC<5:FF C8 32 75 EC>
> Oct 23 18:11:46.54: [ 2892]: --> [2:OK]
> Oct 23 18:11:46.54: [ 2892]: SEND recv RTN (retrain negative)
> Oct 23 18:11:46.54: [ 2892]: SEND FAX (00000024): FROM go@i4 TO
> 0,01234567890 (pag
> 
> 
> ==== 1-D
> Oct 23 18:12:58.43: [ 2906]: SENT 33774 bytes of data
> Oct 23 18:12:58.43: [ 2906]: SEND 1D RTC
> Oct 23 18:12:58.43: [ 2906]: <-- data [29]
> Oct 23 18:12:58.43: [ 2906]: <-- data [2]
> Oct 23 18:12:58.43: [ 2906]: SEND end page
> Oct 23 18:13:01.10: [ 2906]: --> [2:OK]
> Oct 23 18:13:01.10: [ 2906]: MODEM set XON/XOFF/DRAIN: input ignored,
> output disabled
> Oct 23 18:13:01.10: [ 2906]: DELAY 95 ms
> Oct 23 18:13:01.20: [ 2906]: SEND send EOP (no more pages or documents)
> Oct 23 18:13:01.20: [ 2906]: <-- [9:AT+FTH=3\r]
> Oct 23 18:13:01.25: [ 2906]: --> [7:CONNECT]
> Oct 23 18:13:01.25: [ 2906]: <-- HDLC<3:FF C8 F4>
> Oct 23 18:13:01.25: [ 2906]: <-- data [3]
> Oct 23 18:13:01.25: [ 2906]: <-- data [2]
> Oct 23 18:13:02.57: [ 2906]: --> [1:^Q]
> Oct 23 18:13:02.57: [ 2906]: --> [2:OK]
> Oct 23 18:13:02.57: [ 2906]: <-- [9:AT+FRH=3\r]
> Oct 23 18:13:02.90: [ 2906]: --> [7:CONNECT]
> Oct 23 18:13:03.99: [ 2906]: --> HDLC<5:FF C8 31 45 8F>
> Oct 23 18:13:04.00: [ 2906]: --> [2:OK]
> Oct 23 18:13:04.00: [ 2906]: SEND recv MCF (message confirmation)
> Oct 23 18:13:04.00: [ 2906]: SEND FAX (00000025): FROM go@i4 TO
> 0,01234567890 (pa
> 
> 
> Any suggestion (ie.: where to get firmware, if the topic chipset has
> upgradable firmware) is appreciated.

Could you try to connect both modems to the Hylafax server and send the
same fax from modem #2 to modem #1? The log on receiving side is very
interesting. Also save intermediate TIFF -- it would help to catch the bug
if it really exists.

Hope to hear from you soon,
Dmitry


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