mazilo, Configurations such as this are typically used in high-volume/high-availability configurations where the added complexity is needed to meet the unique demands of these systems. If you're providing standard PBX functionality to a few hundred (maybe even thousand) users, FreeSWITCH will do very well on its own (even on a single machine). If you need to provide this functionality to tens of thousands of users (perhaps even more) it starts to make sense to use Kamailio and FreeSWITCH together with Kamailio providing significant scale benefits for SIP signaling and FreeSWITCH providing media handling and PBX functionality. This configuration is also more well suited to failover, load balancing, HA, etc using the SIP functionality in Kamailio. From what I can tell you're better off using FreeSWITCH standalone. On Tue, Nov 30, 2010 at 11:31 AM, mazilo <Nabble@slickdeals.endjunk.com> wrote:
What I meant by PBX system is the basic (default) PBX features from FreeSWITCH. For instance, when I have my FS up for the first time, I just configured my ATA to register to my FS as an extension, added several trunks, and can use it right the way to place/receive calls. What I meant is if I configured my FS as an SBC to Kamailio, will the existing configurations still be working along with the new addition as SBC to Kamailio?
Of course there are some PBX functionalities that can be implemented in
Kamailio, like call hunting -- it is a matter of your design decision. This may not be a bad idea. BTW, since I am not familiar with Kamailio, is it possible configure Kamailio with a trunk to register to a VoIP service provider, i.e. http://callcentric.com CallCentric , etc.?
-- Kristian Kielhofner http://www.astlinux.org http://blog.krisk.org http://www.star2star.com http://www.submityoursip.com http://www.voalte.com