From 66421e3fc5c359e512f03382abf63a594ce13a2d Mon Sep 17 00:00:00 2001 From: russell Date: Mon, 7 Aug 2006 04:15:52 +0000 Subject: Merge my applicationmap_fixup branch to address the issues described in this post to the asterisk-dev mailing list: http://lists.digium.com/pipermail/asterisk-dev/2006-August/022174.html This implements full control over both which channel(s) can activate a dynamic feature, as well as which channel to run the application on. I also updated the documentation on the applicationmap in features.conf.sample in hopes that the configuration is more clear. git-svn-id: http://svn.digium.com/svn/asterisk/trunk@39109 f38db490-d61c-443f-a65b-d21fe96a405b --- configs/features.conf.sample | 43 +++++++++++++++++++++++++++++++++++++++---- 1 file changed, 39 insertions(+), 4 deletions(-) (limited to 'configs') diff --git a/configs/features.conf.sample b/configs/features.conf.sample index 1bfa45820..786722386 100644 --- a/configs/features.conf.sample +++ b/configs/features.conf.sample @@ -42,9 +42,44 @@ context => parkedcalls ; Which context parked calls are in ; Note that the DYNAMIC_FEATURES channel variable must be set to use the features ; defined here. The value of DYNAMIC_FEATURES should be the names of the features ; to allow the channel to use separated by '#'. For example: +; ; Set(DYNAMIC_FEATURES=myfeature1#myfeature2#myfeature3) ; -;testfeature => #9,callee,Playback,tt-monkeys ;Play tt-monkeys to - ;callee if #9 was pressed -;pauseMonitor => #1,caller,Pausemonitor ;Pause monitoring on channel -;unpauseMonitor => #3,caller,UnPauseMonitor ;Unpause monitoring on channel +; +; The syntax for declaring a dynaic feature is the following: +; +; => ,[/],[,] +; +; FeatureName -> This is the name of the feature used in when setting the +; DYNAMIC_FEATURES variable to enable usage of this feature. +; DTMF_sequence -> This is the key sequence used to activate this feature. +; ActivateOn -> This is the channel of the call that the application will be executed +; on. Valid values are "self" and "peer". "self" means run the +; application on the same channel that activated the feature. "peer" +; means run the application on the opposite channel from the one that +; has activated the feature. +; ActivatedBy -> This is which channel is allowed to activated this feature. Valid +; values are "caller", "callee", and "both". "both" is the default. +; The "caller" is the channel that executed the Dial application, while +; the "callee" is the channel called by the Dial application. +; Application -> This is the application to execute. +; AppArguments -> These are the arguments to be passed into the application. +; +; +; IMPORTANT NOTE: The applicationmap is not intended to be used for all Asterisk +; applications. When applications are used in extensions.conf, they are executed +; by the PBX core. In this case, these applications are executed outside of the +; PBX core, so it does *not* make sense to use any application which has any +; concept of dialplan flow. Examples of this would be things like Macro, Goto, +; Background, WaitExten, and many more. +; +; +; Example Usage: +; +;testfeature => #9,peer,Playback,tt-monkeys ;Allow both the caller and callee to play +; ;tt-monkeys to the opposite channel +; +;pauseMonitor => #1,self/callee,Pausemonitor ;Allow the callee to pause monitoring +; ;on their channel +;unpauseMonitor => #3,self/callee,UnPauseMonitor ;Allow the callee to unpause monitoring +; ;on their channel -- cgit v1.2.3