Cisco Cisco TelePresence Video Communication Server Expressway
Introduction
Cisco VCS Deployment Guide: Microsoft OCS 2007 R2, Lync 2010 and Cisco VCS X7.0
Page 13 of 104
Configuring VCS versions prior to X7.0
To configure VCS versions prior to VCS X7.0, use the appropriate deployment guide:
Cisco TelePresence Video Communication Server Microsoft Lync 2010 Deployment Guide (X6.1)
Cisco TelePresence Video Communication Server Microsoft OCS 2007 R1 and R2 Deployment
Guide (X5.2)
Guide (X5.2)
Summary of configuration process
This document describes how to configure the OCS R2, Lync 2010 and the Cisco VCS Control version
X7.x in B2BUA mode so that calls can be made from:
X7.x in B2BUA mode so that calls can be made from:
SIP and H.323 video endpoints registered in the video network to other SIP and H.323 video
endpoints registered in that same video network.
endpoints registered in that same video network.
Microsoft Office Communicator (MOC) clients / Lync clients registered on OCS/Lync server to
other MOC/Lync clients registered on that OCS/Lync server.
other MOC/Lync clients registered on that OCS/Lync server.
SIP and H.323 video endpoints registered in the video network to MOC/Lync clients registered on
OCS/Lync.
OCS/Lync.
MOC/Lync clients registered on OCS/Lync server to SIP and H.323 video endpoints registered in
the video network.
the video network.
It also describes how to enable presence so that MOC/Lync clients can see the presence status of
endpoints registered in the video network.
endpoints registered in the video network.
The configuration process describes each of these stages separately, so that individual stages can be
implemented and tested before moving on to the next.
implemented and tested before moving on to the next.
Different structures for OCS/Lync
OCS/Lync environments have a number of building blocks, and so they may be constructed in many
ways.
ways.
A full scale OCS/Lync deployment is likely to use OCS/Lync Director, Hardware Load Balancers
(HLBs), Front End Processors (FEPs) in enterprise pools, and a redundant AD server.
(HLBs), Front End Processors (FEPs) in enterprise pools, and a redundant AD server.
For Lync installations, Microsoft are recommending that DNS may be used in place of hardware load
balancing for routing SIP traffic. Microsoft say:
balancing for routing SIP traffic. Microsoft say:
DNS Load Balancing
Microsoft Lync Server 2010 introduces DNS load balancing, a software solution that can greatly reduce the administration
overhead for load balancing on your network. DNS load balancing balances the network traffic that is unique to Lync Server
2010, such as SIP traffic and media traffic.
overhead for load balancing on your network. DNS load balancing balances the network traffic that is unique to Lync Server
2010, such as SIP traffic and media traffic.
If you choose to deploy DNS load balancing, your organization’s administration overhead for hardware load balancers will be
greatly reduced. Additionally, complex troubleshooting of problems related to misconfiguration of load balancers for SIP traffic
will be eliminated, and you can prevent server connections so that you can take servers offline. DNS load balancing also
ensures that hardware load balancer problems do not affect such elements of SIP traffic as the basic routing of calls.
greatly reduced. Additionally, complex troubleshooting of problems related to misconfiguration of load balancers for SIP traffic
will be eliminated, and you can prevent server connections so that you can take servers offline. DNS load balancing also
ensures that hardware load balancer problems do not affect such elements of SIP traffic as the basic routing of calls.
Using DNS load balancing may also enable you to purchase lower-cost hardware load balancers than if you used the hardware
load balancers for all types of traffic. DNS load balancing is supported for Front End pools, Edge Server pools, Director pools,
and stand-alone Mediation Server pools.
load balancers for all types of traffic. DNS load balancing is supported for Front End pools, Edge Server pools, Director pools,
and stand-alone Mediation Server pools.