Closed olivierb2 closed 6 years ago
Dear Oliver,
While I am not familiar with Wazo, this issue might be caused by having different versions of the Asterisk development package (headers and libraries) that the UniMRCP modules are built with, and the Asterisk itself.
If this is a Debian-based distribution, then what is the output of
apt --installed list | grep asterisk
Here the output of the command requested, as you can see, I have same header and asterisk package.
asterisk/unknown,now 8:15.2.0-1~wazo4.deb9 amd64 [installé, automatique]
asterisk-dev/unknown,now 8:15.2.0-1~wazo4.deb9 all [installé]
asterisk-sounds-main/unknown,now 8:15.2.0-1~wazo4.deb9 all [installé, automatique]
asterisk-sounds-wav-en-us/unknown,now 1:17.17~20171123.144644.8d6ef03 all [installé, automatique]
asterisk-sounds-wav-fr-fr/unknown,now 1:17.17~20171123.144644.8d6ef03 all [installé, automatique]
python-asterisk-ari/unknown,now 0.3.0-1 all [installé, automatique]
Not sure about Wazo, but I just installed Asterisk 15.2.2 from source and also built UniMRCP modules against. Everything works as intended.
There are no API changes in Asterisk 15.2 which may cause incompatibility issues with modules built externally.
Thanks for the information, I will made further testing, I close this ticket as it seems not related to newest version.
Dear community,
I'm using Asterisk 15.2 on a Wazo distribution. While this Asterisk uniMRCP is compiling correctly, I'm unable to load it from Asterisk.
The other module app_unimrcp.so is loading correctly.
I'm not developper and able to provide a fix. Does anybody is able to propose a patch for this issue?
Thanks
Obitwo