<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Dec 20, 2009, at 2:53 PM, Gad Bentolila wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><font size="-1"><font face="Verdana">DISCLAIMER: I'm REALLY new to FreeSwitch, so please take my advice with a grain of salt.<br></font></font></span></blockquote><div><br></div><div>Welcome to the community.</div><br><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><font size="-1"><font face="Verdana">I have a similar setup (and problem) - the wiki documentation refers to it as "double nat". Like you, my FS and client are behind different NATs and I can register my remote endpoint and make calls (in my case, to the the FS demo ivr at 5000).<br><br>Since your external endpoint (spa3102) is registering, you've likely setup your sip profile correctly (ext-sip-ip, ext-rtp-ip, nat settings, etc).<br></font></font></span></blockquote><div><br></div>Your endpoint need only insert rport and FreeSWITCH will do the right thing. </div><div><br><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><font size="-1"><font face="Verdana">1) Setup stun on your remote endpoint (spa3102 in your case)<br>2) Add <variable name="sip-force-contact" value="NDLB-connectile-dysfunction"/> to the directory xml file that describes your spa3102 endpoint<font class="Apple-style-span" color="#000000" face="Helvetica"><span class="Apple-style-span" style="font-size: medium;"><font class="Apple-style-span" color="#144FAE" face="Verdana"><span class="Apple-style-span" style="font-size: small;"><br></span></font></span></font></font></font></span></blockquote><div><br></div>The device supports STUN also its highly recommended your device know how to overcome its own NAT. I personally do not believe its the registrars place to overcome an endpoints nat... puts undue burden on the registar.</div><div><br><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><font size="-1"><font face="Verdana">Option 1 worked for me right away (eyebeam in my case) and, as expected, the remote sdp had the correct (remote) IP address, since the endpoint is using stun to correctly identify its IP address to FS. However, option 2 has not made a difference (for me). Is it just me or is it strange that SIP works without stun, but RTP doesn't?<br><br></font></font><font size="-1"><font face="Verdana">I guess I've been spoiled by the way Asterisk handles NAT and was hopeful that<span class="Apple-converted-space"> </span></font></font><font size="-1"><font face="Verdana">NDLB-connectile-dysfunction would behave similarly, so I wouldn't have to tell users to setup stun on their clients.<span class="Apple-converted-space"> </span></font></font><font size="-1"><font face="Verdana">Maybe a FS user with some experience with this type of NAT setup and these settings can help. I'd be interested in knowing how to correctly setup remote NATted endpoints without stun - or, at least, hear from someone that this setting works for them without stun.<br><br>Anyway, hope this helps you with your SPA3102.</font></font></span></blockquote><br></div><div>Bottom line is enable rport and use stun on the SPA and it'll just work.</div><div><br></div><div>/b</div><div><br></div><br></body></html>