On Mon, Mar 16, 2009 at 5:22 PM, Henning Westerholt < henning.westerholt@1und1.de> wrote:
On Monday 16 March 2009, Sara EL KABIRI wrote:
[..] Mar 16 17:06:03 [6396] NOTICE:presence:child_init: init_child [12] pid [6396]
*ims@ims-desktop:~$ ims@ims-desktop:~$ ims@ims-desktop:~$ ims@ims-desktop:~$ ims@ims-desktop:~$ sudo netstat -anp | grep 5065 tcp 0 0 192.168.0.99:5065 0.0.0.0:* LISTEN 6370/kamailio tcp 0 0 127.0.0.1:5065 0.0.0.0:* LISTEN 6370/kamailio udp 0 0 192.168.0.99:5065 0.0.0.0:* 6370/kamailio udp 0 0 127.0.0.1:5065 0.0.0.0:* 6370/kamailio ims@ims-desktop:~$ ims@ims-desktop:~$ kamctl moni ERROR: Error opening Kamailio's FIFO /tmp/kamailio_fifo ERROR: Make sure you have the line 'modparam("mi_fifo", "fifo_name", "/tmp/kamailio_fifo")' in your config ERROR: and also have loaded the mi_fifo module.*
It seems that Kamailio is now working fine. Approximately fine i would
say
because of the error throwed by "*kamctl moni*"... Is there something to worry about?
Hi Sara,
yes, it seems to work fine now. :-) The error with the FIFO is nothing to worry about, you can easily fix it when you include the necessary statements to the cfg. You need a loadmodule and a modparam statement for the fifo module, take a look at the default cfg for an example.
Cheers,
Henning
Thanks a lot for your help. I'm grateful :-) About the mi_fifo module, i've checked that in my cfg file before, and the loadmodule and modparam statements are set correctly...
*loadmodule "mi_fifo.so" modparam("mi_fifo", "fifo_name", "/tmp/kamailio_fifo")*