[asterisk-users] Dial

[Steve Edwards]

On Thu, 2 Jul 2009, Steve Totaro wrote:

> AMI has historically been flaky under high load.
>
> Not sure about these days, probably better, but once upon a time 
> pounding on the AMI would crash or just freeze a box, requiring a hard 
> reboot.  The machine would become totally unresponsive except to pings.
>
> Call files worked much better, but that is history, not sure if any of 
> it still applies, but call files work well.
>
> A combination of both call files and AMI would be elaborate.
>
> Maybe some kind of proggy that can interpret output and can issue 
> commands directly into the Asterisk CLI.

My issue with call files is that it is not easy to get any sort of 
feedback with respect to the success or failure of the call, especially 
back into the program that created the call file. Plus, it seems so 
kludgey and inefficient to create a bunch of files and shuffle them about.

Access through the CLI (via -r -x) is problematic because you are subject 
to the whims of another process changing verbosity levels and you may have 
to sift through a lot of cruft as well as the overhead of invoking a 
process for each command.

Access through ${astrundir}/asterisk.ctl would be interesting, especially 
if more than 1 process attempts access.

AMI sounds like the best path to me -- asuming it has improved it's 
stability. I'm still a 1.2 Luddite :)

Thanks in advance,
------------------------------------------------------------------------
Steve Edwards      sedwards at sedwards.com      Voice: +1-760-468-3867 PST
Newline                                             Fax: +1-760-731-3000