add some information on what the user must do to start using AEL

git-svn-id: http://svn.digium.com/svn/asterisk/trunk@5976 f38db490-d61c-443f-a65b-d21fe96a405b

1 files changed, 19 insertions, 0 deletions

diff --git a/doc/README.ael b/doc/README.ael
index ed209bb3c..20ba6f282 100755
--- a/doc/README.ael
+++ b/doc/README.ael
@@ -5,6 +5,25 @@ Over time, people have been pushing to add features to extensions.conf to make
 it more like a programming language.  AEL is intended to provide an actual
 programming language that can be used to write an Asterisk dialplan.
 
+Getting Started
+-------------------------
+The AEL configuration parser (pbx_ael.so) is completely separate from the module
+that parses extensions.conf (pbx_config.so).  To use AEL, the only thing that
+has to be done is the module pbx_ael.so must be loaded by Asterisk.  This will
+be done automatically if using 'autoload=yes' in /etc/asterisk/modules.conf.
+When thenmodule is loaded, it will look for 'extensions.ael' in /etc/asterisk/.
+Both extensions.conf and extensions.ael can be used in conjunction with each 
+other if that is what is desired.  Some users may want to keep extensions.conf
+for the features that are configured in the 'general' section of 
+extensions.conf.
+
+
+Reloading extensions.ael
+-------------------------
+To reload extensions.ael, the following command can be issued at the CLI.
+
+	*CLI> reload pbx_ael.so
+
 
 Contexts
 -------------------------