Difference between revisions of "Install Dahdi"

From Kolmisoft Wiki
Jump to navigationJump to search
Line 108: Line 108:
but they will otherwise operate just as they did in previous versions
but they will otherwise operate just as they did in previous versions


Channel configurations can be read from  
Channel configurations will be read from  


  /etc/asterisk/zapata.conf
  /etc/asterisk/zapata.conf

Revision as of 11:29, 14 May 2012

What is DAHDI

DAHDI is the new name for 'Zaptel' as of May 19th 2008.

More information can be found here

Install your kernel devel package

yum -y install kernel-devel-$(uname -r)

or

yum -y install kernel-PAE-devel

if PAE kernel is used on machine.

Download DAHDI

This manual assumes that you already have MOR billing installed!

cd /usr/src
wget http://downloads.asterisk.org/pub/telephony/dahdi-linux/dahdi-linux-current.tar.gz

Unpack sources

tar xvfz dahdi-linux-current.tar.gz

Download DAHDI tools

cd /usr/src
wget http://downloads.asterisk.org/pub/telephony/dahdi-tools/dahdi-tools-current.tar.gz

Unpack sources

tar xvfz dahdi-tools-current.tar.gz

Build DAHDI linux

cd /usr/src/dahdi-linux-2.5.0.1
make clean

make 
make install

Build DAHDI tools

cd /usr/src/dahdi-tools-2.5.0.1

./configure
make
make install
make config

Alternative setup

Download the complete Dahdi package which includes both the DAHDI module and tools. If you need to influence the installation

of both the DAHDI linux and tools use above steps

wget http://downloads.asterisk.org/pub/telephony/dahdi-linux-complete/dahdi-linux-complete-2.5.0.1+2.5.0.1.tar.gz
tar xvfz dahdi-linux-complete-2.5.0.1+2.5.0.1.tar.gz
cd dahdi-linux-complete-2.5.0.1
make all 
make install
make config

Recompile Asterisk for DAHDI support

cd /usr/src/ASTERISKLOCATIONFOLDER
./configure

make
make menuconfig

Go to "Channel Drivers" and make sure that "chan_dahdi" is checked.

make install
make config

How to use Zap instead of DAHDI

As ZAPTEL is now not used in Asterisk, systems that are still using ZAP channels can be configured to use Dahdi.

Edit /etc/asterisk/asterisk.conf file and add this line:

dahdichanname = no

Adding this entry solves a few issues:

All CLI commands that begin with 'zap' are now available as 'dahdi' commands as well; the 'zap' variants will report that they are deprecated the first time you use each one in an Asterisk instance, but they will otherwise operate just as they did in previous versions

Channel configurations will be read from

/etc/asterisk/zapata.conf

So if you use "dahdichanname = no" - make sure to enter channel configuration in that file.

Source [1]