Re: [hylafax-users] CAPI4HylaFax

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

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

capi4hylafax does not contain fax-protocol code (AFAIK).
it comes with a special faxsend that replaces hylafax's faxsend.
This faxsend can not talk to serial devices but to CAPI-devices.
A capi driver should offer a fax-service to the client (here faxsend)
but must not.
AVM offers free capi drivers for their cards, they have a relly good
fax protocoll code (IMHO)

Eicons seems to emulate a serial device so capi4hylafax is not necessary, 
maybe it can not even be used if the eicon capi-driver does not
offer fax service.


capi4hylafax's faxsend integration into hylax could be better, 
it does not write to xferfaxlog :(

The real pro of AVMs capi driver is that it can handle all the compression
stuff on the fly during the connection, so you can bypass the problems
that hylafax can not do it until now.


what about http://bugs.hylafax.org/bugzilla/show_bug.cgi?id=193 ?
is it related to the problem? I guess it is not in 4.1.1?

Bernd



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