Cisco Cisco TelePresence Video Communication Server Expressway
Introduction
Cisco VCS Deployment Guide: Microsoft OCS 2007 R2, Lync 2010 and Cisco VCS X7.1
Page 9 of 104
For calls into OCS/Lync (from whichever video endpoint the user wants to call from) to have a Caller
ID / call back ID that works, FindMe must re-write the caller ID of calls to OCS/Lync with the relevant
OCS/Lync SIP user ID. For FindMe to be able to do this, calls must be routed through the Cisco VCS
holding the relevant FindMe; having an “OCS/Lync gateway” helps funnel all calls through the correct
place.
ID / call back ID that works, FindMe must re-write the caller ID of calls to OCS/Lync with the relevant
OCS/Lync SIP user ID. For FindMe to be able to do this, calls must be routed through the Cisco VCS
holding the relevant FindMe; having an “OCS/Lync gateway” helps funnel all calls through the correct
place.
OCS/Lync Server can only send calls to:
Cisco VCSs that have “same domain” FindMe users registered to the OCS/Lync Server;
OCS/Lync Server sends the call to the VCS that is registering that user
OCS/Lync Server sends the call to the VCS that is registering that user
a single FQDN (though this may have a round robin DNS address to support a cluster of Cisco
VCSs for resilience) for calls to MCUs accessible via a static domain route defined in OCS/Lync
Server.
VCSs for resilience) for calls to MCUs accessible via a static domain route defined in OCS/Lync
Server.
OCS/Lync server will only accept messages that it has been configured to trust. Having a dedicated
“OCS/Lync gateway” VCS or Cisco VCS cluster also limits the number of trusted devices that need to
be configured in OCS/Lync, as every device that sends SIP messages to OCS/Lync server needs to
be explicitly listed as a trusted host in OCS/Lync server.
“OCS/Lync gateway” VCS or Cisco VCS cluster also limits the number of trusted devices that need to
be configured in OCS/Lync, as every device that sends SIP messages to OCS/Lync server needs to
be explicitly listed as a trusted host in OCS/Lync server.
“OCS/Lync gateway” and multiple OCS/Lync domains
If OCS/Lync supports multiple domains, and the video network is to support these domains as well, it
is recommended that one “OCS/Lync gateway” VCS or VCS cluster is used to handle each domain as
B2BUA only supports registering a single domain.
is recommended that one “OCS/Lync gateway” VCS or VCS cluster is used to handle each domain as
B2BUA only supports registering a single domain.
If some domains are not used in the video network, but need calls to be routed to them, there does not
need to be a “OCS/Lync gateway” VCS for those domains – Search rules can be added to support
routing to these domains.
need to be a “OCS/Lync gateway” VCS for those domains – Search rules can be added to support
routing to these domains.
If different OCS/Lync SIP domains are handled by different “OCS/Lync gateway” VCSs or VCS
clusters, take care to ensure that each “OCS/Lync gateway” VCS or VCS cluster is authoritative
for the presence information that is required for the B2BUA registered FindMe users for that one
shared domain and all endpoints that are referenced by those FindMe entries.
clusters, take care to ensure that each “OCS/Lync gateway” VCS or VCS cluster is authoritative
for the presence information that is required for the B2BUA registered FindMe users for that one
shared domain and all endpoints that are referenced by those FindMe entries.
Multiple “OCS/Lync gateway” per OCS/Lync domain
Apart from when the VCSs are in a single “OCS/Lync gateway” cluster, this is not a recommended
architecture as calls from one video endpoint to another video endpoint that is called via its OCS/Lync
domain will get routed via OCS/Lync rather than directly through the video infrastructure; this will
cause users to lose video functionality like duo video and far end camera control, and also possibly
lose encryption and video quality.
architecture as calls from one video endpoint to another video endpoint that is called via its OCS/Lync
domain will get routed via OCS/Lync rather than directly through the video infrastructure; this will
cause users to lose video functionality like duo video and far end camera control, and also possibly
lose encryption and video quality.
MCUs for ad-hoc conferences from OCS/Lync
Registering each possible conference ID to the OCS/Lync Server via B2BUA FindMe registrations is
sometimes unachievable or impractical based on the number of URIs that need to be registered.
sometimes unachievable or impractical based on the number of URIs that need to be registered.
In this case, it is recommended that MCUs that are used for conferences that OCS/Lync clients can
dial, are registered using their own domain (different from any other video or OCS/Lync domain) to the
video network VCSs.
dial, are registered using their own domain (different from any other video or OCS/Lync domain) to the
video network VCSs.
When configured in their own domain, the MCU conferences can be available via registered FindMe
entries – if set up – and can be accessible via a static route configured on OCS/Lync for this MCU
domain. If regional MCUs exist, the MCUs should have regional domains. For ad-hoc conferences
routed via the OCS/Lync static domain route:
entries – if set up – and can be accessible via a static route configured on OCS/Lync for this MCU
domain. If regional MCUs exist, the MCUs should have regional domains. For ad-hoc conferences
routed via the OCS/Lync static domain route:
If the conference is not underway presence status will be “Off-line”
If the conference has any participants, presence status will be “Available” (not “In-call)
Calling an MCU conference from a MOC/Lync device will require the MCU’s domain to be entered.