 HylaFAX The world's
most advanced open source fax server
|
[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index] [Thread Index]
[hylafax-users] Questions after 4.4.4 upgrade - Was -> Destination user reports receiving incomplete faxes
- To: "HylaFAX Users Mailing List" <hylafax-users@xxxxxxxxxxx>
- Subject: [hylafax-users] Questions after 4.4.4 upgrade - Was -> Destination user reports receiving incomplete faxes
- From: "Stott Hare" <share@xxxxxxxxxxxx>
- Date: Wed, 5 Nov 2008 16:18:45 -0500
|
So we upgraded to 4.4.4 in an effort to
resolve a small subset of our recipients getting incomplete faxes. Post
upgrade, I’ve been able to get most of the settings tweaked back towards
what our processes were expecting output wise, but still have some more work to
be done there, notably the following two finesse items:
However, since the upgrade we have had
significantly more failures than before. Used to be <10 failed faxes a
week, now we’re seeing 20+ a night. My assumption is these new
errors will be tracked back to either a configuration setting, or possibly
modem firmware etc that isn’t as happy with Hylafax 4.4.4. For
reference, we are running Ubuntu Server 6.06 (1gig ram, 2 xeon 3.4GHz) and a
Multi-Tech MT5656ZDX-V. We purchased that modem specifically as it was
one of the ones on the recommended hardware list. The most common failure messages are:
I’ve been reading the archives for
past mention of these reasons, but haven’t made much headway and am open
to suggestions on things to check or change. If it would help for me to
attach any config files, let me know which and I will follow up with that
information.
I examined the
/var/spool/hylafax/info file for one of the numbers that had this error but found
“hasV17Trouble:no” supportsVRes:3 supports2DEncoding:no supportsMMR:no hasV34Trouble:no hasV17Trouble:no supportsPostScript:no supportsBatching:yes calledBefore:yes maxPageWidth:1728 maxPageLength:65535 maxSignallingRate:"9600" minScanlineTime:"20ms/10ms" remoteCSI:"724xxxyyyy" remoteNSF:"00
00 56 55 55 00 88 90 80 5F 00" remoteDIS:"00
72 1D 21 01 88" sendFailures:2 lastSendFailure:"Unspecified
Transmit Phase C error" dialFailures:0 lastDialFailure:"No
carrier detected" pagingProtocol:"ixo"
Previous mention of this
seems to point to bad phone lines (our hadn’t exhibited issue pre-upgrade
and have been tested fine within past year), or possibly a bug requiring
upgrade (which we just did). Hoping there is a config setting we can
tweak here. Thanks in advance! -Stott Hare BlueTarp Financial From: Darren Nickerson
[mailto:darren.nickerson@xxxxxxxx] There are 4.4.4 packages available for most OSes these days, but
there's nothing wrong with a sysadmin who fears change ;-) To disable ECM, try adding '-E' to your sendfax commandline. Here's the
relevant excerpt from the sendfax UNIX manual page: -E Disable
use of the Error Correction Mode (ECM) when trans-
mitting page data. Setting ECM to false will limit the max-
imum speed to 14400 bps. By default HylaFAX will attempt to
use ECM when both the trasmitting modem and receiving
device support it. Note that international calls are some-
times faster when ECM is disabled. Beware also that some
modems and/or facsimile devices do not properly implement
ECM causing transmission failures. -Darren On Aug 12, 2008, at 2:19 PM, Stott Hare wrote:
Thanks Darren. I’ll see if I
can nudge the systems admin to upgrade our Hylafax server to 4.4.4. I
know last time I mentioned it he grumbled about having to do a special build or
some such. How would I configure Hylafax to disable
Error Correction for a specific destination fax only? This isn’t
something I’m familiar with, and initial web searches didn’t reveal
the answer. Thanks again! -Stott From: Darren Nickerson [mailto:darren.nickerson@xxxxxxxx] Stott, Your logs do indicate that ECM is
coming into play here to retransmit frame number 13, so you do have a little
signal degradation going on, but this is not uncommon and should in itself be
causing a problem. It's possible with such an old version of HylaFAX that
you're hitting a bug that's fixed in the current 4.4.4 release, so I recommend
upgrading if that's an option for you. If the problem persists in 4.4.4 there's
a lot more elaborate test procedure you could do to help pin this down. If the problem is on their side, you might
be able to work around it by disabling ECM when sending to this destination. -Darren On Aug 12, 2008, at 1:29 PM, Stott Hare
wrote:
Hello folks, I’m hoping someone can point me in
the right direction in my search for a solution. I have a particular fax
destination that indicates the faxes they are receiving (which were sent from
our Hylafax server) are incomplete or cut off mid page. I’m not
receiving errors indicating there was a failure, but the logs indicate we’ve
been getting partial page signals. Is this indicative of a noisy line, a
bad modem configuration or a problematic destination fax machine? Any
good methods for narrowing this down and resolving? Thanks in advance! -Stott From xferfaxlog: 08/11/08
21:46 SEND
000025660 ttyS4 25995
"" faxadmin@xxxxxxxxxxxx
"207784****"
"207784****" 2220072
1 0:41 0:25
"" ""
"" ""
"faxuser" "00 44 1F 22" From the specific jobs log file: Aug 11 21:46:10.57: [ 8233]: SESSION
BEGIN 000025660 1207207784**** Aug 11 21:46:10.57: [ 8233]: HylaFAX (tm)
Version 4.2.5 Aug 11 21:46:10.57: [ 8233]: SEND FAX:
JOB 25995 DEST 207784**** COMMID 000025660 DEVICE '/dev/ttyS4' FROM 'BlueTarp
Financial, Inc. <faxadmin@xxxxxxxxxxxx>'
USER faxuser Aug 11 21:46:10.57: [ 8233]: <--
[12:AT+FCLASS=1\r] Aug 11 21:46:10.60: [ 8233]: --> [2:OK] Aug 11 21:46:10.60: [ 8233]: DIAL
207784**** Aug 11 21:46:10.60: [ 8233]: <--
[16:ATDT1207784****\r] Aug 11 21:46:26.49: [ 8233]: -->
[7:CONNECT] Aug 11 21:46:27.95: [ 8233]: --> [2:OK] Aug 11 21:46:27.95: [ 8233]: REMOTE NSF
"00 00 56 55 55 00 8C 90 80 EF 00" Aug 11 21:46:27.95: [ 8233]: NSF remote
fax equipment: Brother MFC-3100C/MFC-8600 Aug 11 21:46:27.95: [ 8233]: <--
[9:AT+FRH=3\r] Aug 11 21:46:27.98: [ 8233]: -->
[7:CONNECT] Aug 11 21:46:28.66: [ 8233]: --> [2:OK] Aug 11 21:46:28.66: [ 8233]: REMOTE CSI
"207784****" Aug 11 21:46:28.66: [ 8233]: <--
[9:AT+FRH=3\r] Aug 11 21:46:28.69: [ 8233]: -->
[7:CONNECT] Aug 11 21:46:28.98: [ 8233]: --> [2:OK] Aug 11 21:46:28.98: [ 8233]: REMOTE best
rate 14400 bit/s Aug 11 21:46:28.98: [ 8233]: REMOTE max
A4 page width (215 mm) Aug 11 21:46:28.98: [ 8233]: REMOTE max
unlimited page length Aug 11 21:46:28.98: [ 8233]: REMOTE best
vres 15.4 line/mm Aug 11 21:46:28.98: [ 8233]: REMOTE
format support: MH, MR, MMR Aug 11 21:46:28.98: [ 8233]: REMOTE
supports T.30 Annex A, 256-byte ECM Aug 11 21:46:28.98: [ 8233]: REMOTE best
10 ms/scanline Aug 11 21:46:28.98: [ 8233]: USE 14400
bit/s Aug 11 21:46:28.98: [ 8233]: USE error
correction mode Aug 11 21:46:28.98: [ 8233]: SEND file
"docq/doc34110.ps;f0" Aug 11 21:46:28.98: [ 8233]: USE A4 page
width (215 mm) Aug 11 21:46:28.98: [ 8233]: USE
unlimited page length Aug 11 21:46:28.98: [ 8233]: USE 3.85
line/mm Aug 11 21:46:28.98: [ 8233]: USE 2-D MMR Aug 11 21:46:28.98: [ 8233]: USE 0
ms/scanline Aug 11 21:46:28.98: [ 8233]: SEND
training at v.17 14400 bit/s Aug 11 21:46:28.98: [ 8233]: <--
[9:AT+FRS=7\r] Aug 11 21:46:29.13: [ 8233]: --> [2:OK] Aug 11 21:46:29.13: [ 8233]: <--
[9:AT+FTH=3\r] Aug 11 21:46:30.01: [ 8233]: -->
[7:CONNECT] Aug 11 21:46:30.01: [ 8233]: <-- data
[23] Aug 11 21:46:30.01: [ 8233]: <-- data
[2] Aug 11 21:46:30.04: [ 8233]: -->
[7:CONNECT] Aug 11 21:46:30.04: [ 8233]: <-- data
[7] Aug 11 21:46:30.04: [ 8233]: <-- data
[2] Aug 11 21:46:31.17: [ 8233]: --> [2:OK] Aug 11 21:46:31.17: [ 8233]: <--
[9:AT+FTS=7\r] Aug 11 21:46:31.25: [ 8233]: --> [2:OK] Aug 11 21:46:31.25: [ 8233]: <--
[11:AT+FTM=145\r] Aug 11 21:46:31.28: [ 8233]: -->
[7:CONNECT] Aug 11 21:46:31.28: [ 8233]: DELAY 400 ms Aug 11 21:46:31.68: [ 8233]: <-- data
[1024] Aug 11 21:46:31.68: [ 8233]: <-- data
[1024] Aug 11 21:46:31.68: [ 8233]: <-- data
[652] Aug 11 21:46:31.68: [ 8233]: <-- data
[2] Aug 11 21:46:34.41: [ 8233]: --> [2:OK] Aug 11 21:46:34.41: [ 8233]: <--
[9:AT+FRH=3\r] Aug 11 21:46:34.70: [ 8233]: -->
[7:CONNECT] Aug 11 21:46:35.87: [ 8233]: --> [2:OK] Aug 11 21:46:35.87: [ 8233]: TRAINING
succeeded Aug 11 21:46:35.87: [ 8233]: SEND begin
page Aug 11 21:46:35.88: [ 8233]: SEND EOFB Aug 11 21:46:35.88: [ 8233]: SEND send
frame number 0 Aug 11 21:46:35.88: [ 8233]: SEND send
frame number 1 Aug 11 21:46:35.88: [ 8233]: SEND send
frame number 2 Aug 11 21:46:35.88: [ 8233]: SEND send
frame number 3 Aug 11 21:46:35.88: [ 8233]: SEND send
frame number 4 Aug 11 21:46:35.88: [ 8233]: SEND send
frame number 5 Aug 11 21:46:35.88: [ 8233]: SEND send frame
number 6 Aug 11 21:46:35.88: [ 8233]: SEND send
frame number 7 Aug 11 21:46:35.88: [ 8233]: SEND send
frame number 8 Aug 11 21:46:35.88: [ 8233]: SEND send
frame number 9 Aug 11 21:46:35.88: [ 8233]: SEND send
frame number 10 Aug 11 21:46:35.88: [ 8233]: SEND send
frame number 11 Aug 11 21:46:35.88: [ 8233]: SEND send
frame number 12 Aug 11 21:46:35.88: [ 8233]: SEND send
frame number 13 Aug 11 21:46:35.88: [ 8233]: SEND send
frame number 14 Aug 11 21:46:35.88: [ 8233]: SEND send
frame number 15 Aug 11 21:46:35.88: [ 8233]: SEND send
frame number 16 Aug 11 21:46:35.88: [ 8233]: SEND send
frame number 17 Aug 11 21:46:35.88: [ 8233]: SEND send
frame number 18 Aug 11 21:46:35.88: [ 8233]: SEND send
frame number 19 Aug 11 21:46:35.88: [ 8233]: SEND send
frame number 20 Aug 11 21:46:35.88: [ 8233]: SEND send
frame number 21 Aug 11 21:46:35.88: [ 8233]: SEND send
frame number 22 Aug 11 21:46:35.88: [ 8233]: SEND send
frame number 23 Aug 11 21:46:35.88: [ 8233]: DELAY 200 ms Aug 11 21:46:36.08: [ 8233]: <--
[11:AT+FTM=146\r] Aug 11 21:46:36.11: [ 8233]: -->
[7:CONNECT] Aug 11 21:46:36.11: [ 8233]: DELAY 400 ms Aug 11 21:46:36.51: [ 8233]: <-- data
[1038] Aug 11 21:46:36.51: [ 8233]: <-- data
[1045] Aug 11 21:46:36.51: [ 8233]: <-- data
[1043] Aug 11 21:46:36.51: [ 8233]: <-- data
[1038] Aug 11 21:46:38.51: [ 8233]: <-- data
[1043] Aug 11 21:46:38.51: [ 8233]: <-- data
[1039] Aug 11 21:46:38.51: [ 8233]: <-- data
[667] Aug 11 21:46:38.51: [ 8233]: <-- data
[2] Aug 11 21:46:40.34: [ 8233]: --> [2:OK] Aug 11 21:46:40.34: [ 8233]: <--
[9:AT+FTS=9\r] Aug 11 21:46:40.44: [ 8233]: --> [2:OK] Aug 11 21:46:40.44: [ 8233]: <--
[9:AT+FTH=3\r] Aug 11 21:46:41.32: [ 8233]: -->
[7:CONNECT] Aug 11 21:46:41.32: [ 8233]: <-- data
[7] Aug 11 21:46:41.32: [ 8233]: <-- data
[2] Aug 11 21:46:41.78: [ 8233]: --> [2:OK] Aug 11 21:46:41.78: [ 8233]: SEND send
PPS (partial page signal) Aug 11 21:46:41.78: [ 8233]: SEND send
EOP (no more pages or documents) Aug 11 21:46:41.78: [ 8233]: <--
[9:AT+FRH=3\r] Aug 11 21:46:41.94: [ 8233]: -->
[7:CONNECT] Aug 11 21:46:44.13: [ 8233]: --> [2:OK] Aug 11 21:46:44.13: [ 8233]: SEND recv
PPR (partial page request) Aug 11 21:46:44.13: [ 8233]: <--
[9:AT+FRS=7\r] Aug 11 21:46:44.26: [ 8233]: --> [2:OK] Aug 11 21:46:44.26: [ 8233]: SEND send
frame number 13 Aug 11 21:46:44.26: [ 8233]: SEND send
frame number 13 Aug 11 21:46:44.26: [ 8233]: DELAY 200 ms Aug 11 21:46:44.47: [ 8233]: <--
[11:AT+FTM=146\r] Aug 11 21:46:44.50: [ 8233]: -->
[7:CONNECT] Aug 11 21:46:44.50: [ 8233]: DELAY 400 ms Aug 11 21:46:44.90: [ 8233]: <-- data
[921] Aug 11 21:46:44.90: [ 8233]: <-- data
[2] Aug 11 21:46:45.45: [ 8233]: --> [2:OK] Aug 11 21:46:45.45: [ 8233]: <--
[9:AT+FTS=9\r] Aug 11 21:46:45.55: [ 8233]: --> [2:OK] Aug 11 21:46:45.55: [ 8233]: <--
[9:AT+FTH=3\r] Aug 11 21:46:46.42: [ 8233]: -->
[7:CONNECT] Aug 11 21:46:46.42: [ 8233]: <-- data
[7] Aug 11 21:46:46.42: [ 8233]: <-- data
[2] Aug 11 21:46:46.85: [ 8233]: --> [2:OK] Aug 11 21:46:46.85: [ 8233]: SEND send
PPS (partial page signal) Aug 11 21:46:46.85: [ 8233]: SEND send
EOP (no more pages or documents) Aug 11 21:46:46.85: [ 8233]: <--
[9:AT+FRH=3\r] Aug 11 21:46:47.03: [ 8233]: -->
[7:CONNECT] Aug 11 21:46:48.20: [ 8233]: --> [2:OK] Aug 11 21:46:48.20: [ 8233]: SEND recv
MCF (message confirmation) Aug 11 21:46:48.20: [ 8233]: <--
[9:AT+FRS=7\r] Aug 11 21:46:48.35: [ 8233]: --> [2:OK] Aug 11 21:46:48.35: [ 8233]: SEND end page Aug 11 21:46:48.35: [ 8233]: SEND FAX
(000025660): FROM faxadmin@xxxxxxxxxxxx TO 207784**** (page 1 of 1 sent in
0:20) Aug 11 21:46:48.36: [ 8233]: SEND FAX
(000025660): FROM faxadmin@xxxxxxxxxxxx TO 207784**** (docq/doc34110.ps;f0
sent in 0:20) Aug 11 21:46:49.37: [ 8233]: <--
[9:AT+FTH=3\r] Aug 11 21:46:50.23: [ 8233]: -->
[7:CONNECT] Aug 11 21:46:50.23: [ 8233]: <-- data
[3] Aug 11 21:46:50.23: [ 8233]: <-- data
[2] Aug 11 21:46:50.55: [ 8233]: --> [2:OK] Aug 11 21:46:50.55: [ 8233]: <--
[5:ATH0\r] Aug 11 21:46:51.73: [ 8233]: --> [2:OK] Aug 11 21:46:51.73: [ 8233]: SESSION END |
- Follow-Ups:
- Prev by Date: [hylafax-users] FreeBSD webfax
- Next by Date: Re: [hylafax-users] Questions after 4.4.4 upgrade - Was -> Destination user reports receiving incomplete faxes
- Previous by thread: [hylafax-users] FreeBSD webfax
- Next by thread: Re: [hylafax-users] Questions after 4.4.4 upgrade - Was -> Destination user reports receiving incomplete faxes
- Index(es):