[SOLVED] FreePBX Distro 5.211.65-14 upgraded to 5.211.65-15: zaphfc module was removed from DAHDI

Hello,

today I upgraded FreePBX Distro 5.211.65-14 to 5.211.65-15 by downloading the relevant upgrade script (Upgrade script with the 24.07.2014 timestamp).

The upgrade went well but after reboot I discovered that while (the new) Asterisk 11.11.0 looks running the DAHDI configuration module doesn’t show my ISDN Card anymore and I’m not able to restart DAHDI service from FreePBX GUI (DAHDI Config Module) because FreePBX thinks the Asterisk is not running.

This situation looks like [this one][1] (thread closed yet), which I though was already solved (I touched the /etc/asterisk/ooh323.conf file which, as expected, wasn’t there and then I restarted both Asterisk and DAHDI, gone green) but it seems not.

Here Asterisk and DAHDI service restart/reload:

[[email protected] /]# service asterisk restart
Stopping safe_asterisk:                                    [  OK  ]
Shutting down asterisk:                                    [  OK  ]
Starting asterisk:                                         [  OK  ]
[[email protected] /]# service asterisk reload
[[email protected] /]# service dahdi reload
Rerunning dahdi_cfg:                                       [  OK  ]
[[email protected] /]# service dahdi restart
Unloading DAHDI hardware modules: done
Loading DAHDI hardware modules:
  wct4xxp:                                                 [  OK  ]
  opvxd115:  FATAL: Module opvxd115 not found.
                                                           [FAILED]
  wcte12xp:                                                [  OK  ]
  wcte13xp:                                                [  OK  ]
  wct1xxp:                                                 [  OK  ]
  wcte11xp:                                                [  OK  ]
  tor3e:  FATAL: Module tor3e not found.
                                                           [FAILED]
  r1t1:                                                    [  OK  ]
  rxt1:                                                    [  OK  ]
  wctdm24xxp:                                              [  OK  ]
  wcfxo:                                                   [  OK  ]
  wctdm:                                                   [  OK  ]
  opvxa24xx:  FATAL: Module opvxa24xx not found.
                                                           [FAILED]
  opvxa1200:  FATAL: Module opvxa1200 not found.
                                                           [FAILED]
  rcbfx:                                                   [  OK  ]
  zaphfc:  FATAL: Module zaphfc not found.
                                                           [FAILED]
  wcb4xxp:                                                 [  OK  ]
  wctc4xxp:                                                [  OK  ]
  xpp_usb:                                                 [  OK  ]

Running dahdi_cfg:                                         [  OK  ]

I think DAHDI configuration is still OK (available) (indeed I see it on DAHDI Configuration Module, nothing has changed) BUT it seems that zaphfc module is gone away…(DAHDI Configuration should load it with a all others…but I can’t see it with lsmod…other modules are there but not the zaphfc one).

I also see this dmesg messages:

dahdi: Version: 2.9.2 dahdi: Telephony Interface Registered on major 196 dahdi_transcode: Loaded. dahdi_transcode: Unloaded. dahdi: Telephony Interface Unloaded dahdi: Version: 2.9.2 dahdi: Telephony Interface Registered on major 196 dahdi_transcode: Loaded. dahdi_transcode: Unloaded. dahdi: Telephony Interface Unloaded dahdi: Version: 2.9.2 dahdi: Telephony Interface Registered on major 196 dahdi_transcode: Loaded. dahdi_transcode: Unloaded. dahdi: Telephony Interface Unloaded dahdi: Version: 2.9.2 dahdi: Telephony Interface Registered on major 196 dahdi_transcode: Loaded. dahdi_transcode: Unloaded. dahdi: Telephony Interface Unloaded dahdi: Version: 2.9.2 dahdi: Telephony Interface Registered on major 196 dahdi_transcode: Loaded.

What’s up?

Could be an issue with new Asterisk or new Kernel?

The Upgrade Script to FreePBX Distro 5.211.65-15 updated these system packages:

