<!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>Hi Ryan,<br>
      <br>
      This has nothing to do with dialog pining or accounting - the new
      interface allows OpenSIPS to replicate the dialog state to another
      OpenSIPS instance. If I misunderstood you, please rephrase :)<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 08:20 PM, Ryan Bullock wrote:
    <blockquote
cite="mid:CAAcj4gXoAEvw2WOj5F7wt9-xu-6bGtiOu-roT4eO0tnRF9SW9A@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div>This is pretty exciting!<br>
          <br>
          What are the plans for how this will work with features such
          as dialog pinging and accounting?<br>
          <br>
        </div>
        Regards,<br>
        <br>
        Ryan<br>
      </div>
      <div class="gmail_extra"><br>
        <br>
        <div class="gmail_quote">On Mon, Jul 29, 2013 at 9:46 AM,
          Bogdan-Andrei Iancu <span dir="ltr">&lt;<a
              moz-do-not-send="true" href="mailto:bogdan@opensips.org"
              target="_blank">bogdan@opensips.org</a>&gt;</span> wrote:<br>
          <blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt
            0.8ex; border-left: 1px solid rgb(204, 204, 204);
            padding-left: 1ex;">
            <div 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>
                &nbsp;&nbsp;&nbsp; - BIN is binary encoded so much faster (as
                performance)<br>
                &nbsp;&nbsp;&nbsp; - BIN interface has both sender and receiver in
                OpenSIPS (MI has only the receiver)<br>
                &nbsp;&nbsp;&nbsp; - MI is for external usage</tt><tt>, while BIN is
                internal (opensips2opensips)<br>
                <br>
                Regards,<br>
              </tt>
              <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>
                <div class="h5"> <br>
                  On 07/29/2013 06:22 PM, Liviu Chircu wrote: </div>
              </div>
              <blockquote type="cite">
                <div>
                  <div class="h5"> Hello all,<br>
                    <div> <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"
                        href="http://www.opensips.org/Documentation/Interface-Binary"
                        target="_blank">http://www.opensips.org/Documentation/Interface-Binary</a><br>
                      <br>
                      Best regards,<br>
                      <pre cols="72">-- 
Liviu Chircu
OpenSIPS Developer
<a moz-do-not-send="true" href="http://www.opensips-solutions.com" target="_blank">http://www.opensips-solutions.com</a></pre>
                      <br>
                    </div>
                    <br>
                  </div>
                </div>
                <pre><fieldset></fieldset>
_______________________________________________
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>
            </div>
            <br>
            _______________________________________________<br>
            Devel mailing list<br>
            <a moz-do-not-send="true"
              href="mailto:Devel@lists.opensips.org">Devel@lists.opensips.org</a><br>
            <a moz-do-not-send="true"
              href="http://lists.opensips.org/cgi-bin/mailman/listinfo/devel"
              target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/devel</a><br>
            <br>
          </blockquote>
        </div>
        <br>
      </div>
      <pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
Devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Devel@lists.opensips.org">Devel@lists.opensips.org</a>
<a class="moz-txt-link-freetext" href="http://lists.opensips.org/cgi-bin/mailman/listinfo/devel">http://lists.opensips.org/cgi-bin/mailman/listinfo/devel</a>
</pre>
    </blockquote>
  </body>
</html>