HylaFAX The world's most advanced open source fax server

[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index] [Thread Index]

[hylafax-users] AW: How to tell hylafax to skip a job that doesn' t work?



Title: AW: [hylafax-users] How to tell hylafax to skip a job that doesn't work?

Hi again,

Ok, my mail below was a little premature. Actually hylafax is trying during 3 minutes to connect to the modem and only after these three minutes, aborts the process. It starts again 2 minutes later for a new try.

However, now I've come across another problem: I disconnected (phone line) the fax while hylafax was sending the fax. And now, the log reads:

...snip...
Nov 29 16:57:07.65: [16366]: SEND begin page
Nov 29 16:57:07.65: [16366]: <-- data [1025]
Nov 29 16:57:07.65: [16366]: <-- data [1026]
Nov 29 16:57:07.65: [16366]: <-- data [1027]
Nov 29 16:57:07.65: [16366]: <-- data [1031]
Nov 29 16:57:07.65: [16366]: <-- data [1034]
Nov 29 16:57:08.90: [16366]: <-- data [1025]
Nov 29 16:58:28.90: [16366]: MODEM WRITE SHORT: sent 1025, wrote 232
Nov 29 16:58:28.90: [16366]: SENT 44111 bytes of data
Nov 29 16:58:28.90: [16366]: SEND abort data transfer
Nov 29 16:58:28.90: [16366]: <-- data [1]

Question 1: why is the modem still sending data [1] after it had a MODEM WRITE SHORT?

Question 2: why doesn't the process cleanly abort, also in the logs with "SESSION END" as always?

Question 3: why doesn't hylafax retry later on? It's now 15 minutes since the job started, and faxstat -f is still mentioning "Sending Job 12".

This is really a situation that stinks and I guess that in a couple of minutes, I will get a mail that says: "Your modem is wedged"...

Erich
________________________________

Von: erich.iseli@xxxxxxxxxxxxxxxx
Gesendet: Montag, 29. November 2004 15:45
An: hylafax-users@xxxxxxxxxxx
Betreff: [hylafax-users] How to tell hylafax to skip a job that doesn't work?



Hi list,
 
I'm fiddling with my hylafax installation and wondering, if there's a way to tell hylafax to try to send all the jobs in the queue, and those that don't get sent (because the line is busy, because the fax is offline etc...), to just skip them and come back later.


Right now I'm making a test on two fax machines, A and B. I turned off A, sent a fax to A, then sent a fax to B.
Just after sending job to A, faxstat -f reports "Sending job 12" and lists the related doc13.ps.12 and doc13.ps;01. Then later, the same faxstat -f is reporting "Waiting for modem to come ready" and lists in addition the doc 14.ps which is waiting to be processed.


Now, in an ideal world, the fax server should just say "no answer, ok then next job!"...
 
FYI, hylafax/log/c000000xx just reports (after the AT+... / 2:OK preliminary conversation with the modem):
DIAL 555123456
<-- [15:ATDT555123456\r]
and stops here. Nothing else, no "ABORT" or similar.
 
I'd be really happy for any hints.
 
Erich




Project hosted by iFAX Solutions