Jul 30 15:55:56 Updated: asterisk11-core-11.11.0-1.shmz65.1.18.x86_64 Jul 30 15:55:56 Updated: asterisk11-addons-core-11.11.0-1.shmz65.1.18.x86_64 Jul 30 15:55:56 Updated: asterisk11-addons-mysql-11.11.0-1.shmz65.1.18.x86_64 Jul 30 15:55:57 Updated: asterisk11-addons-ooh323-11.11.0-1.shmz65.1.18.x86_64 Jul 30 15:55:57 Updated: asterisk11-voicemail-11.11.0-1.shmz65.1.18.x86_64 Jul 30 15:55:57 Updated: asterisk11-dahdi-11.11.0-1.shmz65.1.18.x86_64 Jul 30 15:55:57 Updated: asterisk11-doc-11.11.0-1.shmz65.1.18.x86_64 Jul 30 15:55:57 Updated: asterisk11-11.11.0-1.shmz65.1.18.x86_64 Jul 30 15:55:57 Updated: asterisk11-addons-bluetooth-11.11.0-1.shmz65.1.18.x86_64 Jul 30 15:55:57 Updated: asterisk11-addons-11.11.0-1.shmz65.1.18.x86_64 Jul 30 15:55:57 Updated: asterisk11-flite-11.11.0-1.shmz65.1.3.x86_64 Jul 30 15:55:57 Updated: asterisk11-curl-11.11.0-1.shmz65.1.18.x86_64 Jul 30 15:55:57 Updated: asterisk11-odbc-11.11.0-1.shmz65.1.18.x86_64 Jul 30 15:55:57 Updated: asterisk11-flite-debuginfo-11.11.0-1.shmz65.1.3.x86_64 Jul 30 15:56:28 Updated: dahdi-linux-2.9.2-37.shmz65.1.12.x86_64 Jul 30 15:56:28 Updated: dahdi-tools-2.9.2-42.shmz65.1.11.x86_64 Jul 30 15:56:48 Updated: wanpipe-7.0.10-1kernel.2.6.32.431.el6.dahdi.2.9.2.rel.1.shmz65.1.25.x86_64 Jul 30 15:56:48 Updated: dahdi-linux-kmod-debuginfo-2.9.2-20_centos6.2.6.32_431.el6.x86_64.x86_64 Jul 30 15:56:48 Updated: dahdi-tools-doc-2.9.2-42.shmz65.1.11.x86_64 Jul 30 15:56:48 Updated: dahdi-linux-debuginfo-2.9.2-37.shmz65.1.12.x86_64 Jul 30 15:56:49 Updated: dahdi-tools-debuginfo-2.9.2-42.shmz65.1.11.x86_64 Jul 30 15:56:49 Updated: dahdi-linux-devel-2.9.2-37.shmz65.1.12.x86_64 Jul 30 15:57:38 Updated: libpri-1.4.12-13.shmz65.1.4.x86_64 Jul 30 15:57:38 Updated: libtonezone-2.9.2-42.shmz65.1.11.x86_64 Jul 30 15:57:38 Updated: libtonezone-devel-2.9.2-42.shmz65.1.11.x86_64 Jul 30 15:57:38 Updated: libpri-devel-1.4.12-13.shmz65.1.4.x86_64 Jul 30 15:57:39 Updated: fail2ban-0.8.8-106.shmz65.1.116.noarch Jul 30 15:57:43 Updated: kmod-dahdi-linux-2.9.2-20_centos6.2.6.32_431.el6.x86_64.x86_64 Jul 30 15:57:53 Updated: sysadmin-2.7.0-200.shmz65.1.5.noarch Jul 30 15:57:54 Updated: libpri-debuginfo-1.4.12-13.shmz65.1.4.x86_64

on my fully up-to-date FreePBX Distro 5.211.64-14.

I noticed, by performing a yum upgrade, that some packages would be upgraded (after the Upgrade Script yum process yet done):

