[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

[Matt Jordan (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-24501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matt Jordan updated ASTERISK-24501:
-----------------------------------

    Description: 
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).



  was:
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.
* For some incredibly frightening reason, we don't get the ChannelLeftBridge event.

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).

Note that we *are* subscribed to the bridge, so this is very, very bad.

{noformat}
[Nov  5 19:11:34] DEBUG[9048][C-00000000] stasis/control.c: 1415236293.2, dcf45528-07ba-4dcb-b85f-5b86f4837255: Channel leaving bridge
[Nov  5 19:11:34] DEBUG[9048][C-00000000] stasis/app.c: bridge 'dcf45528-07ba-4dcb-b85f-5b86f4837255': is 1 interested in testsuite
[Nov  5 19:11:34] DEBUG[8969] pbx.c: Function CSV_QUOTE(1415236294.246461) result is '"1415236294.246461"'
[Nov  5 19:11:34] DEBUG[9048][C-00000000] stasis/control.c:   reason: Channel was departed from bridge
{noformat}

(And yet no leave event was seen...)

        Summary: ARI: Moving a channel between bridges followed by a hangup can cause an ARI client to not receive an expected ChannelLeftBridge event before StasisEnd  (was: ARI: Moving a channel between bridges followed by a hangup can cause an ARI client to not receive an expected ChannelLeftBridge event)

> 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
>         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)