HylaFAX The world's
most advanced open source fax server
|
|
[
Date Prev][
Date Next][
Thread Prev][
Thread Next]
[
Date Index]
[
Thread Index]
HylaFAX send/receive bug?
This is the second time that I've noticed this "bug" now.
If HylaFAX is processing an outgoing fax and is about to pick up the line
to send it, HylaFAX will not notice any incoming fax calls (rings) during
that period. Consequently, the outgoing fax fails due to a "No carrier
detected" error. If the incoming fax is patient enough, it will get
answered after about six rings when HylaFAX finally gives up looking for a
dial-tone. If the incoming fax isn't patient enough, the call will go
unanswered obviously. The outgoing fax is requeued and is sent properly
later.
I'm guessing that during that period of looking for a dial-tone HylaFAX
isn't configured/programmed to interpret a RING properly (properly being:
answering the incoming fax and postponing the outgoing until afterwards).
The session transcript is below.
I am using hylafax-4.1beta1-1rh6.i386.rpm from the ftp site with no patches
applied.
Is this problem a configuration issue or a programming bug? If a bug, is
there a patch available?
Thanks
Lee Howard
Your facsimile job to 1303-403-5596 was not sent because:
No carrier detected
The job will be retried at 12:59.
---- Transcript of session follows ----
Apr 28 12:54:50.79: [17204]: SESSION BEGIN 00000339 13034035596
Apr 28 12:54:50.79: [17204]: SEND FAX: JOB 69 DEST 1303-403-5596 COMMID
00000339
Apr 28 12:54:50.79: [17204]: DELAY 2600 ms
Apr 28 12:54:53.39: [17204]: <-- [15:ATE0V1Q0S0=0H0\r]
Apr 28 12:54:53.40: [17204]: --> [4:RING]
Apr 28 12:54:53.53: [17204]: --> [2:OK]
Apr 28 12:54:53.53: [17204]: <-- [21:ATS8=2S7=60&K3&D2&C1\r]
Apr 28 12:54:53.67: [17204]: --> [2:OK]
Apr 28 12:54:53.67: [17204]: <-- [12:AT+FCLASS=2\r]
Apr 28 12:54:53.81: [17204]: --> [2:OK]
Apr 28 12:54:53.81: [17204]: <-- [10:AT+FTBC=0\r]
Apr 28 12:54:53.95: [17204]: --> [2:OK]
Apr 28 12:54:53.95: [17204]: <-- [10:AT+FBOR=0\r]
Apr 28 12:54:54.09: [17204]: --> [2:OK]
Apr 28 12:54:54.09: [17204]: <-- [13:AT+FPHCTO=30\r]
Apr 28 12:54:54.23: [17204]: --> [2:OK]
Apr 28 12:54:54.23: [17204]: <-- [24:AT+FDCC=1,5,2,2,1,0,0,0\r]
Apr 28 12:54:54.38: [17204]: --> [2:OK]
Apr 28 12:54:54.38: [17204]: <-- [5:ATM0\r]
Apr 28 12:54:54.52: [17204]: --> [2:OK]
Apr 28 12:54:54.52: [17204]: <-- [12:AT+FCLASS=2\r]
Apr 28 12:54:54.76: [17204]: --> [2:OK]
Apr 28 12:54:54.76: [17204]: <-- [10:AT+FTBC=0\r]
Apr 28 12:54:55.00: [17204]: --> [2:OK]
Apr 28 12:54:55.00: [17204]: <-- [10:AT+FBOR=0\r]
Apr 28 12:54:55.24: [17204]: --> [2:OK]
Apr 28 12:54:55.24: [17204]: <-- [13:AT+FPHCTO=30\r]
Apr 28 12:54:55.48: [17204]: --> [2:OK]
Apr 28 12:54:55.48: [17204]: <-- [24:AT+FDCC=1,5,2,2,1,0,0,0\r]
Apr 28 12:54:55.72: [17204]: --> [2:OK]
Apr 28 12:54:55.72: [17204]: <-- [23:AT+FLID="Deanox, Inc."\r]
Apr 28 12:54:55.96: [17204]: --> [2:OK]
Apr 28 12:54:55.96: [17204]: DIAL 13034035596
Apr 28 12:54:55.96: [17204]: <-- [16:ATDT13034035596\r]
Apr 28 12:54:56.21: [17204]: --> [10:NO CARRIER]
Apr 28 12:54:56.21: [17204]: SEND FAILED: No carrier detected
Apr 28 12:54:56.21: [17204]: <-- [5:ATH0\r]
Apr 28 12:54:56.45: [17204]: --> [2:OK]
Apr 28 12:54:56.45: [17204]: SESSION END