<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Best Windows Mobile SIP VOIP Clients</title>
	<atom:link href="http://cheapestvoipcalls.net/best-windows-mobile-sip-voip-clients/feed/" rel="self" type="application/rss+xml" />
	<link>http://cheapestvoipcalls.net/best-windows-mobile-sip-voip-clients/</link>
	<description></description>
	<lastBuildDate>Sun, 29 Aug 2010 15:51:56 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=3042</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Rob</title>
		<link>http://cheapestvoipcalls.net/best-windows-mobile-sip-voip-clients/comment-page-1/#comment-37</link>
		<dc:creator>Rob</dc:creator>
		<pubDate>Tue, 05 Jan 2010 10:16:46 +0000</pubDate>
		<guid isPermaLink="false">http://cheapestvoipcalls.net/?p=305#comment-37</guid>
		<description>Regrettably - SIP was never designed to be Network Address translation (NAT) friendly and as 99% of cell operators use NAT and dont offer SIP proxys at their boundary firewalls / gateways SIP can be very limited via Mobile.

for example...get two SIP enabled windows mobiles behind a common NAT firewall and registered with an external SIP proxy.

The signalling works first time and the call alert will go through...

sadly though in the majority of cases the voice path will not connect - why ? because the voice part of the SIP call is based on RTP (real time protocol)  is seen as an &quot;unsolicitied request&quot; from outside the firewall - therefore the firewall doesnt know who to forward it to.

Do you see many cell operators adding SIP proxies ? when it may cause them to loose call revenue ?...no?....me neither !! ;-)

Praise be to IAX2 protocol and asterisk! - and to ESCsoftphone / voipsurfer (Same product different badge) for making it available on WM based devices</description>
		<content:encoded><![CDATA[<p>Regrettably &#8211; SIP was never designed to be Network Address translation (NAT) friendly and as 99% of cell operators use NAT and dont offer SIP proxys at their boundary firewalls / gateways SIP can be very limited via Mobile.</p>
<p>for example&#8230;get two SIP enabled windows mobiles behind a common NAT firewall and registered with an external SIP proxy.</p>
<p>The signalling works first time and the call alert will go through&#8230;</p>
<p>sadly though in the majority of cases the voice path will not connect &#8211; why ? because the voice part of the SIP call is based on RTP (real time protocol)  is seen as an &#8220;unsolicitied request&#8221; from outside the firewall &#8211; therefore the firewall doesnt know who to forward it to.</p>
<p>Do you see many cell operators adding SIP proxies ? when it may cause them to loose call revenue ?&#8230;no?&#8230;.me neither !! <img src='http://cheapestvoipcalls.net/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </p>
<p>Praise be to IAX2 protocol and asterisk! &#8211; and to ESCsoftphone / voipsurfer (Same product different badge) for making it available on WM based devices</p>
]]></content:encoded>
	</item>
</channel>
</rss>
