Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

[hylafax-users] "TRAINING failed" problem with "MODEM AGERE OCM V.92 VER2.7A"

294 views
Skip to first unread message

Momonth

unread,
Apr 1, 2011, 5:14:28 AM4/1/11
to hylafa...@hylafax.org
Hello,

I'm trying to setup a remote external fax modem connected to the host
running "CentOS release 5.5 (Final)" via serial port:

ati3
Agere OCM V.92 Ver2.7a (Jun 14 2004) Voice Mercury DP2SH mode-ii SERIAL

I'm testing outgoing calls via minicom and it works, but hylafax can't
send faxes = ( I'm using hylafax-5.2.7-1

Here is the log file of the connection:

Apr 01 10:26:02.56: [13383]: SESSION BEGIN 000000048 001531XXXXXXXXX
Apr 01 10:26:02.56: [13383]: HylaFAX (tm) Version 5.2.7
Apr 01 10:26:02.56: [13383]: SEND FAX: JOB 21 DEST 001531XXXXXXXXX
COMMID 000000048 DEVICE '/dev/ttyS0' FROM 'root
<ro...@sao1-fax-001.booking.pcln.com>' USER root
Apr 01 10:26:02.56: [13383]: STATE CHANGE: RUNNING -> SENDING
Apr 01 10:26:02.56: [13383]: <-- [12:AT+FCLASS=1\r]
Apr 01 10:26:02.58: [13383]: --> [2:OK]
Apr 01 10:26:02.69: [13383]: DIAL 001531XXXXXXXXX
Apr 01 10:26:02.69: [13383]: <-- [22:ATDT0W001531XXXXXXXXX\r]
Apr 01 10:26:30.54: [13383]: --> [7:CONNECT]
Apr 01 10:26:33.24: [13383]: --> HDLC<19:FF C0 04 DB 00 00 00 00 00 00
00 00 00 00 00 00 00 A4 B7>
Apr 01 10:26:33.24: [13383]: --> [2:OK]
Apr 01 10:26:33.24: [13383]: REMOTE NSF "DB 00 00 00 00 00 00 00 00 00
00 00 00 00"
Apr 01 10:26:33.24: [13383]: NSF remote fax equipment: unknown
Apr 01 10:26:33.24: [13383]: <-- [9:AT+FRH=3\r]
Apr 01 10:26:33.26: [13383]: --> [7:CONNECT]
Apr 01 10:26:33.98: [13383]: --> HDLC<25:FF C0 02 9C 6C 8C CC AC 8C EC
0C 4C 8C CC D4 04 04 04 04 04 04 04 04 9F CA>
Apr 01 10:26:33.98: [13383]: --> [2:OK]
Apr 01 10:26:33.98: [13383]: REMOTE CSI "+31XXXXXXXXX"
Apr 01 10:26:33.98: [13383]: <-- [9:AT+FRH=3\r]
Apr 01 10:26:33.99: [13383]: --> [7:CONNECT]
Apr 01 10:26:34.41: [13383]: --> HDLC<15:FF C8 01 00 72 19 23 01 91 01
01 01 04 32 32>
Apr 01 10:26:34.41: [13383]: --> [2:OK]
Apr 01 10:26:34.41: [13383]: REMOTE best rate 9600 bit/s
Apr 01 10:26:34.41: [13383]: REMOTE max A4 page width (215 mm)
Apr 01 10:26:34.41: [13383]: REMOTE max unlimited page length
Apr 01 10:26:34.41: [13383]: REMOTE best vres 200 x 400 dpi
Apr 01 10:26:34.41: [13383]: REMOTE format support: MH, MMR, JBIG
Apr 01 10:26:34.41: [13383]: REMOTE supports T.30 Annex A, 256-byte ECM
Apr 01 10:26:34.41: [13383]: REMOTE best 5 ms/scanline
Apr 01 10:26:34.41: [13383]: USE 9600 bit/s
Apr 01 10:26:34.41: [13383]: USE error correction mode
Apr 01 10:26:34.41: [13383]: SEND file "docq/doc21.ps;00"
Apr 01 10:26:34.41: [13383]: USE A4 page width (215 mm)
Apr 01 10:26:34.41: [13383]: USE unlimited page length
Apr 01 10:26:34.41: [13383]: USE 3.85 line/mm
Apr 01 10:26:34.41: [13383]: USE 2-D MMR
Apr 01 10:26:34.41: [13383]: USE 0 ms/scanline
Apr 01 10:26:34.41: [13383]: SEND training at v.29 9600 bit/s
Apr 01 10:26:34.41: [13383]: <-- [9:AT+FRS=7\r]
Apr 01 10:26:34.53: [13383]: --> [2:OK]
Apr 01 10:26:34.53: [13383]: <-- [9:AT+FTH=3\r]
Apr 01 10:26:35.39: [13383]: --> [7:CONNECT]
Apr 01 10:26:35.39: [13383]: <-- HDLC<23:FF C0 C2 B2 F2 C2 74 E2 72 92
D2 F2 F2 42 04 04 04 04 04 04 04 04 04>
Apr 01 10:26:35.39: [13383]: <-- data [23]
Apr 01 10:26:35.39: [13383]: <-- data [2]
Apr 01 10:26:35.42: [13383]: --> [7:CONNECT]
Apr 01 10:26:35.42: [13383]: <-- HDLC<7:FF C8 C1 00 60 1F 22>
Apr 01 10:26:35.42: [13383]: <-- data [7]
Apr 01 10:26:35.42: [13383]: <-- data [2]
Apr 01 10:26:36.55: [13383]: --> [2:OK]
Apr 01 10:26:36.55: [13383]: <-- [9:AT+FTS=7\r]
Apr 01 10:26:36.62: [13383]: --> [2:OK]
Apr 01 10:26:36.62: [13383]: <-- [10:AT+FTM=96\r]
Apr 01 10:26:36.63: [13383]: --> [7:CONNECT]
Apr 01 10:26:36.63: [13383]: DELAY 400 ms
Apr 01 10:26:37.03: [13383]: <-- data [1024]
Apr 01 10:26:37.03: [13383]: <-- data [776]
Apr 01 10:26:37.03: [13383]: <-- data [2]
Apr 01 10:26:38.57: [13383]: --> [2:OK]
Apr 01 10:26:38.57: [13383]: <-- [9:AT+FRH=3\r]
Apr 01 10:26:39.83: [13383]: --> [7:CONNECT]
Apr 01 10:26:42.29: [13383]: --> HDLC<5:FF C8 22 67 DD>
Apr 01 10:26:42.29: [13383]: --> [2:OK]
Apr 01 10:26:42.29: [13383]: SEND training at v.29 7200 bit/s
Apr 01 10:26:42.29: [13383]: <-- [9:AT+FRS=7\r]
Apr 01 10:26:42.43: [13383]: --> [2:OK]
Apr 01 10:26:42.43: [13383]: <-- [9:AT+FTH=3\r]
Apr 01 10:26:43.29: [13383]: --> [7:CONNECT]
Apr 01 10:26:43.29: [13383]: <-- HDLC<23:FF C0 C2 B2 F2 C2 74 E2 72 92
D2 F2 F2 42 04 04 04 04 04 04 04 04 04>
Apr 01 10:26:43.29: [13383]: <-- data [23]
Apr 01 10:26:43.29: [13383]: <-- data [2]
Apr 01 10:26:43.32: [13383]: --> [7:CONNECT]
Apr 01 10:26:43.32: [13383]: <-- HDLC<7:FF C8 C1 00 70 1F 22>
Apr 01 10:26:43.32: [13383]: <-- data [7]
Apr 01 10:26:43.32: [13383]: <-- data [2]
Apr 01 10:26:44.46: [13383]: --> [2:OK]
Apr 01 10:26:44.46: [13383]: <-- [9:AT+FTS=7\r]
Apr 01 10:26:44.52: [13383]: --> [2:OK]
Apr 01 10:26:44.52: [13383]: <-- [10:AT+FTM=72\r]
Apr 01 10:26:44.53: [13383]: --> [7:CONNECT]
Apr 01 10:26:44.53: [13383]: DELAY 400 ms
Apr 01 10:26:44.93: [13383]: <-- data [1024]
Apr 01 10:26:44.93: [13383]: <-- data [326]
Apr 01 10:26:44.93: [13383]: <-- data [2]
Apr 01 10:26:46.49: [13383]: --> [2:OK]
Apr 01 10:26:46.49: [13383]: <-- [9:AT+FRH=3\r]
Apr 01 10:26:47.74: [13383]: --> [7:CONNECT]
Apr 01 10:26:50.21: [13383]: --> HDLC<5:FF C8 22 67 DD>
Apr 01 10:26:50.21: [13383]: --> [2:OK]
Apr 01 10:26:50.21: [13383]: SEND training at v.27ter 4800 bit/s
Apr 01 10:26:50.21: [13383]: <-- [9:AT+FRS=7\r]
Apr 01 10:26:50.35: [13383]: --> [2:OK]
Apr 01 10:26:50.35: [13383]: <-- [9:AT+FTH=3\r]
Apr 01 10:26:51.21: [13383]: --> [7:CONNECT]
Apr 01 10:26:51.21: [13383]: <-- HDLC<23:FF C0 C2 B2 F2 C2 74 E2 72 92
D2 F2 F2 42 04 04 04 04 04 04 04 04 04>
Apr 01 10:26:51.21: [13383]: <-- data [23]
Apr 01 10:26:51.21: [13383]: <-- data [2]
Apr 01 10:26:51.24: [13383]: --> [7:CONNECT]
Apr 01 10:26:51.24: [13383]: <-- HDLC<7:FF C8 C1 00 50 1F 22>
Apr 01 10:26:51.24: [13383]: <-- data [7]
Apr 01 10:26:51.24: [13383]: <-- data [2]
Apr 01 10:26:52.37: [13383]: --> [2:OK]
Apr 01 10:26:52.37: [13383]: <-- [9:AT+FTS=7\r]
Apr 01 10:26:52.43: [13383]: --> [2:OK]
Apr 01 10:26:52.43: [13383]: <-- [10:AT+FTM=48\r]
Apr 01 10:26:52.45: [13383]: --> [7:CONNECT]
Apr 01 10:26:52.45: [13383]: DELAY 400 ms
Apr 01 10:26:52.85: [13383]: <-- data [900]
Apr 01 10:26:52.85: [13383]: <-- data [2]
Apr 01 10:26:54.93: [13383]: --> [2:OK]
Apr 01 10:26:54.93: [13383]: <-- [9:AT+FRH=3\r]
Apr 01 10:26:56.18: [13383]: --> [7:CONNECT]
Apr 01 10:26:58.65: [13383]: --> HDLC<5:FF C8 22 67 DD>
Apr 01 10:26:58.65: [13383]: --> [2:OK]
Apr 01 10:26:58.65: [13383]: SEND training at v.27ter fallback mode 2400 bit/s
Apr 01 10:26:58.65: [13383]: <-- [9:AT+FRS=7\r]
Apr 01 10:26:58.79: [13383]: --> [2:OK]
Apr 01 10:26:58.79: [13383]: <-- [9:AT+FTH=3\r]
Apr 01 10:26:59.65: [13383]: --> [7:CONNECT]
Apr 01 10:26:59.65: [13383]: <-- HDLC<23:FF C0 C2 B2 F2 C2 74 E2 72 92
D2 F2 F2 42 04 04 04 04 04 04 04 04 04>
Apr 01 10:26:59.65: [13383]: <-- data [23]
Apr 01 10:26:59.65: [13383]: <-- data [2]
Apr 01 10:26:59.68: [13383]: --> [7:CONNECT]
Apr 01 10:26:59.68: [13383]: <-- HDLC<7:FF C8 C1 00 40 1F 22>
Apr 01 10:26:59.68: [13383]: <-- data [7]
Apr 01 10:26:59.68: [13383]: <-- data [2]
Apr 01 10:27:00.81: [13383]: --> [2:OK]
Apr 01 10:27:00.81: [13383]: <-- [9:AT+FTS=7\r]
Apr 01 10:27:00.87: [13383]: --> [2:OK]
Apr 01 10:27:00.87: [13383]: <-- [10:AT+FTM=24\r]
Apr 01 10:27:00.89: [13383]: --> [7:CONNECT]
Apr 01 10:27:00.89: [13383]: DELAY 400 ms
Apr 01 10:27:01.29: [13383]: <-- data [450]
Apr 01 10:27:01.29: [13383]: <-- data [2]
Apr 01 10:27:03.66: [13383]: --> [2:OK]
Apr 01 10:27:03.66: [13383]: <-- [9:AT+FRH=3\r]
Apr 01 10:27:04.93: [13383]: --> [7:CONNECT]
Apr 01 10:27:07.39: [13383]: --> HDLC<5:FF C8 22 67 DD>
Apr 01 10:27:07.39: [13383]: --> [2:OK]
Apr 01 10:27:07.39: [13383]: TRAINING failed
Apr 01 10:27:07.39: [13383]: <-- [9:AT+FRS=7\r]
Apr 01 10:27:07.53: [13383]: --> [2:OK]
Apr 01 10:27:07.53: [13383]: <-- [9:AT+FTH=3\r]
Apr 01 10:27:08.39: [13383]: --> [7:CONNECT]
Apr 01 10:27:08.39: [13383]: <-- HDLC<3:FF C8 DF>
Apr 01 10:27:08.39: [13383]: <-- data [3]
Apr 01 10:27:08.39: [13383]: <-- data [2]
Apr 01 10:27:08.72: [13383]: --> [2:OK]
Apr 01 10:27:08.72: [13383]: MODEM input buffering enabled
Apr 01 10:27:09.72: [13383]: <-- [5:ATH0\r]
Apr 01 10:27:10.50: [13383]: --> [2:OK]
Apr 01 10:27:10.50: [13383]: MODEM set DTR OFF
Apr 01 10:27:10.50: [13383]: STATE CHANGE: SENDING -> MODEMWAIT (timeout 5)
Apr 01 10:27:10.51: [13383]: SESSION END

My hylafax settings are by default, except for ModemDialCmd:


CountryCode: 55
AreaCode: 11
FAXNumber: +XXXXXXXXXX
LongDistancePrefix: 015
InternationalPrefix: 0015
DialStringRules: etc/dialrules
ServerTracing: 1
SessionTracing: 0xFFF
RecvFileMode: 0600
LogFileMode: 0600
DeviceMode: 0600
RingsBeforeAnswer: 1
SpeakerVolume: off
GettyArgs: "-h %l dx_%s"
LocalIdentifier: XXXXXXX
TagLineFont: etc/lutRS18.pcf
TagLineFormat: "From %%l|%c|Page %%P of %%T"
MaxRecvPages: 25

ModemType: Class1 # use this to supply a hint
ModemFlowControl: rtscts # many firmwares have broken software flow control
ModemSetupDTRCmd: AT&D3 # hang up and reset on DTR drop
Class1TMConnectDelay: 400 # counteract quick CONNECT response
Class1HasRHConnectBug: yes # cope with +FRH=3 CONNECT errors

ModemDialCmd: ATDT0W%s

Does anybody have an idea of what can be wrong here?

Thanks,
Vladimir


____________________ HylaFAX(tm) Users Mailing List _______________________
To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi
On UNIX: mail -s unsubscribe hylafax-us...@hylafax.org < /dev/null
*To learn about commercial HylaFAX(tm) support, mail sa...@ifax.com.*

Lee Howard

unread,
Apr 1, 2011, 11:05:39 AM4/1/11
to Momonth, hylafa...@hylafax.org
Momonth wrote:
> Apr 01 10:26:02.69: [13383]: <-- [22:ATDT0W001531XXXXXXXXX\r]
> Apr 01 10:26:30.54: [13383]: --> [7:CONNECT]
> Apr 01 10:26:33.24: [13383]: --> HDLC<19:FF C0 04 DB 00 00 00 00 00 00
> 00 00 00 00 00 00 00 A4 B7>
> Apr 01 10:26:33.24: [13383]: --> [2:OK]
> Apr 01 10:26:33.24: [13383]: REMOTE NSF "DB 00 00 00 00 00 00 00 00 00
> 00 00 00 00"
> Apr 01 10:26:33.24: [13383]: NSF remote fax equipment: unknown
>

That NSF tells us that you're passing through a T.38 link of some sort.

> Apr 01 10:26:33.24: [13383]: <-- [9:AT+FRH=3\r]
> Apr 01 10:26:33.26: [13383]: --> [7:CONNECT]
> Apr 01 10:26:33.98: [13383]: --> HDLC<25:FF C0 02 9C 6C 8C CC AC 8C EC
> 0C 4C 8C CC D4 04 04 04 04 04 04 04 04 9F CA>
> Apr 01 10:26:33.98: [13383]: --> [2:OK]
> Apr 01 10:26:33.98: [13383]: REMOTE CSI "+31XXXXXXXXX"
> Apr 01 10:26:33.98: [13383]: <-- [9:AT+FRH=3\r]
> Apr 01 10:26:33.99: [13383]: --> [7:CONNECT]
> Apr 01 10:26:34.41: [13383]: --> HDLC<15:FF C8 01 00 72 19 23 01 91 01
> 01 01 04 32 32>
> Apr 01 10:26:34.41: [13383]: --> [2:OK]
> Apr 01 10:26:34.41: [13383]: REMOTE best rate 9600 bit/s
> Apr 01 10:26:34.41: [13383]: REMOTE max A4 page width (215 mm)
> Apr 01 10:26:34.41: [13383]: REMOTE max unlimited page length
> Apr 01 10:26:34.41: [13383]: REMOTE best vres 200 x 400 dpi
> Apr 01 10:26:34.41: [13383]: REMOTE format support: MH, MMR, JBIG
> Apr 01 10:26:34.41: [13383]: REMOTE supports T.30 Annex A, 256-byte ECM
> Apr 01 10:26:34.41: [13383]: REMOTE best 5 ms/scanline
>

What an odd set of remote protocol support. JBIG and ECM without V.17.
MH and MMR without MR.

Anyway, remove the T.38 link and see what happens. I suspect your
problems will go away.

Thanks,

Lee.

Momonth

unread,
Apr 1, 2011, 2:54:57 PM4/1/11
to Lee Howard, hylafa...@hylafax.org
I'm successfully sending faxes to the same 'remote' (it's some OKI
device, I can tell you the exact model later on) via "Dialogic DIVA
V-PRI/ E1-30", here is the log file:

