OpenSIPS Forks OpenSER

Tom Keating : VoIP & Gadgets Blog
Tom Keating
| VoIP & Gadgets blog - Latest news in VoIP & gadgets, wireless, mobile phones, reviews, & opinions

OpenSIPS Forks OpenSER

Came across an announcement that OpenSIPS is forking from the popular open source OpenSER solution. OpenSIPS (Open SIP Server) became active today, with its first release (OpenSIPS 1.4.0). I found it a bit surprising that someone is forking OpenSER, since it's a very powerful SIP routing platform. I recently mentioned how OpenSER can be used to bridge Asterisk with Microsoft Office Communications Server 2007.

So what is OpenSIPS about? Well, let me include some snippets from the announcement made today:

OpenSER History:
Voice System started the OpenSER project with a vision of running an
open project that will deliver a professional software. Along the years
Voice System was the main contributor and sustainer of the OpenSER
project, organizing conferences, events and tutorials, all aiming to
consolidate OpenSER as a top solution for industry VoIP.

OpenSER Issues:
In the past time, several critical problems related to OpenSER project
were identified by us:
- the need for a new reliable release - delayed or low-quality releases
are affecting the credibility of the project
- degradation of the project quality - testing, performance measurements
and code quality control are overlooked
- lack of the control, management and coordination of the project -
critical project issues could not be handled or solved

OpenSIPS Solutions:
OpenSIPS is a continuation of the OpenSER project - we have a moral
obligation to develop and deliver the high quality and reliable software
we envisioned when starting OpenSER.

1) a 6 months release cycle, but with no compromise for the technical
2) extensive testing and performance measurements before each major release
3) contributions are guaranteed to be answered and integrated (if
accepted) in less than 1 month
4) code review, architecture control and integrated design for software
5) technical management with a strict developer hierarchy and developer
cooperation to prevent deadlocks or un-availabilities
6) intellectual honesty by having decisions taken on value-based
criteria and arguments.

Ok, I get that they're frustrated with how slow the OpenSER releases are, but is forking OpenSER the solution? I like the 6 month release cycle, code review, and architecture control. Just who is behind this effort? Is it simply VoIP enthusiasts, or is there some corporate backing going on here? And if so, what is the agenda?

Well, whoever is running OpenSIPS, it seems like someone was frustrated not only with the slow releases, but also the slow feature additions. They added these new features that are absent from OpenSER:
  • dialog profiling extension
  • local route for internally generated requests
  • dial plan / translation module
  • general NAT traversal module (for non-invite signalling)
  • peering and rate limit (traffic shaping) modules

    Enhancements like:
  • SRV load balancing (based on weights)
  • nonce re-usage verification (safer authentication)
  • and bug fixing - code, specs and functionality bugs.
I'm just digesting this news myself and I have another deadline I'm working on, so let me know your thoughts on this or if you have more info on OpenSIPS by posting a comment.

Featured Events