|
Hylafax Mailing List Archives
|
[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
Re: Hylafax troubles
On Tue, Mar 23, 1999 at 05:17:00PM +0800, Greg Roberts wrote:
> I'm using a NetComm SmartModem M34F, which support Class 1,2. I'm running
> it in Class 2 mode. I've got the server/session tracing happening, and
> from the logs I can see that the various AT commands are passed to the
> modem, but the job is never sent.
Sorry to be giving the stock answer and all, but do you have any other
faxmodem to try substituting for the modem you're using?
> The reason, no answer from remote, even
> though I've got S8=120, it doesn't matter. That's if the job gets that
> far. Lately I'm getting "the modem appears to be wedged", even if I've
> just turned the modem on, or reset it manually myself.
When you get that reply, what do you _hear_? Is it in fact _getting_
an answer? Is it connecting?
> The last problem is
> that faxstat -v never returns modem ready. I've tried this with a Class 1
> modem as well as the Class 2 modem, but I never get "Modem is ready",
> unless you edit the status file and change what is says (which is probably
> not a good thing).
:-) Yeah. Faxstat will only say "ok" if faxgetty is telling it to.
> I've tried the faxmodem/faxstate combo, but that does
> nothing. The syntax for these two is:
>
> faxmodem '(0,1),(0-5),(0),(0-2),(0,1),(0),(0),(0-7)' cua1
> faxstate -s ready -n cua1
It's _really_ a good idea to use faxgetty, even if you're not going to
have the modem answer. If you aren't then (TTBOMK) faxstat will
_never_ say "Ready".
> The last couple of lines of the job log are these:
>
> Mar 23 17:12:42.07: [32033]: --> [2:OK]
> Mar 23 17:12:42.08: [32033]: <-- [15:ATDT0XXXXXXX@\r]
> Mar 23 17:12:57.13: [32033]: --> [7:RINGING]
> Mar 23 17:12:58.21: [32033]: --> [9:NO ANSWER]
> Mar 23 17:12:58.22: [32033]: <-- [5:ATH0\r]
> Mar 23 17:12:59.43: [32033]: --> [2:OK]
> Mar 23 17:12:59.43: [32033]: MODEM set DTR OFF
> Mar 23 17:12:59.44: [32033]: SESSION END
>
> The 0 after ATDT is intentional. These three problems are common to both
> types of modems I'm using, but I've been working with this for too long,
> and if this doesn't get resolved soon, Hylafax is going to be removed.
Well, it certainly sounds as if your modem isn't admitting to hearing a
connection from the other end. This is almost certainly not HylaFax's
problem, though I admit I'm not certain where it _is_ coming from.
Only just now looked at your address. I know this is a stupid
question, but your modems are expecting Aussie tones, right?
Cheers,
-- jra
--
Jay R. Ashworth jra@baylink.com
Member of the Technical Staff Buy copies of The New Hackers Dictionary.
The Suncoast Freenet Give them to all your friends.
Tampa Bay, Florida http://www.ccil.org/jargon/ +1 813 790 7592
