Re: [hylafax-users] Performance Tuning and sendfax -S

[Lee Howard <faxguy@xxxxxxxxxxxxxxxx>]

Konrad Baechler wrote:

> Mar 25 17:20:48.07: [16944]: <-- [24:AT+FDCC=1,5,2,2,0,2,0,0\r]
> Mar 25 17:20:48.07: [16944]: --> [2:OK]
> Mar 25 17:20:48.07: [16944]: DIAL ...
> Mar 25 17:20:48.07: [16944]: <-- [15:ATDT...\r]
> Mar 25 17:21:27.68: [16944]: --> [5:+FCON]
> Mar 25 17:21:27.68: [16944]: --> [28:+FCSI:"    +41 ..."]
> Mar 25 17:21:27.68: [16944]: REMOTE CSI "+41 ..."
> Mar 25 17:21:27.68: [16944]: --> [22:+FDIS: 1,5,0,2,0,2,0,0]
> Mar 25 17:21:27.68: [16944]: --> [2:OK]
> Mar 25 17:21:27.68: [16944]: REMOTE best rate 14400 bit/s
> Mar 25 17:21:27.68: [16944]: REMOTE max A4 page width (215 mm)
> Mar 25 17:21:27.68: [16944]: REMOTE max unlimited page length
> Mar 25 17:21:27.68: [16944]: REMOTE best vres 7.7 line/mm
> Mar 25 17:21:27.68: [16944]: REMOTE format support: MH
> Mar 25 17:21:27.68: [16944]: REMOTE supports T.30 Annex C, half duplex
>   ECM
> Mar 25 17:21:27.68: [16944]: REMOTE best 0 ms/scanline
> Mar 25 17:21:27.68: [16944]: USE 14400 bit/s
> Mar 25 17:21:27.68: [16944]: USE error correction mode
> Mar 25 17:21:27.68: [16944]: SEND file "docq/doc106.tif;01"
> Mar 25 17:21:27.68: [16944]: USE A4 page width (215 mm)
> Mar 25 17:21:27.68: [16944]: USE unlimited page length
> Mar 25 17:21:27.68: [16944]: USE 7.7 line/mm
> Mar 25 17:21:27.68: [16944]: USE 1-D MH
> Mar 25 17:21:27.68: [16944]: USE 0 ms/scanline
> Mar 25 17:21:27.68: [16944]: <-- [24:AT+FDIS=1,5,0,2,0,0,0,0\r]
> Mar 25 17:21:27.68: [16944]: --> [2:OK]
> Mar 25 17:21:27.68: [16944]: <-- [7:AT+FDT\r]
> Mar 25 17:21:39.70: [16944]: --> [22:+FDCS: 1,3,0,2,0,2,0,0]
> Mar 25 17:21:39.91: [16944]: --> [7:CONNECT]


Okay, in comparing that log above with this log below...

> Mar 25 17:55:29.29: [20939]: <-- [24:AT+FDCC=1,5,2,2,0,2,0,0\r]
> Mar 25 17:55:29.29: [20939]: --> [2:OK]
> Mar 25 17:55:29.29: [20939]: DIAL ...
> Mar 25 17:55:29.29: [20939]: <-- [15:ATDT...\r]
> Mar 25 17:55:47.48: [20939]: --> [5:+FCON]
> Mar 25 17:55:47.48: [20939]: --> [28:+FCSI:"    +41 ..."]
> Mar 25 17:55:47.48: [20939]: REMOTE CSI "+41 ..."
> Mar 25 17:55:47.48: [20939]: --> [22:+FDIS: 1,5,0,2,0,2,0,0]
> Mar 25 17:55:47.48: [20939]: --> [2:OK]
> Mar 25 17:55:47.48: [20939]: REMOTE best rate 14400 bit/s
> Mar 25 17:55:47.48: [20939]: REMOTE max A4 page width (215 mm)
> Mar 25 17:55:47.48: [20939]: REMOTE max unlimited page length
> Mar 25 17:55:47.48: [20939]: REMOTE best vres 7.7 line/mm
> Mar 25 17:55:47.48: [20939]: REMOTE format support: MH
> Mar 25 17:55:47.48: [20939]: REMOTE supports T.30 Annex C, half duplex
>   ECM
> Mar 25 17:55:47.48: [20939]: REMOTE best 0 ms/scanline
> Mar 25 17:55:47.48: [20939]: USE 14400 bit/s
> Mar 25 17:55:47.48: [20939]: USE error correction mode
> Mar 25 17:55:47.48: [20939]: SEND file "docq/doc111.tif;01"
> Mar 25 17:55:47.48: [20939]: USE A4 page width (215 mm)
> Mar 25 17:55:47.48: [20939]: USE unlimited page length
> Mar 25 17:55:47.48: [20939]: USE 7.7 line/mm
> Mar 25 17:55:47.48: [20939]: USE 1-D MH
> Mar 25 17:55:47.48: [20939]: USE 0 ms/scanline
> Mar 25 17:55:47.48: [20939]: <-- [24:AT+FDIS=1,5,0,2,0,0,0,0\r]
> Mar 25 17:55:47.48: [20939]: --> [2:OK]
> Mar 25 17:55:47.48: [20939]: <-- [7:AT+FDT\r]
> Mar 25 17:55:47.98: [20939]: --> [22:+FDCS: 1,5,0,2,0,2,0,0]
> Mar 25 17:55:48.20: [20939]: --> [7:CONNECT]


You'll see that the *only* variation is that the first log has this:

Mar 25 17:21:27.68: [16944]: <-- [7:AT+FDT\r]
Mar 25 17:21:39.70: [16944]: --> [22:+FDCS: 1,3,0,2,0,2,0,0]
Mar 25 17:21:39.91: [16944]: --> [7:CONNECT]

While the last log has this:

Mar 25 17:55:47.48: [20939]: <-- [7:AT+FDT\r]
Mar 25 17:55:47.98: [20939]: --> [22:+FDCS: 1,5,0,2,0,2,0,0]
Mar 25 17:55:48.20: [20939]: --> [7:CONNECT]

It's obvious that the first is using V.29 and the latter is V.34 because 
of the amount of time that elapses between AT+FDT and the response.  
However, from what I can see HylaFAX (and your 'sendfax -3') did nothing 
to provoke this.

If the receiver in both cases here is the same, and if it supported V.34 
in each call, then there must be some variation in the underlying Diva 
behavior that is enabling V.34 in the latter but not in the former.  
Unfortunately, it's really impossible for anyone to make clear sense of 
these things from the tty when working with the Diva Servers... you've 
got to go to the Diva's stuff to do that.

Lee.


____________________ 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*