Interesting post listing PBX alternatives:
http://blog.voipsupply.com/uncategorized/need-an-ip-pbx-101-alternatives-to-cisco-and-avaya
... with Kamailio (OpenSER) included ...
Thursday, November 20, 2008
Carrierroute Extensions In Kamailio 1.5
Courtesy of Henning Westerholt and 1&1, carrierroute module got a bunch of new features that makes the module more flexible than ever and also fixed a few annoyances in the module usage:
1. Improved routing data loading
The module supports now the partioned loading of routing data during startup and reloads. In the past when one want to load big route set it was necessary to increase the private memory pool size, as the data was stored temporarily there. Now this is not necessary anymore, its possible to load route sets with e.g. 400.000 rules in the standard (private memory) configuration.
2. Efficient matching of domains and carriers
In the old implementation a simple linear list was used, this was replaced with a fast binary search function. The module can now look up carrier and domains in most cases with O(log n), which makes it more scalable when a big number of carriers and/ or domains are involved. Only when a dynamic string is used in the config script a full list search is needed.
3. Support for non-numerical prefix matching
Carrierroute now supports also the prefix matching with non-numerical characters. Its possible to use the entire standard ascii charset for route matching. This is configurable with a module parameter, the default implementation is still the know digit matching method. Please keep in mind that memory demands will increase somewhat when the extended matching is used. This additonal flexibility will probably bring a small overhead with it, as some additional logic is involved during the routing deciscion. But this will not be noticable on today standard servers.
4. Extensive refactoring and cleanups
Restructured and refactored the code in most areas, to make the module implementation and structure more understandable, maintainable and extensible. Replaced the usage of custom datatypes and fixup functions with the standard core implementation, switched to the autogenerated DB interface and use now standard glibc functions e.g. for the list search. Changed certain structures to not store the full name of carriers and domains in memory to save space and got finally rid of this mismatch between internal and external carrier ID.
More details about the new implementation can be found in the documentation at:
http://www.kamailio.org/docs/modules/devel/carrierroute.html
Porting hints, e.g. for the new database structure are provided at:
http://www.kamailio.org/dokuwiki/doku.php/install:1.4.x-to-1.5.0
Track the new features introduced in Kamailio devel at:
http://www.kamailio.org/dokuwiki/doku.php/features:new-in-1.5.x
1. Improved routing data loading
The module supports now the partioned loading of routing data during startup and reloads. In the past when one want to load big route set it was necessary to increase the private memory pool size, as the data was stored temporarily there. Now this is not necessary anymore, its possible to load route sets with e.g. 400.000 rules in the standard (private memory) configuration.
2. Efficient matching of domains and carriers
In the old implementation a simple linear list was used, this was replaced with a fast binary search function. The module can now look up carrier and domains in most cases with O(log n), which makes it more scalable when a big number of carriers and/ or domains are involved. Only when a dynamic string is used in the config script a full list search is needed.
3. Support for non-numerical prefix matching
Carrierroute now supports also the prefix matching with non-numerical characters. Its possible to use the entire standard ascii charset for route matching. This is configurable with a module parameter, the default implementation is still the know digit matching method. Please keep in mind that memory demands will increase somewhat when the extended matching is used. This additonal flexibility will probably bring a small overhead with it, as some additional logic is involved during the routing deciscion. But this will not be noticable on today standard servers.
4. Extensive refactoring and cleanups
Restructured and refactored the code in most areas, to make the module implementation and structure more understandable, maintainable and extensible. Replaced the usage of custom datatypes and fixup functions with the standard core implementation, switched to the autogenerated DB interface and use now standard glibc functions e.g. for the list search. Changed certain structures to not store the full name of carriers and domains in memory to save space and got finally rid of this mismatch between internal and external carrier ID.
More details about the new implementation can be found in the documentation at:
http://www.kamailio.org/docs/modules/devel/carrierroute.html
Porting hints, e.g. for the new database structure are provided at:
http://www.kamailio.org/dokuwiki/doku.php/install:1.4.x-to-1.5.0
Track the new features introduced in Kamailio devel at:
http://www.kamailio.org/dokuwiki/doku.php/features:new-in-1.5.x
Tuesday, November 18, 2008
SIP Router Project - GIT Repository Online
The GIT repository for sip-router is now online. GIT URLs:
- git://git.sip-router.org/sip-router (read only)
- http://git.sip-router.org/sip-router (read only, slower, git://… recomended)
- ssh://git.sip-router.org/sip-router (read write but account on git.sip-router.org needed)
Web interface:
- http://git.sip-router.org/cgi-bin/gitweb.cgi
For more info about GIT try:
http://git.or.cz/gitwiki/GitDocumentation
and if you want to know how it works:
http://eagain.net/articles/git-for-computer-scientists/
Special thanks go to Jan Janak, who not only did setup git.sip-router.org (including automatic cvs sync for some of the repos), but he’s also hosting it on one of his private machines.
More details here…
- git://git.sip-router.org/sip-router (read only)
- http://git.sip-router.org/sip-router (read only, slower, git://… recomended)
- ssh://git.sip-router.org/sip-router (read write but account on git.sip-router.org needed)
Web interface:
- http://git.sip-router.org/cgi-bin/gitweb.cgi
For more info about GIT try:
http://git.or.cz/gitwiki/GitDocumentation
and if you want to know how it works:
http://eagain.net/articles/git-for-computer-scientists/
Special thanks go to Jan Janak, who not only did setup git.sip-router.org (including automatic cvs sync for some of the repos), but he’s also hosting it on one of his private machines.
More details here…
Photos from Karlsruhe
Photo album that includes pictures from last week's Karlsruhe meeting of SIP Router project is available at:
http://sip-router.org/pub/photos/album-sip-router-karlsruhe/
http://sip-router.org/pub/photos/album-sip-router-karlsruhe/
Wednesday, November 12, 2008
SIP Router Project - The Meeting In Karlsruhe
Because of taking several days off, a complete report might show up a bit later, now a (short) summary...
First, many thanks to 1&1 for hosting the event and everyone that participated in such short notice. There were representatives from 10 companies:
- 1&1
- FhG Fokus
- Telio
- Asipto
- iptelorg/Tekelec
- Voztelecom
- Iptego
- Itsyscom
- Longphone
- Basis AudioNet
Some pictures should be published in the near future.
After going in short introduction and presentation of the goals from the point of view of each project (SIP Express Router (SER) and Kamailio (OpenSER)), we focused on:
- identification of potential points of conflicts and how to get to a resolution in such case
- code integration for common layer of the first phase
- future development and proposals of new features
- management of the larger eco-system that includes related projects and business entities
I will do several posts detailing what was discussed and proposed there for SIP Router project in few days. meanwhile, the outlines:
- it is hard to avoid conflicts just by some clear and strict rules, so the common sense should lead the collaboration and discussions
- GIT repository should be up in several days so the work can start, with a time line of 2-3 months from now to get core and tm in a very good shape of integration
- another meeting shall be set in about 3 months time, to allow enough time for people to be able to attend, adjust the development and look more deep at the future. While a lot of focus in the next months will be on integration, development of new features won't stop -- for example, steps to a partial asynchronous processing are undertaking, couple of new modules are planned for release, several other modules to bring new functionalities
- we should encourage and promote the development of related applications, like web interfaces, management tools, applications servers -- they add value for community and business
First, many thanks to 1&1 for hosting the event and everyone that participated in such short notice. There were representatives from 10 companies:
- 1&1
- FhG Fokus
- Telio
- Asipto
- iptelorg/Tekelec
- Voztelecom
- Iptego
- Itsyscom
- Longphone
- Basis AudioNet
Some pictures should be published in the near future.
After going in short introduction and presentation of the goals from the point of view of each project (SIP Express Router (SER) and Kamailio (OpenSER)), we focused on:
- identification of potential points of conflicts and how to get to a resolution in such case
- code integration for common layer of the first phase
- future development and proposals of new features
- management of the larger eco-system that includes related projects and business entities
I will do several posts detailing what was discussed and proposed there for SIP Router project in few days. meanwhile, the outlines:
- it is hard to avoid conflicts just by some clear and strict rules, so the common sense should lead the collaboration and discussions
- GIT repository should be up in several days so the work can start, with a time line of 2-3 months from now to get core and tm in a very good shape of integration
- another meeting shall be set in about 3 months time, to allow enough time for people to be able to attend, adjust the development and look more deep at the future. While a lot of focus in the next months will be on integration, development of new features won't stop -- for example, steps to a partial asynchronous processing are undertaking, couple of new modules are planned for release, several other modules to bring new functionalities
- we should encourage and promote the development of related applications, like web interfaces, management tools, applications servers -- they add value for community and business
Tuesday, November 11, 2008
IRC Devel Meeting Summary - Nov 06, 2008
I am trying to summarize the outcome of the IRC devel meeting from last Thursday, Nov 06, 2008. The log is available here...
Regarding the 1.3.x series, we set the 20th of November as the date for 1.3.4 release. There are several fixes and this branch is still used in many production environments, so it worths investing time in it. There are some updates in 1.4.x to be ported and some issues to be investigated.
For a new 1.4.x release (the 1.4.3) we look for the beginning of December as the time frame for setting the date of the release.
The 1.5.x rises in the first phase the question of a shorter time release, as we have lot of new features already implemented, see:
http://www.kamailio.org/dokuwiki/doku.php/features:new-in-1.5.x
http://www.kamailio.org/dokuwiki/doku.php/roadmap:1.5.x
Unfortunately some of the new features are not completed yet (e.g., htable, carrierroute updates, PV migration) so we will stick to 6-8 months release cycle. The next major one that will use the common layer (core and tm) from sip-router could be done in a shorter time than
usual. So, beginning to mid of January should be the time to freeze the code for a release date somewhere in end of January or February.
An important aspect approached during the discussions was the release management and testing management. Perhaps we need to appoint a person to manage releasing process in order to have a better synchronization of the developers. As everyone agrees, testing is very important and we try to improve it. There is a testing suite included in the source tree right now, used for static testing.
The idea of a dynamic testing and testing community was introduced and hopefully we can attract people and build a group of beta testers. There is a proposal of how to implement and what to take care of, probably this one has to continue on devel and users mailing lists for a proper
organizational structure.
GIT became as a subject of migrating from SVN, because of its features for a distributed development environment. However, sourceforge.net does not have such offerings, so it is not possible now anyhow. However the sip-router.org will use it.
Regarding the sip-router.org project, we focused on short term goals, acknowledging that we have several modules offering same functionality but relying on different underlaying data structures, this have to co-exists for a longer time. For the first phase, core + tm the overlapping is rather small, the two projects insisting in the past to improve different aspects of them.
Unfortunately I forgot to bring up some punctual topics proposed, mainly related to tm failure route calling in case of sending error and reply handling/dropping in onreply_routes.
Regarding the 1.3.x series, we set the 20th of November as the date for 1.3.4 release. There are several fixes and this branch is still used in many production environments, so it worths investing time in it. There are some updates in 1.4.x to be ported and some issues to be investigated.
For a new 1.4.x release (the 1.4.3) we look for the beginning of December as the time frame for setting the date of the release.
The 1.5.x rises in the first phase the question of a shorter time release, as we have lot of new features already implemented, see:
http://www.kamailio.org/dokuwiki/doku.php/features:new-in-1.5.x
http://www.kamailio.org/dokuwiki/doku.php/roadmap:1.5.x
Unfortunately some of the new features are not completed yet (e.g., htable, carrierroute updates, PV migration) so we will stick to 6-8 months release cycle. The next major one that will use the common layer (core and tm) from sip-router could be done in a shorter time than
usual. So, beginning to mid of January should be the time to freeze the code for a release date somewhere in end of January or February.
An important aspect approached during the discussions was the release management and testing management. Perhaps we need to appoint a person to manage releasing process in order to have a better synchronization of the developers. As everyone agrees, testing is very important and we try to improve it. There is a testing suite included in the source tree right now, used for static testing.
The idea of a dynamic testing and testing community was introduced and hopefully we can attract people and build a group of beta testers. There is a proposal of how to implement and what to take care of, probably this one has to continue on devel and users mailing lists for a proper
organizational structure.
GIT became as a subject of migrating from SVN, because of its features for a distributed development environment. However, sourceforge.net does not have such offerings, so it is not possible now anyhow. However the sip-router.org will use it.
Regarding the sip-router.org project, we focused on short term goals, acknowledging that we have several modules offering same functionality but relying on different underlaying data structures, this have to co-exists for a longer time. For the first phase, core + tm the overlapping is rather small, the two projects insisting in the past to improve different aspects of them.
Unfortunately I forgot to bring up some punctual topics proposed, mainly related to tm failure route calling in case of sending error and reply handling/dropping in onreply_routes.
Wednesday, November 5, 2008
SIP Router Project Kick Start Meeting
The meeting happens in very short time. Sorry for that, but probably it is better sooner that later as will mark the moment of integration start. It is the place to discuss the technical aspects of the integration, milestones and future development.
Place: Karlsruhe, Germany
Date: Monday, November 10, 2008
Registration: free
More details at:
http://sip-router.org/index.php/meeting/
The results of the meeting will be posted to the site and mailing lists.
Place: Karlsruhe, Germany
Date: Monday, November 10, 2008
Registration: free
More details at:
http://sip-router.org/index.php/meeting/
The results of the meeting will be posted to the site and mailing lists.
Tuesday, November 4, 2008
The SIP Router Project
The SIP Router Project started aiming to build a solid open source SIP routing platform, based on collaboration of the SIP Express Router (SER) and Kamailio (OpenSER) teams.
Developers of these two projects believe that an united and non-conflicting environment will bring many benefits, to them, community members and companies.
- bring together the developers and user communities of both projects
- reduce maintenance overhead
- avoid duplicated efforts in development
- develop a core framework that is flexible, extensible and scalable
- promote and build a solid open source SIP server project
- ensure business credibility
- make future forking undesirable, this harms everybody, affects credibility and business
You are welcome to join! Visit:
http://www.sip-router.org
Mailing list:
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
There will be a meeting for concluding the collaboration and kick start the integration. Everybody is welcome to join. See more details:
http://sip-router.org/index.php/meeting/
Developers of these two projects believe that an united and non-conflicting environment will bring many benefits, to them, community members and companies.
- bring together the developers and user communities of both projects
- reduce maintenance overhead
- avoid duplicated efforts in development
- develop a core framework that is flexible, extensible and scalable
- promote and build a solid open source SIP server project
- ensure business credibility
- make future forking undesirable, this harms everybody, affects credibility and business
You are welcome to join! Visit:
http://www.sip-router.org
Mailing list:
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
There will be a meeting for concluding the collaboration and kick start the integration. Everybody is welcome to join. See more details:
http://sip-router.org/index.php/meeting/
Subscribe to:
Posts (Atom)
Posts
