[Spce-user] RTPEngine Bridge feature on mr3.5.1

[Raúl Alexis Betancor Santana]

So, as I spoted ... it's not supported on the templates.

Why you said that cluster_set's are useless fo spce? ... as far as I looked at the templates (doing testing with them now), if I set a cluster_set of rtp-proxies at domain level for the customers (or use the default set) ... and also set another set for specific peer, that's on the private network, then when that peer get selected to route the call, customer will send rtp to the standar cluster-set rtp proxy, and peer to the specific one ... so giving the feature of rtp-bridge to the front  ... not by using the same rtp-proxy and it's direction directives ... but with the same effect.

The problem is that lot of options that appears on spce are not documented, and it's hard to be testing on blind ... without knowing what it's supposed to do a feature.

Either way ... I'm doing the test of the cluster_set features ... and if not enough, will go on with implementing the bridge features, and of course will release the changes to the community.

Best regards.

----- Mensaje original -----
De: "Alex Lutay" <alutay at sipwise.com>
Para: spce-user at lists.sipwise.com
Enviados: Lunes, 10 de Noviembre 2014 8:50:05
Asunto: Re: [Spce-user] RTPEngine Bridge feature on mr3.5.1

Dear Raúl,

The first your question has been addressed here:
https://lists.sipwise.com/pipermail/spce-user/2014-October/007439.html
In short: at the moment RTPEngine supports bridging while SPCE has no
built-in bridging support.

Regarding "cluster set configuration" it was designed for having RTP
server(s) outside lb/proxy server(s), it is necessary for Carrier 3.x
installations. You can find the section "cluster_set" in config.yml
(while it is almost useless for community edition (SPCE)).

Feel free to add bridging support yourself and share your solution with
other SPCE users. It is a benefits of open sources solutions!

New features development for mr3.6.1 has been closed already.
Bridging support on templates level was not included while
it still may be added in upcoming releases.

mr3.6 mainly focused on system cleanup before the next LTS release
(which is going soon). So, Apache2 is not necessary on SPCE anymore,
everything moved to Nginx. And more...
Stay tuned, mr3.6.1 will be released soon ;-)

On 09/11/14 22:26, Raúl Alexis Betancor Santana wrote:
> Found "lbrtp_set	The cluster set used for SIP lb and RTP" on the peer host page ... but where to create the sets ?
>
> I suppose this should be a lb+rtp set of servers for this particular peer ... as the help said, but don't find where to define them.
...
>
> Doing more testing on the mr3.5.1, saw that rtpengine now have support for what it's called 'bridge' feature, one of the most interested features that this new version give us is to use 'logical' rtp interfaces names, but as far as I see ... the mr3.5.1 templates does not use this feature.
>
> If we define an extra_socket on the config.xml to let the LB listen/reply on other interfaces more than sip_ext ... if you use that on the peering servers for forcing an outbound socket, the RTP continues to be the sip_ext ip ... could be usefull if we are been able to set also the logical rtp interface name on the  peering server page, along with the outbound socket.
>
> Is this feature planed for 3.6? ... or may I missed something and it's implemented on mr3.5.1 and this could be done other way?

-- 
Alexander Lutay
Head of Quality Assurance
Sipwise GmbH, Campus 21/Europaring F15
AT-2345 Brunn am Gebirge

Office: +43(0)13012036
Email: alutay at sipwise.com
Website: http://www.sipwise.com

Meet us @ AFRICACOM : Booth A17/A18
11-13 November 2014 : CTICC Cape Town, South Africa
_______________________________________________
Spce-user mailing list
Spce-user at lists.sipwise.com
https://lists.sipwise.com/listinfo/spce-user