<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Frameset//EN">
<HTML>
<!--(==============================================================)-->
<!--(Document
created with RoboEditor. )============================-->
<!--(==============================================================)-->
<!--(Document created with RoboEditor. )============================-->
<HEAD>
<!-- Inserted by TRADOS: -->
<META HTTP-EQUIV="content-type" CONTENT="text/html; charset=windows-1252">
<TITLE>CAPI4HylaFAX</TITLE>
<!--(Meta)==========================================================-->
</HEAD>
<!--(Body)==========================================================-->
<BODY>
<P>Product: CAPI4Linux, module: CAPI4HylaFAX<BR>
Operating system: Linux<BR>
Version: 01.02.02<BR>
Build: 03.01.17</P>
<H1>Welcome to CAPI4HylaFAX!</H1>
<P>This document contains information and hints about:</P>
<UL>
<LI CLASS="kadov-p">binding of HylaFAX to AVM ISDN-Controllers via CAPI
2.0 </LI>
</UL>
<UL>
<LI CLASS="kadov-p">working with HylaFAX</LI>
</UL>
<UL>
<LI CLASS="kadov-p">converting existing documents</LI>
</UL>
<H2><A NAME="Inhalt"></A>Contents</H2>
<P><A HREF="#1">1 General Information about Fax G3 over the CAPI 2.0
Interface with AVM ISDN-Controllers</A></P>
<BLOCKQUOTE>
<P><A HREF="#1.1">1.1 HylaFAX and Connecting to ISDN Using CAPI 2.0</A></P></BLOCKQUOTE>
<BLOCKQUOTE>
<P><A HREF="#1.2">1.2 Important Information for the Installation of the
HylaFAX Interface for CAPI 2.0</A></P></BLOCKQUOTE>
<P><A HREF="#2">2 Installing the HylaFAX Interface for CAPI 2.0 in SuSE</A></P>
<P><A HREF="#3">3 Installing the HylaFAX Interface for CAPI 2.0 in Other
Distributions</A></P>
<P><A HREF="#4">4 Instructions about the TIFF Format Used and Converting
Existing Files</A></P>
<P><A HREF="#5">5 Instructions for Operation with Multiple AVM
ISDN-Controllers</A></P>
<P><A HREF="#6">6 Instructions for Fax Polling</A></P>
<P><A HREF="#7">7 Further Information Sources</A></P>
<P><A HREF="#8">8 Support</A></P>
<H2><A NAME="1"></A>1 General Information about Fax G3 over the CAPI 2.0
Interface with AVM ISDN-Controllers</H2>
<P>Analog Fax G3 service over the digital ISDN network requires both that
the data transmitted be transformed from analog to digital or from digital
to analog (A/D or D/A transformation), and that as signaling conform to
the Fax G3 standard (such as ITU-T.30).</P>
<P>As part of the CAPI 2.0 standard, this protocol mechanism is subject to
compulsory standardization (T.30 modem for Group 3 fax). The
implementation of this protocol by the manufacturer of the ISDN-Controller
is optional. If Fax G3 is implemented in CAPI 2.0 drivers, software
developed for the CAPI 2.0 interface can access the ISDN-Controller
directly and thus quite easily. All AVM ISDN-Controllers for ISDN basic
rate interface currently supported by CAPI4Linux offer Fax G3 support
over the CAPI 2.0 interface.</P>
<P>Note that when passive ISDN-Controllers like the AVM FRITZ!Card are
used, all calculations for A/D or D/A transformation must be carried by
the CPU of your computer system. This can result in a relatively high
system load, especially when Fax G3 documents are received. Active
controllers such as those from the AVM ISDN-Controller Family B1 all
include their own chip, thus reducing the system's load.</P>
<P><A HREF="#Inhalt">Back to the Table of Contents</A></P>
<H3><A NAME="1.1"></A>1.1 HylaFAX and Connecting to ISDN Using CAPI 2.0</H3>
<P>The current version of HylaFAX unfortunately does not offer direct CAPI
2.0 binding; only a binding for analog modems is included. Until now only
active ISDN-Controllers like the AVM ISDN-Controller B1 could be connected
to HylaFAX by means of a separately installed patch.</P>
<P>The new "CAPI4Linux" now allows the use of practically any
ISDN-Controller equipped with a fax-capable CAPI 2.0 driver compliant with
the LINUX CAPI 2.0 specification. See also the CAPI 2.0 Specification at <BR><A HREF="http://www.capi.org">http://www.capi.org</A></P>
<P>Thus it is possible for the first time to fax with the popular passive
ISDN-Controllers even in Linux. Thanks to CAPI 2.0, multiple ISDN services
can be used at the same time, such as Fax G3 reception and a
connection to the Internet via pppd. The ISDN B channels are assigned
automatically by the CAPI 2.0 driver.</P>
<P>Up to four active AVM ISDN-Controllers with CAPI4Linux drivers can be
installed on each system. Even mixed configurations (one AVM
ISDN-Controller B1 PCI, one ISDN-Controller B1 ISA plus two
ISDN-Controllers C2, for example) are possible with as many as four active
ISDN-Controllers. The CAPI4HylaFAX module then has to be modified for
operation with multiple ISDN-Controllers. Please see the additional
information in <A HREF="#3">section 3</A>.</P>
<P>In any system, only <B>one</B> passive ISDN-Controller (e.g. FRITZ!Card
PCI) can be installed using a CAPI4Linux driver.</P>
<P>The latest version of HylaFAX and more information are available at
<A HREF="http://www.hylafax.org">http://www.hylafax.org</A></P>
<P><A HREF="#Inhalt">Back to the Table of Contents</A></P>
<H3><A NAME="1.2"></A>1.2 Important Information for the Installation of
the HylaFAX Interface for CAPI 2.0</H3>
<P>From the current HylaFAX version on (included with the SuSE 8.1),
HylaFAX always transfers seven parameters to HylaFAX faxrcvd. SuSE Linux
versions 8.0 or below or original HylaFAX versions expect less parameters.
The difference to the original HylaFAX lies in the restricted analog
model, which does not allow the important ISDN features MSN or DDI to be
used for e-mail forwarding.</P>
<P>The new "CAPI4HylaFAX" installation script automatically
adapts existing faxrcvd scripts such that older faxrcvd scripts can
continue working with the current CAPI4HylaFAX version.</P>
<P>In line 33, for example, the script looks like this:</P>
<P># faxrcvd file devID commID error-msg CIDNumber CIDName destination<BR>
#<BR>
<B>if [ $# <FONT COLOR="#008040">-lt</FONT> 7 ]; then</B><BR>
echo "Usage: $0 file devID commID error-msg CIDNumber CIDName
destination"<BR>
fi</P>
<P>The following table specifies the faxrcvd parameters in brief:</P>
<TABLE
STYLE="x-border-left: BORDER table-solid; x-border-top: BORDER table-solid; x-border-right: BORDER table-solid; x-border-bottom: BORDER table-solid; border-collapse: separate;"
BORDER="4">
<TR>
<TD WIDTH="132"><B STYLE="font-weight: bold;">Parameter</B></TD>
<TD WIDTH="722"><B STYLE="font-weight: bold;">Meaning</B></TD>
</TR>
<TR>
<TD WIDTH="132">qfile</TD>
<TD>indicates the received TIFF or SFF fax file</TD>
</TR>
<TR>
<TD WIDTH="132">devid</TD>
<TD WIDTH="722">relates to the virtual modem device required to send a
fax (faxCAPI, for example)</TD>
</TR>
<TR>
<TD WIDTH="132">commid</TD>
<TD WIDTH="722">continuous identification number for incoming calls
(faxes)</TD>
</TR>
<TR>
<TD WIDTH="132">error-msg</TD>
<TD WIDTH="722">includes an entry when problems occurred during fax
reception</TD>
</TR>
<TR>
<TD WIDTH="132">cidnumber</TD>
<TD WIDTH="722">fax number of the sender; if no number is transferred,
the caller ID is shown here</TD>
</TR>
<TR>
<TD WIDTH="132">cidname</TD>
<TD WIDTH="722">name of the sender's fax device;</TD>
</TR>
<TR>
<TD>destination</TD>
<TD>extension number of the recipient (MSN or DDI)</TD>
</TR>
</TABLE>
<P>Further information about faxrcvd can be found in the corresponding
manual page, displayed by entering the command "man faxrcvd" at
a console.</P>
<TABLE
STYLE="float: alignleft; x-border-left: BORDER table-solid; x-border-top: BORDER table-solid; x-border-right: BORDER table-solid; x-border-bottom: BORDER table-solid; border-collapse: separate;"
BORDER="4">
<TR>
<TD><B>ATTENTION:</B></TD>
<TD>If you want to use the current CAPI4HylaFAX version in one of the
SuSE versions between 7.2 and 8.0 and if you want to forward faxes from
a certain MSN or DDI, you have to adapt the the faxrcvd script manually,
since the order of parameters varies depending on which HylaFAX and SuSE
version is used.</TD>
</TR>
</TABLE>
<TABLE
STYLE="float: alignleft; x-border-left: BORDER table-solid; x-border-top: BORDER table-solid; x-border-right: BORDER table-solid; x-border-bottom: BORDER table-solid; border-collapse: separate;"
BORDER="4">
<TR>
<TD><B>NOTE:</B></TD>
<TD>If you use "GlobalCall", please note the following: "GlobalCall",
especially popular in Austria, does not transmit your main number, thus
deactivating the parameter "IncomingMSN" in the "config.faxCAPI"
file. Therefore all voice and fax calls that arrive at the main number
are accepted. If you want to deactivate the automatic call acceptance,
you have to set the parameter "AcceptGlobalCalls" on "0".
In all other cases the pre-set value "1" is preferable.</TD>
</TR>
</TABLE>
<P>More information about HylaFAX and the usage of the "faxrcvd"
script is available at <A HREF="http://www.hylafax.org">http://www.hylafax.org</A>.</P>
<H2><A NAME="2"></A>2 Installing the HylaFAX Interface for CAPI 2.0 in
SuSE</H2>
<P>Please note that the following prerequisites have to be met before
starting installation of HylaFAX:</P>
<H4>Installation requirements:</H4>
<UL>
<LI CLASS="kadov-p">Any Linux distribution, for example, SuSE 7.3/8.0/8.1</LI>
</UL>
<UL>
<LI CLASS="kadov-p">an installed HylaFAX packet including the program
library TIFFLIB. The latest version can be obtained from
<A HREF="http://www.hylafax.org">http://www.hylafax.org</A>.</LI>
</UL>
<UL>
<LI CLASS="kadov-p">You have to perform a "root" installation,
i.e. you have to log in as "super user" in the system</LI>
</UL>
<UL>
<LI CLASS="kadov-p">Read and write rights (rw) to /dev/capi20 have to be
configured for the fax user(s) Please see also <A HREF="#Schritt 5">step
(5)</A>.</LI>
</UL>
<UL>
<LI CLASS="kadov-p">At least one, and no more than four active AVM
ISDN-Controller(s), or any passive AVM ISDN-Controller with a correctly
installed CAPI 2.0 driver from the CAPI4Linux package must be installed.
It is not possible to use the HylaFAX interface "CAPI4HylaFAX"
with the ISDN4Linux package (it is not a CAPI 2.0 interface).</LI>
</UL>
<!--(Table)=========================================================-->
<!--begin!kadov{{-->
<TABLE
STYLE="float: alignleft; x-border-left: BORDER table-solid; x-border-top: BORDER table-solid; x-border-right: BORDER table-solid; x-border-bottom: BORDER table-solid; border-collapse: separate;"
BORDER="4">
<TR>
<TD><B>NOTE:</B></TD>
<TD>AVM supplies pre-compiled patches for SuSE which facilitate
especially simple installation for these distributions. For more details
about installation in other distributions, see <A HREF="#3">section 3</A>.</TD>
</TR>
</TABLE>
<!--}}end!kadov-->
<H4> Installation</H4>
<P><B>(1)</B> Copy the archive "CAPI4HylaFAX-[Version No].tar.gz"
from the CAPI4Linux archive to your computer (e.g. from a diskette using
the "mcopy" command from a console) and start the console
(command prompt).</P>
<P>Extract the archive with the command:</P>
<BLOCKQUOTE>
<P><B STYLE="font-weight: bold;">tar -xzvf CAPI4HylaFAX-[Version
No].tar.gz</B></P></BLOCKQUOTE>
<P>A directory called "CAPI4HylaFAX-[Version No]" is created.</P>
<P><B>(2)</B> Switch to this new "CAPI4HylaFAX-[Version No]"
directory.</P>
<P><B>(3)</B> Run "./install". With "./install -h" you
get an overview of parameters with extended installation options. Next the
system automatically checks for an installed HylaFAX. If the HylaFAX
package is not found, a corresponding message is returned.</P>
<!--(Table)=========================================================-->
<TABLE
STYLE="x-border-left: BORDER table-solid; x-border-top: BORDER table-solid; x-border-right: BORDER table-solid; x-border-bottom: BORDER table-solid; border-collapse: separate;"
BORDER="4">
<TR>
<TD><B>NOTE:</B></TD>
<TD>If the HylaFAX package is not found, you have to enter the "HylaFAX
spool directory" manually as a parameter. Even then it is possible
to send or receive a fax as described in step (4). In this case simply
install stand-alone operation without automatic HylaFAX configuration by
entering the parameter "-s".</TD>
</TR>
</TABLE>
<P>By means of a graphic menu system, you can now perform the initial
configuration of the most important parameters for the fax operation of a
previously installed AVM ISDN-Controller. All configurations are saved in
the file "/var/spool/fax/etc/config.faxCAPI". This file is used
by HylaFAX as well as by the applications "c2faxsend" and "c2faxrecv".
Please see also step (4).</P>
<!--(Table)=========================================================-->
<TABLE
STYLE="x-border-left: BORDER table-solid; x-border-top: BORDER table-solid; x-border-right: BORDER table-solid; x-border-bottom: BORDER table-solid; border-collapse: separate;"
BORDER="4">
<TR>
<TD><B>ATTENTION:</B></TD>
<TD>To configure more than one active AVM ISDN-Controller for fax
operation with HylaFAX, or to change the settings of the CAPI4HylaFAX
module after installation, you MUST (!) manually perform the relevant
settings in the file:<BR>
/var/spool/fax/etc/config.faxCAPI (in SuSE Linux)<BR>
/var/spool/fax/etc/config.faxCAPI (HylaFAX 4.1.x)</TD>
</TR>
</TABLE>
<P><A HREF="#Inhalt">Back to the Table of Contents</A></P>
<P>The graphic menu system allows only the configuration of the basic
functions of an ISDN-Controller during installation. All further settings
can only be performed manually in the file "config.faxCAPI".</P>
<P>For configuration using the menu system, the following parameters are
now available:</P>
<!--(Table)=========================================================-->
<TABLE
STYLE="x-border-left: BORDER table-solid; x-border-top: BORDER table-solid; x-border-right: BORDER table-solid; x-border-bottom: BORDER table-solid; border-collapse: separate;"
BORDER="4">
<TR>
<TD WIDTH="132"><B STYLE="font-weight: bold;">Parameter</B></TD>
<TD WIDTH="722"><B STYLE="font-weight: bold;">Meaning</B></TD>
</TR>
<TR>
<TD WIDTH="132">OutgoingMSN</TD>
<TD>Defines the outgoing MSN to be used at the ISDN basic access. In
this way you can define which MSN from the block of numbers is to be
used for outgoing connections and thus allow MSN-specific accounting.
For some PBXs with an internal So bus you must indicate the MSN of the
extension used.</TD>
</TR>
<TR>
<TD WIDTH="132">IncomingMSNs</TD>
<TD WIDTH="722">Defines the outgoing MSN to be used at the ISDN basic
rate interface. If several ISDN devices with the same ISDN service
indicator are used at the basic rate interface, each of these devices
must be unambiguously addressed via a specific MSN. If this parameter is
NOT (!) defined, all incoming calls with the service indicator "Group
2/3 Fax" and "Telephony (analog)" will be accepted. If
several MSNs are to be used, they must be separated by commas.</TD>
</TR>
<TR>
<TD WIDTH="132">DDIParams</TD>
<TD WIDTH="722">Defines parameters for operation at a PBX ISDN
point-to-point line with direct dial-in (DDI). indicates the number of
digits which precede the extension number.<BR>
Example: 39976-0 => DDIOffset=39976 (number of digits which precede
the extension number)<BR>
"DDILength": indicates the number of digits of the extension
number.<BR>
Example: 4711 => DDILength=4<BR>
"IncomingDDIs": List of extension numbers which are to be
accepted.</TD>
</TR>
<TR>
<TD WIDTH="132">FaxNumber</TD>
<TD WIDTH="722">Defines the fax number which appears in the fax header
at the recipient.<BR>
<B>ATTENTION</B>: HylaFAX cannot process blanks. Use the entry "."
instead. This entry is automatically converted into a blank.</TD>
</TR>
<TR>
<TD WIDTH="132">FaxIdentifier</TD>
<TD WIDTH="722">Defines the local name (station ID) shown in the fax
header at the recipient.</TD>
</TR>
<TR>
<TD WIDTH="132">NumberPrefix</TD>
<TD WIDTH="722">Defines the digit required to access an outside line
when operating at a PBX (generally "0").</TD>
</TR>
</TABLE>
<P><A HREF="#Inhalt">Back to the Table of Contents</A></P>
<TABLE
STYLE="x-border-left: BORDER table-solid; x-border-top: BORDER table-solid; x-border-right: BORDER table-solid; x-border-bottom: BORDER table-solid; border-collapse: separate;"
BORDER="4">
<TR>
<TD><B>NOTE:</B></TD>
<TD>Further parameters for fax polling, for example, can be directly
configured in the file "config.faxCAPI". These parameters are
documented in the file itself.</TD>
</TR>
</TABLE>
<P><B>(4)</B> Now a configuration file is generated automatically at "/var/spool/[hyla]fax/etc/config.faxCAPI".
If for some reason the file does not exist (any more), the default
settings will be used automatically.</P>
<P>Now it is possible to send or receive a fax immediately from the command
line using the following applications No other components are required by
HylaFAX for these operations. These applications thus offer the
opportunity to perform a quick test in stand-alone operation of whether
the software is properly installed.</P>
<!--
(Table)=========================================================-->
<TABLE
STYLE="x-border-left: BORDER table-solid; x-border-top: BORDER table-solid; x-border-right: BORDER table-solid; x-border-bottom: BORDER table-solid; border-collapse: separate;"
BORDER="4">
<TR>
<TD>Send</TD>
<TD>c2faxsend -f TIFF -d [TelNo] [TIFF file]<BR>
c2faxsend -f SFF -d [TelNo] [SFF file]</TD>
</TR>
<TR>
<TD>Receive</TD>
<TD>c2faxrecv -f TIFF<BR>
c2faxrecv -f SFF</TD>
</TR>
</TABLE>
<P>The parameter -h provides a complete survey of the implemented options
in both applications.</P>
<P>The applications "c2faxsend" and "c2faxrecv" search
for the configuration file "config.faxCAPI" at "/var/spool/fax/etc/config.faxCAPI".
It is possible to save the configuration file "config.faxCAPI"
at another location in the system; in this case the location must be
specified in "-C FILE" when the application is opened.</P>
<P>In stand-alone operation without HylaFAX, "c2faxrecv" cannot
be running when a fax is to be sent(!). "c2faxsend" can use only
the "TIFF" (class F, FAX G3, 1 dim. Huffmann coding) and "SFF"
file formats. More information about the SFF format is documented in the
CAPI 2.0 specification. For more information, see
<A HREF="http://www.capi.org">http://www.capi.org</A>. More information
about the TIFF format used is presented in <A HREF="#4">section 4</A> of
this document.</P>
<P>In order to send a document, it should be converted with a corresponding
program first (e.g. with Ghostscript). AVM supplies the demonstration file
"fritz_pic.tif" in the suitable TIFF format. The command for
sending the AVM test fax to any Fax G3 remote site, specified with
[TelNo], is thus</P>
<BLOCKQUOTE>
<P><B STYLE="font-weight: bold;">c2faxsend -vf TIFF -d [TelNo]
fritz_pic.tif</B></P></BLOCKQUOTE>
<P><A NAME="Schritt 5"></A><B>(5)</B> A number of preparatory steps for
using HylaFAX were already automatically performed by the installation
script in step (3).</P>
<P>If HylaFAX is to be used, note the following:</P>
<UL>
<LI CLASS="kadov-p">The "./install" script performed at step
(4) copies the fax files to "/usr/local/bin".</LI>
</UL>
<UL>
<LI CLASS="kadov-p">The system searches for HylaFAX automatically. The
HylaFAX "config file" and the "/etc/inittab" file
are modified as necessary so that faxes can be sent and received over
CAPI 2.0.</LI>
</UL>
<UL>
<LI CLASS="kadov-p">Faxes can only be sent and received with HylaFAX when
"c2faxrecv" is active. Therefore this program was registered
automatically in the "/etc/inittab file".</LI>
</UL>
<UL>
<LI CLASS="kadov-p">Read and write rights (rw) to "/dev/capi20"
must be configured for the fax user(s), which is generally not the case.
When root "c2faxrecv" is activated, "c2faxrecv"
changes its user to "UUCP"; therefore the user "UUCP"
must exist and must have rw rights (read and write rights) to "/dev/capi20".
For "User access" to CAPI the rights of "/dev/capi20"
have to be set to "0666".</LI>
</UL>
<UL>
<LI CLASS="kadov-p">To avoid rebooting, simply activate "c2faxrecv &"
after installation. In some cases it is necessary to end the HylaFAX
program "faxq" and to restart it in order to implement the
changes to the settings in its configuration file.</LI>
</UL>
<P><A HREF="#Inhalt">Back to the Table of Contents</A></P>
<H4>Working in HylaFAX</H4>
<P>To send, just enter "sendfax -d [TelNo] file". The file can
have almost any format. The programs "file" or "a2ps"
must be able to read the format so that the file can be converted
correctly first into PS format and then into TIFF format. Graphical
frontends are also available to facilitate working with HylaFAX. For more
information, see the documentation at</P>
<P><A HREF="http://www.hylafax.org/">http://www.hylafax.org</A></P>
<P>If faxes are to be sent directly from an application, the printer
configuration must be adapted in the application. Usually a command for
printing can be entered in the application, usually just "lpr".
Replace this with "sendfax -d [TelNo]". These functions are
program-dependent and should be documented in the application Help file.</P>
<H4>Fax Reception</H4>
<P>Once a fax is received via HylaFAX, "root" receives a mail
sent by the script "faxrcvd" announcing the reception of a fax.</P>
<P>When using the fax module "c2faxrecv" in stand-alone
operation, you can obtain an analog fax receiving by using the supplied
sample script "sample_faxrcvd".</P>
<P>Once a fax is received, the script specified in the configuration file
(for HylaFAX "faxrcvd") is executed with the following
parameters, separated for HylaFAX mode and stand-alone operation:</P>
<!--(Table)=========================================================-->
<TABLE
STYLE="x-border-left: BORDER table-solid; x-border-top: BORDER table-solid; x-border-right: BORDER table-solid; x-border-bottom: BORDER table-solid; border-collapse: separate;"
BORDER="4">
<TR>
<TD>Stand-alone operation</TD>
<TD>[Result Code] [CAPI Disconnect Reason] [Sender ID] [Called Number
or DDI] [Num of Pages] [File(s)]</TD>
</TR>
<TR>
<TD>HylaFAX mode</TD>
<TD>[faxrcvd file] [devID] [commID] [error-msg] [CIDNumber] [CIDName]
[destination]</TD>
</TR>
</TABLE>
<P>Additional details are available in the HylaFAX documentation.</P>
<P><A HREF="#Inhalt">Back to the Table of Contents</A></P>
<H4>Additional Instructions</H4>
<UL>
<LI CLASS="kadov-p">The configuration file must be located in the "etc"
directory of HylaFAX. (For default settings, see above).</LI>
</UL>
<UL>
<LI CLASS="kadov-p">Even if faxes are only to be sent, "c2faxrecv"
must be active!</LI>
</UL>
<UL>
<LI CLASS="kadov-p">For fax reception, simply execute "c2faxrecv &",
e.g. in a start script, if not already performed by "/etc/inittab".</LI>
</UL>
<UL>
<LI CLASS="kadov-p">Device Names: Because the applications are CAPI 2.0
applications based directly on CAPI, this entry is not actually
necessary. However, the name of the device can be entered in the
commando line, or is entered automatically by HylaFAX. This name is used
for signaling to HylaFAX and to determine the name of the configuration
file: "config.[Device Name]". Thus it is also possible to
manage multiple "c2faxrecv" demons along with their
configuration files. Another option is the "-C" switch.</LI>
</UL>
<UL>
<LI CLASS="kadov-p">If problems occur after installation during fax
transmission, HylaFAX probably didn't process the modifications in the
configuration file yet. In this case enter "faxsetup" or "faxmodem
faxCAPI" as a super user with corresponding rights to implement the
changes in HylaFAX.</LI>
</UL>
<P><A HREF="#Inhalt">Back to the Table of Contents</A></P>
<H2><A NAME="3"></A>3 Installing the HylaFAX Interface for CAPI 2.0 in
Other Distributions</H2>
<P>If you use a distribution or a kernel version other than SuSE
6.3/6.4/7.0/7.3/8.0/8.1, you still can use CAPI4HylaFAX without problems.
Only if the installation routine of CAPI4HylaFAX reports missing (program)
libraries is it necessary to compile the sources supplied in the directory
"/src". To simplify this process, AVM supplies complete "makefiles".
For more details about compiling sources, see the file "README.src".</P>
<P><A HREF="#Inhalt">Back to the Table of Contents</A></P>
<H2><A NAME="4"></A>4 Instructions about the TIFF Format Used and
Converting Existing Files</H2>
<P>TIFF (Tagged Image File Format) files must correspond to the
specification "Class F for facsimile (TIFF Class F)", based on
the TIFF 6.0 specification. In addition, the file must contain
one-dimensional Huffmann coding. This format was specified in "Group
3" by the CCITT (International Telegraph and Telephone Consultative
Committee). For more information about TIFF format, see the "Developer"
division of Adobe Systems Incorporated at <A HREF="http://www.adobe.com">http://www.adobe.com</A></P>
<H4>Converting Existing Files with Ghostscript</H4>
<P>To convert a postscript file into a TIFF file conform to the fax
application, the following command can be used to activate Ghostscript:</P>
<BLOCKQUOTE>
<P><B STYLE="font-weight: bold;">gs -dBATCH -dNOPAUSE -sDEVICE=tiffg3
-sOutputFile=[Name of Tif file] [Name of postscript file]</B></P></BLOCKQUOTE>
<P><A HREF="#Inhalt">Back to the Table of Contents</A></P>
<H2><A NAME="5"></A>5 Instructions for Operation with Multiple AVM
ISDN-Controllers</H2>
<P>Up to four active AVM ISDN-Controllers can be addressed via the CAPI 2.0
interface. It is also possible to install controllers for different bus
systems such as PCI, ISA and PCMCIA. For details about the controller
installation, please refer to the documentation of the driver module Linux
CAPI 2.0.</P>
<P>The CAPI4HylaFAX module simultaneously supports the operation of
multiple active AVM ISDN-Controllers sending and receiving in HylaFAX.
After installing the module CAPI4HylaFAX, some modifications are necessary
in the configuration file "/var/spool/fax/etc/config.faxCAPI".
These changes are necessary because the graphically supported installation
routine described above is designed for one controller only. Other
parameters for the operation of several AVM ISDN-Controllers in the
configuration file "config.faxCAPI" are documented in the file
itself. After modifying the configuration file the module "c2faxrecv"
must be stopped and restarted in order to activate the modification.</P>
<P>A pre-configured sample script is enclosed for operation with the AVM
ISDN-Controller C4 or the AVM ISDN-Controller C4. The script is named "sample_AVMC4_config.faxCAPI".</P>
<P>This script simplifies the configuration of multiple-channel controllers
for CAPI4HylaFAX: just modify the script according to your individual
technical surroundings (MSNs etc.).</P>
<P><A HREF="#Inhalt">Back to the Table of Contents</A></P>
<H2><A NAME="6"></A>6 Instructions for Fax Polling</H2>
<P>Fax polling is now supported with this version of HylaFAX. Operation in
client mode is possible, i.e., CAPI4HylaFAX can be used to poll fax
documents. It is not yet possible to provide callers with fax documents to
poll (Server Mode).</P>
<P>Execute the following file to start fax polling in stand-alone mode:</P>
<BLOCKQUOTE>
<P><B STYLE="font-weight: bold;">c2faxsend -vf TIFF -d [TelNo] -P [mail
address]</B></P></BLOCKQUOTE>
<P>Execute the following file to start fax polling in HylaFAX mode:</P>
<BLOCKQUOTE>
<P><B STYLE="font-weight: bold;">sendfax -d [TelNo] -p</B></P></BLOCKQUOTE>
<P>In either case, a script is started after the fax is received and the
E-mail address and the corresponding fax document are provided. The script
is defined in the configuration file "config.faxCAPI" under the
following parameter:</P>
<BLOCKQUOTE>
<P><B STYLE="font-weight: bold;">PollRcvdCmd</B></P></BLOCKQUOTE>
<P><A HREF="#Inhalt">Back to the Table of Contents</A></P>
<H2><A NAME="7"></A>7 Further Information Sources</H2>
<H4>Information about the Applications Interface CAPI 2.0</H4>
<P>The applications interface CAPI 2.0 can be downloaded free of charge
from the following Internet site:</P>
<P><A HREF="http://www.capi.org">http://www.capi.org</A></P>
<P>Additional questions about the CAPI 2.0 specification should be asked in
the Usenet at the following URL:</P>
<P><A HREF="news:comp.dcom.isdn.capi">news:comp.dcom.isdn.capi</A></P>
<H4>Newsgroup</H4>
<P>Useful discussions of ISDN and Linux issues can be found at:</P>
<P><A HREF="news:de.comp.os.unix.linux.isdn">news:comp.os.linux.networking
or news:comp.dcom.isdn</A></P>
<H4>Faxing with capicvd</H4>
<P>Information about an already existing CAPI 2.0-based program for
receiving faxes (G3) and voice calls is provided at the URL:</P>
<P><A HREF="http://capircvd.de">http://capircvd.berlios.de/index_eng.php3</A></P>
<P><A HREF="#Inhalt">Back to the Table of Contents</A></P>
<H2><A NAME="8"></A>8 Support</H2>
<P>AVM offers support for this product. This support is limited to the
actual installation and the ISDN functionality up to the successful
completion of the test connection or the test fax over CAPI 2.0 drivers
and the CAPI4HylaFAX module in combination with AVM ISDN-Controllers,
using the provided installation programs. For questions about network
configuration, integrated functions of the Linux operating system and
applications from other manufacturers, please contact the relevant
manufacturer or the support service of the distribution used. Please
address any questions concerning configuration and operation of HylaFAX
to:</P>
<P><A HREF="http://www.hylafax.org">http://www.hylafax.org</A></P>
<P>The AVM web site offers detailed information and updates free of charge.</P>
<P>Visit the site at <A HREF="http://www.avm.de/en">http://www.avm.de/en</A>.</P>
<UL>
<LI CLASS="kadov-p">The "Products" category provides detailed
information about all AVM products as well as announcements of new
products and product versions.</LI>
</UL>
<UL>
<LI CLASS="kadov-p">Through "Service" the FAQs (Frequently
Asked Questions) can be accessed along with a list of their answers.
Solutions to concrete problems are offered here. Unfortunately, this
site is only available in German:
<A HREF="http://www.avm.de/de/Service/FAQs/Linux/index.html">http://www.avm.de/de/Service/FAQs/Linux/index.html</A></LI>
</UL>
<UL>
<LI CLASS="kadov-p">The current driver software for all AVM
ISDN-Controllers can be downloaded from the "Download" area.</LI>
</UL>
<P>All programs and drivers available from the Internet site can also be
obtained from the AVM Data Call Center (ADC).</P>
<P>Please use the information sources described above before contacting AVM
Support. If these instructions and the various information sources have
not helped to resolve your problem, contact AVM Support for additional
technical assistance. AVM Support can be reached by E-mail. You may send
your support requests to AVM by E-mail. Support inquiries can be sent to
AVM using the E-mail form provided at the Internet address</P>
<P><A HREF="http://www.avm.de/en/service">http://www.avm.de/en/service</A></P>
<P>Fill out the form and mail it to AVM Support by clicking the "Send"
button.</P>
<P><A HREF="#Inhalt">Back to the Table of Contents</A></P>
<P>EOF<FONT SIZE="-1"></FONT></P>
<!--(HR)============================================================-->
<HR STYLE="/*begin!kadov{{*/ float: aligncenter; /*}}end!kadov*/ ">
<P><FONT SIZE="-1">SAS, SR, FS 01/2003</FONT></P>
</BODY>
</HTML>
distrib
>
Mandriva
>
current
>
i586
>
media
>
contrib-release
>
by-pkgid
>
b6737bd89883fae83589bbf915f94878
>
files
>
9
