HylaFAX The world's
most advanced open source fax server
|
|
[
Date Prev][
Date Next][
Thread Prev][
Thread Next]
[
Date Index]
[
Thread Index]
[hylafax-users] FW: Modem hung indefinately... saga continues
This is a big problem. I have a 10 hour fax window which I need to send
1300 faxes in. If one of the four modems hangs at the beginning of this
window then I will not be able to meet my total fax goal. Currently the
only way to avoid this is to reboot the machine when I notice a stuck job.
I tried using faxrm on that job but it just sits there indefinately and does
not remove the job. The only way I can free up that tty is to reboot. The
faxes I am sending are only 1 page in length. HylaFAX should watch the
tty's and if a job takes longer than xx minutes to send it should abort it
and free up the tty. Loosing a modem line indefinately, until reset, is
unacceptable IMHO.
-----Original Message-----
From: hylafax-users-bounce@hylafax.org
[mailto:hylafax-users-bounce@hylafax.org]On Behalf Of Lee Howard
Sent: Tuesday, July 18, 2000 7:10 PM
To: Brendin Emslie; hylafax-users@hylafax.org
Subject: Re: [hylafax-users] Modem hung indefinately... saga continues
I've had this kind of problem before... it went on for 1/2 hour before I
noticed it and used faxrm to terminate the call. I was especially pleased
because it was long distance, too... to Redmond, Washington (to
you-know-who).
I presumed the problem to be something with the fact that my fax was on the
order of 35 pages or so, and that the recipient's fax would hang up at
approximately page 10 without any warning, and HylaFAX just kept on sending
page after page after page without getting any responses, so it would
resend each page a number of times or maybe it kept sending the data over
and over and over like you've noticed here, and I never bothered really to
analyse the logs too much, but it never loosed the phone line for at least
1/2 hour when I noticed it and ended it myself. I retried the fax in sets
of 10 pages each, and it went through normally.
HylaFAX has some imperfections when it comes to error (or non-response)
handling... mostly due, I think, to the lack of an available testing base
for troublesome fax machines. We see the errors, we have the logs, but
it's not really an option to make a change and then retry a fax a number of
times to a remote fax machine that belongs to someone else.
Lee Howard
>Jul 18 15:19:34.52: [27677]: --> [7:CONNECT]
>Jul 18 15:19:34.52: [27677]: <-- data [6]
>Jul 18 15:19:34.52: [27677]: <-- data [2]
>Jul 18 15:19:36.48: [27677]: --> [2:OK]
>Jul 18 15:19:36.56: [27677]: <-- [10:AT+FTM=48\r]
>Jul 18 15:19:37.57: [27677]: --> [7:CONNECT]
>Jul 18 15:19:37.57: [27677]: <-- data [900]
>Jul 18 15:19:37.57: [27677]: <-- data [2]
>Jul 18 15:19:39.11: [27677]: --> [2:OK]
>Jul 18 15:19:39.11: [27677]: <-- [9:AT+FRH=3\r]
>Jul 18 15:19:40.19: [27677]: --> [7:CONNECT]
____________________ HylaFAX(tm) Users Mailing List _______________________
To unsub: mail -s unsubscribe hylafax-users-request@hylafax.org < /dev/null
____________________ HylaFAX(tm) Users Mailing List _______________________
To unsub: mail -s unsubscribe hylafax-users-request@hylafax.org < /dev/null