there are acls for this yes. check out the ones that refer to nat<span></span><br><br>On Monday, November 2, 2015, Dan Edwards <<a href="mailto:DEdwards@vertical.com">DEdwards@vertical.com</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
<div style="direction:ltr;font-family:Tahoma;color:#000000;font-size:10pt">
<div style="direction:ltr;font-family:Tahoma;color:#000000;font-size:10pt">We're trying to build a system that allows WebSocket SIP traffic through an Nginx proxy to FreeSWITCH and I'm having trouble getting the proper IP address offered in the SDP.
<div><br>
</div>
<div>I added ext-rtp-ip and ext-sip-ip to the profile, but if I come in via the Nginx proxy, FS always offers the local address. I made some code changes to FS to catch the X-Forwarded-For header on the initial WebSocket connect, thinking I could substitute
the forwarded-for IP address for the Nginx address, but this did not correct the problem.</div>
<div><br>
</div>
<div>To be clear, if I run Nginx on 172.1.1.1 and FS on 172.1.1.2, when I come in via Nginx, FS sees the SIP IP as 172.1.1.1 and offers 172.1.1.2 as the RTP address. If I come in via a port-forward, FS offers what I have in 'ext-rtp-ip' as the IP address.</div>
<div><br>
</div>
<div>Is there a way to force FS to always offer ext-rtp-ip, even if the address is local or does this require a code change? If it requires a code change, where does this logic exist?</div>
<div><br>
</div>
<div>Thank you,</div>
<div>Dan</div>
<div><br>
</div>
<div><br>
</div>
</div>
</div>
</div>
</blockquote>