<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Telecom Spend Trends &#187; TEM</title>
	<atom:link href="http://www.hyounpark.com/tag/tem/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.hyounpark.com</link>
	<description>A Blog About Telecom Expense Management and Telecom Life Cycle Management</description>
	<lastBuildDate>Sun, 14 Feb 2010 15:20:15 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>IPDR, why does it matter?</title>
		<link>http://www.hyounpark.com/2010/01/26/ipdr-why-does-it-matter/</link>
		<comments>http://www.hyounpark.com/2010/01/26/ipdr-why-does-it-matter/#comments</comments>
		<pubDate>Tue, 26 Jan 2010 06:05:21 +0000</pubDate>
		<dc:creator>Hyoun Park</dc:creator>
				<category><![CDATA[Telecom Expense Management]]></category>
		<category><![CDATA[billing errors]]></category>
		<category><![CDATA[call detail records]]></category>
		<category><![CDATA[CDR]]></category>
		<category><![CDATA[internet protocol detail records]]></category>
		<category><![CDATA[IPDR]]></category>
		<category><![CDATA[telecom lifecycle management]]></category>
		<category><![CDATA[TEM]]></category>
		<category><![CDATA[TLM]]></category>

		<guid isPermaLink="false">http://www.hyounpark.com/?p=23</guid>
		<description><![CDATA[Will IPDRs lead to the same expense management problems that CDRs have traditionally provided in the world of telecom?]]></description>
		<wfw:commentRss>http://www.hyounpark.com/2010/01/26/ipdr-why-does-it-matter/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
