Friday, September 1, 2017

Kamailio v5.0.3 Released

Kamailio SIP Server v5.0.3 stable 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.
Resources for Kamailio version 5.0.3
Source tarballs are available at:
Detailed changelog:
Download via GIT:
 # git clone https://github.com/kamailio/kamailio kamailio
 # cd kamailio
 # git checkout -b 5.0 origin/5.0
Relevant notes, binaries and packages will be uploaded at:
Modules’ documentation:
What is new in 5.0.x release series is summarized in the announcement of v5.0.0:
Thanks for flying Kamailio!

Tuesday, August 22, 2017

Kamailio Presentation At ClueCon 2017

Fred Posner, our big friend (and baker from Florida), participated to ClueCon Conference 2017 and gave a presentation about Kamailio SIP Server. The slides deck is available at:
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:
Just get in touch with us!
Thank you for flying Kamailio!

Wednesday, August 9, 2017

ACC – SQL Define Removed And Diameter Code Relocated

The ACC module (accounting) in Kamailio got a bit of clean up, therefore be aware of following changes:
  • (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.
Thanks for flying Kamailio!

Tuesday, August 1, 2017

Research On VoIP Fraud Using Kamailio As Sensor

Konstantin Tumalevich has posted an article via GitHub about his research done on VoIP fraud using Kamailio as a sensor, along with other VoIP applications such as Asterisk.
Some interesting facts extracted from the article:
For research, I created honeypot what mimics vulnerable PBX.
For emulation, I used Kamailio nodes that send any calls to termination node and answers to OPTIONS and REGISTER.
For every INVITE I recorded From, To, UA, Call-ID, IP and call time.
Termination node has Kamailio with Flask app for preprocessing calls and Asterisk for topology hiding when calls sent to PSTN.
All calls with a cost of more than 2 cents per minute were rejected with code 486.
I used 4 sensor nodes located in NL, DE, SG and NYC.
For 18 days, 254805 INVITE were collected from 296 different IP’s. On average, 860 INVITEs were received from an IP.
Reports about top source IPs, countries of origin and the operator as well as related graphs can be found in the conclusions of the research. Few hints are also provided about how to protect better.
You can read the entire article at:
Enjoy!
Thanks for flying Kamailio!

Monday, July 24, 2017

ClueCon 2017

As every August for more than a decade, the ClueCon conference takes place again in Chicago, USA, during August 7-10, 2017. Mainly organised by the people behind FreeSwitch project, ClueCon is among those events where you can meet a large group of experienced people with open source realtime communication technologies.
Kamailio will be present with a talk by Fred Posner, one of our very active advocates of the project in North America and not only. His presentation is scheduled for Wednesday, August 9, at 10:45am:
Besides Fred, you will be able to meet other relevant members of Kamailio project or friends from the VoIP world! If you haven’t checked the event so far, do it very soon and consider to register, no much time left and ClueCon is always worth attending! Read moreabout the event at:
Enjoy!
Thank you for flying Kamailio!

Tuesday, July 18, 2017

dSIPRouter – GUI For Kamailio SIP Trunking

dSIPRouter is a web GUI that facilitates deploying Kamailio for SIP trunking services, developed by dOpensource.com and offered as open source on Github under Apache 2.0 license.
It allows to manage the carriers and PBXes from a modern front end web GUI, built in Python. The application was developed for Kamailio 4.4.x series and tested mainly on CentOS.
Enjoy!
Note: should you develop or are aware of any application that is related to Kamailio, do not hesitate to contact us, we will happily publish a news about it on kamailio.org.
Thanks for flying Kamailio!

Monday, July 10, 2017

IvozProvider: Kamailio And Asterisk Based VoIP System

IvozProvider is a provider oriented multilevel IP telephony solution for use on public internet or private networks. It allows multiple access levels within the same infrastructure, from operator administrator to granular brand and company administrators as well as end user.
Here is an excerpt from its presentation:
“IvozProvider was designed always keeping in mind the horizontal scaling of each of its elements, so it can handle hundred of thousands concurrent calls and what is more important, adapt the platform resources to the expected service quality.”
It relies on an handful of open source applications, including Kamailio, RTPEngine, Asterisk, MySQL or JsSIP.
The project is available on Github at:
It has quite an extensive documentation online, offering several options for an easy install:
It is developed by Irontec, the company being another popular SIP-related project, respectively sngrep.

Friday, July 7, 2017

SIREMIS – Ongoing Updates

There is some ongoing work on Siremis (web management interface for kamailio) to make it fully compatible with Kamailio 5.0.x as well as update some of its legacy components:
So I thought to start a discussion here and see if some of those changes are going to impact too much existing installations or what are the best options to use for the future.
Done so far:
  • 1) implemented the JSONRPC client using UDP and unix domain sockets, to work in pair with jsonrpcs module as a replacement for removed MI interface. The old JSONRPC over HTTP is still an option.
  • 2) charts system has been migrated from open flash chart (ofc) to echarts (pure html5/javascript) — therefore no more requiring to enable flash in browser. Configuration is the same and the charts should look pretty similar. If you upgrade, apart of different html view for the charts, the config files should not be changed. If you notice something broken, open an issue on github project linked above.
Planned to be done:
  • 3) Relocate siremis/modules/ser to siremis/modules/sipadmin — this purely for more suggestive name for the admin module related to the SIP services offered by Kamailio, and be in pair with the module sipuser. This is mainly search and replace over php and xml files, however, it is going to impact if you developed your own internal extensions for Siremis and placed them in the ‘ser’ module. It will require that you do the same search+replace
  • 4) Review existing database tables views and add fields for missing columns.
  • 5) Add views for other database tables. First in my mind being the table for rtpengine module. If you use some modules with tables not yet managed by Siremis, reply and list them to set a list of priorities.
Should have other things to report about Siremis and are not yet listed on project’s issue tracker, let’s discuss here.
Testing and feedback for 1) and 2) are very appreciated!
Thanks for flying Kamailio!