<?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: ACMA moves on VoIP&#8217;s widespread Numbering Plan non-compliance</title>
	<atom:link href="http://www.cspcentral.com.au/2008/12/acma-moves-on-voips-widespread-numbering-plan-non-compliance/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.cspcentral.com.au/2008/12/acma-moves-on-voips-widespread-numbering-plan-non-compliance/</link>
	<description>Australia&#039;s ISP and Telco Legal Site</description>
	<lastBuildDate>Fri, 03 Feb 2012 06:16:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Veteran</title>
		<link>http://www.cspcentral.com.au/2008/12/acma-moves-on-voips-widespread-numbering-plan-non-compliance/#comment-134</link>
		<dc:creator>Veteran</dc:creator>
		<pubDate>Sun, 28 Dec 2008 13:06:54 +0000</pubDate>
		<guid isPermaLink="false">http://cspcentral.com.au/wordpress/?p=1226#comment-134</guid>
		<description>The rule that numbers must be associated with a location is a legacy anachronism going back to hard-wired mechanical exchanges. Isn&#039;t it time the ACMA got over it? What about number portability? What about VoIP on mobile Internet?

Any (experienced) database designer will tell you never build intelligence into the primary key. It will always break and then need Mickey Mouse rules to try to recover.  All ACMA needs is a simple (public?) lookup table to associate numbers with a location/ locations/ mobile, ditch the numbering plan and periodic updates, and they can free themselves, the industry and users from unnecessary cost and hassles.</description>
		<content:encoded><![CDATA[<p>The rule that numbers must be associated with a location is a legacy anachronism going back to hard-wired mechanical exchanges. Isn&#8217;t it time the ACMA got over it? What about number portability? What about VoIP on mobile Internet?</p>
<p>Any (experienced) database designer will tell you never build intelligence into the primary key. It will always break and then need Mickey Mouse rules to try to recover.  All ACMA needs is a simple (public?) lookup table to associate numbers with a location/ locations/ mobile, ditch the numbering plan and periodic updates, and they can free themselves, the industry and users from unnecessary cost and hassles.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter</title>
		<link>http://www.cspcentral.com.au/2008/12/acma-moves-on-voips-widespread-numbering-plan-non-compliance/#comment-133</link>
		<dc:creator>Peter</dc:creator>
		<pubDate>Thu, 25 Dec 2008 21:19:51 +0000</pubDate>
		<guid isPermaLink="false">http://cspcentral.com.au/wordpress/?p=1226#comment-133</guid>
		<description>Perhaps it time to look to the future, is there still a need for the current Numbering plan restrictions. VOIP providers are simply meeting customer needs. Who is disadvantaged by non geographic numbers? Calls to and from these numbers are paid for and the transport of the calls as data is also paid for. Perhaps it time to review the need for STD charging and make Australia one local call zone</description>
		<content:encoded><![CDATA[<p>Perhaps it time to look to the future, is there still a need for the current Numbering plan restrictions. VOIP providers are simply meeting customer needs. Who is disadvantaged by non geographic numbers? Calls to and from these numbers are paid for and the transport of the calls as data is also paid for. Perhaps it time to review the need for STD charging and make Australia one local call zone</p>
]]></content:encoded>
	</item>
</channel>
</rss>

