Cisco Cisco TelePresence Video Communication Server Expressway
OCS Relay configuration of “Lync Gateway” Cisco VCS(s)
Cisco VCS Deployment Guide: Microsoft Lync 2010 and Cisco VCS X6.1
Page 44 of 81
OCS Relay configuration of “Lync Gateway”
Cisco VCS(s)
Cisco VCS(s)
The OCS Relay function allows personal video endpoints to appear in a similar manner to an MXP
endpoint registered directly to Lync Server with the same credentials as an existing OC user, but still
maintain the benefits of having the endpoint register to the Cisco VCS which is designed to support
video calling.
endpoint registered directly to Lync Server with the same credentials as an existing OC user, but still
maintain the benefits of having the endpoint register to the Cisco VCS which is designed to support
video calling.
The OCS Relay function also means that the user credentials are no longer needed on each individual
video endpoint. This is possible because the Cisco VCS is configured as a trusted application to Lync
Server. This simplifies the long term endpoint management since passwords do not need to be
updated on the endpoints.
video endpoint. This is possible because the Cisco VCS is configured as a trusted application to Lync
Server. This simplifies the long term endpoint management since passwords do not need to be
updated on the endpoints.
What does OCS Relay do?
When enabled, OCS Relay registers FindMe™ users that are in the same domain as Lync Server to
Lync Server so that they appear like Lync users to other Lync devices.
This means that if a Lync user registers to Lync Server , and FindMe™ registers that same ID to Lync
Server, when the ID is called by another Lync device, the call will be forked to both the registered Lync
client and also to Cisco VCS’s FindMe™. This means that Lync and all video endpoints configured as
primary devices in the FindMe™ will ring when called at the Lync address.
Without OCS Relay and FindMe™, Lync Server will not fork the call to Cisco VCS, but:
Lync Server so that they appear like Lync users to other Lync devices.
This means that if a Lync user registers to Lync Server , and FindMe™ registers that same ID to Lync
Server, when the ID is called by another Lync device, the call will be forked to both the registered Lync
client and also to Cisco VCS’s FindMe™. This means that Lync and all video endpoints configured as
primary devices in the FindMe™ will ring when called at the Lync address.
Without OCS Relay and FindMe™, Lync Server will not fork the call to Cisco VCS, but:
If a Lync is registered with the called address then just that Lync will ring.
If there is no Lync registered and there is no static domain route for this call then the call will just
fail.
fail.
Note: Lync Server only allows FindMe™ users to register if the FindMe™ ID being registered is a
valid user in the Lync Server Active Directory (in the same way that Lync users can only register if
they have a valid account enabled in the Lync AD).
valid user in the Lync Server Active Directory (in the same way that Lync users can only register if
they have a valid account enabled in the Lync AD).
OCS Relay also allows the presence of FindMe™ users registered to Lync Server to provide ‘in-
call’ as well as ‘available’ and ‘off-line’ status to Lync users.
call’ as well as ‘available’ and ‘off-line’ status to Lync users.
•
Endpoint devices and FindMe™ entries that are not registered to Lync Server can only
communicate ‘available’ and ‘off-line’ status to Lync Server, even if OCS Relay is enabled.
communicate ‘available’ and ‘off-line’ status to Lync Server, even if OCS Relay is enabled.
•
Without OCS Relay and FindMe™, Cisco VCS can only communicate ‘available’ and ‘off-line’
status to Lync Server.
status to Lync Server.
Note: The “Lync gateway” Cisco VCS(s) must host the presence server for the domain of the Lync
Server network (test-customer.com) in order for presence to be provided to Lync Server.
Presence of a FindMe™ entry can only be provided if the presence status of the device(s) in the
active location of the FindMe™ entry are hosted on the “Lync gateway” Cisco VCS(s). The “Lync
gateway” Cisco VCS(s) must therefore also host the presence server for the domain of the video
network (vcs.domain).
If FindMe™ entries contain multiple devices in the active location, Cisco VCS will aggregate the
presence of those devices whose presence is hosted on the “Lync gateway” Cisco VCS(s) and
present the appropriate overall presence status.
Server network (test-customer.com) in order for presence to be provided to Lync Server.
Presence of a FindMe™ entry can only be provided if the presence status of the device(s) in the
active location of the FindMe™ entry are hosted on the “Lync gateway” Cisco VCS(s). The “Lync
gateway” Cisco VCS(s) must therefore also host the presence server for the domain of the video
network (vcs.domain).
If FindMe™ entries contain multiple devices in the active location, Cisco VCS will aggregate the
presence of those devices whose presence is hosted on the “Lync gateway” Cisco VCS(s) and
present the appropriate overall presence status.
Use of FindMe™ also allows any endpoint that is referred to in the FindMe™ to take on the caller ID of
that FindMe™ entry. This means that whichever video endpoint makes the call, the receiving Lync and
video endpoints will see the call as having come from the FindMe™ ID. This is especially useful when
the called party wishes to return the call; the return call calls the FindMe™ ID resulting in all endpoints
that FindMe™ entry. This means that whichever video endpoint makes the call, the receiving Lync and
video endpoints will see the call as having come from the FindMe™ ID. This is especially useful when
the called party wishes to return the call; the return call calls the FindMe™ ID resulting in all endpoints