Re: [hylafax-users] Anyone had success with HylaFAX and ZyXel Omni 56K modem?

["Miles K. Forrest" <mforrest@promicro.com>]

>
>
>On Thu, Nov 08, 2001 at 12:21:13PM -0800, Miles K. Forrest wrote:
>
>>Thanks so much for your fast response!
>>
>
>See?  I told you we had support.
>
>>>>I'm having a terrible time getting HylaFAX to work properly.  I'm using 
>>>>Mandrake 8.0 with version hylafax-server-4.1-0.11 (rpm install) with a 
>>>>
>>>I suspect that's supposed to be "4.1.0-11"; if it's not, perhaps the
>>>RPM builder needs to fix his numbering.
>>>
>>>It would be productive to make certain that the person building RPM's
>>>for Mandrake is actually using the production release... now that we
>>>finally have one.  ;-)
>>>
>>It probably is the wrong name, however I pasted it from a rpm -qa|grep 
>>hylafax query, so that seems to be the package number (I like your 
>>attention to detail - things like that drive me nuts.  My wife is just 
>>as bad - she can't handle spellin' errurs!)
>>
>
>Indeed.  Alas, we're not that good about propagating release numbers
>into the log messages, which I think is being worked on.
>
>>>I can't say for sure, but this feels like a flow control problem to me.
>>>Normally, though, those will mess up *all* your calls.
>>>
>>>Is it a *specific* set of fax machines that fail repeatably?  Or, to
>>>put it another way, how wide is the universe of sending fax machines.
>>>No fax device is 100.0% perfect, even dedicated fax machines
>>>occasionally can't talk to one another; it's possible that you've just
>>>hit the jackpot, if the sender group is small (say, 10 or less).
>>>
>>I think it's particular fax machines that fail consistently.
>>
>
>Hmmm... it might be productive to try widening the universe, just as a
>test.  remind the client that they're *not* paying $5000 for a
>commercial package, they can afford to spend a little money on
>tuning...
>
>>>Oh, are you running in class 1?  :-)
>>>
>
>>No, I tried Class 1 but the received faxes were not readable. Somehow 
>>the TIF file was mangled. I didn't expend a lot of effort because the 
>>documentation seemed to infer that Class 2.0 is the better choice.  Why 
>>is Class 1 better?  I read somewhere because it relies more heavily on 
>>HylaFAX to handle the sessions.  Z'hat true?
>>
>
>The doco is no longer accurate, to the extent it suggests that.
>
>Yes; the class 1 code is now *much* better than the average class 2
>code in people's modems.
>
>*Now* I think the problem is flow control, since that will *totally*
>mangle class 1, which only causing intermittent hassles to class 2.
>
>>>>how can this be fixed?  Is the HylaFAX project active, or should I be 
>>>>looking somewhere else for a fax solution?  I'm sure that this is a 
>>>>problem that can be solved with this modem since other people have had 
>>>>great success with the Zyxel modems.
>>>>
>>>You bet we're active.  Not as much as we'd like to be, honestly; good
>>>C++ and fax programmers ain't easy to come by... why do you think
>>>RightFAX is up in 5 digits?  :-)
>>>
>>5 digits?  Y'mean RightFAX costs over $10,000?  Whoah. This customer of 
>>mine who's using it replaced WinFAX which is absolutely unreliable over 
>>any length of time.  If I can get HylaFAX to work reliably, I'd love to 
>>gain more customers and convert them to Linux.
>>
>
>It is my understanding that the commercial packages, expandable to the
>extent that HylaFAX is, range from $1500 up into the 5 digit range,
>yes.
>
>>Thanks again Jay,
>>
>
>No problem.  Try to keep replies on list; the archives are more useful
>that way.
>
Will do.   I'll also switch to Class 1 and dig around the flow control 
settings and see if it works. I'll post my results (fingers crossed).

Miles



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