Voicespan

If, like our Foncordiax product, your Asterisk-based PBX utilises the excellent Flash Operator Panel to give a visual representation of what’s happening on your phone system (including trunk utilisation, extensions, parking lots and more), then you may have noticed that DAHDI trunks don’t appear. It had me stumped for a bit, but Google is most definitely your friend in this case. Below is a simple fix that sorted the problem for me, and I hope it does so for you too.

Firstly, though, you need shell access and an account with high enough permissions to execute the command below…root would be good

• Using your favourite editor, I like nano, edit /etc/asterisk/asterisk.conf
• Change ‘dahdichanname = yes’ to ‘dahdichanname = no’ then save and exit
• Also in /etc/asterisk, execute ‘ln -s chan_dahdi.conf zapata.conf ‘ to create a symbolic link from chan_dahdi.conf to zapata.conf

That’s about it. If you are running FreePBX then you just need to open the trunk, click on ’submit’ and then ‘apply changes’ and your DAHDI trunks should now appear (cleverly disguised as ZAP trunks!). For other flavours you may have to restart DAHDI and/or Asterisk.

EDIT

***Important*** Care is needed with this fix. I made the change above on a system I was prepping for an installation and afterwards any outbound calls on a DADHI channel failed. I spent a lot of time wondering if the analogue line was iffy, but eventually tried reversing the asterisk.conf edit, and that fixed the issue. Of course it meant that FOP no longer showed activity on the ZAP trunks. I suspect that the dial command was trying to use a DAHDI channel, but internally all DAHDI channels were renamed to ZAP channels. When I sort out a fix I’ll post the results.