From e62193f887b236eba7e2fa66afd446a974056880 Mon Sep 17 00:00:00 2001 From: Tilghman Lesher Date: Mon, 15 Dec 2008 21:17:07 +0000 Subject: Allow disabling pattern match searches within the Realtime dialplan switch. (closes issue #13698) Reported by: fhackenberger Patches: 20081211__bug13698.diff.txt uploaded by Corydon76 (license 14) Tested by: fhackenberger git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@164485 65c4cc65-6c06-0410-ace0-fbb531ad65f3 --- configs/extconfig.conf.sample | 13 +++++++++++++ 1 file changed, 13 insertions(+) (limited to 'configs') diff --git a/configs/extconfig.conf.sample b/configs/extconfig.conf.sample index 4c3899fcd..8a17f9b41 100644 --- a/configs/extconfig.conf.sample +++ b/configs/extconfig.conf.sample @@ -60,4 +60,17 @@ ;queue_members => odbc,asterisk ;musiconhold => mysql,asterisk ;queue_log => mysql,aasterisk +; +; +; While most dynamic realtime engines are automatically used when defined in +; this file, 'extensions', distinctively, is not. To activate dynamic realtime +; extensions, you must turn them on in each respective context within +; extensions.conf with a switch statement. The syntax is: +; switch => Realtime/[[db_context@]tablename]/ +; The only option available currently is the 'p' option, which disallows +; extension pattern queries to the database. If you have no patterns defined +; in a particular context, this will save quite a bit of CPU time. However, +; note that using dynamic realtime extensions is not recommended anymore as a +; best practice; instead, you should consider writing a static dialplan with +; proper data abstraction via a tool like func_odbc. -- cgit v1.2.3