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

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

I applied the patch and rebuilt hylafax. It was effective in increasing the
timeout to whatever I set FaxT2Timer to (or 7 seconds by default if unset).
This seemed to help with some receivers who were taking a little more than 5
seconds to return, but did not fix my particular problem receiver. In class
2.0, I see them connect in at most 8 seconds, and even waiting 12 seconds on
the class 1 side didn't get it there (though I did see a full 12 second delay
before timeout). At this point, I'm wondering if they're sending something
squirrely back in the response that the Class 1 software doesn't like ...

Is there a way to turn SessionTracing up (and what would I set it to) in order
to get more detail in the log that might help us see the HDLC frames or
whatever is going back and forth?

Thanks,
Christian

Quoting "Christian M. Watts" <cmwatts@xxxxxxxxxxxxx>:

> Thanks, Lee. I'll try that and report results back.
>
> Christian
>
> Quoting Lee Howard <faxguy@xxxxxxxxxxxxxxxx>:
>
> > Christian M. Watts wrote:
> >
> > > I'm having an issue with the following configuration:
> > >
> > > Gentoo Linux - kernel 2.4.30
> > > Patton 2977 (AKA Digi Datafire RAS) - latest firmware from Patton support
> > > Hylafax 4.2.5
> >
> > Your modem config looks fine.  The only thing that I would suggest 
> > in addition is:
> >
> >  Class1RMPersistence: 0
> >
> > But that will have no effect upon the matter you write about.
> >
> > > Mar 14 12:13:04.41: [31914]: <-- [16:ATDT1XXXXXXXXXX\r]
> > > Mar 14 12:13:22.05: [31914]: --> [7:CONNECT]
> > > Mar 14 12:13:27.05: [31914]: <-- data [1]
> > > Mar 14 12:13:27.25: [31914]: MODEM <Timeout>
> > > Mar 14 12:13:27.25: [31914]: DELAY 200 ms
> > > Mar 14 12:13:27.45: [31914]: <-- [9:AT+FRH=3\r]
> > > Mar 14 12:13:27.61: [31914]: --> [5:ERROR]
> >
> > The time between the CONNECT and the "<-- data [1]" (timeout) is not 
> > configurable.  Can you try the attached patch?  It changes the fixed 
> > 5-second timeout there to be FaxT2Timer, which defaults to 7 seconds.
> >
> > Basically the modem is supposed to report CONNECT when the V.21 HDLC 
> > carrier is detected and then report OK when the HDLC frame is 
> > received correctly, or ERROR if the HDLC frame is received 
> > incorrectly.  I believe that there is a T.30 time limit of 5 seconds 
> > involved here, and that's why the 5-second timeout there exists... 
> > but I can easily see how this could be too short.  A 2-second 
> > increase here is really a lot.
> >
> > Thanks,
> >
> > 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*