[asterisk-bugs] [JIRA] (ASTERISK-21640) Bridge API Enhancements - work through a channel being removed from a bridge by an external party

[Digium Subversion (JIRA)]

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

Digium Subversion closed ASTERISK-21640.
----------------------------------------

    Resolution: Fixed
    
> Bridge API Enhancements - work through a channel being removed from a bridge by an external party
> -------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-21640
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-21640
>             Project: Asterisk
>          Issue Type: New Feature
>          Components: Core/Bridging, Core/ManagerInterface, Core/Stasis
>            Reporter: Matt Jordan
>            Assignee: Richard Mudgett
>              Labels: Asterisk12
>
> There are times when a channel has to be owned by a third party and that third party does not want to put that channel back into another bridge or transfer it to a dialplan location. Examples include:
> * The mythical usage of the infinite wait bridge in {{app_queue}}
> * Stasis-HTTP need to be able to remove a channel from a bridge and own the channel
> There are a few other problems here:
> * If an external entity owns a channel, how do we prevent another third party from stealing it?
> * What does it mean for an external entity to own a channel? Something has to continue to service the channel. Is that autoservice, or a 'quiet' infinite wait 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