[asterisk-bugs] [JIRA] (ASTERISK-25181) ARI: Channels added to Stasis application during WebSocket creation don't receive a StasisStart event

[Ashley Sanders (JIRA)]

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

Work on ASTERISK-25181 started by Ashley Sanders.

> ARI: Channels added to Stasis application during WebSocket creation don't receive a StasisStart event
> -----------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-25181
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-25181
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_ari, Resources/res_stasis
>    Affects Versions: 13.4.0
>            Reporter: Matt Jordan
>            Assignee: Ashley Sanders
>         Attachments: asterisk_full.txt, asterisk_messages.txt, testsuite_messages.txt
>
>
> While fixing ASTERISK-24988 did fix the race condition where a channel is bounced out of the Stasis application due to the WebSocket being connected but the application not being registered, it has introduced another problem where a StasisStart event is not emitted for a channel.
> Consider the following scenario:
> # A WebSocket connection is started. Before the upgrade response is sent back, we register the Stasis application with {{res_stasis}}, such that any channel that joins after the upgrade notice is accepted.
> # A channel hits the dialplan application and is put into Stasis, as the application is registered
> # *HOWEVER* - because the WebSocket TCP connection isn't made, the StasisStart event cannot be sent. This causes the channel to enter Stasis with no notification to the (eventually) connected application.
> Logs showing this are attached. Note that this was also caught by the same TalkDetect test in the TestSuite.



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