Hylafax Mailing List Archives
|
[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
Re: [hylafax-users] Modem faxCAPI (+49.00.00000): No status (cannot open file)
Am 2006.02.07 10:33 schrieb(en) Mauri:
I installed the hylafax but when I have to add a modem how can
identify the Diva Server installed on the server?
I mean with an external modem using serial1 I use faxaddmodem ttyS0,
but the Diva Server is not a serial device what type of tty I have to
put in configuration?
Hello Maurizio,
I don't have a Eicon card, but according to other postings these cards
seem to provide tty interfaces like /dev/ttyds01. (Currently there are
threads "Test Eicon/Modem at lower speeds" and "Sending multiple faxes
simultaneously with eicon diva 4BRI")
If the card has a CAPI interface it may be possible to use
capi4hylafax. This replaces faxgetty and faxsend and uses only the
spooler part of Hylafax.
capi4hylafax is an invention of AVM so maybe it's optimized for AVM's
CAPI implementation. I would prefer the tty interface provided by Eicon.
Am 2006.02.07 15:06 schrieb(en) Mauri:
I'm becoming crazy with this Diva Server 2fx on a Sles9.
Now I have the problem in subject and all suggestions will be very
appreciated (also link to documentation are good for me but I found
only in German)
You must configure the file config.faxCAPI. Your file seems to have the
example number +49.00.00000 in it. On my Debian system this file has
German and English comments.
I don't know how HylaFAX and capi4hylafax is started on a SuSE system,
but somwhere faxmodem must be called to inform HylaFAX about the
faxCAPI "modem" and c2faxrecv must be running.
When you tell me the location of the German documentation I can try to
translate it into English.
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*