Summary:	ASTERISK-21875: Bridge API Enhancements - add CHANNEL(after-bridge-goto) feature
Reporter:	Matt Jordan (mjordan)	Labels:	Asterisk12
Date Opened:	2013-06-06 13:15:10	Date Closed:	2013-06-26 16:05:01
Priority:	Major	Regression?	No
Status:	Closed/Complete	Components:	Core/Bridging
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:
Description:	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.}}
Comments: