some more info on this one, it looks like this is only happening on nodes that have been replicated to, for example, If a registration is processed on node 1, then the nathelper send the locally generated options message out of the correct socket, I presume it gets the sending socket details from the socket information stored by the registrar. (Socket:: udp:10.7.0.175:5060) However, when this registration is replicated (via dmq_usrloc), there is no local socket information for the particular contact, the nathelper module seems to think that it needs to ping this registration contact (it is natted) and sends it out of the wrong interface even if the force_socket module parameter is set for the nathelper module. That brings me on to my next question, why is the nathelper module attempting to ping natted contacts from all registrar's, should it not ping from the registrar that processed the last registration attempt? I had a read of the nathelper module documentation, but I cannot see any obvious setting that would tell nathelper to only ping from the registrar processing the request. Is my understanding of how nathelper is supposed to work correct when it comes to multiple registrar's with registration replication? Myabe I am missing something here, any tips/tricks/suggestions/beatings most welcome Thanks On 23/07/2015 12:14, Asgaroth wrote:

Hi Daniel, Thanks for that information, I had a look at registrar/nathelper and usrloc module documentation, and I do see the server_id parameter in the usrloc module docs for v4.3.x. This appears to be a database only column, I am running in memory only mode using dmq_usrloc to replicate the registrations, in this particular instance, how would I go about setting the server_id parameter when running in memory mode (db_mode 0). Thanks -----Original Message----- From: sr-users [mailto:sr-users-bounces@lists.sip-router.org] On Behalf Of Daniel-Constantin Mierla Sent: Friday 7 August 2015 18:37 To: Kamailio (SER) - Users Mailing List <sr-users(a)lists.sip-router.org> Subject: Re: [SR-Users] NatHelper ignoring force_socket module parameter You have to set server_id to be different for each node in order to send keepalive only for registration received directly, however, iirc, this feature is only in master branch. Cheers, Daniel On 23/07/15 15:19, Asgaroth wrote: -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Book: SIP Routing With Kamailio - http://www.asipto.com _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users(a)lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Hi All, Just to continue on on this particular issue, we are now testing kamailio v5.0.3 and I are still experiencing the same issue. We run 3 registrar servers which run with user location "in-memory" (db_mode 0). These registrar's are configured to replicate registrations using the dmg_usrloc module. All works well except for when nat pinging is enabled. When nat ping is enabled, it appears that the nathelper sends options pings from all 3 servers, and not only the server that processed the registration request. I have tried setting the server_id core parameter on all three of these servers in an attempt to ensure their uniqness, but still, the options pings are being sent from all 3 systems. What I was expecting to see happen was that the registrar that processed/saved the registration, would be the only registrar performing the sip options ping, and the remaining two only have a replicated "copy" of the registration. I'm not sure if this is meant to be classified as a bug or a feature request, seeing that the feature appears to be available when running with an sql database (I've not tested with usloc in database, we require usrloc to be in memory). Do I need to log a bug on github for this issue? I've attached a copy of the aor (usrlock_dump.txt) as dumped by "kamctl ul show" on each of the registrars, and also a sip capture where you can see the options being sent by 3 registrars, but only 1 being responded to. I've attached "sip_capture.txt" to show the options messages being sent by the 3 registrars. I've attached "module_settings.txt" to show the settings for the usrloc/registrar/nathelper modules in case there is a mishap there. An additional observation is that when the registrars that did not process the registration (the ones replicated to), try to send their "ping", they send it over the incorrect interface (ignoring the nathelper parameter "force_socket" which has been set for all 3 registrars). I guess, in this circumstance, this is also a blessing in disguise or else the endpoint would have received 3 options pings to reply to every ping interval. However, I'm not sure if this is the expected bahaviour when setting force_socket for natping module. Any thoughts/tips would be much appreciated. Thanks