![]() |
> My problem is that whenever I try to setup a send-only environment for > exporting orders to our clients I get errors where after sending a fax > the modem never comes back to the 'running and idle' state. An > example of the problem is this: I'll install HylaFax, setup the modem > and everything, have it run faxmodem on each modem, and then send a > fax. The fax will go through perfectly, but afterwards, in faxstat, > the modem is always in a "Waiting for modem to come ready" state. All > subsequent attempts to fax will just sit in the queue while the modem > is in this state. When I was using a send-only mode, it was normal that I got 'Waiting for modem to come ready'. In the documentation it notes that using faxmodem does not necessarily give you as good at status as using faxgetty. However, even though the status was showing incorrectly, I had no trouble sending out additional faxes. Now I am using faxgetty instead of faxmodem, and I would highly suggest it even if you do not want to use reception. If not, you can just set RingsBeforeAnswer: 0 This will ensure faxgetty will not answer the line. However, faxgetty appears to be much better at monitoring the current state of the modem, again confirmed in the documentation. For sanity, try using faxgetty and see if things clear up. At least you will have appropriate data as to what is going on. You can also monitor your logs better. Sunil ____________________ 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@hylafax.org < /dev/null *To learn about commercial HylaFAX(tm) support, mail sales@hylafax.org.*