Live communication server SRV records??
Live communication server (LCS) 2005 SRV records can be a daunting task to setup properly. SIP is the communications protocol for LCS. SIP URIs are id’s given to contacts/users that use the SIP service. LCS uses SIP and when you enter in your user id/sign-in name for Communicator or Windows Messenger, you are giving the client application your SIP URI. If you want to use the automatic configuration for communicator or Windows Messenger, you have to rely on your DNS infrastructure. The client uses your SIP URI from the account information provided (email@example.com) then performs a DNS query to find a matching host record for that SIP URI. This is called a SIP Namespace. There are 4 different types of SRV records that can be used, depending on your environment and client specifications. Perusing Microsoft’s documentation on this subject is a bit challenging, but once you overcome the lack of documentation and incorrect syntax, it can be accomplished. If you have a mixed environment, such as Windows Messenger 5.0 and Office Communicator clients, it’s best to configure several types of SRV records within your DNS environment. Below is a list of SRV records and their purpose.
|LCS Client SRV record for internal use Windows |
(Local Windows Messenger clients (legacy))
|_sip._tls.domain (Should point at the LCS Pool)|
|LCS Access Proxy configuration per domain (off site)||
_sip._tls._tcp.domain (Should point at the Access Proxy FQDN)
|LCS Client SRV record for internal use clients|
(Local Office Communicator clients)
_sipinternaltls._tcp.domain (Should point at the LCS Pool)
|LCS Federated Services|
(Federated partnership with Microsoft)
_sipfederationtls._tcp.domain (Should point at the Access Proxy FQDN)
In my test lab, here is an example of an SRV record I created. This services automatic configurations for internal Office Communicator and Office 2007 Live Meeting clients. Here is a good blog that walks thru the creation steps. (Click here)