[asterisk-bugs] [JIRA] (ASTERISK-23051) ARI: channel variables in JSON breaks passing parameters in JSON

[Kinsey Moore (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-23051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=213978#comment-213978 ] 

Kinsey Moore commented on ASTERISK-23051:
-----------------------------------------

To clarify, the patch on reviewboard allows the format suggested by the issue creator without code duplication and without breaking the ARI API.
                
> ARI: channel variables in JSON breaks passing parameters in JSON
> ----------------------------------------------------------------
>
>                 Key: ASTERISK-23051
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-23051
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_ari
>    Affects Versions: 12.0.0
>            Reporter: Matt Jordan
>            Assignee: Kinsey Moore
>            Severity: Critical
>
> So, since the variables thing was added to the ARI call origination, it now acts differently from all the other calls.
> The other POST calls can all take their parameters as either url params or from an application/json body document.
> Unfortunately, the post body of the originate (POST /ari/channels) behaves differently; fields passed in the JSON object are treated as variable names, not as parameters.  For this one call, you must pass parameters in the URL.
> Ideally, this would have been just:
> {noformat}
>      { "endpoint": "SIP/200", ..... "variables":  { "name1": "value1", "name2": "value2"} }
> {noformat}

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