[OpenSIPS-Users] [NEW] Mid-registrar: scalable registration and call forking
liviu at opensips.org
Wed Dec 21 04:09:07 EST 2016
Very good questions!
- thanks for pointing this out; I have put mid-registrar replication on
the TODO list (the code needs just a few tweaks in order for this to work)
- throttling SUBSCRIBE/PUBLISH requests is definitely feasible (there
were actually quite a few discussions regarding this during both ClueCon
and AstriCon). Just as a note, the mid-registrar implementation is very
light, and cannot be quickly reused in the code of the presence modules,
since it relies on an usrloc API extension.
Thanks for the feedback!
On 20.12.2016 21:18, SamyGo wrote:
> Hi Liviu,
> This looks very neat. This was somewhat possible previously as well
> using customized opensips.cfg, but now its more of a built-in function
> and I like it. However, couple of questions came to my mind after
> going through this.
> - Is this mid-registrar compatible with proto_bin ? Like what if I
> want to have 2+ mid-registrar in Active/Passive mode and registrations
> to be replicated.
> - Can this module help me in PRESENCE handling not just IM/Messaging?
> Like SUBSCRIBE/PUBLISH handling (or redirecting)
> Again big applause for the awesome work.
> Thanks and best regards,
> On Tue, Dec 20, 2016 at 9:33 AM, Liviu Chircu <liviu at opensips.org
> <mailto:liviu at opensips.org>> wrote:
> Hi all,
> The new */mid-registrar/*functionality is now available with
> OpenSIPS 2.3 (current development branch)!
> What is a mid-registrar?*
> The/mid-registrar/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.
> *What can a mid-registrar help with?*
> Acting as a registration front-end to the main SIP registrar, the
> OpenSIPS/mid-registrar/is able to:*
> * Convert incoming high*-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.*
> * Add support for parallel calling*(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.
> *How to use the OpenSIPS mid-registrar?*
> A comprehensive tutorial
> available, explaining how the OpenSIPS mid-registrar can be used
> and how it works.
> For more details on configuration options and available functions,
> see theREADME file
> the module.
> Liviu Chircu
> OpenSIPS Developer
> http://www.opensips-solutions.com <http://www.opensips-solutions.com>
> _______________________________________________ Users mailing list
> Users at lists.opensips.org <mailto:Users at lists.opensips.org>
> Users mailing list
> Users at lists.opensips.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Users