<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
I am using multi-core processors (who isn't) and want to get the most out of opensips + rtpproxy running on the same server.
<div class=""><br class="">
</div>
<div class="">According to opensips docs I can tell opensips to load balance between two instances of rtpproxy on the same machine, controlled through different UDP sockets:</div>
<div class=""><br class="">
</div>
<div class="">(From <a href="http://www.opensips.org/html/docs/modules/2.2.x/rtpproxy.html" class="">http://www.opensips.org/html/docs/modules/2.2.x/rtpproxy.html</a>)</div>
<div class=""><br class="">
</div>
<div class="">
<div class=""># multiple rtproxies for LB</div>
<div class="">modparam("rtpproxy", "rtpproxy_sock",</div>
<div class=""><span class="Apple-tab-span" style="white-space:pre"></span>"udp:localhost:12221 udp:localhost:12222")</div>
</div>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
<div class="">Using rtpproxy 2.0 it looks like I should have two cores per rtpproxy. Is it enough then to set up (CORES / 2) instances of rtpproxy, each with the same parameters on the server but different control sockets, and then tell opensips about them
using the rtpproxy load balance syntax shown above?</div>
<div class=""><br class="">
</div>
<div class="">Do they need to be assigned different RTP ranges, IP addresses or anything like that? I have set up a test box as I just described but cannot tell whether I will have resource conflicts under load.</div>
<br>
<br>
“The information transmitted is intended only for the person or entity to which it is addressed and may contain proprietary, business-confidential and/or privileged material. If you are not the intended recipient of this message you are hereby notified that
any use, review, retransmission, dissemination, distribution, reproduction or any action taken in reliance upon this message is prohibited. If you received this in error, please contact the sender and delete the material from any computer.”
</body>
</html>