I have a new install using FreePBX-1.1009.210.62-x86_64-Full-1350438464.iso. After struggling to get the two Rhino R4FXOEC cards to work, I contacted Rhino support which gave me a setup script to do the setup. After having further problems, I gave them access to the box; after looking around they told me the following.
"Unfortunately there is a couple bugs it the 64bit version of FreePBX. From my understanding the developer does have a fix but you may have to contact them or check the forums.
They packaged a 32 bit version of libpri and libSS7 which prevents chan_dahdi from loading.
The fix may be as simple as running ‘yum update libss7 libpri’ but it could as easily break things so it is always easiest to confirm the fix with the developers. ".
So I did some searching on the FreePBX site and found this document. http://www.freepbx.org/forum/freepbx-distro/distro-discussion-help/freepbx-distro-1-10xx-210-62-releases-stable-releases
Seems that I needed two upgrades to solve the problem.
1.1009.210.62-2- Fix bug with crontabs not being installed at install time.
1.1010.210.62-1- Upgrade to Asterisk 10.9 and all Centos 6.2 Packages. Fix bug in 64bit libpri and libss7
I did the upgrades.
Today I contacted Rhino support again still trying to get to work.
They looked at my system and reported;
However, there is still a problem libss7 on this system, which is preventing Asterisk from using any DAHDi hardware.
pbx1*CLI> module load chan_dahdi.so
Unable to load module chan_dahdi.so
Command 'module load chan_dahdi.so ’ failed.
[2012-11-14 14:01:23] WARNING[3543]: loader.c:405 load_dynamic_module: Error loading module ‘chan_dahdi.so’: libss7.so.1: cannot open shared object file: No such file or directory
[2012-11-14 14:01:23] WARNING[3543]: loader.c:870 load_resource: Module ‘chan_dahdi.so’ could not be loaded.
ldd /usr/lib64/asterisk/modules/chan_dahdi.so
linux-vdso.so.1 => (0x00007fff137f8000)
libtonezone.so.2.0 => /usr/lib64/libtonezone.so.2.0 (0x00007fb4acebb000)
libpri.so.1.4 => /usr/lib64/libpri.so.1.4 (0x00007fb4acc41000)
libss7.so.1 => not found
libopenr2.so.3 => /usr/lib64/libopenr2.so.3 (0x00007fb4aca23000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007fb4ac807000)
libc.so.6 => /lib64/libc.so.6 (0x00007fb4ac476000)
libm.so.6 => /lib64/libm.so.6 (0x00007fb4ac1f2000)
/lib64/ld-linux-x86-64.so.2 (0x00007fb4ad3f3000)
The reason it “can’t find” libss7 is because the libss7 is 32-bit, while chan_dahdi and everything else is 64bit.
file /usr/lib64/asterisk/modules/chan_dahdi.so /usr/lib/libss7.so.1 /usr/lib/libss7.so.1.0
/usr/lib64/asterisk/modules/chan_dahdi.so: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, stripped
/usr/lib/libss7.so.1: symbolic link to `libss7.so.1.0’
/usr/lib/libss7.so.1.0: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked, stripped
Based on this information, I would have to say that “• 1.1010.210.62-1- Upgrade to Asterisk 10.9 and all Centos 6.2 Packages. Fix bug in 64bit libpri and libss7” was unsuccessful. (libpri has a 64bit library installed, so perhaps that portion of the fix was accurate.)
These are bugs that need to be addressed by the FreePBX distribution before your R4FXO, or in fact, any DAHDi hardware at all, will work on your system
Before wrote to the form I did “yum list libss7”
[root@pbx1 boot]# yum list libss7
/usr/lib/yum-plugins/kmod.py:25: DeprecationWarning: the sets module is deprecated
from sets import Set, ImmutableSet
Loaded plugins: fastestmirror, kmod
Loading mirror speeds from cached hostfile
Installed Packages
libss7.x86_64 1.0.2-2_centos6 @anaconda-CentOS-201112091719.x86_64/6.2
[root@pbx1 boot]#
As you can see it shows the package as a 64 bit. I questioned this with Rhino support, and they replyed with:
This is actually very simple to explain. The libss7 rpm provided by FreePBX is tagged as being 64bit, thus what you see in yum, however the actual file that’s installed on-disk is 32bit (confirmed by running “file …pathto/libss7.*”). In short, the RPM provided by FreePBX is “bad” and should not contain any 32bit libraries.
Your yum output coupled with the information I provided should be more than enough for FreePBX to see the problem with their RPM and resolve it.
Can anyone give me any help on this?
Thanks In advance for your help!
Jerry