Cisco Cisco TelePresence Video Communication Server Expressway
OCS Relay configuration of “OCS gateway” Cisco VCS(s)
Display name
Full name of this user
Phone number
E164 number to use when outdialing to a gateway
FindMe ID
URI with OCS’s domain that will register to OCS as though it were
a MOC
a MOC
Principal device
address
address
Routable endpoint URI / E164 or H.323 ID to call when this
FindMe™ is called.
FindMe™ is called.
Initial password
Password needed by the FindMe™ user to log in to Cisco VCS to
administer this account
administer this account
Confirm password
As Initial password
23. Make sure the domain shared with the OCS is DNS resolvable, usually by adding the OCS server
as a DNS server address on the Cisco VCS. See “Configure the DNS” above.
24. Configure the OCS Relay App on the Cisco VCS:
a. Go to the OCS Relay page (Applications->OCS Relay).
b. Configure the following fields:
OCS Relay mode
On
OCS Relay domain
test-customer.com
OCS Relay routing
prefix
prefix
ocs
(the default value)
Note: OCS Relay can take up to 3 minutes to pick up a new OCS Relay FindMe™ entry and register
it. If a number of entries get deleted and the same number get added, it can take OCS Relay up to
60 minutes to observe the change in identities and update the registrations.
it. If a number of entries get deleted and the same number get added, it can take OCS Relay up to
60 minutes to observe the change in identities and update the registrations.
Verify FindMe™ accounts are registered
After the FindMe™ accounts have been configured for at least 60 seconds:
1. Go to the OCS Relay status page (Status > Applications > OCS Relay).
1. Go to the OCS Relay status page (Status > Applications > OCS Relay).
2. Verify the following for each FindMe™:
Registrations state is Registered
Subscription state is Active
Presence state is Online
If the states are not as expected, verify that the FindMe™ and OCS (Active Directory) registered
names are identical.
names are identical.
Testing the Configuration
Test that calls to OCS registered FindMe™ users from Cisco VCS registered endpoints fork to
Cisco VCS registered endpoints listed in the FindMe™ entry and also to the MOC client for this
user.
Cisco VCS registered endpoints listed in the FindMe™ entry and also to the MOC client for this
user.
Test that calls to OCS registered FindMe™ users from MOC clients fork to the MOC client and
also to Cisco VCS registered endpoints listed in the FindMe™ entry for this user.
also to Cisco VCS registered endpoints listed in the FindMe™ entry for this user.
Test that the presence of Cisco VCS endpoints is reflected in MOC presence – log out of the
MOC client for a user and check that the Off-Line, Available and In-Call status of the Cisco VCS
endpoint listed in the relevant FindMe™ is presented as the presence state in a MOC client
watching presence for that user.
MOC client for a user and check that the Off-Line, Available and In-Call status of the Cisco VCS
endpoint listed in the relevant FindMe™ is presented as the presence state in a MOC client
watching presence for that user.
Cisco VCS Deployment Guide: Microsoft OCS 2007 R1 and R2 and Cisco VCS X5.2
Page 63 of 92