[Asterisk-doc] docs extensions.xml,1.6,1.7

[websmith]

Comments:
Update of /cvsroot/asterisk/docs
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv14802

Modified Files:
	extensions.xml 
Log Message:
More work on explaining contexts and the whole reason that the extensions.conf file is so important.
Index: extensions.xml
===================================================================
RCS file: /cvsroot/asterisk/docs/extensions.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -C2 -d -r1.6 -r1.7
*** extensions.xml	18 May 2004 15:30:50 -0000	1.6
--- extensions.xml	19 May 2004 05:41:27 -0000	1.7
***************
*** 1,34 ****
  <chapter>
- 	<!-- Chapter outline and examples written by Jared Smith -->
  	<title>Creating Dialplans</title>
  	<sect1>
  		<title>Introduction to <filename>extensions.conf</filename></title>
  		<para>
! 		You will spend many hours in this file. It is the basis for how
! 		every call made is dealt with. The concepts covered in this section
! 		will be used the entire time you use Asterisk.
  		</para>
  		<sect2>
  			<title>Contexts</title>
  			<para>
! 			The first bit of information to learn about is contexts. Contexts
! 			have a couple of functions within Asterisk dial plan. Contexts
! 			define scope. All calls that enter Asterisk will begin in a
! 			defined context. What is defined in this context will determine
! 			what is possible for the call to do. Contexts can also help build
! 			an IVR menu where you reuse extension numbers as options on you
! 			menu.
  			</para>
  			<para>
! 			Contexts are capable of including other contexts into themselves. 
! 			The include functionality is even possible on a time of day, 
! 			day of week, or day of month  basis. The normal use for this
! 			conditional include is for an automatic transition from business
! 			hours to after hours prompts to direct a caller. 
  			</para>
  			<para>
! 			Contexts are denoted by their name inside of square brackets.
! 			Contexts may contain extension definitions, and includes of other
! 			contexts. 
  			</para>
  		</sect2>
--- 1,36 ----
  <chapter>
  	<title>Creating Dialplans</title>
+ 	<para>
+ 	The dialplan is the central piece of any Asterisk system.  Simply put, the dialplan specifies what Asterisk should do when it answers a call or when an extension is dialed.  The dialplan consists of a list of instuctions or steps that Asterisk should follow.  It is <emphasis role="strong">absolutely vital</emphasis> that you understand dialplans if you want to setup an Asterisk system.  
+ 	</para>
  	<sect1>
  		<title>Introduction to <filename>extensions.conf</filename></title>
  		<para>
! 			The majority of the dialplan is specified in the file <filename>extension.conf</filename>.  This file is made up of three main parts, namely contexts, extensions, and priorities.
  		</para>
  		<sect2>
  			<title>Contexts</title>
  			<para>
! 			Contexts play a central role within the dialplan.  Contexts define scope. You can think of contexts as a way to keep different parts of a dialplan seperate.  As a simple example, contexts can be used to make Asterisk answer one phone line differently than another.  All calls that Asterisk handles will begin in a specified context. The instructions defined in this context will determine what things may happen to the call. 
  			</para>
  			<para>
! 			Contexts can also be used to create "menus" for you callers to follow.  [Explain that this is called IVR and that IVR is one of the main reasons that people like Asterisk.]
  			</para>
+ <!--
  			<para>
! 			[I think this section should probably be later on... no sense in confusing them with conditional includes this early in the game.]
! 			Contexts are also capable of including other contexts inside themselves.  This functionality is even possible on a time of day, day of week, or day of month  basis. The normal use for this conditional include is for an automatic transition from business hours to after hours prompts to direct a caller. 
! 			</para>
! -->
! 			<para>
! 			Contexts are denoted by their name inside of square brackets.  For example, if we were to create a context called "incoming" for incoming calls, we would define it like this:
! 			<informalexample>
! 			<programlisting>
! 			[incoming]
! 			</programlisting>
! 			</informalexample>
! 			</para>
! 			<para>
! 			All of the instructions placed after a context definition are considered part of that context, until another context is defined.
  			</para>
  		</sect2>
***************
*** 278,287 ****
  			</para>
  			<warning>
! 			<para>
! 			There are currently some problems to be aware of when
! 			using the 'h' extension. Specifically, the
! 			variables about the call are lost as the information is
! 			destroyed with the channel. 
! 			</para>
  			</warning>
  			<para>
--- 280,289 ----
  			</para>
  			<warning>
! 				<para>
! 				There are currently some problems to be aware of when
! 				using the 'h' extension. Specifically, the
! 				variables about the call are lost as the information is
! 				destroyed with the channel. 
! 				</para>
  			</warning>
  			<para>