Package: hylafax-server Version: 2:4.3.0-1 Severity: normal Well, this might not be strictly an HF bug, might be a modem issue, but this err.msg already spurred quite a bit of conjectures in the ml and there it was said (hoped) that HF >>4.2.1 would have better handled such situations. This seems not the case, as I'm getting this in the log with 4.3.0 as before with 4.2.1, with 3 different brands of modems, all in Class 1, so I'm reporting it in case HF is really supposed to do something better that this:
cat log/c000039951 :45:33.51: [ 5394]: SESSION BEGIN 000039951 390000111111 :45:33.51: [ 5394]: HylaFAX (tm) Version 4.3.0 :45:40.95: [ 5394]: ANSWER: FAX CONNECTION DEVICE '/dev/ttyS0' :45:40.95: [ 5394]: STATE CHANGE: ANSWERING -> RECEIVING :45:53.32: [ 5394]: RECV FAX (000039951): recvq/fax000025837.tif from +39.0000.333333, route to <unspecified>, 0 pages in 0:13 :45:53 comix FaxGetty[5394]: RECV FAX (000039951): session with +39.0000.333333 terminated abnormally: Failed to properly detect high-speed data carrier. :45:53.32: [ 5394]: RECV FAX: bin/faxrcvd "recvq/fax000025837.tif" "ttyS0" "000039951" "Failed to properly detect high-speed data carrier." :45:53.32: [ 5394]: SESSION END -- paolo -- System Information Debian Release: 3.0 Kernel Version: Linux npp 2.4.26-ss-fb-lm287 #1 Fri Jul 16 21:26:09 CEST 2004 i686 unknown -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