Apr 01 20:33:24.81: [ 8676]: SESSION BEGIN 000099228 +31XXXXXXXXX
Apr 01 20:33:24.81: [ 8676]: HylaFAX (tm) Version 5.2.7
Apr 01 20:33:24.81: [ 8676]: SEND FAX: JOB 133142 DEST 0031XXXXXXXXX
COMMID 000099228 DEVICE '/dev/ttyds20' FROM 'root <root@fax-107>'
USER root
Apr 01 20:33:24.82: [ 8676]: <-- [10:AT+FBOR=0\r]
Apr 01 20:33:24.83: [ 8676]: --> [2:OK]
Apr 01 20:33:24.83: [ 8676]: <-- [24:AT+FDCC=1,D,2,2,8,2,0,0\r]
Apr 01 20:33:24.85: [ 8676]: --> [2:OK]
Apr 01 20:33:24.88: [ 8676]: DIAL 0031XXXXXXXXX
Apr 01 20:33:24.88: [ 8676]: <-- [18:ATDT0031XXXXXXXXX\r]
Apr 01 20:33:41.85: [ 8676]: --> [5:+FCON]
Apr 01 20:33:41.85: [ 8676]: --> [28:+FCSI:" +31XXXXXXXXX"]
Apr 01 20:33:41.85: [ 8676]: REMOTE CSI "+31XXXXXXXXX"
Apr 01 20:33:41.85: [ 8676]: --> [22:+FDIS: 1,3,0,2,0,2,0,1]
Apr 01 20:33:41.85: [ 8676]: --> [2:OK]
Apr 01 20:33:41.85: [ 8676]: REMOTE best rate 9600 bit/s
Apr 01 20:33:41.85: [ 8676]: REMOTE max A4 page width (215 mm)
Apr 01 20:33:41.85: [ 8676]: REMOTE max unlimited page length
Apr 01 20:33:41.85: [ 8676]: REMOTE best vres 7.7 line/mm
Apr 01 20:33:41.85: [ 8676]: REMOTE format support: MH
Apr 01 20:33:41.85: [ 8676]: REMOTE supports T.30 Annex A, 256-byte ECM
Apr 01 20:33:41.85: [ 8676]: REMOTE best 5 ms/scanline
Apr 01 20:33:41.85: [ 8676]: USE 9600 bit/s
Apr 01 20:33:41.85: [ 8676]: USE error correction mode
Apr 01 20:33:41.85: [ 8676]: SEND file "docq/doc1.ps;00"
Apr 01 20:33:41.85: [ 8676]: USE A4 page width (215 mm)
Apr 01 20:33:41.85: [ 8676]: USE unlimited page length
Apr 01 20:33:41.85: [ 8676]: USE 3.85 line/mm
Apr 01 20:33:41.85: [ 8676]: USE 1-D MH
Apr 01 20:33:41.85: [ 8676]: USE 0 ms/scanline
Apr 01 20:33:41.85: [ 8676]: <-- [24:AT+FDIS=0,3,0,2,0,2,0,0\r]
Apr 01 20:33:41.87: [ 8676]: --> [2:OK]
Apr 01 20:33:41.87: [ 8676]: <-- [7:AT+FDT\r]
Apr 01 20:33:48.83: [ 8676]: --> [22:+FDCS: 0,3,0,2,0,2,0,1]
Apr 01 20:33:49.04: [ 8676]: --> [7:CONNECT]
Apr 01 20:33:49.04: [ 8676]: SEND wait for XON
Apr 01 20:33:49.06: [ 8676]: --> [1:^Q]
Apr 01 20:33:49.06: [ 8676]: SEND begin page
Apr 01 20:33:49.06: [ 8676]: <-- data [1027]
Apr 01 20:33:49.06: [ 8676]: <-- data [1029]
Apr 01 20:33:49.08: [ 8676]: <-- data [1029]
Apr 01 20:33:49.10: [ 8676]: <-- data [870]
Apr 01 20:33:49.12: [ 8676]: SENT 3938 bytes of data
Apr 01 20:33:49.12: [ 8676]: <-- data [2]
Apr 01 20:33:49.12: [ 8676]: SEND end page
Apr 01 20:33:49.99: [ 8676]: --> [2:OK]
Apr 01 20:33:49.99: [ 8676]: SEND send EOP (no more pages or documents)
Apr 01 20:33:49.99: [ 8676]: <-- [9:AT+FET=2\r]
Apr 01 20:33:56.31: [ 8676]: --> [8:+FPTS: 1]
Apr 01 20:33:56.31: [ 8676]: --> [8:+FHNG: 0]
Apr 01 20:33:56.31: [ 8676]: REMOTE HANGUP: Normal and proper end of
connection (code 0)
Apr 01 20:33:56.31: [ 8676]: --> [2:OK]
Apr 01 20:33:56.31: [ 8676]: SEND recv MCF (message confirmation)
Apr 01 20:33:56.32: [ 8676]: SEND FAX (000099228): FROM root@fax-107
TO 0031XXXXXXXXX (docq/doc1.ps;00 sent in 0:00:15)
Apr 01 20:33:56.32: [ 8676]: SEND FAX (000099228): FROM root@fax-107
TO 0031XXXXXXXXX (page 1 of 1 sent in 0:00:15)
Apr 01 20:33:58.32: [ 8676]: <-- [5:ATH0\r]
Apr 01 20:33:58.34: [ 8676]: --> [2:OK]
Apr 01 20:33:58.34: [ 8676]: SESSION END

