<div dir="ltr">Maybe you can use the <span style="color:rgb(0,0,0);font-family:Helvetica,Arial">nat_keepalive function of the </span>nat_traversal module instead of automatic keep alive checks?<div><div><div><div><br></div><div><br></div></div></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Apr 18, 2016 at 11:07 AM, Max Mühlbronner <span dir="ltr"><<a href="mailto:mm@42com.com" target="_blank">mm@42com.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I just found this bug which turned into a feature request (from 2012) someone else had exactly the same problem:<br>
<br>
<a href="https://sourceforge.net/p/opensips/feature-requests/99/" rel="noreferrer" target="_blank">https://sourceforge.net/p/opensips/feature-requests/99/</a><br>
<br>
<br>
@Bogdan, if for whatever reason the table is being shared by two Opensips instances (In my case it's not for balancing/failover at all but just for having the registrations for two servers in one central place for checking with external scripts/other optimizations...)<br>
<br>
Shouldn't each instance check whether it's his client or not before sending the keepalive/OPTIONS pings? This would fix the problems in scenarios like mine and i would guess there are a lot of people with the same problem: but they probably never noticed it, or never will.<br>
<br>
<br>
Best Regards<br>
<br>
<br>
Max M.<span class="im HOEnZb"><br>
<br>
On 07.04.2016 13:00, Max Mühlbronner wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi,<br>
<br>
I experienced something weird: I got two servers sharing the same location table. (usrloc module)<br>
<br>
My problem is: both servers got nathelper ping (OPTIONS) enabled. The Opensips instance A has it's own clients and instance B also...<br>
<br>
Now as the location database/table is being shared by both servers the NAT Pings from Instance B are also sent for clients which are registered on instance A.<br>
<br>
I did not find any solution to tell Opensips A/B to only ping "their" registered clients. The force_socket option of nathelper will not solve my issue as both servers got their own socket/IP.<br>
<br>
Is there any workaround for my situation? (Nat ping does not take the socket/IP of the registered client into account?)<br>
<br>
<br>
Best Regards<br>
<br>
</blockquote>
<br>
<br>
<br></span><div class="HOEnZb"><div class="h5">
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
</div></div></blockquote></div><br></div>