![]() |
> Aug 10 01:37:48.19: [ 2683]: SENT 28148 bytes of data > Aug 10 01:37:48.19: [ 2683]: <-- data [2] > Aug 10 01:37:48.37: [ 2683]: SEND end page > Aug 10 01:37:49.22: [ 2683]: --> [2:OK] > Aug 10 01:37:49.22: [ 2683]: SEND send EOP (no more pages or documents) > Aug 10 01:37:49.22: [ 2683]: <-- [9:AT+FET=2\r] > Aug 10 01:37:59.56: [ 2683]: --> [9:+FHNG: 54] > Aug 10 01:37:59.56: [ 2683]: REMOTE HANGUP: No response to EOP repeated 3 > times (code 54) This has been a long standing problem, of course. Unfortunately, it results in many copies of the fax being sent, since Hylafax thinks that there's been an error during transmission (which there has been - the receiving end isn't following the Class 2 protocol, and is hanging up the phone before the session is over). I suggest that the code be changed so that if all pages have been successfully transmitted, that +FHNG be a "success" response to AT+FET=2. What does everyone think about this as a proposed solution? ____________________ 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@hylafax.org < /dev/null *To learn about commercial HylaFAX(tm) support, mail sales@hylafax.org.*