Table of Content (hide)
The current (pre 2.0) OpenSIPS internal design is based on some concepts older than 9 years. At the time, the requirements were few (simple stateless UDP proxy) and the decisions were made accordingly. But with all the additions, both in SIP and functionality (like TCP/TLS, script manipulation, dialog support, external integration, etc), the existing design is not able to cope with the requirements and use-cases any more.
List of issues that the new design wants to solve.
For almost an year discussions were carried and feedback was received about what issues need to be addressed by the new design.
In other words, the whole community was invited to contribute in generating the set of requirements for drafting the new design for OpenSIPS.
Requirements for the new design
The first step in making the new design a reality was to compile all the information to generate a proposal / draft for the design OpenSIPS.
Full and detailed description of a the new design.
First code release of OpenSIPS 2.0 is available for public. This first stage is a partial implementation covering lower layers (transport, parser, messages, dns, MI, DB) and the asynchronous core. The functionality is limited to a stateless SIP proxy (relay).
See here full description of capabilities
Work still in progress.