Re: [SR-Users] NatHelper ignoring force_socket module parameter

I've been toying with this a little more now, and I have now set server_id to different values for each of my registrars, but I still see each of them attempting to send options messages to contacts that have not been processed by the server locally (these aor's have been replicated using dmq_replicate from the server that originally processed the request). What I can see is that if an aor has been replicated to the local registrar, then the "Socket::" value is not propogated, which makes sense, however, the "Socket::" value does exist on the registrar that actually processed the registration request. My configuration here sits behind loadbalancers, and I use the path header to store the recieved details for each nat'ed contact, this "Recieved::" value is set, even when replicating and I think the nathelper module may be assuming that it therefor needs to ping this replicated contact. My registrar's have 2 interfaces, the primary interface is not on the same lan as the loadbalancers, so what happens in this instance is that nathelper tries to send an options to a contact that has been replicated, I presume, it then looks at the socket info to see which socket to send the request out of, doesnt find any for a replicated contact, and then proceeds to send it out of the primary interface. Is there any other way that I could try to get the nathelper module to ignore contacts thats have not been processed by the local kamailio instance. I am running in memory mode only, I do not use the database for usrloc entries, I keep the location "database" in memory only, and I sync the database using the dmq_usrloc module, which works beautifully btw :) Any tips/suggestions would be greatly appreciated. Thanks Bruce On 10/08/2015 13:43, Asgaroth wrote: