I've also thought about these but not implemented any. A couple of my suggestions, both require some location database to say where the conference is: 1. 302 to the correct server, OpenSIPS can handle this for you. 2. Use the second style call to conference app, which then outbound dials into the original one if needs be. On 6 December 2012 14:49, Cal Leeming [Simplicity Media Ltd] < cal.leeming@simplicitymedialtd.co.uk> wrote:
+1, would be very interesting to hear the different thoughts and approaches.
On Thu, Dec 6, 2012 at 2:00 PM, Emrah <lists@kavun.ch> wrote:
This is most interesting and I am curious to know the answer as well.
Cheers, E On Dec 5, 2012, at 5:16 PM, Daniel Eiland <daniel.eiland@gmail.com> wrote:
Hi guys,
I'm trying to deploy a conferencing solution using FreeSWITCH and running into a small issue with fail over / hot-standbys.
In my environment, I've got multiple FreeSWITCH/Conference endpoints registered with an OpenSIPS proxy. When calls come into OpenSIPS they are routed to the FreeSWITCH endpoints based on their q-values. If a FreeSWITCH instance fails (namely the one with the highest q-value), the call is simply routed to the next instance. This works great in most situations, however in some cases (namely network congestion) the FreeSWITCH w/highest priority is simply temporarily unavailable and callers to the same conference endpoint land on different servers.
I'm wondering if there is a mechanism for distributing (or sharing) a conference room across multiple FreeSWITCH instances. Namely, if a user lands in a conference hosted on server A while another lands in the same conference on server B, is there a mechanism in FreeSWITCH to connect the two servers/conferences (Presumably some "static" connection between the servers/rooms) so they can still talk with each over?
Thanks, Daniel
_________________________________________________________________________
Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.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
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.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
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.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
-- *Andrew Cassidy BSc (Hons) MBCS SSCA* Managing Director *T <info@cassidywebservices.co.uk> *03300 100 960 *F<info@cassidywebservices.co.uk> *03300 100 961 *E <info@cassidywebservices.co.uk> *andrew@cassidywebservices.co.uk *W <info@cassidywebservices.co.uk> *www.cassidywebservices.co.uk