Working on an install of FreePBX 13 in CentOS 7.3, and I’m using an A200 card. When I run “dahdi show status” it comes up with “UNCONFI” under alarms. I see a similar unconfigured alarm when I run “dahdi_scan”
I can fix it by running these commands, temporarily. It stops working again when I reboot.
chown -R asterisk. /etc/dahdi
Once I do that, if I asterisk -r and do “dahdi show status”, I see no alarms:
localhost*CLI> dahdi show status
Description Alarms IRQ bpviol CRC Fra Codi Options LBO
wrtdm Board 1 OK 0 0 0 CAS Unk 0 db (CSU)/0-133 feet (DSX-1)
And if I do “dahdi show channels” I see all of my ports:
localhost*CLI> dahdi show channels
Chan Extension Context Language MOH Interpret Blocked In Service Description
pseudo default default Yes
1 from-zaptel default Yes
2 from-zaptel default Yes
3 from-zaptel default Yes
4 from-zaptel default Yes
5 from-zaptel default Yes
6 from-zaptel default Yes
7 from-zaptel default Yes
8 from-zaptel default Yes
As soon as I reboot though, it goes right back to having an unconfigured alarm, and my only channel in “dahdi show channels” is psuedo.
Looking at assigned-spans.conf and system.conf in /etc/dahdi, they aren’t being changed after a reboot that I can tell - the modification date and ownership/perms aren’t changed, and looking inside the files they look the same. Same for chan_dahdi.conf in /etc/asterisk
If I just run the chown and fwconsole restart commands mentioned above, that doesn’t fix it. So what is dahdi_genconf doing to fix this, and what might be un-fixing it at boot? Is wanpipe doing something fishy?