HylaFAX The world's most advanced open source fax server

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

[hylafax-users] set a time-limit on incoming faxes



Hylafax Version: hylafax-4.2.5-1rhel4  (CentOS 4)

Using a Multitech MT5600ZDX as a class 1.0 modem

Hi,

I'm having a problem receiving faxes.  Some are taking a long, long, long time to receive, if they receive at all.  I think the problem comes from older, almost dead fax machines at some stores that fax us.  I don't care about solving this issue, just ending the calls that take too long so that the line isn't busy all the time and legitimate faxes can be received.  I'm getting log files that are 25,000 to 30,000 lines full of HDLC and receiving frame error messages.  I just want to terminate receiving all faxes after 5 minutes.  How do I do that?



Here is what happens, if this helps:

The connection is made and the Training succeeds, so far so good!  Then come a bunch of HDLC errors, I guess this is from error correction trying to make sense of the garbage that is being received.

...
May 20 11:44:02.49: [ 4245]: TRAINING succeeded
May 20 11:44:02.49: [ 4245]: <-- [9:AT+FTH=3\r]
May 20 11:44:02.54: [ 4245]: --> [7:CONNECT]
May 20 11:44:02.54: [ 4245]: <-- data [3]
May 20 11:44:02.54: [ 4245]: <-- data [2]
May 20 11:44:03.86: [ 4245]: --> [2:OK]
May 20 11:44:03.86: [ 4245]: <-- [11:AT+FRM=146\r]
May 20 11:44:04.70: [ 4245]: --> [7:CONNECT]
May 20 11:44:04.77: [ 4245]: HDLC frame not byte-oriented.  Trailing byte: 0xe0
May 20 11:44:04.84: [ 4245]: Bad HDLC terminating flag received.
May 20 11:44:04.84: [ 4245]: HDLC frame with bad address field 0xaf
May 20 11:44:04.98: [ 4245]: HDLC frame not byte-oriented.  Trailing byte: 0xfc
May 20 11:44:05.19: [ 4245]: HDLC frame not byte-oriented.  Trailing byte: 0xf0
May 20 11:44:05.26: [ 4245]: HDLC frame not byte-oriented.  Trailing byte: 0
May 20 11:44:05.26: [ 4245]: Bad HDLC terminating flag received.
May 20 11:44:05.40: [ 4245]: HDLC frame not byte-oriented.  Trailing byte: 0x80
May 20 11:44:05.47: [ 4245]: Bad HDLC terminating flag received.
... etc


The bad HDLC message keep happening for 30 minutes or so, then I start to get:


....
May 20 12:07:01.06: [ 4245]: RECV received frame number 71
May 20 12:07:01.06: [ 4245]: RECV frame FCS check failed
... etc

Which happens for another 30 minutes or so, interlaced with HDLC messages as before,



And then finally:

May 20 13:21:26.22: [ 4245]: RECV FAX (000002457): from (our customer), page 8 in 10:17, INF, 200 x\
 200 dpi, 2-D MMR, 14400 bit/s
May 20 13:21:26.24: [ 4245]: --> [7:CONNECT]
May 20 13:21:27.11: [ 4245]: --> [2:OK]
May 20 13:21:27.11: [ 4245]: RECV recv DCN (disconnect)
May 20 13:21:27.11: [ 4245]: RECV FAX: bin/faxrcvd "recvq/fax000002330.tif" "ttyS0" "000002457" ""
May 20 13:21:27.11: [ 4245]: RECV FAX: end
May 20 13:21:27.11: [ 4245]: SESSION END


Which is about 25,000 lines of log messages, and anywhere from 30 minutes to 2 hours to receive the one fax. 

I don't need to solve this issue, I just need to set a time-limit on incoming faxes so that after 5 or 10 minutes the client connection is terminated.  How do I do that?

thanks,

Kent Rhodes
kent@xxxxxxxxxxxxxx




--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.



Project hosted by iFAX Solutions