Skip to end of metadata
Go to start of metadata

Overview

Let's install DAHDI!

On Linux, we will use the DAHDI-linux-complete tarball, which contains the DAHDI Linux drivers, DAHDI tools, and board firmware files. Again, we're assuming that you've untarred the tarball in the /usr/local/src directory, and that you'll replace X and Y with the appropriate version numbers.

See What to Download? for more information on downloading the DAHDI tarballs.

Install DAHDI before libpri

Icon

libpri 1.4.13 and later source code depends on DAHDI include files. So, one must install DAHDI before installing libpri.

Don't need DAHDI?

Icon

 If you are not integrating with any traditional telephony equipment and you are not planning on using the MeetMe dialplan application, then you do not have to install DAHDI or libpri in order to use Asterisk.

On This Page

 

Starting with DAHDI-Linux-complete version 2.8.0+2.8.0, all files necessary to install DAHDI are available in the complete tarball. Therefore, all you need to do to install DAHDI is:

[root@server src]# cd dahdi-linux-complete-2.X.Y+2.X.Y

[root@server dahdi-linux-complete-2.X.Y+2.X.Y]# make

[root@server dahdi-linux-complete-2.X.Y+2.X.Y]# make install

[root@server dahdi-linux-complete-2.X.Y+2.X.Y]# make config 

 

 

  • No labels

1 Comment

  1. cd dahdi-linux-complete-*
    make
    sudo make install
    sudo make config

    is more generic and avoids error messages if the Terminal was not started with the super user.


    wiki.asterisk.org/wiki/display/DAHDI/Quick+Start+From+Source

    does not allow comments, why ever. Therefore, I comment here. It should be (see https://askubuntu.com/a/268710):

    sudo apt install linux-headers-generic

    Futhermore, DAHDI requires

    sudo apt install libtool

    which is not part of the script install_prereq. In any way, this page here and the page over in DAHDI should be kept in sync, or link to each other at least. The other page does not know about the ‘complete’ package, because it was created earlier. That is OK. However, both pages should follow the same approach, for example:

    make
    sudo make install
    sudo make config

    and not the implicit:

    make all install

    because the make target ‘all’ needs other privileges than the make target ‘install’.