[asterisk-bugs] [JIRA] (ASTERISK-24501) ARI: Moving a channel between bridges followed by a hangup can cause an ARI client to not receive an expected ChannelLeftBridge event before StasisEnd

[Kinsey Moore (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-24501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=223453#comment-223453 ] 

Kinsey Moore commented on ASTERISK-24501:
-----------------------------------------

Apparently StasisStart messages have a similar problem and delayed removal of certain datastores related to masquerade detection cause StasisEnd messages to get swallowed when Stasis() is called in quick succession.

> ARI: Moving a channel between bridges followed by a hangup can cause an ARI client to not receive an expected ChannelLeftBridge event before StasisEnd
> ------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-24501
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-24501
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_ari
>    Affects Versions: 12.6.1, 13.0.0
>            Reporter: Matt Jordan
>            Assignee: Kinsey Moore
>         Attachments: full.txt
>
>
> Consider the following scenario:
> * Channel 1 enters into Bridge A
> * An {{addChannel}} command is issued to add the channel to Bridge B
> * A bridge move operation begins to happen internally.
> * While the bridge move operation occurs, a {{DELETE /channel/1}} occurs. This queues a hangup on the channel, causing it to be removed from Bridge B.
> * We receive a StasisEnd event, followed by the ChannelLeftBridge event, which is wrong.
> This is shown in the attached log, which was produced from the Asterisk Test Suite {{/bridges/move}} test (which is sporadically failing due to this issue).



--
This message was sent by Atlassian JIRA
(v6.2#6252)