Hey Everybody! For those of you that don’t know me, my name is Matthew Fredrickson and I’m the Asterisk Open Source Project Lead. Does that mean I’m the best software developer or most prolific committer to the project? No. Does it mean I can answer every single question about using Asterisk? Not necessarily. Oftentimes it
Inside the Asterisk
Category: Asterisk 14
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
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.
Slight interlude from your regularly scheduled programming. For any interested, Matthew Fredrickson, manager of the Asterisk project, will be giving a webinar today about Asterisk 14 and what’s new with Asterisk since the 13 release. You can get info about it at: https://bit.ly/2gDkXyn It will be live today at 8AM, 2PM, and 9PM CDT. Hope to
For those of you who were unable to attend, AstriDevCon this year at Phoenix continued to impress. There were 39 people signed up, and at least 43 (and probably more – walkins are common) who actually attended. In terms of structure, AstriDevCon is mostly free form, with the number one item of the day being
Asterisk 14 now has the ability to publish extension state using PJSIP PUBLISH requests to another entity acting as an event state compositor. For larger installations, the advantage of this ability is to offload from Asterisk the SUBSCRIBE and NOTIFY responsibility for state changes to the other entity. What can be used as an event
In the past eight weeks since the first beta release of Asterisk 14.0.0, and as we drive towards a general release, community members have collaborated to address more than a dozen important changes in Asterisk. Today, with the release of Asterisk 14.0.0-rc1 (release candidate 1) we now find ourselves on the precipice. The final release
Several improvements to ARI’s media manipulation are coming in Asterisk 14. In this post, we’ll explore media playlists, how they are used, and the problem they solve. A Simple Application It’s fairly common in Asterisk to construct complex sound prompts from multiple simpler sound files. Say, for example, we wanted to emulate the simple IVR
Asterisk’s REST Interface (ARI) in both Asterisk 12 and 13 has the ability to originate (create) outgoing channels. The functionality in ARI mirrors that of the “originate” CLI command, AMI action and dialplan applications. In its use, it creates, in one operation, a channel that is setup, dialed, and directed to a location upon answer.
Asterisk 14: Coming with improved PJSIP DNS Support spoke about the new core DNS API, and mentioned several of the enhancements implemented. In this post we will focus more on the pluggable module that wraps the unbound DNS resolver library mentioned. Specifically with regards to how it can be used. res_resolver_unbound Besides the default system