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

[Jean Aunis - Prescom (JIRA)]

Jean Aunis - Prescom created ASTERISK-29437:
-----------------------------------------------

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