[asterisk-bugs] [JIRA] (ASTERISK-23295) ARI: ChannelEnteredBridge event not delivered to client during bridge move operation

[Kinsey Moore (JIRA)]

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

Kinsey Moore commented on ASTERISK-23295:
-----------------------------------------

I now understand why this happens and I may have a fix.

The issue occurs because when a channel is added to a bridge, the subscription addition process occurs after queueing the channel to be added to the bridge. Under the right circumstances, the channel can get added before the main stasis app loop can process the change in bridges and the addition of the new subscription.

The solution I'm working on involves adding an additional subscription to the bridge before the channel is queued. Unfortunately, this could become an issue if a channel leaves stasis without leaving a stasis bridge since it doesn't appear that a channel is departed from its stasis bridge upon exit from Stasis() (I haven't tested this yet).

> ARI: ChannelEnteredBridge event not delivered to client during bridge move operation
> ------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-23295
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-23295
>             Project: Asterisk
>          Issue Type: Bug
>          Components: Resources/res_ari, Tests/testsuite
>    Affects Versions: 12.0.0
>            Reporter: Matt Jordan
>            Assignee: Kinsey Moore
>         Attachments: ASTERISK-23295-testsuite-log.txt, full.txt.2
>
>
> Note that this was caught by the bridges/move test in the Asterisk Test Suite.
> This test creates two bridges. It takes a channel in ARI, adds it to one bridge, then POSTs an addChannel to the second bridge. The expected result is that the channel leaves the first bridge and enters the second.
> In the attached log, we can see that the core did, in fact, do this, but that the second ChannelEnteredBridge event is never delivered to ARI. The Asterisk log shows the AMI events going out for this transaction, but the attached testsuite log shows that the ARI client never received the event.



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