[hylafax-users] Hylafax + T38modem + VOIP Gateway

To: hylafax-users@xxxxxxxxxxx
Subject: [hylafax-users] Hylafax + T38modem + VOIP Gateway
From: Kimble Young <kimble@xxxxxxxxxxxxxxx>
Date: Tue, 11 Jan 2005 21:07:20 +1100

Has anyone managed to get hylafax + T38modem + a gateway apart from cisco working?

The unit in question is a mediatrix 2402. T38modem negotiates properly but there are a large number of bad HDLC frames and other errors generated.

Ethereal dumps show that a large number of the hdlc-data packets are malformed and that the connection keeps training down in speed.

Faxes do generally make it through if they are short but each page can take up to 3 minutes instead of the usual 30-60 seconds.

I've tried going through their support channels but they aren't much help so I thought i'd ask if anyone has a t38 gateway apart from cisco working properly?

Apologies for asking on the hylafax list but I haven't been able to raise a response on the openh323/t38modem list.

t38modem is - 0.8.0 hylafax is either 4.2.0 or 4.1.8 (tried a few machines) t38modem is run with: t38modem -F -n --old-asn -p ttyx0,ttyx1 -P T.38-UDP --route all@xxxxxxxxxxxx -o trace.log -ttt

config.ttyx0,1

ModemType:              Class1          # use class 1 interface
ModemFlowControl:       rtscts          # default

ModemRevQueryCmd:       AT+FREV?
ModemResetCmds: "AT#CID=10"     # enable ANI/DNIS reporting
RingsBeforeAnswer:      2               # collect info between two RINGs
#QualifyCID:            etc/cid         # CID access control list file
CIDNumber:              "NMBR = "       # pattern string for calling number
CIDName:                "NDID = "       # pattern string for called number

