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 is available, explaining how the OpenSIPS mid-registrar can be used and how it works.
For more details on configuration options and available functions, see the README file of the module.
Drops of wisdom, knowledge and news from OpenSIPS 
One thought on “Mid-registrar: scalable registration and call forking”