Manual
OCS Relay configuration of “OCS gateway” Cisco VCS(s)
presence of those devices whose presence is hosted on the “OCS 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 which ever video endpoint makes the call, the receiving MOC
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 relating to this FindMe™ and any MOC users registered with this ID all ringing
simultaneously – rather than the return call being addressed directly back to the single endpoint that
made the call.
OCS Relay and a cluster of Cisco VCSs
From Cisco VCS X5.0 OCS Relay can be enabled in a cluster of Cisco VCSs. When used in a cluster
of Cisco VCSs, the OCS Relay FindMe™ users will be shared across cluster peers (using an
algorithmic distribution scheme). Each cluster peer will register its own OCS Relay FindMe™ users to
OCS. When calls are made from OCS to OCS Relay FindMe™ users OCS will send the call to the
Cisco VCS peer that registered that user – hence the calls are statically load-shared across the Cisco
VCS peers.
Note: calls to Video endpoint IDs that are not OCS Relay FindMe™ user IDs will not match a
registered user, and so will be routed by the static domain route configured in OCS. These calls to
non-OCS Relay FindMe™ endpoints will therefore be delivered to a single Cisco VCS peer or a range
of Cisco VCS peers (slowly rotating) if a round-robin DNS address is configured in OCS. (When using
round-robin, OCS rotates peers approximately once per 5 seconds - this helps with resilience, but is
not fast enough to provide effective load sharing.
Configure OCS Relay and FindMe™
It is best practice to keep the video endpoints in their own domain, and just have the FindMe™ users
on the “OCS gateway” Cisco VCS with the same domain as OCS. This avoids any confusion as to
what functionality will be received for each entity. When a call arrives for the FindMe™ user, FindMe™
will forward calls appropriately to the defined endpoints, whichever domain they are in.
For example, when mary.jones@test-customer.com is called, the call will fork to the MOC client with
the same name, and also to mary.jones.office@vcs.domain and mary.jones.external@vcs.domain
(assuming that these two vcs.domain devices are listed as primary devices in Mary Jones’ FindMe™.
It is strongly recommended that the user is created on OCS first and then FindMe™ accounts created
on Cisco VCS 5 to 10 minutes later, when the user is fully available on OCS.
Active Directory configuration
Ensure that Active Directory user accounts exist for all FindMe™ accounts on the “OCS gateway”
Cisco VCS(s) that will register to OCS (FindMe™ accounts that have the same domain as OCS).
On the PC running the Active Directory for OCS users:
1. Select Start > Control Panel > Administrative Tools > Active Directory Users and
Computers.
2. Select the ‘Users’ folder under the required domain:
Cisco VCS Deployment Guide: Microsoft OCS 2007 R1 and R2 and Cisco VCS X5.2 Page 58 of 92