While this has been mentioned in a few places I thought it prudent to also create a blog post. Asterisk 13 and Asterisk 17 have entered security fix only status. What does this mean, though? When bug fixes and changes are put up for review they will no longer be done against Asterisk 13 and
Greetings Everyone! Another year has flown by and while we now live in interesting times this has not stopped the development and progress of Asterisk or the Astricon conference[1], so much so that the first release candidate of Asterisk 18 is here[2]. The first step in creating the 18.0.0 release of Asterisk is tagging a
We’ve had a few questions about whether or not Asterisk could easily install on CentOS 8. A few months ago the answer to that question was no. However, given some time, a few added packages later, and a custom open source repository contribution we now believe that answer has changed. In this post I’ll explain
Greetings All, Time certainly flies and it seems like AstriDevCon and AstriCon 2019 were a century ago. It’s hard to imagine that in fact they were only a month and a half ago! Since everyone has had some time to recharge I thought now was a great time to review and talk about what was
Greetings Everyone! Time flies when you are having fun and improving Asterisk; this past year has been no different. October and Astricon [1] are fast approaching; and, thus, the first release candidate of Asterisk is here [2]. The first step in creating the 17.0.0 release of Asterisk is tagging a release candidate: asterisk-17.0.0-rc1. This tag
Overview For those of you who have been around for a while now and contribute to the code base, you probably know about CHANGES and UPGRADE.txt and how annoying it can be when multiple people have made modifications to these files at the same time. For those of you who don’t know what I’m talking
In Asterisk we have an API called device state. As the name implies this allows a device (such as a PJSIP endpoint) to provide notification to the system of its state. Its state may be that it is ringing, that it is on the phone, or that it is unavailable. This provides data to other
Hello Everybody! Can you believe how quickly a year has passed? Time is drawing near to many exciting things – Astricon in October and with that, preparations for the first release of Asterisk 16. The first step in creating a 16.0.0 release of Asterisk is the cutting of the first pre-release version, Asterisk-16.0.0-rc1, from the
With the changing weather, some of us are thinking about summer with excitement, others about winter with trepidation. Regardless of which hemisphere you live in though, it’s time to start thinking about Asterisk 16!
One of the most annoying tasks within Asterisk (or VoIP in general) is the task of CDR and event processing. Why is processing these so annoying? Well, depending on your infrastructure, problems can arise because of any of the below: Row locking within the database Handling of multiple input points Handling a constantly changing data
