HylaFAX The world's most advanced open source fax server

[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: [hylafax-users] COMREC error



On 2005.03.01 08:33 hkbyte wrote:

Mar 02 00:00:18.97: [14524]: HylaFAX (tm) Version 4.1.7

Mar 02 00:00:34.48: [14524]: MODEM input buffering enabled
Mar 02 00:00:34.48: [14524]: <-- [11:AT+FRM=146\r]
Mar 02 00:00:37.63: [14524]: --> [8:+FCERROR]
Mar 02 00:00:37.63: [14524]: MODEM input buffering disabled
Mar 02 00:00:37.63: [14524]: <-- [9:AT+FRH=3\r]
Mar 02 00:00:37.97: [14524]: --> [7:CONNECT]
Mar 02 00:00:38.17: [14524]: --> HDLC<5:FF C8 F4 CC 66>
Mar 02 00:00:38.17: [14524]: --> [2:OK]
Mar 02 00:00:38.17: [14524]: RECV recv EOP (no more pages or documents)
Mar 02 00:00:38.17: [14524]: RECV FAX (00061503): recvq/fax57586.tif from HDA, route to <unspecified>, 0 pages in 0:13
Mar 02 00:00:38.17: [14524]: RECV FAX: COMREC invalid response received

If you upgrade to 4.2.1 you likely won't see this behavior, as +FCERROR handling was altered, I believe. So if the sender doesn't use ECM with you in 4.2.1, then I *think* that it will just repeat the AT+FRM=146 command after +FCERROR. (Which would still have caused a failure.) And if it doesn't, then it *should* handle the EOP by responding with RTN. (Whihc would probably still have caused a failure.) If it doesn't, then let us know.


However, with only 3.5 seconds total possible page transfer time, the page would have been rather small... like a 2 or 3 inch strip only.

Lee.

____________________ 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*




Project hosted by iFAX Solutions