<div dir="ltr">Bogdan, about 10 days ago the mediaproxy-ng project was renamed into rtpengine. What about to add new module with this name? As for me, I'd like to use rtpengine for a long time, but I've never had a module. And I'm unhappy that we will have this module only in trunk, but not in 1.11.<br>
<div class="gmail_extra"><br clear="all"><div>--<br>Nick</div>
<br><br><div class="gmail_quote">2014-02-21 19:33 GMT+04:00 Bogdan Andrei IANCU <span dir="ltr"><<a href="mailto:notifications@github.com" target="_blank">notifications@github.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="HOEnZb"><div class="h5"><p><a href="https://github.com/lemenkov" target="_blank">@lemenkov</a> thanks for the update...I'm a but confused and puzzled. .....The media engine from sipwise is called mediaproxy-ng, but has noting to do to with mediaproxy from AG-projects (not even a fork) - how comes this ???<br>
Further more, why to name the module in OpenSIPS rtpproxy-ng, while it has nothing to do with the RTPproxy media relay ??</p>
<p>It is a lot of confusion and IMHO we should try to clear it up before considering any code.</p>
<p>Regards,<br>
Bogdan</p>
<p style="font-size:small;color:#666">—<br>Reply to this email directly or <a href="https://github.com/OpenSIPS/opensips/pull/152#issuecomment-35740773" target="_blank">view it on GitHub</a>.<img src="https://github.com/notifications/beacon/5479561__eyJzY29wZSI6Ik5ld3NpZXM6QmVhY29uIiwiZXhwaXJlcyI6MTcwODUyOTYxMCwiZGF0YSI6eyJpZCI6MjI0MzY3NDV9fQ==--a3172c8d58423220683a1ce9261921ded2c32c89.gif" height="1" width="1"></p>
</div></div><br>_______________________________________________<br>
Devel mailing list<br>
<a href="mailto:Devel@lists.opensips.org">Devel@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/devel" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/devel</a><br>
<br></blockquote></div><br></div></div>