From a92e9340754e770411d3a04defd629bce58370d3 Mon Sep 17 00:00:00 2001 From: Mark Michelson Date: Mon, 7 Jul 2008 14:35:27 +0000 Subject: 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/trunk@128599 65c4cc65-6c06-0410-ace0-fbb531ad65f3 --- configs/extensions.conf.sample | 2 +- doc/tex/extensions.tex | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/configs/extensions.conf.sample b/configs/extensions.conf.sample index 71a4b204f..2fe4db3f3 100644 --- a/configs/extensions.conf.sample +++ b/configs/extensions.conf.sample @@ -70,7 +70,7 @@ writeprotect=no ;extenpatternmatchnew=no ; ; 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 ; through reloads, and even if deleted from the extensions.conf or diff --git a/doc/tex/extensions.tex b/doc/tex/extensions.tex index 262d14ecd..7521616a1 100644 --- a/doc/tex/extensions.tex +++ b/doc/tex/extensions.tex @@ -6,7 +6,7 @@ must be added to a context. Then, you configure the calling "line" to have access to this context. 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. Extensions are routed according to priority and may be based on any set -- cgit v1.2.3