[hylafax-users] Best PCI Modem to use with Hylafax

["Jeremy Fowler" <jfowler@westrope.com>]

I read in many discussions about which modems people find that work the best
with Hylafax, however; most of them are ISA based. What kinds of PCI modems have
people used with the least amount of problems?

Could the fact that we are using PCI modems that share IRQs have anything to do
with wedged modems errors? Occasionally when faxgetty first initializes a modem,
it comes back wedged. It will eventually come ready after a few tries. It mainly
happens to ttyS3 and ttyS5; however I have seen this error on all of the devices
before.

We're running Hylafax 4.1beta3-1rh7 (rpm) on a Redhat 7.1 box with 4 internal
PCI USR 56K Performance Pro modems in a receive-only environment. We had a lot
of problems with people calling us about not being able to send to us when the
modems were configured to use class 2.0, after switching to class 1 (rts) we had
less problems. However, with class 1, occasionally faxgetty gets stuck receiving
a fax and just sits there. Faxstat shows "Receiving From <insert number here>"
and there is no activity in the logs. Faxgetty should have some kind of timeout
where after a fax in answered and communication begins, if there is no activity
on the modem faxgetty should then automatically reset itself. It's pretty bad
when all four lines are being taken up and no faxes are being received until I
do a killall faxgetty. As a work around I have an hourly script that runs
killall for me, however this is a poor solution since regular faxes will be
terminated that happen to be transmitting at the time cron runs the script. I'm
going to try to write a script that runs hourly that will get the file
timestamps from /var/spool/fax/status/ttySx and if the file is larger than 17
bytes and if its over a certain amount time kill the faxgetty process on that
device. This would work most of the time, but large faxes that are being
received normally might possibly be disconnected. I suppose before I kill the
process I could scan the log file and get the timestamp from the last entry from
that particular faxgetty process. If there hasn't been any entries for like
10-15 mins, kill that proc ID. However, that's involves a lot of data parsing...
A lot of work. Still, it would be nice if there were a command line switch for
faxgetty to run from inittab to tell it to reset after so many minutes of
inactivity after a fax connection.

Well, there you have it.
Thanks for listening,
-Jeremy



____________________ HylaFAX(tm) Users Mailing List _______________________
 To unsub: mail -s unsubscribe hylafax-users-request@hylafax.org < /dev/null