Re: [sr-dev] SIP ping, sockets and multi homed

Thanks for the response Daniel, I was trying to force the socket from the tm:local-request and this was causing me the crash. About this crash I wasn't aware about the ulimit -c I will change that in my servers! And about mtree, do you have some explanation on how to use that for prefix

Re: [sr-dev] SIP ping, sockets and multi homed

Hello, On 22.09.17 04:42, Patrick Wakano wrote: > Hello list, > > After deep investigation I found out that the issue is happening > because of the mechanism Kamailio uses to find the most appropriate > socket combined with the virtual IP usage > For socket selection, Kamailio first asks

Re: [sr-dev] SIP ping, sockets and multi homed

Hello Daniel, I still couldn't make this SIP probing work So currently my setup cannot actively check for GW availability... Any idea about what may be causing it? Thanks for your time, Patrick Wakano On 16 August 2017 at 13:01, Patrick Wakano wrote: > Forgot to mention

Re: [sr-dev] SIP ping, sockets and multi homed

Hello, what are the sockets kamailio is listening on? See `kamcmd help` for the command that lists the sockets. Also, what is the log messages before the first one you pasted, there should be another one printed from get_out_socket(). It is always important to provide kamailio version (kamailio

[sr-dev] SIP ping, sockets and multi homed

Hello Kamailio list, Hope you all doing well! I am stuck with one problem that should be incredibly easy to be done, but apparently it is not I want my dispatcher, LCR and nathelper modules to always SIP ping my SIP clients. I have a Kamailio based SBC that is separating two networks, and so