[hylafax-users] FaxSend failures: "No answer" returned too soon

[Marc Mims <marc@xxxxxxxxxxxxxx>]

I'm trying to resolve a problem where the modem appears to be incorrectly
detecting a "No answer" condition.

We're using a 4-port Mainpine modem. ATI0 returns:
Mainpine Venus V.92 I03.04.02 (0026SD) Voice V2 V92cap 12ns RAM Mercury

Failing outbound faxes sometimes succeed when retried, and i suspect they
would always succeed on retry if the retry count was set high enough (but
that's not a reasonable solution).

Below are leading portions of two logs for a failure and success on retry.
I have elided the email addresses and changed the fax number to protect the
innocent. :-)

In the failure case, note the short time span between issuing the dial
string and the "No answer" response.  In this case, it is approximately 14
seconds.  It seems to range between 8 and 14 seconds.

  ==> c000091438 <==
  Jan 31 17:11:34.35: [29318]: SESSION BEGIN 000091438 18005551212
  Jan 31 17:11:34.35: [29318]: HylaFAX (tm) Version 4.3.1
  Jan 31 17:11:34.35: [29318]: SEND FAX: JOB 59772 DEST 18005551212 COMMID 000091438 DEVICE '/dev/ttyF4' FROM '<elided>' USER postman
  Jan 31 17:11:34.35: [29318]: <-- [12:AT+FCLASS=1\r]
  Jan 31 17:11:34.36: [29318]: --> [2:OK]
  Jan 31 17:11:34.36: [29318]: DIAL 9W,18005551212
  Jan 31 17:11:34.36: [29318]: <-- [22:ATX4DT9W,18005551212@\r]
  Jan 31 17:11:48.70: [29318]: --> [9:NO ANSWER]
  Jan 31 17:11:48.70: [29318]: SEND FAILED: JOB 59772 DEST 18005551212 ERR No answer from remote
  Jan 31 17:11:48.70: [29318]: <-- [5:ATH0\r]
  Jan 31 17:11:48.75: [29318]: --> [2:OK]

  ==> c000091441 <==
  Jan 31 17:16:59.34: [29323]: SESSION BEGIN 000091441 18005551212
  Jan 31 17:16:59.34: [29323]: HylaFAX (tm) Version 4.3.1
  Jan 31 17:16:59.34: [29323]: SEND FAX: JOB 59772 DEST 18005551212 COMMID 000091441 DEVICE '/dev/ttyF3' FROM '<elided>' USER postman
  Jan 31 17:16:59.34: [29323]: <-- [12:AT+FCLASS=1\r]
  Jan 31 17:16:59.34: [29323]: --> [2:OK]
  Jan 31 17:16:59.35: [29323]: DIAL 9W,18005551212
  Jan 31 17:16:59.35: [29323]: <-- [22:ATX4DT9W,18005551212@\r]
  Jan 31 17:17:33.57: [29323]: --> [7:CONNECT]
  Jan 31 17:17:35.08: [29323]: --> HDLC<16:FF C0 04 00 00 6A AA AA 00 31 09 01 E5 B8 95 A0>
  Jan 31 17:17:35.08: [29323]: --> [2:OK]
  Jan 31 17:17:35.08: [29323]: REMOTE NSF "00 00 56 55 55 00 8C 90 80 A7 1D"


Some notes on the dial string:
- The comma is superfluous.  I added it to test the theory that dialing too
  soon after getting an outside line dial tone might result in the bogus
  "No answer" return.  It simply added 2 seconds to the time span between
  issuing the dial command and receiving the "No answer" response.

- Without the trailing @, I get "No carrier" with the same, short time span
  between dial and response.


Any assistance appreciated.

	-Marc


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