|HylaFAX The world's most advanced open source fax server|
> The default ModemPageDoneTimeout is a rather large integer (180000).
> So it is bigger than 16-bits, so it requires a 32-bit > allocation by the > compiler. It and ModemPageStartTimeout are the only default timeout > values that large. You could try setting it lower, say at 60000 (one > minute, and within a 16-bit range) to see if the size of the timeout
> value is a factor.
To check if the fault occurs more often in connection to a quicker timeout?
> I can send you code patches to add some debugging info in > there so that > we can see what's actually going on. If you can make use of them and > want to try it out, let me know.
Yes, this would be nice.
Will the patches also work on the sources shipped by SuSE?
> The catalyst to the problem, however, appears to be the lack of an > expected modem response. In Class 2.0 you'll need to consult > the modem > manufacturer for a firmware fix. So HylaFAX can fix the "stuck" > faxgetty, but the modem manufacturer must fix the modem error.
Actually the modems (ELSA Microlink 28.8 TQV) worked fine under W2k. Unfortunately ELSA meanwhile became insolvent, I don't know about available firmware fixes.
Description: Binary data