drive to collab vcs to cucm migration
DESCRIPTION
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. - PowerPoint PPT PresentationTRANSCRIPT
Cisco Confidential 1Cisco Confidential 1Cisco ConfidentialCisco Confidential© 2010 Cisco and/or its affiliates. All rights reserved.
Drive to CollabVCS to CUCM Migration
Technical Training
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 2
Agenda• Objective
• Roles of CUCM and VCS
• VCS to CUCM Migration Considerations
• Migration Activities• users• dial plan• directory• Registration• Licenses
• License Migration
• Caveats/Limitations
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 3
VCS UCM - VSEM
12-18 months
12-18 months
Value Proposition & Opportunity Migration Guides & Tools Case Studies & Success Stories License MigrationE
Migrate VCS installed base to Cisco UCM
Why & How Attractive Promotions & Incentives Comprehensive EnablementS
Enable Video Only (VCS) customers to experience Cisco Collaboration suiteV
M
License, Service & Hardware offers Endpoints Promotions Migration Bundles Partner Incentives
Partner & Field Enablement Partner Trainings on UCM Migration Support & Services
Number of VCS UCM Migrations
Migration Bookings in $
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 4
Cisco Unified Communications Manager 10.5Single, Unified platform for feature-rich Voice and Video
Control
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 5
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
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 6
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
6
VCSControl
VCSExpress
way
ExpresswayCore
ExpresswayEdge
CSR10 Expressway Solution
UCM
SIP TrunkSignaling Proxy (“SIP line side”)
Firewall Traversal
Firewall Traversal
Legacy Solution
Trusted certificates are
required
Optional
Cisco Confidential 7© 2013 Cisco and/or its affiliates. All rights reserved.
Migration Considerations
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 8
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)!
8
Registration DeviceProvisioning
DeviceManagement
EndpointOBTP TMSscheduling*
Directories/Phone Books
VOIP Jabber Immersive(CTS/TX)
On Campus endpoints onUCM
UCM/Prime UCM/Prime TMSUCM/UDS
or TMS (14.4 with TP endpoints only)
√ √ √Remote via Expressway to UCM
UCM/Prime UCM/Prime No IP access to the device UCM/UDS √ √ √
On Campus endpoints on VCS Control
TMS TMS TMS TMS Not supported
Not supported
Notsupported
Remote via Expressway to VCS Control
TMS(PE) No IP access to the device
No IP access to the device TMS Not
supportedNot
supportedNot
supported
* TMS can schedule any endpoint into a conference, but OBTP is only available to campus devices
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 9
UCM Registration BenefitsDX70, 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
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 10
CUCM and VCS Capability ComparisonCapability VCS UCM
Device/User registrations H.323 & SIP, LDAP or manual. Focused on URI based dialing.
SIP & SCCP, phone auto-registration, LDAP, manual or mixed. Focused on numeric (DN) dialing which can be aliased with URIs
Device security SIP/H.323 authentication, TLS SIP authentication, phone certificates, TLS, SRTP
Device feature management N/A – done by TMS Native
Dial plan handling Zones, subzones, transforms, and rules Partitions, calling search spaces, filters, calling and called party transformations, route patterns, URI aliases
User routing rules “Find Me” application only Single Number Reach
Bandwidth control (CAC) Subzones, pipes and links Global, regional, inter-cluster, on local trunks and device network topologies
Trunks Zone Trunk/Partitions/Calling Search Spaces
Call Queuing N/A Hunt pilot queuing, routing, announcements, contact center type call treatments
Firewall traversal Control client and Expressway server Expressway solution
Computer Telephony Interfaces N/A Application user, JTAPI device control, CTI ports, third-party (e.g. home) phone support
Application control N/A Voicemail, Webex conferencing, IM and presence, CTI
Cisco Confidential 11© 2013 Cisco and/or its affiliates. All rights reserved.
Migration Scenarios
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 12
Video Call Control Architecture Today:
Scenario #1a
VCS only for Call Control All Endpoints Compatible with UCM
Exp E
Recommended Call Control Architecture:
UCM
BE6000/BE7000
Internet
Exp C
Add BE6000 or BE7000 (UCM & Exp C) Add BE6000 (Exp E) Migrate Endpoints from VCS to UCM Leverage existing MCU & TMS
Internet
VCS EVCS C
Virtual Exp C & E could reside in the same server
BE6000 or CE
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 13
Video Call Control Architecture Today:
Scenario #1b
VCS only for Call Control All Endpoints Compatible with UCM
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
VCS EVCS C
UCM
BE6000/BE7000
Internet
VCS CV8.2
VCS EV8.2
Recommended Call Control Architecture:
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 14
Scenario #2a
Internet
VCS EVCS C
Video Call Control Architecture Today:
Exp E
Recommended Call Control Architecture:
UCM
BE6000/BE7000
Internet
Exp C
Add BE6000 or BE7000 (UCM & Exp C) Add BE6000 (Exp E) Refresh H.323 EP with new low cost EP Leverage existing MCU & TMS
VCS only for Call Control Some Endpoints Compatible with UCM Some Legacy H.323 Endpoints
Virtual Exp C & E could reside in the same server
BE6000 or CE
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 15
Scenario #2b
Internet
VCS EVCS C
Video Call Control Architecture Today:
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
VCS only for Call Control Some Endpoints Compatible with UCM Some Legacy H.323 Endpoints
UCM
BE6000/BE7000
Internet
VCS CV8.2
VCS EV8.2
Recommended Call Control Architecture:
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 16
Scenario #3
Internet
VCS EVCS C
Video Call Control Architecture Today:
Recommended Call Control Architecture:
UCM
BE6000/BE7000
Internet
VCS CV8.2
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
VCS only for Call Control Some Endpoints Compatible with UCM Some Legacy H.323 Endpoints
Virtual Exp C & E could reside in the same server
VCS EV8.2
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 17
VCS EVCS C
Video Call Control Architecture Today:
UCMIsolated Voice / Video Networks
Scenario #4
Internet
Recommended Call Control Architecture:
Internet
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
VCS for Video Call Control & Virtual UCM 9.1 or 10.0 for Voice All Endpoints Compatible with UCM
UCMv9.1 or 10.x
VCS Cv8.1
VCS Ev8.1
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 18
VCS EVCS C
Video Call Control Architecture Today:
UCM
Isolated Voice / Video Networks
Scenario #5
Internet
Recommended Call Control Architecture:
UCMInternet
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
VCS for Video Call Control & Virtual UCM 9.1 or 10.0 for Voice All Endpoints Compatible with UCM
UCM
SIP Trunk
VCS C VCS E
BE6000/BE7000
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 19
VCS EVCS C
Video Call Control Architecture Today:
CUCMIsolated Voice / Video Networks
Scenario #6
Internet
VCS for Video Call Control & UCM (bare metal with version pre 9.x) Some Endpoints Compatible with UCM Some Legacy H.323 Endpoints
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
Recommended Call Control Architecture:
Internet
UCMv9.1 or 10.x
VCS Cv8.1
VCS Ev8.1
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 20
Scenario #7Video Call Control Architecture Today:
Recommended Call Control Architecture:
VCS EVCS C
CUCMIsolated Voice / Video Networks
Internet
VCS for Video Call Control & UCM (bare metal with version pre 9.x) Some Endpoints Compatible with UCM Some Legacy H.323 Endpoints
Recommended Call Control Architecture:
Internet
VCS CV8.2
VCS EV8.2UCM
UCM
SIP Trunk
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
Cisco Confidential 21© 2013 Cisco and/or its affiliates. All rights reserved.
Migration Checklist
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 2222
• 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
Migration Checklist
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 2323
• 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
Migration – Dial Plan
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 2424
• 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
Migration – Shared Line
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 2525
• 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
Migration – Endpoints Registrations
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 26
• 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
26
Migration – Address Book
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 27
Migration Conference bridge – (Rendezvous / Scheduled)
27
Unified CM VCS
TX Series
MCU
EX, MX C-Series
Users meeting URIRendezvous
• VCS Search rule to CUCM for Multiway numbers• Configure route pattern on CUCM for Multiway numbers• 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
MCU
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 28
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 “xstatus SystemUnit ProductId”.
• 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.
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 29
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
Cisco Confidential 30© 2013 Cisco and/or its affiliates. All rights reserved.
License Migration
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 31
License Migration ProcessUnified CM 9.1
Every Personal Endpoint OR Soft Client Migrated @ No Cost One UCL Enh OR Enh
Plus User License
VCS UCM/Exp
Every Room System Migrated
One TelePresence Room License@ No Cost
License Transfer
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
Every Personal Endpoint & Soft Client for Same User
One UCL Enhanced Plus@ No Cost
Every Purchased Traversal License on VCS E
One Rich Media License for VCS C & E@ No Cost
Draft: Details
being worked out
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 32
How to Take Advantage of the Program?Step By Step Instructions
1 2 3 4 5
Run Readiness Assessment
Tools
Engage with PDI Help Desk
Plan Licence Migration
Order SKUs as needed via CB+
Migrate to Unified CM
Enable Video Only (VCS) customers to experience Cisco Collaboration suite
Drive to Collab: VCS to UCM
Optional