Manual

OCS Relay configuration of “OCS gateway” Cisco VCS(s)
OCS Relay configuration of “OCS gateway”
Cisco VCS(s)
The OCS Relay function allows personal video endpoints to appear in a similar manner to an MXP
endpoint registered directly to OCS 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 host to OCS. This
simplifies the long term endpoint management since passwords do not need to be updated on the
endpoints.
In which versions can I use OCS Relay?
OCS Relay functionality was introduced into Cisco VCS in version X4.1.
It needs OCS R2 or later to operate properly.
What does OCS Relay do?
When enabled, OCS Relay registers FindMe™ users that are in the same domain as OCS to OCS so
that they appear like MOC users to other MOC devices.
This means that if a MOC user registers to OCS, and FindMe™ registers that same ID to OCS, when
the ID is called by another MOC device, the call will be forked to both the registered MOC client and
also to Cisco VCS’s FindMe™. This means that MOC and all video endpoints configured as primary
devices in the FindMe™ will ring when called at the MOC address.
Without OCS Relay and FindMe™, OCS will not fork the call to Cisco VCS, but:
 if a MOC is registered with the called address then just that MOC will ring.
 if there is no MOC registered but there is a static domain route to the Cisco VCS for OCS’s
domain and OCS is R2 or later the call will be routed to Cisco VCS to handle.
 if there is no MOC registered and there is no static domain route for this call (or OCS is R1) then
the call will just fail.
Note: OCS only allows FindMe™ users to register if the FindMe™ ID being registered is a valid user
in the OCS Active Directory (in the same way that MOC users can only register if they have a valid
account enabled in the OCS AD).
 OCS Relay also allows the presence of FindMe™ users registered to OCS to provide ‘in-call’ as
well as ‘available’ and ‘off-line’ status to MOC users.
 Endpoint devices and FindMe™ entries that are not registered to OCS can only communicate
‘available’ and ‘off-line’ status to OCS, even if OCS Relay is enabled.
 Without OCS Relay and FindMe™, Cisco VCS can only communicate ‘available’ and ‘off-line’
status to OCS.
Note: The “OCS gateway” Cisco VCS(s) must host the presence server for the domain of the OCS
network (test-customer.com) in order for presence to be provided to OCS.
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 “OCS gateway” Cisco VCS(s). The “OCS
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
Cisco VCS Deployment Guide: Microsoft OCS 2007 R1 and R2 and Cisco VCS X5.2 Page 57 of 92