Summary:	ASTERISK-22872: ARI: Allow specifying channel variables during a POST /channels
Reporter:	Matt Jordan (mjordan)	Labels:
Date Opened:	2013-11-20 15:51:18.000-0600	Date Closed:	2013-12-13 11:19:33.000-0600
Priority:	Major	Regression?
Status:	Closed/Complete	Components:	Resources/res_ari
Versions:		Frequency of Occurrence
Related Issues:	causes ASTERISK-23051 ARI: channel variables in JSON breaks passing parameters in JSON
Environment:		Attachments:
Description:	When originating a channel using {{POST /channels}}, by the time you get the channel into your ARI application, it may be too late to set needed variables/properties. This can especially be true for things like caller ID/CDR information. When creating the channel, we should be able to set variables on that channel. This can be done as a query parameter to the REST call, and should allow for multiple variables to be specified: {noformat} POST /channels?endpoint=foo&variables={"variable1": "foo", "variable2": "bar"} {noformat} Or {noformat} POST /channels?endpoint=foo&variables={"CALLERID(name)": "foo", "CDR(accountcode)": "local1"} {noformat} Note that the variables will be specified in JSON. We'll need to validate that values to ensure that we aren't passed structured data.
Comments: