I&#39;m sure that Raul had a good point that I&#39;m crazy for doing this, but right now unfortunately I do not have a lot of options, and believe with some solid logic in the config can resolve this issue.  Right now I appear to be having an ACK come back from a 200 that turns into an endless loop.  I&#39;m using <br>
<br>advertised_address=&quot;75.101.136.125&quot;<br><br><br><br>U <a href="http://10.250.7.164:5060">10.250.7.164:5060</a> -&gt; <a href="http://76.102.118.209:3724">76.102.118.209:3724</a><br>SIP/2.0 200 OK.<br>Via: SIP/2.0/UDP 192.168.1.102:3724;received=76.102.118.209;branch=z9hG4bK-d8754z-ff34ad60b13c376a-1---d8754z-;rport=3724.<br>
Call-ID: NTU3NTE3NmZiNjVkNGYzNWEzYWVhZWQ4MjhhYjczN2E..<br>CSeq: 2 INVITE.<br>Contact: &lt;<a href="http://sip:2001@76.102.118.209:11386">sip:2001@76.102.118.209:11386</a>&gt;.<br>From: &quot;Daniel Goepp&quot; &lt;<a href="mailto:sip%3A1001@vidtel.com">sip:1001@vidtel.com</a>&gt;;tag=ac7fa632.<br>
To: &quot;2001&quot; &lt;<a href="mailto:sip%3A2001@vidtel.com">sip:2001@vidtel.com</a>&gt;;tag=8f7b7e78f8cb0eca.<br>Record-Route: &lt;sip:75.101.136.125;lr=on&gt;.<br>Allow: INVITE,ACK,CANCEL,BYE,UPDATE,INFO,OPTIONS,REFER,NOTIFY.<br>
Server: TANDBERG/257 (TE2.0.0.191892).<br>Supported: replaces,100rel,timer,gruu,path,outbound,com.tandberg.sdp.extensions.v1.<br>Session-Expires: 500; refresher=uas.<br>Min-SE: 90.<br>Content-Type: application/sdp.<br>Content-Length: 217.<br>
.<br>v=0.<br>o=tandberg 103 1 IN IP4 192.168.1.101.<br>s=-.<br>c=IN IP4 192.168.1.101.<br>b=CT:64.<br>t=0 0.<br>m=audio 2330 RTP/AVP 0 101.<br>b=TIAS:64000.<br>a=rtpmap:0 PCMU/8000.<br>a=rtpmap:101 telephone-event/8000.<br>
a=fmtp:101 0-15.<br>a=sendrecv.<br><br><br>U <a href="http://76.102.118.209:3724">76.102.118.209:3724</a> -&gt; <a href="http://10.250.7.164:5060">10.250.7.164:5060</a><br>ACK <a href="http://sip:2001@76.102.118.209:11386">sip:2001@76.102.118.209:11386</a> SIP/2.0.<br>
Via: SIP/2.0/UDP 192.168.1.102:3724;branch=z9hG4bK-d8754z-6d520059c54f5b74-1---d8754z-;rport.<br>Max-Forwards: 70.<br>Route: &lt;sip:75.101.136.125;lr&gt;.<br>Contact: &lt;<a href="http://sip:1001@192.168.1.102:3724">sip:1001@192.168.1.102:3724</a>&gt;.<br>
To: &quot;2001&quot;&lt;<a href="mailto:sip%3A2001@vidtel.com">sip:2001@vidtel.com</a>&gt;;tag=8f7b7e78f8cb0eca.<br>From: &quot;Daniel Goepp&quot;&lt;<a href="mailto:sip%3A1001@vidtel.com">sip:1001@vidtel.com</a>&gt;;tag=ac7fa632.<br>
Call-ID: NTU3NTE3NmZiNjVkNGYzNWEzYWVhZWQ4MjhhYjczN2E..<br>CSeq: 2 ACK.<br>Proxy-Authorization: Digest username=&quot;1001&quot;,realm=&quot;<a href="http://vidtel.com">vidtel.com</a>&quot;,nonce=&quot;4ad65ba02105a03bfdc0e3839160a42b5e1d90ac&quot;,uri=&quot;<a href="mailto:sip%3A2001@vidtel.com">sip:2001@vidtel.com</a>&quot;,response=&quot;0eea648b121320214ab8ec908eb97446&quot;,algorithm=MD5.<br>
User-Agent: eyeBeam release 1104g stamp 54685.<br>Content-Length: 0.<br>.<br><br><br>U <a href="http://10.250.7.164:5060">10.250.7.164:5060</a> -&gt; <a href="http://75.101.136.125:5060">75.101.136.125:5060</a><br>ACK <a href="http://sip:2001@76.102.118.209:11386">sip:2001@76.102.118.209:11386</a> SIP/2.0.<br>
Via: SIP/2.0/UDP 75.101.136.125;branch=z9hG4bK3128.7db9df05.2.<br>Via: SIP/2.0/UDP 192.168.1.102:3724;received=76.102.118.209;branch=z9hG4bK-d8754z-6d520059c54f5b74-1---d8754z-;rport=3724.<br>Max-Forwards: 69.<br>Route: &lt;sip:75.101.136.125;lr&gt;.<br>
Contact: &lt;<a href="http://sip:1001@192.168.1.102:3724">sip:1001@192.168.1.102:3724</a>&gt;.<br>To: &quot;2001&quot;&lt;<a href="mailto:sip%3A2001@vidtel.com">sip:2001@vidtel.com</a>&gt;;tag=8f7b7e78f8cb0eca.<br>From: &quot;Daniel Goepp&quot;&lt;<a href="mailto:sip%3A1001@vidtel.com">sip:1001@vidtel.com</a>&gt;;tag=ac7fa632.<br>
Call-ID: NTU3NTE3NmZiNjVkNGYzNWEzYWVhZWQ4MjhhYjczN2E..<br>CSeq: 2 ACK.<br>Proxy-Authorization: Digest username=&quot;1001&quot;,realm=&quot;<a href="http://vidtel.com">vidtel.com</a>&quot;,nonce=&quot;4ad65ba02105a03bfdc0e3839160a42b5e1d90ac&quot;,uri=&quot;<a href="mailto:sip%3A2001@vidtel.com">sip:2001@vidtel.com</a>&quot;,response=&quot;0eea648b121320214ab8ec908eb97446&quot;,algorithm=MD5.<br>
User-Agent: eyeBeam release 1104g stamp 54685.<br>Content-Length: 0.<br>.<br><br>-dg<br>
<br><br><div class="gmail_quote">On Wed, Oct 7, 2009 at 11:20 PM, Bogdan-Andrei Iancu <span dir="ltr">&lt;<a href="mailto:bogdan@voice-system.ro">bogdan@voice-system.ro</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi Daniel,<br>
<br>
Try using set_advertised_address() before sending the call out.<br>
      <a href="http://www.opensips.org/Resources/DocsCoreFcn#toc125" target="_blank">http://www.opensips.org/Resources/DocsCoreFcn#toc125</a><br>
