[asterisk-bugs] [JIRA] (ASTERISK-26468) ari: Bridge events stop working after this sequence of ARI calls
Joshua Colp (JIRA)
noreply at issues.asterisk.org
Thu Nov 3 16:14:09 CDT 2016
[ https://issues.asterisk.org/jira/browse/ASTERISK-26468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joshua Colp updated ASTERISK-26468:
-----------------------------------
Attachment: ASTERISK-26468.diff
This is a patch which should resolve this problem. Can you apply it and see if it resolves it for your cases?
> 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
> Assignee: Joshua Colp
> Labels: ARI, stasis
> Attachments: ASTERISK-26468.diff, debug_log_26468.txt
>
>
> 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/b1ecceb5-0432-40e6-b8c4-04dda2246cd5/addChannel?channel=atom_asterisk-1476777778.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/b1ecceb5-0432-40e6-b8c4-04dda2246cd5/addChannel?channel=atom_asterisk-1476777808.1"
> curl -v -u asterisk:asterisk -X DELETE "http://localhost:8088/ari/channels/atom_asterisk-1476777778.0"
> curl -v -u asterisk:asterisk -X DELETE "http://localhost:8088/ari/channels/atom_asterisk-1476777808.1"
> curl -v -u asterisk:asterisk -X DELETE "http://localhost:8088/ari/bridges/b1ecceb5-0432-40e6-b8c4-04dda2246cd5"
> curl -v -u asterisk:asterisk -X POST "http://localhost:8088/ari/bridges"
> {code}
> h4. Expected Behaviour
> After the last POST (creating a new bridge), I should receive a "BridgeCreated" event on the websocket (according to https://wiki.asterisk.org/wiki/display/AST/Asterisk+14+REST+Data+Models#Asterisk14RESTDataModels-BridgeCreated)
> h4. Behaviour actually encountered
> 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.
> (logs attached)
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list