[Asterisk-Users] Fast AGI Options. Eeeek!

Douglas Garstang
2006-01-25T19:45:50Z

Some questions regarding calling Fast AGI from the dial plan.

Considering that the server side of the Fast AGI has to be able to a) use
threading and b) connect to MySQL, this causes some serious limitations. I'm
not a C programmer, so development options are either perl or python.

It appears that the perl DBI isn't thread safe, so that rules out Perl.
Python's database interfaces are apparently thread safe _to a point_, so
that seems like a better idea. I'd prefer to stick with Perl because I am
more familar with it, but oh well...

Has anyone done this? Was it successful? Did you control the entire dial plan
logic from the AGI, or did you just make AGI calls as necessary to look certain
things up? What about iterative queries where you had to maintain the state from
one call of the AGI to the next? Did you stay in the AGI until control was
complete, or did you return control to the Asterisk dial plan after every
lookup, where it performed some actions, and then you returned to the AGI.... if
this was the way you did it, how did you maintain the database state from one
call to the next???

Did you have multiple AGI scripts, broken down by function, or did you have one
AGI script that was passed a value that specified it's function, and then
you branched into some section of this all-encompassing AGI based on the value
passed?

Thanks,
Doug.