[asterisk-commits] branch murf/AEL-trunk-fixesonly r33067 - /team/murf/AEL-trunk-fixesonly/doc/

[asterisk-commits at lists.digium.com]

Author: murf
Date: Thu Jun  8 13:04:18 2006
New Revision: 33067

URL: http://svn.digium.com/view/asterisk?rev=33067&view=rev
Log:
added some verbage to ael.txt to cover the cidmatch spec in
extension names.


Modified:
    team/murf/AEL-trunk-fixesonly/doc/ael.txt

Modified: team/murf/AEL-trunk-fixesonly/doc/ael.txt
URL: http://svn.digium.com/view/asterisk/team/murf/AEL-trunk-fixesonly/doc/ael.txt?rev=33067&r1=33066&r2=33067&view=diff
==============================================================================
--- team/murf/AEL-trunk-fixesonly/doc/ael.txt (original)
+++ team/murf/AEL-trunk-fixesonly/doc/ael.txt Thu Jun  8 13:04:18 2006
@@ -35,7 +35,7 @@
       Asterisk. Embedded in this language is the Application/AGI
       commands, of which one application call per step, or priority
       can be made. You can think of this as a "macro assembler"
-      language, that AEL2 will compile into.
+      language, that AEL will compile into.
 
 
 Any programmer of AEL should be familiar with it's syntax, of course,
@@ -178,7 +178,7 @@
 * About "aelparse"          *
 *****************************
 
-You can also use the "aelparse" program to check your extensions.ael
+You can use the "aelparse" program to check your extensions.ael
 file before feeding it to asterisk. Wouldn't it be nice to eliminate
 most errors before giving the file to asterisk?
 
@@ -270,7 +270,7 @@
 capitalized letter somewhere in its name. In the Asterisk extension
 language, application names are NOT case-sensitive.
 
-The following are keywords in the AEL2 language:
+The following are keywords in the AEL language:
 
     * abstract
     * context
@@ -581,6 +581,9 @@
 specification of hints, and a keyword, regexten, that will force the
 numbering of priorities to start at 2.
 
+The ability to make extensions match by CID is preserved in
+AEL; just use '/' and the CID number in the specification. See below.
+
 
 context default {
 
@@ -604,6 +607,18 @@
 
 The regexten must come before the hint if they are both present.
 
+CID matching is done as with the extensions.conf file. Follow the extension
+name/number with a slash (/) and the number to match against the Caller ID:
+
+context zoombo 
+{
+	819/7079953345 => { NoOp(hello, 3345); }
+}
+
+In the above,  the 819/7079953345 extension will only be matched if the
+CallerID is 7079953345, and the dialed number is 819. Hopefully you have
+another 819 extension defined for all those who wish 819, that are not so lucky
+as to have 7079953345 as their CallerID!
 
 
 Includes