If you are editing
/etc/dahdi/system.conf file
and
/etc/asterisk/chan_dahdi_groups.conf
Well anything dahdi related (and there are very good reasons to do that, for many reasons) then you will need to disable/uninstall/delete the “dahdi helper module” in FreePBX as it will overwrite them on a reboot.
As far as I know you are right about this but ever since one of the recent updates my DAHDI stuff doesn’t survive a reboot and it used to and it’s normal behavior for these files to be rewritten like that…
They recently updated in the distro wanpipe to 7.0.14 (latest version from Sangoma is 7.0.15 and the version we had before was 7.0.12) and a lot of the DAHDI tools and I guess one of these updates is causing NDSiouxFan and me problems…
I also got the latest batch of updates to FreePBX modules today (and there were quite a few) but I doubt it is that…
Did you try my suggestion yet? Once it has “helped” you, you can disable it or it will “help you again” every reboot . Any changes you want must be done in the GUI if it is enabled, when disabled then those files will be stable over a reboot.
Thanks guys. I restored my .conf files and reloaded, and got my analog lines to work. Nick, I am running with a OpenVox card with 4 FXO ports connected to my PSTN.
Dicko, I do not see a “dahdi helper module” in my Module Admin. If I disable my “dahdi config” in module administration, I do not lose my analog channels upon disable, and it survives a reboot, but then I do not have access to look at my DAHDI channels under Connectivity.
Did you recently update your packages? I had a few news dahdi* packages installed a few days ago and this was my first reboot since then…
In my case simply doing a “fwconsole restart” once the machine was booted did the trick… The files we talked about had the right permissions but I have not checked their content yet…
Nick - This is a development stage PBX not in service yet, so I have been installing the distro and running all of the updates. After I rebooted, it appeared that my .conf files were overwritten. A “fwconsole restart” did not bring it back until I restored my dahdi .conf files. I then ran a “fwconsole restart” and my analog channels came back. FreePBX indicated that I had new hardware, and the channels would not work until I went in and did an Edit under DAHDI Config. I was able to make (and receive) PSTN calls after I did an Edit.
I copied the entire working configuration and the entire non working configuration…
No difference…
The problem does not behave in exactly the same way for me and David but then there is special support for Sangoma hardware in the FreePBX/FreePBX distro scripts and my card is a Sangoma A200.
The good old non “dahdi helper” sangoma install works fine, coincidentally I did it today for a real world client . . . 2x4 port hardware with EC, everything worked perfectly.
Personally I call that DAHDI helper non-native support… Now that FreePBX is under Sangoma I hope they will eventually add real native support…
There are quite a few settings like Hardware EC DTMF support we can’t set when using it…
dicko, they not only updated the wanpipe drivers but a lot of dahdi* packages, I am assuming these might be the cause of the problem…
I could turn off Sangoma DAHDI support but I don’t expect it would make any difference because the files that are generated for a working config and a non-working config are identical…
(under /etc/dahdi, /etc/asterisk and /etc/wanpipe…)
It look like something gets incorrectly initialized at boot (or maybe it’s some sort of permission problem, I also got those “Permission denied” messages IIRC…).
Because Sangoma and FreePBX are all in the same stable, then hopefully they will get it working eventually, I can assure you I have successfully used both Sangoma hardware and FreePBX for many years, I am very happy with both of them , but because of old habits and distrust of the dahdi helper module’s completeness, I just do it outside of the FreePBX dahdi module, end of problem, works like a champ.
It is very incomplete, there are quite a few parameter like hardware DTMF and detection which can’t be set for example with it and it looks like with more recent drivers there are other new options which cannot be configured from here…
And it did for me too, removing dahdi-config and setuping manually is the only thing that works…
I would have like to go the FreePBX way but I can’t afford to have a server which won’t survive a reboot and my ticket was just today assigned to someone…
Well it was American thanksgiving so perhaps they should have assigned it to a Canadian/Sangoma dude, I believe they did that holiday a couple of weeks ago (I kinda like setuping Eh! )