<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>Hello Maxim,<br>
</p>
given the discussion here, I would like to get some updates for
myself regarding 2.0 in terms of capacity and other stuff.<br>
<br>
I was using rtpproxy 1.x with kamailio doing load balancing across
many instances of rtpproxy. I was using 1000 streams as estimation
for one instance and I see it's what you mentioned as well. Is it
the recommended (or the good) value for 2.0? Most of deployments
still use v1.2, given it's presence in stable/old OS distros.<br>
<br>
It's any relevant architectural change in 2.0? Like more threads
used by the app or other I/O refactoring? Iirc, v1.x uses one for
control commands?<br>
<br>
I wanted to report at some point, with v1.x, on some centos (iirc),
when there was no active call, rtpproxy was eating a lot of cpu.
With a call (or more) going on, the cpu went to normal. I think it
was like waiting for I/O was using the cpu. Switching to debian was
a solution at that moment, so might not be rtpproxy, but I am
wondering if you or anyone else faced same issue. Also, if I am not
wrong, the person that reported to me said that 2.0 didn't revealed
the same behaviour.<br>
<br>
Cheers,<br>
Daniel<br>
<br>
<div class="moz-cite-prefix">On 19/10/16 09:46, Maxim Sobolev wrote:<br>
</div>
<blockquote
cite="mid:CAH7qZfs9jnmBeOaDAQDnniwHf8ozxPxueQN8h11Sx1p26BNxOg@mail.gmail.com"
type="cite">
<div dir="ltr">Alex, no problem. Nobody knows everything. :)
<div><br>
</div>
<div>-Max</div>
<div><br>
</div>
<div>On Wed, Oct 19, 2016 at 12:35 AM, Alex Balashov <span
dir="ltr"><<a moz-do-not-send="true"
href="mailto:abalashov@evaristesys.com" target="_blank">abalashov@evaristesys.com</a>></span>
wrote:
<div class="gmail_extra">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Hi
Maxim,<br>
<br>
Duly noted! I certainly did not intend to mislead anyone
or to be disingenuous; I gave information that was, to
the best of my knowledge, true. I appreciate your
followup and clarification, which certainly is useful
for my own knowledge as well!<br>
<br>
My sincere apologies...<br>
<br>
-- Alex<br>
<div>
<div class="h5"><br>
<br>
On October 19, 2016 3:32:24 AM EDT, Maxim Sobolev
<<a moz-do-not-send="true"
href="mailto:sobomax@sippysoft.com">sobomax@sippysoft.com</a>>
wrote:<br>
>Alex, with all due respect, things you said
about rtpproxy capacity is<br>
>somewhat outdated and misleading. We have some
nodes in the field, that<br>
>handle 5,000-6,000 rtp sessions in peak. Those
are running 6 rtpproxy<br>
>instances, 1,000 sessions each. 2-3 year old
CPUs, 12 cores in total.<br>
><br>
>We also have an open source solution called
rtp_cluster, which allows<br>
>building larger scale deployments, for at least
up to 50,000<br>
>bidirectional<br>
>streams using multiple nodes running rtpproxy.
Available here<br>
><a moz-do-not-send="true"
href="https://github.com/sippy/rtp_cluster"
rel="noreferrer" target="_blank">https://github.com/sippy/rtp_<wbr>cluster</a>.
You are also welcome to check our<br>
>talk last summer at the opensips devsummit in
Austin where we gave it<br>
>some<br>
>limelight.<br>
><br>
>So you are off by two orders of magnitude
roughly with regards to the<br>
>capacity. :)<br>
><br>
>And yes, we've been happily running large
deployments at AWS for at<br>
>least 6<br>
>years now.<br>
><br>
>Rodrigo, speaking about your original question,
I could not tell much<br>
>about<br>
>rtpengine due to a lack of practical experience
with it. But from what<br>
>I<br>
>read on its website it seems to be logical
continuation of the<br>
>mediaproxy<br>
>package packed with some cutting edge sexy
features.<br>
><br>
>In a nutshell rtpproxy and mediaproxy/rtpengine
are just two<br>
>independently<br>
>developed pieces of software, doing somewhat
similar function. What<br>
>would<br>
>work in your particular setting depends on your
requirements and<br>
>constraints.<br>
><br>
>Here at Sippy Labs we focus on stability,
compatibility and portability<br>
>for<br>
>a predominantly regular audio traffic.<br>
><br>
>We also have a test suite that check
compatibility of the latest<br>
>production<br>
>and development versions of the rtpproxy against
array of different SIP<br>
>engines, including Kamailio. <a
moz-do-not-send="true"
href="https://travis-ci.org/sippy/voiptests"
rel="noreferrer" target="_blank">https://travis-ci.org/sippy/<wbr>voiptests</a><br>
><br>
>So with rtpproxy you are not locked in into
single SIP engine, you can<br>
>mix<br>
>and match to fit your particular goal.<br>
><br>
>And yes, last but not least, all our code is BSD
licensed, so you can<br>
>build<br>
>you proprietary box that uses it.<br>
><br>
>Hope it helps.<br>
><br>
>-Max<br>
><br>
>On Oct 17, 2016 11:33 AM, "Alex Balashov" <<a
moz-do-not-send="true"
href="mailto:abalashov@evaristesys.com">abalashov@evaristesys.com</a>><br>
>wrote:<br>
><br>
>> On 10/17/2016 02:29 PM, Rodrigo Moreira
wrote:<br>
>><br>
>> What is difference between modules rtpproxy
and rtpengine?<br>
>>><br>
>><br>
>> rtpproxy is a userspace process which,
historically, has a relatively<br>
>> limited call throughput capacity (maybe a
few hundred calls), though<br>
>this<br>
>> might be addressed to some degree in
rtpproxy 2.0. Nevertheless, it<br>
>has<br>
>> been commonly used and well supported in
the *SER family for long<br>
>time.<br>
>><br>
>> RTPEngine is a newer initiative from
Sipwise, and uses kernel-mode<br>
>> forwarding to achieve close to on-the-wire
RTP forwarding speeds. It<br>
>can do<br>
>> 10,000+ concurrent bidirectional RTP
streams. It also has lots of<br>
>other<br>
>> features which can be useful in, for
example, running an RTP relay in<br>
>1:1<br>
>> NAT environments such as AWS, or in
enabling WebRTC.<br>
>><br>
>> However, it is a bit more complicated to
set up than vanilla<br>
>rtpproxy. Not<br>
>> much more, though.<br>
>><br>
>> -- Alex<br>
>><br>
>> --<br>
>> Alex Balashov | Principal | Evariste
Systems LLC<br>
>><br>
>> Tel: <a moz-do-not-send="true"
href="tel:%2B1-706-510-6800" value="+17065106800">+1-706-510-6800</a>
(direct) / <a moz-do-not-send="true"
href="tel:%2B1-800-250-5920" value="+18002505920">+1-800-250-5920</a>
(toll-free)<br>
>> Web: <a moz-do-not-send="true"
href="http://www.evaristesys.com/"
rel="noreferrer" target="_blank">http://www.evaristesys.com/</a>,
<a moz-do-not-send="true"
href="http://www.csrpswitch.com/" rel="noreferrer"
target="_blank">http://www.csrpswitch.com/</a><br>
>><br>
>> ______________________________<wbr>_________________<br>
>> SIP Express Router (SER) and Kamailio
(OpenSER) - sr-users mailing<br>
>list<br>
>> <a moz-do-not-send="true"
href="mailto:sr-users@lists.sip-router.org">sr-users@lists.sip-router.org</a><br>
>> <a moz-do-not-send="true"
href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users"
rel="noreferrer" target="_blank">http://lists.sip-router.org/<wbr>cgi-bin/mailman/listinfo/sr-<wbr>users</a><br>
>><br>
><br>
><br>
</div>
</div>
>-----------------------------<wbr>------------------------------<wbr>-------------<br>
<span class="">><br>
>_____________________________<wbr>__________________<br>
>SIP Express Router (SER) and Kamailio (OpenSER) -
sr-users mailing list<br>
><a moz-do-not-send="true"
href="mailto:sr-users@lists.sip-router.org">sr-users@lists.sip-router.org</a><br>
><a moz-do-not-send="true"
href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users"
rel="noreferrer" target="_blank">http://lists.sip-router.org/<wbr>cgi-bin/mailman/listinfo/sr-<wbr>users</a><br>
<br>
<br>
</span>-- Alex<br>
<br>
--<br>
Principal, Evariste Systems LLC (<a
moz-do-not-send="true"
href="http://www.evaristesys.com" rel="noreferrer"
target="_blank">www.evaristesys.com</a>)<br>
<br>
Sent from my Google Nexus.<br>
<div class="HOEnZb">
<div class="h5"><br>
<br>
______________________________<wbr>_________________<br>
SIP Express Router (SER) and Kamailio (OpenSER) -
sr-users mailing list<br>
<a moz-do-not-send="true"
href="mailto:sr-users@lists.sip-router.org">sr-users@lists.sip-router.org</a><br>
<a moz-do-not-send="true"
href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users"
rel="noreferrer" target="_blank">http://lists.sip-router.org/<wbr>cgi-bin/mailman/listinfo/sr-<wbr>users</a><br>
</div>
</div>
</blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
<div class="gmail_signature"
data-smartmail="gmail_signature">
<div dir="ltr">Maksym Sobolyev<br>
Sippy Software, Inc.<br>
Internet Telephony (VoIP) Experts<br>
Tel (Canada): +1-778-783-0474<br>
Tel (Toll-Free): +1-855-747-7779<br>
Fax: +1-866-857-6942<br>
Web: <a moz-do-not-send="true"
href="http://www.sippysoft.com" target="_blank">http://www.sippysoft.com</a><br>
MSN: <a moz-do-not-send="true"
href="mailto:sales@sippysoft.com" target="_blank">sales@sippysoft.com</a><br>
Skype: SippySoft<br>
</div>
</div>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:sr-users@lists.sip-router.org">sr-users@lists.sip-router.org</a>
<a class="moz-txt-link-freetext" href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Daniel-Constantin Mierla
<a class="moz-txt-link-freetext" href="http://twitter.com/#!/miconda">http://twitter.com/#!/miconda</a> - <a class="moz-txt-link-freetext" href="http://www.linkedin.com/in/miconda">http://www.linkedin.com/in/miconda</a>
Kamailio Advanced Training, Berlin, Oct 24-26, 2016 - <a class="moz-txt-link-freetext" href="http://www.asipto.com">http://www.asipto.com</a></pre>
</body>
</html>