<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Call it fuchs-relay, sipwise-relay or anything else but rtpproxy and mediaproxy as they have nothing to do with any of them.<div><br></div><div>Adrian</div><div><br><div><br><div><div>Pe 22.02.2014, la 12:13, Richard Fuchs <<a href="mailto:notifications@github.com">notifications@github.com</a>> a scris:</div><br class="Apple-interchange-newline"><blockquote type="cite"><p>Correct, the protocol is different and incompatible, but heavily based on the original rtpproxy protocol in terms of functionality. The protocol offers all the same flags that the original rtpproxy protocol supported, just transported in a different way to allow it to be extended freely. Also, at least in the original rtpproxy-ng module, the function interface is completely identical to the rtpproxy module.</p><p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br>Reply to this email directly or <a href="https://github.com/OpenSIPS/opensips/pull/152#issuecomment-35803475">view it on GitHub</a>.<img src="https://github.com/notifications/beacon/5479561__eyJzY29wZSI6Ik5ld3NpZXM6QmVhY29uIiwiZXhwaXJlcyI6MTcwODYxMTIyOCwiZGF0YSI6eyJpZCI6MjI0MzY3NDV9fQ==--8498a7d4d8153fafa01c1b4cfcb16d39f1f48556.gif" height="1" width="1"></p>_______________________________________________<br>Devel mailing list<br><a href="mailto:Devel@lists.opensips.org">Devel@lists.opensips.org</a><br>http://lists.opensips.org/cgi-bin/mailman/listinfo/devel<br></blockquote></div><br></div></div></body></html>