Re: [hylafax-users] Patton 2977 timeout in class 1

[Lee Howard <faxguy@xxxxxxxxxxxxxxxx>]

Christian M. Watts wrote:

> 2. Lee's patch fixed many of the problem destinations, but not a 
> particular one
> that I'm concerned with.


Did you have to change FaxT4Timer at all to get these to work?  My use 
of FaxT4Timer here was somewhat arbitrary... I used it so that you could 
adjust it, if needed for testing, but if in production use that timeout 
needs to be adjusted, then we'll need to use some setting other than 
FaxT4Timer.

We corresponded privately about the one particular destination, and I 
felt like I did an adequate job of figuring out what the problem was 
with that destination and I presented you with a workaround that worked 
for me when faxing from a Patton 2977.  Did the ModemDialCmd adjustment 
not help at all in your tests?

> A remaining free-for-all question:
>
> Is there a way to use Class 2.0 on a per-destination basis? This seems 
> like it
> might be the quickest path to getting things where I'd like them to be 
> if it's
> possible to do it.


Yes.  You basically merge all of the items from your Class 1 config with 
your Class 2.0 config, and where there are collisions you use the Class 
1 setting over the Class 2.0 setting (like ModemType).  Then, you use 
DestControls to set those collision items to the Class 2.0 value when 
sending to that destination.

If the ModemDialCmd workaround (which also uses DestControls) works, 
then I would suspect that it would be much easier than this.

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*