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

[Patrice Fournier <pfournier@loups.net>]

Quoting procadas@creditus.pt:

> This is what happens when I send the fax from whfc, for example.
> 
> Apr 04 12:46:36.22: [ 5832]: SEND FAX: JOB 1731 DEST xxxxxxxxx COMMID
> 00003654 DEVICE '/dev/ttyS1'

There should be two lines before that one... look at the first one with 
SESSION BEGIN <commid> <cannonical number>

Doest the cannonical number really is the cannonical number or is there an 
error in your rules that make them all match point to the same number? The 
info file you need to look at for the capabilities as seen by HylaFAX will 
be info/<that cannonical number>

> Apr 04 12:46:36.22: [ 5832]: DELAY 75 ms
> Apr 04 12:46:36.30: [ 5832]: DELAY 2600 ms
> Apr 04 12:46:38.90: [ 5832]: <-- [4:ATZ\r]
> Apr 04 12:46:39.03: [ 5832]: --> [2:OK]
> Apr 04 12:46:39.03: [ 5832]: DELAY 3000 ms
> Apr 04 12:46:42.03: [ 5832]: <-- [5:ATE0\r]
> Apr 04 12:46:42.04: [ 5832]: --> [4:ATE0]
> Apr 04 12:46:42.04: [ 5832]: --> [2:OK]
> Apr 04 12:46:42.04: [ 5832]: <-- [5:ATV1\r]
> Apr 04 12:46:42.05: [ 5832]: --> [2:OK]
> Apr 04 12:46:42.05: [ 5832]: <-- [5:ATQ0\r]
> Apr 04 12:46:42.06: [ 5832]: --> [2:OK]
> Apr 04 12:46:42.06: [ 5832]: <-- [7:ATS0=0\r]
> Apr 04 12:46:42.07: [ 5832]: --> [2:OK]
> Apr 04 12:46:42.07: [ 5832]: <-- [7:ATS8=2\r]
> Apr 04 12:46:42.09: [ 5832]: --> [2:OK]
> Apr 04 12:46:42.09: [ 5832]: <-- [8:ATS7=60\r]
> Apr 04 12:46:42.11: [ 5832]: --> [2:OK]
> Apr 04 12:46:42.11: [ 5832]: <-- [12:AT+FCLASS=1\r]
> Apr 04 12:46:42.13: [ 5832]: --> [2:OK]
> Apr 04 12:46:42.13: [ 5832]: <-- [5:ATM0\r]
> Apr 04 12:46:42.14: [ 5832]: --> [2:OK]
> Apr 04 12:46:42.14: [ 5832]: <-- [12:AT+FCLASS=1\r]
> Apr 04 12:46:42.26: [ 5832]: --> [2:OK]
> Apr 04 12:46:42.26: [ 5832]: DIAL 0,xxxxxxxxx
> Apr 04 12:46:42.26: [ 5832]: <-- [16:ATDT0,xxxxxxxxx\r]
> Apr 04 12:47:03.71: [ 5832]: --> [7:CONNECT]
> Apr 04 12:47:05.60: [ 5832]: --> [2:OK]
> Apr 04 12:47:05.60: [ 5832]: REMOTE NSF "00 00 79 00 00 00 82 0F 09 12
> 00 10 05 02 85 C
> 8 88 80 80 01 01 49 02 47 41 4C 45 52 49 41 53 20 50 52 49 4D 4F 52 20
> 03 BA"
> Apr 04 12:47:05.60: [ 5832]: NSF remote fax equipment: Panasonic
> Apr 04 12:47:05.60: [ 5832]: NSF remote station ID: "xxxxxxxxxxxxx "
> Apr 04 12:47:05.60: [ 5832]: <-- [9:AT+FRH=3\r]
> Apr 04 12:47:05.62: [ 5832]: --> [7:CONNECT]
> Apr 04 12:47:06.29: [ 5832]: --> [2:OK]
> Apr 04 12:47:06.29: [ 5832]: REMOTE CSI "xxxxxxxxxxxx"
> Apr 04 12:47:06.29: [ 5832]: <-- [9:AT+FRH=3\r]
> Apr 04 12:47:06.31: [ 5832]: --> [7:CONNECT]
> Apr 04 12:47:06.56: [ 5832]: --> [2:OK]
> Apr 04 12:47:06.56: [ 5832]: REMOTE best rate 9600 bit/s
> Apr 04 12:47:06.56: [ 5832]: REMOTE max page width 1728 pixels in 215
> mm
> Apr 04 12:47:06.56: [ 5832]: REMOTE max unlimited page length
> Apr 04 12:47:06.56: [ 5832]: REMOTE best vres 7.7 line/mm
> Apr 04 12:47:06.56: [ 5832]: REMOTE best format 1-D MR
> Apr 04 12:47:06.56: [ 5832]: REMOTE best 20 ms, 10 ms/scanline
> Apr 04 12:47:06.56: [ 5832]: USE 9600 bit/s
> Apr 04 12:47:06.56: [ 5832]: USE 20 ms, 10 ms/scanline
> Apr 04 12:47:06.56: [ 5832]: SEND file "docq/doc1731.ps;40"
> Apr 04 12:47:06.56: [ 5832]: Document was encoded with 2DMR, but
> client does not support this data format

That means the info file told HylaFAX that the remote system could do 
2D...

> Apr 04 12:47:06.56: [ 5832]: <-- [9:AT+FTH=3\r]
> Apr 04 12:47:06.61: [ 5832]: --> [7:CONNECT]
> Apr 04 12:47:06.61: [ 5832]: <-- data [3]
> Apr 04 12:47:06.61: [ 5832]: <-- data [2]
> Apr 04 12:47:07.93: [ 5832]: --> [2:OK]
> Apr 04 12:47:07.93: [ 5832]: <-- [5:ATH0\r]
> Apr 04 12:47:09.86: [ 5832]: --> [2:OK]
> Apr 04 12:47:09.86: [ 5832]: SESSION END

Isn't there a call after that one for the same job which sends the file in 
1D? That's how it's supposed to work (and how it worked here whenever a 
remote changed machine to one that didn't do 2D)

> Editing the info/351xxxxxx file I can see supports2DEncoding:no.

Are you sure you edit the right file (see my comment about the first line 
of the communication log)

> I think hylafax turn to 1-D but because the file was encoded 2DMR the
> error show up?

Sorry, I don't understand that question... but HylaFAX encoded the file in 
2DMR because the info file said the remote would do it according to the 
last call to that number... as the current call can be accomplished in 2D, 
it hang up to be able to convert the document and try again. Are you 
faxing lots of faxes, with many lines? If all the numbers maps to the same 
cannonical number, and most machines do 2D, the file could be change to 
show 2D support between the two calls which would make the second attempt 
still fail... 

-- 
Patrice Fournier
pfournier@loups.net

____________________ 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