<div dir="ltr">Hi Guys,<div><br></div><div>Some updates on the rtpproxy project;</div><div><br></div><div>We have now moved the rtpproxy project from sourceforge to github <a href="http://github.com/sippy/rtpproxy">http://github.com/sippy/rtpproxy</a></div>
<div><br></div><div>This change should make the project more visibility & and transparency. Please feel free to create Issues for feature requests and bugs, and of course Pull Requests are appreciated! :)</div><div><br>
</div><div>We have also moved the mailing list over to Google Groups: <a href="https://groups.google.com/forum/#!forum/rtpproxy">https://groups.google.com/forum/#!forum/rtpproxy</a> </div><div><br></div><div>We will do a maintenance release - version 1.3, and Max is busy working on a 2.0 release, which has some significant improvements to jitter characteristics, and performance.</div>
<div><br></div><div>Best Regards,</div><div>-Jev</div><div><br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Jun 9, 2014 at 8:25 AM, Maxim Sobolev <span dir="ltr"><<a href="mailto:sobomax@sippysoft.com" target="_blank">sobomax@sippysoft.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><div>Hey Bogdan, sorry for missing your message. The mail traffic these days is insane, so it's hard to keep atop of all issues. <br>
<br></div>We are working behind the scene on what would become rtpproxy 2.0, the code is pretty stable and we have it deployed in like 30-40 places. The main changes are in the timing loop, which improves the jitter significantly and recently we've also split UDP sending code into its own thread(s). That code is available here: <a href="https://bitbucket.org/sippysoft/rtpproxy" target="_blank">https://bitbucket.org/sippysoft/rtpproxy</a>. It's only tested to compile on FreeBSD, but it should not be difficult to compile it on Linux. This basically pushes it to the limits of what's possible to achieve with the standard POSIX facilities. We've been able to push 16-core machine up to 400KPPS in and 400KPPS out with it, all the way up to 90% CPU, while the older version started choking at about 30%. Our plan is to tie few loose ends and push it out to the official repo as a basis for 2.0. <br>
<br></div>Beyond 2.0, there is another project in progress that is using novel netmap framework to overcome performance issues of the traditional kernel-based socket API. This potentially would allow us to increase capacity at least 5 times on the comparable hardware. The framework itself is pretty low-level, so I am working on a library that would allow it to be more easily integrated into an app. The WiP code is here. <a href="https://bitbucket.org/sobomax/libsinet" target="_blank">https://bitbucket.org/sobomax/libsinet</a>. <br>
<br></div>Another direction that we are going to explore is to add transcoding support. We have 2 cards in our lab now and setting up the devtesting system just today. I've heard that you have done some work in this direction, so if you want to share something with us, we would be very interested to look at those patches.<br>
<br></div><div>On the open-source side we plan to move the project into some modern project management facility, the favorite being github. My colleague Jev is driving this change.<br><br></div>In general I don't mind giving you or anyone else from the OpenSIPS team read-write access to repository if you feel like integrating some of your patches.<br>
<div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Apr 14, 2014 at 5:03 AM, Bogdan-Andrei Iancu <span dir="ltr"><<a href="mailto:bogdan@opensips.org" target="_blank">bogdan@opensips.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello Maxim,<br>
<br>
Long time, no talks, but I hope everything is fine on your side.<br>
<br>
I'm reaching you in order to ask about your future plans in regards to the rtpproxy project? We see no much activity around it and other media relays are popping around.<br>
<br>
RTPP is an essential component for us, we invested a lot of work, we have many patches (extensions) for it (which we want to push to the public tree, but there is no answer on this) and we are also looking for investing a lot into big future plans (as adding more functionalities).<br>
<br>
Now, my question is - what is your commitment and disponibility for the RTPP project ? depending on that we what to re-position ourselves, as we do not want to waste time and work on things which are out of control.<br>
<br>
Best regards,<span class="HOEnZb"><font color="#888888"><span><font color="#888888"><br>
<br>
-- <br>
Bogdan-Andrei Iancu<br>
OpenSIPS Founder and Developer<br>
<a href="http://www.opensips-solutions.com" target="_blank">http://www.opensips-solutions.<u></u>com</a><br>
<br>
</font></span></font></span></blockquote></div><span class="HOEnZb"><font color="#888888"><br><br clear="all"><br>-- <br><div dir="ltr">Maksym Sobolyev<br>Sippy Software, Inc.<br>Internet Telephony (VoIP) Experts<br>Tel (Canada): <a href="tel:%2B1-778-783-0474" value="+17787830474" target="_blank">+1-778-783-0474</a><br>
Tel (Toll-Free): <a href="tel:%2B1-855-747-7779" value="+18557477779" target="_blank">+1-855-747-7779</a><br>
Fax: <a href="tel:%2B1-866-857-6942" value="+18668576942" target="_blank">+1-866-857-6942</a><br>Web: <a href="http://www.sippysoft.com" target="_blank">http://www.sippysoft.com</a><br>MSN: <a href="mailto:sales@sippysoft.com" target="_blank">sales@sippysoft.com</a><br>
Skype: SippySoft<br></div>
</font></span></div></div>
</blockquote></div><br></div></div>