User guide

The second step is to ensure that the hardware drivers have been properly compiled and loaded. By
running #lsmod you should see that the wctdm driver is loaded. You should also see that the wctdm
driver depends on the zaptel driver that depends on the crc_ccitt module.
# lsmod
zaptel 191748 7 wctdm
crc_ccitt 2304 3 hisax,zaptel,irda
Step 3: Configuring the TDM400P Card with ztcfg
The third step is to configure the hardware. The wctdm drivers are general purpose software for all
versions of the TDM400P card (remember that the PCI board can host up to 4 FXS/FXO ports). We
start by indicating that we have placed an FXO module in the first port of the PCI card.
The simplest /etc/zaptel.conf configuration file for this case is:
fxsls=1
loadzone=us
defaultzone=us
The first line (fxsls=1) means that we are using FXS signalling of type Loopstart in Port 1 of the
TDM400P. Remember that the FXO module needs to be signalled with an FXS module.
The second and third parameters of the zaptel configuration file indicates the type of tone used in this
region.
40
The zaptel configuration utility /sbin/ztcfg that is installed as part of the Asterisk source code distribution
(or the package zaptel) reads the /etc/zaptel.conf configuration file.
A typical output appears as follows:
# ztcfg -vv
Zaptel Configuration
=========================
Channel map:
40. A list of tone specifications is available at: http://www.itu.int/ITU-T/inr/forms/files/tones-0203.pdf
Page 35 TRICALCAR | www.wilac.net/tricalcar – Version: February 2008