Cisco Cisco TelePresence Video Communication Server Expressway
Enabling endpoints registered on the video network to call MOC clients registered on OCS
6. Repeat steps 3 to 5 for all domains routable to or through the “OCS gateway” Cisco VCS(s),
including the domain shared between OCS and Cisco VCS (If there is a shared domain).
Note: Static routes should be set up for all domains handled by the Cisco VCS, including the domain
shared by Cisco VCS and OCS if Cisco VCS and OCS share the same domain.
shared by Cisco VCS and OCS if Cisco VCS and OCS share the same domain.
If OCS tries to route a call to the domain shared between OCS and Cisco VCS:
- OCS will first check all its registrations, both OCS MOC registrations and OCS Relay FindMe™
registrations registered to OCS. If any registration is found that matches the called URI the call
will be sent to that device, or if multiple registrations exist, the call will be forked to all registered
devices that match the URI.
- If there is no registration and OCS is OCS R2, OCS will then check the static domain routes
and if there is one for this domain OCS will route the call to the destination specified.
- OCS will first check all its registrations, both OCS MOC registrations and OCS Relay FindMe™
registrations registered to OCS. If any registration is found that matches the called URI the call
will be sent to that device, or if multiple registrations exist, the call will be forked to all registered
devices that match the URI.
- If there is no registration and OCS is OCS R2, OCS will then check the static domain routes
and if there is one for this domain OCS will route the call to the destination specified.
If OCS tries to route a call to a domain that is not shared between OCS and Cisco VCS:
- OCS (both R1 and R2) will check the static domain routes and if there is one for this domain
OCS will route the call to the destination specified.
- OCS (both R1 and R2) will check the static domain routes and if there is one for this domain
OCS will route the call to the destination specified.
Note: Although the primary access to end users registered on Cisco VCS may be via a specific
domain, providing static routes for other domains handled by Cisco VCS means that:
domain, providing static routes for other domains handled by Cisco VCS means that:
Endpoints in different domains that may call OCS can be called back using their ‘caller ID’ which
may have a domain other than the primary domain.
may have a domain other than the primary domain.
When using OCS Relay and OCS and Cisco VCS have the same domain for registered devices,
devices like MCUs and ISDN gateways which may register IDs in the same domain as OCS, but
not have FindMe™ IDs associated with them (e.g. because they are ad hoc conferences) will be
able to be called by OCS (if OCS is OCS R2).
devices like MCUs and ISDN gateways which may register IDs in the same domain as OCS, but
not have FindMe™ IDs associated with them (e.g. because they are ad hoc conferences) will be
able to be called by OCS (if OCS is OCS R2).
7. Repeat steps 2 to 6 for all pools that can directly communicate to Cisco VCS.
Configure OCS to make media encryption optional
By default OCS mandates the use of encrypted media. The headers used in OCS SRTP, however, are
different from those used by video network devices. Calls between the video network and OCS must
therefore use unencrypted media, unless you are using Cisco VCS version X5.2 or later with the
Enhanced OCS Collaboration option key and the connection between the Cisco VCS and OCS is
TLS.
different from those used by video network devices. Calls between the video network and OCS must
therefore use unencrypted media, unless you are using Cisco VCS version X5.2 or later with the
Enhanced OCS Collaboration option key and the connection between the Cisco VCS and OCS is
TLS.
If the Cisco VCS is not using the Enhanced OCS Collaboration option key or is not connected to
OCS via TLS, then the Microsoft Office Communications Server 2007 zone configuration in the “OCS
gateway” Cisco VCS(s) handles the signaling to ensure that media encryption is not negotiated. OCS
needs to be configured to accept calls where media is not encrypted.
OCS via TLS, then the Microsoft Office Communications Server 2007 zone configuration in the “OCS
gateway” Cisco VCS(s) handles the signaling to ensure that media encryption is not negotiated. OCS
needs to be configured to accept calls where media is not encrypted.
For the OCS Director pool and every OCS FEP pool:
1. Select the Pool.
1. Select the Pool.
2. Select
Properties > Pool Properties.
3. Change
Encryption level from Require Encryption to Supports Encryption
4. Click
Apply.
Cisco VCS Deployment Guide: Microsoft OCS 2007 R1 and R2 and Cisco VCS X5.2
Page 44 of 92