I'd have to agree with Duane here. There are very little cases where AGI's aren't suitable.
On Mon, May 5, 2008 at 10:24 AM, Duane <[EMAIL PROTECTED]> wrote: > Reza M. Reza wrote: > > > We are aware of Asterisk's own internal database stuff and want to stay > > away from it. Every hardcore Asterisk consultant/user knows of it and > > almost goes without saying. Also every hardcore Asterisk user knows of > > AGI & its limitations. > > Depends on your application, freepbx seems to use it, although I find > freepbx limiting compared to hand coding asterisk configs myself, > although it is what it is and does what it does. > > What's so limiting about AGI? I find Asterisk unable to handle > registrations/calls a long time before AGI kills performance. > > If the starting up and tearing down of processes is causing problems you > run the app as FastAGI instead, it doesn't even have to be on the same > machine. > > Failing those suggestions you are left with a clear choice/decision, > write or pay someone to write a suitable asterisk module, or use some > other software that will do what you're attempting. > > -- > > Best regards, > Duane > > http://www.freeauth.org - Enterprise Two Factor Authentication > http://www.nodedb.com - Think globally, network locally > http://www.sydneywireless.com - Telecommunications Freedom > http://e164.org - Global Communication for the 21st Century > > "In the long run the pessimist may be proved right, > but the optimist has a better time on the trip." > >
