- freezing in 1-1.5 months

- 1-1.5 months testing

- release by end of September/ beginning of October

Right now, current development state is:

- all but one module (seas) were updated to work with the new core

- several addons in kamailio core and tm still to be included in GIT master branch

- many new features developed: mecached, event_route, xml doc handling … see:

http://sip-router.org/wiki/features/new-in-devel

All of you are invites to test, startup guidelines can be found at:

http://sip-router.org/wiki/migration/kamailio-3.0-config

You can send feedback at: <sr-dev [at] lists.sip-router.org>

Particularly, siptrace was refurbished a lot. Before release, there are couple of new features that should get in trunk since sip route core offers support for such extensions:

- ability to filter the ACK for negative replies issued by sl module in the script

- ability to store stateless forwarded messages (now only stateful ones being stored)

Testing is very much appreciated, see guidelines at Kamailio 3.0 Config wiki page.

event_route[groupid:eventid] {

    [actions]

}

The main purpose for it is to allow modules (and core) to be able to execute code written in configuration file when a specific event happens, without altering the config grammar. Also, in short term, the modules that fire events should be able to impose what type of actions can be used in the respective event_route – now functions allowed in request route can be used.

First module that uses this feature is htable, executing an event route only once, when all modules were initialised. A typical use case is to initialise some items in a hash table. Example:

modparam("htable", "htable", "a=>size=4;")

event_route[htable:mod-init] {

  $sht(a=>calls-to::10.10.10.10) = 0;

  $sht(a=>max-calls-to::10.10.10.10) = 100;

}

route {

  if(is_method("INVITE") && !has_totag())

  {

    switch($rd) {

      case "10.10.10.10":

        lock("calls-to::10.10.10.10");

        $sht(a=>calls-to::10.10.10.10) =

            $sht(a=>calls-to::10.10.10.10) + 1;

        unlock("calls-to::10.10.10.10");

        if($sht(a=>calls-to::10.10.10.10)>$sht(a=>max-calls-to::10.10.10.10))

        {

           sl_send_reply("500", "To many calls to .10");

           exit;

        }

      break;

      ...

    }

  }

}

This system will be used to get kamailio‘s error_route and local_route functionalities. Other cases I have in mind now are:

• auto-expired dialog route introduced in kamailio 1.5.0 to become event_route[dialog:auto-expired]
• call event route when a location record has expired on timer:event_route[usrloc:auto-expired] making available via PV details of expired contact
• rtimer module routes to become event routes

There is now a page to collect guidelines for the default Kamailio configuration file used with sip-router. We invite all of you to test it, not only this one, but your private configs as well.
http://sip-router.org/wiki/migration/kamailio-3.0-config

Feel free to add to the wiki page or post questions about it to sr-users@lists.sip-router.org. This is a new list created for users of sip-router project, you can subscribe to it at:
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

At this stage, sip router can be used with modules from both Kamailio (OpenSER) and SER projects, mixed in same instance at the same time. Therefore you can choose the best ones that fit your needs. For Kamailio (OpenSER) users there is a page that tries to collect new features they got from SER side (still a lot to add there, hope ser developers will contribute what they find missing). Another page collects links for ser and kamailio users to find what the other project brings:
http://sip-router.org/wiki/migration/new-features-for-k-users
http://sip-router.org/wiki/features/inherited-features

It was not only integration work in the past months, sip router has quite a bunch of brand new feature. The wiki page to collect the summary is available at:
http://sip-router.org/wiki/features/new-in-devel

Jan just set online documentation portal, available for web browsing:
http://sip-router.org/docbook/sip-router/branch/master/

Common modules are located in directory ‘modules’ while kamailio and ser specific modules can be found under module_k and modules_s. Project’s wiki portal got also good content and it is under heavy work — note that everyone can contribute to wiki:
http://sip-router.org/wiki

Couple of core and tm features are not yet integrated or not exactly as they were in Kamailio. Please report the ones you are missing in your config at:
http://sip-router.org/wiki/devel/kamailio-integration#tm_and_core_extensions

It is the place that should set the priority rank for integration. I hope that in 1-2 months time frame to get into beta stage and prepare a stable release.

Many thanks for those that allocated resources to make things evolve to this stage and many thanks in advance for those that will start testing and help improving the sip router project.

http://sip-router.org/docbook/sip-router/branch/master/

This is all the docbook documentation that we currently have in the repository, including the documents under doc, modules, modules_k, modules_s, and lib subdirectories.

The HTML documentation is updated automatically upon changes in the git repository.

http://sip-router.org/pub/events/2009-05-Amoocon/2009-amoocon-sip-router.org.pdf

The two day event, although Asterisk centric, brought many people from different projects and technologies around SIP and VoIP. Very interesting talks about integration with web and social networking, SS7 or database clustering.

SIP-Router.org and Kamailio (OpenSER) projects will be largely presented at the event by talks and case studies of:

• Daniel-Constatin Mierla: http://www.amoocon.de/users/14
• Olle E. Johansson: http://www.amoocon.de/users/61

If you are around Berlin the days before the event or in Rostock during the event and want to meet, discuss the current stage and future of SIP-Router.org, send an email to: <miconda [at] gmail (dot) com>

• Kamailio (OpenSER)
• SIP Express Router (SER)

For a period of time there will be available both mailing lists addresses, but we strongly encourage you to update your email agenda with the new mailing list address.

The Kamailio (OpenSER) archive is preserved, you can check it and register to the mailing list at:

http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users-es

http://sip-router.org/wiki/devel/kamailio-integration

Once the modules are completed, the last phase is to bring to sip-router the config extensions implemented in Kamailio (OpenSER) core – about 20 functions.