http://sip-router.org/tracker/

Feel free to use it to report:

• bugs (code, documentation, web site)
• feature requests
• improvements

This is the common new development mailing list for SIP Express Router (SER), Kamailio (OpenSER), and SIP-Router projects. We will not be using the old mailing lists any more, although their email addresses still exist and they are forwarded to the new mailing list.

We migrated all subscribers from serdev@lists.iptel.org and devel@lists.kamailio.org to the new mailing list. Because mailman cannot migrate users while preserving all their settings, it is possible that some of the settings that you may have configured in the www interface of mailman got lost. If this is the case then, please, go to the www interface of the new mailing list at:
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
and restore them manually. We apologize for this inconvenience, but mailman does not seem to offer any tool that would automate this process.

Also, you may need to updated your email filters if you use them. The email address of the mailing list is sr-dev@lists.sip-router.org. The old mailing list addresses still work, thus you may occasionally see emails posted to serdev@iptel.org or devel@lists.kamailio.org. If you post an email to serdev@iptel.org or devel@lists.kamailio.org then it will be forwarded to this mailing list transparently.

Archives of the two former mailing lists are still available at:
http://lists.iptel.org/pipermail/serdev
http://lists.kamailio.org/pipermail/devel

and they’ll continue to be available there. We have no plans to move them elsewhere, because their locations are well known and they are referred from many other sites around the net. For your convenience the info page of the new list contains direct links to the old archives:

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

The new mailing list will receive commit logs from three source repositories:
1) SER cvs repository at BerliOS.de
2) Kamailio SVN repository at SourceForge.net
3) The shared git repository of SIP-Router.org
We can redirect some of the commitlogs somewhere else later if this generates too much traffic.

So, we hereby declare the mailing list open for all ser/kamailio/sip-router related traffic. Welcome everybody, have a lot of fun and hope to see you in many fruitful discussions.

SER and Kamailio developer groups

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

sr-users@lists.sip-router.org

You can subscribe to it at:

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

It is intended for community users, the early testers at this moment in time.

The other mailing lists available for the project are:

- sr-dev – for development related discussions
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev

- sr-users-es – sip router Spanish community mailing list
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users-es

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.

These are mostly my (Jan’s) personal suggestions, things that I consider nice-to-have
or interesting (and which I kept on my todo lists for far too long). Most of
them would make nice projects for students.

If you are a student, or if you supervise students, or if you are interested
in working on some of the topics then, please let me know. I’d be happy to
help you get started and provide some initial implementation guidance.

The list currently contains:

• Integration With User and Group Database in UNIX/Linux

• Dynamically Configured Mass Virtual Hosting

• Generic RADIUS Driver

• Syntax Highlighting of SER Configuration in Dokuwiki

• Internalization of Reason Phrases

• Multiplexing of SIP and RTP on One Socket

• Database Driver for Sqlite

• Overload Control for sip-router

• MAC Address Authentication and Authorization

• Python Integration

• SOCKS Support

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>