Christian M. Watts wrote:
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?
The modem is not going to give us any more information.
The Patton driver could, but I don't know how to analyze that data...
you'd have to pass it on to Patton... and I'm not quite sure how far
that would get you.
If you can give me the problematic numbers in a private e-mail I can
place some calls and see exactly what's going on by listening to the
actual call.
It's possible that the Patton is reporting CONNECT at this moment
prematurely, although I don't have these problems on my Patton. Do
your ATI commands report the following? (use probemodem or minicom
to test):
ATI0: Digi RAS modem 56000
ATI1: 255
ATI2: OK
ATI3: V20040915-K56_DS
ATI4: PATTON56K_RAS
ATI5: 022
ATI6: 3.29K1/5.71B
ATI7: 000
ATI8: ERROR
ATI9: (1.00DBI0052\00000000\MODEM\\DataFire RAS 24 PT1__)
You said that you're using the latest firmware, but last time I
checked their latest fax firmware was not to be found on their
web/ftp site. You had to call them and get them to send it to you.
Certainly the firmware in padm-1.20-1.tar.gz is not the latest.
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*