From c02a439e3b5793b3feedf2f08c1da582973e245e Mon Sep 17 00:00:00 2001 From: Russell Bryant Date: Wed, 6 Feb 2008 15:19:41 +0000 Subject: [PATCH] Clarify setting DYNAMIC_FEATURES so that it gets inherited by outbound channels. (due to a discussion between me and a user via email) git-svn-id: https://origsvn.digium.com/svn/asterisk/branches/1.4@102651 65c4cc65-6c06-0410-ace0-fbb531ad65f3 --- configs/features.conf.sample | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/configs/features.conf.sample b/configs/features.conf.sample index 57b1fa12b7..969074c8e5 100644 --- a/configs/features.conf.sample +++ b/configs/features.conf.sample @@ -47,8 +47,11 @@ context => parkedcalls ; Which context parked calls are in ; 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) +; Set(__DYNAMIC_FEATURES=myfeature1#myfeature2#myfeature3) ; +; (Note: The two leading underscores allow these feature settings to be set on +; on the outbound channels, as well. Otherwise, only the original channel +; will have access to these features.) ; ; The syntax for declaring a dynamic feature is the following: ;