ARI: Add ability to raise arbitrary User Events

User events can now be generated from ARI.  Events can be signalled with
arbitrary json variables, and include one or more of channel, bridge, or
endpoint snapshots.  An application must be specified which will receive
the event message (other applications can subscribe to it).  The message
will also be delivered via AMI provided a channel is attached.  Dialplan
generated user event messages are still transmitted via the channel, and
will only be received by a stasis application they are attached to or if
the channel is subscribed to.

This change also introduces the multi object blob mechanism used to send
multiple snapshot types in a single message.  The dialplan app UserEvent
was also changed to use multi object blob, and a new stasis message type
created to handle them.

ASTERISK-22697 #close
Review: https://reviewboard.asterisk.org/r/3494/
........

Merged revisions 414405 from http://svn.asterisk.org/svn/asterisk/branches/12


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

1 files changed, 56 insertions, 0 deletions

diff --git a/res/ari/resource_events.c b/res/ari/resource_events.c
index 098049fc6..d159741c2 100644
--- a/res/ari/resource_events.c
+++ b/res/ari/resource_events.c
@@ -217,3 +217,59 @@ void ast_ari_websocket_events_event_websocket(struct ast_ari_websocket_session *
 		ast_json_unref(msg);
 	}
 }
+
+void ast_ari_events_user_event(struct ast_variable *headers,
+	struct ast_ari_events_user_event_args *args,
+	struct ast_ari_response *response)
+{
+	enum stasis_app_user_event_res res;
+	struct ast_json *json_variables = NULL;
+
+	if (args->variables) {
+		ast_ari_events_user_event_parse_body(args->variables, args);
+		json_variables = ast_json_object_get(args->variables, "variables");
+	}
+
+	if (ast_strlen_zero(args->application)) {
+		ast_ari_response_error(response, 400, "Bad Request",
+			"Missing parameter application");
+		return;
+	}
+
+	res = stasis_app_user_event(args->application,
+		args->event_name,
+		args->source, args->source_count,
+		json_variables);
+
+	switch (res) {
+	case STASIS_APP_USER_OK:
+		ast_ari_response_no_content(response);
+		break;
+
+	case STASIS_APP_USER_APP_NOT_FOUND:
+		ast_ari_response_error(response, 404, "Not Found",
+			"Application not found");
+		break;
+
+	case STASIS_APP_USER_EVENT_SOURCE_NOT_FOUND:
+		ast_ari_response_error(response, 422, "Unprocessable Entity",
+			"Event source was not found");
+		break;
+
+	case STASIS_APP_USER_EVENT_SOURCE_BAD_SCHEME:
+		ast_ari_response_error(response, 400, "Bad Request",
+			"Invalid event source URI scheme");
+		break;
+
+	case STASIS_APP_USER_USEREVENT_INVALID:
+		ast_ari_response_error(response, 400, "Bad Request",
+			"Invalid userevnet data");
+		break;
+
+	case STASIS_APP_USER_INTERNAL_ERROR:
+	default:
+		ast_ari_response_error(response, 500, "Internal Server Error",
+			"Error processing request");
+	}
+}
+