The development of new features for next major release, Kamailio v5.1, is going to be frozen on Monday, October 16, 2017. The master branch received plenty of new features since the release of v5.0, which was out by end of February 2017.
Next release will bring at least 7 new modules (although we are expecting one or more to make it in during next days). Not really up to date, the list of new features is collected in the wiki page at:
To sync properly for the next major release of Kamailio (v5.1.0) and ongoing development, we propose an IRC devel meeting for next week, on Wednesday, Sep 27, 2017. An alternative would be the following day, Sep 28, or if there are many devs that want to attend and cannot do it these days, we can look at another date. Just propose new day and time via sr-dev mailing list.
The meeting is going to be held as usual in the #kamailio channel on freenode.net IRC network.
A wiki page was created to collect the topics that are wanted to be discussed:
We want to highlight another project that uses Kamailio, which together with FreeSwitch, is part of PyFreeBilling, an open source billing platform targeting VoIP wholesale. It is released under AGPLv3.
Kamailio SIP Server v5.0.3stable is out – a minor release including fixes in code and documentation since v5.0.2. The configuration file and database schema compatibility is preserved, which means you don’t have to change anything to update.
Kamailio v5.0.3 is based on the latest version of GIT branch 5.0. We recommend those running previous 5.0.x or older versions to upgrade. There is no change that has to be done to configuration file or database structure comparing with the previous release of the v5.0 branch.
You can find some good hints and tips about using Kamailio for building intelligent SIP routing.
As usual, we would like to thank for spending time and financial resources for promoting Kamailio. Should you present at a large world wide event or small meetup in your area and have some notes about Kamailio, we definitely appreciate it a lot and we are more than happy to host a copy of the slides on our events directory:
(1) the define conditions on SQL_ACC were removed — this was enabled for more than 10 years and only made the code look complex and hard to follow up its logic.
(2) the code related to DIAMETER accounting was relocated to acc_diameter (new) module. It was a consistent size of code that was not enabled for sooo… long. It is now a dedicated module, similar to acc_radius. The diameter accounting code, even a new module now, is in the same stage, compiling but not tested, in pair with auth_diameter module, it may work, but very likely not.
In summary, what’s important for those using the acc module — it offers the same functionality as it was enabled by default in the past 10 years or more: writing accounting records to syslog and sql databases — only the unused code was relocated.
The acc module is now slimmer, only with the code that it needs, therefore easier to maintain and enhance for the future. For any issue, as usual open a report on Github project portal.