sysmocom
/
asterisk
11
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
asterisk/res/stasis
History
David M. Lee f6a227a451 Continue events when ARI WebSocket reconnects 
This patch addresses a bug in the /ari/events WebSocket in handling
reconnects.

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
connection.

To avoid memory leaks from lingering, unused application, the
application list is cleaned up whenever new applications are
registered/unregistered.

(closes issue ASTERISK-21970)
Review: https://reviewboard.asterisk.org/r/2678/


git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@395120 65c4cc65-6c06-0410-ace0-fbb531ad65f3
 		2013-07-23 13:42:46 +00:00
..
app.c Continue events when ARI WebSocket reconnects 2013-07-23 13:42:46 +00:00
app.h Continue events when ARI WebSocket reconnects 2013-07-23 13:42:46 +00:00
command.c Break res_stasis into smaller files. 2013-05-14 21:45:08 +00:00
command.h Break res_stasis into smaller files. 2013-05-14 21:45:08 +00:00
control.c ARI: MOH start and stop for a channel 2013-07-19 19:40:27 +00:00
control.h Break res_stasis into smaller files. 2013-05-14 21:45:08 +00:00