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

["Christian M. Watts" <cmwatts@xxxxxxxxxxxxx>]

Resolution! For those interested:

Lee was able to diagnose the problem as some echo on the destination that was
causing it not to properly detect tones at the beginning of the call. The
solution presented was to use destctrls and either set ModemDialCmd to ATDT%s@
for that destination or to merge my Class 1 and Class 2.0 configs and use
destctrls to set ModemType to Class2.0 for the destination.

The ATDT%s@ didn't seem to work out in this particular instance, but setting
ModemType to Class2.0 does function as Lee describes below and gives me a
working solution that doesn't involve running my Modems in Class 2.0 all the
time.

Thanks again, Lee. Your dedication to the Hylafax platform is certainly one of
the key ingredients in why it works so well.

Christian


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

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