![]() |
The destination fax receives just fine from everyone else and the TNT is plugged into a DS-3 so it's all digital on that end so the line has got to be decent. The receiver is not saying anything. It gets the connect, says receiving fax, then drops it and goes back to displaying the time/date. I just reconfigured my modem with faxaddmodem (saving off the other config file) as a class 2 modem and it was able to negotiate a speed properly and send the fax. However, it was not able to terminate the fax properly. The attached c00011658 has a log of a fax transmission in class 2. If nothing else this might show that the line between them is good and they should be able to negotiate a connection.
This does not happen to all destinations, but it does happen to around 25% of the machines we try to fax to.
Aug 24 16:33:11.86: [11977]: <-- data [2] Aug 24 16:33:11.86: [11977]: SEND end page Aug 24 16:36:11.86: [11977]: MODEM TIMEOUT: reading line from modem Aug 24 16:36:11.86: [11977]: MODEM <Timeout> Aug 24 16:36:11.86: [11977]: <-- [6:AT+FK\r] Aug 24 16:36:41.86: [11977]: MODEM TIMEOUT: reading line from modem Aug 24 16:36:41.86: [11977]: MODEM <Timeout>
A separate issue: I just restarted faxgetty with a kill with a job in the queue and I saw this in the log:
Aug 24 16:20:59 lnx FaxSend[11006]: /dev/t/dev/ttya0: Can not open modem (No such file or directory)
I have been noticing this occasionally for weeks. I'm sure I have the device named correctly everywhere in my configs, I don't know where this mangled device path is coming from.
____________________ 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*