FreePBX DAHDI card not connecting
-
Yesterday we had an accidental reboot of our FreePBX server. Yes, I wasn't paying attention and power cycled the machine. Anyway...
Once the machine came back online the DAHDI card won't connect. It shows the card but I cannot edit anything. Internal calls all work.
@JaredBusch Any kick in the right direction to get this back online would be helpful.
-
@wls-itguy said in FreePBX DAHDI card not connecting:
Yesterday we had an accidental reboot of our FreePBX server. Yes, I wasn't paying attention and power cycled the machine. Anyway...
Once the machine came back online the DAHDI card won't connect. It shows the card but I cannot edit anything. Internal calls all work.
@JaredBusch Any kick in the right direction to get this back online would be helpful.
Checking the status of the dahdi service I get this:
[root@pbxhost ~]# systemctl start dahdi Job for dahdi.service failed because the control process exited with error code. See "systemctl status dahdi.service" and "journalctl -xe" for details.
checking for details:
[root@pbxhost ~]# systemctl status dahdi.service ā dahdi.service - LSB: DAHDI kernel modules Loaded: loaded (/etc/rc.d/init.d/dahdi; bad; vendor preset: disabled) Active: failed (Result: exit-code) since Wed 2022-02-02 10:26:28 CST; 1min 47s ago Docs: man:systemd-sysv-generator(8) Process: 5799 ExecStart=/etc/rc.d/init.d/dahdi start (code=exited, status=1/FAILURE) Feb 02 10:26:28 pbxhost.url.local dahdi[5799]: wcb4xxp: [ OK ] Feb 02 10:26:28 pbxhost.url.local dahdi[5799]: wctc4xxp: [ OK ] Feb 02 10:26:28pbxhost.url.local dahdi[5799]: xpp_usb: modprobe: FATAL: Module xpp_usb not found. Feb 02 10:26:28 pbxhost.url.local dahdi[5799]: [FAILED] Feb 02 10:26:28 pbxhost.url.local dahdi[5799]: Running dahdi_cfg: DAHDI_SPANCONFIG failed on span 1: No suc... (6) Feb 02 10:26:28 pbxhost.url.local dahdi[5799]: [FAILED] Feb 02 10:26:28 pbxhost.url.local systemd[1]: dahdi.service: control process exited, code=exited status=1 Feb 02 10:26:28 pbxhost.url.local systemd[1]: Failed to start LSB: DAHDI kernel modules. Feb 02 10:26:28pbxhost.url.local systemd[1]: Unit dahdi.service entered failed state. Feb 02 10:26:28 pbxhost.url.local systemd[1]: dahdi.service failed. Hint: Some lines were ellipsized, use -l to show in full.
checking Journal:
[root@pbxhost ~]# journalctl -xe Feb 02 10:29:01 pbxhost.url.local systemd[1]: Started Session 3726 of user asterisk. -- Subject: Unit session-3726.scope has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit session-3726.scope has finished starting up. -- -- The start-up result is done. Feb 02 10:29:01 pbxhost.url.local CROND[6367]: (asterisk) CMD (/usr/sbin/fwconsole queuestats --syncall >> /tmp/rea Feb 02 10:29:01 pbxhost.url.local CROND[6368]: (asterisk) CMD (/usr/local/sbin/fwconsole pms wu_alert > /dev/null 2 Feb 02 10:29:01 pbxhost.url.local CROND[6369]: (asterisk) CMD ([ -e /usr/sbin/fwconsole ] && sleep $((RANDOM%30)) & Feb 02 10:29:10 pbxhost.url.local crontab[6409]: (asterisk) LIST (asterisk) Feb 02 10:29:10 pbxhost.url.local crontab[6411]: (asterisk) LIST (asterisk) Feb 02 10:29:10 pbxhost.url.local crontab[6413]: (asterisk) LIST (asterisk) Feb 02 10:29:10 pbxhost.url.local crontab[6415]: (asterisk) LIST (asterisk) Feb 02 10:29:10 pbxhost.url.local crontab[6417]: (asterisk) LIST (asterisk) Feb 02 10:29:10 pbxhost.url.local crontab[6418]: (asterisk) REPLACE (asterisk) Feb 02 10:29:10 pbxhost.url.local crontab[6420]: (asterisk) LIST (asterisk) Feb 02 10:29:10 pbxhost.url.local crontab[6422]: (asterisk) LIST (asterisk) Feb 02 10:29:10 pbxhost.url.local crontab[6423]: (asterisk) REPLACE (asterisk) Feb 02 10:29:10 pbxhost.url.local crontab[6425]: (asterisk) LIST (asterisk) Feb 02 10:29:10 pbxhost.url.local systemd[1]: Removed slice User Slice of asterisk. -- Subject: Unit user-995.slice has finished shutting down -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit user-995.slice has finished shutting down.
-
@wls-itguy I have not touched a DAHDI card in 10 years.
-
Make sure the OS can even see the card(s)?
lspci
-
@jaredbusch said in FreePBX DAHDI card not connecting:
Make sure the OS can even see the card(s)?
lspci
[root@pbxhost ~]# lspci 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor DRAM Controller (rev 09) 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09) 00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04) 00:16.0 Communication controller: Intel Corporation 7 Series/C216 Chipset Family MEI Controller #1 (rev 04) 00:16.3 Serial controller: Intel Corporation 7 Series/C210 Series Chipset Family KT Controller (rev 04) 00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network Connection (Lewisville) (rev 04) 00:1a.0 USB controller: Intel Corporation 7 Series/C216 Chipset Family USB Enhanced Host Controller #2 (rev 04) 00:1b.0 Audio device: Intel Corporation 7 Series/C216 Chipset Family High Definition Audio Controller (rev 04) 00:1c.0 PCI bridge: Intel Corporation 7 Series/C216 Chipset Family PCI Express Root Port 1 (rev c4) 00:1c.4 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 5 (rev c4) 00:1d.0 USB controller: Intel Corporation 7 Series/C216 Chipset Family USB Enhanced Host Controller #1 (rev 04) 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev a4) 00:1f.0 ISA bridge: Intel Corporation C216 Series Chipset LPC Controller (rev 04) 00:1f.2 RAID bus controller: Intel Corporation SATA Controller [RAID mode] (rev 04) 00:1f.3 SMBus: Intel Corporation 7 Series/C216 Chipset Family SMBus Controller (rev 04) 02:00.0 PCI bridge: PLX Technology, Inc. PEX8112 x1 Lane PCI Express-to-PCI Bridge (rev aa) 03:04.0 Network controller: Sangoma Technologies Corp. A200/Remora FXO/FXS Analog AFT card
Doesn't look like it even sees the card.
-
@wls-itguy said in FreePBX DAHDI card not connecting:
03:04.0 Network controller: Sangoma Technologies Corp. A200/Remora FXO/FXS Analog AFT card
Do you also have an FXS/FXO card?
-
Not anymore those got removed when we got rid of the POTS lines.
-
Turns out the updated kernel doesn't like the Dahdi card. So support had to roll back the kernel version until the engineering team fixes it. No kernel updates for me until then.
-
@wls-itguy said in FreePBX DAHDI card not connecting:
Turns out the updated kernel doesn't like the Dahdi card. So support had to roll back the kernel version until the engineering team fixes it. No kernel updates for me until then.
How can you get kernel updates on CentOS? I thought you'd only get security patches on the same kernel. Exactly for the reason to avoid the problem you had.
-
@pete-s said in FreePBX DAHDI card not connecting:
@wls-itguy said in FreePBX DAHDI card not connecting:
Turns out the updated kernel doesn't like the Dahdi card. So support had to roll back the kernel version until the engineering team fixes it. No kernel updates for me until then.
How can you get kernel updates on CentOS? I thought you'd only get security patches on the same kernel. Exactly for the reason to avoid the problem you had.
Did you mean on FreePBX?
-
@pete-s said in FreePBX DAHDI card not connecting:
@wls-itguy said in FreePBX DAHDI card not connecting:
Turns out the updated kernel doesn't like the Dahdi card. So support had to roll back the kernel version until the engineering team fixes it. No kernel updates for me until then.
How can you get kernel updates on CentOS? I thought you'd only get security patches on the same kernel. Exactly for the reason to avoid the problem you had.
@dashrender said in FreePBX DAHDI card not connecting:
@pete-s said in FreePBX DAHDI card not connecting:
@wls-itguy said in FreePBX DAHDI card not connecting:
Turns out the updated kernel doesn't like the Dahdi card. So support had to roll back the kernel version until the engineering team fixes it. No kernel updates for me until then.
How can you get kernel updates on CentOS? I thought you'd only get security patches on the same kernel. Exactly for the reason to avoid the problem you had.
Did you mean on FreePBX?
I have Update Manager module and this is the kernel header they rolled back to:
kernel-headers.x86_64 3.10.0.1127.10.1.el7. The newest release is 3.10.0-1127.19.1.el7 which is the one that has the issue with my Dahdi card.
-
@wls-itguy said in FreePBX DAHDI card not connecting:
I have Update Manager module and this is the kernel header they rolled back to:
kernel-headers.x86_64 3.10.0.1127.10.1.el7. The newest release is 3.10.0-1127.19.1.el7 which is the one that has the issue with my Dahdi card.
Total Linux Noob here - is that really a new kernel or just a patched kernel? Hell is there a difference?
-
@dashrender said in FreePBX DAHDI card not connecting:
Total Linux Noob here - is that really a new kernel or just a patched kernel? Hell is there a difference?
Good question. Maybe @JaredBusch can answer that one.
-
@dashrender said in FreePBX DAHDI card not connecting:
Total Linux Noob here - is that really a new kernel or just a patched kernel? Hell is there a difference?
Every patch is a new kernel.
-
@wls-itguy said in FreePBX DAHDI card not connecting:
@dashrender said in FreePBX DAHDI card not connecting:
Total Linux Noob here - is that really a new kernel or just a patched kernel? Hell is there a difference?
Good question. Maybe @JaredBusch can answer that one.
3.10 is the linux kernel and 0 is the minor revision. Those numbers are from the linux kernel team. 1127 the patch number (Redhat's I think). The rest of the numbers is redhat's numbering scheme.
So Linux kernel team makes the kernel. And they maintain it for a couple of years - if it's a LTS kernel.
Redhat takes the stable kernel and adjust it for their use. Then Redhat maintains their kernel themselves by backporting security patches to it forever - long after the kernel is EOL.
That's why I'm surprised it broke hardware support because that exactly why Redhat sticks to the same old kernel for many, many years. They don't want to break anything.
Here you can see what kernel version each release is using.
-
@pete-s
Doesn't FreePBX use their own distro though? Or is that something different?
-
@wls-itguy said in FreePBX DAHDI card not connecting:
@pete-s
Doesn't FreePBX use their own distro though? Or is that something different?
I don't know. I was always under the impression it was CentOS, which until recently is the same as RedHat Enterprise Linux.
I'm sure @JaredBusch knows more.
-
@pete-s said in FreePBX DAHDI card not connecting:
@wls-itguy said in FreePBX DAHDI card not connecting:
@pete-s
Doesn't FreePBX use their own distro though? Or is that something different?
I don't know. I was always under the impression it was CentOS, which until recently is the same as RedHat Enterprise Linux.
I'm sure @JaredBusch knows more.
FreePBX is Sangoma 7, a fork of CentOS 7.
They had a private alpha of FreePBX 15 or 16 built on CentOS 8 that was never public. That was killed when RedHat killed CentOS 8.FreePBX 16 is still Sangoma 7, but with PHP 7.4 ported in and a few other updates.
There has been no announcement yet, but a few threads on, choosing a new fork to go forward with.