Ah yes, are you also doing NAT detection and fixing contact?<br clear="all"><br>-dg<br>
<br><br><div class="gmail_quote">On Fri, May 21, 2010 at 10:40 AM, David J. <span dir="ltr"><<a href="mailto:david@styleflare.com">david@styleflare.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div bgcolor="#ffffff" text="#000000">
Yes, I did that, but I am not seeing those changes in the Via Tag,
although I do see them as Appended if that is the correct behavior?<br>
<br>
Via: SIP/2.0/UDP PRIVATE_IP:5061;branch=0;received=PUBLIC_IP.<br>
<br>
<br>
On 5/21/10 12:43 PM, Daniel Goepp wrote:
<blockquote type="cite">Did you make the change recommended by Bogdan?<br>
<br>
--clip<br>
yes, you can set and advertised port and IP to be used (instead of the<br>
actual listening IP:port). See:<br>
advertise_address <a href="http://www.opensips.org/Resources/DocsCoreFcn16#toc24" target="_blank">http://www.opensips.org/Resources/DocsCoreFcn16#toc24</a><br>
advertise_port <a href="http://www.opensips.org/Resources/DocsCoreFcn16#toc25" target="_blank">http://www.opensips.org/Resources/DocsCoreFcn16#toc25</a><br clear="all">
--clip<br>
<br>
I am not experiencing the same problem you are.<br>
<br>
-dg<br>
<br>
<br>
<div class="gmail_quote">On Fri, May 21, 2010 at 9:05 AM, David J. <span dir="ltr"><<a href="mailto:david@styleflare.com" target="_blank">david@styleflare.com</a>></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;">
<div bgcolor="#ffffff" text="#000000">Daniel,<br>
<br>
You said you got opensips/rtp-proxy working on EC2, when testing it, I
see the VIA headers have the EC2 internal ip and the BYE messages not
getting routed correctly, any advice on how to solve that?<br>
<br>
Thanks
<div>
<div><br>
<br>
<br>
On 5/21/10 12:02 PM, Daniel Goepp wrote:
<blockquote type="cite">You need to be careful though because you
will likely not
get media then. We could not find a way to get MediaProxy to work, but
we did patch rtpproxy to work. We just added a -A parameter which is
the publicly advertised address. See:<br>
<br>
<a href="http://opensips-open-sip-server.1449251.n2.nabble.com/Rtpproxy-behind-the-NAT-td5008041.html#none" target="_blank">http://opensips-open-sip-server.1449251.n2.nabble.com/Rtpproxy-behind-the-NAT-td5008041.html#none</a><br>
<br>
-dg<br>
<br>
<br>
<div class="gmail_quote">On Fri, May 21, 2010 at 1:34 AM,
Bogdan-Andrei Iancu <span dir="ltr"><<a href="mailto:bogdan@voice-system.ro" target="_blank">bogdan@voice-system.ro</a>></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
Stefano,<br>
<br>
yes, you can set and advertised port and IP to be used (instead of the<br>
actual listening IP:port). See:<br>
advertise_address <a href="http://www.opensips.org/Resources/DocsCoreFcn16#toc24" target="_blank">http://www.opensips.org/Resources/DocsCoreFcn16#toc24</a><br>
advertise_port <a href="http://www.opensips.org/Resources/DocsCoreFcn16#toc25" target="_blank">http://www.opensips.org/Resources/DocsCoreFcn16#toc25</a><br>
<br>
Regards,<br>
Bogdan<br>
<div>
<div><br>
Stefano Pisani wrote:<br>
> I need to put opensips 1.6.2 behind a firewall.<br>
> In this case the server has an internal IP (192.168.x.x)<br>
> There is a way to configure the extern (public) IP in opensis, in
this<br>
> way all the headers of messagges will be correct.<br>
><br>
> stefano<br>
><br>
> _______________________________________________<br>
> Users mailing list<br>
> <a href="mailto:Users@lists.opensips.org" target="_blank">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>
><br>
><br>
<br>
<br>
</div>
</div>
<font color="#888888">--<br>
Bogdan-Andrei Iancu<br>
<a href="http://www.voice-system.ro" target="_blank">www.voice-system.ro</a><br>
</font>
<div>
<div><br>
<br>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org" target="_blank">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>
<pre><fieldset></fieldset>
_______________________________________________
Users mailing list
<a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a>
</pre>
</blockquote>
<br>
</div>
</div>
</div>
<br>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org" target="_blank">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>
<br>
</blockquote>
</div>
<br>
<pre><fieldset></fieldset>
_______________________________________________
Users mailing list
<a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a>
</pre>
</blockquote>
<br>
</div>
<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>
<br></blockquote></div><br>