<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix"><tt>Brett, you put the </tt><tt>finger
on the wound :)</tt><tt><br>
</tt><tt><br>
</tt><tt>I looked around to other alternatives (to avoid
re-inventing the wheel) - like mediaproxy or rtpengine - and I
saw no carrier-grade features in the there - please correct me
if I'm wrong.</tt><tt><br>
</tt><tt><br>
</tt><tt>I'm looking to see if the problem is correctly identified
and if there is a large consent in the community about this
need. As we would like to through some resources into this
(hopefully other parties too), as ideally we should be going in
the right direction </tt><tt>:)</tt><tt><br>
</tt><tt><br>
</tt><tt>Regards,</tt><br>
<pre class="moz-signature" cols="72">Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
<a class="moz-txt-link-freetext" href="http://www.opensips-solutions.com">http://www.opensips-solutions.com</a></pre>
On 27.05.2014 16:52, Brett Nemeroff wrote:<br>
</div>
<blockquote
cite="mid:CAPwC5wyxeRd02Wej24B6WpX5dOwCofmhaJj_D2bxT0v4uV0pUg@mail.gmail.com"
type="cite">
<div dir="ltr">Just wanted to add my 0.02 here..
<div><br>
</div>
<div>I totally agree with Bogdan. For the applications where
opensips + a RTP relay make sense, HA and persistence are much
more important. </div>
<div><br>
</div>
<div>WebRTC and ICE are kinda applications in of themselves. And
although these applications are going to grow in popularity,
the "legacy" needs for an RTP relay are still massively
prevalent in the space. A general push towards "Carrier
Grade", resiliency and redundancy I think is much better for
the project as a whole. </div>
<div><br>
</div>
<div>Not only that, consider that applications requiring ICE or
WebRTC will greatly benefit from HA / persistence, but not so
much the other way around :) </div>
<div><br>
</div>
<div>YMMV</div>
<div><br>
</div>
<div>-Brett</div>
<div><br>
</div>
</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Sun, May 25, 2014 at 6:30 AM,
Bogdan-Andrei Iancu <span dir="ltr"><<a
moz-do-not-send="true" 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">
<div bgcolor="#FFFFFF" text="#000000">
<div><tt>Hello,<br>
<br>
As always, the truth is in the middle.<br>
<br>
I agree RTPP is behind on certain things (and this is
why we want to do them), but on the other hand it is a
good platform with other good features (missing on the
other relays). RTPP has better ability in individually
controlling the stream (audio /video), ability to set
timeouts and onhold with no conflicts, ability to
generates events on timeout, more flexibility in
handling symmetric / asymmetric NATs, ability to do
media injection (playback), ability to do call
recording<br>
<br>
What neither mediaproxy, nor rtpengine have is a
mechanism for implementing RTP failover (for ongoing
calls) or restart persistence . This is something we
want to look into. I would love to have ICE and WebRTC
on my media relay, for the HA and persistence are more
important I would say.<br>
<br>
Regards,<br>
</tt>
<div class="">
<pre cols="72">Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
<a moz-do-not-send="true" href="http://www.opensips-solutions.com" target="_blank">http://www.opensips-solutions.com</a></pre>
</div>
<div>
<div class="h5"> On <a moz-do-not-send="true"
href="tel:24.05.2014%2001" value="+12405201401"
target="_blank">24.05.2014 01</a>:59, Muhammad
Shahzad Shafi wrote:<br>
</div>
</div>
</div>
<blockquote type="cite">
<div>
<div class="h5">
<p>To be honest, i have stopped using rtpproxy for
over 2 years now. It is not evolving as fast as it
should be, specially in the context of ICE and
WebRTC technologies.</p>
<p>I would like to suggest that opensips team should
consider adding support for rtpengine from
SIPWise,</p>
<p><a moz-do-not-send="true"
href="https://github.com/sipwise/rtpengine"
target="_blank">https://github.com/sipwise/rtpengine</a></p>
<p>For now mediaproxy from AG Projects is the only
good choice for handling media in opensips with
ICE support (though it still lacks WebRTC
features).</p>
<p>Thank you.</p>
<p> </p>
<p>On 2014-05-23 14:55, Bogdan-Andrei Iancu wrote:</p>
<blockquote type="cite"
style="padding-left:5px;border-left:#1010ff 2px
solid;margin-left:5px;width:100%"><tt>Going for a
public exposure on this question to Maxim, maybe
we will get an answer here.<br>
<br>
</tt>
<div><br>
-------- Original Message --------
<table border="0" cellpadding="0"
cellspacing="0">
<tbody>
<tr>
<th align="RIGHT" nowrap="nowrap"
valign="BASELINE">Subject:</th>
<td>RTPproxy project</td>
</tr>
<tr>
<th align="RIGHT" nowrap="nowrap"
valign="BASELINE">Date:</th>
<td>Mon, 14 Apr 2014 15:03:31 +0300</td>
</tr>
<tr>
<th align="RIGHT" nowrap="nowrap"
valign="BASELINE">From:</th>
<td>Bogdan-Andrei Iancu</td>
</tr>
<tr>
<th align="RIGHT" nowrap="nowrap"
valign="BASELINE">To:</th>
<td>Maxim Sobolev</td>
</tr>
<tr>
<th align="RIGHT" nowrap="nowrap"
valign="BASELINE">CC:</th>
<td>Razvan Crainea</td>
</tr>
</tbody>
</table>
<br>
<br>
<pre>Hello Maxim,
Long time, no talks, but I hope everything is fine on your side.
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.
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).
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.
Best regards,
--
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
<a moz-do-not-send="true" href="http://www.opensips-solutions.com" target="_blank">http://www.opensips-solutions.com</a>
</pre>
</div>
</blockquote>
<div>
<pre>--
Mit freundlichen Grüßen
Muhammad Shahzad
-----------------------------------
CISCO Rich Media Communication Specialist (CRMCS)
CISCO Certified Network Associate (CCNA)
Cell: <a moz-do-not-send="true" href="tel:%2B49%20176%2099%2083%2010%2085" value="+4917699831085" target="_blank">+49 176 99 83 10 85</a>
MSN: <a moz-do-not-send="true" href="mailto:shari_786pk@hotmail.com" target="_blank">shari_786pk@hotmail.com</a>
Email: <a moz-do-not-send="true" href="mailto:shaheryarkh@googlemail.com" target="_blank">shaheryarkh@googlemail.com</a></pre>
</div>
<br>
<fieldset></fieldset>
<br>
</div>
</div>
<pre>_______________________________________________
Users mailing list
<a moz-do-not-send="true" href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a>
<a moz-do-not-send="true" href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a>
</pre>
</blockquote>
<br>
</div>
<br>
_______________________________________________<br>
Users mailing list<br>
<a moz-do-not-send="true"
href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br>
<a moz-do-not-send="true"
href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users"
target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
<br>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a>
<a class="moz-txt-link-freetext" href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a>
</pre>
</blockquote>
<br>
</body>
</html>