Summary:ASTERISK-21057: Bridge API Enhancements - add Stasis-Core events
Reporter:Matt Jordan (mjordan)Labels:Asterisk12
Date Opened:2013-02-08 15:58:04.000-0600Date Closed:2013-05-25 13:24:47
Versions:Frequency of
Description:Please see the [Bridge Construction|http://svn.asterisk.org/svn/asterisk/team/group/bridge_construction/] Team project for the current status of this work.

Bridging technologies and the applications that use the bridging API will sometimes needs to be notified when the state of the bridge or a channel in the bridge changes. These events have to be propagated over Stasis-Core, which will have to produce bridge event notifications for AMI/Stasis-HTTP (and other Stasis-Core consumers).

* Add create/enter/leave/destroy/update bridge stasis messages. Note that this cannot be completed until ASTERISK-21331 adds unique identifiers.
** Bridge Stasis messages should be caching and should have a first class object representing their state. This implies an ast_bridge_snapshot is needed, similar to ast_channel_snapshot
* Refactor AMI to subscribe to a bridge topic. Add callbacks for the events in a new {{manager_bridges}} and raise the appropriate AMI events per the specification.
* Add AMI actions to query for all bridges in the system and for specific information on a single bridge.
Comments:By: Kinsey Moore (kmoore) 2013-04-04 11:38:23.754-0500

Current work can be found here: https://origsvn.digium.com/svn/asterisk/team/kmoore/stasis-bridge_events

The groundwork is laid and state updates are sent for creation, destruction, bridge option changes, video source changes, video source removal, channel addition, and channel removal.

By: Kinsey Moore (kmoore) 2013-04-04 12:57:35.175-0500

Bridge merge events have been added which currently go only to the all-bridge-events topic (ast_bridge_topic_all()).

By: Kinsey Moore (kmoore) 2013-04-05 07:47:41.613-0500

The code and documentation for the AMI events has been committed in manager_bridging.c.

By: Kinsey Moore (kmoore) 2013-04-10 14:33:48.798-0500

AMI actions are now committed and the review is available here: https://reviewboard.asterisk.org/r/2438/

By: Kinsey Moore (kmoore) 2013-05-25 13:24:47.586-0500

This issue has been closed in favor of continuing the work in ASTERISK-21711.