2011/4/1 Lee Howard <fax...@howardsilvan.com>:


>
> What an odd set of remote protocol support. JBIG and ECM without V.17. MH
> and MMR without MR.
>
> Anyway, remove the T.38 link and see what happens. I suspect your problems
> will go away.

Could you please tell me a bit more how can "remove the T.38 link"?

If it's about changing "OKI" settings, I doubt then that it's the
case. Because as I showed above it can actually accept faxes, and not
only from my fax server, but also other people (using deferent devices
I'd assume) send faxes ..

Thanks,
Vladimir

Lee Howard

unread,
Apr 1, 2011, 8:41:26 PM4/1/11
to Momonth, hylafa...@hylafax.org

Note that HylaFAX is seeing the receiver differently here than it did
from when using your Class 1 modem. Note also that there is no T.38 NSF
presented here when using the Dialogic. Here's what you got with the
Class 1 modem:

Apr 01 10:26:34.41: [13383]: REMOTE best rate 9600 bit/s
Apr 01 10:26:34.41: [13383]: REMOTE max A4 page width (215 mm)
Apr 01 10:26:34.41: [13383]: REMOTE max unlimited page length
Apr 01 10:26:34.41: [13383]: REMOTE best vres 200 x 400 dpi
Apr 01 10:26:34.41: [13383]: REMOTE format support: MH, MMR, JBIG
Apr 01 10:26:34.41: [13383]: REMOTE supports T.30 Annex A, 256-byte ECM
Apr 01 10:26:34.41: [13383]: REMOTE best 5 ms/scanline


Note that there are a whole host of differences between the two with
respect to vres and format support. Whether the receiver is presenting
itself differently or whether the T.38 link is not involved with the
Dialogic.

> Apr 01 20:33:41.85: [ 8676]: USE 9600 bit/s
> Apr 01 20:33:41.85: [ 8676]: USE error correction mode
> Apr 01 20:33:41.85: [ 8676]: SEND file "docq/doc1.ps;00"
> Apr 01 20:33:41.85: [ 8676]: USE A4 page width (215 mm)
> Apr 01 20:33:41.85: [ 8676]: USE unlimited page length
> Apr 01 20:33:41.85: [ 8676]: USE 3.85 line/mm
> Apr 01 20:33:41.85: [ 8676]: USE 1-D MH
> Apr 01 20:33:41.85: [ 8676]: USE 0 ms/scanline
>

Consequently, when using the Dialogic you end up sending with MH
compression. However, when sending with the Class 1 modem...

Apr 01 10:26:34.41: [13383]: USE 9600 bit/s
Apr 01 10:26:34.41: [13383]: USE error correction mode
Apr 01 10:26:34.41: [13383]: SEND file "docq/doc21.ps;00"
Apr 01 10:26:34.41: [13383]: USE A4 page width (215 mm)
Apr 01 10:26:34.41: [13383]: USE unlimited page length
Apr 01 10:26:34.41: [13383]: USE 3.85 line/mm
Apr 01 10:26:34.41: [13383]: USE 2-D MMR
Apr 01 10:26:34.41: [13383]: USE 0 ms/scanline
Apr 01 10:26:34.41: [13383]: SEND training at v.29 9600 bit/s


.. you end up using MMR compression.

My initial guess here is that the T.38 link is either adding or
modifying the DIS signal from the receiver to include MMR and JBIG and
that this is the real problem - that when HylaFAX sends DCS including
MMR it causes the fax to fail because the receiver doesn't really
support MMR... or at least not through the T.38 link, anyway.

I think you're going to need to disable ModemSoftRTFCC on your Class 1
modem and then submit the job requesting MH compression when sending to
that location. How you go about doing that will depend on what client
software you are using to submit the faxes.

If you're using sendfax, then if you update your HylaFAX+ version to
5.3.0 or newer (and I'd recommend 5.5.0) you could use the -O
config:ModemSoftRTFCC:no option to do this without disabling
ModemSoftRTFCC for all destinations. With 5.2.7 you could use
JobControl, though, to do it a bit more dynamically.

>> Anyway, remove the T.38 link and see what happens. I suspect your problems
>> will go away.
>>
>
> Could you please tell me a bit more how can "remove the T.38 link"?
>

Typically you'd talk to your telco or work with your PBX to not use
fax-over-ip channels.

> If it's about changing "OKI" settings,

What are "OKI" settings?

> I doubt then that it's the
> case. Because as I showed above it can actually accept faxes, and not
> only from my fax server, but also other people (using deferent devices
> I'd assume) send faxes ..

The two sessions were dissimilar. So something is happening differently
between them. It's not an apples-to-apples comparison.

Thanks.

Lee.

0 new messages