 HylaFAX The world's
most advanced open source fax server
|
[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index] [Thread Index]
Re: [hylafax-users] Failed to properly d
- To: <bill.allison@xxxxxxxxx>, <andrew.rinaldi@xxxxxxxxxxxx>, <hylafax-users@xxxxxxxxxxx>
- Subject: Re: [hylafax-users] Failed to properly d
- From: "SCIN - Danilo Bottino" <info@xxxxxxx>
- Date: Mon, 17 Jul 2006 17:04:45 +0200
Hey some good news.
The mainboard is equipped with only one serial port connected to a UPS, so I connected a Prolific PL2303 usb-to-serial adapter to the Agere (actually /dev/modem is a symbolic link to /dev/ttyUSB0).
I connected the modem to COM1 and it works just fine, no more 'Bad HDLC terminating flag received'.. I guess I need a mainboard with two _real_ serial ports.
----- Original Message ----- From: <bill.allison@xxxxxxxxx>
To: <andrew.rinaldi@xxxxxxxxxxxx>; <info@xxxxxxx>; <hylafax-users@xxxxxxxxxxx>
Sent: Monday, July 17, 2006 4:07 PM
Subject: Re: [hylafax-users] Failed to properly d
I use them very successfully but would also recommend don't buy but if you happen to already have one by all means give it a go. Be aware that you *must* apply latest firmware upgrades to avoid problems.
Regards Bill A
-----Original Message----- From: andrew.rinaldi@xxxxxxxxxxxx Sent: 17 July 2006 13:29 To: info@xxxxxxx; hylafax-users@xxxxxxxxxxx Subject: Re: [hylafax-users] Failed to properly d
-------------------------------------------------------------------------- -- Hi Danilo,
I think that most users and developers would recommend that you avoid USR products with HylaFAX.
Regards
ANDREW RINALDI Mainpine Ltd. Support USA +1 718 701 2422 | Asia/Europe +44 1225 436137 andrew.rinaldi@xxxxxxxxxxxx | www.mainpine.com
-----Original Message----- From: SCIN - Danilo Bottino [mailto:info@xxxxxxx] Sent: 17 July 2006 13:23 To: andrew.rinaldi@xxxxxxxxxxxx; hylafax-users@xxxxxxxxxxx Subject: Re: [hylafax-users] Failed to properly detect high-speed data carrier
Hi Andrew,
thanks for your quick reply. About point 1 I'll sure give it a try.. this is my very first setup of a faxserver on linux and I lack experience. About point 2, I guess it would be easier to buy a brand new modem.. I wonder if a us robotics would work as intendend.
----- Original Message ----- From: "andrew rinaldi" <andrew.rinaldi@xxxxxxxxxxxx> To: "'SCIN - Danilo Bottino'" <info@xxxxxxx>; <hylafax-users@xxxxxxxxxxx> Sent: Monday, July 17, 2006 2:08 PM Subject: Re: [hylafax-users] Failed to properly detect high-speed data carrier
Hi Danilo,8345]:
We have seen a lot of problems with the 'stock' Agere OCM (and OCF) firmware. Here are my suggestions for you to try;
(1) Upgrade to 4.3.0
(2) Ask for a modem firmware upgrade (Note: by default the OCM/OCF chipsets do not require external flash memory and a full firmware upgrade is therefore impossible... however, if you are VERY lucky the board will have a flash chip fitted).
Regards
ANDREW RINALDI Mainpine Ltd. Support USA +1 718 701 2422 | Asia/Europe +44 1225 436137 andrew.rinaldi@xxxxxxxxxxxx | www.mainpine.com
-----Original Message----- From: hylafax-users-bounce@xxxxxxxxxxx [mailto:hylafax-users-bounce@xxxxxxxxxxx] On Behalf Of SCIN - Danilo Bottino Sent: 17 July 2006 12:56 To: hylafax-users@xxxxxxxxxxx Subject: [hylafax-users] Failed to properly detect high-speed data carrier
Hi all,
I did a search but I can't find a solution to this problem. I run hylafax 4.2.1 on a Debian Sarge box with an external Agere 56k modem. Sometimes I receive the infamous 'high-speed data carrier' error, is there anything I can do?
The modem is:
MODEM AGERE OCM V.92 VER2.7A (JUN 14 2004) VOICE MERCURY DP2SH MODE-II SERIAL Agere OCM V.92 Ver2.7a
And here's the session log:
Jul 17 12:40:56.84: [ 8345]: SESSION BEGIN 000000164 3842448 Jul 17 12:40:56.84: [ 8345]: HylaFAX (tm) Version 4.2.1 Jul 17 12:40:56.84: [ 8345]: <-- [4:ATA\r] Jul 17 12:41:05.63: [ 8345]: --> [7:CONNECT] Jul 17 12:41:05.63: [ 8345]: ANSWER: FAX CONNECTION DEVICE '/dev/modem' Jul 17 12:41:05.63: [ 8345]: RECV FAX: begin Jul 17 12:41:05.65: [8345]:--> [7:CONNECT] Jul 17 12:41:05.68: [ 8345]: --> [7:CONNECT] Jul 17 12:41:07.81: [ 8345]: --> [2:OK] Jul 17 12:41:07.81: [ 8345]: <-- [9:AT+FRH=3\r] Jul 17 12:41:07.99: [ 8345]: --> [7:CONNECT] Jul 17 12:41:09.73: [ 8345]: --> [2:OK] Jul 17 12:41:09.73: [ 8345]: REMOTE TSI "CARREFOUR" Jul 17 12:41:09.73: [ 8345]: <-- [9:AT+FRH=3\r] Jul 17 12:41:09.74: [ 8345]: --> [7:CONNECT] Jul 17 12:41:10.03: [ 8345]: --> [2:OK] Jul 17 12:41:10.03: [ 8345]: REMOTE wants 14400 bit/s Jul 17 12:41:10.03: [ 8345]: REMOTE wants A4 page width (215 mm) Jul 17 12:41:10.03: [ 8345]: REMOTE wants unlimited page length Jul 17 12:41:10.03: [ 8345]: REMOTE wants 7.7 line/mm Jul 17 12:41:10.03: [ 8345]: REMOTE wants 1-D MH Jul 17 12:41:10.03: [ 8345]: REMOTE wants T.30 Annex A, 256-byte ECM Jul 17 12:41:10.03: [ 8345]: RECV training at v.17 14400 bit/s Jul 17 12:41:10.03: [ 8345]: <-- [11:AT+FRM=145\r] Jul 17 12:41:11.81: [ 8345]: --> [7:CONNECT] Jul 17 12:41:13.32: [ 8345]: RECV: TCF 2720 bytes, 0% non-zero, 2699 zero-run Jul 17 12:41:13.33: [ 8345]: --> [10:NO CARRIER] Jul 17 12:41:13.33: [...DELAY 75 ms Jul 17 12:41:13.41: [ 8345]: TRAINING succeeded Jul 17 12:41:13.41: [ 8345]: <-- [9:AT+FTH=3\r] Jul 17 12:41:14.27: [ 8345]: --> [7:CONNECT] Jul 17 12:41:14.59: [ 8345]: --> [2:OK] Jul 17 12:41:14.59: [ 8345]: <-- [11:AT+FRM=146\r] Jul 17 12:41:15.68: [ 8345]: --> [7:CONNECT] Jul 17 12:41:16.03: [ 8345]: RECV received frame number 0byte:[cut] ... Jul 17 12:41:45.24: [ 8345]: RECV received frame number 195 Jul 17 12:41:45.31: [ 8345]: Bad HDLC terminating flag received. Jul 17 12:41:45.45: [ 8345]: Bad HDLC terminating flag received. Jul 17 12:41:45.45: [ 8345]: Bad HDLC terminating flag received. Jul 17 12:41:45.52: [ 8345]: Bad HDLC terminating flag received. Jul 17 12:41:45.59: [ 8345]: Bad HDLC terminating flag received. Jul 17 12:41:45.59: [ 8345]: Bad HDLC terminating flag received. Jul 17 12:41:45.59: [ 8345]: Bad HDLC terminating flag received. Jul 17 12:41:45.59: [ 8345]: Bad HDLC terminating flag received. Jul 17 12:41:45.66: [ 8345]: Bad HDLC terminating flag received. Jul 17 12:41:45.66: [ 8345]: Bad HDLC terminating flag received. Jul 17 12:41:45.66: [ 8345]: HDLC frame too short (4 bytes) Jul 17 12:41:45.80: [ 8345]: HDLC frame not byte-oriented. Trailing byte: 0xe0 Jul 17 12:41:45.87: [ 8345]: HDLC frame not byte-oriented. Trailingbyte:0xf8 Jul 17 12:41:45.94: [ 8345]: Bad HDLC terminating flag received. Jul 17 12:41:46.01: [ 8345]: Bad HDLC terminating flag received. Jul 17 12:41:46.08: [ 8345]: Bad HDLC terminating flag received. Jul 17 12:41:46.08: [ 8345]: HDLC frame not byte-oriented. Trailingbyte:0xe0 Jul 17 12:41:46.08: [ 8345]: HDLC frame not byte-oriented. Trailingbyte:0xf8 Jul 17 12:41:46.15: [ 8345]: HDLC frame not byte-oriented. Trailingbyte:0xf0 Jul 17 12:41:46.22: [ 8345]: HDLC frame not byte-oriented. Trailingbyte:0xf0 Jul 17 12:41:46.29: [ 8345]: Bad HDLC terminating flag received. Jul 17 12:41:46.29: [ 8345]: HDLC frame not byte-oriented. Trailingbyte:0xfc Jul 17 12:41:46.30: [ 8345]: HDLC frame not byte-oriented. Trailingbyte:0x80 Jul 17 12:41:46.37: [ 8345]: HDLC frame not byte-oriented. Trailingbyte:0xc0 Jul 17 12:41:46.44: [ 8345]: HDLC frame with bad address field 0xc2 Jul 17 12:41:46.44: [ 8345]: Bad HDLC terminating flag received. Jul 17 12:41:46.58: [ 8345]: HDLC frame not byte-oriented. Trailingbyte:0xf0 Jul 17 12:41:46.65: [ 8345]: Bad HDLC terminating flag received. Jul 17 12:41:46.72: [ 8345]: HDLC frame not byte-oriented. Trailingbyte:0xc0 Jul 17 12:41:46.79: [ 8345]: Bad HDLC terminating flag received. Jul 17 12:41:46.79: [ 8345]: Bad HDLC terminating flag received. Jul 17 12:41:46.79: [ 8345]: HDLC frame not byte-oriented. Trailingbyte:0xf0 Jul 17 12:41:46.79: [ 8345]: HDLC frame not byte-oriented. Trailingbyte:0xf8 Jul 17 12:41:46.93: [ 8345]: HDLC frame not byte-oriented. Trailingbyte:0xfc Jul 17 12:41:46.93: [ 8345]: HDLC frame not byte-oriented. Trailingbyte:0xc0 Jul 17 12:41:47.00: [ 8345]: HDLC frame not byte-oriented. Trailing
byte:0 Jul 17 12:41:47.00: [ 8345]: HDLC frame not byte-oriented. Trailingbyte:0xc0 Jul 17 12:41:47.07: [ 8345]: HDLC frame not byte-oriented. Trailing
byte:0 Jul 17 12:41:47.14: [ 8345]: Bad HDLC terminating flag received. Jul 17 12:41:47.21: [ 8345]: Bad HDLC terminating flag received. Jul 17 12:41:47.21: [ 8345]: Bad HDLC terminating flag received. Jul 17 12:41:47.28: [ 8345]: Bad HDLC terminating flag received. Jul 17 12:41:47.36: [ 8345]: HDLC frame not byte-oriented. Trailing
byte:0 Jul 17 12:41:47.43: [ 8345]: HDLC frame with bad address field 0xb7 Jul 17 12:41:47.43: [ 8345]: Bad HDLC terminating flag received. Jul 17 12:41:47.64: [ 8345]: Bad HDLC terminating flag received. Jul 17 12:41:47.71: [ 8345]: HDLC frame not byte-oriented. Trailing
byte:0 Jul 17 12:41:47.78: [ 8345]: HDLC frame not byte-oriented. Trailing
byte:0 Jul 17 12:41:47.78: [ 8345]: HDLC frame not byte-oriented. Trailing
byte:0 Jul 17 12:41:47.78: [ 8345]: HDLC frame with bad address field 0x84 Jul 17 12:41:47.85: [ 8345]: Bad HDLC terminating flag received. Jul 17 12:41:47.85: [ 8345]: HDLC frame not byte-oriented. Trailing
byte:0 Jul 17 12:41:47.99: [ 8345]: Bad HDLC terminating flag received. Jul 17 12:41:48.06: [ 8345]: Bad HDLC terminating flag received. Jul 17 12:41:48.13: [ 8345]: Bad HDLC terminating flag received. Jul 17 12:41:48.13: [ 8345]: Bad HDLC terminating flag received. Jul 17 12:41:48.13: [ 8345]: HDLC frame not byte-oriented. Trailingbyte:0x80 Jul 17 12:41:48.27: [ 8345]: HDLC frame not byte-oriented. Trailingbyte:0x80 Jul 17 12:41:48.27: [ 8345]: Bad HDLC terminating flag received. Jul 17 12:41:48.34: [ 8345]: HDLC frame with bad address field 0x8e Jul 17 12:41:48.41: [ 8345]: Bad HDLC terminating flag received. Jul 17 12:41:48.42: [ 8345]: Bad HDLC terminating flag received. Jul 17 12:41:48.42: [ 8345]: HDLC frame not byte-oriented. Trailingbyte:0xfc Jul 17 12:41:48.48: [ 8345]: HDLC frame not byte-oriented. Trailingbyte:0xfc Jul 17 12:41:48.56: [ 8345]: Bad HDLC terminating flag received. Jul 17 12:41:48.63: [ 8345]: HDLC frame not byte-oriented. Trailingbyte:0xe0 Jul 17 12:41:48.70: [ 8345]: HDLC frame not byte-oriented. Trailingbyte:0xe0 Jul 17 12:41:48.77: [ 8345]: Bad HDLC terminating flag received. Jul 17 12:41:48.84: [ 8345]: HDLC frame not byte-oriented. Trailing
byte:0 Jul 17 12:41:48.84: [ 8345]: HDLC frame not byte-oriented. Trailingbyte:0xfc Jul 17 12:41:48.91: [ 8345]: HDLC frame not byte-oriented. Trailingbyte:0xfc Jul 17 12:41:48.91: [ 8345]: HDLC frame not byte-oriented. Trailingbyte:0xc0 Jul 17 12:41:48.98: [ 8345]: HDLC frame not byte-oriented. Trailingbyte:0xf8 Jul 17 12:41:49.05: [ 8345]: HDLC frame not byte-oriented. Trailingbyte:0xc0 Jul 17 12:41:49.12: [ 8345]: HDLC frame not byte-oriented. Trailingbyte:0xf0 Jul 17 12:41:49.12: [ 8345]: HDLC frame not byte-oriented. Trailingbyte:0xc0 Jul 17 12:41:49.19: [ 8345]: HDLC frame not byte-oriented. Trailingbyte:0xc0 Jul 17 12:41:49.26: [ 8345]: Bad HDLC terminating flag received. Jul 17 12:41:49.33: [ 8345]: Bad HDLC terminating flag received. Jul 17 12:41:49.40: [ 8345]: HDLC frame with bad address field 0x9d Jul 17 12:41:49.47: [ 8345]: HDLC frame not byte-oriented. Trailing byte: 0 Jul 17 12:41:49.47: [ 8345]: HDLC frame not byte-oriented. Trailing byte: 0x80 Jul 17 12:41:49.54: [ 8345]: Bad HDLC terminating flag received. Jul 17 12:41:49.55: [ 8345]: Bad HDLC terminating flag received. Jul 17 12:41:49.61: [ 8345]: Bad HDLC terminating flag received. Jul 17 12:41:49.61: [ 8345]: HDLC frame not byte-oriented. Trailing12:41:53.90:0xc0 Jul 17 12:41:49.62: [ 8345]: Bad HDLC terminating flag received. Jul 17 12:41:49.62: [ 8345]: RECV assumed RCP frame with block end Jul 17 12:41:49.72: [ 8345]: --> [10:NO CARRIER] Jul 17 12:41:49.72: [ 8345]: <-- [9:AT+FRH=3\r] Jul 17 12:41:50.02: [ 8345]: --> [7:CONNECT] Jul 17 12:41:50.87: [ 8345]: --> [10:NO CARRIER] Jul 17 12:41:50.87: [ 8345]: MODEM No carrier Jul 17 12:41:50.87: [ 8345]: <-- [9:AT+FRH=3\r] Jul 17 12:41:51.16: [ 8345]: --> [7:CONNECT] Jul 17 12:41:52.80: [ 8345]: --> [2:OK] Jul 17 12:41:52.80: [ 8345]: RECV recv PPS (partial page signal) Jul 17 12:41:52.80: [ 8345]: RECV recv MPS (more pages, same document) Jul 17 12:41:52.80: [ 8345]: RECV received 238 frames of block 1 of page 1 Jul 17 12:41:52.80: [ 8345]: <-- [9:AT+FRS=7\r] Jul 17 12:41:53.04: [ 8345]: --> [2:OK] Jul 17 12:41:53.04: [ 8345]: <-- [9:AT+FTH=3\r] Jul 178345]:[ 8345]: --> [7:CONNECT] Jul 17 12:41:55.14: [ 8345]: --> [2:OK] Jul 17 12:41:55.14: [ 8345]: RECV send PPR (partial page request) Jul 17 12:41:55.14: [ 8345]: <-- [11:AT+FRM=146\r] Jul 17 12:41:55.92: [ 8345]: --> [8:+FCERROR] Jul 17 12:41:55.92: [ 8345]: <-- [11:AT+FRM=146\r] Jul 17 12:42:02.62: [ 8345]: --> [8:+FCERROR] Jul 17 12:42:02.62: [ 8345]: <-- [11:AT+FRM=146\r] Jul 17 12:42:03.40: [ 8345]: --> [8:+FCERROR] Jul 17 12:42:03.40: [ 8345]: <-- [11:AT+FRM=146\r] Jul 17 12:42:07.07: [ 8345]: --> [8:+FCERROR] Jul 17 12:42:07.07: [ 8345]: <-- [11:AT+FRM=146\r] Jul 17 12:42:07.85: [ 8345]: --> [8:+FCERROR] Jul 17 12:42:07.85: [ 8345]: <-- [11:AT+FRM=146\r] Jul 17 12:42:11.45: [ 8345]: --> [8:+FCERROR] Jul 17 12:42:11.45: [ 8345]: <-- [11:AT+FRM=146\r] Jul 17 12:42:12.23: [ 8345]: --> [8:+FCERROR] Jul 17 12:42:12.23: [ 8345]: <-- [11:AT+FRM=146\r] Jul 17 12:42:15.83: [ 8345]: --> [8:+FCERROR] Jul 17 12:42:15.83: [ 8345]: <-- [11:AT+FRM=146\r] Jul 17 12:42:16.61: [ 8345]: --> [8:+FCERROR] Jul 17 12:42:16.61: [ 8345]: <-- [11:AT+FRM=146\r] Jul 17 12:42:23.61: [12:42:24.09:RECV keeping unconfirmed page Jul 17 12:42:23.75: [ 8345]: RECV: 60928 bytes of data, 1981 total lines Jul 17 12:42:23.86: [ 8345]: --> [2:] Jul 17 12:42:23.86: [ 8345]: --> [2:OK] Jul 17 12:42:23.86: [ 8345]: <-- [9:AT+FRS=7\r] Jul 17 12:42:24.08: [ 8345]: --> [2:OK] Jul 17carrier."[ 8345]: RECV FAX (000000164): from CARREFOUR, page 1 in 1:11, INF, 7.7 line/mm, 1-D MH, 14400 bit/s Jul 17 12:42:24.09: [ 8345]: RECV FAX (000000164): recvq/fax000000089.tif from CARREFOUR, route to <unspecified>, 1 pages in 1:19 Jul 17 12:42:24.09: [ 8345]: RECV FAX: Failed to properly detect high-speed data carrier. Jul 17 12:42:24.09: [ 8345]: <-- [9:AT+FTH=3\r] Jul 17 12:42:24.95: [ 8345]: --> [7:CONNECT] Jul 17 12:42:25.27: [ 8345]: --> [2:OK] Jul 17 12:42:25.27: [ 8345]: RECV FAX (000000164): session with CARREFOUR terminated abnormally: Failed to properly detect high-speed data carrier. Jul 17 12:42:25.27: [ 8345]: RECV FAX: bin/faxrcvd "recvq/fax000000089.tif" "modem" "000000164" "Failed to properly detect high-speed data"" "" Jul 17 12:42:25.28: [ 8345]: RECV FAX: end Jul 17 12:42:25.28: [ 8345]: SESSION END
Any help would be greatly appreciated.
_________________________________ Danilo Bottino - SCIN Servizi Informatici Tel. 011/9242690 Cel. 333/2290918 Fax 011/9242922 info@xxxxxxx - www.scin.it
____________________ 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*
____________________ 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*
____________________ 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*
____________________ 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*
____________________ 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*
- References:
- Re: [hylafax-users] Failed to properly d
- From: bill . allison
- Re: [hylafax-users] Failed to properly d
- Prev by Date: Re: [hylafax-users] Hylafax terminates while receiving
- Next by Date: Re: [hylafax-users] Which Distro offers a working Email-to-fax and fax-to-Email gateway ?
- Previous by thread: Re: [hylafax-users] Failed to properly d
- Next by thread: [hylafax-users]
- Index(es):
Project hosted by iFAX Solutions