Summary: | ASTERISK-21335: Bridge API Enhancements - add externally initiated blind transfers | ||||||||||||||||||
Reporter: | Matt Jordan (mjordan) | Labels: | Asterisk12 | ||||||||||||||||
Date Opened: | 2013-03-29 09:11:38 | Date Closed: | 2013-05-10 09:54:52 | ||||||||||||||||
Priority: | Major | Regression? | |||||||||||||||||
Status: | Closed/Complete | Components: | Core/Bridging Core/Channels | ||||||||||||||||
Versions: | Frequency of Occurrence | ||||||||||||||||||
Related Issues: |
| ||||||||||||||||||
Environment: | Attachments: | ||||||||||||||||||
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.
Once we have the ability to gain control of a channel (see ASTERISK-21334), we should be able to implement {{ast_bridge_transfer_blind}}. This would let a higher level application or channel driver request that a channel be blind transferred out of a bridge to another extension. As the first application/AMI action to be refactored to use this, {{ChannelRedirect}} and the {{Redirect}} AMI action should be refactored to be able to either yank a channel out of an application and transfer them to an extension, or call {{ast_bridge_transfer_blind}} and blind transfer a channel to a new extension. | ||||||||||||||||||
Comments: |