> On 9/13/07, *Kevin P. Fleming* <kpfleming@digium.com
> <mailto:kpfleming@digium.com>> wrote:
>
> It shouldn't be that hard to translate the AEL example into
> traditional
> dialplan language; in fact, Asterisk does that itself when you
> load the
> AEL into memory, so if you load it yourself and then do a 'dialplan
> show' you'll see the translated version, which you can then copy into
> your database.
>
>
> 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.
>
> 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.).
>
> --
> j.
>
> ------------------------------------------------------------------------
Thank you for the awesome help!
--
Thank you and have a wonderful day,
Anthony Francis
Rockynet VOIP
(303) 444-7052 opt 2
voip@rockynet.com
_______________________________________________
Sign up now for AstriCon 2007! September 25-28th.
--Bandwidth and Colocation Provided by http://www.api-digital.com--
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
No comments:
Post a Comment