Merged revisions 128599 via svnmerge from

https://origsvn.digium.com/svn/asterisk/trunk

........
r128599 | mmichelson | 2008-07-07 09:35:27 -0500 (Mon, 07 Jul 2008) | 6 lines

Update a few instances of "extensions reload" to "dialplan reload"
in the documentation.

Patch provided by caio1982 (license 22)


........


git-svn-id: https://origsvn.digium.com/svn/asterisk/branches/1.6.0@128601 65c4cc65-6c06-0410-ace0-fbb531ad65f3
This commit is contained in:
Mark Michelson
2008-07-07 14:36:30 +00:00
parent 8c095156bd
commit 2fbb1c5b86
2 changed files with 2 additions and 2 deletions

View File

@@ -70,7 +70,7 @@ writeprotect=no
;extenpatternmatchnew=no ;extenpatternmatchnew=no
; ;
; If clearglobalvars is set, global variables will be cleared ; If clearglobalvars is set, global variables will be cleared
; and reparsed on an extensions reload, or Asterisk reload. ; and reparsed on a dialplan reload, or Asterisk reload.
; ;
; If clearglobalvars is not set, then global variables will persist ; If clearglobalvars is not set, then global variables will persist
; through reloads, and even if deleted from the extensions.conf or ; through reloads, and even if deleted from the extensions.conf or

View File

@@ -6,7 +6,7 @@ must be added to a context. Then, you configure the calling "line" to have
access to this context. access to this context.
If you change the dialplan, you can use the Asterisk CLI command If you change the dialplan, you can use the Asterisk CLI command
"extensions reload" to load the new dialplan without disrupting "dialplan reload" to load the new dialplan without disrupting
service in your PBX. service in your PBX.
Extensions are routed according to priority and may be based on any set Extensions are routed according to priority and may be based on any set