From 444d30b434da4e1e1ee9f21afa454f2e0bb26907 Mon Sep 17 00:00:00 2001
From: Stefan Schmidt <sst@sil.at>
Date: Wed, 13 Oct 2010 08:58:41 +0000
Subject: [PATCH] Report what extension called a failed macro
Add the extension and context of the calling channel to the log output if a macro could not be found.
(closes issue #18112)
Reported by: prado
Patches:
app_macro-info.diff uploaded by prado (license 510)
Tested by: schmidts
git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@291361 65c4cc65-6c06-0410-ace0-fbb531ad65f3
---
apps/app_macro.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/apps/app_macro.c b/apps/app_macro.c
index e5ab2bc21a..e533436f15 100644
--- a/apps/app_macro.c
+++ b/apps/app_macro.c
@@ -301,7 +301,7 @@ static int _macro_exec(struct ast_channel *chan, const char *data, int exclusive
if (!ast_exists_extension(chan, fullmacro, "s", 1,
S_COR(chan->caller.id.number.valid, chan->caller.id.number.str, NULL))) {
if (!ast_context_find(fullmacro))
- ast_log(LOG_WARNING, "No such context '%s' for macro '%s'\n", fullmacro, macro);
+ ast_log(LOG_WARNING, "No such context '%s' for macro '%s'. Was called by %s@%s\n", fullmacro, macro, chan->exten, chan->context);
else
ast_log(LOG_WARNING, "Context '%s' for macro '%s' lacks 's' extension, priority 1\n", fullmacro, macro);
return 0;
--
GitLab