[Asterisk-doc] docs/volume-one vm1chp3-compiling.xml, 1.8,
1.9 vm1chp5-dialplans.xml, 1.14, 1.15
jimvanm
cvs at sohoskyway.net
Wed Oct 6 23:43:20 CDT 2004
Comments:
Update of /cvsroot/asterisk/docs/volume-one
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv9411/volume-one
Modified Files:
vm1chp3-compiling.xml vm1chp5-dialplans.xml
Log Message:
Started work on references to v1.0.
Also, began the process of changing from CVS to FTP for downloading.
Index: vm1chp3-compiling.xml
===================================================================
RCS file: /cvsroot/asterisk/docs/volume-one/vm1chp3-compiling.xml,v
retrieving revision 1.8
retrieving revision 1.9
diff -C2 -d -r1.8 -r1.9
*** vm1chp3-compiling.xml 17 Sep 2004 03:07:29 -0000 1.8
--- vm1chp3-compiling.xml 7 Oct 2004 04:43:14 -0000 1.9
***************
*** 1,293 ****
<?xml version="1.0" encoding="UTF-8"?>
! <chapter>
! <title>Compiling Asterisk</title>
!
! <sect1>
! <title>Getting Asterisk from CVS</title>
!
! <sect2>
! <title>What is CVS?</title>
!
[...1094 lines suppressed...]
! ></example
! ><para
! >With this minimal configuration set, we should be able to start Asterisk successfully. We can do this with the following command.</para
! ><example
! ><title
! >Starting Asterisk</title
! ><programlisting
! >
/usr/sbin/asterisk -cvvv
! </programlisting
! ></example
! ><para
! >Asterisk will start now and you should see a <command
! >CLI*></command
! > prompt. You will notice several errors as Asterisk starts saying it is unable to find various file names. These files are currently outside the scope of this document and will be discussed in future volumes. At this point Asterisk is not fully functional, but we do know that it will start successfully. All that remains is the configuration of the system.</para
! ></sect2
! ></sect1
! ></chapter
! >
\ No newline at end of file
Index: vm1chp5-dialplans.xml
===================================================================
RCS file: /cvsroot/asterisk/docs/volume-one/vm1chp5-dialplans.xml,v
retrieving revision 1.14
retrieving revision 1.15
diff -C2 -d -r1.14 -r1.15
*** vm1chp5-dialplans.xml 28 Sep 2004 18:00:20 -0000 1.14
--- vm1chp5-dialplans.xml 7 Oct 2004 04:43:14 -0000 1.15
***************
*** 4,10 ****
>Brief Introduction to Dialplans</title
><para
! >The dialplan is the heart of an Asterisk system. The dialplan defines how Asterisk should handle calls. It consists of a list of instructions or steps that Asterisk should follow, which are triggered by digits received by the system. To sucessfully set up your own Asterisk system, it is <emphasis
! >absolutely vital</emphasis
! > that you understand dialplans.</para
><para
>This chapter will explain how dialplans work in a step-by-step manner, and give you the skills to create your own. The examples in this chapter have been designed to build upon one another, so feel free to go back and reread a section if something doesn't make sense. While this chapter is by no means an exhaustive survey of all the possible things that dialplans can do, our aim is to cover all the fundamentals.</para
--- 4,8 ----
>Brief Introduction to Dialplans</title
><para
! >The dialplan is the heart of an Asterisk system, as it defines how Asterisk should handle calls. It consists of a list of instructions or steps that Asterisk should follow, which are triggered by digits (or characters) received from a channel or application. To sucessfully set up your own Asterisk system, you will need to understand the dialplan.</para
><para
>This chapter will explain how dialplans work in a step-by-step manner, and give you the skills to create your own. The examples in this chapter have been designed to build upon one another, so feel free to go back and reread a section if something doesn't make sense. While this chapter is by no means an exhaustive survey of all the possible things that dialplans can do, our aim is to cover all the fundamentals.</para
***************
*** 14,47 ****
><para
>The majority of the dialplan is specified in the file <filename
! >extensions.conf</filename
! >. This file is made up of four main parts: contexts, extensions, priorities, and applications. In this section, we'll cover each of these parts, and explain how they work together to create a dialplan.</para
><note
- ><title
- ></title
><para
! >In most Asterisk installations, the <filename
! >extensions.conf</filename
! > file is located in either <filename
! class="directory"
! >/etc/asterisk</filename
! > or <filename
! class="directory"
! >/usr/local/asterisk/etc</filename
! >. The location of your <filename
>extensions.conf</filename
> may vary, depending on how you installed Asterisk.</para
></note
><para
>If you installed the Asterisk sample files, you probably have an existing <filename
>extensions.conf</filename
! > file. We do not recommend modifying the existing file. Instead, we suggest you create your <filename
>extensions.conf</filename
! > file from scratch. This will greatly assist your learning, and give you a better understanding of how each part of the file plays a role in the dialplan. </para
><para
! >Having just told you that you should not use the sample files to build your first dialplan, we should also tell you that the sample <filename
>extensions.conf</filename
! > remains a fantastic resource to learn many of the variables and assorted subtleties of dialplans. Rather than delete it we suggest you rename it to something like <filename
>extensions.conf.sample</filename
! >. You will then always have it to refer to later.</para
><sect2
><title
--- 12,51 ----
><para
>The majority of the dialplan is specified in the file <filename
! >/etc/asterisk/extensions.conf</filename
! >. </para
><note
><para
! >The location of your <filename
>extensions.conf</filename
> may vary, depending on how you installed Asterisk.</para
></note
><para
+ >This file is made up of four main parts: <emphasis
+ >contexts</emphasis
+ >, <emphasis
+ >extensions</emphasis
+ >, <emphasis
+ >priorities</emphasis
+ >, and <emphasis
+ >applications</emphasis
+ >. In this section, we'll cover each of these parts, and explain how they work together to create a dialplan. When we're done, you will have created a basic, yet functional dialplan.</para
+ ><para
>If you installed the Asterisk sample files, you probably have an existing <filename
>extensions.conf</filename
! > file. We are not going to modify that file. Instead, we suggest you build your <filename
>extensions.conf</filename
! > file from scratch. This will greatly assist your learning, and give you a better understanding of how each part of the file plays a role in the dialplan.</para
><para
! >The sample <filename
>extensions.conf</filename
! > remains a fantastic resource to learn many of the variables and assorted subtleties of dialplans. We suggest you rename it to something like <filename
>extensions.conf.sample</filename
! >. You will then always have it to refer to later. Try something like this:</para
! ><para
! ><programlisting
! ># mv /etc/asterisk/extensions.conf /etc/asterisk/extensions.conf.sample</programlisting
! ></para
! ><para
! ></para
><sect2
><title
***************
*** 52,59 ****
> context does something completely different from menu choice "1" in the <token
>[ServiceDepartment]</token
! > context. You can put different users in different contexts, so that when someone [ABCWidgetsInc] dials "0" from their set they go to their own reception but when the president of [KeepItSimpleStoopid] dials "0" he goes directly to the PSTN operator. This could be handy if we wanted to provide different reception destinations for differnt companies, all sharing the same Asterisk server. Any call that Asterisk handles will begin in a certain context. The instructions defined in this context will determine what things may happen to the call.</para
><note
- ><title
- ></title
><para
>Contexts are often used to create voice menus that give callers a list of extensions to choose from by pressing keys on a touch-tone phone. This functionality is commonly referred to as an auto-attendant. We'll cover auto-attendants in more depth later in the chapter.</para
--- 56,61 ----
> context does something completely different from menu choice "1" in the <token
>[ServiceDepartment]</token
! > context. You can put different users in different contexts, so that when someone from [ABCWidgetsInc] dials "0" from their set they go to their own reception but when the president of [KeepItSimpleStoopid] dials "0" he goes directly to the PSTN operator. This could be handy if we wanted to provide different reception destinations for different companies, all sharing the same Asterisk server. Any call that Asterisk handles will begin in a certain context. The instructions defined in this context will determine what things may happen to the call.</para
><note
><para
>Contexts are often used to create voice menus that give callers a list of extensions to choose from by pressing keys on a touch-tone phone. This functionality is commonly referred to as an auto-attendant. We'll cover auto-attendants in more depth later in the chapter.</para
***************
*** 86,90 ****
>At the very beginning of the <filename
>extensions.conf</filename
! > file, there is a special context called [globals]. The globals context is where settings and variables can be defined that can be used throughout your dialplan. We aren't going to use the full power of the [globals] context, but you should be aware of why it exists. <!--
[I'm taking this out for now... let's not confuse them with
variables yet. Think simple!]
--- 88,92 ----
>At the very beginning of the <filename
>extensions.conf</filename
! > file, there is a special context called [globals]. The globals context is where settings and variables can be defined that can be used throughout your dialplan. We aren't going to use the full power of the [globals] context, but you should be aware of why it exists.<!--
[I'm taking this out for now... let's not confuse them with
variables yet. Think simple!]
***************
*** 1204,1213 ****
><para
><emphasis
! >Hangup</emphasis
! > is where calls will go to when hangup is detected, or where you can send calls that you want to hangup on.</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
><emphasis
--- 1206,1211 ----
><para
><emphasis
! >Invalid</emphasis
! > is for when Asterisk has determined that the input from the call is not valid for the current context. You may wish to play a prompt explaining the extension was invalid, and then send the call back to the extension that contains the menu prompts.</para
><para
><emphasis
***************
*** 1216,1221 ****
><para
><emphasis
! >Invalid</emphasis
! > is for when Asterisk has determined that the input from the call is not valid for the current context. You may wish to play a prompt explaining the extension was invalid, and then send the call back to the extension that contains the menu prompts.</para
><para
><emphasis
--- 1214,1223 ----
><para
><emphasis
! >Hangup</emphasis
! > is where calls will go to when hangup is detected, or where you can send calls that you want to hangup on.<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
><para
><emphasis
***************
*** 1340,1344 ****
>Conclusion</title
><para
! >We have simply scratched the surface of dialplan creation within Asterisk. However, you now have enough knowledge to go out learn the many applications that Asterisk has built into it to expand your dialplan. You should now understand many of the fundamental applications and be well on your way to creating full features dialplans. Spend more time playing with the applications built into Asterisk and expanding upon the dialplan we've created in this chapter by utilizing the basic skills you have aquired from this book. Asterisk is a wonderful and ever evolving application. We hope you have learned much and continue developing with the Asterisk platform.</para
></sect1
></chapter
--- 1342,1346 ----
>Conclusion</title
><para
! >By this point it must be obvious that we have simply scratched the surface of dialplan creation within Asterisk. However, you now have enough knowledge to go out and learn the many applications that Asterisk has built into it to expand your dialplan. You should now understand many of the fundamental applications and be well on your way to creating powerful dialplans. Spend more time playing with the applications built into Asterisk and expanding upon the dialplan we've created in this chapter by utilizing the basic skills you have aquired from this book. Asterisk is a wonderful and ever evolving application. We hope you have learned much and continue developing with the Asterisk platform.</para
></sect1
></chapter
More information about the Asterisk-Doc
mailing list