Hylafax Mailing List Archives |
hi,
i'm having trouble with my hylafax, i cant send fax. this is my logs.
Aug 6 12:27:06 myfaxserver FaxQueuer[797]: SUBMIT JOB 5
Aug 6 12:27:06 myfaxserver FaxGetty[816]: ANSWER: Can not lock modem device
Aug 6 12:27:12 myfaxserver FaxSend[842]: MODEM ROCKWELL AC/K56/V2.200-V90_2M_DLS
Aug 6 12:27:12 myfaxserver FaxSend[842]: HylaFAX (tm) Version 4.1
Aug 6 12:27:12 myfaxserver FaxSend[842]: SEND FAX: JOB 5 DEST 6334599 COMMID 00000007
Aug 6 12:27:12 myfaxserver FaxSend[842]: DEVICE '/dev/ttyS0'
million thanks'
jhojo
-----Original Message-----
From: Lee Howard [mailto:faxguy@deanox.com]
Sent: Saturday, August 04, 2001 4:23 AM
To: Otto Brandstätter; hylafax-users@hylafax.org
Subject: Re: [hylafax-users] No response to EOP !?
At 07:35 PM 8/3/01 +0200, Otto Brandstätter wrote:
>Good evening !
>
>I am using Cypheus client software on a W2k workstation to access a
>HylaFax 4.1 server on a RedHat 6.2 server with a USR 56k Faxmodem.
>Well, it seems to work fine, but sending faxes is making problems.
>i get the following:
>[...]
>Aug 03 15:36:30.58: [ 1507]: <-- data [622]
>Aug 03 15:36:30.58: [ 1507]: SENT 63084 bytes of data
>Aug 03 15:36:30.58: [ 1507]: SEND 1D RTC
>Aug 03 15:36:30.58: [ 1507]: <-- data [9]
>Aug 03 15:36:34.79: [ 1507]: SEND end page
>Aug 03 15:36:34.79: [ 1507]: SEND send EOP (no more pages or documents)
>Aug 03 15:36:34.79: [ 1507]: <-- data [2]
>Aug 03 15:36:48.19: [ 1507]: --> [7:+FHS:54]
>Aug 03 15:36:48.19: [ 1507]: REMOTE HANGUP: No response to EOP repeated
>3 times (code 54)
>Aug 03 15:36:48.19: [ 1507]: <-- [5:ATH0\r]
>Aug 03 15:36:48.32: [ 1507]: --> [2:OK]
>Aug 03 15:36:48.32: [ 1507]: SESSION END
>
>It doesn´t make a difference, where I am sending to.... HylaFax is
>trying to resend the page until the MaxSend is reached.
>
>Does anyone know something about this ?
Yup. I hope that you're using Class 1 with this USR. And... if you are
there is yet another problem. All USR modems (including the Couriers that
I've tried) have a 110 - 150 ms pause after +FTH=3 and before the CONNECT
response. For some reason this is the catalyst in some environments to
induce "no response to EOP". And, having actually listened to the fax
squelching in these situations, you'll find that the remote isn't even
sending the MCF message, probably because it's not even hearing EOP at all.
This is not isolated to USR modems. All Lucent-chipet modems also suffer
from a similar delay, but theirs is 860 - 890 ms. To USR's benefit, on the
2nd and 3rd repeats of EOP the delay is back to normal 40 - 50 ms (Lucents
are consistently delayed), and many remote systems will respond to them at
that point. However, some do not.
The workaround for this problem is to use Class 2 with the Lucents (if
available), but I'd not recommend that you use Class 2.0 with the USRs
unless exceptionally needed. There is a way to configure your config file
(by merging the Class 1 and Class 2.0 prototype configs except for the
"ModemType" entries) so that you can use DestControls to specify ModemType,
but I'll leave that for you to figure out if you choose to be that brave ;-)
Lee.
____________________ HylaFAX(tm) Users Mailing List _______________________
To unsub: mail -s unsubscribe hylafax-users-request@hylafax.org < /dev/null
|