---> Package dahdi-tools.x86_64 0:2.9.2-42.shmz65.1.11 will be updated ---> Package dahdi-tools.x86_64 0:2.9.2-42.shmz65.1.12 will be an update ---> Package dahdi-tools-debuginfo.x86_64 0:2.9.2-42.shmz65.1.11 will be updated ---> Package dahdi-tools-debuginfo.x86_64 0:2.9.2-42.shmz65.1.12 will be an update ---> Package dahdi-tools-doc.x86_64 0:2.9.2-42.shmz65.1.11 will be updated ---> Package dahdi-tools-doc.x86_64 0:2.9.2-42.shmz65.1.12 will be an update ---> Package libtonezone.x86_64 0:2.9.2-42.shmz65.1.11 will be updated ---> Package libtonezone.x86_64 0:2.9.2-42.shmz65.1.12 will be an update ---> Package libtonezone-devel.x86_64 0:2.9.2-42.shmz65.1.11 will be updated ---> Package libtonezone-devel.x86_64 0:2.9.2-42.shmz65.1.12 will be an update

So I did those updates and now DAHDI is come back BUT no digital hardware is shown in FreePBX, the ISDN PCI board the system has is OK because I’m able to see it with dahdi_hardware command:

pci:0000:05:00.0 zaphfc- 1397:2bd0 HFC-S ISDN BRI card

But zaphfc- make me think that there is a module issue here.
[1]: [SOLVED] Yummed to Asterisk 11.11 tonight - Yikes!

We no longer are patching DAHDI for openvox as their patches are failing for 2.9.2 so we removed them after they ignored us for 2 weeks on getting us updated patches. Those modules were included from the openvox patch in the past.

Go into dahdi module in FreePBX and tell it to not load those modules anymore.

OK, I test now…but I never considered (watched) OpenVOX modules, leaving them (as many others) loaded by default (in DAHDI Config Modules Settings): even if my system is loading various modules it uses only the zaphfc (due to the installed ISDN PCI Card).

OK, unselected: opvxd115, opvxa24xx and opvxa1200 and now the system is rebooting after the changes were applied.

1 Like

So I should remove those right?

Still no DAHDI Hardware…lsmod shows no opv* modules loaded anymore but neither the zaphfc!

As you can see DAHDI Config Modules didn’t loaded any opv* modules after the system reboot.

Ohhh…maybe I should disabe also the tor3e (used by Allo 1,2 and 4 port T1/E1/J1 card) module?

opvxd115:  FATAL: Module opvxd115 not found. tor3e:  FATAL: Module tor3e not found. opvxa24xx:  FATAL: Module opvxa24xx not found. opvxa1200:  FATAL: Module opvxa1200 not found.

but, please, do not remove the zaphfc module (the /etc/dahdi/modules shows that zaphfc is used also by OpenVox B100P: 1 NT/TE BRI ports card…but not only for running cards of OpenVox!).

zaphfc:  FATAL: Module zaphfc not found.

Indeed here is what I obtain with a DAHDI service restart:

[[email protected] /]# service dahdi restart Unloading DAHDI hardware modules: done Loading DAHDI hardware modules:   wct4xxp:                                                 [  OK  ]   wcte12xp:                                                [  OK  ]   wcte13xp:                                                [  OK  ]   wct1xxp:                                                 [  OK  ]   wcte11xp:                                                [  OK  ]   tor3e:  FATAL: Module tor3e not found.                                                            [FAILED]   r1t1:                                                    [  OK  ]   rxt1:                                                    [  OK  ]   wctdm24xxp:                                              [  OK  ]   wcfxo:                                                   [  OK  ]   wctdm:                                                   [  OK  ]   rcbfx:                                                   [  OK  ]   zaphfc:  FATAL: Module zaphfc not found.                                                            [FAILED]   wcb4xxp:                                                 [  OK  ]   wctc4xxp:                                                [  OK  ]   xpp_usb:                                                 [  OK  ]

Running dahdi_cfg:                                         [  OK  ]

