 HylaFAX The world's
most advanced open source fax server
|
[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index] [Thread Index]
[hylafax-users] hdlc errors
- To: hylafax-users@xxxxxxxxxxx
- Subject: [hylafax-users] hdlc errors
- From: Robert Haas <robert.haas@xxxxxxxxxxxxxx>
- Date: Tue, 03 May 2005 16:37:54 -0400
I am running Hylafax 4.2.1 on a RedHat 7.3 system with a modem that identifies itself as:
MODEM HAYES V.90 SERIAL S052099GV
The modem is connected to an analog card on a Mitel SX200 and receives calls via direct inward dial. We're using this only for purposes of receiving faxes, not sending them. Faxes from some senders come through with no problem at all, but other senders experience repeated failures. The two common error messages are:
Failed to properly detect high-speed data carrier. and T.30 T2 timeout, expected signal not received
In the first case, the following is typical:
May 03 20:08:40.45: [ 828]: SESSION BEGIN 000000323 18568341111
May 03 20:08:40.45: [ 828]: HylaFAX (tm) Version 4.2.1
May 03 20:08:40.45: [ 828]: <-- [4:ATA\r]
May 03 20:08:46.81: [ 828]: --> [7:CONNECT]
May 03 20:08:46.81: [ 828]: ANSWER: FAX CONNECTION DEVICE '/dev/ttyS0'
May 03 20:08:46.81: [ 828]: RECV FAX: begin
May 03 20:08:46.85: [ 828]: --> [7:CONNECT]
May 03 20:08:46.88: [ 828]: --> [7:CONNECT]
May 03 20:08:49.00: [ 828]: --> [2:OK]
May 03 20:08:49.00: [ 828]: <-- [9:AT+FRH=3\r]
May 03 20:08:52.10: [ 828]: --> [0:]
May 03 20:08:52.10: [ 828]: MODEM <Empty line>
May 03 20:08:52.11: [ 828]: --> [2:]
May 03 20:08:52.11: [ 828]: --> [2:OK]
May 03 20:08:52.11: [ 828]: DELAY 1500 ms
May 03 20:08:53.61: [ 828]: <-- [9:AT+FTH=3\r]
May 03 20:08:54.48: [ 828]: --> [7:CONNECT]
May 03 20:08:54.51: [ 828]: --> [7:CONNECT]
May 03 20:08:54.54: [ 828]: --> [7:CONNECT]
May 03 20:08:56.66: [ 828]: --> [2:OK]
May 03 20:08:56.66: [ 828]: <-- [9:AT+FRH=3\r]
May 03 20:08:56.86: [ 828]: --> [7:CONNECT]
May 03 20:08:58.17: [ 828]: --> [2:OK]
May 03 20:08:58.17: [ 828]: REMOTE wants 14400 bit/s
May 03 20:08:58.17: [ 828]: REMOTE wants A4 page width (215 mm)
May 03 20:08:58.17: [ 828]: REMOTE wants unlimited page length
May 03 20:08:58.17: [ 828]: REMOTE wants 3.85 line/mm
May 03 20:08:58.17: [ 828]: REMOTE wants 2-D MMR
May 03 20:08:58.17: [ 828]: REMOTE wants T.30 Annex A, 256-byte ECM
May 03 20:08:58.17: [ 828]: RECV training at v.17 14400 bit/s
May 03 20:08:58.17: [ 828]: <-- [11:AT+FRM=145\r]
May 03 20:08:59.93: [ 828]: --> [7:CONNECT]
May 03 20:09:01.42: [ 828]: RECV: TCF 2688 bytes, 0% non-zero, 2665 zero-run
May 03 20:09:01.43: [ 828]: --> [10:NO CARRIER]
May 03 20:09:01.43: [ 828]: DELAY 75 ms
May 03 20:09:01.51: [ 828]: TRAINING succeeded
May 03 20:09:01.51: [ 828]: <-- [9:AT+FTH=3\r]
May 03 20:09:02.38: [ 828]: --> [7:CONNECT]
May 03 20:09:02.70: [ 828]: --> [2:OK]
May 03 20:09:02.70: [ 828]: <-- [11:AT+FRM=146\r]
May 03 20:09:03.47: [ 828]: --> [7:CONNECT]
May 03 20:09:05.14: [ 828]: RECV received frame number 0
...after which things seem to go along OK for a while, and then eventually after a number of pages have been received...
May 03 20:11:34.30: [ 828]: <-- [9:AT+FTH=3\r]
May 03 20:11:35.17: [ 828]: --> [7:CONNECT]
May 03 20:11:35.17: [ 828]: RECV send MCF (message confirmation)
May 03 20:11:35.17: [ 828]: RECV FAX (000000323): from <UNSPECIFIED>, page 7 in 0:31, INF, 3.85 line/mm, 2-D MMR, 14400 bit/s
May 03 20:11:35.49: [ 828]: --> [2:OK]
May 03 20:11:35.49: [ 828]: <-- [11:AT+FRM=146\r]
May 03 20:11:36.29: [ 828]: --> [7:CONNECT]
May 03 20:11:37.95: [ 828]: RECV received frame number 0
May 03 20:11:38.09: [ 828]: RECV received frame number 1
May 03 20:11:38.24: [ 828]: RECV received frame number 2
May 03 20:11:38.39: [ 828]: RECV received frame number 3
May 03 20:11:38.53: [ 828]: RECV received frame number 4
May 03 20:11:38.67: [ 828]: RECV received frame number 5
May 03 20:11:38.81: [ 828]: RECV received frame number 6
May 03 20:11:39.03: [ 828]: RECV received frame number 7
May 03 20:11:39.03: [ 828]: RECV received RCP frame
May 03 20:11:39.14: [ 828]: --> [10:NO CARRIER]
May 03 20:11:39.14: [ 828]: <-- [9:AT+FRH=3\r]
May 03 20:11:39.18: [ 828]: --> [7:CONNECT]
May 03 20:11:40.42: [ 828]: --> [2:OK]
May 03 20:11:40.42: [ 828]: RECV recv PPS (partial page signal)
May 03 20:11:40.42: [ 828]: RECV recv MPS (more pages, same document)
May 03 20:11:40.42: [ 828]: RECV received 8 frames of block 1 of page 8
May 03 20:11:40.43: [ 828]: RECV: 1859 bytes of data, 1112 total lines
May 03 20:11:40.43: [ 828]: <-- [9:AT+FRS=7\r]
May 03 20:11:40.57: [ 828]: --> [2:OK]
May 03 20:11:40.57: [ 828]: <-- [9:AT+FTH=3\r]
May 03 20:11:41.44: [ 828]: --> [7:CONNECT]
May 03 20:11:41.44: [ 828]: RECV send MCF (message confirmation)
May 03 20:11:41.44: [ 828]: RECV FAX (000000323): from <UNSPECIFIED>, page 8 in 0:06, INF, 3.85 line/mm, 2-D MMR, 14400 bit/s
May 03 20:11:41.76: [ 828]: --> [2:OK]
May 03 20:11:41.76: [ 828]: <-- [11:AT+FRM=146\r]
May 03 20:11:48.87: [ 828]: --> [2:]
May 03 20:11:48.87: [ 828]: --> [2:OK]
May 03 20:11:48.87: [ 828]: <-- [9:AT+FRS=7\r]
May 03 20:11:49.42: [ 828]: --> [2:OK]
May 03 20:11:49.43: [ 828]: RECV FAX: Failed to properly detect high-speed data carrier.
May 03 20:11:49.43: [ 828]: <-- [9:AT+FTH=3\r]
May 03 20:11:49.43: [ 828]: RECV FAX (000000323): from <UNSPECIFIED>, page 9 in 0:08, INF, 3.85 line/mm, 2-D MMR, 14400 bit/s
May 03 20:11:49.43: [ 828]: RECV FAX (000000323): recvq/fax000000326.tif from <UNSPECIFIED>, route to <unspecified>, 9 pages in 3:03
May 03 20:11:50.29: [ 828]: --> [7:CONNECT]
May 03 20:11:50.61: [ 828]: --> [2:OK]
May 03 20:11:50.61: [ 828]: RECV FAX (000000323): session with <UNSPECIFIED> terminated abnormally: Failed to properly detect high-speed data carrier.
May 03 20:11:50.61: [ 828]: RECV FAX: bin/faxrcvd "recvq/fax000000326.tif" "ttyS0" "000000323" "Failed to properly detect high-speed data carrier." "" ""
May 03 20:11:50.61: [ 828]: RECV FAX: end
May 03 20:11:50.62: [ 828]: SESSION END
In the second case, where I get a T.30 T2 timeout, the fax transmission will often start normally and then suddenly it will stop receiving frames, and many or all of the frames will begin reporting "HDLC frame not byte-oriented" and/or "Bad HDLC terminating flag received". This is typical:
[...good stuff...]
May 03 18:40:16.11: [32206]: RECV received frame number 58
May 03 18:40:16.25: [32206]: RECV received frame number 59
May 03 18:40:16.46: [32206]: RECV received frame number 60
May 03 18:40:16.60: [32206]: RECV received frame number 61
May 03 18:40:16.74: [32206]: RECV received frame number 62
May 03 18:40:16.88: [32206]: RECV received frame number 63
May 03 18:40:17.02: [32206]: RECV received frame number 64
May 03 18:40:17.16: [32206]: RECV received frame number 65
May 03 18:40:17.23: [32206]: RECV received frame number 66
May 03 18:40:17.23: [32206]: RECV frame FCS check failed
May 03 18:40:17.30: [32206]: Bad HDLC terminating flag received.
May 03 18:40:17.45: [32206]: HDLC frame not byte-oriented. Trailing byte: 0xfc
May 03 18:40:17.45: [32206]: HDLC frame not byte-oriented. Trailing byte: 0xc0
May 03 18:40:17.45: [32206]: Bad HDLC terminating flag received.
May 03 18:40:17.52: [32206]: Bad HDLC terminating flag received.
May 03 18:40:17.60: [32206]: HDLC frame not byte-oriented. Trailing byte: 0xfc
May 03 18:40:17.60: [32206]: Bad HDLC terminating flag received.
May 03 18:40:17.60: [32206]: HDLC frame not byte-oriented. Trailing byte: 0xf8
May 03 18:40:17.60: [32206]: HDLC frame not byte-oriented. Trailing byte: 0x80
May 03 18:40:17.68: [32206]: Bad HDLC terminating flag received.
May 03 18:40:17.68: [32206]: HDLC frame not byte-oriented. Trailing byte: 0x80
May 03 18:40:17.68: [32206]: HDLC frame not byte-oriented. Trailing byte: 0xfc
May 03 18:40:17.68: [32206]: Bad HDLC terminating flag received.
May 03 18:40:17.82: [32206]: HDLC frame not byte-oriented. Trailing byte: 0x80
May 03 18:40:17.90: [32206]: Bad HDLC terminating flag received.
May 03 18:40:17.90: [32206]: Bad HDLC terminating flag received.
May 03 18:40:17.98: [32206]: Bad HDLC terminating flag received.
[...more crap...]
I guess what I'm wondering is - is this a problem with my phone line, my modem, my firmware, or Hylafax? Any recommendations on how to fix?
Thanks in advance,
...Robert
____________________ HylaFAX(tm) Users Mailing List _______________________ To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi On UNIX: mail -s unsubscribe hylafax-users-request@xxxxxxxxxxx < /dev/null *To learn about commercial HylaFAX(tm) support, mail sales@xxxxxxxxx*
- Follow-Ups:
- Re: [hylafax-users] hdlc errors
- From: Lee Howard
- Re: [hylafax-users] hdlc errors
- Prev by Date: [hylafax-users] Is there a mailing list or forum for Cypheus?
- Next by Date: [hylafax-users] notify
- Previous by thread: Re: [hylafax-users] Is there a mailing list or forum for Cypheus?
- Next by thread: Re: [hylafax-users] hdlc errors
- Index(es):
Project hosted by iFAX Solutions