<?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 for Tin Cups and String: The Convergent Microsoft UC Blog</title>
	<atom:link href="http://www.tincupsandstring.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.tincupsandstring.com</link>
	<description>All about our Microsoft Unified Communications practice (you know, OCS 2007 and Exchange UM) plus whatever else we feel like.</description>
	<pubDate>Thu, 09 Sep 2010 01:20:44 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on Wave 14 Series: High Availability by Richard Brynteson</title>
		<link>http://www.tincupsandstring.com/2010/08/09/wave-14-series-high-availability/comment-page-1/#comment-1333</link>
		<dc:creator>Richard Brynteson</dc:creator>
		<pubDate>Thu, 12 Aug 2010 15:18:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.tincupsandstring.com/?p=308#comment-1333</guid>
		<description>Derek,

I haven't seen any guidance from Microsoft and when/if they do publish something it will most likely need to be very generic and talk about the role of the PSTN provider.  The answer is ultimately going to be, you will need to talk to multiple players potentially.  Typically you would have two PSTN connections at each site.  The first trick is to make sure they are the same provider.  In many cases, this can't be done.  So in those situations you may end up having to look at a SIP provider and seeing what options they provide for failover purposes.  If it is done via a SIP provider, you may just need the provider to cut over DID's from the remote location to the primary location in the event of a failure.  However, this process, depending on the provider could take time.  This is where I think all of the providers fail a little bit because moving DID's from one area to the other in a quick manor just doesn't seem all that possible for some of them.

I know that isn't quite the answer you were looking for but it's the start.  I think in the next few years as the industry moves further beyond the traditional PBX we will start to see other/better options.

