<?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: T-Mobile USA text timestamp problem in Denver</title>
	<atom:link href="http://www.mobileindustryreview.com/2007/07/t-mobile_usa_text_timestamp_problem_in_denver.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.mobileindustryreview.com/2007/07/t-mobile_usa_text_timestamp_problem_in_denver.html</link>
	<description>Daily news and opinion for 250,000 industry executives and mobile fanatics</description>
	<lastBuildDate>Tue, 14 Feb 2012 22:14:00 +0100</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Verizon Gets it Right</title>
		<link>http://www.mobileindustryreview.com/2007/07/t-mobile_usa_text_timestamp_problem_in_denver.html/comment-page-1#comment-69837</link>
		<dc:creator>Verizon Gets it Right</dc:creator>
		<pubDate>Fri, 13 Jul 2007 13:50:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.smstextnews.com/2007/07/t-mobile_usa_text_timestamp_problem_in_denver.html#comment-69837</guid>
		<description>Sorry folks, but Verizon gets it right.  All of my incoming texts on my Verizon phone are time stamped correctly.  If they can do it right, why can&#039;t T-Mobile?  I feel sorry for the person who sent this in as well as all the other T-Mobile customers in AZ</description>
		<content:encoded><![CDATA[<p>Sorry folks, but Verizon gets it right.  All of my incoming texts on my Verizon phone are time stamped correctly.  If they can do it right, why can&#8217;t T-Mobile?  I feel sorry for the person who sent this in as well as all the other T-Mobile customers in AZ</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Fahed</title>
		<link>http://www.mobileindustryreview.com/2007/07/t-mobile_usa_text_timestamp_problem_in_denver.html/comment-page-1#comment-69738</link>
		<dc:creator>Fahed</dc:creator>
		<pubDate>Fri, 13 Jul 2007 06:02:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.smstextnews.com/2007/07/t-mobile_usa_text_timestamp_problem_in_denver.html#comment-69738</guid>
		<description>Internetworking in the US was a big problem for a very long time and one of the reasons which prevented the delay of SMS being taken up. In the end, it was mostly resolved by using some of the larger aggregators (e.g. Sybase365) to handle the messages as inbetweens.

As such, although i&#039;m not too sure about T-Mobile, the problem probably lies there some where. Not that much to worry about though.</description>
		<content:encoded><![CDATA[<p>Internetworking in the US was a big problem for a very long time and one of the reasons which prevented the delay of SMS being taken up. In the end, it was mostly resolved by using some of the larger aggregators (e.g. Sybase365) to handle the messages as inbetweens.</p>
<p>As such, although i&#8217;m not too sure about T-Mobile, the problem probably lies there some where. Not that much to worry about though.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chad</title>
		<link>http://www.mobileindustryreview.com/2007/07/t-mobile_usa_text_timestamp_problem_in_denver.html/comment-page-1#comment-69718</link>
		<dc:creator>Chad</dc:creator>
		<pubDate>Fri, 13 Jul 2007 03:53:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.smstextnews.com/2007/07/t-mobile_usa_text_timestamp_problem_in_denver.html#comment-69718</guid>
		<description>I think it may have to do with the fact that the SMS service center for your area is in Denver. A SMS gets sent from your handset to the Denver server, then gets timestamped when sent through, then again at your handset (based on local time).  Sounds like something got hincky when they changed the DST settings.</description>
		<content:encoded><![CDATA[<p>I think it may have to do with the fact that the SMS service center for your area is in Denver. A SMS gets sent from your handset to the Denver server, then gets timestamped when sent through, then again at your handset (based on local time).  Sounds like something got hincky when they changed the DST settings.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: carlo</title>
		<link>http://www.mobileindustryreview.com/2007/07/t-mobile_usa_text_timestamp_problem_in_denver.html/comment-page-1#comment-69669</link>
		<dc:creator>carlo</dc:creator>
		<pubDate>Fri, 13 Jul 2007 00:31:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.smstextnews.com/2007/07/t-mobile_usa_text_timestamp_problem_in_denver.html#comment-69669</guid>
		<description>Blame it on Arizona for not going on daylight savings time like the rest of the country, so in the summer they&#039;re on Pacific time, not Mountain time (like Denver) as they are the rest of the year.</description>
		<content:encoded><![CDATA[<p>Blame it on Arizona for not going on daylight savings time like the rest of the country, so in the summer they&#8217;re on Pacific time, not Mountain time (like Denver) as they are the rest of the year.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

