Since Asterisk is most famous opensource telephony platforum out there. The main reason of the popularity is its integration various telecoms service through telephony modules and hardware. Hence most of the people confuse when they upgrade their Asterisk and they do not find chan_zap module in the Asterisk modules directory. Asterisk wonder what’s wrong with the hardware. They do not know that Digium has changed the zaptel package name with Dahdi. I was reported a lot of questions about Zap and Dahdi difference. Below is a little explain that what is DAHDI? what’s difference between Zaptel and Dahdi and how it will effect your Asterisk infrastructure in future.

DAHDI (Digium Asterisk Hardware Device Interface). But it seems that Astricon’s joke was not entirely a joke: Digium Zaptel development stops and rename it DAHDI (Digium Asterisk Hardware Device Interface). Approximately two years ago, the owner of the trademark has contacted the company and Digium Zaptel advised that the name is actually a brand name. The company produces a phone card and would like to see on demand ‘phone card Zaptel’ not granted would not be associated with their brand name products.

In connection with the situation and to prevent it in the future, the new name will be registered as a brand (like Asterisk). For these purposes, will be released version DAHDI 2.0.0, which would include virtually all the functions of Zaptel 1.4 (except for supporting kernel 2.4 and drivers for older cards torisa and wcusb).

Asterisk 1.6 will be able to use only DAHDI, previous versions will remain compatible with Zaptel 1.4 (Asterisk 1.4 cmozhet used as Zaptel, and DAHDI). After version DAHDI 2.0.0 Issue Zaptel with correction of errors will stop.

The file is replaced by zaptel.conf /etc/dahdi/system.conf and although they are virtually equal on the inside, there is a small detail, the echo canceler that can dynamically load and unload and select independently for each DAHDI channel, and if we have a primary E1 (30 channels of voice) can use an echo canceller for the first 10 channels, another echo canceler for the 10 following another for the last 10. ¿Useful? it is not now, but sure someone will find it. For everything else, is exactly the same.

Moreover, the file has become zapata.conf /etc/asterisk/chan_dahdi.conf and true, is almost the same inside, the differences are minimal and some quite odd that I leave you to discover

Related posts

• Open source Asterisk PBX (7)
• Asterisk zaptel.conf configuration with X100P FXO and TDM04B Cards (8)
• Asterisk zapata.conf configuration (1)
• Asterisk queues.conf (2)
• Telephony PCI Slots (0)

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

Related posts

• Telephony PCI Slots (0)
• Free Digium Hardware (0)
• Digium Telephony TDM Cards (3)
• Asterisk chan_dahdi (4)
• WiSip 802.11 SIP phone configuration (0)