[asterisk-bugs] [JIRA] (ASTERISK-21880) Bridge API Enhancements - add CHANNEL(after-bridge-goto) feature
Matt Jordan (JIRA)
noreply at issues.asterisk.org
Fri Jun 7 07:27:04 CDT 2013
Matt Jordan created ASTERISK-21880:
--------------------------------------
Summary: Bridge API Enhancements - add CHANNEL(after-bridge-goto) feature
Key: ASTERISK-21880
URL: https://issues.asterisk.org/jira/browse/ASTERISK-21880
Project: Asterisk
Issue Type: Improvement
Security Level: None
Components: Core/Bridging
Reporter: Matt Jordan
Target Release: 12
When channels are released from a bridge, there are three options available to them:
* Be hung up (which is the default)
* Go to a particular dialplan location. This is typically set by the Bridge/Dial applications.
* Execute a C callback function (internal implementation detail)
Of the second, it would be highly desirable to have the after-bridge location be set through the CHANNEL function. Channels have the ability to bridged in a variety of ways, and allowing a function to set the property removes the need for adding specific application fields to a large class of applications.
The syntax should be:
{{CHANNEL(after-bridge-goto)=[context,[exten]],priority}}
Where {{context,exten,priority}} follows the parseable goto format (allowing for specification of only priority, etc.)
*NOTE*
This addresses the following *BUGBUG* comment in trunk:
{{./funcs/func_channel.c: * BUGBUG add CHANNEL(after_bridge_goto)=<parseable-goto> Sets an after bridge goto datastore property on the channel.}}
--
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