Re: [hylafax-users] ModemWaitTimeCmd is not working

[Lee Howard <faxguy@xxxxxxxxxxxxxxxx>]

Tomas Novosad wrote:
> Oct 08 14:34:12.11: [22427]: <-- [9:ATS7=120\r]
> Oct 08 14:34:12.11: [22427]: --> [2:OK]
> Oct 08 14:34:12.11: [22427]: <-- [6:ATS7?\r]
> Oct 08 14:34:12.11: [22427]: --> [6:R07=78]
> Oct 08 14:34:12.11: [22427]: --> [2:OK]
> Oct 08 14:34:12.11: [22427]: <-- [14:ATDT737309887\r]
> Oct 08 14:35:36.28: [22427]: --> [10:NO CARRIER]

Firstly, it appears that the modem (Eicon Diva Server) did not accept 
120 s as the S7 register, but instead made it be 78 s.  And, yet, it 
provided the NO CARRIER response a mere 24 s into the call.

It's possible that, being on a digital interface, that the modem knows 
that the call was disconnected or hung up or reached a non-answering 
number... and thus there may be no point in it waiting longer before 
terminating the dial command with NO CARRIER.

However, you'll need to consult Eicon to know for sure what's going on here.

Thanks,

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*