<br>
or use the record_route_preset() function :<br>
     <a href="http://www.opensips.org/html/docs/modules/devel/rr.html#id228590" target="_blank">http://www.opensips.org/html/docs/modules/devel/rr.html#id228590</a><br>
<div><div></div><div class="h5"><br>
Regards,<br>
Bogdan<br>
<br>
Daniel Goepp wrote:<br>
&gt; After further investigation, this only updating the Via header, but<br>
&gt; the RR is remaining untouched:<br>
&gt;<br>
&gt; Record-Route: &lt;sip:10.250.7.164;lr=on&gt;<br>
&gt;<br>
&gt; Ideas about how I might get this field updated correctly?<br>
&gt;<br>
&gt; Thanks<br>
&gt;<br>
&gt; -dg<br>
&gt;<br>
&gt; On Wed, Oct 7, 2009 at 2:10 PM, Bogdan-Andrei Iancu<br>
&gt; &lt;<a href="mailto:bogdan@voice-system.ro">bogdan@voice-system.ro</a>&gt; wrote:<br>
&gt;<br>
&gt;&gt; Hi Daniel,<br>
&gt;&gt;<br>
&gt;&gt; try using the advertise_address and advertise_port to force opensips in<br>
&gt;&gt; using the public IPs of the NAT:<br>
&gt;&gt;    <a href="http://www.opensips.org/Resources/DocsCoreFcn#toc24" target="_blank">http://www.opensips.org/Resources/DocsCoreFcn#toc24</a><br>
&gt;&gt;<br>
&gt;&gt; Regards,<br>
&gt;&gt; Bogdan<br>
&gt;&gt;<br>
&gt;&gt; Daniel Goepp wrote:<br>
&gt;&gt;<br>
&gt;&gt;&gt; I am trying to setup OpenSIPs to run behind a firewall, and not<br>
&gt;&gt;&gt; finding much information regarding how to get OpenSIPs to be aware of<br>
&gt;&gt;&gt; the public IP for it&#39;s signaling.  The firewall is setup with a 1 to 1<br>
&gt;&gt;&gt; NAT for the public and private IPs, and right now all udp and tcp<br>
&gt;&gt;&gt; traffic is being passed directly through.  Has anyone successfully<br>
&gt;&gt;&gt; gotten OpenSIPs setup like this?  If so, can you please provide any<br>
&gt;&gt;&gt; information on how it was setup.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; TIA<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; -dg<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; _______________________________________________<br>
&gt;&gt;&gt; Users mailing list<br>
&gt;&gt;&gt; <a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br>
&gt;&gt;&gt; <a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;<br>
&gt;&gt; _______________________________________________<br>
&gt;&gt; Users mailing list<br>
&gt;&gt; <a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br>
&gt;&gt; <a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;<br>
&gt; _______________________________________________<br>
&gt; Users mailing list<br>
&gt; <a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br>
&gt; <a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
&gt;<br>
&gt;<br>
<br>
<br>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
</div></div></blockquote></div><br>