DAHDI Config broke PRI settings?

General Help
1

I updated my FreePBX Distro server last night, from 5.211.65-13 to -14. After the update, everything seemed fine, but I got a frantic call this morning from my users reporting that they couldn’t call out or receive incoming calls. Turned out that DAHDI was not loading for my TE134 PRI card. Took me a while to figure out, but the relevant log entries turned up:

[2014-06-17 07:43:42] VERBOSE[6607] loader.c: chan_iax2.so => (Inter Asterisk eXchange (Ver 2))
[2014-06-17 07:43:42] VERBOSE[6607] pbx.c: == Registered application 'DAHDISendKeypadFacility'
[2014-06-17 07:43:42] VERBOSE[6607] pbx.c: == Registered application 'DAHDISendCallreroutingFacility'
[2014-06-17 07:43:42] VERBOSE[6607] sig_wat.c: -- Registered libwat
[2014-06-17 07:43:42] VERBOSE[6607] config.c: == Parsing '/etc/asterisk/chan_dahdi.conf': Found
[2014-06-17 07:43:42] VERBOSE[6607] config.c: == Parsing '/etc/asterisk/chan_dahdi_general.conf': Found
[2014-06-17 07:43:42] VERBOSE[6607] config.c: == Parsing '/etc/asterisk/chan_dahdi_general_custom.conf': Found
[2014-06-17 07:43:42] VERBOSE[6607] config.c: == Parsing '/etc/asterisk/chan_dahdi_channels_custom.conf': Found
[2014-06-17 07:43:42] VERBOSE[6607] config.c: == Parsing '/etc/asterisk/chan_dahdi_groups.conf': Found
[2014-06-17 07:43:42] VERBOSE[6607] config.c: == Parsing '/etc/asterisk/chan_dahdi_additional.conf': Found
[2014-06-17 07:43:42] VERBOSE[6607] chan_dahdi.c: -- Registered channel 1, ISDN PRI signalling
[2014-06-17 07:43:42] VERBOSE[6607] chan_dahdi.c: -- Registered channel 2, ISDN PRI signalling
[2014-06-17 07:43:42] VERBOSE[6607] chan_dahdi.c: -- Registered channel 3, ISDN PRI signalling
[2014-06-17 07:43:42] VERBOSE[6607] chan_dahdi.c: -- Registered channel 4, ISDN PRI signalling
[2014-06-17 07:43:42] VERBOSE[6607] chan_dahdi.c: -- Registered channel 5, ISDN PRI signalling
[2014-06-17 07:43:42] VERBOSE[6607] chan_dahdi.c: -- Registered channel 6, ISDN PRI signalling
[2014-06-17 07:43:42] VERBOSE[6607] chan_dahdi.c: -- Registered channel 7, ISDN PRI signalling
[2014-06-17 07:43:42] VERBOSE[6607] chan_dahdi.c: -- Registered channel 8, ISDN PRI signalling
[2014-06-17 07:43:42] VERBOSE[6607] chan_dahdi.c: -- Registered channel 9, ISDN PRI signalling
[2014-06-17 07:43:42] VERBOSE[6607] chan_dahdi.c: -- Registered channel 10, ISDN PRI signalling
[2014-06-17 07:43:42] VERBOSE[6607] chan_dahdi.c: -- Registered channel 11, ISDN PRI signalling
[2014-06-17 07:43:42] VERBOSE[6607] chan_dahdi.c: -- Registered channel 12, ISDN PRI signalling
[2014-06-17 07:43:42] VERBOSE[6607] chan_dahdi.c: -- Registered channel 13, ISDN PRI signalling
[2014-06-17 07:43:42] VERBOSE[6607] chan_dahdi.c: -- Registered channel 14, ISDN PRI signalling
[2014-06-17 07:43:42] VERBOSE[6607] chan_dahdi.c: -- Registered channel 15, ISDN PRI signalling
[2014-06-17 07:43:42] VERBOSE[6607] chan_dahdi.c: -- Registered channel 16, ISDN PRI signalling
[2014-06-17 07:43:42] VERBOSE[6607] chan_dahdi.c: -- Registered channel 17, ISDN PRI signalling
[2014-06-17 07:43:42] VERBOSE[6607] chan_dahdi.c: -- Registered channel 18, ISDN PRI signalling
[2014-06-17 07:43:42] VERBOSE[6607] chan_dahdi.c: -- Registered channel 19, ISDN PRI signalling
[2014-06-17 07:43:42] VERBOSE[6607] chan_dahdi.c: -- Registered channel 20, ISDN PRI signalling
[2014-06-17 07:43:42] VERBOSE[6607] chan_dahdi.c: -- Registered channel 21, ISDN PRI signalling
[2014-06-17 07:43:42] VERBOSE[6607] chan_dahdi.c: -- Registered channel 22, ISDN PRI signalling
[2014-06-17 07:43:42] VERBOSE[6607] chan_dahdi.c: -- Registered channel 23, ISDN PRI signalling
[2014-06-17 07:43:42] ERROR[6607] chan_dahdi.c: Signalling requested on channel 24 is ISDN PRI but line is in Unknown signalling 896 signalling
[2014-06-17 07:43:42] ERROR[6607] chan_dahdi.c: Unable to register channel '1-24'

