[Asterisk-doc] docs extensions.xml,1.9,1.10

[blitzrage]

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

Modified Files:
	extensions.xml 
Log Message:
blitzrage
- added documentation pertaining to extensions, priorities and the 's' ext.
Index: extensions.xml
===================================================================
RCS file: /cvsroot/asterisk/docs/extensions.xml,v
retrieving revision 1.9
retrieving revision 1.10
diff -C2 -d -r1.9 -r1.10
*** extensions.xml	20 May 2004 05:40:54 -0000	1.9
--- extensions.xml	21 May 2004 18:27:05 -0000	1.10
***************
*** 15,19 ****
  			</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>
  <!--
--- 15,21 ----
  			</para>
  			<para>
! 			<emphasis>[Explain that this is called IVR and that IVR is one of the main reasons that people like Asterisk.]
! 			Contexts can also be used to create "menus" for you callers to follow.  
! 			The menus are what you hear when you call a company that has a recording read things you are able to do.  Based on what the voice says, you make choices on your keypad by pressing different numbers.  This is referred to as an auto-attendant or interactive voice response (IVR) system.  The reason Asterisk is so popular is because of the way you are able to customize different menu systems based on different situations.</emphasis>
  			</para>
  <!--
***************
*** 42,46 ****
  			<para>
  			[C'mon... we've got to change this.  Odds are that the reader won't have any idea what a "subroutine" is, and I'd be willing to be they have no idea what "old BASIC programming" is like.  Can't we explain this in plain english, and not programmer-speak?] 
! 			The extension definitions are very much like subroutines in
  			programming. You will define them as the steps a call will take as
  			it progresses though your dial plan. A single extension line will
--- 44,63 ----
  			<para>
  			[C'mon... we've got to change this.  Odds are that the reader won't have any idea what a "subroutine" is, and I'd be willing to be they have no idea what "old BASIC programming" is like.  Can't we explain this in plain english, and not programmer-speak?] 
! 
! 			The extension definations are how call flow are determined.  These work
! 			in a very linear fashion which makes them easy to understand and follow.
! 			You will define them as the steps a call will take as it progresses through
! 			your dial plan.  A single extension line will contain the extension number or
! 			special letter you are defining, the priority number, the function you wish
! 			to be applied and any arguments to be passed to the function.
! 			</para>
! 			<para>
! 			Functions allow us to perform various actions within our dial plan.  These functions
! 			or "commands" can be passed information also referred to as "arguments".  With this
! 			information our function is able to manipulate the call somehow so that something
! 			happens.  To see a listing of the possible functions you are able to use in Asterisk, see
! 			Appendix C.
! 
! <!--			The extension definitions are very much like subroutines in
  			programming. You will define them as the steps a call will take as
  			it progresses though your dial plan. A single extension line will
***************
*** 50,54 ****
  			passed to the function. The priority numbers must be consecutive for
  			the call to progress from one to the next. Here is an example of a 
! 			extension definition.
  			</para>
  		</sect2>
--- 67,71 ----
  			passed to the function. The priority numbers must be consecutive for
  			the call to progress from one to the next. Here is an example of a 
! 			extension definition. -->
  			</para>
  		</sect2>
***************
*** 59,62 ****
--- 76,85 ----
           extension.  Priority <emphasis>1</emphasis> is executed before
           priority <emphasis>2</emphasis>, and so on.  Each priority calls a function with certain arguments.  (We'll probably have to explain functions and arguments.)]
+ 			Priorities show which order functions are applied to a specified extension.  Each priority calls one specific function
+ 			per line.  The priority numbers are the order in which the functions are applied.  Typically
+                         these priority numbers simply start at 1 and increment consecutively for each line in the context.  However there are 
+ 			exceptions to this rule.  For instance, if you use the Dial() function and the channel you are attempting 
+ 			to call	is busy, then the next priority the context is going to attempt is the current priority number + 101.  This allows
+ 			you to perform a different set of functions when the line is busy, ie. go to voicemail.
  			</para>
  		</sect2>
***************
*** 71,74 ****
--- 94,103 ----
  			<para>
  			[Before we get too far into our example, we should explain the 's' extension.  Explain that when calls are answered, they almost always do to the 's' extension in the context specified by zapata.conf/sip.conf/etc.]
+ 
+ 			The 's' extension is used when we do not have a specific extension we wish to call.  This is used in a context which
+ 			will be directed to when we answer a call.  Incoming calls get directed to either a specified context or the default context.
+ 			We use the 's' extension because there is no specific number we wish to use at this point.  It can almost be thought about
+ 			like an automatically executed extension.  We use the 's' extension in contexts which get referenced in files like zapata.conf
+ 			and sip.conf.
  			</para>
  		</sect2>