Index: doc/extensions.txt
===================================================================
RCS file: /usr/cvsroot/asterisk/doc/extensions.txt,v
retrieving revision 1.2
diff -u -r1.2 extensions.txt
--- doc/extensions.txt	15 Feb 2004 07:48:46 -0000	1.2
+++ doc/extensions.txt	25 Aug 2005 13:30:08 -0000
@@ -1,18 +1,46 @@
+The Asterisk dialplan
+=====================
+
+The Asterisk dialplan is divided into contexts. For each "line" you want to
+enable, you add an extension in a context reachable for the phone you want
+to dial from. 
+
+If you change the dialplan, you can use the Asterisk CLI command
+"extensions 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
-of digits, #, and *.  For each extension, several actions may be listed
-and each given a priority.  When each action completes, it generally moves
-to the next priority (except for some modules which use explicitly GOTO's. 
+of characters (a-z), digits, #, and *. 
+
+For each extension, several actions may be listed and each given a priority. 
+When each action completes, it generally moves to the next priority (except for
+some modules which use explicitly GOTO's. 
+
 Extensions frequently have data they pass to the executing application
-(most frequently a string).  There are some reserved application names: 
+(most frequently a string).  You can see the available dialplan applications
+by entering the "show applications" command in the CLI.
+
+In this version of Asterisk, dialplan functions are added. These can
+be used as arguments to any application. For a list of the installed
+functions in your Asterisk, use the "show functions" command.
 
-	GoTo:	Go to a specific extension
-	Answer:	Answer the line, if it hasn't already been answered
+* Example dial plan
+
+The example dial plan, in the configs/extensions.conf.sample file
+is installed as extensions.conf if you run "make samples" after
+installation of Asterisk. This file includes many more instructions
+and examples than this file, so it's worthwile to read it.
 	
-Also, there are some extensions with important meanings:
+* Special extensions
+
+There are some extensions with important meanings:
 
 	s:	What to do when an extension context is entered (unless
 		overridden by the low level channel interface)
+		This is used in macros, and some special cases. 
+		"s" is not a generic catch-all wildcard extension.
 	i:	What to do if an invalid extension is entered
+	h:	The hangup extension, executed at hangup
 	t: 	What to do if nothing is entered in the requisite amount
 		of time.