1 / 22

VCS to UCM Migration Program

VCS to UCM Migration Program. Two Primary Customer Profiles. Customers with VCS and UCM. Customers with VCS Only. Voice/Video. IM/Presence. Messaging. Cisco UCM 9.1 or 10 .x. Mobility. Network Management. Session Management.

macey-eaton
Télécharger la présentation

VCS to UCM Migration Program

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. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. VCS to UCM MigrationProgram

  2. Two Primary Customer Profiles • Customers with VCS and UCM • Customers with VCS Only Voice/Video IM/Presence Messaging Cisco UCM 9.1 or 10.x Mobility Network Management Session Management

  3. VCS to UCM Migration is a part of “Drive to Collab” Drive to Collab Migration Displacement Adoption Competitive Displacement in Focused Markets UCM Upgrades to version 10.5 VCS to UCM Migrations Accelerate Consumption of Collaboration Solution

  4. Drive to Collab: VCS to UCM Migration • Simplified Migration Process • Customized Migration Collateral • Simplified License Migration • Readiness Assessment Tools • Compelling Offers • License, Service Offers • Server Hardware offers • Endpoints Promotions • Comprehensive Support • VCS to UCM Migration TAC (24x7) • PDI Help Desk • Program Team Support • Focused Enablement • Partner Enablement • Field Enablement • Landing Page & Support forums VCS to UCM Migration

  5. BYOD, Mobility & SNR Pervasive Video: From Browser to Boardroom Consolidate Communications Infrastructure Collaboration Platform - now and future Cloud: HCS & CMR Self Provisioning & Self Care Support for New Endpoints Virtualization Why Migrate from VCS to UCM? Technical Decision Maker

  6. LOB User Benefits on UCM • Consistent User Experience across all devices • Single Portal for Users • Enhanced Video Features: Click to Call from Desktop, Video Greeting & Video on Hold Connected User Centric Collaborative Anywhere, Any Device Intuitive & Ease of Use Browser to Boardroom • Experience New Endpoint Innovation • Instant Messaging, Presence & escalating to Web Conferencing • B2B Collaboration with Customers, Suppliers, & Partners • Collaboration Edge (Remote & Mobile Access without VPN) • Collaborate from any device • Hot-desking (Extension Mobility) • Reachability on all devices (Single Number Reach)

  7. Cisco Collaboration Architecture Prime Collaboration TelePresence Infrastructure Webex, B2B, Remote & Mobile Access Scheduled Meetings HD Video Expressway-C Expressway-E Communications Virtualization / Unified Computing Mobility Ad Hoc Network Resiliency / Medianet Unified IM & TMS Messaging & Queuing Multiparty Conferencing Presence Telephony TelePresenceConductor Legacy SIP / H.323 iOS Android Lync Immersive SIP Expressway-C or VCS Control Multipurpose Windows Mac OS X H.323 Video Telephony Personal TelePresence XML 7

  8. Preferred Collaboration Architecture Prime TMS MCU / TS Ad Hoc & Rendezvous EXP C EXP E Conductor Internet CUCM MCU Scheduled Calls

  9. Migration Scenarios

  10. 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 TP server/ MCU & TMS • Leverage Prime Collab for Management BE6000 or CE BE6000/BE7000 Internet UCM • Exp C Exp E Virtual Exp C & E could reside in the same server

  11. 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 TP server/MCU & TMS • Leverage Prime Collab for Management Internet UCM VCS E V8.2 • VCS C • V8.2

  12. 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 TP server/MCU & TMS • Leverage Prime Collab for Management Internet UCM • Exp C Exp E Virtual Exp C & E could reside in the same server

  13. 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 TP server/MCU & TMS • Leverage Prime Collab for Management BE6000/BE7000 Internet UCM VCS E V8.2 • VCS C • V8.2

  14. 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 TP server/MCU & TMS • Leverage Prime Collab for Management UCM VCS E V8.2 • VCS C • V8.2 Virtual Exp C & E could reside in the same server

  15. 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 TP server/MCU & TMS • Option of moving from VCS C&E to Exp C&E Internet VCS E V8.2 VCS C V8.2 UCM v9.1 or 10.x

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

  17. 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 TP server/MCU & TMS Internet VCS E V8.2 UCM v9.1 or 10.x VCS C V8.2

  18. 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 TP server/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

  19. Role of TMS is now different… Now… Before… • Endpoint Management • Phone Books • Conference Management • Infrastructure Management • Scheduling • Reporting & Analytics • Conference Management • Scheduling TMS TMS • Endpoint Management • Phone Books • Reporting & Analytics • (Need Prime Advanced) Prime & UCM

  20. “CUCM Upgrade Central” v4.0 includes VCS Assessment Available June End on the App Store Readiness Assessment iPadApp for VCS to UCM Migration : • Live data mining on VCS & TMS • Registered Endpoint types & count • License Count Usage report • Recommendation on Next Steps • Customized Upgrade Procedure to migrate to UCM Coming Soon on Apple App Store: https://itunes.apple.com/us/app/id650114526

  21. VCS to UCM Migration Resources Landing Page for All VCS to UCM Migration Resources Customer Landing Page: http://www.cisco.com/go/cucmupgrade Support Alias for VCS to UCM Questions Drive to Collab Program Team: ask-drive-to-collab@cisco.com

More Related