[asterisk-bugs] [JIRA] (ASTERISK-26468) ARI bridge events stop working after this sequence of ARI calls

[Asterisk Team (JIRA)]

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

Asterisk Team commented on ASTERISK-26468:
------------------------------------------

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].

> ARI bridge events stop working after this sequence of ARI calls
> ---------------------------------------------------------------
>
>                 Key: ASTERISK-26468
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26468
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Core/Stasis, Resources/res_ari_bridges
>    Affects Versions: 13.10.0, 14.0.2
>         Environment: Debian 8.5
> 3.16.0-4-686-pae
> gcc (Debian 4.9.2-10) 4.9.2
>            Reporter: Daniele Pallastrelli
>
> h4. Frequency
> Systematic issue.
> h4. Symptoms
> Bridge events stop flowing from ARI websocket after a precise sequence of ARI requests occours.
> h4. Steps required to reproduce the issue
> {code}
> wscat -c "ws://localhost:8088/ari/events?api_key=asterisk:asterisk&app=attendant&subscribeAll=true"
> curl -v -u asterisk:asterisk -X POST "http://localhost:8088/ari/applications/attendant/subscription?eventSource=channel:,endpoint:,bridge:,deviceState:"
> curl -v -u asterisk:asterisk -X POST "http://localhost:8088/ari/bridges"
> curl -v -u asterisk:asterisk -X POST "http://localhost:8088/ari/channels?endpoint=SIP/101&app=attendant"
> curl -v -u asterisk:asterisk -X POST "http://localhost:8088/ari/bridges/6c83e708-b59b-4200-8dbe-f6d7ee31d2cf/addChannel?channel=atom_asterisk-1476373625.0"
> curl -v -u asterisk:asterisk -X POST "http://localhost:8088/ari/channels?endpoint=SIP/290&app=attendant"
> curl -v -u asterisk:asterisk -X POST "http://localhost:8088/ari/bridges/6c83e708-b59b-4200-8dbe-f6d7ee31d2cf/addChannel?channel=atom_asterisk-1476373662.1"
> curl -v -u asterisk:asterisk -X DELETE "http://localhost:8088/ari/channels/atom_asterisk-1476373625.0"
> curl -v -u asterisk:asterisk -X DELETE "http://localhost:8088/ari/channels/atom_asterisk-1476373662.1"
> curl -v -u asterisk:asterisk -X DELETE "http://localhost:8088/ari/bridges/6c83e708-b59b-4200-8dbe-f6d7ee31d2cf"
> curl -v -u asterisk:asterisk -X POST "http://localhost:8088/ari/bridges"
> {code}
> h4. Result
> After the last POST (creating a new bridge), I don't receive the event "BridgeCreated" on the websocket and in general I don't receive bridge events anymore.
> The last bridge event I get is the "BridgeDestroyed" corresponding to the last DELETE http request.



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