Hey P,

So I’m confused on where we are at with this?

I disabled opv* modules and the tor3e via DAHDI Config Modules, applied and rebooted but still zaphfc isn’t loaded (there isn’t any zaphfc module at all in the system, AFAIK):

[[email protected] /]# service dahdi restart Unloading DAHDI hardware modules: done Loading DAHDI hardware modules:   wct4xxp:                                                 [  OK  ]   wcte12xp:                                                [  OK  ]   wcte13xp:                                                [  OK  ]   wct1xxp:                                                 [  OK  ]   wcte11xp:                                                [  OK  ]   r1t1:                                                    [  OK  ]   rxt1:                                                    [  OK  ]   wctdm24xxp:                                              [  OK  ]   wcfxo:                                                   [  OK  ]   wctdm:                                                   [  OK  ]   rcbfx:                                                   [  OK  ]   zaphfc:  FATAL: Module zaphfc not found.                                                            [FAILED]   wcb4xxp:                                                 [  OK  ]   wctc4xxp:                                                [  OK  ]   xpp_usb:                                                 [  OK  ]

Running dahdi_cfg:                                         [  OK  ]

It seems that latest Dahdi 2.9.2 (the one provided with/by FreePBX Distro 5.211.65-15 and the subsequent last hour yum updates which were available, mostly regarding dahdi-tools as you can read above) removed the zaphfc driver/Kernel Module!

No zaphfc.ko under /lib/modules/2.6.32-431.el6.x86_64/dahdi/ folder (there isn’t the zaphfc subfolder at all, so can’t be the Kernel module too)…I have a FreePBX Distro 6.12.65-13 still with DAHDI 2.9.0 that has that Kernel module.

Below what the system reports:

[email protected] ~]# cd /lib/modules/2.6.32-431.el6.x86_64/dahdi/ [[email protected] dahdi]# ls -lah total 12M drwxr-xr-x 11 root root 4.0K Jul 30 15:57 . drwxr-xr-x  9 root root 4.0K Jul 30 15:58 .. -rw-r--r--  1 root root 325K Jul 24 20:22 dahdi_dynamic_eth.ko -rw-r--r--  1 root root 379K Jul 24 20:22 dahdi_dynamic_ethmf.ko -rw-r--r--  1 root root 301K Jul 24 20:22 dahdi_dynamic.ko -rw-r--r--  1 root root 307K Jul 24 20:22 dahdi_dynamic_loc.ko -rw-r--r--  1 root root 193K Jul 24 20:22 dahdi_echocan_jpah.ko -rw-r--r--  1 root root 225K Jul 24 20:22 dahdi_echocan_kb1.ko -rw-r--r--  1 root root 236K Jul 24 20:22 dahdi_echocan_mg2.ko -rw-r--r--  1 root root 195K Jul 24 20:22 dahdi_echocan_oslec.ko -rw-r--r--  1 root root 208K Jul 24 20:22 dahdi_echocan_sec2.ko -rw-r--r--  1 root root 204K Jul 24 20:22 dahdi_echocan_sec.ko -rw-r--r--  1 root root 1.5M Jul 24 20:22 dahdi.ko -rw-r--r--  1 root root 253K Jul 24 20:22 dahdi_transcode.ko drwxr-xr-x  2 root root 4.0K Jul 30 15:57 oct612x -rw-r--r--  1 root root 530K Jul 24 20:22 pciradio.ko drwxr-xr-x  5 root root 4.0K Jul 24 20:22 rhino -rw-r--r--  1 root root 451K Jul 24 20:22 tor2.ko drwxr-xr-x  2 root root 4.0K Jul 30 15:57 voicebus -rw-r--r--  1 root root 1.2M Jul 24 20:22 wcaxx.ko drwxr-xr-x  2 root root 4.0K Jul 30 15:57 wcb4xxp -rw-r--r--  1 root root 332K Jul 24 20:22 wcfxo.ko -rw-r--r--  1 root root 478K Jul 24 20:22 wct1xxp.ko drwxr-xr-x  2 root root 4.0K Jul 30 15:57 wct4xxp drwxr-xr-x  2 root root 4.0K Jul 30 15:57 wctc4xxp drwxr-xr-x  2 root root 4.0K Jul 30 15:57 wctdm24xxp -rw-r--r--  1 root root 477K Jul 24 20:22 wctdm.ko -rw-r--r--  1 root root 764K Jul 24 20:22 wcte11xp.ko drwxr-xr-x  2 root root 4.0K Jul 30 15:57 wcte12xp -rw-r--r--  1 root root 1.5M Jul 24 20:22 wcte13xp.ko -rw-r--r--  1 root root 1.7M Jul 24 20:22 wcte43x.ko drwxr-xr-x  2 root root 4.0K Jul 30 15:57 xpp

