First goal is to have a common version that would run current SER and Kamailio (OpenSER) config scripts with minimal changes (if at all). We might have a config variable to switch from SER to OpenSER style config (if we can’t merge them completely). There won’t be any lost of functionality from any of the projects.

We considered that is better to start from one project and add from the other project – it is easier to build on an working version rather than pulling out from both and try to integrate. The collaboration will be tested by creating a common core and TM module. If this works out, further merging will be taken in consideration.

Initial integration:

• start with core and TM module taken from SER and then add from openser
• openser pseudo-variable framework
• openser script changes (e.g. case, while) and TM updates

Components to merge or adapt:

• module interface
• DB API compatibility mode
• Management Interface (MI) and SER RPC
• check if avps are compatible
• compatible per process timer
• openser statistics interface
• path support
• review OpenSER logs for other changes / bugfixes

Infrastructure:

• try to speed things up (take shortcuts, leave time consuming stuff for later discussions)
• name: sip-router.org (short form to be decided: srouter, sip-router, a.s.o)
• repository hosted at sip-router.org
• use GIT with cvs and svn access

A diagram showing how the integration work will start: