On Wed, 03 Sep 2014 09:40:00 -0400 Roger Schmid <[email protected]> wrote:
> this xml configuration is the blown up version of asterisk Which is owed to having the same target audience and a common featureset. > native database connection doesnt exist I can only speculate what you mean by that, but depending on what you need the database for, there is of course native support. There is even is a variety of options: e.g. when using lua/js/perl/python/etc. for call control: https://wiki.freeswitch.org/wiki/Languages_for_Call_Control or for filing CDRs away: https://wiki.freeswitch.org/wiki/Cdr > actually in a ISP environment freeswitch is no use, because of > fundamental limit of scalability but a loadtest was promissing and > was showing at least double capacity compared to Asterisk. There are significant architectural advantages freeswitch has over asterisk which I won't dive into right now because they are already well documented by people more familiar with the intricate details. Start here: http://www.freeswitch.org/node/117 For ISP or carrier environments however you're right: neither of both is a good choice. yate offers much more flexibility and scalability there. If you want to go totally crazy, there is also Yxa: http://www.stacken.kth.se/project/yxa/ however I have no idea if it is used anywhere in production. I don't want to start or get into a lengthy debate here about "what's better" because there is no answer to that. In the end the question always is: "Is the tool I'm using the most suitable tool for the job and does the underlying architecture match my preferences and requirements?" Cheers, -mh _______________________________________________ swinog mailing list [email protected] http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog
