[Freeswitch-users] mod_conference with cluster ODBC

[Peter Olsson]

Yes,

Since there is only one voice channel between the servers, if you relate to that channel, everything from the other server will follow.

/Peter


-----Ursprungligt meddelande-----
Från: freeswitch-users-bounces at lists.freeswitch.org [mailto:freeswitch-users-bounces at lists.freeswitch.org] För Steven Ayre
Skickat: den 5 januari 2011 16:27
Till: FreeSWITCH Users Help
Ämne: Re: [Freeswitch-users] mod_conference with cluster ODBC

Out of interest rupa, how are conference commands such as relate
implemented during a conf-conf bridge? For instance when specifying
member A on FS1 should be heard by member B on FS2 but not by member C
on FS2? I'm guessing it's only possible on the same server, not across
a cluster?

-Steve


On 5 January 2011 15:20, Rupa Schomaker <rupa at rupa.com> wrote:
> 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.
> On Wed, Jan 5, 2011 at 2:15 AM, joy this <thisjoy0528 at gmail.com> wrote:
>>
>> Would you please explain how to bridge two conference in different servers
>> together? I tried the uuid_bridge and uuid_transfer, but it doesn't work. I
>> could only use "originate sofia/gateway/gateway_name/extension" to bridge,
>> but I don't want the dailing appear.
>>
>> Beside, I want to know that how to bridge two conference in the same
>> server together. I could use "conference cof_name transfer" to bridge, but
>> when I bridge the members in conference B to conference A, the conference B
>> will be destroyed. So I can not transfer the original conference B members
>> back.
>>
>> Sincerely yours,
>> thisjoy.
>>
>> 2011/1/4 João Mesquita <jmesquita at freeswitch.org>
>>>
>>> They are indeed 2 completely different conferences. There's no
>>> implementation of making these 2 conferences bridge themselves
>>> automatically.
>>> The way I have solved this problem for now is have an ESL daemon
>>> "listening" on the conference creation events and bridging the 2 servers
>>> together when the one with the same name on the same domain is created. This
>>> solution might work for you and it's no too hard to implement.
>>> Regards,
>>> João Mesquita
>>
>>
>> _______________________________________________
>> 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

!DSPAM:4d248eeb32762038977453!