Re: [hylafax-users] class1 modem and modem capabilities

[Giulio Orsero <giulioo@pobox.com>]

On Fri, 13 Jul 2001 23:56:52 -0600, you wrote:

>>1) Why 'Supports "Class 2' ?? This is just a curiosity since the modem is
>As you're aware, it's not terribly bad, but it is erronious output.
ok
>>2) Why not 2-D MMR too? I think I'd save on connection time.
>Again, faxgetty is misinterpreting the DCC response somewhere near here:

>    traceBits(modemParams.df, Class2Params::dataFormatNames);
>However, I highly suspect that HylaFAX is still utilizing 2-D MMR
>whenever/if possible.  This here is merely a listing, and not a setting.
>
>Can you list your DCC response? (AT+FDCC=?)  Does this even work on a Class
>1 modem, though?
>Maybe it's AT+FTM=? on a Class 1 modem...
OK
at+fdcc=?
ERROR
at
OK
at+ftm=?
3,24,48,72,73,74,96,97,98,121,122,145,146
 
OK

I thougth that with class1, 2d was HylaFAX resposability altogether, so that it
should not matter what the modem says.

My class1 modems attached to HylaFAX advertise 2-D MR as they maximum encoding
when receiving. 
When HylaFAX contacts a real fax machine that claims it supports 2-D MMR it
records "supports2DEncoding:yes" in info/XXX, that is the same thing it records
when the remote end says "2-D MR", so how can HylaFAX does something different
when encoding stuff?

Even if modem is class1 I've tried
Class2DCCQueryCmd:      "!(0,1),(0-5),(0-4),(0-2),(0,3),(0),(0),(0-7)"
So that 0,3 should mean 2-D MMR, but no luck.


-- 
giulioo@pobox.com


____________________ HylaFAX(tm) Users Mailing List _______________________
 To unsub: mail -s unsubscribe hylafax-users-request@hylafax.org < /dev/null