Hylafax Mailing List Archives
|
[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
Re: [hylafax-users] capi4hylafax (again) take 2 :)
Am 2004.10.27 09:32 schrieb(en) Gavin Hamill:
Do you know how capi4hylafax actually works? I don't understand the
data flow involved - does 'c2faxrecv' emulate AT commands at /dev/
faxCAPI or something?
No. capi4hylafax does not emulate a modem. I think c2faxrecv runs
independently from hylafax and does the receiving on it's own. It
creates FIFO.faxCAPI and uses FIFO in /var/spool/hylafax to communicate
with hylafax.
For sending the program c2faxsend completely replaces the program
normally used by hylafax.
When I have /dev/faxCAPI symlinked to /dev/capi20 as guided by a
tutorial whose URL I have lose, faxstat always shows 'Waiting for
modem to come ready',
On my system everything works without such a link. I don't think this
link is useful for anything, because you cannot use /dev/capi20 like a
modem device.
This link would make faxgetty happy when it checks for the existence of
a device corresponding to the config.* file, but it would fail to
initialize the modem. Faxgetty also complains about the config file
because capi4hylafax uses a different syntax.
and if this symlink is not present, then faxstat always shows
'Terminated' as the status - is this correct?
I was expecting the traditional 'Running and idle' status..
Did you try "faxstat" after disabling faxgetty?
My system prints:
natira%mei ~> faxstat
HylaFAX scheduler on hedril.private.bodo-m.de: Running
Modem faxCAPI (+49.xxxx.yyyyyyy): Running and idle
Bodo
____________________ HylaFAX(tm) Users Mailing List _______________________
To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi
On UNIX: mail -s unsubscribe hylafax-users-request@xxxxxxxxxxx < /dev/null
*To learn about commercial HylaFAX(tm) support, mail sales@xxxxxxxxx*