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] Fax received ok, but sender thinks it failed and resends
Chris 'Xenon' Hanson wrote:
Dec 12 16:08:34.00: [16428]: <-- [9:AT+FTH=3\r]
Dec 12 16:08:35.07: [16428]: --> [7:CONNECT]
Dec 12 16:08:35.07: [16428]: <-- data [3]
Dec 12 16:08:35.07: [16428]: <-- data [2]
Dec 12 16:08:35.39: [16428]: --> [2:OK]
Here, when sending the CFR signal the modem behaves as it should.
However...
Dec 12 16:08:55.72: [16428]: <-- [9:AT+FTH=3\r]
Dec 12 16:08:55.72: [16428]: --> [10:NO CARRIER]
Dec 12 16:08:55.72: [16428]: RECV send MCF (message confirmation)
Here, when trying to send the MCF signal, the modem confusingly responds
with "NO CARRIER" which is not a permissible response to AT+FTH=3.
Dec 12 16:09:00.07: [16428]: <-- [9:AT+FTH=3\r]
Dec 12 16:09:00.07: [16428]: --> [10:NO CARRIER]
Dec 12 16:09:00.07: [16428]: RECV send MCF (message confirmation)
And again.
Dec 12 16:09:04.49: [16428]: <-- [9:AT+FTH=3\r]
Dec 12 16:09:04.49: [16428]: --> [10:NO CARRIER]
Dec 12 16:09:04.49: [16428]: RECV send MCF (message confirmation)
And again.
The NO CARRIER response comes awfully fast (immediately). I suspect
that the NO CARRIER is already in the buffer before the AT+FTH=3 is
given. However, I'm not seeing the requisite "CONNECT" response below,
either.
So, something is wrong with the Class 1 behaviors of the modem. Unless
we learn how to work-around the matter there can be very little hope for
reliable faxing with this modem.
Thanks,
Lee.
Unless we learn how to work-around this
____________________ 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*