[asterisk-users] [asterisk-app-dev] ARI application execution feature survey

Matthew Jordan mjordan at digium.com
Tue Apr 2 18:25:50 CDT 2019

On Tue, Apr 2, 2019 at 4:18 PM Joshua C. Colp <jcolp at digium.com> wrote:

> On Tue, Apr 2, 2019, at 8:15 PM, BJ Weschke wrote:
> > I get the desired use case to run app_amd from within a Stasis
> > application, but I’m not sure about app_queue. You have everything at
> > your disposal within ARI itself to replicate all of the functionality
> > of app_queue and beyond.
> Yes, there are certain applications which are logically building blocks to
> bigger applications. AMD is one of those which would be best if it were its
> own functionality within ARI, but allowing execution of the application is
> a good enough option. I don't think applications such as Queue, Dial,
> ConfBridge, Playback, Record or some others really make sense.
Assuming the TALK_DETECTION function isn't sufficient, it's worth noting
that the information that AMD uses to make its decisions are available to
the parts of Asterisk that make up ARI. I wonder if it would be better to
simply wrap up the existing talk detection events under some other HTTP
resource  rather than open up this entire concept.

While I'm pretty far removed from the guts of Asterisk these days, the
notion of having dialplan applications be executed from within ARI just
fills me with some fear. You can certainly open up some nightmare scenarios
where people invoke Stasis from within Stasis recursively, or invoke GoTo
or other dialplan context affecting applications.

For that matter, many of the monolithic dialplan applications have specific
options that place channels into dialplan contexts that execute after their
execution. I'm not even sure I can begin to wrap my head around what that
will do to a channel in ARI.

*Matthew Jordan*
Digium - A Sangoma Company | Senior Vice President, Software and Services |
445 Jan Davis Drive NW - Huntsville, AL 35806 - US
direct: +1 256 428 6107
Check us out at: https://digium.com · https://sangoma.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20190402/a01e7b58/attachment.html>
-------------- next part --------------
asterisk-app-dev mailing list
asterisk-app-dev at lists.digium.com

More information about the asterisk-users mailing list