OK, I did the Yum Shell procedure and, despite the system still shows:
- kmod-dahdi-linux-2.9.2-18_centos6.2.6.32_431.el6.x86_64
- kmod-dahdi-linux-2.9.2-19_centos6.2.6.32_431.el6.x86_64
as installed packages, along with the:
- kmod-dahdi-linux-2.9.0.1-67_centos6.2.6.32_431.el6.x86_64
the procedure itself seems to have worked as expected (I sent you a PM with details).
After that I rebooted the system, then I just checked that FreePBX DAHDI settings were all there (they were untouched) and I did the only one thing that seemed necessary and requested by FreePBX DAHDI Config module: to edit the DAHDI Hardware settings of my PSTN Card, settings that were lost in between (I presume that’s normal due to what we did).
Finally dahdi_hardware shows me the card status and, through Asterisk console, I’m able to see (via show dahdi channels and show dahdi status) that all seems come back to work! I tested an (here: early morning) incoming call and I see it flows through the system.
I will test the system today for outgoing calls but I feel it would be OK.
Should I worry about kmod-dahdi-linux-2.9.2 packages? I’m really too scared to touch anything now.
P.S.
Funny: in the end today I think I’m the only one in the planet Earth with FreePBX Distro 5.211.65-15 AND DAHDI 2.9.0.1 and I learned a series of BIG lessons!
I modified the Thread title…it seems more pertinent to cite zaphfc removal (so if other users search for zaphfc they will find this thread for sure).
I’m in debt with you all.
The points are now:
- What will then happen with (FreePBX/Schmooze provided) zaphfc?
- Who is actually responsible for developing (and which take care of) zaphfc?
- What actions should be done to continue running (or to implement a new) FreePBX Distro system (without worring for its future in terms of software upgrades) that uses generic (not only OpenVox branded) HFC “Cologne Chip” based ISDN cards?
- Is there a Hardware related roadmap about FreePBX DAHDI Firmware (thus administrators can understand what is going to happen with their specific Hardware)?
- In which way you manage (or interact with) the development and the maintenance of DAHDI drivers to incorporate them into FreePBX DAHDI and SHMZ OS?
We all know that ISDN BRI is typically “European” and it’s not so common in North America region…this maybe explains why issues with zaphfc (if any…I could the only one up to know) and FreePBX Distro will eventually only hit European based system that uses those HFC based BRI ISDN cards (in the end, I’m looking now, the zaphfc support lasted about 18 months since its inclusion with the FREEPBX-6241, it was a milestone).
This could be a subject for another specific Thread, I suppose.