I won’t post two copies of that, but it started out “Unable to register channel ‘1-25’.” I tried several times to recreate the configuration in DAHDI Config, setting the group to use 24 channels, like it has been for a year. In crisis mode, I was finally able to edit chan_dahdi_groups.conf manually to get calls flowing. The original line was channel =>1-25 so I changed it to channel =>1-24. That still gave the same error, so I changed it again, to channel =>1-23 to get things working.

So, is this a DAHDI Config bug introduced in the update?

Thanks,
Corey

2

Can you go in to the Dahdi config module and provide a screenshot of your digital spans

3

Between FreePBX Distro 5.211.65-13 and FreePBX Distro 5.211.65-14, apart the update of Asterisk 11.9.0 to Asterisk 11.10.2, the libpri was updated; here the yum.log from my system (I don’t have a PRI line…just a BRI line and nothing bad happened):

  • Jun 14 10:31:46 Updated: libpri-1.4.12-13.shmz65.1.3.x86_64
  • Jun 14 10:31:46 Updated: libpri-devel-1.4.12-13.shmz65.1.3.x86_64
  • Jun 14 10:31:47 Updated: libpri-debuginfo-1.4.12-13.shmz65.1.3.x86_64

It shouldn’t something that references to DAHDI Config Module version (2.11.42 or 2.11.43 if you updated very recently), but mine should be really a question than a statement (I’m still with DAHDI Config 2.11.42…).

About the B Channels: on T1 shouldn’t be 23 B Channel and the 24th channel is the D Channel used for ISDN Signalling? so setting available Channels from 1 to 23 should be right.

4

Same problem here. Had to change chan_dahdi_groups.config > channel =>1-2 ; it was channel =>1-3.
Here is the screenshot with setting that creates =>1-2

5

Which DAHDI Config module version does your system have (2.11.42 or 2.11.43)?

Mine (working) below with DAHDI 2.11.42 and an HFC-S PCI ISDN BRI Card…

6

Mine is 2.11.43

7

OK so looks like something on the dahdi module in FreePBX is broke. @tm1000

8

I’m on DAHDI config 2.11.43.

The problem with putting a lower number here is that the module always adds a group to fill it out to 24. So, even if I set Group 0 to 23, the module will add a Group 1 with one channel. And, that same logic really blows up if you try to change the channel count on a group that is already saved.

So, I ended up with the manual fix.

9

So When I was fixing a few issues last month I apparently introduced this little quirk of adding 1. I have corrected this and added an “s” option to create a skip group. So if you wish to skip the remainder of channels just set the Group to “s”.

This is in QA at the moment and I will update everyone when it is released.

10

I just updated my primary and secondary server tonight from 5.211.65-12 to 5.211.65-14 and found both PRI’s out of service. Let’s just say i’ve never felt panic like that before when both went down, luckily a google search instantly brought this up and it’s taught me a valuable lesson! - I’ll be planning this better next time and will wait till the scripts are a few weeks old before installing them.

The config on both of my systems had changed to

channel = 1-31

It should have been

channel = 1-15,17-31

I’m running a standard QSIG PRI

Does this mean any interface change I make will write the bug back (until a new update is put out)?

11

Yes please don’t download or make any changes until I properly QA this whole thing. It’s honestly turned into a bit of a nightmare.

12

Just downloaded 1h ago :
DAHDi Config 2.11.43 Schmooze Com Inc Online upgrade available (2.11.44)

Applied and changed something in config but still get wrong channels on my OpenVox B400P:

channel =>1-3
channel =>10-12

but should be:
channel =1-2
channel =10-11

13

Please see my message above.

14

Everything should be fixed in 2.11.45. I hope. I really really really hope

15

I applied it about an hour ago, and went through the motions of updating my config to be sure the files came out right. Everything looks great. I did click the “Reset Groups” link, and nothing seemed to happen, but I might be misunderstanding what it’s supposed to do.

Thank you for your very quick help on this.

Corey

16

Yes, I saw afterwards !
And after a long night (being new to Asterisk) I finally found the culprit part was the wrong channel count from your Dahdi beeing written.
But when you haven’t seen a lot of dahdi configs it’s not easy to figure out, specially because I rolled back a lot of older and working backups and it still didn’t work !
I guess it’s because once they’re loaded you start to write out the conf file again.

Q: Is there a way to rollback to earlier versions of Asterisk modules if something happends again ?

Thanks for your fast response !

17

Module Rollback is (should be) a feature of FreePBX 12, it’s not available on FreePBX 2.11, AFAIK reading other threads on the argument.

Not a consideration that let us to avoid a “regression experience” once a FreePBX Module update has been done and the system starts to experience some sort of issue related to it…but would be still interesting to have a way to know the FreePBX Module Changelog before to apply that update manually, especially if the update operation is done via CLI (via FreePBX GUI - Module Admin that happens yet): at least reading the changelog should help us to decice when and if perform that update.

18

Applied 2.11.45 changed Dahdi / channel parameters pressed Apply and verified that the channels were writtend correctly.
Everything fixed for me !

Thanks, great work.

19

Good to know, I suggest to present a text version of the change log while updating via CLI and a second confirmation if he really wants to do it.
But rollback is still critical, because guessing from what can go wrong by reading the change log is still hard :wink:

20

You probably have to clear your cache for that to work. You can always see JavaScript errors by bringing up the JavaScript console as well.