The zaphfc was provided by OpenVox as its not part of stock DAHDI so its not included anymore.

What? Do you know you’re killing a running system by removing such a module (which is used to control a broad range of HFC “Cologne Chip” based PSTN boards, not only OpenVox branded)?

In which way I can turn back with working DAHDI?

I need that module…otherwise my system is (actually) garbage…this is very disruptive IMHO!

IMHO if the new DAHDI 2.9.2 by/for FreePBX is not supporting zaphfc anymore…somebody should tell users that have system working with zaphfc module to NOT upgrade their systems…but this should be told before and not after! I mean, looking at FREEPBX-7750 (part of FreePBX Distro 5.211.65-15 upgrade), I can’t really know that zaphfc module support is going to be removed!

I am sorry that was not communicated. I guess it was a overlooked by me so I will take the blame. But in defense the ticket says update to dahdi 2.9.2 and dahdi 2.9.2 does not include support for that device

In the past we had included some other items for openvox but since their patches are failing to apply to 2.9.2 we can not keep waiting on them when other users need support for 2.9.2 for new digium cards and to fix some major issues in some digium T1 cards so we moved on without openvox.

As shown here we only officialyl patch dahdi for Rhino for quite some time. http://wiki.freepbx.org/display/FD/FreePBX+Distro+Features+above+stock+Asterisk

I am sorry once again that it was not communicated that we had been patching for OpenVox and stopped doing so.

OK, I understand…I don’t want to open a discussion…I just need to understand how (in which way) I could fix the situation now.

I’ve a running system FreePBX Distro 5.211.65-15 with DAHDI 2.9.2 without PSTN connectivity due to lack of zaphfc…how can I fix that? it’s really important…then I can think about a long term solution (as example find a suitable ISDN BRI Card fully supported by FreePBX), but now I’m unable to go that route. Can you understand?

This might work

yum downgrade kmod-dahdi*

Hi tm1000, the yum downgrade worked (no errors in downgrading from kmod-dahdi-linux-2.9.2-20_centos6.2.6.32_431.el6.x86_64 to kmod-dahdi-linux-2.9.2-19_centos6.2.6.32_431.el6.x86_64) but no zaphfc Kernel module popped up (I doubt it will pop up after a reboot, isn’t it?).

At this point I ask myself: if I upload to the system the lacking zaphfc.ko module into /lib/modules/2.6.32-431.el6.x86_64/dahdi/zaphfc sub-folder? …I saw that FreePBX Distro 6.12.65-13 shares the same Kernel (and so the same modules) with FreePBX Distro 5.211.65-15 and, luckily enough, since I didn’t upgraded that system, it still has the zaphfc.ko Kernel Module I desperately need.
Could it work?

It will just say FATAL cant load linked module. But you can try it. You might have to keep downgrading dahdi though, you can keep running it over and over till it reaches the end.

Ah, OK, you mean downgrading not only the kmod-dahdi* but all dahdi* packages?

The other option (to try to manually upload the zaphfc.ko Kernel Module) could hit against the fact that the zaphfc.ko has its dependecies…and if those dependencies (which i don’t know now) are not correctly satisified I’ll end up with a not running system.

