2008 January

January 2008

Asterisk 1.4 not only adds features to your PBX, it also adds enhanced voice quality for VoIP. The new and improved jitterbuffer implementation covers all RTP-based VoIP channels. Previoiusly, only the IAX2 channel driver had a jitter buffer implementation. (more…)

The Asterisk project has a very strict policy in regards to backwards compatibility. Unless we can’t find another solution, we’re not allowed to remove a function between releases. A configuration for Asterisk 2.4 should work in the next release. In order to be able to change functionality we warn users in one release and then remove the functionality in the coming release. So a configuration in 3.0 works in 3.2 but maybe not in 3.4.

This article tries to provide help with known problems with upgrading. Read on to learn how to avoid the traps! (more…)

Asterisk 1.4 delivers many new features. In regards to call state subscriptions, there are many news for you. Call state subscriptions are what makes the lamps blink on your phone when your collegue’s phone rings. In 1.4, you can make it blink based on activity in parking lots and meetme conferences as well. Read on! (more…)

Asterisk 1.4 introduces a new level of Jabber integration, developed by Matthew O’Gorman at Digium. The Asterisk Open Source PBX integrates with Jabber/XMPP in many ways. (more…)

I am proud to report that Alec Saunders report  that Infoworld reports that Yahoo is going to test OpenID. This is an important step for OpenID. I believe OpenID is a very good example of not trying to solve the whole puzzle with one solution, but build a small building block that moves us forward. I’ve blogged earlier about the importance of OpenID and how it relates to Enum and iname and… All the other solutions out there. I need an OpenID speaker for Bob 2.0 – anyone out there?Alec writes:

Infoworld reports this morning that Yahoo appears close to becoming an identity provider for OpenID. This, of course, is the next step in a full implementation. You can already use OpenID to log into Yahoo properties like Flickr, for instance.

Asterisk IdeasFor a long time, we have needed a platform for managing feature requests – things that the community or developers would like to see in Asterisk. We used to have a “feature request” category in the bug tracker, but there was no good way to handle them in the bug tracker and they where in the way for the work done by developers in the tracker. They ended up getting closed, only to be reachable by searching closed bug reports. Not a very good solution for brainstorms and good ideas.

The new site is basically a blog with comments and voting capability. You register on the site to be able to file a feature request. Other people may then add comments or vote for requests.

Hopefully, this will be a repository of ideas and a good discussion platform. Things will be stored and accessible. As usual, filing a feature request is not a guarantee that anything will happen. You still need to make sure developer resources are put to it somehow.

Please also remember that it’s not a support forum. You can’t get help in the idea repository. There are already mailing lists and forums in place for that.

Let’s try this out for a while and see if it’s a good tool that works for us. Register for an account on www.asteriskideas.org today!

Thanks for any feedback!


Happy New Year, Asterisk community!

During 2007 we accomplished a lot. We polished Asterisk 1.4 to a new state of readiness for production. We moved Asterisk 1.2 into no-maintenance mode, something I think we might have to reconsider after a discussion on the Asterisk-users mailing list. And we did not release anything new. Which is a good thing.

Why is that a good thing? Well, in an Open Source project you can choose between many different release strategies, depending on the software. Asterisk is a PBX. A PBX is in most cases something you don’t upgrade unless there’s a need to. We see that on the slow uptake everytime we release a new version of Asterisk. One year after the release of Asterisk 1.4, most of the installed base seems to run Asterisk 1.2. And they’re happy with it.

The problem is getting new features out there. We have a policy of not introducing new features to a released version of the software. That means we’re forcing people to upgrade to get new features – and new bugs. Would it be possible to create a new module interface so we can release various modules independently of the core? I don’t know, but that would create more complexity at the same time as it gives us a bit more flexibility for upgrades. At this point, 1.6 modules will not run in an 1.2 or 1.4 environment.

Anyway, I just wanted to write a note to say Happy New 2008! During this year, we hope to release a new version of Asterisk. During next year, you might be interested to put it into production. We developers just have to realize that it takes an awfully long time from idea to implementation in real life in the Open Source PBX market.