[sr-dev] [kamailio/kamailio] v5.0.4: nathelper: dont ping replicated aor's (#1299)

00Asgaroth00 notifications at github.com
Fri Nov 3 14:18:59 CET 2017


Thanks for the info, just a quick question, if the same situation was in place when running 3 registrar's in db-only mode, then we can use the server_id and filter_server_id so that only 1 registrar will ping the contact. At lease, that is what I am interpreting in the module documentation. Is that correct? 

I think that if you don't have the server_id and filter_server_id parameters set for nathelper, then all 3 database-only registrars will also ping the contact? Is that correct? Or, does nathelper/registrar us the aor "socket" parameter to decide if it need to send the ping from the local registrar? What i mean is, if the socket is set, and is a local socket, then send the ping, if there is not a socket set, or, if there is a socket set and is not local, then don't send the keep-alive message.

How does nathelper currently decide if it needs to send a keep-alive message from the local registrar?

Currently, I'm lucky that only 1 keep-alive message is actually making it through to the endpoint, however, if kamailio used the force_socket parameter correclty then all 3 keep-alives would make it through to the endpoint, which, I'm guessing, is not desired behaviour, or am I wrong with that assumption?

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/1299#issuecomment-341700749
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kamailio.org/pipermail/sr-dev/attachments/20171103/036b3557/attachment.html>


More information about the sr-dev mailing list