Richard</description>
		<content:encoded><![CDATA[<p>Derek,</p>
<p>I haven&#8217;t seen any guidance from Microsoft and when/if they do publish something it will most likely need to be very generic and talk about the role of the PSTN provider.  The answer is ultimately going to be, you will need to talk to multiple players potentially.  Typically you would have two PSTN connections at each site.  The first trick is to make sure they are the same provider.  In many cases, this can&#8217;t be done.  So in those situations you may end up having to look at a SIP provider and seeing what options they provide for failover purposes.  If it is done via a SIP provider, you may just need the provider to cut over DID&#8217;s from the remote location to the primary location in the event of a failure.  However, this process, depending on the provider could take time.  This is where I think all of the providers fail a little bit because moving DID&#8217;s from one area to the other in a quick manor just doesn&#8217;t seem all that possible for some of them.</p>
<p>I know that isn&#8217;t quite the answer you were looking for but it&#8217;s the start.  I think in the next few years as the industry moves further beyond the traditional PBX we will start to see other/better options.</p>
<p>Richard</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Exchange 2010 and Outlook 2003 SP3 Users by Justin McMillen</title>
		<link>http://www.tincupsandstring.com/2010/04/20/exchange-2010-and-outlook-2003-sp3-users/comment-page-1/#comment-1330</link>
		<dc:creator>Justin McMillen</dc:creator>
		<pubDate>Thu, 12 Aug 2010 01:43:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.tincupsandstring.com/?p=255#comment-1330</guid>
		<description>Hi, this saved my life. I have been pulling my hair out for days on this problem. Couldnt figure out why some people could connect to calendars and others couldnt. Thanks alot.</description>
		<content:encoded><![CDATA[<p>Hi, this saved my life. I have been pulling my hair out for days on this problem. Couldnt figure out why some people could connect to calendars and others couldnt. Thanks alot.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Exchange 2010 and Outlook 2003 SP3 Users by Outlook 2003 with Exchange 2010 Shared Calendar Issue</title>
		<link>http://www.tincupsandstring.com/2010/04/20/exchange-2010-and-outlook-2003-sp3-users/comment-page-1/#comment-1329</link>
		<dc:creator>Outlook 2003 with Exchange 2010 Shared Calendar Issue</dc:creator>
		<pubDate>Thu, 12 Aug 2010 01:39:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.tincupsandstring.com/?p=255#comment-1329</guid>
		<description>[...] kit out and opening up my 5th floor window for a quick death, I finally found a solution. Richard Brynteson at Tin Cups and Strings is a god among [...]</description>
		<content:encoded><![CDATA[<p>[...] kit out and opening up my 5th floor window for a quick death, I finally found a solution. Richard Brynteson at Tin Cups and Strings is a god among [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Wave 14 Series: High Availability by Derek Johnson</title>
		<link>http://www.tincupsandstring.com/2010/08/09/wave-14-series-high-availability/comment-page-1/#comment-1314</link>
		<dc:creator>Derek Johnson</dc:creator>
		<pubDate>Tue, 10 Aug 2010 12:38:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.tincupsandstring.com/?p=308#comment-1314</guid>
		<description>This is cool and I do know Enterprise Voice, but not the actual PBX side.  Do you know if Microsoft has or will have instructions on what is needed at the Telephony Side to allow for the PRI connected to the branch site with the SBA and what is required at the PRI side at the main location with the Pool to allow the PBX to allow both PRIs to handle this type of failover with the DIDs?</description>
		<content:encoded><![CDATA[<p>This is cool and I do know Enterprise Voice, but not the actual PBX side.  Do you know if Microsoft has or will have instructions on what is needed at the Telephony Side to allow for the PRI connected to the branch site with the SBA and what is required at the PRI side at the main location with the Pool to allow the PBX to allow both PRIs to handle this type of failover with the DIDs?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Wave 14 Series: High Availability by Tin Cups and String: The Convergent Microsoft UC Blog » Wave 14 Series: High Availability &#171; JC&#8217;s Blog-O-Gibberish</title>
		<link>http://www.tincupsandstring.com/2010/08/09/wave-14-series-high-availability/comment-page-1/#comment-1313</link>
		<dc:creator>Tin Cups and String: The Convergent Microsoft UC Blog » Wave 14 Series: High Availability &#171; JC&#8217;s Blog-O-Gibberish</dc:creator>
		<pubDate>Tue, 10 Aug 2010 11:57:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.tincupsandstring.com/?p=308#comment-1313</guid>
		<description>[...] Tin Cups and String: The Convergent Microsoft UC Blog » Wave 14 Series: High&#160;Availability  Posted on August 10, 2010 by johnacook   http://www.tincupsandstring.com/2010/08/09/wave-14-series-high-availability/ [...]</description>
		<content:encoded><![CDATA[<p>[...] Tin Cups and String: The Convergent Microsoft UC Blog » Wave 14 Series: High&nbsp;Availability  Posted on August 10, 2010 by johnacook   <a href="http://www.tincupsandstring.com/2010/08/09/wave-14-series-high-availability/" rel="nofollow">http://www.tincupsandstring.com/2010/08/09/wave-14-series-high-availability/</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Wave 14 Series: New Features by Tin Cups and String: The Convergent Microsoft UC Blog &#187; Wave 14 Series: High Availability</title>
		<link>http://www.tincupsandstring.com/2010/07/27/wave-14-series-new-features/comment-page-1/#comment-1309</link>
		<dc:creator>Tin Cups and String: The Convergent Microsoft UC Blog &#187; Wave 14 Series: High Availability</dc:creator>
		<pubDate>Mon, 09 Aug 2010 18:25:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.tincupsandstring.com/?p=298#comment-1309</guid>
		<description>[...] Wave 14 Series: New Features  [...]</description>
		<content:encoded><![CDATA[<p>[...] Wave 14 Series: New Features  [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Integrating OCS with Vocera - A packaged UC solution from Convergent by UC App Store &#171; Unified Communications</title>
		<link>http://www.tincupsandstring.com/2010/06/08/integrating-ocs-with-vocera-a-packaged-uc-solution-from-convergent/comment-page-1/#comment-1302</link>
		<dc:creator>UC App Store &#171; Unified Communications</dc:creator>
		<pubDate>Sun, 08 Aug 2010 09:07:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.tincupsandstring.com/?p=270#comment-1302</guid>
		<description>[...] OCS and Vocera &#8211; Convergent &#8211; check out the demo video here [...]</description>
		<content:encoded><![CDATA[<p>[...] OCS and Vocera &#8211; Convergent &#8211; check out the demo video here [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Wave 14 Series: New Features by Rolando Winterstein</title>
		<link>http://www.tincupsandstring.com/2010/07/27/wave-14-series-new-features/comment-page-1/#comment-1300</link>
		<dc:creator>Rolando Winterstein</dc:creator>
		<pubDate>Sat, 07 Aug 2010 18:56:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.tincupsandstring.com/?p=298#comment-1300</guid>
		<description>Anyone have a good reference to DR planning ?</description>
		<content:encoded><![CDATA[<p>Anyone have a good reference to DR planning ?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Phones for OCS Wave 14 from Aastra and Polycom, plus SIP integration from NET by Suresh Tatavarthy</title>
		<link>http://www.tincupsandstring.com/2010/04/03/phones-for-ocs-wave-14-from-aastra-and-polycom/comment-page-1/#comment-1289</link>
		<dc:creator>Suresh Tatavarthy</dc:creator>
		<pubDate>Wed, 04 Aug 2010 04:53:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.tincupsandstring.com/?p=206#comment-1289</guid>
		<description>SmartSIP is now available for the following phone models:
- Cisco 7960/7940/7911/7906
- Polycom SoundPoint IP 301/550/650
- Aastra 6731i/6757i
- Linksys SPA942
- Ascom IP-DECT with 9d24 handset
- Analog phones through NET gateways
- Softphones X-Lite
We plan to extend our base of supported phones.

Thank you
Suresh Tatavarthy
NET Product Management &amp; Marketing
Suresh_Tatavarthy@net.com</description>
		<content:encoded><![CDATA[<p>SmartSIP is now available for the following phone models:<br />
- Cisco 7960/7940/7911/7906<br />
- Polycom SoundPoint IP 301/550/650<br />
- Aastra 6731i/6757i<br />
- Linksys SPA942<br />
- Ascom IP-DECT with 9d24 handset<br />
- Analog phones through NET gateways<br />
- Softphones X-Lite<br />
We plan to extend our base of supported phones.</p>
<p>Thank you<br />
Suresh Tatavarthy<br />
NET Product Management &amp; Marketing<br />
<a href="mailto:Suresh_Tatavarthy@net.com">Suresh_Tatavarthy@net.com</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Phones for OCS Wave 14 from Aastra and Polycom, plus SIP integration from NET by rdxvoip</title>
		<link>http://www.tincupsandstring.com/2010/04/03/phones-for-ocs-wave-14-from-aastra-and-polycom/comment-page-1/#comment-1288</link>
		<dc:creator>rdxvoip</dc:creator>
		<pubDate>Tue, 03 Aug 2010 16:08:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.tincupsandstring.com/?p=206#comment-1288</guid>
		<description>Looks like EHS is missing. so back to "cool" technology -  handset lifters...</description>
		<content:encoded><![CDATA[<p>Looks like EHS is missing. so back to &#8220;cool&#8221; technology -  handset lifters&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
