Update documentation to not imply we support overriding options.

(issue #16855)
Reported by: davidw

git-svn-id: https://origsvn.digium.com/svn/asterisk/branches/1.4@250041 65c4cc65-6c06-0410-ace0-fbb531ad65f3

diff --git a/doc/configuration.txt b/doc/configuration.txt
index 39e906101450d5212adadc7dcd6a33935d048b41..7f86d060f4b98d4d5d697c651d9ea41c76bca99c 100644 (file)
--- a/doc/configuration.txt
+++ b/doc/configuration.txt
@@ -118,32 +118,40 @@ previously based upon) were included in the new section.  For example
 consider the following:
 
 [foo]
-permit=192.168.0.2
-host=asdf
-deny=192.168.0.1
+disallow=all
+allow=ulaw
+allow=alaw
 
 [bar]
-permit=192.168.1.2
-host=jkl
-deny=192.168.1.1
+allow=gsm
+allow=g729
+permit=192.168.2.1
 
 [baz](foo,bar)
+type=friend
 permit=192.168.3.1
+context=incoming
 host=bnm
 
-The [baz] section will be processed as though it had been written in the 
+The [baz] section will be processed as though it had been written in the
 following way:
 
 [baz]
-permit=192.168.0.2
-host=asdf
-deny=192.168.0.1
-permit=192.168.1.2
-host=jkl
-deny=192.168.1.1
+disallow=all
+allow=ulaw
+allow=alaw
+allow=gsm
+allow=g729
+permit=192.168.2.1
+type=friend
 permit=192.168.3.1
+context=incoming
 host=bnm
 
+It should also be noted that there are no guaranteed overriding semantics, 
+meaning that if you define something in one template, you should not expect to
+be able to override it by defining it again in another template.
+
 Additional Examples:
 --------------------