[asterisk-bugs] [JIRA] (ASTERISK-21057) Bridge API Enhancements - add Stasis-Core events

[Kinsey Moore (JIRA)]

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

Kinsey Moore edited comment on ASTERISK-21057 at 4/4/13 11:40 AM:
------------------------------------------------------------------

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

The groundwork is laid and messages are sent for creation, destruction, bridge option changes, video source changes, video source removal, channel addition, and channel removal.
                
      was (Author: kmoore):
    Current work can be found here: https://origsvn.digium.com/svn/asterisk/team/kmoore/stasis-bridge_events

The groundwork is laid and messages are sent for creation, destruction, bridge option changes, channel addition, and channel removal.
                  
> Bridge API Enhancements - add Stasis-Core events
> ------------------------------------------------
>
>                 Key: ASTERISK-21057
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-21057
>             Project: Asterisk
>          Issue Type: Improvement
>          Components: Core/Bridging
>            Reporter: Matt Jordan
>            Assignee: Kinsey Moore
>              Labels: Asterisk12
>      Target Release: 12
>
>
> 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.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira