Thoughts below.
On Tue, Oct 11, 2016 at 2:04 PM, Sébastien Duthil
wrote:
> Hi everyone,
>
> Sylvain Boily and I gave a talk during Astridevcon 2016 about our usage
> of ARI in the XiVO project [1]. We'd like to discuss some of the issues
> we encountered, to see if other people have had similar i
Matt Fredrickson wrote:
First off, sorry about the delayed response. Your proposal sounds
reasonable to me - that is to say, I can't see anything wrong with
adding that behavior. Perhaps making channel variable dumping on
StasisEnd optional instead of mandatory would be better, but other
th
On Tue, Oct 18, 2016 at 9:26 AM, Joshua Colp wrote:
> Matt Fredrickson wrote:
>
>
>
>>
>> First off, sorry about the delayed response. Your proposal sounds
>> reasonable to me - that is to say, I can't see anything wrong with
>> adding that behavior. Perhaps making channel variable dumping on
>
Matthew Jordan wrote:
There are a few wrinkles with emitting channel variables with
arbitrary events (of which StasisEnd would qualify).
When an event is emitted out of the APIs, it's typically being done so
as a result of a message having been published on the Stasis message
bus. The message
Hi,
In a new review request ([1]) I call for removing code that supports
dialing a DAHDI channel by name. I suspect this feature was never
actually used. I quote here from the commit message:
Support for referring to DAHDI channels by logical names was added in
(FIXME: when? Asterisk 11? 1.8?) an
