res/ari/resource_channels: Add missing 'no_answer' reason to DELETE /channels

One of the canonical reasons for hanging up a channel is because the far end
failed to answer - or because someone else answered, and we want to get rid of
this channel. This patch adds the missing value to the 'reason' query parameter
for the DELETE /channels operation.

Review: https://reviewboard.asterisk.org/r/4400

ASTERISK-24745 #close
Reported by: Ben Merrills
patches:
  add_no_answer_ari_hangup_cause.diff uploaded by Ben Merrills (License 6678)

git-svn-id: https://origsvn.digium.com/svn/asterisk/branches/13@431622 65c4cc65-6c06-0410-ace0-fbb531ad65f3

diff --git a/res/ari/resource_channels.c b/res/ari/resource_channels.c
index d1d54a2f042f9ffc6648a4746d380fea33654ba8..24aabe588a6f9f5e735daa64ef5869e38ed6bd22 100644 (file)
--- a/res/ari/resource_channels.c
+++ b/res/ari/resource_channels.c
@@ -704,6 +704,8 @@ void ast_ari_channels_hangup(struct ast_variable *headers,
                cause = AST_CAUSE_BUSY;
        } else if (!strcmp(args->reason, "congestion")) {
                cause = AST_CAUSE_CONGESTION;
+       } else if (!strcmp(args->reason, "no_answer")) {
+               cause = AST_CAUSE_NOANSWER;
        } else {
                ast_ari_response_error(
                        response, 400, "Invalid Reason",

diff --git a/rest-api/api-docs/channels.json b/rest-api/api-docs/channels.json
index 887191373206188ce494c62b288b21ab1ffdbef0..6baebe3544b885ab8e7130f7d5d889955d6363f7 100644 (file)
--- a/rest-api/api-docs/channels.json
+++ b/rest-api/api-docs/channels.json
@@ -313,7 +313,8 @@
                                                                "values": [
                                                                        "normal",
                                                                        "busy",
-                                                                       "congestion"
+                                                                       "congestion",
+                                                                       "no_answer"
                                                                ]
                                                        }
                                                }