[Freeswitch-users] Dynamic Dialplan

[SP]

Everything you can do in a static dialplan you can do via curl as
well.  Multiple extensions, search/conditions are allowed.  Don't sell
the curl short, it's very powerful and can get the ball rolling.

On Sun, Feb 8, 2009 at 21:21, Doug Blacksone <dougblackstone at gmail.com> wrote:
> Hi,
>
> Right now, I am working on getting freeswitch configured for our call-center
> with more than 1000 agents.  There are several areas where we need the
> dialplan to be configurable based on some user detail in the database.
> Therefore, the dialplan needs to be some-what dynamic based-on inputs from
> the database.
>
> I would like to know from other implementation as to the most scalable way
> of doing high performance dynamic dialplan that is super scalable.
>
> There are three ways I can think of:
>
> 1. Static dialplan using customized freeswitch mod to access postgres for
> data
> pros: best performance
> cons: harder to program
>
> 2. Static dialplan using lua to access postgres for data
> pros: easy to program, maybe-performance is better than curl
> cons: need to search through all the extensions to find one dialplan,
> performance is slower than the first one.
>
> 3. curl-based dialplan using Java Servlet and HTTP
> pros: easy to program, freeswitch only gets one extension and no extension
> search
> cons: performance is slow than the other two
>
> Is this a correct analysis?
> If from a pure performance's perspective, how much performance can a
> customized mod gains in comparison to lua?
>
> For a production system that needs to be highly scalable, what do you
> recommend?
>
>
> Thank you very much for any input to our critical design decision.
>
> Doug