[asterisk-bugs] [JIRA] (ASTERISK-21555) Bridge API Enhancements - implement channel variables in the bridging core
Matt Jordan (JIRA)
noreply at issues.asterisk.org
Mon Oct 21 12:46:14 CDT 2013
[ https://issues.asterisk.org/jira/browse/ASTERISK-21555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matt Jordan updated ASTERISK-21555:
-----------------------------------
Target Release Version/s: 1.8.24.0
> Bridge API Enhancements - implement channel variables in the bridging core
> --------------------------------------------------------------------------
>
> Key: ASTERISK-21555
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-21555
> Project: Asterisk
> Issue Type: New Feature
> Components: Core/Bridging
> Reporter: Matt Jordan
> Assignee: Richard Mudgett
> Labels: Asterisk12
> Target Release: 1.8.24.0
>
>
> The following channel variables need to be set in the bridging core:
> * BRIDGEPEER - set in two party and native bridge mixing technologies when channels join.
> ** Optionally, this can also be set in softmix, but the BRIDGEPEER variable will have to a comma separated list of channel names.
> * BRIDGEPVTCALLID - same as BRIDGEPEER
> * BLINDTRANSFER - set when channels are put into a parking bridge. Preferably, set any time a blind transfer occurs.
> * GOTO_ON_BLINDXFR - this can be set to the location a channel should go to after it blind transfers a channel. This needs to be checked by the various blind transfer functions.
> * TRANSFER_CONTEXT - this needs to be used by the blind/attended transfer functions if set
> * DYNAMIC_FEATURENAME - set by dynamic features
--
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
More information about the asterisk-bugs
mailing list