[asterisk-dev] ARI events order

[Jean Aunis]

Le 06/09/2018 à 16:18, Matthew Jordan a écrit :
>
>
> On Wed, Sep 5, 2018 at 5:23 PM Seán C. McCord <ulexus at gmail.com 
> <mailto:ulexus at gmail.com>> wrote:
>
>     As to the events should have a deterministic order or not, I
>     cannot speak, but this is definitely normal behaviour.
>
>
>     On Wed, Sep 5, 2018 at 12:22 PM Jean Aunis <jean.aunis at prescom.fr
>     <mailto:jean.aunis at prescom.fr>> wrote:
>
>         Hello,
>
>         It looks like the ARI events ordering during channel
>         destruction is not deterministic. I noticed this for
>         ChannelLeftBridge and ChannelDestroyed events : given a
>         channel is in a bridge and is hanged up, sometimes
>         ChannelLeftBridge is raised before ChannelDestroyed, sometimes
>         it's the contrary. Test conditions are exactly the same in
>         both cases.
>
>         Is this non-deterministic behaviour normal, or should it be
>         considered as a bug ?
>
>         To my mind, ChannelDestroyed should always be the very last
>         event raised for a given channel. From a developper point of
>         view, it would give a clear indication that the resources
>         associated to the channel can be freed.
>
>         Regards
>
> The events regarding a Channel entering and leaving a Bridge are 
> deterministic with respect to the Bridge's lifetime, but are not 
> deterministic with respect to the Channel's lifetime. While it's a bit 
> different, this is discussed somewhat on the AMI specification page:
> <snip>
Thanks for the answer, I understand the problem. I'll live with it.

Regards

Jean
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-dev/attachments/20180906/847ea032/attachment.html>