HylaFAX The world's most advanced open source fax server

[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: [hylafax-users] RECV send RTN (retrain negative), class2



Mark Tilles wrote:

CLIP <<<<


RECV send MCF (message confirmation)
Apr 19 17:49:21.67: [ 5575]: RECV FAX (000000994): from 018168502, page 6 in
0:22, INF, 3.85 line/mm, 1-D MH, 14400 bit/s
Apr 19 17:49:21.67: [ 5575]: <-- [7:AT+FDR\r]
Apr 19 17:49:23.71: [ 5575]: --> [7:CONNECT]
Apr 19 17:49:23.71: [ 5575]: RECV: begin page
Apr 19 17:49:23.71: [ 5575]: RECV: send trigger 021
Apr 19 17:49:23.71: [ 5575]: <-- data [1]
Apr 19 17:49:23.71: [ 5575]: Copy quality checking performed by modem
Apr 19 17:49:42.17: [ 5575]: RECV: 32528 bytes of data, 176 total lines
Apr 19 17:50:00.28: [ 5575]: RECV: 32602 bytes of data, 290 total lines
Apr 19 17:50:18.32: [ 5575]: RECV: 32646 bytes of data, 439 total lines
Apr 19 17:50:37.24: [ 5575]: RECV: 31830 bytes of data, 634 total lines
Apr 19 17:50:54.26: [ 5575]: RECV: 32668 bytes of data, 698 total lines
Apr 19 17:51:12.46: [ 5575]: RECV: 32442 bytes of data, 770 total lines
Apr 19 17:51:22.92: [ 5575]: RECV: 19409 bytes of data, 813 total lines
Apr 19 17:51:22.94: [ 5575]: --> [15:+FPTS:2,816,6,5]
Apr 19 17:51:24.04: [ 5575]: --> [6:+FET:2]
Apr 19 17:51:24.04: [ 5575]: RECV recv EOP (no more pages or documents)
Apr 19 17:51:24.04: [ 5575]: --> [2:OK]
Apr 19 17:51:24.04: [ 5575]: RECV send RTN (retrain negative)
Apr 19 17:51:24.04: [ 5575]: <-- [7:AT+FDR\r]
Apr 19 17:51:26.40: [ 5575]: --> [7:+FHNG:0]
Apr 19 17:51:26.40: [ 5575]: REMOTE HANGUP: Normal and proper end of connection
(code 0)



Can someone please tell me why my MultiTech 5634-ZBA modem sends "RECV send RTN (retrain negative)"
instead of "RECV send MCF (message confirmation)"
when receiving faxes from some senders? This seems to result in false
error reports.



In Class 2 the modem is handling the copy quality checking (and correction). So although HylaFAX doesn't see the errors (because the modem "fixed" them) the modem did, and thus it correctly sends RTN to indicate to the sender that the page quality was unacceptable.


That said, the +FPTS response there indicates 816 lines of image data (which roughly corresponds to what the modem delivered to HylaFAX). Add that shortness to the size of the data (211+ K), and something seems awfully weird here.

This modem is set up in Class2, works more reliably for me than Class1.  Hylafax
5.0.3.


The MT5634 modems work well in Class 2.0 and 2.1 - I can't vouch for them in Class 2, although I expect them to work tolerably well there also. That said, I really cannot fathom them working any less reliably in Class 1 than they do in Class 2.


What problems were you having in Class 1 that convinced you that you needed to switch to 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@xxxxxxxxxxx < /dev/null *To learn about commercial HylaFAX(tm) support, mail sales@xxxxxxxxx*




Project hosted by iFAX Solutions