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] Error parsing "+FTM"
On 2004.07.28 15:55 "Roper, Brent" wrote:
Here is the error log I noticed this time it is an "+FRM" error but I
am
getting both frequently but I have now noticed it does not always lock
up
the modem.
Jul 28 14:00:06 APS-Hustn-FxSvr FaxGetty[15461]: <-- [8:ATS7=60\r]
Jul 28 14:00:06 APS-Hustn-FxSvr FaxGetty[15461]: --> [4:RING]
Jul 28 14:00:06 APS-Hustn-FxSvr FaxGetty[15461]: MODEM Ring
Jul 28 14:00:07 APS-Hustn-FxSvr FaxGetty[15461]: --> [2:OK]
Jul 28 14:00:09 APS-Hustn-FxSvr FaxGetty[15461]: <-- [9:AT+FRM=?\r]
Jul 28 14:00:39 APS-Hustn-FxSvr FaxGetty[15461]: MODEM TIMEOUT:
reading line from modem
Jul 28 14:00:39 APS-Hustn-FxSvr FaxGetty[15461]: Error parsing "+FRM"
query response: "OK"
You seemed to be getting a call coming in at the same time as the modem
was initializing. Search the archives and Bugzilla for "glare" (posts
from me, in particular) for some ideas on how to reduce the likelihood
of it occurring.
That said, with analog modems you cannot completely eliminate it from
occurring. With HylaFAX 4.2.0 we do as much as possible to handle
instances of glare. Notice that the RING following ATS7=60 did not
bother us. However, it's possible that the incoming RING bothered the
*modem*, and has thus caused it do behave as it has with the AT+FRM=?
response.
If this only affects the AT+FRM=? and AT+FTM=? command responses, you
could simply do without those commands by setting in your modem config
file:
Class1TMQueryCmd: "!3,24,48,72,73,74,96,97,98,121,122,145,146"
Class1RMQueryCmd: "!3,24,48,72,73,74,96,97,98,121,122,145,146"
This will prevent HylaFAX from querying the modem for this information,
and thus eliminates the need for a response to the command.
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*