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

[Matt Jordan (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-21057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matt Jordan updated ASTERISK-21057:
-----------------------------------

    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.

  was:
As part of the [API work|https://wiki.asterisk.org/wiki/display/AST/Asterisk+12+API+Improvements], the model for bridging used within Asterisk is undergoing some major rework. In particular, all bridging in Asterisk will use the existing Bridging API, added by Joshua Colp since 1.6.

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. This task is to add extension point (observers/callbacks) for particular events in the bridge.

One obvious consumer of these points is Stasis-Core, which will have to produce bridge event notifications for AMI/Stasis-HTTP (and other Stasis-Core consumers)

* Add bridge and bridge channel hooks for enter/leave/answer/merge/tech-change/empty events.  Note that an answer hook will not be usable until the early bridge is implemented (assuming early state of channels is handled by the bridging API)

* Add create/enter/leave/destroy bridge stasis events. Note that this cannot be completed until ASTERISK-21331 adds unique identifiers.

        Summary: Bridge API Enhancements - add Stasis-Core events  (was: Bridge API Enhancements - add API extension points and Stasis-Core events)
    
> 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
>              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