[hylafax-users] How 2D-MR work?

To: hylafax-users@hylafax.org
Subject: [hylafax-users] How 2D-MR work?
From: procadas@creditus.pt
Date: Wed, 3 Apr 2002 19:49:11 +0100
I return to this question(not entirely :-) ) because after tracing the logs
for a couple of days I can resume the situation to this:

If I force 1-D in the command line the job went well(I included the tag in
my scripts), but if the fax is sent from some client or not including the
-1 parameter the fax fails. The advice from Lee to include in destctrls
<number> supports2DEncoding=no don't fix the problem, but I can see in the
logs that hylafax receive the REMOTE best format 1-D MR message but is
unable to reencoding the job. No one seems having this behavior in their
systems so I'm asking myself if something is brooke in the midlle. If I
could use the tag Use2D in destctrls maybe could fix things while I not
found what's going on. Just one last question, where in the log we cann see
wich enconding(1-D/2D) is used? Thanks.

Apr 03 19:50:33.28: [23459]: SEND FAX: JOB 1617 DEST 23250 COMMID 00003387
DEVICE '/dev
/ttyS0'
Apr 03 19:50:33.28: [23459]: DELAY 75 ms
Apr 03 19:50:33.36: [23459]: DELAY 2600 ms
Apr 03 19:50:35.96: [23459]: <-- [4:ATZ\r]
Apr 03 19:50:36.09: [23459]: --> [2:OK]
Apr 03 19:50:36.09: [23459]: DELAY 3000 ms
Apr 03 19:50:39.09: [23459]: <-- [5:ATE0\r]
Apr 03 19:50:39.22: [23459]: --> [4:ATE0]
Apr 03 19:50:39.22: [23459]: --> [2:OK]
Apr 03 19:50:39.22: [23459]: <-- [5:ATV1\r]
Apr 03 19:50:39.35: [23459]: --> [2:OK]
Apr 03 19:50:39.35: [23459]: <-- [7:ATQ0X4\r]
Apr 03 19:50:39.48: [23459]: --> [2:OK]
Apr 03 19:50:39.48: [23459]: <-- [7:ATS0=0\r]
Apr 03 19:50:39.61: [23459]: --> [2:OK]
Apr 03 19:50:39.61: [23459]: <-- [7:ATS8=2\r]
Apr 03 19:50:39.74: [23459]: --> [2:OK]
Apr 03 19:50:39.74: [23459]: <-- [8:ATS7=60\r]
Apr 03 19:50:39.87: [23459]: --> [2:OK]
Apr 03 19:50:39.87: [23459]: <-- [12:AT&H2&I2&R1\r]
Apr 03 19:50:40.01: [23459]: --> [2:OK]
Apr 03 19:50:40.01: [23459]: <-- [11:ATS13=1&D2\r]
Apr 03 19:50:40.15: [23459]: --> [2:OK]
Apr 03 19:50:40.15: [23459]: <-- [6:AT&C1\r]
Apr 03 19:50:40.28: [23459]: --> [2:OK]
Apr 03 19:50:40.28: [23459]: <-- [12:AT+FCLASS=1\r]
Apr 03 19:50:40.42: [23459]: --> [2:OK]
Apr 03 19:50:40.42: [23459]: <-- [12:AT+FCLASS=0\r]
Apr 03 19:50:40.56: [23459]: --> [2:OK]
Apr 03 19:50:40.56: [23459]: <-- [5:ATM0\r]
Apr 03 19:50:40.69: [23459]: --> [2:OK]
Apr 03 19:50:40.69: [23459]: <-- [12:AT+FCLASS=1\r]
Apr 03 19:50:40.93: [23459]: --> [2:OK]
Apr 03 19:50:40.93: [23459]: DIAL ,23250
Apr 03 19:50:40.93: [23459]: <-- [11:ATDT,23250\r]
Apr 03 19:50:59.16: [23459]: --> [7:CONNECT]
Apr 03 19:51:00.63: [23459]: --> [2:OK]
Apr 03 19:51:00.63: [23459]: REMOTE NSF "00 00 09 00 09 00 30 30 30 30 FF
FF FF FF FF F
F FF FF 22 55 12 75 0F FF FF FF FF FF FF FF 65"
Apr 03 19:51:00.63: [23459]: NSF remote fax equipment: Xerox
Apr 03 19:51:00.63: [23459]: NSF remote station ID: "0000"
Apr 03 19:51:00.63: [23459]: <-- [9:AT+FRH=3\r]
Apr 03 19:51:00.64: [23459]: --> [7:CONNECT]
Apr 03 19:51:01.35: [23459]: --> [2:OK]
Apr 03 19:51:01.35: [23459]: REMOTE CSI "xxxxxxxxxx"
Apr 03 19:51:01.35: [23459]: <-- [9:AT+FRH=3\r]
Apr 03 19:51:01.36: [23459]: --> [7:CONNECT]
Apr 03 19:51:01.65: [23459]: --> [2:OK]
Apr 03 19:51:01.65: [23459]: REMOTE best rate 14400 bit/s
Apr 03 19:51:01.65: [23459]: REMOTE max page width 1728 pixels in 215 mm
Apr 03 19:51:01.65: [23459]: REMOTE max unlimited page length
Apr 03 19:51:01.65: [23459]: REMOTE best vres 7.7 line/mm
Apr 03 19:51:01.65: [23459]: REMOTE best format 2-D MMR
Apr 03 19:51:01.65: [23459]: REMOTE supports T.30 Annex A, ECM
Apr 03 19:51:01.65: [23459]: REMOTE best 10 ms/scanline
Apr 03 19:51:01.65: [23459]: USE 14400 bit/s
Apr 03 19:51:01.65: [23459]: USE 10 ms/scanline
Apr 03 19:51:01.65: [23459]: SEND file "docq/doc1617.ps;40"
Apr 03 19:51:01.65: [23459]: USE page width 1728 pixels in 215 mm
Apr 03 19:51:01.65: [23459]: USE unlimited page length
Apr 03 19:51:01.65: [23459]: USE 3.85 line/mm
Apr 03 19:51:01.65: [23459]: USE 2-D MR
Apr 03 19:51:01.65: [23459]: SEND training at v.17 14400 bit/s
Apr 03 19:51:01.65: [23459]: <-- [9:AT+FTH=3\r]
Apr 03 19:51:01.84: [23459]: --> [7:CONNECT]
Apr 03 19:51:01.84: [23459]: <-- data [23]
Apr 03 19:51:01.84: [23459]: <-- data [2]
Apr 03 19:51:01.86: [23459]: --> [7:CONNECT]
Apr 03 19:51:01.86: [23459]: <-- data [6]
Apr 03 19:51:01.86: [23459]: <-- data [2]
Apr 03 19:51:03.82: [23459]: --> [2:OK]
Apr 03 19:51:03.82: [23459]: <-- [9:AT+FTS=7\r]
Apr 03 19:51:03.90: [23459]: --> [2:OK]
Apr 03 19:51:03.90: [23459]: <-- [11:AT+FTM=145\r]
Apr 03 19:51:05.38: [23459]: --> [7:CONNECT]
Apr 03 19:51:05.38: [23459]: <-- data [1024]
Apr 03 19:51:05.38: [23459]: <-- data [1024]
Apr 03 19:51:05.38: [23459]: <-- data [652]
Apr 03 19:51:05.38: [23459]: <-- data [2]
Apr 03 19:51:06.91: [23459]: --> [2:OK]
Apr 03 19:51:06.91: [23459]: <-- [9:AT+FRH=3\r]
Apr 03 19:51:07.42: [23459]: --> [7:CONNECT]
Apr 03 19:51:08.37: [23459]: --> [2:OK]
Apr 03 19:51:08.37: [23459]: TRAINING succeeded
Apr 03 19:51:08.37: [23459]: DELAY 75 ms
Apr 03 19:51:08.45: [23459]: <-- [11:AT+FTM=146\r]
Apr 03 19:51:08.71: [23459]: --> [7:CONNECT]
Apr 03 19:51:08.71: [23459]: SEND begin page
Apr 03 19:51:08.71: [23459]: <-- data [1027]
Apr 03 19:51:08.71: [23459]: <-- data [1024]
Apr 03 19:51:08.71: [23459]: <-- data [465]
Apr 03 19:51:08.71: [23459]: SENT 2513 bytes of data
Apr 03 19:51:08.71: [23459]: SEND 2D RTC
Apr 03 19:51:08.71: [23459]: <-- data [30]
Apr 03 19:51:08.71: [23459]: <-- data [2]
Apr 03 19:51:08.71: [23459]: SEND end page
Apr 03 19:51:10.15: [23459]: --> [2:OK]
Apr 03 19:51:10.15: [23459]: <-- [9:AT+FTS=9\r]
Apr 03 19:51:10.25: [23459]: --> [2:OK]
Apr 03 19:51:10.25: [23459]: SEND send EOP (no more pages or documents)
Apr 03 19:51:10.25: [23459]: <-- [9:AT+FTH=3\r]
Apr 03 19:51:10.40: [23459]: --> [7:CONNECT]
Apr 03 19:51:10.40: [23459]: <-- data [3]
Apr 03 19:51:10.40: [23459]: <-- data [2]
Apr 03 19:51:11.58: [23459]: --> [2:OK]
Apr 03 19:51:11.58: [23459]: <-- [9:AT+FRH=3\r]
Apr 03 19:51:12.22: [23459]: --> [7:CONNECT]
Apr 03 19:51:13.01: [23459]: --> [2:OK]
Apr 03 19:51:13.01: [23459]: SEND recv MCF (message confirmation)
Apr 03 19:51:13.01: [23459]: SEND FAX (00003387): FROM xxxxxxxxxxx TO 23250
(p
age 1 of 1 sent in 0:12)
Apr 03 19:51:13.01: [23459]: SEND FAX (00003387): FROM xxxxxxxxx TO 23250
(d
ocq/doc1617.ps;40 sent in 0:12)
Apr 03 19:51:13.01: [23459]: <-- [9:AT+FTH=3\r]
Apr 03 19:51:13.20: [23459]: --> [7:CONNECT]
Apr 03 19:51:13.20: [23459]: <-- data [3]
Apr 03 19:51:13.20: [23459]: <-- data [2]
Apr 03 19:51:14.38: [23459]: --> [2:OK]
Apr 03 19:51:14.38: [23459]: <-- [5:ATH0\r]
Apr 03 19:51:14.61: [23459]: --> [2:OK]
Apr 03 19:51:14.61: [23459]: SESSION END


Pedro Ro�adas (procadas@creditus.pt)
Dpt� Inform�tica,BPN-Cr�ditus Technical Staff


____________________ 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@hylafax.org < /dev/null
Follow-Ups:
- Re: [hylafax-users] How 2D-MR work?
  - From: Giulio Orsero
Prev by Date: [hylafax-users] Hylafax & mgetty (speed and proxyarp problem)
Next by Date: Re: [hylafax-users] How 2D-MR work?
Previous by thread: Re: [hylafax-users] faxgetty does not pass the call to vgetty
Next by thread: Re: [hylafax-users] How 2D-MR work?
Index(es):
- Main
- Thread
Project hosted by iFAX Solutions