[Freeswitch-users] mod_conference with cluster ODBC

Chris Rienzo cmrienzo at gmail.com
Sat Jan 8 18:28:39 MSK 2011


I think circularly linked conferences cause echo.  Daisy chained conferences have high latency, though are simple to build.


On Jan 8, 2011, at 8:37, "Kris" <kris at livecall.com> wrote:

> On second thought, Joao may be right. If the conference is spread accross 10 
> servers, and one crashes, it keeps the other users chatting. A->B->C->D->A. 
> C crashes, the conference on B has to become aware, and immediately connect 
> to D. I don't know if such failover exists in mod_conference or even if 
> having conferences circularly linked would cause a feedback. If they are 
> circularly linked and only one fails, it should still work even without 
> failover.
> 
> ----- Original Message ----- 
> From: "Madovsky" <infos at madovsky.org>
> To: "FreeSWITCH Users Help" <freeswitch-users at lists.freeswitch.org>
> Sent: Friday, January 07, 2011 3:31 PM
> Subject: Re: [Freeswitch-users] mod_conference with cluster ODBC
> 
> 
> it's what I thought first, but Joao is not hot for that apparently.
> for now I had another idea as I don't want to spread the same
> conference in several servers.
> 
> Franck
> 
> ----- Original Message ----- 
> From: "Kris" <kris at livecall.com>
> To: "FreeSWITCH Users Help" <freeswitch-users at lists.freeswitch.org>
> Sent: Friday, January 07, 2011 4:43 PM
> Subject: Re: [Freeswitch-users] mod_conference with cluster ODBC
> 
> 
> Just an idea..soon I will have to put people that are answered on multiple
> servers into the same conference. I am thinking about having a table on the
> central SQLServer like this: ConferenceName, ServerName. . I would lookup
> the server a particular conference is on and then transfer the caller to
> that server and extension that will put the caller into the appropriate
> conference (dial something.. at SERVER)- I guess. I've seen the export word
> that maybe the way to pass on variables to the other server such as the
> ConferenceName, UserName
> 
> Then the server hosting the conference will have an extension that has the
> forums profile and controls
>      <action application="conference" data="${ConferenceName}@forums"/>
> That way all the users are in the same conference and can be controlled
> there instead of having only one link to a bunch of callers on another
> server.
> 
> If you get it going, could you email the dial strings, extensions you
> used.etc.I am curious..
> Kris
> 
> ----- Original Message ----- 
> From: "Madovsky" <infos at madovsky.org>
> To: "FreeSWITCH Users Help" <freeswitch-users at lists.freeswitch.org>
> Sent: Friday, January 07, 2011 10:28 AM
> Subject: Re: [Freeswitch-users] mod_conference with cluster ODBC
> 
> 
> I got it thanks,
> but do you think it would be more interesting to reduce
> bandwidth and latency between nodes and centralize the conference on one
> node only
> by transferring the incoming user to the right node ?
>  ----- Original Message ----- 
>  From: João Mesquita
>  To: FreeSWITCH Users Help
>  Sent: Thursday, January 06, 2011 4:33 PM
>  Subject: Re: [Freeswitch-users] mod_conference with cluster ODBC
> 
> 
>  Ok, let me see if I can get this into your head. (giggles)
> 
> 
>  A conference means that the audio needs to mixed in together so that all
> participants can talk/hear each other, right? If you implement something in
> C on mod_conference, you are going to essentially do the same as what an ESL
> app does. You _need_ to call in from one server to the other so that you can
> mix the audio of all the participants. The real advantage would be the
> management API being only one for everything and the challenge is exactly
> that. How to mute certain users on a conference that is spanning over 10
> servers or deaf them, etc...
> 
> 
>  A SIP "user" is easier because you don't have to bridge audio from another
> server necessarily. Got it?
> 
> 
>  Regards,
>  João Mesquita
> 
> 
> 
>  On Thu, Jan 6, 2011 at 6:25 PM, Madovsky <infos at madovsky.org> wrote:
> 
>    Rupa,
> 
>    I don't want bother anyone with this thread but why not
>    to manage conference as SIP user ?
>    if someone from server A call an other who is registered on server B, so
>    FS do it automatically, why not with conference ? Or maybe create a
> param
>    in mod_conference that let the choice of the admin to manage unique name
> in
>    all cluster or not.
>    like <param name="cluster_unique_name" value="true"/>
>    I will try to understand the C code to hack something like this...
> 
> 
>    ----- Original Message -----
>    From: "Rupa Schomaker" <rupa at rupa.com>
>    To: "FreeSWITCH Users Help" <freeswitch-users at lists.freeswitch.org>
> 
>    Sent: Thursday, January 06, 2011 3:01 PM
>    Subject: Re: [Freeswitch-users] mod_conference with cluster ODBC
> 
> 
>    Yes
> 
>    On Thu, Jan 6, 2011 at 1:40 PM, Madovsky <infos at madovsky.org> wrote:
>> in case of you have 8 servers you have to do it for each ?
>> 
>> Thanks
>> 
>> ----- Original Message -----
>> From: joy this
>> To: FreeSWITCH Users Help
>> Sent: Thursday, January 06, 2011 2:51 AM
>> Subject: Re: [Freeswitch-users] mod_conference with cluster ODBC
>> It works. Thank you everyone.
>> 
>> 2011/1/5 Rupa Schomaker <rupa at rupa.com>
>>> 
>>> Use the api: conference <confname> dial [{dial string
>>> options}]<endpoint_module_name>/<destination> [<callerid_number>
>>> [<callerid_name>]]
>>> To initiate the call from within conference A on server 1. Have a
>>> corresponding dialplan entry on server 2 to accept the call and add
> it
>>> into
>>> the conference A on server 2. You've now bridged the two conferences
> in
>>> the
>>> two servers.
>> 
>> ________________________________
>> 
>> _______________________________________________
>> 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
>> 
>> --
>> This message has been scanned for viruses and
>> dangerous content by MailScanner, and is
>> believed to be clean.
>> _______________________________________________
>> 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
>> 
>> 
> 
> 
> 
>    --
>    -Rupa
> 
>    _______________________________________________
>    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
> 
> 
>    _______________________________________________
>    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
> 
> 
> 
> 
> 
> ------------------------------------------------------------------------------
> 
> 
>  _______________________________________________
>  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
> 
> 
> _______________________________________________
> 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
> 
> 
> 
> 
> 
> _______________________________________________
> 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



More information about the FreeSWITCH-users mailing list