<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#ffffff">
<tt>In long term we plan to use the BIN interface to replicate even
more internal data between multiple OpenSIPS instances, like doing
registration replication (instead of doing it from script via
SIP). Theoretically it may be used for replicating even
transaction state between 2 OpenSIPS instances - imagine having a
call ringing on instance A and being accepted on instance B (after
a failover) - 0% losses !<br>
<br>
Aside realtime data replication, the BIN interface is to be used
also for exchanging any other type of information between OpenSIPS
instances, like federating multiple instances.<br>
<br>
The main advantages of the BIN interface over the MI interface :<br>
- BIN is binary encoded so much faster (as performance)<br>
- BIN interface has both sender and receiver in OpenSIPS (MI
has only the receiver)<br>
- MI is for external usage</tt><tt>, while BIN is internal
(opensips2opensips)<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>
<br>
On 07/29/2013 06:22 PM, Liviu Chircu wrote:
<blockquote cite="mid:51F688BA.8030208@opensips.org" type="cite">
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
Hello all,<br>
<div class="moz-forward-container"> <br>
OpenSIPS just got better with a <i>new core interface</i> and a
<i>new failover mechanism</i>!<br>
<br>
The purpose of the new <b>Binary Internal Interface </b>is to
offer a fast and efficient communication channel between
OpenSIPS instances. OpenSIPS modules can now use this core
interface to send/receive packets with specific information. A
common usage case for this feature would be data replication
between a primary instance and a backup one.<br>
<br>
This is especially useful in scenarios with OpenSIPS instances
which handle large amounts of concurrent calls, so that failover
through a database backend is not feasible anymore due to the
significant time required in order to load the needed tables.<br>
<br>
As an example of using the interface, the dialog module now
offers the possibility of <b>replicating dialogs</b> to another
instance. The script writer may now configure a set of proxies
which will receive dialog-related events: <i>creation</i>, <i>confirmation</i>
and <i>deletion</i>, all in <i>realtime</i>. These messages
are compact and they are sent over UDP. The dialog module now
also exports several new statistics which show the total
sent/received replication packets.<br>
<br>
Configuring UDP listeners for the new interface is trivial and
explained in the OpenSIPS manuals [1].<br>
<br>
[1]: <a moz-do-not-send="true" class="moz-txt-link-freetext"
href="http://www.opensips.org/Documentation/Interface-Binary">http://www.opensips.org/Documentation/Interface-Binary</a><br>
<br>
Best regards,<br>
<pre class="moz-signature" cols="72">--
Liviu Chircu
OpenSIPS Developer
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://www.opensips-solutions.com">http://www.opensips-solutions.com</a></pre>
<br>
</div>
<br>
<pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
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>
</body>
</html>