[asterisk-bugs] [JIRA] (ASTERISK-29437) ARI / channel events: events emitted after ChannelDestroyed

[Jean Aunis - Prescom (JIRA)]

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

Jean Aunis - Prescom commented on ASTERISK-29437:
-------------------------------------------------

I didn't capture the Websocket handshake, so the traffic may not be properly displayed by wireshark, but events are visible in the payload of TCP packets (port 8088).

The inbound channel is placed in the Stasis application "bridge-dial" by the dialplan.
Another application called "noOp" subscribes to the channel.
So there are 2 applications subscribed to the channel: "noOp" and "bridge-dial".

In the logs the offending channel has the id 1621492709.539.
Not much is done on it: the "noOp" application is subscribed and a few variables are retrieved.

Unfortunately the issue is difficult to reproduce. I will provide ARI debugging if I can.

> ARI / channel events: events emitted after ChannelDestroyed
> -----------------------------------------------------------
>
>                 Key: ASTERISK-29437
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-29437
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_ari_channels
>    Affects Versions: 16.16.0
>            Reporter: Jean Aunis - Prescom
>            Assignee: Jean Aunis - Prescom
>            Severity: Major
>         Attachments: events_outoforder.pcap, full.txt
>
>
> It happens randomly that ChannelHangupRequest and StasisEnd events are emitted by Asterisk after the ChannelDestroyed event.
> As far as I understand, ChannelDestroyed should always be the last event emitted for a given channel, so ChannelHangupRequest and StasisEnd should be always emitted before.
> I'm attaching the full log and a wireshark capture of the ARI Websocket highlighting the issue:
> - a SIP call is received and cancelled after 2 seconds
> - when the CANCEL request is received, ARI events are emitted in this order :
> 1- ChannelDestroyed (packets 84 and 87)
> 2- ChannelHangupRequest (packet 91)
> 3- StasisEnd (packet 93)



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