[asterisk-bugs] [JIRA] (ASTERISK-21057) Bridge API Enhancements - add API extension points

[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:
-----------------------------------

    Target Release Version/s: 12
    
> Bridge API Enhancements - add API extension points
> --------------------------------------------------
>
>                 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
>
>
> 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.
> ** As part of this, add bridge id support.  This can leverage the UUID library, or it can use the channel scheme of using the hostname + a monotonically increasing sequence number.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira