Outbound fax suddenly doesn't work, T30 T1 Timeout

Jeroen

Joined
Feb 3, 2009
Messages
1
Likes
0
Points
0
#1
Hello,

I'm currently running HylaFAX Version 4.3.3 on CentOS 5 2.6.18-53.1.19.el5 on several IAX modems.
The HylaFAX installation came with a popular PBX distribution called Elastix(1.3-2).

There have been no configuration changes nor have there been any updates executed.
Out of the blue I'm unable to send any faxes over Hylafax. It has worked fine for several months.

When sending any random fax it will promptly give me the errormessage "No Answer (T.30 T1 timeout)" on the senders end with the following tracelog:


Sending end>
Feb 02 08:51:01.50: [ 4922]: SESSION BEGIN 000000014 [removed phonenumber]
Feb 02 08:51:01.50: [ 4922]: HylaFAX (tm) Version 4.3.3
Feb 02 08:51:01.50: [ 4922]: SEND FAX: JOB 1 DEST [removed phonenumber] COMMID 000000014 DEVICE '/dev/ttyIAX1' FROM 'root <j.vanvierzen@xxxxxxxxx>' USER root
Feb 02 08:51:01.50: [ 4922]: STATE CHANGE: RUNNING -> SENDING
Feb 02 08:51:01.50: [ 4922]: <-- [12:AT+FCLASS=1\r]
Feb 02 08:51:01.50: [ 4922]: --> [2]
Feb 02 08:51:01.50: [ 4922]: MODEM set XON/XOFF/FLUSH: input ignored, output disabled
Feb 02 08:51:01.50: [ 4922]: DIAL [removed phonenumber]
Feb 02 08:51:01.50: [ 4922]: <-- [15:ATDT[removed phonenumber]\r]
Feb 02 08:51:06.18: [ 4922]: --> [7]
Feb 02 08:51:16.18: [ 4922]: MODEM TIMEOUT: receiving HDLC frame data
Feb 02 08:51:16.18: [ 4922]: <-- data [1]
Feb 02 08:51:16.20: [ 4922]: --> [2]
Feb 02 08:51:16.20: [ 4922]: DELAY 200 ms
Feb 02 08:51:16.40: [ 4922]: <-- [9:AT+FRH=3\r]
Feb 02 08:51:23.40: [ 4922]: --> [0:]
Feb 02 08:51:23.40: [ 4922]: MODEM <Empty line>
Feb 02 08:51:23.40: [ 4922]: MODEM TIMEOUT: waiting for v.21 carrier
Feb 02 08:51:23.40: [ 4922]: <-- data [1]
Feb 02 08:51:23.40: [ 4922]: --> [2]
Feb 02 08:51:23.40: [ 4922]: DELAY 200 ms
Feb 02 08:51:23.60: [ 4922]: <-- [9:AT+FRH=3\r]
Feb 02 08:51:28.76: [ 4922]: ABORT: job abort requested
Feb 02 08:51:30.60: [ 4922]: --> [0:]
Feb 02 08:51:30.60: [ 4922]: MODEM <Empty line>
Feb 02 08:51:30.60: [ 4922]: MODEM TIMEOUT: waiting for v.21 carrier
Feb 02 08:51:30.60: [ 4922]: <-- data [1]
Feb 02 08:51:30.60: [ 4922]: --> [2]
Feb 02 08:51:30.60: [ 4922]: DELAY 200 ms
Feb 02 08:51:30.80: [ 4922]: <-- [9:AT+FRH=3\r]
Feb 02 08:51:37.81: [ 4922]: --> [0:]
Feb 02 08:51:37.81: [ 4922]: MODEM <Empty line>
Feb 02 08:51:37.81: [ 4922]: MODEM TIMEOUT: waiting for v.21 carrier
Feb 02 08:51:37.81: [ 4922]: <-- data [1]
Feb 02 08:51:37.81: [ 4922]: --> [2]
Feb 02 08:51:37.81: [ 4922]: DELAY 200 ms
Feb 02 08:51:38.01: [ 4922]: <-- [9:AT+FRH=3\r]
Feb 02 08:51:45.01: [ 4922]: --> [0:]
Feb 02 08:51:45.01: [ 4922]: MODEM <Empty line>
Feb 02 08:51:45.01: [ 4922]: MODEM TIMEOUT: waiting for v.21 carrier
Feb 02 08:51:45.01: [ 4922]: <-- data [1]
Feb 02 08:51:45.01: [ 4922]: --> [2]
Feb 02 08:51:45.01: [ 4922]: DELAY 200 ms
Feb 02 08:51:45.21: [ 4922]: <-- [9:AT+FRH=3\r]
Feb 02 08:51:52.21: [ 4922]: --> [0:]
Feb 02 08:51:52.21: [ 4922]: MODEM <Empty line>
Feb 02 08:51:52.21: [ 4922]: MODEM TIMEOUT: waiting for v.21 carrier
Feb 02 08:51:52.21: [ 4922]: <-- data [1]
Feb 02 08:51:52.21: [ 4922]: --> [2]
Feb 02 08:51:52.21: [ 4922]: DELAY 200 ms
Feb 02 08:51:52.41: [ 4922]: No answer (T.30 T1 timeout)
Feb 02 08:51:52.41: [ 4922]: SEND FAILED: JOB 1 DEST [removed phonenumber] ERR No answer (T.30 T1 timeout)
Feb 02 08:51:52.41: [ 4922]: <-- [9:AT+FTH=3\r]
Feb 02 08:51:52.43: [ 4922]: --> [7]
Feb 02 08:51:52.43: [ 4922]: <-- HDLC<3:FF C8 DF>
Feb 02 08:51:52.43: [ 4922]: <-- data [2]
Feb 02 08:51:52.43: [ 4922]: MODEM input buffering enabled
Feb 02 08:51:52.43: [ 4922]: SEND FAILED: JOB 1 DEST [removed phonenumber] ERR Call aborted by user
Feb 02 08:51:52.43: [ 4922]: <-- [5:ATH0\r]
Feb 02 08:51:53.62: [ 4922]: --> [10:NO CARRIER]
Feb 02 08:51:53.62: [ 4922]: MODEM No carrier
Feb 02 08:51:53.62: [ 4922]: MODEM set DTR OFF
Feb 02 08:51:53.62: [ 4922]: MODEM set baud rate: 0 baud (flow control unchanged)
Feb 02 08:51:53.62: [ 4922]: STATE CHANGE: SENDING -> MODEMWAIT (timeout 5)
Feb 02 08:51:53.62: [ 4922]: SESSION END

On the receiving end I noticed a similar problem, it appears to me that one end isn
 

Members online

Latest posts

Forum statistics

Threads
30,901
Messages
130,885
Members
17,562
Latest member
colak
Top