asterisk users - Jun 2008 - Any reason to *not* use AEL? (Also, MixMonitor q)

I am building a new Asterisk server here at the office, and I'm 
wondering if there are any downsides to creating my dialplan with AEL. 
It seems more intuitive (to me), but I'm not sure if there are any 
pitfalls I need to be aware of first.

We use this for internal extensions, 8 pots lines, and our answering 
service which gets about 500 incoming calls a day down our T1.

Also, one more quick question too:  Currently I'm using MixMonitor to 
record incoming calls.  The problem, however, is once calls are 
transferred, recording stops.  Is it possible to keep recording after a 
call is transferred, and if so, how?

Thanks in advance,
Jay

AEL in 1.4 was the first version of AEL that most people consider 
"stable".  Since not many people uses AEL, you won't get nearly as
much
(if any) community support compared to if you are using the non-AEL syntax.

Jay Moore wrote:
> I am building a new Asterisk server here at the office, and I'm 
> wondering if there are any downsides to creating my dialplan with AEL. 
> It seems more intuitive (to me), but I'm not sure if there are any 
> pitfalls I need to be aware of first.
> 
> We use this for internal extensions, 8 pots lines, and our answering 
> service which gets about 500 incoming calls a day down our T1.
> 
> Also, one more quick question too:  Currently I'm using MixMonitor to 
> record incoming calls.  The problem, however, is once calls are 
> transferred, recording stops.  Is it possible to keep recording after a 
> call is transferred, and if so, how?

Jay Moore wrote:
> I am building a new Asterisk server here at the office, and I'm 
> wondering if there are any downsides to creating my dialplan with AEL. 
> It seems more intuitive (to me), but I'm not sure if there are any 
> pitfalls I need to be aware of first.
>
> We use this for internal extensions, 8 pots lines, and our answering 
> service which gets about 500 incoming calls a day down our T1.
>
> Also, one more quick question too:  Currently I'm using MixMonitor to 
> record incoming calls.  The problem, however, is once calls are 
> transferred, recording stops.  Is it possible to keep recording after a 
> call is transferred, and if so, how?
>
> Thanks in advance,
> Jay
>
> _______________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
>
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-users
>   
I use AEL in almost everything I do and work a lot with Steve Murphy to 
work out any issues I have found with it. In Asterisk 1.4 AEL is VERY 
solid. The only thing you need to watch for is falling into some basic 
"traps" like calling ${EXTEN} from within a switch (the AEL compiler 
uses sw-xxxx extensions for case instances).  In order to easier see 
what the compiler puts out, I asked Steve to add the -w option to 
AELPARSE which writes a file (extensions.conf.aeldump) which is . much 
easier to read than doing a "dialplan show [context]".

Anyway, I'll be more than happy to help with any issues you may have 
with AEL. I'm even working on writing a little book or at least series 
of articles on AEL


-- 
Sherwood McGowan
VoIP / Telecom Solutions
sherwood.mcgowan at gmail.com

Jay Moore wrote:
> I am building a new Asterisk server here at the office, and I'm 
> wondering if there are any downsides to creating my dialplan with AEL. 
> It seems more intuitive (to me), but I'm not sure if there are any 
> pitfalls I need to be aware of first.
>
> We use this for internal extensions, 8 pots lines, and our answering 
> service which gets about 500 incoming calls a day down our T1.
>
> Also, one more quick question too:  Currently I'm using MixMonitor to 
> record incoming calls.  The problem, however, is once calls are 
> transferred, recording stops.  Is it possible to keep recording after a 
> call is transferred, and if so, how?
>
> Thanks in advance,
> Jay
>
> _______________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
>
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-users
>   
Also, quick note, you can't continue the recording, however you can 
record a new file upon transfer

-- 
Sherwood McGowan
VoIP / Telecom Solutions
sherwood.mcgowan at gmail.com

On Tuesday 03 June 2008 09:03:16 Sherwood McGowan wrote:
> The only thing you need to watch for is falling into some basic
> "traps" like calling ${EXTEN} from within a switch (the AEL
compiler
> uses sw-xxxx extensions for case instances).
This should already be solved in the latest release.  The extension will
be saved in an alternate variable, and references to ${EXTEN} below
a switch will be converted to use that alternate variable.

-- 
Tilghman

my entire dialplan is in AEL.

Diego Aguirre
Infodag - Inform?tica
FWD#: 459696
EnumLookup#: +55 21 8138-2710
DUNDi-br#: 21 8138-2710

Jay Moore escreveu:
> I am building a new Asterisk server here at the office, and I'm 
> wondering if there are any downsides to creating my dialplan with AEL. 
> It seems more intuitive (to me), but I'm not sure if there are any 
> pitfalls I need to be aware of first.
> 
> We use this for internal extensions, 8 pots lines, and our answering 
> service which gets about 500 incoming calls a day down our T1.
> 
> Also, one more quick question too:  Currently I'm using MixMonitor to 
> record incoming calls.  The problem, however, is once calls are 
> transferred, recording stops.  Is it possible to keep recording after a 
> call is transferred, and if so, how?
> 
> Thanks in advance,
> Jay
> 
> _______________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
> 
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-users
>

On June 3, 2008 09:21:48 am Jay Moore wrote:
> I am building a new Asterisk server here at the office, and I'm
> wondering if there are any downsides to creating my dialplan with AEL.
> It seems more intuitive (to me), but I'm not sure if there are any
> pitfalls I need to be aware of first.
Community support is the big one.  Personally I think AEL's a solution
looking
for a problem.  Ask Leif Madsen about what he can make a standard dialplan 
do.  :-)

-A.

On Tue, Jun 3, 2008 at 8:21 AM, Jay Moore <jaymoore at accu-com.com>
wrote:
> I am building a new Asterisk server here at the office, and I'm
> wondering if there are any downsides to creating my dialplan with AEL.
> It seems more intuitive (to me), but I'm not sure if there are any
> pitfalls I need to be aware of first.
We use AEL exclusively here. We run a small call center with both
inbound queues and outbound sales calls. All told around 3000 calls a
day flow through the system; some inbound, some outbound, some
extension to extension.

No pitfalls that I'm aware of, other than all of the NoOp's it
generates. This leads to a very busy CLI if you run at verbosity level
3 or higher.

-James

2008/6/4 Tzafrir Cohen <tzafrir.cohen at
xorcom.com>:
> On Wed, Jun 04, 2008 at 10:45:13AM +0100, Gavin Henry wrote:
>> What about using RealTime LDAP in 1.6? That woudl be much faster than a
RDBMS.
>
> If performance is such a major issue, why not use explicit queries?
>
> realtime has overhead even in extensions/proiorities where it is not used.
Static will always be faster than any Realtime. But as I understand
it, some things should be kept out of it.