Multi faxing problems Hylafax+

zootal <[email protected]> Wed, 13 Mar 2019 14:19:25 -0700
Newsgroups gmane.comp.telephony.fax.hylafax.user
Message-ID <[email protected]>
First of all, I'm using Hylafax+ 5.5.7, not "Hylafax", but the Hylafax+ 
website says go here, so I don't know if anyone here can help me or not. 
If this is the wrong place for help, please say so.

Slackware 14.1 64 bit 4.9.148 kernel. Problem existed with the 4.4.x 
kernel, a kernel upgrade did not change anything.

The modem is an older USR Courier v.everything USR 1.020.091-B. It's a 
larger modem made years ago, I'm not sure how old it is.

We sometimes queue up hundreds of faxes at a time, and the unit runs 
24/7 until it finishes the queue. These are legit faxes, btw, not a fax 
spamming operation - we send hundreds of financial statements every 
week. We are in the process of converting to an email system so with a 
bit of luck faxing will go away, but until then I need get this thing 
working.

So this is the history:

1) Configured modem as class 1. It's been running this way for a while, 
but it results in a failure rate of about 20%. Some recipient fax 
machines are worse than others, some machines almost never receive the 
fax, others never fail. I think there is a strong correlation between 
the failure rate and the type of device receiving the fax.

2) Replace old modem with brand new USR USB fax modem. Error rate jumps 
up to 50%. WTF.

3) Plug old USR back in, reconfigure as class 2.0. Errors gone! 100% 
success rate!

BUT, now I get this:

Mar 13 10:23:05.07: [11019]: <-- data [1024]
Mar 13 10:23:05.07: [11019]: <-- data [1024]
Mar 13 10:23:05.07: [11019]: <-- data [589]
Mar 13 10:23:05.07: [11019]: SENT 19021 bytes of data
Mar 13 10:23:05.07: [11019]: SEND 1D RTC
Mar 13 10:23:05.07: [11019]: <-- data [9]
Mar 13 10:23:05.07: [11019]: SEND end page
Mar 13 10:23:05.07: [11019]: SEND send EOP (no more pages or documents)
Mar 13 10:23:05.07: [11019]: <-- data [2]
Mar 13 10:23:17.62: [11019]: --> [7:+FHS:54]
Mar 13 10:23:17.62: [11019]: REMOTE HANGUP: No response to EOP repeated 
3 times (code 54)
Mar 13 10:23:17.62: [11019]: --> [2:OK]
Mar 13 10:23:18.62: [11019]: <-- [5:ATH0\r]
Mar 13 10:23:18.79: [11019]: --> [2:OK]
Mar 13 10:23:18.79: [11019]: MODEM set DTR OFF
Mar 13 10:23:18.79: [11019]: STATE CHANGE: SENDING -> MODEMWAIT (timeout 5)
Mar 13 10:23:18.79: [11019]: SESSION END

And hylafax thinks the fax failed, so it repeats this two more times. 
The recipient gets 3 copies of the same fax.

This is where I am at today, and I'm not quite sure how to proceed. I'm 
about to set retries to ONE so that when this occurs they still get 
their fax, but if I do then there won't be any busy-retry functionality 
for those times when the fax line is busy.

I know that class 1 seems to be the preferred way to go, but that gave 
us a 20% error rate. Class 2.0 gives us 100% success rate, but hylafax 
doesn't seem to recognize that the fax actually succeeded.

I'm open to suggestions. Maybe I need a new modem, but something better 
quality than the USR USB modem I tried? Should I switch from hylafax+ to 
hylafax? Is there some way to configure hylafax so it recognizes that 
the page really was received?



____________________ HylaFAX(tm) Users Mailing List _______________________
  To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi
 On UNIX: mail -s unsubscribe [email protected] < /dev/null
  *To learn about commercial HylaFAX(tm) support, mail [email protected].*