From e1a54c9ec981b3ffb113966f1e22a6661a401dfa Mon Sep 17 00:00:00 2001 From: emaktech Date: Tue, 28 May 2019 14:27:29 -0400 Subject: [PATCH] Fix Call Block Type Setting Check When setting call_block_matching, the setting was not being evaluated as true because it was looking for 'call block' group when the actual name is 'call_block'. Adding the underscore fixes this small syntax issue and the setting works correctly. --- resources/install/scripts/app/call_block/index.lua | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/resources/install/scripts/app/call_block/index.lua b/resources/install/scripts/app/call_block/index.lua index ee5a888ed4..66acde087a 100644 --- a/resources/install/scripts/app/call_block/index.lua +++ b/resources/install/scripts/app/call_block/index.lua @@ -89,7 +89,7 @@ This method causes the script to get its manadatory arguments directly from the -- get the configuration variables from the DB local db = dbh or Database.new('system') local settings = Settings.new(db, domain_name, domain_uuid) - local call_block_matching = settings:get('call block', 'call_block_matching', 'text'); + local call_block_matching = settings:get('call_block', 'call_block_matching', 'text'); --send to the log logger("D", "NOTICE", "params are: " .. string.format("'%s', '%s', '%s', '%s'", params["cid_num"],