[OpenSIPS-Users] RTPproxy weight question

[Bogdan-Andrei Iancu]

Hi Nick,

Do not use weights 0, but something not zero, as this will affect the 
weight sum (when doing the selection).

Try replacing the weights with 10, let's say.

Regards,

Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com


On 12/05/2012 10:10 AM, Nick Altmann wrote:
> My configuration:
> modparam("rtpproxy", "rtpproxy_sock", "1 == udp:1.1.1.1:22222=0 
> udp:2.2.2.2:22222=0 udp:3.3.3.3:22222=0 udp:4.4.4.4:22222=0")
>
> Why used only first rtpproxy from set?
>
> My configs generated from m4 and may be minimum like this:
> modparam("rtpproxy", "rtpproxy_sock", "1 == udp:1.1.1.1:22222=0 
> udp:2.2.2.2:22222=0 udp:3.3.3.3:22222=0 udp:4.4.4.4:22222=0")
>
> and maximum like this:
> modparam("rtpproxy", "rtpproxy_sock", "1 == udp:1.1.1.1:22222=0 
> udp:2.2.2.2:22222=0 udp:3.3.3.3:22222=0 udp:4.4.4.4:22222=0")
> modparam("rtpproxy", "rtpproxy_sock", "2 
> == udp:a.a.a.a:22222=1 udp:b.b.b.b:22222=1 udp:1.1.1.1:22222=0 
> udp:2.2.2.2:22222=0 udp:3.3.3.3:22222=0 udp:4.4.4.4:22222=0")
> modparam("rtpproxy", "rtpproxy_sock", "3 
> == udp:c.c.c.c:22222=1 udp:d.d.d.d:22222=1 udp:1.1.1.1:22222=0 
> udp:2.2.2.2:22222=0 udp:3.3.3.3:22222=0 udp:4.4.4.4:22222=0")
>
>
> Expected behavior:
> When set for set number 3 (for example):
> Balance between c.c.c.c and d.d.d.d, if they are not available, 
> balance between 1.1.1.1, 2.2.2.2, 3.3.3.3, 4.4.4.4.
> For set number 1 - only balance between 1.1.1.1, 2.2.2.2, 3.3.3.3, 
> 4.4.4.4.
>
> How can I configure it to work as expected?
>
> --
> Nick
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20121205/cf20facd/attachment.htm>