System information

The init script uses the /etc/dahdi/modules file to determine which modules should be
loaded to support the hardware in the system. The installation of the init script attempts
to automatically set up this file for you, but you should check it to make sure it is correct:
# Autogenerated by tools/xpp/dahdi_genconf (Dahdi::Config::Gen::Modules) on
# Tue Jul 27 10:31:46 2010
# If you edit this file and execute tools/xpp/dahdi_genconf again,
# your manual changes will be LOST.
wctdm24xxp
There is one more configuration file required for DAHDI: /etc/dahdi/system.conf. It
looks like this:
# Specify that we would like DAHDI to generate tones that are
# used in the United States.
loadzone = us
defaultzone = us
# We have 4 FXS ports; configure them to use FXO signaling.
fxoks = 1-4
This configuration assumes the card is being used in the United States.
For some tips on internationalization, see Chapter 9.
If the card you are configuring does not have hardware-based echo cancellation, an-
other line will need to be added to /etc/dahdi/system.conf to enable software-based echo
cancellation:
echocanceller = mg2,1-4
MG2 is the recommended echo canceller that comes with the official
DAHDI package. There is another open source echo canceller out there
that is compatible with DAHDI, called OSLEC (Open Source Line Echo
Canceller). Many people report very good results with the use of
OSLEC. For more information about the installation of OSLEC on your
system, see the website at http://www.rowetel.com/blog/oslec.html.
Now, use the init script to load the proper modules and initialize the hardware:
$ sudo /etc/init.d/dahdi start
Loading DAHDI hardware modules:
wctdm24xxp: [ OK ]
Running dahdi_cfg: [ OK ]
Now that DAHDI has been configured, it is time to move on to the relevant configu-
ration of Asterisk. Once Asterisk is installed, ensure that the chan_dahdi module has
been installed. If it is not loaded in Asterisk, check to see if it exists in /usr/lib/asterisk/
Analog Phones | 101