<?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>Doug on IP Comm &#187; microsoft response point</title>
	<atom:link href="http://dougonipcomm.com/tag/microsoft-response-point/feed/" rel="self" type="application/rss+xml" />
	<link>http://dougonipcomm.com</link>
	<description>An independent voice on VoIP, telecom, and IP Communications</description>
	<lastBuildDate>Mon, 21 May 2012 18:24:20 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
		<item>
		<title>Microsoft Response Point future not looking good</title>
		<link>http://dougonipcomm.com/2009/07/01/microsoft-response-point-future-not-looking-good/</link>
		<comments>http://dougonipcomm.com/2009/07/01/microsoft-response-point-future-not-looking-good/#comments</comments>
		<pubDate>Wed, 01 Jul 2009 16:10:44 +0000</pubDate>
		<dc:creator>Doug Mohney</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[business voip]]></category>
		<category><![CDATA[Digium]]></category>
		<category><![CDATA[IP PBX]]></category>
		<category><![CDATA[Microsoft]]></category>
		<category><![CDATA[microsoft response point]]></category>
		<category><![CDATA[VoIP]]></category>

		<guid isPermaLink="false">http://dougonipcomm.wordpress.com/?p=265</guid>
		<description><![CDATA[ <p>ChannelWeb reports that Microsoft is wishy-washy about what will to happen with it&#8217;s Response Point SMB VoIP system.</p> <p>Meeting with VoIP VARs, Response Point Program Manager John Frederickson said Microsoft doesn&#8217;t currently plan to release future versions of Response Point. It will, however, continue to maintain the product and evaluate specific feature requests.  The [...]]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: right; margin-left: 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fdougonipcomm.com%2F2009%2F07%2F01%2Fmicrosoft-response-point-future-not-looking-good%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fdougonipcomm.com%2F2009%2F07%2F01%2Fmicrosoft-response-point-future-not-looking-good%2F&amp;source=DougonIPComm&amp;style=normal&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
<p><em>ChannelWeb</em> reports that Microsoft is wishy-washy about what will to happen with it&#8217;s <a href="http://www.crn.com/software/218102171;jsessionid=AQNH3SUHZ11RSQSNDLPCKH0CJUNN2JVN">Response Point SMB VoIP system</a>.</p>
<p>Meeting with VoIP VARs, Response Point Program Manager John Frederickson said Microsoft doesn&#8217;t currently plan to release future versions of Response Point. It will, however, continue to maintain the product and evaluate specific feature requests.  The company will also continue supporting OEMs and selling Response Point 1.0 Service Pack 2.</p>
<p>So, you want to buy a dead/legacy-ed out product because&#8230;?</p>
<p>Back in May, Microsoft laid off a bunch of people working on Response Point and hasn&#8217;t said diddly about plans to develop/release a 2.0 version.  Things don&#8217;t look good as the Response Point GM has been moved over to Microsoft&#8217;s search group and there&#8217;s a &#8220;small&#8221; engineering team still around to maintain the product, but Response Point is &#8220;funded&#8221; and has a marketing budget through June 30, 2010.</p>
<p>An email from Microsoft to ChannelWeb said the company didn&#8217;t &#8220;announce anything&#8221; at the meeting and expects to have more details to share on future development at the end of this calendar year.</p>
<p>Some VARs love Response Point, but they are discomforted that Microsoft has basically frozen the product.  Other players in the IP PBX game would like to see Response Point just Go Away &#8211; the Digium people seem to be especially catty when it comes to the SMB PBX.</p>
]]></content:encoded>
			<wfw:commentRss>http://dougonipcomm.com/2009/07/01/microsoft-response-point-future-not-looking-good/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>What&#039;s happening to Microsoft Response Point?</title>
		<link>http://dougonipcomm.com/2009/05/10/whats-happening-to-microsoft-response-point/</link>
		<comments>http://dougonipcomm.com/2009/05/10/whats-happening-to-microsoft-response-point/#comments</comments>
		<pubDate>Sun, 10 May 2009 22:17:37 +0000</pubDate>
		<dc:creator>Doug Mohney</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[IP PBX]]></category>
		<category><![CDATA[microsoft response point]]></category>
		<category><![CDATA[Response Point]]></category>
		<category><![CDATA[smb]]></category>
		<category><![CDATA[smb phone system]]></category>
		<category><![CDATA[SMB VoIP]]></category>
		<category><![CDATA[VoIP]]></category>

		<guid isPermaLink="false">http://dougonipcomm.wordpress.com/?p=30</guid>
		<description><![CDATA[ <p>When the axe came down at Microsoft last week, the Response Point small business phone team took a hit. How fatal it is to the business and new product releases is up for debate amongst the peanut gallery.</p> <p>Whispers of Response Point&#8217;s demise started out from an anonymous post on a blog tracking Microsoft [...]]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: right; margin-left: 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fdougonipcomm.com%2F2009%2F05%2F10%2Fwhats-happening-to-microsoft-response-point%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fdougonipcomm.com%2F2009%2F05%2F10%2Fwhats-happening-to-microsoft-response-point%2F&amp;source=DougonIPComm&amp;style=normal&amp;b=2" height="61" width="50" /><br />
			</a>
		</div>
<p>When the axe came down at Microsoft last week, the Response Point small business phone team took a hit. How fatal it is to the business and new product releases is up for debate amongst the peanut gallery.</p>
<p>Whispers of Response Point&#8217;s demise started out from an anonymous post on a blog tracking Microsoft layoffs saying that the entire Response Point team had been &#8220;canned.&#8221;  Microsoft begs to differ and ZDNet quotes a company spokesperson saying—</p>
<ul>
<li>Microsoft continues to support Response Point version 1.0. and current OEMs, service providers and resellers that are selling it. Customers will continue to be supported through their OEMs.</li>
<li>Microsoft will continue to promote the product online and spotlight compatible 3rd party services and add-on products.</li>
<li>The Response Point team has not been moved to another division and</li>
<li>The team is evaluating the strategy for the next version of the product and will continue to investigate the opportunity in the small business market.</li>
</ul>
<p>Response Point has been kicking around since October 2007 and the IP PBX is targeted at SMBs with one to 50 phones.  SP2 &#8212; the latest release &#8212; included support for basic call queuing, better SIP trunking, and, VPN support, an automated night receptionist scheduler, and URL/HTML customization for web 2.0/mash-up style creations.</p>
<p>Around IT Expo in February, the Response Point &#8220;team&#8221; numbered a lean-mean 35 members. No indications on how many people got the axe last week or how many remain.</p>
<p><em>Shoutout to Bill Miller for the <a href="http://twitter.com/beelinebill">Tweet<br />
</a>Sources: Microsoft Response Point <a href="http://blogs.technet.com/rp/archive/2009/05/07/next-chapter-for-response-point.aspx">blog</a> and ZDNet&#8217;s <a href="http://blogs.zdnet.com/microsoft/?p=2694">blog</a>.</em></p>
]]></content:encoded>
			<wfw:commentRss>http://dougonipcomm.com/2009/05/10/whats-happening-to-microsoft-response-point/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

