<?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: DNS Records and Office Communicator Automatic Client Sign-In</title>
	<atom:link href="http://blog.insideocs.com/2008/08/19/dns-records-and-office-communicator-automatic-client-sign-in/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.insideocs.com/2008/08/19/dns-records-and-office-communicator-automatic-client-sign-in/</link>
	<description>Microsoft Office Communications Server - Tips, Tricks, and Insight</description>
	<lastBuildDate>Fri, 12 Mar 2010 07:59:21 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.3</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Communicator Automatic Sign-In when SIP Domain Different from AD Domain &#171; Inside OCS</title>
		<link>http://blog.insideocs.com/2008/08/19/dns-records-and-office-communicator-automatic-client-sign-in/comment-page-1/#comment-318</link>
		<dc:creator>Communicator Automatic Sign-In when SIP Domain Different from AD Domain &#171; Inside OCS</dc:creator>
		<pubDate>Mon, 14 Sep 2009 21:14:21 +0000</pubDate>
		<guid isPermaLink="false">http://ocsbuzz.wordpress.com/?p=3#comment-318</guid>
		<description>[...] OCS server or pool to sign into via DNS SRV records (this process is well documented – my posting DNS Records and Office Communicator Automatic Client Sign-In describes it). Normally the SRV record resolves to the FQDN of the OCS standard edition host or OCS [...]</description>
		<content:encoded><![CDATA[<p>[...] OCS server or pool to sign into via DNS SRV records (this process is well documented – my posting DNS Records and Office Communicator Automatic Client Sign-In describes it). Normally the SRV record resolves to the FQDN of the OCS standard edition host or OCS [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The OCS 2007 Automatic Sign-In Troubleshooting Tool V2.0 &#171; Inside OCS</title>
		<link>http://blog.insideocs.com/2008/08/19/dns-records-and-office-communicator-automatic-client-sign-in/comment-page-1/#comment-169</link>
		<dc:creator>The OCS 2007 Automatic Sign-In Troubleshooting Tool V2.0 &#171; Inside OCS</dc:creator>
		<pubDate>Wed, 12 Aug 2009 05:11:15 +0000</pubDate>
		<guid isPermaLink="false">http://ocsbuzz.wordpress.com/?p=3#comment-169</guid>
		<description>[...] DNS Records and Office Communicator Automatic Client Sign-In [...]</description>
		<content:encoded><![CDATA[<p>[...] DNS Records and Office Communicator Automatic Client Sign-In [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The OCS 2007 Automatic Sign-In Troubleshooting Tool V1.0 &#171; Inside OCS</title>
		<link>http://blog.insideocs.com/2008/08/19/dns-records-and-office-communicator-automatic-client-sign-in/comment-page-1/#comment-95</link>
		<dc:creator>The OCS 2007 Automatic Sign-In Troubleshooting Tool V1.0 &#171; Inside OCS</dc:creator>
		<pubDate>Fri, 24 Jul 2009 21:39:58 +0000</pubDate>
		<guid isPermaLink="false">http://ocsbuzz.wordpress.com/?p=3#comment-95</guid>
		<description>[...] DNS Records and Office Communicator Automatic Client Sign-In [...]</description>
		<content:encoded><![CDATA[<p>[...] DNS Records and Office Communicator Automatic Client Sign-In [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Automatic Office Communicator Sign-In (Part 1 &#8211; The Correct DNS Service Location (SRV) Record) &#171; Inside OCS</title>
		<link>http://blog.insideocs.com/2008/08/19/dns-records-and-office-communicator-automatic-client-sign-in/comment-page-1/#comment-96</link>
		<dc:creator>Automatic Office Communicator Sign-In (Part 1 &#8211; The Correct DNS Service Location (SRV) Record) &#171; Inside OCS</dc:creator>
		<pubDate>Fri, 24 Jul 2009 21:07:16 +0000</pubDate>
		<guid isPermaLink="false">http://ocsbuzz.wordpress.com/?p=3#comment-96</guid>
		<description>[...] the SIP domain of the user attempting to sign-in. The SRV record must be of a particular format. See my previous blog post on what the format of the DNS record should be. The SIP domain is the right-hand-side of the [...]</description>
		<content:encoded><![CDATA[<p>[...] the SIP domain of the user attempting to sign-in. The SRV record must be of a particular format. See my previous blog post on what the format of the DNS record should be. The SIP domain is the right-hand-side of the [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Troubleshooting Microsoft Office Communicator Issues 101 &#171; Inside OCS</title>
		<link>http://blog.insideocs.com/2008/08/19/dns-records-and-office-communicator-automatic-client-sign-in/comment-page-1/#comment-97</link>
		<dc:creator>Troubleshooting Microsoft Office Communicator Issues 101 &#171; Inside OCS</dc:creator>
		<pubDate>Mon, 29 Jun 2009 19:50:54 +0000</pubDate>
		<guid isPermaLink="false">http://ocsbuzz.wordpress.com/?p=3#comment-97</guid>
		<description>[...] previous post, DNS Records and Office Communicator Automatic Client Sign-In, summarizes how Communicator uses DNS to connect to the [...]</description>
		<content:encoded><![CDATA[<p>[...] previous post, DNS Records and Office Communicator Automatic Client Sign-In, summarizes how Communicator uses DNS to connect to the [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bill Dishman</title>
		<link>http://blog.insideocs.com/2008/08/19/dns-records-and-office-communicator-automatic-client-sign-in/comment-page-1/#comment-94</link>
		<dc:creator>Bill Dishman</dc:creator>
		<pubDate>Wed, 17 Sep 2008 21:37:51 +0000</pubDate>
		<guid isPermaLink="false">http://ocsbuzz.wordpress.com/?p=3#comment-94</guid>
		<description>Hi.

I have a pretty large deployment in progress. One thing I dont really understand.

I have one external srv record.  _sip._tls.. This points to my server in a datacenter in Atlanta.

I also want a pool in the UK, Australia, and Singapore.

Since I only have one srv record externally for my domain, that means for an internet user, they will always start first by hitting my datacenter in Atlanta, then the director takes over and sends the traffic back to Singapore?

In Singapore, UK, Australia I will have a front end server, a director an edge server, and isa firewall and possibly a mediation server.</description>
		<content:encoded><![CDATA[<p>Hi.</p>
<p>I have a pretty large deployment in progress. One thing I dont really understand.</p>
<p>I have one external srv record.  _sip._tls.. This points to my server in a datacenter in Atlanta.</p>
<p>I also want a pool in the UK, Australia, and Singapore.</p>
<p>Since I only have one srv record externally for my domain, that means for an internet user, they will always start first by hitting my datacenter in Atlanta, then the director takes over and sends the traffic back to Singapore?</p>
<p>In Singapore, UK, Australia I will have a front end server, a director an edge server, and isa firewall and possibly a mediation server.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
