Posted: Thu Dec 02, 2004 10:33 am Post subject: [Asterisk-doc] docs/volume-one vm1chp3-compiling.xml, 1.13,
Comments:
Update of /cvsroot/asterisk/docs/volume-one
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv24122/volume-one
Modified Files:
vm1chp3-compiling.xml vm1chp5-dialplans.xml
Log Message:
s/seperate/separate/
Index: vm1chp3-compiling.xml
===================================================================
RCS file: /cvsroot/asterisk/docs/volume-one/vm1chp3-compiling.xml,v
retrieving revision 1.13
retrieving revision 1.14
diff -C2 -d -r1.13 -r1.14
*** vm1chp3-compiling.xml 11 Oct 2004 19:48:01 -0000 1.13
--- vm1chp3-compiling.xml 2 Dec 2004 18:30:28 -0000 1.14
***************
*** 281,285 ****
<note>
<para>
! The loadzone parameter allows you to specify the tones that can be generated by that interface. A comma seperated list of two letter country codes will load the tones for that country or region. The currently available list of tone zones defined in the <filename>
zonedata.c</filename>
file in <filename
--- 281,285 ----
<note>
<para>
! The loadzone parameter allows you to specify the tones that can be generated by that interface. A comma separated list of two letter country codes will load the tones for that country or region. The currently available list of tone zones defined in the <filename>
zonedata.c</filename>
file in <filename
Index: vm1chp5-dialplans.xml
===================================================================
RCS file: /cvsroot/asterisk/docs/volume-one/vm1chp5-dialplans.xml,v
retrieving revision 1.16
retrieving revision 1.17
diff -C2 -d -r1.16 -r1.17
*** vm1chp5-dialplans.xml 11 Oct 2004 19:48:02 -0000 1.16
--- vm1chp5-dialplans.xml 2 Dec 2004 18:30:28 -0000 1.17
***************
*** 604,608 ****
</para>
--><para>
! In our examples thus far we have limited ourselves to a single context. It is probably fair to assume that most installations will have more than one context. One great use of contexts is to give outside callers a different experience than people calling from inside extensions. Besides providing a different user experience, contexts are also used as a mechanism to seperate privileges for different classes of callers, where the privilege might be making long-distance calls, or calling certain extensions. In our next example, we'll create a simple dialplan with two internal phone extensions, and set up the ability for these two extension to call each other. To accomplish this, let's create a new context called [internal].</para>
<note>
<para>
--- 604,608 ----
</para>
--><para>
! In our examples thus far we have limited ourselves to a single context. It is probably fair to assume that most installations will have more than one context. One great use of contexts is to give outside callers a different experience than people calling from inside extensions. Besides providing a different user experience, contexts are also used as a mechanism to separate privileges for different classes of callers, where the privilege might be making long-distance calls, or calling certain extensions. In our next example, we'll create a simple dialplan with two internal phone extensions, and set up the ability for these two extension to call each other. To accomplish this, let's create a new context called [internal].</para>
<note>
<para>
***************
*** 881,885 ****
send the user to their mailbox and prompts them for a password (if configured
to require a password). This allows the user to check their voicemail without
! requiring them to login to a seperate extension.
</para>
</sect2>
--- 881,885 ----
send the user to their mailbox and prompts them for a password (if configured
to require a password). This allows the user to check their voicemail without
! requiring them to login to a separate extension.
</para>
</sect2>
***************
*** 945,949 ****
[internal]
exten => _1XXX,1,Dial(SIP/${EXTEN}) <lineannotation>
! ; replace seperate <function>
Dial()</function>
statements with a single pattern matching statement</lineannotation>
--- 945,949 ----
[internal]
exten => _1XXX,1,Dial(SIP/${EXTEN}) <lineannotation>
! ; replace separate <function>
Dial()</function>
statements with a single pattern matching statement</lineannotation>
***************
*** 953,957 ****
<note>
<para>
! Do not seperate your pattern matches with hyphens (-) as this could possibly lead to errors.</para>
</note>
<para>
--- 953,957 ----
<note>
<para>
! Do not separate your pattern matches with hyphens (-) as this could possibly lead to errors.</para>
</note>
<para>
***************
*** 962,968 ****
application we wish to call, we can make use of the ${EXTEN} channel variable. For example, if we were to dial 1001, then our pattern would match that number. The ${EXTEN} variable would then contain the number dialed, and be passed to the <function>
Dial()</function>
! application. We have effectively replaced the two seperate <function>
Dial()</function>
! statements with a single line. All extension numbers in the range of 1000 -> 1999 would be matched by this line and we no longer need to add a seperate line for each extension available to our PBX.</para>
<!--<para>
[Explain ${EXTEN:i:j} syntax]
--- 962,968 ----
application we wish to call, we can make use of the ${EXTEN} channel variable. For example, if we were to dial 1001, then our pattern would match that number. The ${EXTEN} variable would then contain the number dialed, and be passed to the <function>
Dial()</function>
! application. We have effectively replaced the two separate <function>
Dial()</function>
! statements with a single line. All extension numbers in the range of 1000 -> 1999 would be matched by this line and we no longer need to add a separate line for each extension available to our PBX.</para>
<!--<para>
[Explain ${EXTEN:i:j} syntax]
***************
*** 990,994 ****
[internal]
exten => _1XXX,1,Dial(SIP/${EXTEN}) <lineannotation>
! ; replace seperate <function>
Dial()</function>
statements with a single pattern matching statement</lineannotation>
--- 990,994 ----
[internal]
exten => _1XXX,1,Dial(SIP/${EXTEN}) <lineannotation>
! ; replace separate <function>
Dial()</function>
statements with a single pattern matching statement</lineannotation>
***************
*** 1163,1167 ****
[internal]
exten => _1XXX,1,Dial(SIP/${EXTEN}) <lineannotation>
! ; replace seperate <function>
Dial()</function>
statements with a single pattern matching statement</lineannotation>
--- 1163,1167 ----
[internal]
exten => _1XXX,1,Dial(SIP/${EXTEN}) <lineannotation>
! ; replace separate <function>
Dial()</function>
statements with a single pattern matching statement</lineannotation>
***************
*** 1276,1280 ****
[internal]
exten => _1XXX,1,Dial(SIP/${EXTEN}) <lineannotation>
! ; replace seperate <function>
Dial()</function>
statements with a single pattern matching statement</lineannotation>
--- 1276,1280 ----
[internal]
exten => _1XXX,1,Dial(SIP/${EXTEN}) <lineannotation>
! ; replace separate <function>
Dial()</function>
statements with a single pattern matching statement</lineannotation>
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum