Review Board 1.7.16

Continue events when ARI WebSocket reconnects

Review Request #2678 - Created July 16, 2013 and submitted

David Lee
This patch addresses a bug in the /ari/events WebSocket in handling

When a Stasis application's associated WebSocket was disconnected and
reconnected, it would not receive events for any channels or bridges
it was subscribed to.

The fix was to lazily clean up Stasis application registrations,
instead of removing them as soon as the WebSocket goes away.

When an application is unregistered at the WebSocket level, the
underlying application is simply deactivated. If the application
WebSocket is reconnected, the application is reactivated for the new

To avoid memory leaks from lingering, unused application, the
application list is cleaned up whenever new applications are
Several rounds of connecting the WebSocket, putting channels in the
Stasis app, disconnecting/reconnecting the WebSocket.
Review request changed
Updated (July 23, 2013, 9:22 a.m.)
  • changed from pending to submitted
Committed in revision 395133 runs on a server provided by Digium, Inc. and uses bandwidth donated to the open source Asterisk community by API Digital Communications in Huntsville, AL USA.
Please report problems with this site to