<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Great, this could be the solution to my
problem. I had no idea, i will look into it.<br>
<br>
Thanks very much.<br>
<br>
<br>
Best Regards<br>
<br>
Max M.<br>
<br>
On 18.04.2016 12:21, Benjamin Cropley wrote:<br>
</div>
<blockquote
cite="mid:CAF7jiz+jZ=ZmUsR=Zy36ORckfEMFENaGMrTe-FFwrL79odXg0w@mail.gmail.com"
type="cite">
<pre wrap="">Maybe you can use the nat_keepalive function of the nat_traversal module
instead of automatic keep alive checks?
On Mon, Apr 18, 2016 at 11:07 AM, Max Mühlbronner <a class="moz-txt-link-rfc2396E" href="mailto:mm@42com.com"><mm@42com.com></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">I just found this bug which turned into a feature request (from 2012)
someone else had exactly the same problem:
<a class="moz-txt-link-freetext" href="https://sourceforge.net/p/opensips/feature-requests/99/">https://sourceforge.net/p/opensips/feature-requests/99/</a>
@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...)
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.
Best Regards
Max M.
On 07.04.2016 13:00, Max Mühlbronner wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hi,
I experienced something weird: I got two servers sharing the same
location table. (usrloc module)
My problem is: both servers got nathelper ping (OPTIONS) enabled. The
Opensips instance A has it's own clients and instance B also...
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.
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.
Is there any workaround for my situation? (Nat ping does not take the
socket/IP of the registered client into account?)
Best Regards
</pre>
</blockquote>
<pre wrap="">
_______________________________________________
Users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a>
<a class="moz-txt-link-freetext" href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a>
</pre>
</blockquote>
<pre wrap="">
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a>
<a class="moz-txt-link-freetext" href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a>
</pre>
</blockquote>
<br>
<br>
</body>
</html>