vicidial.org

Hi guys, here i am seeking for help again ñ_ñ.

First of all this is my setup enviroment.

Installation Method: Vicibox Redux 3.1.10 single server
Hardware: Sangoma AFT A102

upgrades vía zypper
Asterisk: 2.4.29-2-vici
DAHDI: 2.4.1.2-23.3
Wanpipe: 3.5.20-13.5
OpenR2: 1.3.1-1.1


dahdi/system.conf

Code: Select all

loadzone=us
defaultzone=us

#Sangoma A102 port 1 [slot:4 bus:2 span:1] <wanpipe1>
span=1,1,0,cas,hdb3
cas=1-15:1101
cas=17-31:1101

#Sangoma A102 port 2 [slot:4 bus:2 span:2] <wanpipe2>
span=2,2,0,cas,hdb3
cas=32-46:1101
cas=48-62:1101

asterisk/chan_dadi.conf

Code: Select all

[trunkgroups]

[channels]
usecallerid=yes
hidecallerid=no
callwaiting=yes
usecallingpres=yes
callwaitingcallerid=yes
threewaycalling=yes
transfer=yes
canpark=yes
cancallforward=yes
callreturn=yes
busydetect=yes
busycount=6
echocancel=no
echocancelwhenbridged=no
relaxdtmf=yes
rxgain=0.0
txgain=0.0

signalling=mfcr2
mfcr2_variant=mx
mfcr2_get_ani_first=no
mfcr2_max_ani=10
mfcr2_max_dnis=4
mfcr2_category=national_subscriber
mfcr2_logdir=log
mfcr2_logging=all

context=trunkinbound
group=0
callgroup=0
pickupgroup=0
channel => 1-15
channel => 17-31
channel => 32-46
channel => 48-62

OK, now, the problem:

When i try to load chan_dahdi i got this error message:

Code: Select all

VDTS01*CLI> module load chan_dahdi.so
[Jun 19 12:06:11] WARNING[10419]: pbx.c:3027 ast_register_application: Already have an application 'DAHDISendKeypadFacility'
[Jun 19 12:06:11] WARNING[10419]: pbx.c:3027 ast_register_application: Already have an application 'ZapSendKeypadFacility'
[Jun 19 12:06:11]   == Parsing '/etc/asterisk/chan_dahdi.conf': [Jun 19 12:06:11] Found
[Jun 19 12:06:11] ERROR[10419]: chan_dahdi.c:13594 process_dahdi: Unknown signalling method 'mfcr2' <<<<<<<==========
[Jun 19 12:06:11] ERROR[10419]: chan_dahdi.c:13148 build_channels: Signalling must be specified before any channels are.

As you can see asterisk does not recognize the mfcr2 signaling, i have extactly this setup on toher 3 servers but i patched those by my own, this is the first time i use de Kumba's already patched asterisk, Is anything wrong in my config files? Do i have to use something else than signaling=mfcr2 ?

Thanks guy for help, and sorry if i post too much information, i just want to help you to help me.

Thank you very much in advance..

There was already a thread with similar issue here:

http://www.vicidial.org/VICIDIALforum/v ... ight=mfcr2

But we are using diferente asterisk version.


And i just got realized that this thread should be in Vicibox section instead in support, sorry for that can someone help me to move this thread to propper section?

It looks like the asterisk-vici on zypper is not properly patched


ldd /usr/lib64/asterisk/modules/chan_dahdi.so
linux-vdso.so.1 => (0x00007fffed5dd000)
libtonezone.so.2.0 => /usr/lib64/libtonezone.so.2.0 (0x00007f5fb7ffe000)
libpri-1.4.so.0 => /usr/lib64/libpri-1.4.so.0 (0x00007f5fb7da3000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f5fb7968000)
libc.so.6 => /lib64/libc.so.6 (0x00007f5fb7608000)
libm.so.6 => /lib64/libm.so.6 (0x00007f5fb73b0000)
/lib64/ld-linux-x86-64.so.2 (0x00007f5fb84e3000)

After i patch asterisk by my own:


ldd /usr/lib64/asterisk/modules/chan_dahdi.so
linux-vdso.so.1 => (0x00007fffed5dd000)
libtonezone.so.2.0 => /usr/lib64/libtonezone.so.2.0 (0x00007f5fb7ffe000)
libpri-1.4.so.0 => /usr/lib64/libpri-1.4.so.0 (0x00007f5fb7da3000)
libopenr2.so.3 => /usr/local/lib/libopenr2.so.3 (0x00007f5fb7b85000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f5fb7968000)
libc.so.6 => /lib64/libc.so.6 (0x00007f5fb7608000)
libm.so.6 => /lib64/libm.so.6 (0x00007f5fb73b0000)
/lib64/ld-linux-x86-64.so.2 (0x00007f5fb84e3000)


And now MFCR2 is working

i just zypper si asterik-vici patchit by my own, replace /usr/lib64/asterisk/modules/chan_dahdi.so wit /usr/lib/asterisk/modules/chan_dahdi.so

Interesting. Back to the drawing board I guess. I'll see what I can come up with for 3.1.11 release.

Kumba, I'm having the same behavior, and I did the exact same thing that covarrubiasgg did.

One interesting thing is that when I try to patch your Asterisk source, it tells me that it is already patched. If I just build it as I downloaded, it will generate chan_dahdi.so on /usr/lib/asterisk/modules with the correct lib, notice that your directory is /usr/lib64... I'm not familiar with your process of bulding it, but maybe this is some clue.

I have set up a testing E1 that I can easily change from ISDN or R2, if you wish to post a pre-release version of 3.1.11, I could test it fast for you, just let me know.

Thanks

Ok, I've got it updated, and I see it linked in the RPM. So download vicibox 3.1.10, do a zypper up, and see if MFCR2 works without recompiling.

Hello,

sorry, still doesn't work. I just did a zypper up and tested it, no success.

this is the ldd result:

Code: Select all

vicidial:~ # ldd /usr/lib64/asterisk/modules/chan_dahdi.so
        linux-vdso.so.1 =>  (0x00007fff41695000)
        libtonezone.so.2.0 => /usr/lib64/libtonezone.so.2.0 (0x00007f47c438d000)
        libpri-1.4.so.0 => /usr/lib64/libpri-1.4.so.0 (0x00007f47c4132000)
        libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f47c3f14000)
        libc.so.6 => /lib64/libc.so.6 (0x00007f47c3bb4000)
        libm.so.6 => /lib64/libm.so.6 (0x00007f47c395d000)
        /lib64/ld-linux-x86-64.so.2 (0x00007f47c483d000)


and this shows up when we load chan_dahdi.so:

Code: Select all

[Jul 25 01:25:52] ERROR[4654]: chan_dahdi.c:13594 process_dahdi: Unknown signalling method 'r2mfc'
[Jul 25 01:25:52] ERROR[4654]: chan_dahdi.c:8937 mkintf: Signalling requested on channel 32 is ISDN PRI but line is in MFC/R2 signalling
[Jul 25 01:25:52] ERROR[4654]: chan_dahdi.c:13217 build_channels: Unable to register channel '32-46,48-62'


Just let me know when you need to test again.

Thanks.

I installed ViciBox v.3.1.10, did a zypper refresh and zypper up, and ldd now shows it linking against openr2.

Can you verify it's working?

Yes !! It works !!

Thanks a lot Kumba, great work.