<?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: VoIP by Numbers, 1, 2, 3</title>
	<atom:link href="http://www.allaboutnortel.com/2006/08/16/voip-by-numbers-1-2-3/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.allaboutnortel.com/2006/08/16/voip-by-numbers-1-2-3/</link>
	<description>All the News about Nortel Networks</description>
	<lastBuildDate>Thu, 09 Sep 2010 02:59:25 +0000</lastBuildDate>
	
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: All Nortel, All the Time &#187; Blog Archive &#187; VoIP 1, 2, 3: Analyst Reaction</title>
		<link>http://www.allaboutnortel.com/2006/08/16/voip-by-numbers-1-2-3/comment-page-1/#comment-295</link>
		<dc:creator>All Nortel, All the Time &#187; Blog Archive &#187; VoIP 1, 2, 3: Analyst Reaction</dc:creator>
		<pubDate>Mon, 21 Aug 2006 17:55:32 +0000</pubDate>
		<guid isPermaLink="false">http://allaboutnortel.com/?p=271#comment-295</guid>
		<description>[...] Orion Securities analyst Duncan Stewart has picked up on the news report that Nortel has a new channel program in place to make it easier for existing and potential customers to migrate to VoIP from legacy telephony systems. Stewart is pleased Nortel has recognized&#160;a problem that encouraged channel partners to &#8220;rip and replace&#8221; Nortel gear with Cisco&#8217;s,&#160;but he said it is a &#8220;bit horrifying that this was not fixed sooner&#8221;. Here&#8217;s an excerpt from his research report: [...]</description>
		<content:encoded><![CDATA[<p>[...] Orion Securities analyst Duncan Stewart has picked up on the news report that Nortel has a new channel program in place to make it easier for existing and potential customers to migrate to VoIP from legacy telephony systems. Stewart is pleased Nortel has recognized&nbsp;a problem that encouraged channel partners to &#8220;rip and replace&#8221; Nortel gear with Cisco&#8217;s,&nbsp;but he said it is a &#8220;bit horrifying that this was not fixed sooner&#8221;. Here&#8217;s an excerpt from his research report: [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Godzilla</title>
		<link>http://www.allaboutnortel.com/2006/08/16/voip-by-numbers-1-2-3/comment-page-1/#comment-293</link>
		<dc:creator>Godzilla</dc:creator>
		<pubDate>Thu, 17 Aug 2006 14:34:31 +0000</pubDate>
		<guid isPermaLink="false">http://allaboutnortel.com/?p=271#comment-293</guid>
		<description>the issue is that migrating from legacy system to VoIP is itself a legacy strategy.

It was devised back when Nortel and Avaya/Lucent had the lion&#039;s share of the PBX market, and when VoIP was far less mature than it is today. The strategy aimed at transitioning weary customers from TDM systems to VoIP progressively, thus allowing incremental steps, and progressively locking the customer into the Nortel solution.  The thought was that a small incremental step would be cheaper initially than a rip and replace from Cisco or whoever, and would make the customer progressively more comfortable with the VoIP concept.  Of course this was a complex strategy, with many moving parts, and compared with the simplicity of Cisco&#039;s forklift strategy.   Avaya had a similar strategy

Fast forward 2006.  VoIP is now much more stable, customers are much more familiar, and pricing continues to edge downwards.   There are a lot fewer qualms now about forklift: it is simpler, quicker, gets it done, so the customer can then move on and focus on other priorities.  (note: are there also SOX issues?  with a migration plan, you may not be able to recognize revenues for years)

In summary, Nortel&#039;s comples progressive migration strategy was designed for a different age when they had market dominance, and when customers viewed VoIP with suspiscion.  The equipment is fine.  It&#039;s the marketing and strategy that have become stale.</description>
		<content:encoded><![CDATA[<p>the issue is that migrating from legacy system to VoIP is itself a legacy strategy.</p>
<p>It was devised back when Nortel and Avaya/Lucent had the lion&#8217;s share of the PBX market, and when VoIP was far less mature than it is today. The strategy aimed at transitioning weary customers from TDM systems to VoIP progressively, thus allowing incremental steps, and progressively locking the customer into the Nortel solution.  The thought was that a small incremental step would be cheaper initially than a rip and replace from Cisco or whoever, and would make the customer progressively more comfortable with the VoIP concept.  Of course this was a complex strategy, with many moving parts, and compared with the simplicity of Cisco&#8217;s forklift strategy.   Avaya had a similar strategy</p>
<p>Fast forward 2006.  VoIP is now much more stable, customers are much more familiar, and pricing continues to edge downwards.   There are a lot fewer qualms now about forklift: it is simpler, quicker, gets it done, so the customer can then move on and focus on other priorities.  (note: are there also SOX issues?  with a migration plan, you may not be able to recognize revenues for years)</p>
<p>In summary, Nortel&#8217;s comples progressive migration strategy was designed for a different age when they had market dominance, and when customers viewed VoIP with suspiscion.  The equipment is fine.  It&#8217;s the marketing and strategy that have become stale.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: long on nortel</title>
		<link>http://www.allaboutnortel.com/2006/08/16/voip-by-numbers-1-2-3/comment-page-1/#comment-294</link>
		<dc:creator>long on nortel</dc:creator>
		<pubDate>Wed, 16 Aug 2006 15:25:46 +0000</pubDate>
		<guid isPermaLink="false">http://allaboutnortel.com/?p=271#comment-294</guid>
		<description>If you read the entire article it suugest  that the issue was that of a poor pricing methodolgy and not inferior product, when posting  these extracts be responsible and present the facts or at least the enire article.</description>
		<content:encoded><![CDATA[<p>If you read the entire article it suugest  that the issue was that of a poor pricing methodolgy and not inferior product, when posting  these extracts be responsible and present the facts or at least the enire article.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
