Many of you have probably skipped right to this section. Well, you can still read the above when you are finished with this.
The table below has listed some criteria and how SER and OpenSER address each. You should find the criteria important for you and decide based on that. Please contact gettingstarted@onsip.org if you have other criteria you feel should be present.
Criteria | SER | OpenSER |
Release frequency/new features | Long release cycles, you need to use the experimental module or the HEAD version to get new features | Frequently minor releases (0.a.x) with new features available. Major changes available in major releases (0.x), but no history of this yet |
Large user community | Well-established community with the serusers@iptel.org mailing list as the main exchange. Many active contributors. High volume and questions must be well writton out to receive an answer | Voice System/OpenSER core developers are very active and most questions are answered. |
Release quality/stability | The long release cycles and large community reduces the risk of running into bugs if you use a stable release. | The high focus on new features and frequent releases increases the likeliness of bugs in a stable release. The officially stated policy for stability is release often |
Documentation | Administrators manual at iptel.org is outdated, but still useful. The main source of module documentation is in the README files of each module. The OpenSER 0.9.x documentation can mostly be used. And this document is a good starter! | Very high focus on documentation. The modules README files, as well as some tutorials can be found at http://openser.org/docs/ A WIKI has also been created. And this document is a good starter! |
Support for various architectures | The person responsible for compiling on architectures works on SER | Hard to say, probably the OpenSER developers will try to merge in architecture changes from SER CVS |
Development participation | Code repository at:http://developer.berlios.de/projects/ser/ Patches (and bugs) to existing code should be submitted to http://bugs.sip-router.org/ or directly to the developer d in README). Modules or larger code extensions can be submitted to greger@teigre.com (maintainer of experimental module) | Code repository at http://sourceforge.net/projects/openser/ Send email to devel@openser.org (note! mailing list) |
Commercial support | Iptelorg.com sells commercial licenses of enhanced SER. Many consultants are present on the serusers@iptel.org mailing list | Voice System offers software and consulting. Availability of other consultants is unknown. |