[asterisk-users] Building an IVR

Michael Collins
Mon, 07 Jul 2008 18:26:05 -0000

Hmm...



You may be in one of those positions where there just isn't a great
solution because your environment has so many constraints.  You might
want to check out the way freeswitch handles IVRs, dialplan hooks,
FAGI-ish connections, etc.  It will still take some work, of course,
because there isn't an out-of-box solution (that I'm aware of) that can
meet all of your requirements without lots of time/money/effort.



-MC



________________________________

From: asterisk-users-bounces at lists.digium.com
[mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of Douglas
Garstang
Sent: Monday, July 07, 2008 10:21 AM
To: asterisk-users at lists.digium.com
Subject: [asterisk-users] Building an IVR



So, I need to build a complicated IVR with Asterisk, with a lot of back
end hooks. The dial plan itself has a lot of limitations, not the least
of which is that the dial plan is ugly, hard to maintain, and full of
gotchas like all variables being global etc etc.

I've been involved with Asterisk for a couple of years now and this is a
problem I have yet to see a good solution for.

1. I looked at VXML but it has too many integration problems.
2. AGI has overhead.
3. Fast AGI has single point of failure problems (we're using Asterisk
1.2 which bombs out the call when an AGI request fails), and has too
many moving parts for what should be something fairly simple.
4. I'm aware of res_perl, but am not a fan of the maintainability of
perl.
5. I looked for a valid link to res_python, but couldn't find anything.
6. Adhearsion? Looked at it a few months ago but couldn't work it out.
There was too much 'voodoo' going on.
7. I'm not a C programmer, so writing a custom module, is both overkill
and not feasible.

Do I have any other options?

Doug.





-------------- next part --------------
An HTML attachment was scrubbed...