[Freeswitch-users] Distributed Conference Room

[SamyGo]

Hi,

If I were you, I'd prefer to have a memcached register of active conference
room on their server(s), if the primary server fails to accept my call or
it has reached a max.confernece.participant limit (N lets say) then I would
append custom header in the failure route which tells which server and
which conference room this call belongs to and route it to any End point
FreeSwitch.

Call gets accepted on newer server, add it into the previously stated
opensips registry. Then at the new FreeSwitch server add few scripts to
detect those custom headers..initiate a new conference and a new call to
dial to the server in header and add it into my current conference as
participant. This is really interesting to initiate a call between two
(freeswitches or more) and adding it as participant in local conference.

Thats what I always find more practical.

Any new call to same conference will again consult memcache from opensips
and hence gets routed to the last inserted server IP with participant
vacancy.

I hope I made some sense.

Thanks
Sammy
On Dec 6, 2012 7:05 PM, "Emrah" <lists at 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 at 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 at freeswitch.org
> > http://www.freeswitchsolutions.com
> >
> > 
> > 
> >
> > Official FreeSWITCH Sites
> > http://www.freeswitch.org
> > http://wiki.freeswitch.org
> > http://www.cluecon.com
> >
> > FreeSWITCH-users mailing list
> > FreeSWITCH-users at 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 at freeswitch.org
> http://www.freeswitchsolutions.com
>
> 
> 
>
> Official FreeSWITCH Sites
> http://www.freeswitch.org
> http://wiki.freeswitch.org
> http://www.cluecon.com
>
> FreeSWITCH-users mailing list
> FreeSWITCH-users at lists.freeswitch.org
> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
> http://www.freeswitch.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freeswitch.org/pipermail/freeswitch-users/attachments/20121206/e175b86a/attachment.html