DAHDI

DAHDI is the replacement for Zaptel made by Digium. More information about this change is: Zaptel project being renamed to DAHDI.

Note -> Since AstLinux 1.1.0 the DAHDI Perl scripts “dahdi_genconf” and “dahdi_hardware” can be used to generate and verify a DAHDI configuration.

Note -> Since AstLinux 1.4.0 (DAHDI 3.1) “dahdi_hfcs” is no more included!

When moving from an existing Zaptel install, see below: Moving from Zaptel to DAHDI

This page explains the proper way to set up your DAHDI device on Astlinux systems. We assume at this point that you have a working Astlinux system and are able to retain password changes over a reboot (ie. persistent storage is configured).

Please read this next step very carefully:

• If you've used the web interface to configure your system, the configuration file to edit is /mnt/kd/rc.conf.d/user.conf
• If you've ONLY used the CLI to create your configuration, you will have a single /mnt/kd/rc.conf file and NO /mnt/kd/rc.conf.d directory, so the configuration file to edit is /mnt/kd/rc.conf
• If the /mnt/kd/rc.conf.d directory exists, DO NOT use /mnt/kd/rc.conf

Never edit ''/etc/rc.conf'' directly!

Edit <configfile>.conf as determined above. Add or change DAHDIMODS to the correct value.

Examples:

# OLD Digium 400p (and clones)
DAHDIMODS="wctdm"

# NEW Digium cards 410p, etc.
DAHDIMODS="wctdm24xxp"

# Rhino 8 and 24 port analog cards
DAHDIMODS="rcbfx"

# 2-8 port HFC-multi BRI cards (formerly supported by mISDN with "hfcmulti")
DAHDIMODS="wcb4xxp dahdi_echocan_oslec"

# Since AstLinux 1.0.3 up to AstLinux 1.3.10: Single port HFC-S BRI cards (formerly supported by mISDN with "hfcpci" (unofficial 3rd-party driver))
DAHDIMODS="dahdi_hfcs dahdi_echocan_oslec"

Create a system.conf file in /mnt/kd/dahdi. This will be used after rebooting. Create or edit a chan_dahdi.conf file in /mnt/kd/asterisk/.

These two files correspond to /etc/dahdi/system.conf, and /etc/asterisk/chan_dahdi.conf in a non-AstLinux Asterisk installation. Edit these files according to the DAHDI documentation.

Note -> From AstLinux 0.7 or later.

Moving from Zaptel to DAHDI is pretty straightforward. The names of the files have changed and the channel names have changed. (NOTE that for Asterisk 1.4, you can use ZAP/X for your channel declarations, but this is deprecated, so you should move to DAHDI/X).

• zaptel.conf (/mnt/kd/zaptel.conf) is now called system.conf. Simply rename /mnt/kd/zaptel.conf to /mnt/kd/dahdi/system.conf.
• /etc/asterisk/zapata.conf should be renamed to chan_dahdi.conf
• Edit your dialplan and change Zap/XX references to DAHDI/XX
• Change ZAPMODS to DAHDIMODS in your /mnt/kd/rc.conf.d/user.conf file (or /mnt/kd/rc.conf)
• Reboot your system

DAHDI does not configure an echo cancellation method by default. If your DAHDI hardware does not have hardware echo cancellation, you will need to specify this in the system.conf file.

Valid echo cancellers are: mg2, kb1, sec2, sec and oslec. Specify as follows:

echocanceller=mg2,1-8

This specifies use of the mg2 echo canceller on channels 1-8.