[hylafax-users] "Successful" Faxes never receied after delay in 4.1.8

[Bill Binko <bill-sender-4b2fd6@xxxxxxxxx>]

Hello everyone,

We have been seeing faxes sent to several destinations that were declared
"successful" by hylafax never actually print on the far end.  I've looked
at the comm logs, and have noticed that all of them have a delay between
when hylafax sends EOP (no more pages) and when the remote responds with
+FHS:0 and hylafax says "Normal and proper end of connection".

The delay seems to be between 20 and 60 seconds.  Here is a sample:

Jul 27 16:43:10.91: [16402]: <-- data [1027]
Jul 27 16:43:11.10: [16402]: <-- data [364]
Jul 27 16:43:11.10: [16402]: SENT 22890 bytes of data
Jul 27 16:43:11.10: [16402]: SEND 2D RTC
Jul 27 16:43:11.10: [16402]: <-- data [10]
Jul 27 16:43:11.28: [16402]: SEND end page
Jul 27 16:43:11.28: [16402]: SEND send EOP (no more pages or documents)
Jul 27 16:43:11.28: [16402]: <-- data [2]
Jul 27 16:43:55.50: [16402]: --> [6:+FHS:0]
Jul 27 16:43:55.50: [16402]: REMOTE HANGUP: Normal and proper end of connection (code 0)
Jul 27 16:43:55.50: [16402]: SEND recv MCF (message confirmation)
... email omitted
Jul 27 16:43:55.50: [16402]: <-- [5:ATH0\r]
Jul 27 16:43:55.50: [16402]: --> [2:OK]
Jul 27 16:43:55.50: [16402]: SESSION END

Notice the delay btween 16:43:11 and 16:43:55.

We are running Hylafax 4.1.8 on Mandrake 10.0 (hylafax-server-4.1.8-2mdk)
using three internal Multitech ZPX modems.

The modem IDs as : MODEM MULTI-TECH SYSTEMS MT5634ZPX-PCI-V92/1.25p

We are running in class 2.1 with certain features disabled due to firmware
issues.

I have been trying (unsuccessfully) to convince my client to go to
4.2.0rc2 and class 1.0.  I realize that that would probably solve most of
my problems including this one.  I can't get him to go to class 1 with
4.1.8 due to the amount of v.34 (38.4) faxing he does.

Is this a known issue, and is it fixed in 4.2.0?  If so, it would be a
great motivator for me to use to get my client to move.  Their big issue
is the "rc" status.  I've explained that it shouldn't be an issue (open
source, it being more stable than 4.1.8, etc).  So far, they want to wait.

Thanks, and I'll be happy to provide more logs if you need them.

Bill


____________________ 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*