Re: [hylafax-users] CAPI4HylaFax

[Lee Howard <faxguy@deanox.com>]

On 2002.03.11 14:52 Chris Parsons wrote:
> To sum up my two posts, CAPI4HylaFax and CVS version of SendFax Broken?:
> 
> 
> I'm running an eicon card on RHLinux 7.0 with kernal version 2.2.16-22
> With
> HylaFax 4.1.1. I'm using the Divas for Linux Server Drivers version 1.0
> Build 102-393 with a Diva Server 4BRI card.
> The Card Worked Well for faxing under nt however had problems with faxes.
> So
> we decided to switch to HylaFax.
> 
> The original install used the ttyds0X ports provided by the Eicon driver.
> Using Class 2 mode it would not negotiate properly with various fax
> machines. In class 1 mode it appeared to work alright but come full
> production scale many faxes failed with the MPS / EOP error thats been
> documented many times in the archive of this list. I follow the solution
> I
> found to download the CVS version and compile. From then on the error was
> "
> send program terminated abnormally with error 0x06. The archives werent
> too
> helpfull in this case. It was suggested to set logging to max, they
> already
> are and produce nothing of note to help the situation.
> 
> I decided at this point to switch to the CAPI4HylaFax. However
> documentation
> is very limited and after getting one line to work, any attempt to get
> more
> than that caused the  Connection dropped with Reason 0x2002 (Illegal
> Controller / PLCI / NCCI.) Looking through the sources for capi4hylafax
> did
> not help as it appears to be when it looks for the ISDN channel. I could
> even replicate this error with only one line installed.
> 
> 
> Any Ideas? Which way should I go?

I assume that there are no Session logs generated before these failures 
occur. (?)

What I say now I say based on other experience, but not experience with 
CAPI, ISDN, or Eicon hardware...

I would recommend that you do not use CAPI4HylaFax.  I tend to believe 
that it won't work with the new changes in 4.1.1, anyway, plus I hope that 
HylaFAX Class 1 protocol is better than that of CAPI4HylaFax.  If 
everything was working in 4.1 with the Eicon driver but not in 4.1.1 
(minus the MPS/EOP problems), then I recommend that you revert to 4.1 
source, and begin applying 4.1.1 patches to the source from Bugzilla until 
you find the culprit patch that messed things up for the Eicon driver.

However, your problems seem bizarre in that so many of us are and have 
been using 4.1.1 (or equivalent) for so long now without any problems, and 
I suspect that Eicon hardware users are among us.

Before you go through the effort of doing when I indicated above, I would 
recommend that you completely remove all HylaFAX source and binaries from 
your system and then recompile and reinstall from new 4.1.1 (or CVS) 
source... that is, unless you're absolutely certain that all your binaries 
are matching versions and that there was no error in compilation or 
installation lately.

Frankly, however, the only significant alterations to Class 1 protocol 
between 4.1 and 4.1.1 which really targetted MPS/EOP errors were 
Class1SendMsgDelay and Class1*WaitCmd.
http://bugs.hylafax.org/bugzilla/show_bug.cgi?id=185
http://bugs.hylafax.org/bugzilla/show_bug.cgi?id=197
These patches may not apply to 4.1 source cleanly.

Lee.

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