| Summary: | ASTERISK-21640: Bridge API Enhancements - work through a channel being removed from a bridge by an external party | ||
| Reporter: | Matt Jordan (mjordan) | Labels: | Asterisk12 |
| Date Opened: | 2013-04-18 16:06:53 | Date Closed: | 2013-05-17 16:52:01 |
| Priority: | Major | Regression? | |
| Status: | Closed/Complete | Components: | Core/Bridging Core/ManagerInterface Core/Stasis |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | 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? | ||
| Comments: | By: Richard Mudgett (rmudgett) 2013-04-29 19:32:45.484-0500 This functionality will also be useful for protocol attended transfers (ASTERISK-21336) to an application so the channel can leave a bridge before being masqueraded to the application channel. | ||