Jan 04 17:46:06.81: [12066]: SESSION BEGIN 000000107 612944444444 Jan 04 17:46:06.81: [12066]: HylaFAX (tm) Version 4.2.0 Jan 04 17:46:06.81: [12066]: <-- [4:ATA\r] Jan 04 17:46:11.26: [12066]: --> [7:CONNECT] Jan 04 17:46:11.26: [12066]: ANSWER: FAX CONNECTION DEVICE '/dev/ttyx1' Jan 04 17:46:11.26: [12066]: RECV FAX: begin Jan 04 17:46:11.33: [12066]: <-- data [32] Jan 04 17:46:11.33: [12066]: <-- data [2] Jan 04 17:46:13.06: [12066]: --> [7:CONNECT] Jan 04 17:46:13.06: [12066]: <-- data [23] Jan 04 17:46:13.06: [12066]: <-- data [2] Jan 04 17:46:13.78: [12066]: --> [7:CONNECT] Jan 04 17:46:13.78: [12066]: <-- data [10] Jan 04 17:46:13.78: [12066]: <-- data [2] Jan 04 17:46:14.19: [12066]: --> [2:OK] Jan 04 17:46:14.19: [12066]: <-- [9:AT+FRH=3\r] Jan 04 17:46:14.96: [12066]: --> [7:CONNECT] Jan 04 17:46:16.08: [12066]: --> [2:OK] Jan 04 17:46:16.08: [12066]: REMOTE wants 9600 bit/s Jan 04 17:46:16.08: [12066]: REMOTE wants A4 page width (215 mm) Jan 04 17:46:16.08: [12066]: REMOTE wants unlimited page length Jan 04 17:46:16.08: [12066]: REMOTE wants 3.85 line/mm Jan 04 17:46:16.08: [12066]: REMOTE wants 1-D MH Jan 04 17:46:16.08: [12066]: REMOTE wants T.30 Annex A, 256-byte ECM Jan 04 17:46:16.08: [12066]: RECV training at v.29 9600 bit/s Jan 04 17:46:16.08: [12066]: <-- [10:AT+FRM=96\r] Jan 04 17:46:16.27: [12066]: --> [7:CONNECT] Jan 04 17:46:18.05: [12066]: RECV: TCF 1907 bytes, 0% non-zero, 1907 zero-run Jan 04 17:46:18.05: [12066]: --> [10:NO CARRIER] Jan 04 17:46:18.05: [12066]: DELAY 75 ms Jan 04 17:46:18.13: [12066]: TRAINING succeeded Jan 04 17:46:18.13: [12066]: <-- [9:AT+FTH=3\r] Jan 04 17:46:18.13: [12066]: --> [7:CONNECT] Jan 04 17:46:18.13: [12066]: <-- data [3] Jan 04 17:46:18.13: [12066]: <-- data [2] Jan 04 17:46:19.21: [12066]: --> [2:OK] Jan 04 17:46:19.21: [12066]: <-- [10:AT+FRM=96\r] Jan 04 17:46:20.72: [12066]: --> [7:CONNECT] Jan 04 17:46:21.58: [12066]: RECV received frame number 0 Jan 04 17:46:21.84: [12066]: RECV received frame number 1 Jan 04 17:46:22.10: [12066]: RECV received frame number 2 Jan 04 17:46:22.36: [12066]: RECV received frame number 3 Jan 04 17:46:22.50: [12066]: RECV received frame number 4 Jan 04 17:46:22.77: [12066]: RECV received frame number 5 Jan 04 17:46:23.04: [12066]: RECV received frame number 6 Jan 04 17:46:23.18: [12066]: RECV received frame number 7 Jan 04 17:46:23.44: [12066]: RECV received frame number 8 Jan 04 17:46:23.70: [12066]: RECV received frame number 9 Jan 04 17:46:23.81: [12066]: RECV received frame number 10 Jan 04 17:46:23.81: [12066]: RECV frame FCS check failed Jan 04 17:46:23.81: [12066]: HDLC frame with bad address field 0xa3 Jan 04 17:46:24.06: [12066]: HDLC frame with bad address field 0x94 Jan 04 17:46:24.06: [12066]: HDLC frame with bad address field 0xa4 Jan 04 17:46:24.06: [12066]: HDLC frame with bad address field 0xc2 Jan 04 17:46:24.07: [12066]: HDLC frame too short (3 bytes) Jan 04 17:46:24.39: [12066]: HDLC frame with bad address field 0xef Jan 04 17:46:24.39: [12066]: HDLC frame with bad address field 0x91 Jan 04 17:46:24.63: [12066]: HDLC frame with bad address field 0x8e Jan 04 17:46:24.74: [12066]: HDLC frame with bad address field 0xa6 Jan 04 17:46:24.87: [12066]: HDLC frame with bad address field 0xc8 Jan 04 17:46:24.87: [12066]: HDLC frame too short (4 bytes) Jan 04 17:46:24.87: [12066]: HDLC frame too short (3 bytes) Jan 04 17:46:24.87: [12066]: HDLC frame with bad address field 0xcb Jan 04 17:46:24.88: [12066]: HDLC frame with bad address field 0xc2 Jan 04 17:46:24.88: [12066]: HDLC frame with bad address field 0x8e Jan 04 17:46:24.88: [12066]: HDLC frame with bad address field 0xa5 ..... similar messages repeated many times ...... Jan 04 17:46:56.65: [12066]: RECV assumed RCP frame with block end Jan 04 17:46:56.65: [12066]: --> [10:NO CARRIER] Jan 04 17:46:56.65: [12066]: <-- [9:AT+FRH=3\r] Jan 04 17:46:56.74: [12066]: --> [7:CONNECT] Jan 04 17:46:57.85: [12066]: --> [2:OK] Jan 04 17:46:57.85: [12066]: RECV recv PPS (partial page signal) Jan 04 17:46:57.85: [12066]: RECV recv MPS (more pages, same document) Jan 04 17:46:57.85: [12066]: RECV received 156 frames of block 1 of page 1 Jan 04 17:46:57.85: [12066]: <-- [9:AT+FRS=7\r] Jan 04 17:46:57.93: [12066]: --> [2:OK] Jan 04 17:46:57.93: [12066]: <-- [9:AT+FTH=3\r] Jan 04 17:46:57.93: [12066]: --> [7:CONNECT] Jan 04 17:46:57.93: [12066]: <-- data [35] Jan 04 17:46:57.93: [12066]: <-- data [2] Jan 04 17:47:00.91: [12066]: --> [2:OK] Jan 04 17:47:00.91: [12066]: RECV send PPR (partial page request) Jan 04 17:47:00.91: [12066]: <-- [10:AT+FRM=96\r] Jan 04 17:47:02.14: [12066]: --> [7:CONNECT] Jan 04 17:47:02.80: [12066]: RECV received frame number 10 .... similar to above .... Jan 04 17:47:59.36: [12066]: RECV keeping unconfirmed page Jan 04 17:47:59.86: [12066]: RECV: 39936 bytes of data, 606 total lines Jan 04 17:47:59.86: [12066]: RECV FAX (000000107): from <UNSPECIFIED>, page 1 in 1:41, INF, 3.85 line/mm, 1-D MH, 9600 bit/s Jan 04 17:47:59.87: [12066]: RECV FAX (000000107): recvq/fax000000060.tif from < UNSPECIFIED>, route to <unspecified>, 1 pages in 1:48 Jan 04 17:47:59.89: [12066]: RECV FAX: T.30 T2 timeout, expected signal not rece ived Jan 04 17:47:59.89: [12066]: <-- [9:AT+FTH=3\r] Jan 04 17:47:59.90: [12066]: --> [7:CONNECT] Jan 04 17:47:59.90: [12066]: <-- data [3] Jan 04 17:47:59.90: [12066]: <-- data [2] Jan 04 17:48:00.92: [12066]: --> [5:ERROR] Jan 04 17:48:00.92: [12066]: MODEM Command error Jan 04 17:48:00.92: [12066]: RECV FAX (000000107): session with <UNSPECIFIED> te rminated abnormally: T.30 T2 timeout, expected signal not received Jan 04 17:48:00.92: [12066]: RECV FAX: bin/faxrcvd "recvq/fax000000060.tif" "tty x1" "000000107" "T.30 T2 timeout, expected signal not received" "" "439934943" Jan 04 17:48:00.93: [12066]: RECV FAX: end Jan 04 17:48:00.93: [12066]: SESSION END

____________________ 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] Hylafax + T38modem + VOIP Gateway
  - From: Alexandre Aractingi

Prev by Date: Re: [hylafax-users] **ANNOUNCE** hylafax-4.2.1beta1 released
Next by Date: Re: [hylafax-users] Hylafax + T38modem + VOIP Gateway
Previous by thread: Re: [hylafax-users] faxgetty flailing and failing.
Next by thread: Re: [hylafax-users] Hylafax + T38modem + VOIP Gateway
Index(es):
- Main
- Thread

Report any problems to webmaster@hylafax.org

HylaFAX is a trademark of Silicon Graphics Corporation.
Internet connectivity for hylafax.org is provided by:
VirtuALL Private Host Services