dadhi_genconf conflicts with FreePBX - solution

This is a temporary solution until dahdi_genconf and FreePBX can work out an agreement on the dahdi configuration:


dahdi_genconf creates /etc/dahdi/system.conf (similar to old /etc/zaptel.conf) and /etc/asterisk/dahdi_channels.conf (similar to old /etc/asterisk/zapata-auto.conf).

Unfortunately, /etc/asterisk/dahdi_channels.conf throws a lot of "default"settings in that really shouldn’t be there such as fxs signaling, extension numbering (starting at 4001), mailboxes, T1 trunking configuration, etc…

FreePBX generates /etc/asterisk/chan_dahdi.conf and /etc/asterisk/chan_dahdi_additional.conf where the extensions, FXS signaling , etc. is configured. These are the files that should hold this information not /etc/asterisk/dahdi_channels.conf which causes conflicts resulting in none of the dahdi channels being registered.

If you have a problem with dahdi channels, view the /var/log/asterisk/full file (full is the filename). It has great information on why a dahdi channel fails to register. If one channel fails, all fail! Be warned, /var/log/asterisk/full is a LARGE text file (usually 1 to 4 MB), search for the term “dahdi”. Typically right after there will be the loading/registering of the dahdi channels and clues as to why it didn’t get loaded/registered. (I usually delete the contents and reload asterisk to get a small 240 kB file to look at).

SOLUTION: erase all fxs configuration from /etc/asterisk/dahdi_channels.conf. I suggest using it for configuring only the fxo lines as there doesn’t seem to be anyplace to do this yet.

Here’s the latest up to date dahdi documents

and if you’ve ever wondered exactly what the T1 alarms mean (yellow, red, blue, etc…) here’s where you find it at the Dahdi Telephony Interface page