If we aren't interested in events, don't generate the FullyBooted event on AMI login.

(closes issue #19089)
Reported by: bklang
Patches:
      issue19089-1.8-r316204.patch uploaded by seanbright (license 71)
Tested by: seanbright

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

diff --git a/main/manager.c b/main/manager.c
index 52b991c787483f8d0dfd0a1ecf78bbdd9792bd51..a8447ef753a0c19b9f8afec3dac0a24a68528a9e 100644 (file)
--- a/main/manager.c
+++ b/main/manager.c
@@ -2946,7 +2946,8 @@ static int action_login(struct mansession *s, const struct message *m)
                ast_verb(2, "%sManager '%s' logged on from %s\n", (s->session->managerid ? "HTTP " : ""), s->session->username, ast_inet_ntoa(s->session->sin.sin_addr));
        }
        astman_send_ack(s, m, "Authentication accepted");
-       if (ast_test_flag(&ast_options, AST_OPT_FLAG_FULLY_BOOTED)) {
+       if ((s->session->send_events & EVENT_FLAG_SYSTEM)
+               && ast_test_flag(&ast_options, AST_OPT_FLAG_FULLY_BOOTED)) {
                struct ast_str *auth = ast_str_alloca(80);
                const char *cat_str = authority_to_str(EVENT_FLAG_SYSTEM, &auth);
                astman_append(s, "Event: FullyBooted\r\n"