Hey there,
The short answer is "yes" to both. The plan is to have this change in 13,
16, and master. Once it is done with the review process and merged into the
branches, the next release we cut will contain these changes. As for the
appname and the dialplan entry that's automatically added, that'
Ah so just to confirm - above in the thread theres a variable in the url
passed in called context so that you could have an app name of foo but a
context of bar and also an ari application without a context called alice
and therefore alice could still be addressable from dialplan. So do we want
the
With the current approach, the context is now reliant on the appname, and
if you are wanting to do "automatic" entry into Stasis with an endpoint,
the only context that will matter is the one automatically created on
application launch. Say your application is "master". When it's launched,
you'll h
Hello,
I hope someone can help me as I've been struggling with this for almost
2 days now and am unable to find anything that works in my web searches.
I am trying to upgrade my test system from Asterisk 11 to Asterisk
16.1.1, along with dahdi-linux-complete-3.0.0+3.0.0 and libpri-1.6.0
(wit
Howdy,
Support for the TDM410, among others, was removed from the DAHDI 3.x driver
packages. Those cards went end of sale on February 1 of 2014, and Digium
(Sangoma) do not test them as a part of any releases. The README (iirc) in
the package should list the cards still supported in the 3.x rele
