<div dir="auto"><div>Yes, for sure. As long as the transport is UDP based, the RTPProxy would just work. The change should be trivial, you can get it fixed locally, test and then open a pull request against opensips repo.<div dir="auto"><br></div><div dir="auto">-Max</div><br><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu., Apr. 2, 2020, 11:43 a.m. Robert Dyck, <<a href="mailto:rob.dyck@telus.net">rob.dyck@telus.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><u></u>
<div style="font-family:'Sans Serif';font-size:10pt;font-weight:400;font-style:normal">
<p style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px">Regarding opensips-3.0</p>
<p style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px">Use case - webrtc client behind NAT</p>
<p style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px"> </p>
<p style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px">The rtpproxy module emitted the error message "<span style="font-family:'monospace';color:#000000;background-color:#ffffff">can't extract media port from the message" ( by the way, very misleading ). In reality extract_mediainfo fails because it could not find a supported payload type in the media description. The payload type in question is "UDP/TLS/RTP/SAVPF".</span></p>
<p style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px"> </p>
<p style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px"><span style="font-family:'monospace';color:#000000;background-color:#ffffff">RFC 5764 section 8 introduces four more RTP types.</span></p>
<p style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px"><span style="font-family:'monospace';color:#000000;background-color:#ffffff">DCCP/TLS/RTP/SAVP and SAVPF</span></p>
<p style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px"><span style="font-family:'monospace';color:#000000;background-color:#ffffff">UDP/TLS/RTP/SAVP and SAVPF</span></p>
<p style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px"> </p>
<p style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px"><span style="font-family:'monospace';color:#000000;background-color:#ffffff">Should rtpproxy.c be extended to support these additional RTP types?</span></p>
<p style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px"> </p>
<p style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px"><span style="font-family:'monospace';color:#000000;background-color:#ffffff">Thank you, Rob</span></p></div>_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org" target="_blank" rel="noreferrer">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" rel="noreferrer noreferrer" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
</blockquote></div></div></div>