world wide technology webinar - understanding esc15
TRANSCRIPT
Copyright © 2016 World Wide Technology, Inc. All rights reserved.
DoD Collaboration VisionUnderstanding ESC 15 and preparing for the futureApril 7th, 2016
Joe Berger | Collaboration Practice Manager
Joe Heron | Collaboration Technical Architect, Federal
Guest Speaker: Rick Pina | Principal Technologist, DoD
Agenda
o Current DoD Vision
o Collaboration Architectures for DOD
o Benefits and features – Why Upgrade
o JITC certified applications/end points
o Upgrade definitionso Licensing
o Hardware
o Application
o Tools for Collaboration
o Integration Options
o Customer example
o Q&A
Guest Speaker
Rick PinaCurrent Role: WWT Principal Technologist DoDPrevious Role: CTO, US Army (Retired)
Department of Defense Vision
Quick Explanation of the JITC Collaboration Certs
• LSC (Local Session Controller) – Collaboration
deployment is based on the UCR2008 guidance. Intent is to
replace costly legacy TDM lines with SIP/TLS network trunks
to the DISA telephony core. An LSC is deployed and
maintained (normally) on a customer premise.
• ESC (Enterprise Session Controller) – Collaboration
deployment is based on the UCR2013 guide and is part of
the DISA’s overall Unified Capabilities Plan of providing
hosted/cloud based DOD communication requirements.
Customer’s connected to an ESC fall into a Type 1,2, or 3
category based on users local communications survivability
requirement should the connection to the ESC be broken.
• UCCP (Unified Capabilities Collaboration Product) – Is
designed to provide collaboration soft client (only)
functionality to DOD customers. UCCP environments do not
natively communicate with outside entities but must go
through a LSC or ESC certified environment.
Why Move?Unified Experience Every
Room
Every Desk
Every Device
Simplified User Experience• Single identity for Voice, Video, IM, Presence• SIP URI dialing or E164• Single Sign On• New certified end points and applications
Easy management and provisioning• Centralized Certificate Management for
CUCM & IM&P• Collaboration endpoint management from
one system
Cisco AnnouncementsCUCM 8.6 End of Sale & Support
8.6.1 is outdated and is
reaching the end of Sale
(Aug 2016) and
supportability (Aug 2017)
Cisco Unified Communications Manager (UCM) 10.5
Cisco Session Management Edition (SME) 10.5
Cisco Unity Connection (CUXN) 10.5
Cisco Instant Messaging and Presence (IM/P) 10.5
Cisco WebEx Meeting Server (CWMS) 2.5
Jabber for Windows 11.0
IP Communicator 8.6.1
RedSky E-911 6.3.1
ESC15 JITC APL Certified UC Applications
ESC 15: Cisco Collaboration Endpoints
Collaboration Rooms
Quick Set SX10 and SX20
MX200 G2 and MX300 G2
MX700 and MX800
MX800 DualComing Soon
Telepresence Integration Solutions
Codex SX80
Collaboration Desk Endpoints
Standard Definition
DX650 DX70 DX80
Soft Clients
Jabber and CWMS
Cisco IP Phones
8800 Series7900 Series7800 Series6900 Series 8831 8900 Series 9900 Series
UCM 10.X Device Licensing Summary
UCL Essential
UCL Basic
UCL Enhanced / Enhanced Plus CUWL StandardCUWL Professional
Analog
39056901
6921
6911
Fax
TelePresenceRoom
MX / Profile Series
System Codecs and SX Series
99xx
89xx
792x
Jabber Mobile
Third Party SIP
DX650/DX70/DX897937 / 8831
TX / CTS / T Series
79xx
88xx
69xx
Jabber Desktop
78xx
7821
Note: CUCM 8.X was DLU based so a customer must provide some form of proof of purchase to convert to UCL/CUWL. Opening a TAC case with licensing is normally involved.
JITC 10.5 Licensing PathsHow to Upgrade to CUCM 10.5
Non-JELA Customer
Customer without UCSS/SWSS
Purchase Upgrade
Non-JELA Customer
Customer withUCSS/ESW/SWSS
Order V10.X upgrade via
Cisco Licensing PUT Tool
Open a case with GLO by emailing
Contact the Account
Team
JELA customer
Active UCSS/SWSS at JELA time
Order V10.X upgrade via
Cisco Licensing PUT Tool
Open a case with GLO by emailing
Contact the Account
Team
JELA customer
Inactive UCSS/SWSS at JELA time
Running CUCM 8.6.1
Running CUCM prior to 8.6.1
Contact the Account Team
Purchase Upgrade
Bridge Upgrade: Appliance to Appliance model (long downtime)• Older servers that cannot run newer version of CUCM but can upgrade to 8.0(3) or later
Jump Upgrade: Appliance to Virtualized model (minimal downtime)• Older servers that cannot upgrade to 8.0(3) or later to virtualized• Virtualized CUCM with 6.1(4), 6.1(5), 7.1(3) and 7.1(5) for lab upgrade to 8.X
Platform Change: Appliance to Virtualized or Virtual to Virtual model (variable downtime)
• Older servers that cannot support the latest CUCM or CUCM 10.X virtualized• Single or multiple hop upgrade or migration
Check out: http://docwiki.cisco.com/wiki/CUCM_Upgrades_and_Migrations_FAQ
Upgrading Hardware to CUCM 10.5
Bridge
Jump
PlatformChange
Virtualized CUCM 10.5(2)
Note: 10.5 Must be virtualized!!!
MCS or Appliance hardware
I. Greenfield (low risk)
Build ESC 10.5 from scratch
II.Cloned the VMs from existing ESC 8.X (low risk)
Perform the in-place upgrade (Alternate lab infrastructure)
III.In-place Upgrade from existing ESC 8.X on existing Infrastructure (more risk)
IV.Use Prime Collaboration Deployment Tool to perform migration (more risk)
8.X or Later to 10.5 or fresh install of 10.5
V.Rebuild in lab New H/w….use cloned copies of database…upgrade/test and send hardware out to sites. (low risk)
Application Upgrade from CUCM 8.X
Prime Collaboration Key Components
1. Provisioning
1. Central configuration, simple
deployment
2. Assurance
1. Continuous
monitoring/diagnostics
3. Analytics
1. Long-term trending/reporting
3rd Party Integrations
Microsoft Lync/Skype for Business
SAML/SSO – Identity Management
Enterprise Integrations (GVS,DSN,Directory/LiteScape)
Acano (already on JITC coming soon to the ESC)
Headsets to enable Softphone
WWT Support
Proof of Concepts
Workshops (free)
Lab as a Service
Professional Services
Certified Trainings
Adoption Services
Customer Upgrade ExampleHealthcare Provider
https://www2.wwt.com/case-study/healthcare-system-tests-major-uc-upgrade-to-de-risk-downtime/
Questions?
Customer Upgrade ExampleHealthcare Provider
UC Design consisting of fourteen different VMs to simulate customer’s 19 remote sites
Configuration of Cisco UCS B-series blades in the ATC
Ixia solution used to simulate WAN conditions for all nine remote sites.
Upload customer data to test environment
Review Cisco Bug notes for the current and future version of code
Perform prepared Test and Acceptance documentation
Document results
Identified any potential impact caused by CM cluster size and geographic distribution over the WAN
Gave customer better understanding of upgrade process and minimized potential impacts
Provided a tested and proven upgrade roadmap
Customer successfully validated upgrade path and developed roadmap using less resources
Needed to validate upgrade from CUCM version 8.5
Had experienced failed upgrades in the past
24x7 Environment meant that the system had to be upgraded with as little downtime as possible