Can't start work with ari


#1

https://wiki.asterisk.org/wiki/display/AST/Getting+Started+with+ARI

How to load module ari?

Load module res_http_websocket.so.

vs-ita-deb-01*CLI> core show version
Asterisk 15.7.1 built by root @ vs-ita-deb-01 on a x86_64 running Linux on 2019-01-14 13:47:47 UTC
vs-ita-deb-01*CLI>
adminis@vs-ita-deb-01:~$ sudo cat /etc/asterisk/ari.conf  | grep -v "^;"
[general]
enabled = yes       ; When set to no, ARI support is disabled.
pretty = yes       ; When set to yes, responses from ARI are

[asterisk]
type=user
read_only = no     ; When set to yes, user is only authorized for
password=asterisk         ; Crypted or plaintext password (see password_format).

adminis@vs-ita-deb-01:~$ sudo cat /etc/asterisk/http.conf  | grep -v "^;"
[general]
servername=Asterisk
enabled=yes
bindaddr=0.0.0.0
enablestatic=yes
bindport=8088
prefix=

vs-ita-deb-01*CLI> module show like http
Module                         Description                              Use Count  Status      Support Level
res_http_websocket.so          HTTP WebSocket Support                   2          Running          extended
1 modules loaded
vs-ita-deb-01*CLI> module show like odbc
Module                         Description                              Use Count  Status      Support Level
res_odbc.so                    ODBC resource                            0          Running              core
1 modules loaded
vs-ita-deb-01*CLI> module load res_ari.so
Unable to load module res_ari.so
Command 'module load res_ari.so ' failed.
[Feb  6 23:33:49] WARNING[55461]: loader.c:577 load_dlopen: Error loading module 'res_ari.so': /usr/lib/asterisk/modules/res_ari.so: undefined symbol: stasis_app_set_global_debug
[Feb  6 23:33:49] WARNING[55461]: loader.c:1180 load_resource: Module 'res_ari.so' could not be loaded.


#2

The load module loader is trying to load something, but on the same system, this can come up with unresolved symbol error, but usually, it loads all modules. What is the issue coming up? as it is just a warning. If you want to remove this error you can play with your module.conf file change order of loading module.