VoIP Mailing List Archives

[dougblackstone at gmai...]

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

[krice at freeswitch.org]

If you want an extremely high performance you write your own dialplan module... Its not that hard...

Or option 1 is the more high performance way to fo...

Curl with a serverlet will scale to a point but I doubt it will get to where you need in the long run
Static and do what you need, but how scalable is lua is unknown at this point (someone should post some info on that) and its known that java script doesn’t scale that well for large installs

K


From: Doug Blacksone <dougblackstone@gmail.com>
Reply-To: <freeswitch-users@lists.freeswitch.org>
Date: Mon, 9 Feb 2009 11:21:49 +0800
To: <freeswitch-users@lists.freeswitch.org>
Subject: [Freeswitch-users] Dynamic Dialplan

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







_______________________________________________
Freeswitch-users mailing list
Freeswitch-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org

[sicfslist at gmail.com]

Doug,
Ken is right on this one. I know there are some guys on the list (like Ken) that could help you write a module. It's probably the best way to go (if you're going to have all agents running off of one or two boxes).

If you're going to spread the agents / calls around on multiple boxes or use a combo of OpenSIPS / OpenSer / pick your flavor ... and FS then using xml_curl will work fine. We've got that working today and it's been acceptable.

SDR

[krice at suspicious.org]

Also depending on what your Timeframe is like there is a distributed queue mechanism with skills based routing on the way...


From: Shelby Ramsey <sicfslist@gmail.com>
Reply-To: <freeswitch-users@lists.freeswitch.org>
Date: Sun, 8 Feb 2009 22:20:22 -0600
To: <freeswitch-users@lists.freeswitch.org>
Subject: Re: [Freeswitch-users] Dynamic Dialplan

Doug,

Ken is right on this one. I know there are some guys on the list (like Ken) that could help you write a module. It's probably the best way to go (if you're going to have all agents running off of one or two boxes).

If you're going to spread the agents / calls around on multiple boxes or use a combo of OpenSIPS / OpenSer / pick your flavor ... and FS then using xml_curl will work fine. We've got that working today and it's been acceptable.

SDR




_______________________________________________
Freeswitch-users mailing list
Freeswitch-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org

[andrew at hijacked.us]

On Sun, Feb 08, 2009 at 10:50:31PM -0600, Ken Rice wrote:

[wasim at convergence.pk]

On Mon, Feb 9, 2009 at 10:16 AM, Andrew Thompson <andrew@hijacked.us (andrew@hijacked.us)> wrote:

[pauld at versafon.com]

Option 3 does not have slow performance, Java apps can be highly
scalable high performance when written right, this is a serious strong
typed language unlike lua and javascript.
I actually tested such solution against MySql cluster with 500 calls/m
load script, scaled just fine.
Contact me off list if you need professional help with that.

Doug Blacksone wrote:

[anthony.minessale at g...]

hint: when you have "harder to program" under cons: that's usually how you find the right choice


On Mon, Feb 9, 2009 at 8:01 AM, pauld <pauld@versafon.com (pauld@versafon.com)> wrote:

[kokoska.rokoska at pos...]

Just my 2c:

If you use curl with lighttpd and custom built fastcgi "C" responder (it
is really simple with fcgi libs - even I can do it performance could
be not that bad.

Like I wrote in the past it can handle about 2000 reguest per second
(including SQL query wiht simple "postprocessing").

Best regards,

kokoska.rokoska


Doug Blacksone napsal(a):

[sprice at gmail.com]

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@gmail.com> wrote:

[intralanman at freeswi...]

kokoska rokoska wrote:

[kokoska.rokoska at pos...]

Raymond Chandler napsal(a):

[anthony.minessale at g...]

That's why I chose mod_xml_curl as a demo for the xml_hook api. It's not only a demo, it's rather functional =D

You have 2 choices other than using the stuff we already have in tree.

1) write a custom dialplan module, this module gets a single callback function a dialplan_hunt function that has the session and the caller profile. you can see from mod_enum or mod_dialplan_xml how this can be used to make your own module that looks in a db and returns instructions to FS on the fly.

2) write a custom xml_hook and use it with mod_dialplan_xml, this type of module embeds itself into the xml lookups so when something tries to find something in the xml registry, your function is called and you can do your db lookups and generate the xml returned as binary xml obj built from a result of the query. This is more powerfule because it allows you to pre-empt any xml lookups so you can deliver directory, config, dialplan, phrase macros, etc


mod_xml_curl is an example of #2, it turns the xml_req into a url req and feeds the xml returned over the http socket into an xml object and returns it as the result in place of the static contents of the xml file.


On Mon, Feb 9, 2009 at 12:03 PM, kokoska rokoska <kokoska.rokoska@post.cz (kokoska.rokoska@post.cz)> wrote:

[ajlong at worldlink.net]

What about a mod_perl XML binding like the example here?
http://wiki.freeswitch.org/wiki/Mod_perl and
http://wiki.freeswitch.org/wiki/Mod_perl_and_Generating_XML

Would this be faster than a setup like

mod_curl_xml -> lighttpd -> FastCGI/Perl ?

I guess it would depend on if mod_perl in FreeSWITCH spawns new interpreter per request
or if it uses one interpreter instance with multiple threads to execute pre-loaded perl.

Anyone know if this is the case?

Regards,
-Adam




-----Original Message-----
From: freeswitch-users-bounces@lists.freeswitch.org [mailto:freeswitch-users-bounces@lists.freeswitch.org] On Behalf Of kokoska rokoska
Sent: Monday, February 09, 2009 1:03 PM
To: freeswitch-users@lists.freeswitch.org
Subject: Re: [Freeswitch-users] Dynamic Dialplan




Raymond Chandler napsal(a):

[kokoska.rokoska at pos...]

Anthony Minessale napsal(a):