Drive to collab vcs to cucm migration
This presentation is the property of its rightful owner.
Sponsored Links
1 / 32

Drive to Collab VCS to CUCM Migration PowerPoint PPT Presentation


  • 128 Views
  • Uploaded on
  • Presentation posted in: General

Drive to Collab VCS to CUCM Migration. Technical T raining. Agenda. Objective Roles of CUCM and VCS VCS to CUCM Migration Considerations Migration Activities users dial plan directory Registration Licenses License Migration Caveats/Limitations. VCS  UCM - VSEM. V.

Download Presentation

Drive to Collab VCS to CUCM Migration

An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -

Presentation Transcript


Drive to collab vcs to cucm migration

Drive to CollabVCS to CUCM Migration

Technical Training


Agenda

Agenda

  • Objective

  • Roles of CUCM and VCS

  • VCS to CUCM Migration Considerations

  • Migration Activities

    • users

    • dial plan

    • directory

    • Registration

    • Licenses

  • License Migration

  • Caveats/Limitations


  • Vcs ucm vsem

    VCS  UCM - VSEM

    V

    Enable Video Only (VCS) customers to experience Cisco Collaboration suite

    Migrate VCS installed base to Cisco UCM

    • License, Service & Hardware offers

    • Endpoints Promotions

    • Migration Bundles

    • Partner Incentives

    • Partner & Field Enablement

    • Partner Trainings on UCM

    • Migration Support & Services

    S

    Why & How

    Comprehensive Enablement

    Attractive Promotions & Incentives

    • Value Proposition & Opportunity

    • Migration Guides & Tools

    • Case Studies & Success Stories

    • License Migration

    12-18 months

    Number of VCS  UCM Migrations

    E

    Migration Bookings in $

    12-18 months

    M


    Cisco unified communications manager 10 5

    Cisco Unified Communications Manager 10.5

    Single, Unified platform for feature-rich Voice and Video

    Control


    Cucm and vcs roles

    CUCM and VCS Roles

    • VCS

    • VCS provides firewall traversal, legacy support, and H.323 interworking functionality

    • There are now four possible operating modes of the VCS:

    • VCS-Control

    • VCS-Expressway

    • Expressway-Core (new)

    • Expressway-Edge (new)

    • CUCM

      • UC Manager is Cisco’s strategic call control platform, CUCM is the Single cluster for voice or video device, including legacy and 3rd party endpoints

      • CUCM Integrated provisioning, management, phonebooks, and conferencing


    Vcs roles legacy and new

    VCS Roles – Legacy and New

    • New - firewall traversal using “Expressway” Core and Edge

    • Legacy - VCS “Control” version is still supported for registering H.323, legacy Tandberg, and 3rd party endpoints

    • The original VCS-Expressway is also still supported for B2B, Jabber Video for TelePresence (a.k.a. Movi) and Webex enabled TelePresence

    • Devices CANNOT directly register on either Expressway-Core or Edge. They register on UCM via SIP proxy.

    • Both solutions work as a strict pairing

    VCS

    Control

    VCS

    Expressway

    Firewall Traversal

    UCM

    Optional

    Legacy Solution

    Expressway

    Core

    Expressway

    Edge

    Firewall Traversal

    Trusted certificates are required

    CSR10 Expressway Solution

    SIP Trunk

    Signaling Proxy (“SIP line side”)


    Migration considerations

    Migration Considerations


    Benefits of endpoint registration on cucm

    Benefits of Endpoint Registration on CUCM

    • Key factors in this decision are the endpoint type/model and how they connect to the call control network- Directly via L2/L3?, WAN/VPN? Internet?

    • CUCM 10.5 makes it easier to register endpoints on UCM, and fully manage them, no matter how they are networked (VPN or Expressway)!

    * TMS can schedule any endpoint into a conference, but OBTP is only available to campus devices


    Ucm registration benefits

    UCM Registration Benefits

    • DX70, DX80, DX650 and SX10 can only be registered to UCM

    • Endpoints registered on CUCM gain the following key features and benefits:

    • Single Pt. of Dial Plan Administration

    • Single Call Admission Control Domain

    • Geographic redundancy

    • CUCM Phones features :

    • Voice Mail indicator /Call Forward All /Consultative Transfer

    • Shared Lines /SNR /Ad Hoc conferencing/CTI Control/BLF

    • CSS/Partitions /Hunt Groups/ Music on Hold/ Announcements


    Cucm and vcs capability comparison

    CUCM and VCS Capability Comparison


    Migration scenarios

    Migration Scenarios


    Drive to collab vcs to cucm migration

    Scenario #1a

    Video Call Control Architecture Today:

    Internet

    • VCS only for Call Control

    • All Endpoints Compatible with UCM

    VCS E

    VCS C

    Recommended Call Control Architecture:

    • Add BE6000 or BE7000 (UCM & Exp C)

    • Add BE6000 (Exp E)

    • Migrate Endpoints from VCS to UCM

    • Leverage existing MCU & TMS

    BE6000

    or CE

    BE6000/BE7000

    Internet

    UCM

    • Exp C

    Exp E

    Virtual Exp C & E could reside in the same server


    Drive to collab vcs to cucm migration

    Scenario #1b

    Video Call Control Architecture Today:

    Internet

    • VCS only for Call Control

    • All Endpoints Compatible with UCM

    VCS E

    VCS C

    Recommended Call Control Architecture:

    BE6000/BE7000

    • Add BE6000 or BE7000 (UCM)

    • Upgrade VCS C & E to Version 8.2

    • Migrate SIP Endpoints from VCS to UCM

    • Leverage existing MCU & TMS

    Internet

    UCM

    VCS E

    V8.2

    • VCS C

    • V8.2


    Drive to collab vcs to cucm migration

    • Scenario #2a

    Video Call Control Architecture Today:

    • VCS only for Call Control

    • Some Endpoints Compatible with UCM

    • Some Legacy H.323 Endpoints

    Internet

    VCS E

    VCS C

    Recommended Call Control Architecture:

    BE6000

    or CE

    BE6000/BE7000

    • Add BE6000 or BE7000 (UCM & Exp C)

    • Add BE6000 (Exp E)

    • Refresh H.323 EP with new low cost EP

    • Leverage existing MCU & TMS

    Internet

    UCM

    • Exp C

    Exp E

    Virtual Exp C & E could reside in the same server


    Drive to collab vcs to cucm migration

    • Scenario #2b

    Video Call Control Architecture Today:

    • VCS only for Call Control

    • Some Endpoints Compatible with UCM

    • Some Legacy H.323 Endpoints

    Internet

    VCS E

    VCS C

    Recommended Call Control Architecture:

    Recommended Call Control Architecture:

    • Add BE6000 or BE7000 (UCM)

    • Upgrade VCS C & E to Version 8.2

    • Refresh H.323 EP with new low cost EP

    • Leverage existing MCU & TMS

    BE6000/BE7000

    Internet

    UCM

    VCS E

    V8.2

    • VCS C

    • V8.2


    Drive to collab vcs to cucm migration

    • Scenario #3

    Video Call Control Architecture Today:

    • VCS only for Call Control

    • Some Endpoints Compatible with UCM

    • Some Legacy H.323 Endpoints

    Internet

    VCS E

    VCS C

    Recommended Call Control Architecture:

    BE6000/BE7000

    Internet

    • Add BE6000 or BE7000 (UCM)

    • Upgrade VCS C & E to Version 8.2

    • Migrate SIP Endpoints from VCS to UCM

    • Leave H.323 EP with VCS C

    • Leverage existing MCU & TMS

    UCM

    VCS E

    V8.2

    • VCS C

    • V8.2

    Virtual Exp C & E could reside in the same server


    Scenario 4

    • VCS for Video Call Control & Virtual UCM 9.1 or 10.0 for Voice

    • All Endpoints Compatible with UCM

    Scenario #4

    • Video Call Control Architecture Today:

    Internet

    VCS C

    VCS E

    UCM

    Isolated Voice / Video Networks

    Recommended Call Control Architecture:

    • Migrate all Endpoints from VCS to UCM

    • Upgrade VCS C & E to version 8.2 to enable Mobile & remote Access

    • Add Exp @ no cost to scale if need be

    • Add BE6000 (Exp E)

    • Leverage existing MCU & TMS

    • Option of moving from VCS C&E to Exp C&E

    Internet

    VCS E

    v8.1

    VCS C

    v8.1

    UCM

    v9.1 or 10.x


    Scenario 5

    • VCS for Video Call Control & Virtual UCM 9.1 or 10.0 for Voice

    • All Endpoints Compatible with UCM

    Scenario #5

    • Video Call Control Architecture Today:

    Internet

    VCS C

    VCS E

    UCM

    Isolated Voice / Video Networks

    Recommended Call Control Architecture:

    BE6000/BE7000

    • Add BE6000 or BE7000 (UCM)

    • Migrate all Endpoints from VCS to BE

    • Upgrade VCS C & E to version 8.2 to enable Mobile & remote Access

    • Add Exp @ no cost to scale if need be

    • Add SIP Trunk between Voice & Video UCM

    • Leverage existing MCU & TMS

    • Option of moving from VCS C&E to Exp C&E

    Internet

    SIP Trunk

    UCM

    VCS E

    VCS C

    UCM


    Scenario 6

    • VCS for Video Call Control & UCM (bare metal with version pre 9.x)

    • Some Endpoints Compatible with UCM

    • Some Legacy H.323 Endpoints

    Scenario #6

    • Video Call Control Architecture Today:

    Internet

    VCS C

    VCS E

    CUCM

    Isolated Voice / Video Networks

    Recommended Call Control Architecture:

    • Upgrade UCM to 9.1 or 10.5 and virtualize or Refresh servers to BE6000/BE7000

    • Upgrade VCS C & E to version 8.2 to enable Mobile & remote Access

    • Migrate all Endpoints from VCS to UCM

    • Refresh H.323 EP with new low cost EP

    • Leverage existing MCU & TMS

    Internet

    VCS E

    v8.1

    UCM

    v9.1 or 10.x

    VCS C

    v8.1


    Scenario 7

    • VCS for Video Call Control & UCM (bare metal with version pre 9.x)

    • Some Endpoints Compatible with UCM

    • Some Legacy H.323 Endpoints

    Scenario #7

    • Video Call Control Architecture Today:

    Internet

    CUCM

    VCS E

    VCS C

    Isolated Voice / Video Networks

    Recommended Call Control Architecture:

    Recommended Call Control Architecture:

    BE6000/BE7000

    • Add BE6000 or BE7000 (UCM)

    • Upgrade VCS C & E to version 8.2 to enable Mobile & remote Access

    • Add Exp @ no cost to scale if need be

    • Migrate all Endpoints from VCS to BE

    • Leave H.323 EP with VCS C

    • Add SIP Trunk between Voice & Video UCM

    • Leverage existing MCU & TMS

    • Option of moving from VCS C&E to Exp C&E

    Internet

    SIP Trunk

    VCS E

    V8.2

    • VCS C

    • V8.2

    UCM

    UCM


    Migration checklist

    Migration Checklist


    Drive to collab vcs to cucm migration

    Migration Checklist

    • Verify the compatibility of various devices in your network with UCM - Unified Communications Manager Software Compatibility Matrix

    • Based on your scenario, you may migrate all endpoints to your existing UCM or to a new UCM. Update all the UCM versions to the latest UCM release. UCM 10.x and higher is only supported on virtual machines

    • Update video endpoint version versions to the latest firmware. The Cisco Unified Communications System Release Summary Matrix for IP Telephony summarizes the phone firmware version recommended with all Cisco Unified Communications Manager releases.

    • Identify endpoint numbers and aliases

    • Sync Ldap users from AD into UDS or add as end users

    • Map the URIs in the DN

    • Use BAT tool to do bulk import of endpoints to UCM

    • Move FindMe to Shared line in CUCM

    • Configure SIP registration or enable CDP on the endpoint

    • If needed change the Endpoints provisioning mode to CUCM in TMS if endpoint is provisioned

    • Migrate Phone books and directory


    Drive to collab vcs to cucm migration

    Migration – Dial Plan

    • Devices

      • Identify video devices

      • Group them into a subzone in the VCS

    • URI

      • Identify the URIs that are to be migrated

      • Delete the URI entries from the ILS catalog

    • DNs

      • Update the Unified CM route patterns that point to the VCS


    Drive to collab vcs to cucm migration

    Migration – Shared Line

    • As part of migration, consider making the migrated device a shared line with other phones for the DN. For example, If you had a UCM cluster with a device for a user on both UCM and VCS, you can migrate the VCS device to UCM, and make the migrated device to be a shared line with the user’s existing UCM DN.

  • Associate user with device

  • Update the Primary DN in the end user configuration

  • In DN configure the alias for the user

  • Use BAT tool to configure the phones into the Unified CM

  • Enable SNR functionality if needed


  • Drive to collab vcs to cucm migration

    Migration – Endpoints Registrations

    • Upgrade video endpoints software to latest version: Cisco Unified Communications System Release Summary Matrix for IP Telephony

    • Update the release key and option keys

    • If Protocol is changed from H.323 to SIP, then update protocol configuration and default call protocol configuration

    • Access the endpoint using browser or SSH and change the provisioning mode and the Vlan mode to auto. This enables CDP and uses option 150 to register with the Unified CM

    • If setting VLAN is not possible, then configure SIP information and configure Unified CM as registrar


    Drive to collab vcs to cucm migration

    Migration – Address Book

    Directory synchronized with LDAP

    User Data Service (UDS) provides phone directory for Unified CM registered endpoints

    UDS supports blended addresses, that send DN and URI information to display and use for history and redial/missed call lists

    Address book is automatically configured for C-series endpoints and points to UDS

    TMS supports Unified CM directory for phone books

    VCS endpoints have phone books through TMS


    Drive to collab vcs to cucm migration

    Migration Conference bridge – (Rendezvous / Scheduled)

    VCS

    Unified CM

    EX, MX

    C-Series

    • [email protected]

    • [email protected]

    MCU

    Users meeting URI

    MCU

    TX Series

    Rendezvous

    VCS Search rule to CUCM for Multiwaynumbers

    Configure route pattern on CUCM for Multiwaynumbers

    ILS import for user allocated bridges into CUCM/SME

    Move registration of the MCUs to the CUCM/Conductor

    Scheduled conferences

    Map DN to Alias conferences

    27


    Migration considerations1

    Migration Considerations

    • Release Key is not required when migrating from VCS.

    • Consider making the directory/phone book in UCM similar to that in VCS, via setting up the Active Directory integration in UCM and importing the users regularly.

    • Enable Active Directory authentication in UCM so that Jabber for Windows, Mac and iPad will use single sign-on.

    • "Cisco TelePresence Profile 52 (C60)” fails to register in UCM unless the device type changed to "Cisco TelePresence Codec C60". We need to setup the exact device type in UCM match the output of SSH command “xstatusSystemUnitProductId”.

    • TC4 and older software doesn’t support UCM provision mode. Need to upgrade the endpoint to TC5 or TC6 (with appropriate Release Key) before switching from VCS to UCM.

    • Use BAT in UCM to create multiple devices, Remote Destination Profiles and Remote Destinations efficiently.


    Caveats

    Caveats

    • Extensive changes to configuration such as adjusting gain, camera source etc. cannot be configured through the CUCM

    • No retry video call at lower bandwidth, CUCM retries call as audio


    License migration

    License Migration


    License migration process

    License Migration Process

    License Transfer

    VCS

    UCM/Exp

    • Every Personal Endpoint OR Soft Client Migrated

    • One UCL Enh OR Enh Plus User License

    • @ No Cost

    Unified CM 9.1

    • Every Personal Endpoint & Soft Client for Same User

    • One UCL Enhanced Plus

    • @ No Cost

    • Every Room System Migrated

    • One TelePresence Room License

    • @ No Cost

    • Every Purchased Traversal License on VCS E

    • One Rich Media License for VCS C & E

    Draft: Details being worked out

    • @ No Cost

    • Use the SKUs in CB Plus while registering your deal

    • Purchase of UCSS/ESW for each device migrated is required for 1 or 3 years


    How to take advantage of the program step by step instructions

    How to Take Advantage of the Program?Step By Step Instructions

    Enable Video Only (VCS) customers to experience Cisco Collaboration suite

    Drive to Collab: VCS to UCM

    1

    2

    4

    3

    5

    Run Readiness Assessment Tools

    Engage with PDI Help Desk

    Plan Licence Migration

    Order SKUs as needed via CB+

    Migrate to

    Unified CM

    Optional


  • Login