![]() |
At 04:14 PM 5/25/01 -0400, Jim TheVoice wrote: >I use HylaFAX, Version 4.1 (beta 3) on a Solaris 8 machine with a MultiTech > MT1932ZDX on the /dev/ttyb port. It's a send only machine. > > Look at the results of the following commands and files contents. > ***************************************************************** > # faxstat > HylaFAX scheduler on infog2: Running > Modem ttyb (+1.418.851.9976): Waiting for modem to come ready > > ***************************************************************** > from mail: > The HylaFAX software thinks that there is a problem with the modem > on device /dev/ttyb that needs attention; repeated attempts to > initialize the modem have failed. > ? > > Consult the server trace logs for more information on what is happening. > > ***************************************************************** > /var/adm/message: > [...] > May 25 14:17:49 infog2 FaxQueuer[513]: [ID 793248 daemon.error] MODEM > /dev/ttyb appears to be wedged > ServerTracing: 1 > SessionTracing: 11 You can find out why if you turn your ServerTracing up to 0xFFF, restart faxgetty, and then analyze your syslog. Lee. ____________________ HylaFAX(tm) Users Mailing List _______________________ To unsub: mail -s unsubscribe hylafax-users-request@hylafax.org < /dev/null