Update documentation to not imply we support overriding options.

(closes issue #16855)
Reported by: davidw

git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@250037 65c4cc65-6c06-0410-ace0-fbb531ad65f3
This commit is contained in:
Leif Madsen
2010-03-02 20:36:10 +00:00
parent ecfa2dcb2e
commit aec5c6f840

View File

@@ -152,17 +152,19 @@ consider the following:
\begin{astlisting}
\begin{verbatim}
[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
\end{verbatim}
\end{astlisting}
@@ -173,17 +175,23 @@ following way:
\begin{astlisting}
\begin{verbatim}
[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
\end{verbatim}
\end{astlisting}
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.
\subsubsection{Additional Examples}
(in top-level sip.conf)