Problem with R2/MFC support
Posted: Fri Mar 18, 2011 2:32 pm
Hi guys,
A couple months ago I had an issue with MFC/R2 support that was supposed to be included into the 3.1 ISO. At that time I recompiled Asterisk with the patch for OpenR2 included but later on I noticed that I had misspelled one configuration item and I couldn't tell for sure where the problem really was.
Today I tried to install another E1 line with MFC/R2 signalling and I found that the problem seems to be the patch that was not applied to Asterisk before compillation.
The OpenR2 library manual tell us to run this below to verify if everything went ok, and as you can see it is not.
This is the output on my server:
This is what I get when loading chan_dahdi:
I wonder if the patch didn't become deprecated since it needs to be the exact version of the Asterisk you are installing in, the correct patch for 1.4.27 release of Asterisk is here: http://code.google.com/p/openr2/downloa ... 1&q=1.4.27
OperR2 library installs other stuff into the server, that part seems to be ok, "r2test" is one small app to test channels and it is included into the .ISO.
Well, I will be glad to test this the next time it's released.
Thanks
A couple months ago I had an issue with MFC/R2 support that was supposed to be included into the 3.1 ISO. At that time I recompiled Asterisk with the patch for OpenR2 included but later on I noticed that I had misspelled one configuration item and I couldn't tell for sure where the problem really was.
Today I tried to install another E1 line with MFC/R2 signalling and I found that the problem seems to be the patch that was not applied to Asterisk before compillation.
The OpenR2 library manual tell us to run this below to verify if everything went ok, and as you can see it is not.
In order to verify if chan_dahdi.so are properly compiled and linked with OpenR2, you can
execute this command:
# ldd channels/chan_dahdi.so | grep openr2
That command should show something like this:
libopenr2.so.1 => /usr/lib/libopenr2.so.1 (0x0000000000589000)
This is the output on my server:
/usr/lib64/asterisk/modules # ldd chan_dahdi.so
linux-vdso.so.1 => (0x00007fff4d1c3000)
libtonezone.so.2.0 => /usr/lib64/libtonezone.so.2.0 (0x00007fd2e7e12000)
libpri-1.4.so.0 => /usr/lib64/libpri-1.4.so.0 (0x00007fd2e7bb8000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007fd2e799a000)
libc.so.6 => /lib64/libc.so.6 (0x00007fd2e763a000)
libm.so.6 => /lib64/libm.so.6 (0x00007fd2e73e3000)
/lib64/ld-linux-x86-64.so.2 (0x00007fd2e82c0000)
This is what I get when loading chan_dahdi:
[Mar 18 15:27:17] ERROR[10443]: chan_dahdi.c:13209 process_dahdi: Unknown signalling method 'mfcr2'
[Mar 18 15:27:17] ERROR[10443]: chan_dahdi.c:8567 mkintf: Signalling requested on channel 94 is ISDN PRI but line is in MFC/R2 signalling
[Mar 18 15:27:17] ERROR[10443]: chan_dahdi.c:12819 build_channels: Unable to register channel '94-108,110-124'
I wonder if the patch didn't become deprecated since it needs to be the exact version of the Asterisk you are installing in, the correct patch for 1.4.27 release of Asterisk is here: http://code.google.com/p/openr2/downloa ... 1&q=1.4.27
OperR2 library installs other stuff into the server, that part seems to be ok, "r2test" is one small app to test channels and it is included into the .ISO.
Well, I will be glad to test this the next time it's released.
Thanks