Slight interlude from your regularly scheduled programming. For any interested, Matthew Fredrickson, manager of the Asterisk project, will be giving a webinar on Tuesday December 5th 2017 about Asterisk 15 and what’s new with Asterisk since the 14 release. You can get info about it at: https://bit.ly/2AhDSuR It will be live at 9AM, 2PM, and 8PM
Inside the Asterisk
Setting the “max_contacts” configuration option too low can cause loss of registrations. How that can happen and some recommendations are described.
This week, we’re pleased to say that we’ve updated the Asterisk 13, 15 and master branches’ bundled version of pjproject to 2.7.1. This release contains a fix for an important security issue and we urge all users to upgrade accordingly. https://downloads.asterisk.org/pub/security/AST-2017-009.html https://issues.asterisk.org/jira/browse/ASTERISK-27319 Thanks to Youngsung Kim at LINE Corporation for finding and reporting the original issue.
As is well known, there are several ways to extend Asterisk features, but if you want to exploit the full power of its raw primitive objects — channels, bridges, endpoints, media, etc. — you really need to use ARI. On the other hand, if the performances of your application are important, chances are you’re using
Asterisk’s MALLOC_DEBUG is a compile time tool that helps find some common memory usage problems such as memory corruption and memory leaks. The debug tool helps find similar things as valgrind but without the huge performance penalty. You enable MALLOC_DEBUG in menuselect’s “Compiler Flags” menu along with other useful compile time options like DONT_OPTIMIZE. With
[dropshadowbox align=”none” effect=”lifted-both” width=”auto” height=”” background_color=”#ffffff” border_width=”1″ border_color=”#dddddd” ]tl;dr: We fixed the vulnerabilities. If you’d like to read the conclusion of this admittedly long saga, scroll down to the Conclusion at the end.[/dropshadowbox] Overview This month, the Asterisk project performed two security releases to address an unauthorized RTP data disclosure vulnerability in its real-time transport
In a previous post some of the upcoming changes made for Asterisk 15 have been discussed. Specifically, one of the items mentioned is the beginnings of a multi-stream media framework. Starting in 15, groundwork has been laid that greatly enhances media flow in Asterisk. Taking advantage of this new architecture, changes have also been made
In my previous post I talked about what WebRTC support is like in Asterisk 14. Since Asterisk 15 is going to be released soon let’s take a look at how WebRTC support differs in it from Asterisk 14. The “webrtc” PJSIP Configuration Option As the WebRTC specification has evolved and changed the functionality in Asterisk
WebRTC has been in Asterisk since Asterisk 11 and over time has evolved just as the WebRTC specification itself has evolved. The WebRTC implementation we started with is not the one we currently use. It is in thanks to the community that has contributed both issues and fixes that our WebRTC has continued to improve.
It is with great pleasure I wish to inform the world of the first beta release of the new Asterisk 15 branch. It’s a very exciting time to be a user of Asterisk! Asterisk 15 is arguably the biggest release of Asterisk that has happened in the last 10 or so years. There has been