[asterisk-bugs] [JIRA] (ASTERISK-21058) Bridge API Enhancements - rework Local channels/Local channel bridging

[Matt Jordan (JIRA)]

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

Matt Jordan updated ASTERISK-21058:
-----------------------------------

    Description: 
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.


As part of the refactoring work, it is inevitable that local channel optimization will break. This task it to make it functional again.

One way this could be implemented is to pull much of chan_local's logic into a bridging module.  There seem to be times where it could be useful to create a local channel structure and impart the channels into different bridges or put one end into a bridge and the other executes an application.  

  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.

As part of the refactoring work, it is inevitable that local channel optimization will break. This task it to make it functional again.

One way this could be implemented is to pull much of chan_local's logic into a bridging module.  There seem to be times where it could be useful to create a local channel structure and impart the channels into different bridges or put one end into a bridge and the other executes an application.  

    
> Bridge API Enhancements - rework Local channels/Local channel bridging
> ----------------------------------------------------------------------
>
>                 Key: ASTERISK-21058
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-21058
>             Project: Asterisk
>          Issue Type: Improvement
>          Components: Channels/chan_local, Core/Bridging
>    Affects Versions: 12
>            Reporter: Matt Jordan
>              Labels: Asterisk12
>
> 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.
> As part of the refactoring work, it is inevitable that local channel optimization will break. This task it to make it functional again.
> One way this could be implemented is to pull much of chan_local's logic into a bridging module.  There seem to be times where it could be useful to create a local channel structure and impart the channels into different bridges or put one end into a bridge and the other executes an application.  

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