Summary:ASTERISK-21335: Bridge API Enhancements - add externally initiated blind transfers
Reporter:Matt Jordan (mjordan)Labels:Asterisk12
Date Opened:2013-03-29 09:11:38Date Closed:2013-05-10 09:54:52
Status:Closed/CompleteComponents:Core/Bridging Core/Channels
Versions:Frequency of
must be completed before resolvingASTERISK-21518 Bridge API Enhancements - refactor chan_iax2 to perform blind transfers using the new bridging framework
must be completed before resolvingASTERISK-21519 Bridge API Enhancements - implement blind transfers in chan_sip
must be completed before resolvingASTERISK-21523 Bridge API Enhancements - refactor sig_pri_attempt_transfer to use Bridging Framework
must be completed before resolvingASTERISK-21524 Bridge API Enhancements - refactor chan_misdn's misdn_attempt_transfer
must be completed before resolvingASTERISK-21525 Bridge API Enhancements - refactor chan_mgcp attempt_transfer
must be completed before resolvingASTERISK-21526 Bridge API Enhancements - refactor chan_skinny skinny_transfer
must be completed before resolvingASTERISK-21527 Bridge API Enhancements - refactor chan_unistim attempt_transfer
is related toASTERISK-21456 New SIP Channel Driver - add basic REFER support and SIP blind transfers
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.