On Fri, Oct 21, 2016 at 12:32 PM, Kevin Harwell <kharw...@digium.com> wrote: > On Fri, Oct 21, 2016 at 10:49 AM, Corey Farrell <g...@cfware.com> wrote: >> >> >> I'm in favor per app config. I do not yet use ARI, but when I do I >> will have '#tryinclude /etc/asterisk/ari.d/*.conf' in ari.conf. My >> hope is that each ARI app would install it's own config to >> /etc/asterisk/ari.d, avoid modification of ari.conf / global options. >> Per app config would also be important if dialplan functions can be >> added to StasisEnd. >> > > This is getting down more into implementation details, but instead of > configs what about adding the desired variables to the event subscribe > command? Each app could subscribe (or when they subscribe) to an event and > specify the variable(s) they desire. At least to start this could be limited > to a small list of allowed events and variables.
Sounds fine. I'm not sure what benefit there would be to limiting which variables can be used but that sort of restriction could easily be relaxed/removed later. The obvious exception being to block live_dangerously functions by default. -- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
