<?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"
	>
<channel>
	<title>Comments on: Response Point vs Talkswitch - a comparison of small business phone systems</title>
	<atom:link href="http://selkowitz.org/response-point-vs-talkswitch-a-comparison-of-small-business-phone-systems/feed/" rel="self" type="application/rss+xml" />
	<link>http://selkowitz.org/response-point-vs-talkswitch-a-comparison-of-small-business-phone-systems/</link>
	<description>The Life and Times of Seattle's Small Business Systems Consultant.  Articles and advice on small business phone systems, phone and internet services, VoIP, and all things technology related.</description>
	<pubDate>Thu, 11 Mar 2010 06:06:32 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: Doug Steinschneider</title>
		<link>http://selkowitz.org/response-point-vs-talkswitch-a-comparison-of-small-business-phone-systems/#comment-17005</link>
		<dc:creator>Doug Steinschneider</dc:creator>
		<pubDate>Sat, 19 Dec 2009 01:20:39 +0000</pubDate>
		<guid isPermaLink="false">http://selkowitz.org/response-point-vs-talkswitch-a-comparison-of-small-business-phone-systems/#comment-17005</guid>
		<description>Great discussion. Now 1 year and a half later Kevin is vindicated on the Microsoft backing is no guarantee stance. I actually believe that Microsoft will keep Response Point as a product line but many MS partners believe they will offer some variant of their UC products instead in the future. I have worked with Cisco Call Manager for years because I support one customer on standalone Call Manager / Unity (it's own T1/PRI, router, concentrator and switch) so I decided to implement Response Point for customers. The sale is easy but the partner must be very thorough and uncover every phone users needs and educate them on what will be changing as they move to the new system. The Response Point works nicely over SIP trunks on our local cable provider.</description>
		<content:encoded><![CDATA[<p>Great discussion. Now 1 year and a half later Kevin is vindicated on the Microsoft backing is no guarantee stance. I actually believe that Microsoft will keep Response Point as a product line but many MS partners believe they will offer some variant of their UC products instead in the future. I have worked with Cisco Call Manager for years because I support one customer on standalone Call Manager / Unity (it&#8217;s own T1/PRI, router, concentrator and switch) so I decided to implement Response Point for customers. The sale is easy but the partner must be very thorough and uncover every phone users needs and educate them on what will be changing as they move to the new system. The Response Point works nicely over SIP trunks on our local cable provider.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James Wu</title>
		<link>http://selkowitz.org/response-point-vs-talkswitch-a-comparison-of-small-business-phone-systems/#comment-13564</link>
		<dc:creator>James Wu</dc:creator>
		<pubDate>Thu, 18 Jun 2009 18:36:04 +0000</pubDate>
		<guid isPermaLink="false">http://selkowitz.org/response-point-vs-talkswitch-a-comparison-of-small-business-phone-systems/#comment-13564</guid>
		<description>Your site and posts are very interesting ! Thanks for providing such a great resource. With so many junk sites out there it's refreshing to find one with valuable, useful information ! I'll be back to read regularly !
Thanks,
Jeanine</description>
		<content:encoded><![CDATA[<p>Your site and posts are very interesting ! Thanks for providing such a great resource. With so many junk sites out there it&#8217;s refreshing to find one with valuable, useful information ! I&#8217;ll be back to read regularly !<br />
Thanks,<br />
Jeanine</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Vic</title>
		<link>http://selkowitz.org/response-point-vs-talkswitch-a-comparison-of-small-business-phone-systems/#comment-13543</link>
		<dc:creator>Vic</dc:creator>
		<pubDate>Thu, 18 Jun 2009 08:11:37 +0000</pubDate>
		<guid isPermaLink="false">http://selkowitz.org/response-point-vs-talkswitch-a-comparison-of-small-business-phone-systems/#comment-13543</guid>
		<description>I don't see RP going anywhere.  Microsoft has a very long and dubious history whenever they veer away from their core strengths.  You mentioned that home phone thing Microsoft did long ago.  Perfect example.  Just because it runs on XP does not make it a core strength of Microsoft.  Not impressed that the they are obviously using standard PC hardware.  Too many ways they can try cut corners there.  Telco is not the PC industry.  The market does not respond well to ANY indication of unreliability.  Speaking of reliability,  Microsoft has less than stellar points there in the PC world.  In the Telco world it is nothing short of show stopping on multiple levels.

Even if you discount all those things.  There are fundamental business problems here.  Microsoft is currently going in about 20 different directions. They are trying to beat Google, they are trying to beat Nintendo, they are trying to dominate Enterprise UC with their Comm Server and the new Exchange with PBX features.

So with all those things going on it is hard to see how they can just walk in and make much of a long term dent in the small business PBX market that many many companies have been doing nothing but for decades.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t see RP going anywhere.  Microsoft has a very long and dubious history whenever they veer away from their core strengths.  You mentioned that home phone thing Microsoft did long ago.  Perfect example.  Just because it runs on XP does not make it a core strength of Microsoft.  Not impressed that the they are obviously using standard PC hardware.  Too many ways they can try cut corners there.  Telco is not the PC industry.  The market does not respond well to ANY indication of unreliability.  Speaking of reliability,  Microsoft has less than stellar points there in the PC world.  In the Telco world it is nothing short of show stopping on multiple levels.</p>
<p>Even if you discount all those things.  There are fundamental business problems here.  Microsoft is currently going in about 20 different directions. They are trying to beat Google, they are trying to beat Nintendo, they are trying to dominate Enterprise UC with their Comm Server and the new Exchange with PBX features.</p>
<p>So with all those things going on it is hard to see how they can just walk in and make much of a long term dent in the small business PBX market that many many companies have been doing nothing but for decades.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin Selkowitz</title>
		<link>http://selkowitz.org/response-point-vs-talkswitch-a-comparison-of-small-business-phone-systems/#comment-9420</link>
		<dc:creator>Kevin Selkowitz</dc:creator>
		<pubDate>Tue, 17 Jun 2008 18:34:16 +0000</pubDate>
		<guid isPermaLink="false">http://selkowitz.org/response-point-vs-talkswitch-a-comparison-of-small-business-phone-systems/#comment-9420</guid>
		<description>One other correction, I mentioned MAPI and I meant TAPI. TAPI is the telecom standard for click to dial and other computer/phone integration. 

I know TAPI is on the Talkswitch roadmap - I can't discuss timelines but its sooner than I expected!</description>
		<content:encoded><![CDATA[<p>One other correction, I mentioned MAPI and I meant TAPI. TAPI is the telecom standard for click to dial and other computer/phone integration. </p>
<p>I know TAPI is on the Talkswitch roadmap - I can&#8217;t discuss timelines but its sooner than I expected!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin Selkowitz</title>
		<link>http://selkowitz.org/response-point-vs-talkswitch-a-comparison-of-small-business-phone-systems/#comment-9419</link>
		<dc:creator>Kevin Selkowitz</dc:creator>
		<pubDate>Tue, 17 Jun 2008 18:07:27 +0000</pubDate>
		<guid isPermaLink="false">http://selkowitz.org/response-point-vs-talkswitch-a-comparison-of-small-business-phone-systems/#comment-9419</guid>
		<description>I've discussed flexible extension numbering with Talkswitch, I know its on the roadmap. 

I currently have the new 6.1 prerelease for Talkswitch Partners - I can tell you 6.1 voicemail to email does allow for save/delete from email - no more calling in to delete messages. After upgrading to 6.1 you need to do a bit more setup - but once that's done its great! Its also server agnostic - anything with POP and SMTP works fine. 

Certainly the availability of carrier grade SIP will vary by region. In Seattle 1.5Mb symmetrical DSL with a phone line (for the fax) is ~$60/month - a great connection for VoIP traffic. Also rolling out later this year is ethernet over copper which will be 5-30Mb symmetrical. 

My thoughts on T1s are if you're small (less than 10 lines) then PSTN is cheaper as long as you don't need DIDs. If you're bigger then the voice lines are cutting into a lot of the T1's bandwidth on an integrated T1. Once you hit bonded T1s, ethernet over copper will deliver more bang for the buck - word is 5Mb ethernet over copper will be in the pricing ballpark of bonded 3Mb T1s. 

I'm not saying T1s don't have a market, but depending on the region they've got a limited future.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve discussed flexible extension numbering with Talkswitch, I know its on the roadmap. </p>
<p>I currently have the new 6.1 prerelease for Talkswitch Partners - I can tell you 6.1 voicemail to email does allow for save/delete from email - no more calling in to delete messages. After upgrading to 6.1 you need to do a bit more setup - but once that&#8217;s done its great! Its also server agnostic - anything with POP and SMTP works fine. </p>
<p>Certainly the availability of carrier grade SIP will vary by region. In Seattle 1.5Mb symmetrical DSL with a phone line (for the fax) is ~$60/month - a great connection for VoIP traffic. Also rolling out later this year is ethernet over copper which will be 5-30Mb symmetrical. </p>
<p>My thoughts on T1s are if you&#8217;re small (less than 10 lines) then PSTN is cheaper as long as you don&#8217;t need DIDs. If you&#8217;re bigger then the voice lines are cutting into a lot of the T1&#8217;s bandwidth on an integrated T1. Once you hit bonded T1s, ethernet over copper will deliver more bang for the buck - word is 5Mb ethernet over copper will be in the pricing ballpark of bonded 3Mb T1s. </p>
<p>I&#8217;m not saying T1s don&#8217;t have a market, but depending on the region they&#8217;ve got a limited future.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve</title>
		<link>http://selkowitz.org/response-point-vs-talkswitch-a-comparison-of-small-business-phone-systems/#comment-9414</link>
		<dc:creator>Steve</dc:creator>
		<pubDate>Tue, 10 Jun 2008 22:16:36 +0000</pubDate>
		<guid isPermaLink="false">http://selkowitz.org/response-point-vs-talkswitch-a-comparison-of-small-business-phone-systems/#comment-9414</guid>
		<description>Thanks for the reply!  

I simply believe it would be trivial for Talkswitch to have flexible extensions.  Until they offer this, some of our customers will not make the jump, or seek other options (Cisco).

I have seen many SMBs embrace Windows Live Messenger for chatting, and those that have voicemail to email feature completely abandon the traditional "message button + pin code" method.  UC is just a matter of integrating all of these capabilities (+telephony) together.  I look forward to the 6.1 release to see how "improved" their voicemail to email really is, because last I checked, you had to delete the message on both the phone system and email seperately.

Although I agree with you in theory that SIP is the future, our problem is with the throttled/capped upload.  Most Canadian SMBs that we deal with are "stuck" with assymetrical "consumer" grade internet either because of the cost of commercial ISP (&#62;500$ for T1), distance issues (sdsl) or simply not available and/or expensive (Fiber).  We also have reliability concerns - no matter how much we all want ITSPs to replace BELL, most ISPs don't provide SLAs for the aforementioned internet access.  I would prefer to see inbound calls using traditional PSTN, and an offload (with quality metrics for automatic failover) of calls to ITSPs until we have better access.  Until we have that, offering a T1 solution makes sense to me.  If Cisco (SMB offering) and Allworx both have a T1 solution, then there must be a market.

That being said, I do agree with you that Talkswitch is a decent phone system, but IMHO, just shy of "great".

Let's hope the next version does that, nothing would make me happier.</description>
		<content:encoded><![CDATA[<p>Thanks for the reply!  </p>
<p>I simply believe it would be trivial for Talkswitch to have flexible extensions.  Until they offer this, some of our customers will not make the jump, or seek other options (Cisco).</p>
<p>I have seen many SMBs embrace Windows Live Messenger for chatting, and those that have voicemail to email feature completely abandon the traditional &#8220;message button + pin code&#8221; method.  UC is just a matter of integrating all of these capabilities (+telephony) together.  I look forward to the 6.1 release to see how &#8220;improved&#8221; their voicemail to email really is, because last I checked, you had to delete the message on both the phone system and email seperately.</p>
<p>Although I agree with you in theory that SIP is the future, our problem is with the throttled/capped upload.  Most Canadian SMBs that we deal with are &#8220;stuck&#8221; with assymetrical &#8220;consumer&#8221; grade internet either because of the cost of commercial ISP (&gt;500$ for T1), distance issues (sdsl) or simply not available and/or expensive (Fiber).  We also have reliability concerns - no matter how much we all want ITSPs to replace BELL, most ISPs don&#8217;t provide SLAs for the aforementioned internet access.  I would prefer to see inbound calls using traditional PSTN, and an offload (with quality metrics for automatic failover) of calls to ITSPs until we have better access.  Until we have that, offering a T1 solution makes sense to me.  If Cisco (SMB offering) and Allworx both have a T1 solution, then there must be a market.</p>
<p>That being said, I do agree with you that Talkswitch is a decent phone system, but IMHO, just shy of &#8220;great&#8221;.</p>
<p>Let&#8217;s hope the next version does that, nothing would make me happier.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin Selkowitz</title>
		<link>http://selkowitz.org/response-point-vs-talkswitch-a-comparison-of-small-business-phone-systems/#comment-9410</link>
		<dc:creator>Kevin Selkowitz</dc:creator>
		<pubDate>Sat, 07 Jun 2008 18:48:54 +0000</pubDate>
		<guid isPermaLink="false">http://selkowitz.org/response-point-vs-talkswitch-a-comparison-of-small-business-phone-systems/#comment-9410</guid>
		<description>I have to largely disagree with your concerns, but you also have to keep in mind Talkswitch is a product designed to fit 90% of small businesses - its not meant to be everything to everyone. 

Predefined extensions - yes, its occasionally a problem. But even non-fixed extensions doesn't guarantee no changes as most systems have ranges. We did one client recently with an old Partner ACS who's extensions were two digit - I don't know any modern system which does those. Then I had a client who's extensions from their Virtual PBX started at 3000, even Allworx limits 4 digit extensions to 1000-2999. 

T1/PRI isn't the future of scalability - its SIP trunking over dedicated carrier connections (not public internet). For example one local carrier is rolling out SIP trunks with unlimited LD for $29/line over a dedicated SDSL - something which seriously cuts costs over a T1/PRI. For those needing more bandwidth, another local carrier is rolling out 5-30Mb ethernet over copper with SIP trunks. Bottom line is the future is SIP and a 248vs or two is great for SIP. 

Unified Communications (UC) - this is always one of those vague things that most small businesses don't need. But Talkswitch has been improving with things like their Attendant Console w/ IM, and 6.1 improves their voicemail to email functionality which is the most desired UC feature. 

No MAPI - in two years I've only had one customer that seriously desired MAPI. MAPI is usually desired by companies with CRM and most small businesses don't have it. That may change in the coming years, but Talkswitch will adapt and updates are free for life. 

Conference calls - external conference services make a lot more sense than internal conference bridges for most companies. We sell a system with a conference bridge option (Allworx) so you have to pay for that feature plus extra lines - you'll need enough lines for everyone to call in. Unless your business conferences all the time, keeping additional lines around just isn't worth it. Go to http://www.freeconferencecall.com/ and conference call for free - no software licenses and no extra lines. 

No one can say for sure how fast the Response Point team will move, but lets look at some other major Microsoft products. 5 years to release Vista after XP. Only three service packs to XP in 6 years. 5 years from Internet Explorer 6 to 7. 

On the flip side Talkswitch introduced 6.0 in February 2008 and is releasing the new 6.1 in June 2008. 

Talkswitch is a terrific phone system for small businesses that need great functionality at a great price. Allworx is a terrific phone system for every feature under the sun. Response Point may be great later...we'll see.</description>
		<content:encoded><![CDATA[<p>I have to largely disagree with your concerns, but you also have to keep in mind Talkswitch is a product designed to fit 90% of small businesses - its not meant to be everything to everyone. </p>
<p>Predefined extensions - yes, its occasionally a problem. But even non-fixed extensions doesn&#8217;t guarantee no changes as most systems have ranges. We did one client recently with an old Partner ACS who&#8217;s extensions were two digit - I don&#8217;t know any modern system which does those. Then I had a client who&#8217;s extensions from their Virtual PBX started at 3000, even Allworx limits 4 digit extensions to 1000-2999. </p>
<p>T1/PRI isn&#8217;t the future of scalability - its SIP trunking over dedicated carrier connections (not public internet). For example one local carrier is rolling out SIP trunks with unlimited LD for $29/line over a dedicated SDSL - something which seriously cuts costs over a T1/PRI. For those needing more bandwidth, another local carrier is rolling out 5-30Mb ethernet over copper with SIP trunks. Bottom line is the future is SIP and a 248vs or two is great for SIP. </p>
<p>Unified Communications (UC) - this is always one of those vague things that most small businesses don&#8217;t need. But Talkswitch has been improving with things like their Attendant Console w/ IM, and 6.1 improves their voicemail to email functionality which is the most desired UC feature. </p>
<p>No MAPI - in two years I&#8217;ve only had one customer that seriously desired MAPI. MAPI is usually desired by companies with CRM and most small businesses don&#8217;t have it. That may change in the coming years, but Talkswitch will adapt and updates are free for life. </p>
<p>Conference calls - external conference services make a lot more sense than internal conference bridges for most companies. We sell a system with a conference bridge option (Allworx) so you have to pay for that feature plus extra lines - you&#8217;ll need enough lines for everyone to call in. Unless your business conferences all the time, keeping additional lines around just isn&#8217;t worth it. Go to <a href="http://www.freeconferencecall.com/" rel="nofollow">http://www.freeconferencecall.com/</a> and conference call for free - no software licenses and no extra lines. </p>
<p>No one can say for sure how fast the Response Point team will move, but lets look at some other major Microsoft products. 5 years to release Vista after XP. Only three service packs to XP in 6 years. 5 years from Internet Explorer 6 to 7. </p>
<p>On the flip side Talkswitch introduced 6.0 in February 2008 and is releasing the new 6.1 in June 2008. </p>
<p>Talkswitch is a terrific phone system for small businesses that need great functionality at a great price. Allworx is a terrific phone system for every feature under the sun. Response Point may be great later&#8230;we&#8217;ll see.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steven</title>
		<link>http://selkowitz.org/response-point-vs-talkswitch-a-comparison-of-small-business-phone-systems/#comment-9403</link>
		<dc:creator>Steven</dc:creator>
		<pubDate>Wed, 04 Jun 2008 14:40:28 +0000</pubDate>
		<guid isPermaLink="false">http://selkowitz.org/response-point-vs-talkswitch-a-comparison-of-small-business-phone-systems/#comment-9403</guid>
		<description>We've been looking for an SMB IP PBX solution, and found that the market does not really offer anything robust. I've had the opportunity to work with Talkswitch, and found several major weaknesses in its offering:

1. Predefined extensions.  This means any SMB with an existing phone system will need to change any/all marketing documents and business cards to reflect changes in extensions.

2. Talkswitch also lacks scalability.  To use a T1 (which makes sense to replace 8+ analog line installs).  To use a T1, you need additional hardware that essentially breaks a T1 into analog circuits.  16 extensions per box.

Other lacking features:
No UC, no MAPI (integrate with Exchange), 3rd party softphone and a messy application for configuring the units. No transcoding (G711 - G729), no conference calls beyond 3 members

Why I find Microsoft a more credible long term option, is that they will move faster than Talkswitch, offer flexible and international options, and eventually true MAPI integration with Exchange.  It wasn't until recently that Talkswitch offered French and Spanish (6.0).  Talkswitch does not offer MAPI integration, and does not seem to acknowledge UC in its future.  

That Response Point isn't mature, isn't a big surprise, after all it is a version "1".

Either way, the market is ready for some solid competition from Microsoft.  Perhaps Talkswitch will awaken from its slumber and get moving again.

I can only advise potential buyers of an IP PBX solution to shop around first.  Cisco Unified 500, Allworx, Trixbox are also potential options.  Although Cisco is quite a bit more expensive than a Talkswitch, the capabilities are clearly superior, as well as offering switching, routing, firewalling, vpn, wireless options to boot.</description>
		<content:encoded><![CDATA[<p>We&#8217;ve been looking for an SMB IP PBX solution, and found that the market does not really offer anything robust. I&#8217;ve had the opportunity to work with Talkswitch, and found several major weaknesses in its offering:</p>
<p>1. Predefined extensions.  This means any SMB with an existing phone system will need to change any/all marketing documents and business cards to reflect changes in extensions.</p>
<p>2. Talkswitch also lacks scalability.  To use a T1 (which makes sense to replace 8+ analog line installs).  To use a T1, you need additional hardware that essentially breaks a T1 into analog circuits.  16 extensions per box.</p>
<p>Other lacking features:<br />
No UC, no MAPI (integrate with Exchange), 3rd party softphone and a messy application for configuring the units. No transcoding (G711 - G729), no conference calls beyond 3 members</p>
<p>Why I find Microsoft a more credible long term option, is that they will move faster than Talkswitch, offer flexible and international options, and eventually true MAPI integration with Exchange.  It wasn&#8217;t until recently that Talkswitch offered French and Spanish (6.0).  Talkswitch does not offer MAPI integration, and does not seem to acknowledge UC in its future.  </p>
<p>That Response Point isn&#8217;t mature, isn&#8217;t a big surprise, after all it is a version &#8220;1&#8243;.</p>
<p>Either way, the market is ready for some solid competition from Microsoft.  Perhaps Talkswitch will awaken from its slumber and get moving again.</p>
<p>I can only advise potential buyers of an IP PBX solution to shop around first.  Cisco Unified 500, Allworx, Trixbox are also potential options.  Although Cisco is quite a bit more expensive than a Talkswitch, the capabilities are clearly superior, as well as offering switching, routing, firewalling, vpn, wireless options to boot.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
