![]() |
Firstly let me point out that I *strongly* doubt that the Diva Server will allow you to disable copy-quality checking on the modem. Thus, "Copy quality checking performed by host" is not accurate and could get you into trouble if ever the modem says RTN but HylaFAX CQ does not.
If you didn't read the README that comes with 4.2.0, then you missed this part:
* Due to tighter adherance to the Class 2 specifications, HylaFAX copy-
quality checking now operates slightly different in Class 2/2.0/2.1 than
in previous versions. This change will not effect users of most modems,
but users of the Eicon Diva Server will probably need to add
"Class2ECMType: 2.0" to their respective modem config files.
If you haven't, then I recommend that you do this. If you have, then we have a problem still with the codebase.
Jun 09 13:21:08.84: [ 1023]: <-- [7:AT+FDR\r]
Jun 09 13:21:08.94: [ 1023]: --> [7:CONNECT]
Jun 09 13:21:08.94: [ 1023]: RECV: begin page
Jun 09 13:21:08.94: [ 1023]: RECV: send trigger 021
Jun 09 13:21:08.94: [ 1023]: Copy quality checking performed by host
Jun 09 13:21:31.82: [ 1023]: RECV: 0 total lines, 0 bad lines, 0 consecutive bad lines
And what this probably means is that the remote did not want to retrain and resend the page, and so it hung up. The error message would be accurate, then, and if there is any fix to be made for any reproducible problems, it would have to be done by Eicon.
____________________ 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*