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

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

I'll have to download the CVS version then. Only problem is I hate having to
compile new binaries over installed packages and messing up the rpm database.
When is the next rpm binary release scheduled for hylafax that has these new
features/fixes?

Thanks for the quick response and helpful info,
-Jeremy


-----Original Message-----
From: hylafax-users-bounce@hylafax.org
[mailto:hylafax-users-bounce@hylafax.org]On Behalf Of Lee Howard
Sent: Thursday, May 31, 2001 4:44 PM
To: Jeremy Fowler; hylafax-users@hylafax.org
Subject: Re: [hylafax-users] Best PCI Modem to use with Hylafax


At 04:29 PM 5/31/01 -0500, Jeremy Fowler wrote:
>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?

USR/3Com 3CP5610(A)  - you're using this I believe, still suffers from
buggy Class 2.0 firmware

Lucent Tech Winmodem - using the linux kernel module, Class 1 only, works
well, but I fear that the module isn't completely stable

MultiTech MT5634ZPX-PCI - I'm testing one now, works great in Class 1, but
I haven't gotten Class 2 to work... yet.

There are others, but I haven't tried them.

>Could the fact that we are using PCI modems that share IRQs have anything
to do
>with wedged modems errors?

Yes.  faxgetty is so intensive that you could have problems sharing IRQs, I
suspect.  But... with this particular modem (I'm quite familiar with it)
there are issues with the reset.  Current CVS has these fixes.
(ModemDTRDropDelay)

> 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.

Yes, initially this starts as a "cannot setup modem" problem, then after a
few tries, it calls it "wedged".  It happens all the time with 3CP5610 modems.

>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.

This is a USR thing, and not a 3CP5610 thing.  USR's Class 2.0 firmware has
timing issues, and I've found that some senders can't even CONNECT to it in
Class 2.0, however, I've found the exact opposite, too.

> 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.

You are right, and this fix is in current CVS, too.  (Was committed at the
same time as the ModemDTRDropDelay.)

Lee.



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



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