Manual

Appendix 4 – Known interoperating limitations
DTMF
MOC R1 generates in-band DTMF only – this is good as it will work with any recipient requiring DTMF,
whether the call is delivered to the endpoint as a SIP call or whether the call is delivered interworked
to H.323.
MOC R2 generates RFC2833 DTMF only – this causes problems if the OCS call is interworked by
Cisco VCS to H.323. Although Cisco VCS interworks the signaling, it does not interwork out-of-band
DTMF, instead the Cisco VCS interworking function does not accept the request from OCS to use
RFC 2833 telephone events. With MOC R2, if a recipient H.323 device needs DTMF key entry (e.g.
for PIN entry) rather than supplying DTMF as in-band tones when the DTMF selection is made, it just
reports to the user that it cannot send the RFC 2833 tones.
Microsoft Server
In Microsoft Server 2008 R2 the TLS configuration has changed. This has been seen to cause
problems with Cisco VCS connecting to OCS over TLS, and also cause problems for OCS
components to talk to one another if connecting over TLS.
At this stage it is recommended that Microsoft Server 2008 R2 is not used as the server to install OCS
components on.
Further details on changes and limitations imposed when using Microsoft Server 2008 R2 may be
found on the Microsoft support site: http://support.microsoft.com/kb/
982021/.
Microsoft Servers recommended are:
 Microsoft Server 2003
 Microsoft Server 2003 R2
 Microsoft Server 2008
Call forward from MOC to a Cisco VCS FindMe™ or endpoint
results in a ‘loop detected’ call.
If a call from Cisco VCS is made to a MOC Client which has a forward to another Cisco VCS
registered endpoint or a FindMe™ then Cisco VCS sees this as a looped call.
FindMe™ Caller ID set to FindMeID causes calls from MOC to
fail
If:
 FindMe™ Caller ID is set to FindMeID and
 a MOC client’s URI is in the active location of a FindMe™ and
 a call is made from that MOC to a SIP destination
the call will fail because OCS does not like the caller ID (From: header) being modified.
If the call is interworked on the “OCS gateway” Cisco VCS, the call will work as required.
Best practice is that a MOC endpoint should never be included as a FindMe™ device. If MOC devices
and video endpoints are to be related, OCS Relay should be used and a FindMe™ ID which is the
same as the MOC URI should be created.
Cisco VCS Deployment Guide: Microsoft OCS 2007 R1 and R2 and Cisco VCS X5.2 Page 74 of 92