Well on a not-yet-updated (to DAHDI 2.9.2) FreePBX Distro 6.12.65-13 I see these dependencies:

[[email protected] dahdi]# modprobe --show-depends zaphfc
insmod /lib/modules/2.6.32-431.el6.x86_64/kernel/lib/crc-ccitt.ko
insmod /lib/modules/2.6.32-431.el6.x86_64/dahdi/dahdi.ko
insmod /lib/modules/2.6.32-431.el6.x86_64/dahdi/zaphfc/zaphfc.ko

which, on the updated FreePBX Distro 5.211.65-15, lack only for the absence of zaphfc.ko…I’m not sure how to do. Downgrade dahdi* up to a (near in time) version that will start working or trying the dirty way of uploading that zaphfc.ko Kernel Modules?
What is your opinion? are there any concerns about one way or another?

Should I first downgrade kmod-dahdi-linux* and wanpipe* (because actual versions requires dahdi-2.9.2 and so I can’t downgrade dahdi-2.9.2 in a clean way…) and then downgrade dahdi* various packages?

No…it’s going to be a mess of (missed) dependency resolution…

You can keep running yum downgrade kmod-dahdi* is my point. It’s not a one time only thing

OK, it’s what I’m trying to do (I did only that, others are mine speculations only) but after with the second yum downgrade attempt I receive:

[[email protected] ~]# yum downgrade kmod-dahdi* Loaded plugins: changelog, fastestmirror, kmod, security Setting up Downgrade Process Loading mirror speeds from cached hostfile Resolving Dependencies --> Running transaction check ---> Package kmod-dahdi-linux.x86_64 0:2.9.2-18_centos6.2.6.32_431.el6.x86_64 will be a downgrade ---> Package kmod-dahdi-linux.x86_64 0:2.9.2-19_centos6.2.6.32_431.el6.x86_64 will be erased --> Finished Dependency Resolution

Dependencies Resolved

===================================================================================================================================================================================================================
 Package                                            Arch                                     Version                                                                   Repository                             Size

Reinstalling:
 kmod-dahdi-linux                                   x86_64                                   2.9.2-18_centos6.2.6.32_431.el6.x86_64                                    pbx                                   4.9 M

Transaction Summary

Reinstall     1 Package(s)

Total size: 4.9 M
Is this ok [y/N]: y
Downloading Packages:
Running rpm_check_debug
Running Transaction Test

Transaction Check Error:
  package kmod-dahdi-linux-2.9.2-18_centos6.2.6.32_431.el6.x86_64.x86_64 is already installed

Error Summary

when the first yum downgrade attempt was successfull.

Ah that is as low as it goes then. Darn.

Well the issue is kmod RPMS are not like a normal RPM.

If you do a rpm -qa | grep kmod-dahdi I bet the old one is still installed.

1 Like

I’m on a dead end road for an upgrade…regardless the precious help of tm1000 (the route of forced downgrading looks not so linear…) I need to ask you an extra help because the fact you (as FreePBX Developers, strictly speaking, not you as a person) experienced some issues with OpenVox and the whole affair was then resolved with their DAHDI Kernel Modules removal on (and starting with) FreePBX Distro 5.211.65-15 can create potential issues to end users that uses zaphfc for their PSTN Cards (mostly ISDN BRI I think).

IMHO there should be a sort of “decommissioning” path to follow and not a such abrupt cut (there is Hardware involved)…It’s not possible to upgrade a FreePBX Distro that has been running well for almost one year (traversing a lot of updates/upgrades) and then, suddenly, saw it falling due to a unexpected (tell me who know that outside the FreePBX Developers circle) Kernel Module removal.

This is not a “correct workflow” IMHO (It may be correct from your internal standpoint but not from an external one). I’m not defending OpenVox…I really don’t care about it (and think how much ignorant I am that I didn’t know who was/is responsible for the zaphfc Kernel Module!)…it’s just the way things are happening…there wasn’t any sort of (external) “staging” effort in that.