1. Drive to Collab VCS to CUCM Migration
Technical Training

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

3. VCS  UCM - VSEM
Enable Video Only (VCS) customers to experience Cisco Collaboration suite V
Migrate VCS installed base to Cisco UCM
Why & How
Attractive Promotions & Incentives
Comprehensive Enablement S
12-18 months
Value Proposition & Opportunity
Migration Guides & Tools
Case Studies & Success Stories
License Migration E
License, Service & Hardware offers
Endpoints Promotions
Migration Bundles
Partner Incentives
Partner & Field Enablement
Partner Trainings on UCM
Migration Support & Services M
Number of VCS  UCM Migrations
Migration Bookings in $
Remove customer silos
Enable Video Customers to
Targets:
50% (7500) customer converted by end of CY15
Top 30 partners enabled by end of CY14
80% video revenue attach to UCM by end of CY15 3

4. Cisco Unified Communications Manager 10.5
Single, Unified platform for feature-rich Voice and Video
Control
Single cluster for voice or video device, including legacy and 3rd party endpoints
Integrated provisioning, management, phonebooks, and conferencing
Flexible connectivity outside the private network
Deployable TODAY

5. CUCM and VCS Roles
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
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)

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
VCS
Control
VCS
Expressway
Firewall Traversal
UCM
Legacy Solution
Optional
Expressway
Core
Expressway
Edge
Firewall Traversal
Trusted certificates are required
CSR10 Expressway Solution
SIP Trunk
Signaling Proxy (“SIP line side”)

7. Migration Considerations

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)!
Registration
Device
Provisioning
Management
Endpoint
OBTP TMS
scheduling*
Directories/
Phone Books
VOIP
Jabber
Immersive
(CTS/TX)
On Campus endpoints on
UCM
UCM/Prime
TMS
UCM/UDS
or TMS (14.4 with TP endpoints only) √
Remote via Expressway to
No IP access to the device
On Campus
endpoints on VCS Control
Not supported
Not
supported
Remote via Expressway to VCS Control
TMS(PE)
With Expressway x8.1, Jabber 9.6 and TC 7.1 devices can now register to UC Manager via Expressway path
UCM’s directories/phone books are provided by its User Data Services (UDS)
TMS provides endpoint “one button to push” conference scheduling in all “on-net” cases only
* TMS can schedule any endpoint into a conference, but OBTP is only available to campus devices

9. 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

10. CUCM and VCS Capability Comparison
Facilitator Notes: Include all facilitation instructions in this box
CUCM and VCS Capability Comparison
Rev. 10/2/2012
Capability
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
Application user, JTAPI device control, CTI ports, third-party (e.g. home) phone support
Application control
Voic , Webex conferencing, IM and presence, CTI
Remote Expert Training

11. Migration Scenarios

12. Virtual Exp C & E could reside in the same server
Scenario #1a
Video Call Control Architecture Today:
Internet
VCS E
VCS C
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
BE6000
or CE
Virtual Exp C & E could reside in the same server

13. Scenario #1b Video Call Control Architecture Today:
Internet
VCS E
VCS C
VCS only for Call Control
All Endpoints Compatible with UCM
Recommended Call Control Architecture:
Add BE6000 or BE7000 (UCM)
Upgrade VCS C & E to Version 8.2
Migrate SIP Endpoints from VCS to UCM
Leverage existing MCU & TMS
BE6000/BE7000
Internet
UCM
VCS C
V8.2
VCS E
V8.2

14. Virtual Exp C & E could reside in the same server
Scenario #2a
Video Call Control Architecture Today:
Internet
VCS E
VCS C
VCS only for Call Control
Some Endpoints Compatible with UCM
Some Legacy H.323 Endpoints
Recommended Call Control Architecture:
Add BE6000 or BE7000 (UCM & Exp C)
Add BE6000 (Exp E)
Refresh H.323 EP with new low cost EP
Leverage existing MCU & TMS
BE6000/BE7000
BE6000
or CE
Internet
UCM
Exp C
Exp E
H.323 – Trunk to UCM
3rd party – trunk to exp C
Virtual Exp C & E could reside in the same server

