<br><br><div class="gmail_quote">On Wed, Mar 10, 2010 at 5:25 PM, arliyardo <span dir="ltr"><<a href="mailto:arliyardo@gmail.com">arliyardo@gmail.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;">
my scenario like this:<br><pre>PHONE1->FS (192.168.0.4) -> NAT1 (Public IP 1.2.3.4) -> INTERNET -> NAT2 (Public IP 5.6.7.8) -> PHONE2 (192.168.1.100)<br>First, I have forwarded sip port and rtp port.<br>I have try servaral configurations in <a href="http://wiki.freeswitch.org/wiki/General_NAT_example_scenarios" target="_blank">http://wiki.freeswitch.org/wiki/General_NAT_example_scenarios</a> and without luck!<br>
<br>PHONE2 only regists to FS, how can FS gets through NAT2 to PHONE2, include sip signaling and rtp connection ? <br></pre>
<br></blockquote><div>The key here is that you have two devices that can totally mess with your SIP and RTP: NAT1 and NAT2. What are these two devices? Secondly, what kind of phone is PHONE2? Some phones work better than others. Third, have you captured the SIP traffic behind each NAT device to see what's going on? You won't be able to fix the problem until you actually find out what the problem is and where it is happening. For the record, I've done this kind of thing using X-Lite and Snom 300's as the PHONE2 in your example, so I know it is possible. The trick is making sure that your NAT devices have their SIP ALG's turned off. Check this page to see if you have one of these devices:<br>
<a href="http://wiki.freeswitch.org/wiki/ALG">http://wiki.freeswitch.org/wiki/ALG</a><br><br>-MC<br></div></div><br>