<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<tt>Hi Sammy,<br>
<br>
Yes, you are correct . The current clustering support for usrloc
covers only simple replication (usually for HA purposes). The next
step is to achieve distribution and partitioning of registrations
across the cluster (this is work in progress) and it will be
available in the 2.3 release.<br>
<br>
Regards,<br>
</tt>
<pre class="moz-signature" cols="72">Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
<a class="moz-txt-link-freetext" href="http://www.opensips-solutions.com">http://www.opensips-solutions.com</a></pre>
<div class="moz-cite-prefix">On 14.06.2016 15:21, SamyGo wrote:<br>
</div>
<blockquote
cite="mid:CAJUJwtghi8qLRDkvd2XrsyQ5aTF_nTCN3q_wyMv9SZOmuuj61w@mail.gmail.com"
type="cite">
<p dir="ltr">Thanks Bogdan,</p>
<p dir="ltr">Will it be correct to say that usrloc replication is
not the way to go if a mesh cluster of OpenSIPS, with every node
knowing all the online subscribers anywhere, is to be created. !</p>
<p dir="ltr">Also, even if I do set ip_nonlocal_bind would each
OpenSIPS getting this replicated registration start sending
keepalives to that subscriber too? </p>
<p dir="ltr">Do you think a shared redis cluster for storing AoRs
is more suitable for the task instead of this approach!</p>
<p dir="ltr">Thanks,<br>
Sammy</p>
<div class="gmail_quote">On Jun 14, 2016 06:07, "Bogdan-Andrei
Iancu" <<a moz-do-not-send="true"
href="mailto:bogdan@opensips.org">bogdan@opensips.org</a>>
wrote:<br type="attribution">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF"> Hi Sammy,<br>
<br>
The registration records are usually bound to an interface
(the ip and port the registration was received) - that
interface will be used all the time in the communication
with the registered end point.<br>
<br>
Now, when if server A receives the Registration on interface
X, and this is replicated to server B, this server B may not
have the X interface, but something else (an Y interface).
So the registration record will loose some information (the
interface it is bound to). This is the nature of the error
message you see.<br>
And yes, using the ip_nonlocal_bind options is the way to
go.<br>
<br>
Once replicated, the registration records are independent
and they do not depend on the what is happening with the
original node (where the registration was pushed from).<br>
<br>
Regards,<br>
<pre cols="72">Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
<a moz-do-not-send="true" href="http://www.opensips-solutions.com" target="_blank">http://www.opensips-solutions.com</a></pre>
<div>On 14.06.2016 09:35, SamyGo wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">Hi,
<div>I've a cluster setup with userloc replication
enabled for 3+ servers. As soon as a user register
anywhere the other servers which receive this
replicated contact display these errors:<br>
<font face="monospace, monospace"><br>
</font>
<div><font face="monospace, monospace">ERROR:usrloc:receive_ucontact_insert:
non-local socket <udp:1X.2XX.XX.XX:5060></font></div>
<div><font face="monospace, monospace">ERROR:usrloc:receive_ucontact_insert:
failed to process replication event. dom:
'location', aor: '<a moz-do-not-send="true"
href="mailto:89654@1X.2XX.XX.XX" target="_blank">89654@1X.2XX.XX.XX</a>'</font></div>
<div><font face="monospace, monospace">ERROR:usrloc:receive_binary_packet:
failed to process a binary packet!</font></div>
</div>
<div><br>
</div>
<div>The solution(kind of) for the same error has been
discussed in this thread:</div>
<div><a moz-do-not-send="true"
href="http://lists.opensips.org/pipermail/users/2015-February/030910.html"
target="_blank">http://lists.opensips.org/pipermail/users/2015-February/030910.html</a><br>
</div>
<div><br>
</div>
<div>The question here is, is setting <i>ip_nonlocal_bind
</i>for this userlocation replication a solution ? or
should the replication mechanism be modified to
process the replications from other nodes !</div>
<div><br>
Say even if this works, the next question is, what
would happen to the contacts from a server which is no
longer active. The Contacts disappear as soon as the
clusterer node becomes inactive ?<br>
<br>
</div>
<div>Looking for some clarity on this topic.</div>
<div><br>
</div>
<div>Regards,</div>
<div>Sammy</div>
<div><br>
</div>
</div>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
Users mailing list
<a moz-do-not-send="true" href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a>
<a moz-do-not-send="true" href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a>
</pre>
</blockquote>
<br>
</div>
</blockquote>
</div>
</blockquote>
<br>
</body>
</html>