Cisco Cisco TelePresence Management Suite (TMS) Version 15
Appendix 2: Migration Paths to CMR Hybrid
This appendix describes how to migrate previous solution deployments, to the preferred architecture. This
release of CMR Hybrid uses the CMR Premises release 4.0 architecture which has two recommended
deployment architectures for conferencing infrastructure:
n
Conferencing infrastructure connected to Unified CM. This is the preferred architecture.
n
Conferencing infrastructure connected to Cisco VCS.
For new (first-time) deployments the Unified CM-connected deployment should be implemented.
For existing audio and video deployments which do not match either of the two scenarios, we recommend
that deployments are migrated to the CMR Premises 4.0 deployment using the 4.0 recommended code
levels, as this is the tested architecture on top of which new feature developments are being planned.
To move to the CMR Hybrid deployment:
n
Start by moving the infrastructure to the CMR Premises 4.0 standard.
n
Then, if endpoints are currently registered to the Cisco VCS, move the endpoints that can register to
Unified CM to Unified CM.
Prerequisites
CMR Premises release 4.0 makes use of endpoint caller IDs, displaying them in Roster lists and, if enabled,
on-screen in conferences in TelePresence Server ActivePresence mode. We recommend reviewing the dial
plan to ensure that displayed caller IDs are meaningful. For more information, see Provisioning Display
Supported software versions for CMR Hybrid
Product
Recommended Minimum
Notes
TelePresence Server
4.1
4.1
TelePresence Server bridges must be
configured for remote management by
the TelePresence Conductor.
TelePresence Conductor
XC3.0
XC3.0
MCU
4.5
4.5
Cisco VCS
X8.5
X8.2. (required for
Microsoft Lync)
Table 27: Required software versions
Cisco Collaboration Meeting Rooms (CMR) Hybrid Configuration Guide (TMS 14.6 - WebEx WBS29.11)
Page 247 of 254
Appendix 2: Migration Paths to CMR Hybrid
Managing System Behavior