![]() |
On Mon, 26 Feb 2001 20:09:41 +0100, you wrote: >lut 26 19:35:53.86: [29356]: RECV send RTN (retrain negative) >lut 26 19:35:53.86: [29356]: <-- [7:AT+FDR\r] >lut 26 19:35:57.08: [29356]: --> [8:+FHNG:72] >lut 26 19:35:57.08: [29356]: REMOTE HANGUP: COMREC error (code 72) >lut 26 19:35:57.08: [29356]: RECV FAX (00000006): recvq/fax00002.tif from <UNSPECIFIED>, route >to <unspecified>, 0 pages in 0:37 >lut 26 19:35:57.08: [29356]: RECV FAX: COMREC error >lut 26 19:35:57.08: [29356]: RECV FAX (00000006): session with <UNSPECIFIED> terminated >abnormally: COMREC error >lut 26 19:35:57.08: [29356]: RECV FAX: bin/faxrcvd "recvq/fax00002.tif" "cua1" "00000006" >"COMREC error" >--- >I mean, I could understand if this was physical device that protests >against such parameters but why should software care?! I don't understand what you mean. HylaFAX did not receive the fax ok, so it asked the remote end to resend it, but the remote end closed the call following the convention not to honor RTN requests. So the fax was not received (or at least HylaFAX did not judge the received stuff good enough) and HylaFAX called faxrcvd with the error it got. The only weird thing is the filename in the faxrcvd invocation, as no file exists with that name. If you increase the log level (in config.<devid>) you'll see why HylaFAX did not accept the fax. -- giulioo@pobox.com ____________________ HylaFAX(tm) Users Mailing List _______________________ To unsub: mail -s unsubscribe hylafax-users-request@hylafax.org < /dev/null