Re: [hylafax-users] CAPI4HylaFax

["Bernd Proissl" <lists@proissl.de>]

> I rebuilt my version of Hylafax from CVS because I was getting massive MPS,
> EOP problems to certain machines. However that broke the fax sending
> completely. I reinstalled and Install CAPI4HylaFax because I have an eicon 4
> Bri card. Most of the time it works how ever every so often the log reports
> something similar to the below.
> 
> What would cause this problem???:
> 
...
> Mar 11 12:34:19.93: [ 3937]: Connection dropped with Reason 0x2002 (Illegal
> Controller / PLCI / NCCI).

But there is no MPS, EOP, etc in this logs.

I do not know the Bri detalis but with avm CAPI hylafax's faxsend is completely
replaced with avm's version and this versions lets CAPI do all the fax
protocoll work. It is not integrated in hylafax log framework either.

If this is true for Bri also it would not help you to build hylafax from cvs.
Look at the readme from capi4hylafax, try to send a fax without hylafax (to
your problematic destination if there is one)

Bernd


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