<html>
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<tt>Hi William,<br>
<br>
IF you end up chaining multiple RTPproxy'es, you need to be sure
you avoid the "learning" deadlock between them - as rtpproxy is
normally waiting to receive RTP in order to learn the end-points
IP+port (as the IP coordinates from SDP are private, so not
usable). So, if the IP in the received SDP in public, use the "r"
flag when triggering rtpproxy (not to wait, but to trust the
IP+port in SDP) - see
<a class="moz-txt-link-freetext" href="http://www.opensips.org/html/docs/modules/2.3.x/rtpproxy.html#idp5556688">http://www.opensips.org/html/docs/modules/2.3.x/rtpproxy.html#idp5556688</a><br>
<br>
Best regards,<br>
</tt>
<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>
OpenSIPS Summit 2018
<a class="moz-txt-link-freetext" href="http://www.opensips.org/events/Summit-2018Amsterdam">http://www.opensips.org/events/Summit-2018Amsterdam</a>
</pre>
<div class="moz-cite-prefix">On 01/12/2018 08:48 PM, William Simon
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:24168CC2-E066-4A7E-B1C4-861A7BF6F9A9@stratusvideo.com">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
I have a provider that is reflecting the a=nortpproxy:yes
attribute back to me in the SDP of its reply. I know it's being
reflected back because when I customize that header using the
nortpproxy_str setting, I get my own value back in the provider's
replies.
<div class=""><br class="">
</div>
<div class="">The result is that the answer side of rtpproxy isn't
engaged and there's no audio.</div>
<div class=""><br class="">
</div>
<div class="">From an old thread (<a
href="http://lists.opensips.org/pipermail/users/2012-November/023444.html"
class="" moz-do-not-send="true">http://lists.opensips.org/pipermail/users/2012-November/023444.html</a>)
it seems like the best option for me is to simply disable this
a=nortpproxy:yes attribute and let the opensips logic engage
rtpproxy all the time.</div>
<div class=""><br class="">
</div>
<div class="">What kind of negative side effects would I face by
disabling this and letting rtpproxy engage every time? Is this
flag only really useful when you are working with a hierarchy of
SIP proxies in your own environment? My topology has two
equal-priority equal-weight opensips proxies that serve as
clustered load balancer as well as outbound-proxy for internal
freeswitch servers.</div>
<div class=""><br class="">
</div>
<div class="">Thanks</div>
<div class="">W Simon</div>
<br>
<br>
“The information transmitted is intended only for the person or
entity to which it is addressed and may contain proprietary,
business-confidential and/or privileged material. If you are not
the intended recipient of this message you are hereby notified
that any use, review, retransmission, dissemination, distribution,
reproduction or any action taken in reliance upon this message is
prohibited. If you received this in error, please contact the
sender and delete the material from any computer.”
<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>