<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.2.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Yippeeee! STUN works!</title>
	<link>http://eugenia.gnomefiles.org/2006/12/19/yippeeee-stun-works/</link>
	<description></description>
	<pubDate>Fri, 21 Nov 2008 05:13:38 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.2.2</generator>

	<item>
		<title>By:  Eugenia</title>
		<link>http://eugenia.gnomefiles.org/2006/12/19/yippeeee-stun-works/#comment-2098</link>
		<author> Eugenia</author>
		<pubDate>Fri, 29 Dec 2006 11:11:00 +0000</pubDate>
		<guid>http://eugenia.gnomefiles.org/2006/12/19/yippeeee-stun-works/#comment-2098</guid>
		<description> STUN exists now on the v3 firmware. But it&#8217;s hardcoded to a Nokia  STUN server. You can&#8217;t change that setting, but at least exists inside the program, so SIP servers like Gizmo and VoiceBuster now work.
	
Plese note that some SIP servers don&#8217;t require a STUN server, but instead an outbound proxy to be defined. This is true for the FWD and Ekiga SIP services for example.
	
As for the port in the firewall, this is true for all SIP connections and SIP clients, not just for the E61. Port 5060 must be &#8220;port triggered&#8221; (port opened for all clients connected to your WiFi router), not &#8220;port forwarded&#8221;
in your firewall. </description>
		<content:encoded><![CDATA[<p>STUN exists now on the v3 firmware. But it&#8217;s hardcoded to a Nokia  STUN server. You can&#8217;t change that setting, but at least exists inside the program, so SIP servers like Gizmo and VoiceBuster now work.</p>
<p>Plese note that some SIP servers don&#8217;t require a STUN server, but instead an outbound proxy to be defined. This is true for the FWD and Ekiga SIP services for example.</p>
<p>As for the port in the firewall, this is true for all SIP connections and SIP clients, not just for the E61. Port 5060 must be &#8220;port triggered&#8221; (port opened for all clients connected to your WiFi router), not &#8220;port forwarded&#8221;<br />
in your firewall.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By:  mieses</title>
		<link>http://eugenia.gnomefiles.org/2006/12/19/yippeeee-stun-works/#comment-2097</link>
		<author> mieses</author>
		<pubDate>Fri, 29 Dec 2006 03:27:00 +0000</pubDate>
		<guid>http://eugenia.gnomefiles.org/2006/12/19/yippeeee-stun-works/#comment-2097</guid>
		<description> STUN doesn&#8217;t work.  There are no STUN settings.  Sipgate still requries a port opened in the firewall.  How were you able to confirm that STUN works? </description>
		<content:encoded><![CDATA[<p>STUN doesn&#8217;t work.  There are no STUN settings.  Sipgate still requries a port opened in the firewall.  How were you able to confirm that STUN works?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By:  Bruno</title>
		<link>http://eugenia.gnomefiles.org/2006/12/19/yippeeee-stun-works/#comment-2096</link>
		<author> Bruno</author>
		<pubDate>Sun, 24 Dec 2006 10:55:00 +0000</pubDate>
		<guid>http://eugenia.gnomefiles.org/2006/12/19/yippeeee-stun-works/#comment-2096</guid>
		<description> Hello there. Where is the STUN setting in the new firmware? I could not find it. OTOH, using AUTO instead of TCP or UDP on SIP settings, I can now receive calls behind my NAT-router. Using UDP setting (my asterisk server only uses UDP) I was able to make but not receive the calls.
Unfortunatelly the two last firmwares still have the nasty bug on which you need to use the blue arrow key to get the numbers on a number only input field. And, odd enough, when numlocking (double blue key) the rest of the keyboard (including dot) becames unusable. It is a pain to input an IP address that way &lt;img src='http://eugenia.gnomefiles.org/images/smilies/icon_sad.gif' alt=':-(' /&gt;
Cheers from Brazil </description>
		<content:encoded><![CDATA[<p>Hello there. Where is the STUN setting in the new firmware? I could not find it. OTOH, using AUTO instead of TCP or UDP on SIP settings, I can now receive calls behind my NAT-router. Using UDP setting (my asterisk server only uses UDP) I was able to make but not receive the calls.<br />
Unfortunatelly the two last firmwares still have the nasty bug on which you need to use the blue arrow key to get the numbers on a number only input field. And, odd enough, when numlocking (double blue key) the rest of the keyboard (including dot) becames unusable. It is a pain to input an IP address that way <img src='http://eugenia.gnomefiles.org/images/smilies/icon_sad.gif' alt=':-(' /><br />
Cheers from Brazil</p>
]]></content:encoded>
	</item>
</channel>
</rss>
