<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p><tt>Hi all,</tt><tt></tt><br>
</p>
<div class="moz-forward-container"><tt> The new </tt><tt><strong
style="font-weight: bold !important;"><em>mid-registrar</em></strong></tt><tt><span
class="Apple-converted-space"> </span></tt><tt>functionality
is now available with OpenSIPS 2.3 (current development branch)!</tt><br>
<b><tt><br>
What is a mid-registrar?</tt></b><br>
<tt><br>
The</tt><tt><span class="Apple-converted-space"> </span></tt><tt><span
class="emphasis"><em>mid-registrar</em></span></tt><tt><span
class="Apple-converted-space"> </span></tt><tt>is a
mid-component of a SIP platform, designed to work between end
users and the platform's main registration component. It opens
up new possibilities for leveraging existing infrastructure in
order to continue to grow (as subscribers and as registration
traffic) while keeping an existing low-resources registrar
server.<br>
<br>
</tt><tt><b>What can a mid-registrar help with?</b><br>
<br>
</tt><tt>Acting as a registration front-end to the main SIP
registrar, the OpenSIPS</tt><tt><span
class="Apple-converted-space"> </span></tt><tt><em>mid-registrar</em></tt><tt><span
class="Apple-converted-space"> </span></tt><tt>is able to:</tt><tt><strong
style="font-weight: bold !important;"><br>
<br>
* Convert incoming high</strong></tt><tt>-rate
registration traffic into a low-rate variant, towards the main
registrar layer. With proper configuration, it can absorb over
90% of existing registration traffic while preserving the
back-end's user location state, effectively reducing resource
usage at the respective layer.</tt><tt><strong
style="font-weight: bold !important;"><br>
<br>
* Add support for parallel calling</strong></tt><tt><span
class="Apple-converted-space"> </span></tt><tt>(registration
based) to registrar servers which are not able to provide such
functionality; The OpenSIPS mid-registrar can aggregate all the
registered contacts from the same user (AOR) and push forward to
the main registrar a single registration per AOR. On the way
back, from the main registrar, an incoming call will be parallel
forked to all registered contacts of the user/AOR.</tt><tt><br>
<br>
<b>How to use the OpenSIPS mid-registrar?</b></tt><tt><br>
<br>
<a moz-do-not-send="true"
href="http://www.opensips.org/Documentation/Tutorials-MidRegistrar"
target="_blank"
data-mce-href="http://www.opensips.org/Documentation/Tutorials-MidRegistrar"
style="color: rgb(0, 170, 220);">A comprehensive tutorial</a></tt><tt><span
class="Apple-converted-space"> </span></tt><tt>is available,
explaining how the OpenSIPS mid-registrar can be used and how it
works.</tt><br>
<tt><br>
For more details on configuration options and available
functions, see the</tt><tt><span class="Apple-converted-space"> </span></tt><tt><a
moz-do-not-send="true"
href="http://www.opensips.org/html/docs/modules/2.3.x/mid_registrar.html"
target="_blank"
data-mce-href="http://www.opensips.org/html/docs/modules/2.3.x/mid_registrar.html"
style="color: rgb(0, 170, 220);">README file</a></tt><tt><span
class="Apple-converted-space"> </span></tt><tt>of the module.</tt><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>
</div>
</body>
</html>