Hi, we have a similar task for this on our TODO list. There was this idea that the timer ping should take the pinging responsability from routing processes.

Here is some improvement suggestions, if they apply to you too:

1. Register timer callback only if "rtpengine_ping_interval" modparam is > 0 (default can be 0, disabled)
2. In rtpp_test() function check if "force" param is == 0 and if "rtpengine_ping_interval" modparam is > 0, then return imediately => this should take the pinging responsability from SIP routing processes
3. Please check what happens with build_rtpp_socks() inside the ping timer callback, when there is at least 1 rtpengine in the list down. I think sockets will be re-built each time timer triggers

Thank you,
Stefan

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: <kamailio/kamailio/pull/4016/c2459124310@github.com>