![]() |
In my modem config files there is not a parameter like this, so I assume that the value used is the default one. Am I right?
Which one should I used to avoid this and sending only a copy of the fax sent? I am a little confuse. With 'retransmit' only send the page again when the receiver send the RTN signal?
* Fernando <fernando.alhambra@xxxxxxxxx> [070316 07:23]:
> Anyone can tell me while HylaFAX said: Your job to XXXXXXXXX was > completed successfully and we have not received the correct document? > I usually send about 200 faxes or more every day and I've got only one > or two errors like this.
From your session log: > mar 14 12:45:58.35: [31762]: SEND recv RTN (retrain negative)^M > mar 14 12:45:58.35: [31762]: SEND FAX (000000593): FROM user1@xxxxxxx TO XXXXXXXXX (page 1 of 1 sent in 0:37)^M > mar 14 12:45:58.35: [31762]: SEND FAX (000000593): FROM user1@xxxxxxx TO XXXXXXXXX (docq/doc557.ps;01 sent in 0:37)^M
I would look at the setting of RTNHandlingMethod in your device config file. My guess is ithat it's set to Ignore?
From the 4.3.2 man page: http://www.hylafax.org/man/4.3.2/hylafax-config.4f.php
RTNHandlingMethod string Retransmit-Ignore RTN signal handling method
RTNHandlingMethod
Specifies how to react to an RTN signal received from the remote: one of '' Retransmit '', '' Giveup '','' Ignore '', or '' Retransmit-Ignore ''.
'' Retransmit '' assumes that the page is not received succesfully. HylaFAX will make up to two additional attempts to send the page, decreasing signalling rate and retraining. If RTN continues, up to 2 additional calls will be placed. The downside is that if the remote always responds with RTN, the page will be sent 9 times and no following pages will be sent. Many fax machines will not behave this way, although T.30 specification seems clear that this is the intent of the RTN signal.
Many fax machines will interpret RTN as meaning to not send the same data again. That is because RTN may indicate problems with flow control, incorrectly encoded T.4 data, or some incompatibility other than line noise. Fax machines that interpret RTN this way will disconnect and require a manual retransmission. This ''over and out'' behaviour can be activated by the '' Giveup '' value. The advantage to this behavior is that the same page of image data will not be sent multiple times, but the downside is that the following pages will not be sent.
'' Ignore '' is similar to '' Giveup '' in that it makes the assumption the data cannot be automatically accepted by the receiver. However, rather than disconnecting the page of image data is abandoned and processing moves on to the next. The remote is left to decide what to do with the unacceptable page of image data. The downside to this behavior, is that the remote may or may not have kept the page, depending on its interpretation of the RTN signal - but it does allow us to continue on to the next page.
'' Retransmit-Ignore '' is a combination of '' Retransmit '' and '' Ignore ''. The page of image data is retransmitted up to two additional times, but rather than disconnecting after a third RTN signal for the same page, processing then continues on to the next page. This approach is an effort to satisfy both interpretations of an RTN signal. It allows the receiver to hopefully receive a better copy of the image data while not failing to send subsequent pages. If the receiver saves or prints a copy of pages for which it transmits RTN, then it could save or print up to three copies of every page.
-- Aidan Van Dyk Create like a god, aidan@xxxxxxxxxxx command like a king, http://www.highrise.ca/ work like a slave.
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFF+o12uVxNPsxNPScRAtnsAJ0VIgpD4NXhNDowtFs1PU8rATmBGwCeJ2q3 CGaHgYK4/fUWcPunvIy+NG0= =e2DD -----END PGP SIGNATURE-----
-- FAP
____________________ 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*