<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">You may want to try this again with latest svn trunk. We have done quite a lot of work to make nat support much better sense 1.0.4 <div><br></div><div>Mike</div><div><br></div><div>p.s. I can't comment about version 1.4 due to broken flux capacitor.</div><div><br></div><div><br><div><div>On Dec 3, 2009, at 4:36 AM, Henry Huang wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">My freeswitch is using public IP. I setup a gateway registering to voipstunt, and put it under internal profile. I tried to make call, and I got no RTP back from the provider... Tried treating NAT issue by changing IP address, internal IP, external IP. But no use, still getting no audio. <div>
<br></div><div>Finally, I gave up play around with the internal profile and put the gateway <b>settings under external profile. And magically, it worked.</b> I am getting audio now. But it leads me to wonders, what's the core difference between external profile and internal profile. Even if I set the external SIP IP and exteranl RTP IP to the public IP in internal profile, I am still getting no audio. Can anyone clear the concept for me here?</div>
<div><br></div><div>by the way, I am using freeswitch 1.4 stable version. <br><div><br></div><div><br clear="all"><br>-- <br>Henry Huang<br><br>
</div></div>
_______________________________________________<br>FreeSWITCH-users mailing list<br><a href="mailto:FreeSWITCH-users@lists.freeswitch.org">FreeSWITCH-users@lists.freeswitch.org</a><br>http://lists.freeswitch.org/mailman/listinfo/freeswitch-users<br>UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users<br>http://www.freeswitch.org<br></blockquote></div><br></div></body></html>