[asterisk-bugs] [JIRA] (ASTERISK-21336) Bridge API Enhancements - add externally initiated attended transfers

[Digium Subversion (JIRA)]

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

Digium Subversion closed ASTERISK-21336.
----------------------------------------

    Resolution: Fixed
    
> Bridge API Enhancements - add externally initiated attended transfers
> ---------------------------------------------------------------------
>
>                 Key: ASTERISK-21336
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-21336
>             Project: Asterisk
>          Issue Type: New Feature
>          Components: Core/Bridging, Core/Channels
>            Reporter: Matt Jordan
>            Assignee: Mark Michelson
>              Labels: Asterisk12
>      Target Release: 12
>
>
> 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_attended}}. This would let a higher level application or channel driver request that a channel initiate an attended transfer.
> Attended transfers are obviously more complicated then blind transfers. A few things need to be thought through:
> * Unlike a DTMF initiated transfer inside a bridge, an externally initiated attended transfer will typically consist of 4 channels in 2 already established bridges. Thus, the {{ast_bridge_transfer_attended}} is most likely less about initiating a transfer then it is about taking those four channels and merging their bridges appropriately to complete the attended transfer.
> * Optionally, an attended transfer operation may want to also simply merge 3 of the 4 channels into a single bridge, creating a multi-party bridge.
> * An attended transfer will need to potentially update roles on the various channels (who is the caller/peer needs to be set appropriately)

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