|HylaFAX The world's most advanced open source fax server|
On 2005.02.16 09:35 Mike McMullen wrote:
I have noticed that right before the wedging occurs, a fax was received
that failed with the following message:
Received premature V.34 termination.
I'm also seeing as I posted yesterday:
"Failed to properly detect hight-speed data carrier"
And sometimes the modem wedges after that.
I've attached the config file for one of the modems. Wedging errors appear with equal frequency on either modem.
I can supply logs if someone thinks that would help.
Any insight appreciated!
The thing to do would be to see if the modem really is wedged. So when the modem wedges, without power-cycling the modem or otherwise changing things, run 'minicom -o' on it and see if you can get it to respond after a few ATZs or something. If that doesn't work, then maybe let minicom initialize it (by omitting the -o). If you can get it to respond, then HylaFAX needs some improvement with the "reset" routine. If you can't, then the modem really is hung, and it's likely a firmware issue that MultiTech will need to examine.
The session log that causes the modem to hang/wedge would be useful in assisting you.
One of the modems wedged this morning and per your suggestion, I turned off the faxgetty on the modem and removed it from hylafax and ran minicom on it. Using the speed in the conf.modem file of 56K I was unable to get any response at all from the modem.
An incoming fax attempt failed about 5 times before the modem wedged. After the last failed attempt it appears the modem wedged. I've attached the com log if that can provide any help.
Description: Binary data