Thanks Henning,<div><br></div><div>we are currently doing it looking for error messages in the logs, and it´s ok, but since the request is processed by the kamailio routing script via the xmlrpc module with the dispatch_rpc() command , I was wondering if there could be a way to check the command output inside the same script.</div>
<div><br></div><div><br></div><div>Regards</div><div><br></div><div>Javi</div><div><br><div class="gmail_quote">2011/2/24 Henning Westerholt <span dir="ltr"><<a href="mailto:henning.westerholt@1und1.de">henning.westerholt@1und1.de</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im">On Wednesday 23 February 2011, Javier Gallart wrote:<br>
> I've upgraded to 3.1.2 and compiled with the DEFS+= -DMI_SYSTEM_MALLOC<br>
> option. Looking good so far. Any thoughts about my second question, that<br>
> is, how to be aware from the scripts if the any problems has arisen in the<br>
> mi command?<br>
<br>
</div>Hi Javier,<br>
<br>
there are several ways how to monitor this condition:<br>
<br>
* create a check that grep in the log file for the error msg<br>
* check the output of "kamctl fifo get_statistics all" for the memory<br>
informations<br>
* do a OPTIONS ping to the server that is replied statefully (thus allocates<br>
memory) and check this<br>
* and probably the best, just check the return value of the mtree reload FIFO<br>
cmd?<br>
<br>
Cheers,<br>
<font color="#888888"><br>
Henning<br>
</font></blockquote></div><br></div>