Manual

OCS Relay configuration of “OCS gateway” Cisco VCS(s)

Note: If SIP registration proxy mode is already configured as ProxyToAny this is also suitable.

12. Ensure that presence is enabled (as described in Enabling MOC clients to see the presence

status of endpoints registered on Cisco VCS Control).

13.

Ensure that the OCS Neighbor zone is set up as described in”“OCS gateway” Cisco VCS Control

config

uration (2)”.

(If the OCS Neighbor zone is named anything other than “OCS”, then the CPL below must be

updated to match the OCS Neighbor zone Name.)

14. Modify the “To OCS” Search rule set up in “Set up a Search rule to select what gets routed to the

OCS zone”, replace the rule with:

Priority

Source Any

Mode AliasPatternMatch

Pattern type Regex

Pattern string

(.*)ocs\.(test-customer\.com.*)

Pattern behavior Replace

Replace string

\1\2

On successful match Stop

Target Zone OCS

Note: If multiple domains are supported on OCS, only a single domain can be used with OCS

Relay functionality (Cisco VCS registering as a MOC) – other domains should be handled using

the Search rules configured previously.

15. Click Save.

Note: The CPL below converts calls to test-customer.com destined for OCS to calls to

ocs.test-customer.com.

A second Search rule, as defined in ‘OCS receiving Presence from non-OCS Relay FindMe™ entries,

here there is

a transform for Cisco VCS devices accessing OCS’ (in Appendix 7 – Presence with

and without transforms) is not necessary for OCS to see the pre

sence of OCS Relay FindMe™ users.

The OCS Relay communicates presence to OCS using Microsoft signaling.

16. Create a text file containing the following call policy (CPL), but replacing test-customer.com with

the name of the sip domain shared between the Cisco VCS and OCS (and also the zone name if

not “OCS”). Save it as a “.txt” file.

Cisco VCS Deployment Guide: Microsoft OCS 2007 R1 and R2 and Cisco VCS X5.2 Page 61 of 92