<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<tt>Hi, Ewgeny!<br>
<br>
The usrloc binary replication is only the first step in the
direction of an horizontally scalable OpenSIPS cluster. It is
designed to provide a hot-backup registrar, through the use of a
Virtual IP.<br>
<br>
To answer your questions:<br>
<br>
1) with usrloc binary replication, if the primary machine reboots,
the VIP will automatically switch over to the hot backup, and the
SIP registrar solution will continue to work. Once server 1 comes
back online (in secondary mode) it will gradually become
up-to-date with server 2 (current primary), within a couple of
hours.<br>
<br>
2) dialog replication is currently implemented in a similar
manner, with a hot backup, and no need for an SQL database in
order to keep real-time information.<br>
<br>
<br>
We are currently working on providing a distributed SIP registrar
solution in the upcoming OpenSIPS 2.2 LTS. You can read some of
the discussions around it here [1]. Questions / suggestions are
welcome!<br>
<br>
[1]: <a class="moz-txt-link-freetext" href="http://www.opensips.org/Community/IRCmeeting20150527">http://www.opensips.org/Community/IRCmeeting20150527</a><br>
<br>
</tt>
<pre class="moz-signature" cols="72">Liviu Chircu
OpenSIPS 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 29.02.2016 16:06, <a class="moz-txt-link-abbreviated" href="mailto:evoip@ukr.net">evoip@ukr.net</a>
wrote:<br>
</div>
<blockquote cite="mid:56D4507E.6030102@ukr.net" type="cite">
<meta http-equiv="content-type" content="text/html;
charset=windows-1252">
Hi !<br>
<br>
It's really nice option - that now Opensips nodes can replicate
"SIP registrations" and "Dialogs" between each other w <strong
style="color: rgb(51, 51, 51); font-family: Arial, sans-serif;
font-size: 14px; font-style: normal; font-variant: normal;
letter-spacing: normal; line-height: 22.2222px; orphans: auto;
text-align: start; text-indent: 0px; text-transform: none;
white-space: normal; widows: 1; word-spacing: 0px;
-webkit-text-stroke-width: 0px; background-color: rgb(255, 255,
255);">"bin_listen<span class="Apple-converted-space"> "
options.<br>
<br>
<a moz-do-not-send="true" class="moz-txt-link-freetext"
href="http://www.opensips.org/Documentation/Interface-Binary-2-1">http://www.opensips.org/Documentation/Interface-Binary-2-1</a><br>
</span></strong><br>
I have a few question related to cluster architecture with fail
over: <br>
<br>
1). <br>
<br>
- If one of the "Opensips phone edges" was restarted - can it
catch all USRLOC registrations through binary interface from alive
nodes ? <br>
- if it can't do restoring of the database through binary
interface - maybe you have an idea how to do that ?<br>
<br>
<br>
2).<br>
<br>
- it's share dialogs information - if one node is suddenly down,
can call dialog be proceeded on other node ?<br>
<br>
<pre class="moz-signature" cols="72">With kind regards,
Ewgeny Berladin
Voip Engineer</pre>
<br>
<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>
</body>
</html>