Manual

Appendix 7 – Presence with and without transforms
Appendix 7 – Presence with and without
transforms
Presence SIP messages often have extra parameters in the URI header after the user-id@domain. In
order to ensure that these extra parameters do not cause the search rules to fail to match, a ‘.*’ is
appended to pattern strings.
OCS receiving Presence from non-OCS Relay FindMe™ entries,
where there is no
transform for Cisco VCS devices accessing
OCS
For example, where to reach a MOC [e-mail] the video endpoint calls
[e-mail]
The documentation above specifies the required configuration to allow calls and presence to be routed
when the video network device calls the MOC endpoint’s registered name to call it.
OCS receiving Presence from non-OCS Relay FindMe™ entries,
where there is
a transform for Cisco VCS devices accessing
OCS
For example, where to reach a MOC [e-mail] the video endpoint calls
[e-mail]
If a search rule has been created with a domain name transform, for example to allow callers to dial
[e-mail] as well / instead of [e-mail], an additional search rule
with a pattern string for the raw domain (in this example .*@test-customer.com.*) must be added to
allow presence messages through (OCS requests that the presence Notifies are sent to the OCS’s
raw domain).
Allowing calls to the raw domain as well as the pre-transform domain is also useful for endpoints
supporting dial back to caller. The calling party’s caller identity will contain the raw domain information.
For example, if non OCS Relay set Search Rule 1 as follows:
Priority 100
Source Any
Mode AliasPatternMatch
Pattern type Regex
Pattern string
(.*)@ocs.domain
Pattern behavior Replace
Replace string
\[e-mail]
On successful match Stop
Target zone OCS
Add a second search rule:
Priority 100
Source Any
Mode AliasPatternMatch
Cisco VCS Deployment Guide: Microsoft OCS 2007 R1 and R2 and Cisco VCS X5.2 Page 77 of 92