Asterisk 1.4.18-rc4 Now Available

Asterisk 1.4.18-rc4 is now available.

This release candidate includes an important fix for a regression related to the
use of codec_g729 that caused decoders to not get properly released. Additional
fixes added today that are included in this release candidate include:

  • fixes for some locking errors in chan_agent
  • a memory leak related to the use of AMI redirect
  • Solaris compatibility fixes
  • a fix related to call recordings from Monitor getting deleted before being mixed if a blind transfer is done from a Queue.

Thanks to everyone that has jumped on to help out with testing of release candidates! It has already been extremely helpful.

This release candidate is published for anyone that is interested in helping to test it for a couple of days before it is officially released. To download the release candidate, use the following svn command:

$ svn co asterisk-1.4.18-rc4

If you would like it in tarball format, use the following commands:

$ svn export asterisk-1.4.18-rc4
$ tar -czvf asterisk-1.4.18-rc4.tar.gz asterisk-1.4.18-rc4/


Asterisk 1.6 Features: TLS for Manager (AMI) and HTTP

I have pointed out this file before, but I’d like to point it out again. If you’re curious what new features have been added for Asterisk 1.6 since 1.4 was released, then check out the CHANGES file. The current version of it can be found here.

There are a lot of cool features in there, so I’ll pull some out from time to time to highlight them.

One of the nice features in this version is native TLS support for the Asterisk manager interface as well as the built-in HTTP server. This was developed by one of our outstanding community developers, Luigi Rizzo. This means that it is easier to make applications that use these interfaces more secure. For example, users of the AsteriskGUI that is bundled with AsteriskNOW will have an easier time setting up secure access to configure Asterisk from a web browser. Previously, the way to do this was to proxy communication with Asterisk through a web server such as Apache or lighttpd.

Turning on this feature is easy. For the manager interface, only two options are required in the [general] section of manager.conf:

sslenable = yes
sslcert = /var/lib/asterisk/asterisk.pem

For the HTTP interface, the exact same two options are required, but for http.conf.

We take security very seriously in the Asterisk project. This has really been demonstrated through our current process for handling security issues that get reported to us. Now, in Asterisk 1.6, with TLS support for SIP signalling, The Asterisk Manager Interface (AMI), as well as the HTTP interface, we’re making it even easier to secure communications with your Asterisk server.

Asterisk 1.4.18-rc3 Now Available

Asterisk 1.4.18-rc3 is now available. The important bug fixes that made it into this RC are a couple of crash fixes for ChanSpy/MixMonitor. A few other less severe bug fixes made it in, as well.

This release candidate is published for anyone that is interested in helping to test it for a couple of days before it is officially released. To download the release candidate, use the following svn command:

$ svn co asterisk-1.4.18-rc3

If you would like it in tarball format, use the following commands:

$ svn export asterisk-1.4.18-rc3
$ tar -czvf asterisk-1.4.18-rc3.tar.gz asterisk-1.4.18-rc3/


Asterisk 1.6.0-beta2 and 1.4.18-rc2 Now Available

The Asterisk development team has released versions 1.6.0-beta2 and and 1.4.18-rc2.

The new beta for 1.6 is available for download from

The release candidate for 1.4.18 is only available via svn. It is available for anyone that would like to help test 1.4.18 over the next couple of days before it gets officially released.

To download the 1.4.18 release candidate:

$ svn co 1.4.18-rc2

To make a tarball out of the previous checkout, do:

$ svn export asterisk-1.4.18-rc2
$ tar -czvf asterisk-1.4.18-rc2.tar.gz asterisk-1.4.18-rc2/

Please report any issues to

Thank you for your support!

Digium Relaxes Google AdWord Policy

If you heard anything about the recent policy changes made by Digium in regards to the usage of its trademarks with Google AdWords, then be sure you see the official response from our CEO, Danny Windham, on the Digium blog.

From the response:

Over the past week we have received a number of charged responses regarding the recent change in policy related to the use of Digium trademarked terms in Google AdWords. Some of the responses supported our attempts to better control the use of Digium trademarked terms. Some of the responses disagreed with the policy, but respected Digium’s right to have changed the policy. Others were from individuals who clearly were unhappy with the change and the process by which it was implemented. We have listened carefully to the feedback, and as a result are relaxing our Google AdWord policy.

Asterisk 1.6.0-beta1 released

The development team has published Asterisk version 1.6.0-beta1. Everyone is encouraged to help test Asterisk 1.6, so that the release may be available soon.

Asterisk 1.6 will be the first major release of Asterisk since 1.4, which was released just over one year ago. This release contains a number of new features, as well as architectural improvements for improved performance.

A list of the new features is available in the CHANGES file:

Asterisk 1.6 also brings about a new release management style. This release management policies have been changed for Asterisk 1.6 to account for some of the things we have learned while maintaining Asterisk 1.2 and 1.4 in the past. For more information on the new release management policy, see the following thread on the asterisk-dev mailing list:

The support levels for Asterisk 1.2 and 1.4 will not change in the near future. There are no current plans as to when the support of those releases will change. Those decisions will be made as a result of discussions in the developer community when the time comes, and a public announcement will be made
with plenty of advance notice before anything changes.

Thank you for the support, and we look forward to your feedback on this release!