Cisco Cisco TelePresence Video Communication Server Expressway
Introduction
Cisco VCS Deployment Guide: Microsoft Lync 2010 and Cisco VCS X6.1
Page 8 of 81
The version of operating system that Lync Server runs on must be the 64-bit editions of the
following operating systems:
following operating systems:
•
Windows Server 2008 R2 Standard/Enterprise/Datacenter operating system
•
Windows Server 2008 Standard/Enterprise/Datacenter operating system with Service Pack 2
(SP2)
(SP2)
Why add a “Lync Gateway” Cisco VCS Control?
The “Lync Gateway” Cisco VCS is an interface between an existing working video network and the
Microsoft Lync system. There are a number of settings that need to be configured on the “Lync
Gateway” that are different from the recommended configurations for standard video routing Cisco
VCSs. For instance the “Lync Gateway” Cisco VCS requires that Call routed mode be set to Always,
as the Cisco VCS has to modify the Lync Server SIP signaling to make it suitable for standard video
endpoints, MCUs etc. The knock-on effect of this is that call licenses are always used on this “Lync
Gateway” Cisco VCS. It also requires interworking to be On rather than Registered only which can
cause calls to be interworked when they need not.
Microsoft Lync system. There are a number of settings that need to be configured on the “Lync
Gateway” that are different from the recommended configurations for standard video routing Cisco
VCSs. For instance the “Lync Gateway” Cisco VCS requires that Call routed mode be set to Always,
as the Cisco VCS has to modify the Lync Server SIP signaling to make it suitable for standard video
endpoints, MCUs etc. The knock-on effect of this is that call licenses are always used on this “Lync
Gateway” Cisco VCS. It also requires interworking to be On rather than Registered only which can
cause calls to be interworked when they need not.
Having the separate “Lync Gateway” Cisco VCS and making it the video network presence server also
allows this Cisco VCS or cluster of Cisco VCS peers to handle the subscriptions and presence
requests from Lync Server for video network users. Handling them in the “Lync Gateway” prevents the
Lync Server presence requests being “spammed” into the existing video network and adversely
affecting the run time operation of the previously working system.
allows this Cisco VCS or cluster of Cisco VCS peers to handle the subscriptions and presence
requests from Lync Server for video network users. Handling them in the “Lync Gateway” prevents the
Lync Server presence requests being “spammed” into the existing video network and adversely
affecting the run time operation of the previously working system.
OCS Relay requires dedicated CPL. If CPL is required anywhere else in the network (for example, to
limit which calls are allowed to be routed to ISDN gateways or other resources) it is hard to merge
different CPL scripts.
limit which calls are allowed to be routed to ISDN gateways or other resources) it is hard to merge
different CPL scripts.
For FindMe™ to re-write the caller ID, calls must be routed through the Cisco VCS holding the
relevant FindMe™; having a “Lync gateway” helps funnel all calls through the correct place.
relevant FindMe™; having a “Lync gateway” helps funnel all calls through the correct place.
Lync Server can only send calls to:
Cisco VCSs that have “same domain” OCS Relay FindMe™ users registered to the Lync Server,
and
and
a single FQDN (though this may have a round robin DNS address to support a cluster of Cisco
VCSs for resilience) for calls to endpoints accessible via a static domain route defined in Lync
Server
VCSs for resilience) for calls to endpoints accessible via a static domain route defined in Lync
Server
If Lync Server supports multiple domains, all domains can be handled by a single “Lync gateway”
Cisco VCS / cluster, or one “Lync gateway” Cisco VCS / cluster can be used for each domain.
Cisco VCS / cluster, or one “Lync gateway” Cisco VCS / cluster can be used for each domain.
If different Lync Server domains are handled by different “Lync gateway” Cisco VCSs or Cisco
VCS clusters, take care to ensure that each “Lync gateway” Cisco VCS or Cisco VCS cluster is
authoritative for the presence information that is required for the OCS Relay FindMe™ users and
all endpoints that are referenced by those FindMe™ entries.
VCS clusters, take care to ensure that each “Lync gateway” Cisco VCS or Cisco VCS cluster is
authoritative for the presence information that is required for the OCS Relay FindMe™ users and
all endpoints that are referenced by those FindMe™ entries.
If one “Lync gateway” Cisco VCS or Cisco VCS cluster is used, note that only one domain can be
handled by OCS Relay.
handled by OCS Relay.
Having a dedicated “Lync gateway” Cisco VCS or Cisco VCS cluster also limits the number of trusted
devices that need to be configured in Lync Server.
devices that need to be configured in Lync Server.
Although in the example, nothing is shown registered to the “Lync gateway” Cisco VCS, it is often a
good place to register an MCU if significant numbers of Lync callers are going to be sharing
conferences with standard video endpoint users.
good place to register an MCU if significant numbers of Lync callers are going to be sharing
conferences with standard video endpoint users.
Small test and demo networks?
For small test and demo networks, video endpoints may be registered to the “Lync gateway” Cisco
VCS Control, the small Video Network being controlled by the same Cisco VCS that is the interface to
Lync Server.
VCS Control, the small Video Network being controlled by the same Cisco VCS that is the interface to
Lync Server.