[asterisk-commits] qwell: trunk r80048 - in /trunk: ./ configs/extensions.conf.sample
SVN commits to the Asterisk project
asterisk-commits at lists.digium.com
Mon Aug 20 11:12:29 CDT 2007
Date: Mon Aug 20 11:12:29 2007
New Revision: 80048
Merged revisions 80047 via svnmerge from
r80047 | qwell | 2007-08-20 11:08:49 -0500 (Mon, 20 Aug 2007) | 7 lines
(closes issue #10499)
Reported by: casper
extensions.conf.sample.diff uploaded by casper (license 55)
Update CLI examples in extensions.conf.sample to reflect command changes.
trunk/ (props changed)
Binary property 'branch-1.4-merged' - no diff available.
--- trunk/configs/extensions.conf.sample (original)
+++ trunk/configs/extensions.conf.sample Mon Aug 20 11:12:29 2007
@@ -5,7 +5,7 @@
; inbound and outbound calls in Asterisk.
; This configuration file is reloaded
-; - With the "extensions reload" command in the CLI
+; - With the "dialplan reload" command in the CLI
; - With the "reload" command (that reloads everything) in the CLI
@@ -22,7 +22,7 @@
; if static=yes and writeprotect=no, you can save dialplan by
-; CLI command 'save dialplan' too
+; CLI command "dialplan save" too
@@ -45,10 +45,10 @@
; NOTE: A complication sets in, if you put your global variables into
; the AEL file, instead of the extensions.conf file. With clearglobalvars
-; set, a 'reload' will often leave the globals vars cleared, because it
+; set, a "reload" will often leave the globals vars cleared, because it
; is not unusual to have extensions.conf (which will have no globals)
; load after the extensions.ael file (where the global vars are stored).
-; So, with 'reload' in this particular situation, first the AEL file will
+; So, with "reload" in this particular situation, first the AEL file will
; clear and then set all the global vars, then, later, when the extensions.conf
; file is loaded, the global vars are all cleared, and then not set, because
; they are not stored in the extensions.conf file.
@@ -574,8 +574,8 @@
; For more information on applications, just type "core show applications" at your
; friendly Asterisk CLI prompt.
-; 'core show application <command>' will show details of how you
+; "core show application <command>" will show details of how you
; use that particular application in this file, the dial plan.
-; 'core show functions" will list all dialplan functions
-; 'core show function <COMMAND>' will show you more information about
+; "core show functions" will list all dialplan functions
+; "core show function <COMMAND>" will show you more information about
; one function. Remember that function names are UPPER CASE.
More information about the asterisk-commits