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
Inside the Asterisk
Kia Ora! (Or Be Healthy) (Don’t ask – I like greetings from various languages) If you haven’t noticed from the various emails and posts Asterisk 18.0.0 has now been released and is available for download here! As previously mentioned in our blog post for 18.0.0-rc1 this is an LTS release, meaning it will be supported
Video has been a continued theme of Asterisk for some years now. We put into place the foundation to allow us to do video better, and have over time taken advantage of this and advanced things further. I thought I would take a little bit of time to reflect back on what has been done.
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, so much so that the first release candidate of Asterisk 18 is here. The first step in creating the 18.0.0 release of Asterisk is tagging a
When stream support was initially added to Asterisk we did it in the most backwards compatible way possible to ensure that we did not have to modify the entirety of Asterisk. This has allowed us to gradually improve parts of Asterisk as we’ve expanded our stream and video support. To that end the next part
Prompted by a post on the Asterisk users mailing list I thought I’d write a bit about Asterisk versioning and releases for this blog post. The Asterisk project at any given time has between 2 and 3 major versions of Asterisk being released. When I say major version I’m referring to an entirely different branch
When PJSIP support was written for Asterisk we naturally needed the ability to display the SIP messages being sent and received. This took the form of the res_pjsip_logger module which hooks into the message sending and receiving path and logs the messages. The functionality was written to be familiar to users of chan_sip by allowing
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
At recent AstriDevCon meetings, we discussed the possibility of allowing an ARI application to capture or inject media into calls it controlled. With the release of Asterisk 16.6, that capability is now available. More information is available on the Asterisk Wiki External Media and ARI web page but let’s go over a simple scenario. Let’s say
If you download Asterisk 17 and start it up, you might be one of the people that notices the following messages: If you are using chan_pjsip, which has been available in Asterisk since version 12 was released in 2013, you’ll never see this message. But, if you do see this message, do not be afraid!