HylaFAX The world's
most advanced open source fax server
|
|
[
Date Prev][
Date Next][
Thread Prev][
Thread Next]
[
Date Index]
[
Thread Index]
Possible workaround for the EOP failure?
-----BEGIN PGP SIGNED MESSAGE-----
I have searched the archives, and have not really found an answer to this
question. Is there a configuration change that I can make that will fail
a job after one "No response to EOP" message? I am sending out ~25
faxes/day to a list of ~100 numbers, using HylaFax 4.1beta1-1rh6 on a
redhat 6.0 system with a USR 56K internal fax/modem (I know it is crap,
but you use what you have available). The faxes get to their intended
destination, and get there fine. I think this is a problem with the
receiving machine not following the fax protocol since when I send out the
EOP, the other machine hangs up with no acknowledgement of the EOP,
causing my machine to think that there has been some error in
transmission, ergo, it tried to re-send the job 3x. I am using class 2.0
and I have not yet tried to change the class to 1, but this will be my
next step, upon recommendation. I just thought I would ask first. Any
other needed information can be sent, and pointers to information are
appreciated.
<===============================================>
Robert D. Crawford
mailto:rdcrawford@mindspring.com
http://dennysprojects.virtualave.net
pgp key at pgpkeys.mit.edu
<===============================================>
-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 5.0i for non-commercial use
Charset: noconv
iQEVAwUBONi/JTbRA6YK8j8BAQEmZQf/bZMC1MnpI1ow7hgAvgRgcdYsjcfdunqS
Kd1TVRKpeWItwMe7zs+lRrXdDdsOHDOHGFCdJWf+0KcPv4SWcYuMP35piBIvlfBb
t4UdqO7zQXQHUxdANmPwkUyXfyTAjO3y6SnKqtk1DtNlihAWZU3IGwTa064TX1YN
ImxEn5zlVwtJnKKMo/wrsrBWanWvSEJMurs72ozbdveVmMrzz1GgLTpHAsgdyi3c
Nh0cmVm7vtvdOF1tOr3Ca2bFFN9eKAoFEieF1VJAvTlmGhSRje262P0TyfpCeX4t
8eWkowrsBoJxFPMK8fl8PZFj6SYfrsnwLno0aEW8PDLj4WPwVyoGaA==
=eamI
-----END PGP SIGNATURE-----