15. Scenario #2b Video Call Control Architecture Today:
Internet
VCS E
VCS C
VCS only for Call Control
Some Endpoints Compatible with UCM
Some Legacy H.323 Endpoints
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 C
V8.2
VCS E
V8.2
H.323 – Trunk to UCM
3rd party – trunk to exp C

16. Virtual Exp C & E could reside in the same server
Scenario #3
Video Call Control Architecture Today:
Internet
VCS E
VCS C
VCS only for Call Control
Some Endpoints Compatible with UCM
Some Legacy H.323 Endpoints
Recommended Call Control Architecture:
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
BE6000/BE7000
Internet
UCM
VCS C
V8.2
VCS E
V8.2
H.323 – Trunk to UCM
3rd party – trunk to exp C
Virtual Exp C & E could reside in the same server

17. Scenario #4 Video Call Control Architecture Today: UCM VCS C VCS E
VCS for Video Call Control & Virtual UCM 9.1 or 10.0 for Voice
All Endpoints Compatible with UCM
Video Call Control Architecture Today:
Internet
UCM
VCS C
VCS E
Isolated Voice / Video Networks
Migrate all Endpoints from VCS to UCM
Upgrade VCS C & E to version 8.2 to enable Mobile & remote Access
Add 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
Recommended Call Control Architecture:
Internet
UCM
v9.1 or 10.x
VCS C
v8.1
VCS E
v8.1
Codec – SX
Desktop – EX DX
Profile – MX

18. Scenario #5 Video Call Control Architecture Today:
VCS for Video Call Control & Virtual UCM 9.1 or 10.0 for Voice
All Endpoints Compatible with UCM
Video Call Control Architecture Today:
Internet
UCM
VCS C
VCS E
Isolated Voice / Video Networks
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 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
Recommended Call Control Architecture:
BE6000/BE7000
Internet
SIP Trunk
UCM
UCM
Codec – SX
Desktop – EX DX
Profile – MX
VCS C
VCS E

19. Scenario #6 Video Call Control Architecture Today: CUCM VCS C VCS E
VCS for Video Call Control & UCM (bare metal with version pre 9.x)
Some Endpoints Compatible with UCM
Some Legacy H.323 Endpoints
Video Call Control Architecture Today:
Internet
CUCM
VCS C
VCS E
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
UCM
v9.1 or 10.x
VCS C
v8.1
VCS E
v8.1
Codec – SX
Desktop – EX DX
Profile – MX

20. Scenario #7 Video Call Control Architecture Today: CUCM VCS E VCS C
VCS for Video Call Control & UCM (bare metal with version pre 9.x)
Some Endpoints Compatible with UCM
Some Legacy H.323 Endpoints
Video Call Control Architecture Today:
Internet
CUCM
VCS E
VCS C
Isolated Voice / Video Networks
Add BE6000 or BE7000 (UCM)
Upgrade VCS C & E to version 8.2 to enable Mobile & remote Access
Add 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
Recommended Call Control Architecture:
Recommended Call Control Architecture:
BE6000/BE7000
Internet
SIP Trunk
VCS C
V8.2
VCS E
V8.2
UCM
UCM
Codec – SX
Desktop – EX DX
Profile – MX

21. Migration Checklist

22. 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

23. Migration – Dial Plan Devices URI DNs 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

24. 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

25. 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

26. 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

27. Migration Conference bridge – (Rendezvous / Scheduled)
Unified CM
VCS
EX, MX
C-Series
Users meeting URI
MCU
TX Series
MCU
Rendezvous
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 27

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.
CUCM doesn’t have AD integration by default
Movi used to use AD user/passwd.

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

30. License Migration

31. License Migration Process
VCS
License Transfer
UCM/Exp
Every Personal Endpoint OR Soft Client Migrated
@ No Cost
One UCL Enh OR Enh Plus User License
Unified CM 9.1
Every Personal Endpoint & Soft Client for Same User
@ No Cost
One UCL Enhanced Plus
Every Room System Migrated
@ No Cost
One TelePresence Room License
Draft: Details being worked out
Every Purchased Traversal License on VCS E
@ No Cost
One Rich Media License for VCS C & E
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
----- Meeting Notes (6/9/14 10:02) -----
1 scenario
possibly give CUWL Pro

32. 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 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
Optional