Re: Multi faxing problems Hylafax+

On 03/13/2019 02:19 PM, zootal wrote:
> 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%.

I'd need to look at your logs when in Class 1 to comment with
specificity, but USR modems, including Couriers, are not particularly
reliable fax modems.=C2=A0 They do okay, but historically there have been
some firmware problems (such as with +FTS/+FRS commands) that impact
reliability somewhat.=C2=A0 Still, though, I wouldn't expect the failure =
rate
to be at 20%.

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

Well, not 100% success, because you're about to illustrate a problem
you're having in Class 2.0.=C2=A0 That said, your Class 2.0 configuration
does not include Error Correction Mode (ECM) while your Class 1
configuration likely did.=C2=A0 So, without ECM there is no assurance tha=
t
the fax image is perfectly legible (unaltered from the original) on the
receiving end... just that the receiver maintained communication
throughout the entire session and a hope that its MCF signal
necessitates as much data checking as they can perform (line and pixel
counts, basically).

> 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)

The Class 2.0 modem firmware is telling HylaFAX that it lost
communication with the receiver and cannot be certain that the receiver
got the page image data.=C2=A0 That's why HylaFAX will resend.

> 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.

It's not HylaFAX failing to recognize that the fax actually succeeded,
but rather the modem... and it may not even be the modem's fault,
either.=C2=A0 It certainly could just not have heard the response from th=
e
receiver.

> 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?

There are better modems, but that's not going to resolve your problem,
most likely.

You won't see any improvement in switching from HylaFAX+ to hylafax.org
releases.

It's probably not something that you can resolve with configuration.

Let's talk about your fax line because your failure rates in Class 1
seem to indicate that as being the most-likely culprit.=C2=A0 Where is th=
e
fax line coming from?=C2=A0 In particular, is it a VoIP line?=C2=A0 Is th=
e line
shared with some other device?=C2=A0 Does the line have call waiting enab=
led
on it?=C2=A0 Does it have DSL service on it?

Thanks,

Lee.


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