I can second Daniel's suggestion to rather use xmlrpc. A while back we tested both versions and xmlrpc performance (and stability) was way better.<div><br></div><div>Cheers</div><div>Jason<br><br><div class="gmail_quote">
On Fri, Feb 17, 2012 at 10:17 AM, Daniel-Constantin Mierla <span dir="ltr"><<a href="mailto:miconda@gmail.com">miconda@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hello,<div class="im"><br>
<br>
On 2/17/12 7:23 AM, Nathaniel L Keeling wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hello,<br>
<br>
I am trying to compile mi_xmlrpc on Solaris 10 64bit OS and I am getting this error:<br>
<br>
CC (gcc) [M mi_xmlrpc.so] abyss_xmlrpc_server.o<br>
abyss_xmlrpc_server.c:948:1: error: conflicting types for 'shutdownAbyss'<br>
abyss_xmlrpc_server.c:945:34: note: previous declaration of 'shutdownAbyss' was here<br>
abyss_xmlrpc_server.c: In function 'normalLevelAbyssRun':<br>
abyss_xmlrpc_server.c:1005:42: warning: passing argument 2 of 'xmlrpc_registry_set_shutdown' from incompatible pointer type [enabled by default]<br>
/opt/csw/include/xmlrpc-c/<u></u>server.h:114:1: note: expected 'void (* const)(struct xmlrpc_env * const, void * const, const char * const, void * const)' but argument is of type 'void (*)(struct xmlrpc_env * const, void * const, const char * const)'<br>
gmake[1]: *** [abyss_xmlrpc_server.o] Error 1<br>
gmake: *** [modules_k] Error 1<br>
</blockquote>
<br></div>
do you have any xmlrpc-c library installed? If yes, what version? For some old versions the module uses an included version, since there were bugs in the library.<br>
<br>
You can try to remove the line 945 in the abyss_xmlrpc_server.c file from the module for the error, but I see some other warnings that indicate some mixage of libraries.<br>
<br>
On the other hand, it is recommended to use xmlrpc module, it is located in 'modules/' and can run mi and new-rpc commands. For running mi commands, that use 'mi' as XMLRPC command, then the first parameter is the name of MI command, followed by the rest of the parameters.<br>
<br>
Btw, these are for v3.1+ of kamailio.<br>
<br>
Cheers,<br>
Daniel<span class="HOEnZb"><font color="#888888"><br>
<br>
-- <br>
Daniel-Constantin Mierla -- <a href="http://www.asipto.com" target="_blank">http://www.asipto.com</a><br>
<a href="http://linkedin.com/in/miconda" target="_blank">http://linkedin.com/in/miconda</a> -- <a href="http://twitter.com/miconda" target="_blank">http://twitter.com/miconda</a></font></span><div class="HOEnZb"><div class="h5">
<br>
<br>
<br>
______________________________<u></u>_________________<br>
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list<br>
<a href="mailto:sr-users@lists.sip-router.org" target="_blank">sr-users@lists.sip-router.org</a><br>
<a href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users" target="_blank">http://lists.sip-router.org/<u></u>cgi-bin/mailman/listinfo/sr-<u></u>users</a><br>
</div></div></blockquote></div><br></div>
<pre>This email is subject to the disclaimer of Smile Communications (PTY) Ltd. at http://www.smilecoms.com/disclaimer