Migration Paths

Migration Overview

You can migrate previous solution deployments, to the preferred architecture. This release of CMR Hybrid uses the CMR Premises release 5.0 architecture which has two recommended deployment architectures for conferencing infrastructure:

  • Conferencing infrastructure connected to Unified CM. This is the preferred architecture.

  • 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 5.0 deployment using the 5.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:

  • Start by moving the infrastructure to the CMR Premises 5.0 standard.

  • Then, if endpoints are currently registered to the Cisco VCS, move the endpoints that can register to Unified CM to Unified CM.

Migration Prerequisites

CMR Premises release 5.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 Names Across the Solution in Provisioning Endpoint Display Names.

Supported Software Versions for Migration

Table 1 Supported Software Versions

Product

Recommended

Minimum

Notes

TelePresence Server

4.2

4.1

TelePresence Server bridges must be configured for remote management by the TelePresence Conductor.

TelePresence Conductor

XC4.0

XC3.0

XC3.0.2 required for TSP audio

MCU

4.5

4.5

Cisco VCS

X8.5.3

X8.5

Cisco VCS-for H.323 registration

X8.5.3

X8.5

Cisco Expressway

X8.5.3

X8.5

Cisco TMS

15.0

14.6

Cisco TMSPE

1.5

1.4

Unified CM

10.5(2)SU2

10.5(2)SU1

Migrate a Cisco Unified Communications Manager-only System to CMR Hybrid

Procedure
    Step 1   Upgrade Unified CM to the recommended version for CMR Hybrid.
    Step 2   Add TelePresence Conductor to Unified CM and deploy bridges trunked to TelePresence Conductor; these components support all conference types.
    Step 3   Upgrade endpoint software to the version supplied with Unified CM.
    Step 4   Upgrade Cisco TMS/Cisco TMSPE to ensure support for Personal CMR / rendezvous and Scheduling.
    Step 5   If WebEx participants are to be included in calls, ensure that Unified CM is running at least code version 9.1(2)SU2 and update Unified CM configuration to support Early Offer.
    Step 6   To allow participants external to the company network to join conferences, deploy Cisco Expressway-C and Cisco Expressway-E for the firewall traversal.
    Step 7   If Lync interop is required add a Cisco Expressway-C / Cisco VCS Control to be the gateway to the Microsoft Lync infrastructure. Version X8.5 or later is required. (See the Cisco VCS / Cisco Expressway deployment guides to identify whether Cisco VCS Control or Cisco Expressway-C is most appropriate for your needs.)
    Step 8   If you want to add Legacy and H.323 endpoints to the solution, add a Cisco VCS Control onto which those endpoints can register.

    Separate Audio and Video Endpoints

    Some Unified CM deployments use a Unified CM for audio-only endpoints and a separate Unified CM for video endpoints. The ideal solution is to run both systems at the same Unified CM version, and in that case you should follow the Migrate a Cisco Unified Communications Manager-only System to CMR Hybrid instructions above.

    If there are reasons why audio and video endpoints need to register to separate Unified CMs and they need to run different versions, then, before proceeding, verify with your account manager that the two Unified CM versions are acceptable in the deployment. In this case follow the Migrate a Cisco Unified Communications Manager-only System to CMR Hybrid instructions above on the video Unified CM.

    Migrate Cisco Unified Communications Manager and Cisco VCS to CMR Hybrid

    Procedure
      Step 1   Upgrade Cisco VCS to the recommended version for CMR Hybrid.
      Step 2   Upgrade Unified CM to the recommended version for CMR Hybrid.
      Step 3   Move / keep TelePresence Conductor connected to Unified CM with bridges trunked to TelePresence Conductor.
      Step 4   If the TelePresence Conductor is moved from Cisco VCS, ensure that the search rules that used to send calls to the TelePresence Conductor under Cisco VCS now send the calls to Unified CM and that the Unified CM forwards these calls to TelePresence Conductor.
      Step 5   Cisco VCS architecture can remain as configured for firewall traversal, Lync interop and Legacy / H.323 endpoint registration.
      Step 6   Migrate endpoints that can register to Unified CM to Unified CM, upgrading software to the required versions for this solution release.

      Comparison of Endpoint Capabilities

      The following table compares the capabilities of endpoints registered to Unified CM and endpoints registered to Cisco VCS.

      Table 2 Endpoint Capabilities

      Capability

      Registered to Unified CM

      Registered to Cisco VCS

      Phone books

      TMS phone books Hierarchical directory

      TMS phone books Hierarchical directory

      Management

      Managed by Unified CM & Prime Collaboration suite Provisioned by Unified CM

      Managed by Cisco TMS

      Provisioned by Cisco TMS

      Conference scheduling

      Managed by Cisco TMS

      Managed by Cisco TMS

      Firewall traversal

      Using Cisco Expressway-C and Cisco Expressway-E

      Using Cisco VCS Expressway

      Conference escalation

      Ad hoc

      Multiway

      Features and Version Dependencies

      Table 3 Features and Version Dependencies

      Feature

      Versions Required

      CMR provisioning and user portal

      XC 3.0, TMS 14.6, TMSPE 1.4

      TelePresence Server scalability improvements

      TS 4.1

      Basic TelePresence Server Cascade

      TS 4.1, XC 3.0, TMSPE 1.4

      TelePresence Server User Experience Improvements

      TS 4.1

      TelePresence Server Serviceability Improvements

      TS 4.1

      Single alias for host/guest conference, with role determined by PIN

      TS 4.1, XC 3.0, TMS 14.6, TMSPE 1.4

      Associated Products, Versions, and Features

      Table 4 Associated Products, Versions, and Features

      Product

      Versions

      Features

      MCU

      4.5

      Minimum version for 4.0 operation. Adds:

      • ClearPath (Flux 1)

      • Separate content channel for encrypted SIP participants

      • Domain added for out dial requests without a domain—needed for WebEx out dial (for TSP conferenced audio) when the MCU is trunked to Unified CM.

      Unified CM

      10.5(2)SU1

      Minimum version supported

      Ad hoc bridge now configured as data connection and explicit SIP trunk

      Cisco VCS

      X8.5

      Minimum version for Lync gateway operation in this release of CMR Hybrid

      Cisco TMS

      14.6

      Minimum version for WebEx in CMR Hybrid and Host / Guest PIN

      For more details about the CMR Premises solution and deployment, refer to the following guides: