On 9/13/07, <b class="gmail_sendername">Kevin P. Fleming</b> <<a href="mailto:kpfleming@digium.com">kpfleming@digium.com</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
It shouldn't be that hard to translate the AEL example into traditional<br>dialplan language; in fact, Asterisk does that itself when you load the<br>AEL into memory, so if you load it yourself and then do a 'dialplan
<br>show' you'll see the translated version, which you can then copy into<br>your database.</blockquote><div><br>You can also use 'aelparse -w' to dump extensions.ael as extensions.ael.dump to assist in this. The branching and labeling of priorities is designed for efficiency, not readability, so you'll have to go over it carefully to get a good feel for how AEL constructs are turned into extensions.
<br><br>According to Murf, one of the purposes of this switch was to allow people to write dialplan in AEL and insert it into * installations where AEL was either not supported (1.2) or not viable (GUIs, realtime, resistance to change, etc.).
<br></div></div><br>-- <br>j.<br><br>