In a blog post long ago we talked about the addition of the create and dial ARI functionality for allowing channels to exist within ARI applications before they have been answered. This has seen use by various people and it came to light that it presented a slight difference in API definition in comparison to
In a blog post long ago we talked about the addition of the create and dial ARI functionality for allowing channels to exist within ARI applications before they have been answered. This has seen use by various people and it came to light that it presented a slight difference in API definition in comparison to
Review If you’ve been following this blog post series, then you should have a channel driver that’s ready to be integrated with ARI. If not, then check out Part 1 and Part 2 first. The purpose of this final chapter in the series will be to get your channel driver working with ARI, which is
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
The Asterisk Rest Interface (ARI) over the last year received several enhancements that have been requested by the community: server side event filtering automatic context creation moving a channel between apps Although these topics have been discussed previously, with Astricon, and the release of Asterisk 17.0.0 just around the corner I think it’s a good
Overview One of the topics of discussion every year at Astricon is not needing to use the dialplan in order to use Stasis. This involves a couple of different things in order to bypass dialplan completely. First of all, the only way to enter Stasis is to have a line of dialplan that places the
Since the arrival of the Asterisk REST Interface (ARI) requests have been made to allow for event type filtering capabilities. Consumers have wanted a way to make it so Asterisk only sends a specified subset of events to the connected application. Guess what, the wait is finally over! Starting with Asterisk 13.26.0, and Asterisk 16.3.0
The stasis message bus is something that is used every day as of Asterisk 13 when you are using Asterisk. It provides the foundation of such things as CDR, CEL, ARI, AMI, and some operations in applications. It allows a message to be published and then handled by a subscriber. These messages are automatically created
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
