Installing the TDM04B
Plug it into a spare PCI slot on your Asterisk server, just like any other expansion card. If you installed the Zaptel drivers when you installed Asterisk, you’re almost there. (If you didn’t, you need to re-install Asterisk and compile in Zaptel support.) The next step is to configure /etc/zaptel.conf. First make a backup copy of the original /etc/zaptel.conf:
# zaptel.conf zaptel.conf-old
Delete everything in zaptel.conf. If you’re using the Nano editor, just hold down Ctrl+k until everything is gone. Then copy these lines into it:
;zaptel.conf
loadzone = us
defaultzone=us
fxsks=1,2,3,4
Notice how lines are commented with semi-colons, and not hash marks. Now you can manually load the module if you like, to make sure it loads:
# modprobe wctdm
# lsmod
Module Size Used by
wctdm 34880 0
...
Asterisk X100P FXO card installation
Here is opensource Asterisk zaptel.conf example for FXO card #2
# This is the zaptel.conf file for opensource Asterisk telephony server. Asterisk # can be found on http://www.asterisk.org/
#
# This file is found in /etc/zaptel.conf and is NOT in /etc/asterisk
#
# More recent versions of this file can be found on:
# http://www.networks.pk
# Zaptel Configuration File
#
# This file is parsed by the Zaptel Configurator, ztcfg
#
#
# This is a very simple file used only with a single X100P
# card in my Linux box.
fxsks=1
loadzone=us
defaultzone=us
Tags: Asterisk, FXO card, PCI slot, wctdm, X100P, zaptel.conf
Regards,
I am using TDM04B card with asterisk 1.4. I have downloaded and installed Zaptel 1.4.0. Earlier I was using Asterisk 1.2 and Zaptel 1.2 with the same card, and it was working properly. Now when I give the command ztcfg -vvvv, I get the following logs:
Notice: Configuration file is /etc/zaptel.conf
line 4: Unable to read Zaptel version information.
Zaptel Version:
Echo Canceller:
Configuration
======================
Channel map:
Channel 01: FXS Kewlstart (Default) (Slaves: 01)
Channel 02: FXS Kewlstart (Default) (Slaves: 02)
Channel 03: FXS Kewlstart (Default) (Slaves: 03)
Channel 04: FXS Kewlstart (Default) (Slaves: 04)
4 channels configured.
Changing signalling on channel 1 from Unused to FXS Kewlstart
ZT_CHANCONFIG failed on channel 1: Inappropriate ioctl for device (25)
The zaptel.conf file
loadzone = us
defaultzone=us
fxsks=1,2,3,4
When i restart the system still i get the same error while loading. Inappropriate ioctl for device (25).
Please guide..
Thanks,
Riyaz Kajalwala
Did your OS recognize the card?
By typing ‘lspci’ you will receive a list of all the PCI devices you have. Note that Digium cards are recognized under different name:
you should see something like this : Communication controller: you can verify this by doing “lsmod”
Did you load the module for digium TDM04B card. For FXO do this:
modprobe wctdmÂyou can verify this by doing “lsmod”try these
cat /proc/interruptsordmesgoutput to prove a module for Digium card is loaded or not.Try changing:
fxsks=1,2,3,4to:
fxsks=1-4I was getting the same error with four lines, one for each fxoks/fxsks. Changing to two lines of
fxoks=1-2andfxsks=3-4make ztcfg happy.salam
i am in islamabad and want to purchase a FXO card. can u tell me any company or vendor?
Hi,
I’m trying to install zaptel and i’m facing the follow error while compile zaptel. please help
log:
In file included from /usr/src/zaptel/kernel/xpp/xpd.h:26,
from /usr/src/zaptel/kernel/xpp/card_fxo.c:27:
/usr/src/zaptel/kernel/xpp/xdefs.h:117: error: conflicting types for âboolâ
include/linux/types.h:36: error: previous declaration of âboolâ was here
make[4]: *** [/usr/src/zaptel/kernel/xpp/card_fxo.o] Error 1
make[3]: *** [/usr/src/zaptel/kernel/xpp] Error 2
make[2]: *** [_module_/usr/src/zaptel/kernel] Error 2
make[2]: Leaving directory `/usr/src/kernels/2.6.18-92.1.6.el5-i686′
make[1]: *** [modules] Error 2
make[1]: Leaving directory `/usr/src/zaptel’
make: *** [all] Error 2
Nabi, This is bug in zaptel.4.1.11,
I faced the same problem while compiling zaptel.
You can apply the following zaptel patch:
http://bugs.digium.com/file_download.php?file_id=19260&type=bug
1. Open the URL copy the text in zaptel source directory i.e. zaptel.patch
2. Apply the patch using following command you are done.
patch -p1 < zaptel.patch