Hi, Am I understanding correctly? I assume Kamailio would remove itself from
the media flow in this case, leaving just Client --> FS --> Client for media transfer, right?
Correct, Kamailio is not involved in media exchange. It sounds like this still wouldn't remove the need for shared state
management across the FS cluster, though. So, you'd have a Kamailio cluster backed by a database processing SIP registrations and location information, backed by FS with a shared database storing call state. This should allow the failure of either a Kamailio instance and/or FS instance and still allow the call to be recovered. It'll also allow you to offload all SIP registration to Kamailio and it's database, while leaving FS freed up for media/call routing. Does this sound right?
It depends, personally I would not have share db between Freeswitch servers. How often you expect one Freeswitch server to fail? In this case shared DB will help only with call recover, so if one server fails second will take care of a call, but if you don't have this then existing calls on that server will drop with server. Again it depends on your requirements if this death and life question, then probably you need to have shared DB, but in almost all other cases, I doubt. I don't expect that freeswitch will fail often, but shared DB will add much more complexity in to this architecture, so again you need to look to your requirements and then you need to decide what is best way for you. With kind regards, Jurijs On Sun, Apr 17, 2016 at 6:56 AM, Sergey Safarov <s.safarov@gmail.com> wrote:
Warning Kazoo is not designed to creation thousands of devices in one realm.
On Sun, Apr 17, 2016, 03:14 Brian :: <bc@iptel.co> wrote:
Take a look at the 2600hz kazoo platform. Will probably do everything you need out of the box..
On Sat, Apr 16, 2016 at 6:01 PM, Colin Morelli <colin.morelli@gmail.com> wrote:
I think that's part of what I'm trying to figure out here.
I'm looking to run a SIP platform that will support multiple tenants and device types (SIP phones, WebRTC clients, etc). Each tenant can be isolated to a subset of hosts, as there's no need to bridge across multiple tenants. My initial thought was to run SIP proxies in front of small clusters of FS servers. Essentially creating cluster A, B, C, and so on, each of which is made up of a few FS hosts. Then, have a much smaller number of Kamailio instances in the front that essentially proxy SIP traffic to the appropriate SIP cluster for the requested domain.
However, I'm not sure how well this scales. I've been reading a lot about FS being great as a media server, but there being better options for the signaling portion. My proposal would still push SIP registration and signaling to FS, just with a proxy in front. The alternative approach is to have Kamailio do all SIP registration and signaling, using FS as a media server, but I'm not sure what implications this has on the ability to do dynamic call routing in FS (for example, how would I use uuid_intercept to intercept a live call if Kamailio is performing all of the signaling)
Most likely my issue is just a lack of depth in the understanding of the roles that Kamailio and FS would play in a hybrid scenario (I'll admit I'm new to this).
Thanks for the response.
Best, Colin
On Sat, Apr 16, 2016 at 12:54 PM Luis Daniel Lucio Quiroz <luis.daniel.lucio@gmail.com> wrote:
Explain more what you want to do. I have dinner it without kamalio.
Don't
know if that fits your needs
Le 16 avr. 2016 12:41 PM, "Colin Morelli" <colin.morelli@gmail.com> a écrit :
Does anyone have any good references for horizontally scaling out
large
multi-tenant FS clusters? Most of what I've been able to find involving load balancing Kamailio/OpenSIPS is fairly old (2+ years), and there's no recent versions of the information available. Has this not changed or is there a fundamental shift in how people have been tackling this problem?
To clarify, I'm just looking for pointers/references here. Although if anyone has some personal experience I'd greatly appreciate specific examples and insight as well.
Thanks in advance.
Best, Colin
Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________
Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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