Enhance your collaboration experience by enabling Pervasive Video on your Cisco Unified Communications Manager (Part 1 of 2) Shawn Cardinal, Cisco Collaboration CSE scardina@cisco.com

Thank you for attending Cisco Connect Toronto 2015, here are a few housekeeping notes to ensure we all enjoy the session today.

§  Please ensure your cellphones / laptops are set on silent to ensure no one is disturbed during the session

§  This is your session. Please ask questions or contact me scardina@cisco.com

House Keeping Notes

Let’s continue this conversation on…

Cisco’s mobile collaboration team application

Visit the Collaboration booth in the World of Solutions to join the Connect Spark room

www.ciscospark.com

In this session, we’ll explore the value of enabling pervasive video in your Collaboration environment. We will also examine the technical requirements for enabling video on Cisco Unified Communications Manager. Note: Attendees should have a basic understanding of a CUCM deployment.

Session Objectives

Icons used in this presentation Unified Communications Manager

Expressway Core (formerly VCS Control)

Expressway Edge or Unified Border Element (CUBE)

Advanced Security Appliance (ASA)

TelePresence Server or MCU

TelePresence Management Suite or Prime Collaboration

Directory Server or Phone Book

Generic DHCP Server

Cisco IOS Router with VPN Client

Generic Firewall / NAT

Branch Office

Home Office

Network

Large Office

Immersive TelePresence System (CTS / TX Series)

Multipurpose TelePresence System (Profile, MX, SX, C Series)

Personal TelePresence System (EX Series)

Unified IP Video Phone (8900, 9900, DX 650 Series)

PC client (Jabber for Windows / Mac)

BYOD client (Jabber for IOS / Android)

AnyConnect VPN Client

TelePresence Conductor

CUCM – Cisco Unified Communications Manager – unified call control server

VCS – Video Communications Server – video call control server

MCU – Multipoint Control Unit – conferencing bridge resource

TPS – TelePresense Server – virtual conferencing bridge resource

TMS – TelePresence Management Suite – video management server

CTS – Cisco TelePresence System – legacy Cisco video systems

CUBE – Cisco Unified Border Element – Cisco router feature

CMR – Collaboration Meeting Rooms – premise, cloud or hybrid video conferencing

URI – Uniform Resource Identifier – string of characters used for dialing

SIP – Session Initiation Protocol – communication protocol

SNR – Single Number Reach – feature in CUCM

Acronyms used in this presentation

§  Why video on CUCM? §  Unified Call Control Architecture

§  Technical Considerations §  Dialing Options for CUCM §  CUCM Video Conferencing Components §  CUCM Video Conferencing Licensing §  VCS to CUCM Migration

§  Stay tuned for – Part 2 with Robert Bouchard

Agenda

Video: Better Than Being There

§  Augmented Reality §  Intelligent Proximity §  Video Everywhere

CUCM Video Registration Benefits User experience benefits:

§  Unified, intuitive video experience drives user adoption. §  Voice Mail indicator / Call Forward All / Consultative Transfer §  Shared Lines / SNR / Ad Hoc conferencing / CTI Control / BLF §  Simplified calling: E.164 or URI

Every Desk

Every Room

Every Pocket

UCM Video Registration Benefits Administration benefits:

§  Single point of Dial Plan Administration §  Allows for a more controlled dial-plan §  Single Call Admission Control Domain §  Geographic redundancy §  DX70, DX80, and DX650 can only be registered to UCM §  Expressway included – Mobile and Remote Access for Jabber and desktop

endpoints. §  CUCM 10.5 makes it easier to register endpoints on UCM and fully manage

them, no matter how they are connected to the network (VPN or Expressway)!

Video as easy as voice!

CUCM Video Registration Benefits Business benefits:

§  Increased ROI §  Reduce operational costs §  Reduce delivery time

§  More effective collaboration §  Increased employee satisfaction §  Increased customer satisfaction

Architectural Evolution Circa 2010 – At The Close Of The TANDBERG Acquisition

14

•  TelePresence and UC endpoints typically deployed on separate UCM clusters

•  Limited interoperability between endpoints (TelePresence Server was the bridge between these formerly non-interoperable worlds)

•  Lots of product functional overlap in every category: endpoints, call

control, B2B connectivity, bridging, scheduling and management

•  Different dial plans (numerical vs. alpha-numeric centric)

•  Different methods of provisioning, management and monitoring

•  Feature inconsistency across the portfolio

UC Manager (Voice)

VCS Control VCS Expressway

CTS Triple

MXP, SX, Profile Series

IP Phones

CTMS

CUPC Video Advantage IP Communicator

SIP H.323 SCCP, MGCP, ISDN CTSMAN

Internet

UC Manager (TelePresence)

PSTN

CTS Single T3

EX T1 Movi

MCU TS

B2B Exchange

CUBE

ISDN TMS Prime

Architectural Evolution Circa 2011 – 2013

UC Manager 8.6 – 9.0 (Combined Voice & TelePresence)

VCS Control VCE Expressway

TX Series

MXP, SX and C Series

IP Phones

Jabber Windows Jabber Mac OS X

SIP H.323 SCCP, MGCP, ISDN

Internet

PSTN

EX Series

Movi

TS and/or MCU for ad hoc and rendezvous

TMS

IP PSTN CUBE

Conductor

Any Endpoint

TS and/or MCU for scheduled

EX Series

WebEx-enabled TelePresence

Lync

TMS Prime

15

Architectural Evolution 2014

16

Expressway-C Expressway-E

IP Phones DX Series

Jabber Win, Mac, iOS and Android

SIP H.323 SCCP, MGCP, ISDN

Internet

Jabber Win, Mac, iOS and Android

TS and/or MCU for ad hoc, rendezvous

Any Endpoint

EX Series

SX, MX and C Series

Cloud-enabled TelePresence

TX Series

EX Series

Conductor

PSTN

IP PSTN CUBE

Lync

UC Manager 9.1 – 10.x (Combined Voice & TelePresence)

TMS

TS and/or MCU for scheduled

Prime

VCS Control

Architectural Evolution 2015

17

Expressway-C Expressway-E

IP Phones DX Series

Jabber Win, Mac, iOS and Android

SIP H.323 SCCP, MGCP, ISDN

Internet

Jabber Win, Mac, iOS and Android

Any Endpoint

EX Series

SX, MX and C Series

Cloud-enabled TelePresence

TX Series

EX Series

PSTN

IP PSTN CUBE

Lync

UC Manager 9.1 – 10.x (Combined Voice & TelePresence)

Prime

VCS Control

TS and/or MCU for ad hoc, rendezvous

& scheduled

Conductor

TMS

VCS

Webex Remote & Mobile

Access

Messaging & Queuing

Ad Hoc

Scheduled Meetings

HD Video

IM &

Presence

Telephony

Mobility

Edge Infrastructure

Expressway

CUBE / ISR-VG

SIP and Legacy PSTN Services

Interop and Legacy Video

Cisco Unified Collaboration Architecture

§  Unified CM for Registration and Call Control

§  SIP is the primary protocol - all endpoints register via SIP

§  VCS-C for legacy H.323 endpoints and/or Interop

§  SIP Trunk between Unified CM and VCS-C/Expressway C

§  Expressway C/E or VCS-C/E provides firewall traversal/B2B services

§  TS/MCU behind Conductor with SIP trunk to UCM

§  TMS is used for phone books on non-immersive endpoints and for scheduling

§  Prime Collaboration Manager is used for endpoint management and user provisioning

Best Practice for CUCM Video Deployment

§  Preferred Architectures provide prescriptive design guidance that simplifies and drives design consistency for Cisco Collaboration deployments.

§  Preferred Architectures are targeted at the Commercial, Commercial Select and small Enterprise customers, but can be used as a design base for larger customers.

Design Guidance Cisco Preferred Architecture

Dialing Options for CUCM

§  Using TMS phonebook sources for endpoints supporting folders (MX/SX/C)

§  Jabber and Unified CM only endpoints to use UDS (TX/IX/DX)

Phonebook Sources

Calling someone – Old School v’s Millennials

24

Dial a URI

Matches email and IM experience

Scales beyond organization

Dial a number

Same as dialing a phone or look up in directory.

Either way, easy and familiar

URI routing/dialing

•  Why –  Native dialing method in SIP based video equipment –  Extend support for SIP video endpoints registered with Cisco UCM –  Unambiguous dialing from directories –  better integration with other call controls where URI dialing is the native

dialing habit (e.g. VCS) –  Enables easier B2B video call routing

•  Limitations –  URIs can not be used for PSTN calls (as long as there’s no mapping to E.

164) –  Limited endpoint support (+E.164/numbers might still be the native format)

25

URI Dialing

•  In Cisco UCM all endpoints will still have a DN •  Alpha URI can be associated with DN on any device (not only SIP) •  Phones always register via the DN (do not necessarily even know that there is

an associated alpha URI)

DN: 2000

DN: 2001

URI: boardroom@cisco.com

URI: shawn@cisco.com

URIs and Directory Numbers

•  Up to 5 URIs can be configured per DN •  Enduser’s directory URIs are assigned to

directory numbers based on enduser’s primary extension; partition “Directory URI” (cannot be changed/deleted)

•  other URIs can be in any partition; no need to have them in the same partition as the DN

27

URIs and DNs

•  One URI associated with DN is marked the primary URI •  Auto-generated URI based on user’s primary extension will always be the

primary URI

•  If no auto-generated URI exists one of the other URIs can be marked “primary” •  Primary URI will be used as URI identity for calls from/to this line

Primary URI

28

Alpha URI vs. Number

•  Dialed “numbers” can contain: +, 0-9, *, A-D

•  SIP Profile now has “Dial String Interpretation” setting

•  relevant for calls from endpoints and trunks

•  Default: 0-9, * and + (Recommended)

•  Recommendation: use un-ambiguous alpha URIs

•  “user=phone” tag in request URI forces treatment as numeric URI

How to Differentiate Between a Number and an Alpha URI

29

Calling URIs

•  URIs can be called if the URIs’ partition is member of calling CSS

•  CSSs can contain DN and URI partitions

•  partitions can contain DNs and URIs •  CSS/partition logic for URIs is

identical to DN logic

30

Calling Search Space

DN \+4961007739764

Directory URI

jkrohn@cisco.com Device

User dials “jkrohn@cisco.com”

User dials “+4961007739764”

\+4961007739123

alice@cisco.com

CUCM Video Conferencing Considerations

§  What type of conferencing is required? §  CMR Instant (ad-hoc) §  CMR Personal (rendezvous) §  CMR Scheduled

§  Conferencing resource management §  Video bridge ports are valuable. §  Ports are required for CMR Instant meetings §  Ports for scheduled conferences should be guaranteed

Video Conferencing Considerations

Conferencing Types of Conferences

Description

CMR Instant (ad-hoc) A conference that is not scheduled or organized in advance.

CMR Personal (rendezvous)

A conference that requires callers to dial a predetermined number or URI to reach a shared conferencing resource.

CMR Scheduled A conference planned in advance with a predetermined start and stop time.

Conferencing Components for Conferencing

Component Description

Cisco TelePresence Conductor Manages and allocates conferencing resources requested from Unified CM

Cisco TelePresence Server Provides voice and video conferencing.

Available on dedicated hardware platforms and on virtual machine.

Cisco TelePresense Management Server

Management for endpoint reporting and calendar integration.

§  Starting point – Add Conductor and Telepresence Server to CUCM

§  Recommended deployment is based on Preferred Architectures §  CMR Instant and CMR Personal

§  Scheduling through Conductor §  Dedicated and Shared bridge model

§  CMR Hybrid adds WebEx to on premise conferencing

Conferencing on CUCM

§  Configuring SIP Trunks between Unified CM and Conductor for Instant and Personal conferences.

§  CMR Instant and CMR Personal conferences: §  UCM routing calls to conferences that will be dynamically created by Conductor. §  Conferences are not static but can be initiated at any time. §  Not configured or tied to specific bridge resources.

Conferencing on UCM CMR Instant and CMR Personal

Conferencing on UCM CMR Instant and CMR Personal

TelePresence Servers

Conductor

Pool 1 Pool 2

SIP H.323 SCCP, MGCP, ISDN Management SIP and API Control

CM

R

Instant CM

R

Pers

onal

Internet

UC Manager

Lync

VCS Control VCS Expressway

MCU / TS

SX, MX, C, Profile Series

TX/IX Series

EX Series

CTS/TX Single

PSTN

IP PSTN

Any Endpoint

TMS Prime

MXP Jabber Win, Mac, iOS and Android

EX Series

§  Historically scheduling has used dedicated resources to guarantee that a specific number of ports will be available throughout the scheduled meeting.

§  Previous versions of TMS supported limited Conductor scheduling with several major caveats. New releases of TMS 14.6, Conductor XC3.0 and TS4.1 help alleviate many of the initial challenges of placing scheduling resources behind Conductor.

§  Remote-managed bridges, MultiParty Media 310/320 and Virtual TelePresence Servers, can NOW be scheduled, along with the 8710.

§  Conference placement is done at conference start time.

Conferencing on UCM Scheduling through Conductor

Conferencing on UCM Scheduling through Conductor

Dedicated Resources Shared Resources •  100% guaranteed scheduled conferences. •  Similar to previous TMS deployment with

directly managed TelePresence Servers. •  Single TS, in single Bridge Pool, in single

Service Preference. TMS can have multiple Service Preferences in a prioritized list.

•  Based on Conductor IP Zone, so possible loss of conference placement intelligence if using IP Zones with directly managed bridges.

•  Simplest deployment, TelePresence Servers are dynamically allocated for any type of conference.

•  Scheduled conferences are best-effort service just as Instant and Permanent conferences are.

•  If utilization is high, additional TelePresence Servers can be deployed.

•  Takes advantage of Optimized Conferencing.

Conferencing on UCM Scheduling through Conductor

UCM TMS Conductor

Pool 3

CMR Instant, CMR Personal and scheduling - shared bridge

Scheduling – dedicated bridge

Pool 4 Pool 5

Pool 1 Pool 2

Single Bridge per Pool

SIP SIP and API control

CUCM Video Conferencing Licensing

Cisco TelePresence Room License: Includes rights to one Cisco TelePresence Room-based system, including Cisco TelePresence, Profile, and Solution Series platforms.

CUCM Video Endpoint Licensing

MX700 – 55’’ MX800 – 70’’ IX5000 – 65’’ MX300 G2 – 55’’

SX20

SX10

SX80

Cisco Collaboration 10 Licensing Summary

Personal Multiparty ü + + + +

WebEx Conferencing ü + + + +

Unity Connection ü ü + + +

Expressway ü ü ü N/A N/A

Jabber UC ü ü ü N/A N/A

Jabber IM/P ü ü ü ü ü

Prime Collaboration ü ü ü ü ü

# of Devices Supported Multiple Multiple Two / One One One

CUWL Professional

CUWL Standard

UCL Enhanced Plus /

Enhanced UCL

Basic UCL

Essential

CPE & Hosted

CPE & Hosted

Personal Multiparty Allows for up to 4 parties in a video conference; included in CUWL Pro

WebEx Conferencing One Named User license for both WebEx Meeting Center (1 year) AND WebEx Meetings Server; included in CUWL Pro

Expressway Remote Worker Firewall traversal for voice and video; included in UCL Enhanced & above ------------------------- Firewall traversal for IM&P; included with all UCM licenses

Prime Collaboration Cisco Prime Collaboration Standard; included with CUCM

ü = included w/ license + = optional add-on N/A = not available w/ license

Multiparty Licensing Overview All licenses include unlimited meetings, HD Video, Audio and Content Sharing and more!

Personal Multiparty Basic

Included with CUWL-Pro

Good for small meetings

Personal Multiparty

Advanced Per host, perpetual

Ideal formost Deployments

4 people per meeting 1 host license High-definition Video

Unrestricted meeting size 1 host license Full HD Video

Meeting Type: Ad-hoc Personal CMR

Meeting Type: Ad-hoc Personal CMR Scheduled

Reach: Lync interoperability External participants

Enterprise Agreement

Per host, perpetual

Pervasive video for all

Unrestricted meeting size Unrestricted host licenses Unrestricted video quality

Meeting Type: Ad-hoc Personal or Device CMR Scheduled

Reach: Lync interoperability External participants

RECOMMENDED ENTERPRISE

Personal Multiparty Activations

Activations

Each Personal Multiparty Basic license

includes:

Each Personal Multiparty Advanced license

includes:

Telepresence Server 8 Screen Licenses on first order +

1 Screen License for every 30 users 11 Screen Licenses on first order +

1 Screen License for every 15 users (rounded up)

TelePresence Conductor**

1 Full Conductor License

2 Full Conductor Licenses

Lync Interoperability None 1 Lync interop license on first order

+ 1 additional Lync license for every 300 users (rounded up)

*Expressway Rich Media Session (RMS E or C)

None

5 RMS licenses on first order + 1 RMS licenses for every 15 users (rounded up)

TMS Managed Devices** None 25 device licenses on first order

*Two RMS licenses (one loaded on Expressway-C and one on Expressway-E) are required for each concurrent B2B Call. Only one RMS license is required on Expressway-C for each concurrent Lync call. **additional licenses should be purchased a-la-carte

Video Architecture Traditional

VCS-Centric Traditional

UCM-Centric Mix

VCS+UCM Strategic Direction

Call Control VCS-C UCM UCM and VCS-C UCM

SIP Registration VCS-C UCM UCM and VCS-C UCM

H.323 Registration VCS-C UCM VCS-C (for legacy only) VCS-C (for legacy only)

Conferencing Control VCS-C UCM

Conductor or VCS-C/UCM for Adhoc & Rendezvous

Conductor

VCS-C/CUCM for Scheduled

Conferencing Bridge MCU CTMS CTMS, TS and/or MCU TS

Conference Scheduling TMS CTS Manager TMS or CTS-Man TMS

Remote Access VCS-E ASA VCS-E and/or Expressway Series Expressway Series

Provisioning TMS UCM UCM and/or TMS Prime Collaboration

Management TMS UCM UCM, TMS or Prime Collaboration Prime Collaboration

VCS and UCM Comparison Capability VCS Unified CM

Device Registration Manual (or via TMS) Auto-registration, DHCP Option 150 or Manual

Protocols H.323 & SIP SIP

Dialing Behavior URI or Alias based dialing and IP dialing Focused on numeric (DN) dialing which can be aliased with URIs

Device security SIP/H.323 authentication, TLS, SRTP SIP authentication, phone certificates, TLS, SRTP

Device feature management N/A – done by TMS Native

Dial plan handling Zones, subzones, transforms, search rules, regex

Partitions, calling search spaces, filters, calling and called party transformations, route patterns, URI

aliases

User routing rules “FindMe” application Shared Line or 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

Application control N/A Voicemail, WebEx conferencing, IM&P, CTI

Benefits of Endpoint Registration on CUCM §  CUCM 10.5 makes it easier to register endpoints on UCM and fully manage them, no

matter how they are connected to the network (VPN or Expressway)!

Registration Device Provisioning

Device Management

Endpoint OBTP TMS scheduling*

Directories/ Phone Books VOIP Jabber

Immersive (CTS/TX)

On Campus endpoints on UCM

UCM/Prime UCM/Prime TMS UCM/UDS

or TMS (from 14.4 with TP ep´s 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

Not supported

Remote via Expressway to VCS Control

TMS(PE) No IP access to the device

No IP access to the device TMS Not

supported Not

supported Not

supported

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

§  Verify Existing and/or any new user requirements §  Identify critical features and system functionality

§  Collect information on existing endpoints and users

§  Identify New Components Required for the New Architecture

§  Develop new design

§  Map Features/Functionality and User Requirements to the New Architecture

High-Level Migration Strategy Planning

§  Recommended order for migration/implementation 1.  Upgrade existing devices to new versions 2.  New Provisioning Component (Cisco Prime) 3.  Call Control Components (Implement New UCM if one does not exists) 4.  Migrate Endpoints (VCS to UCM) 5.  Migrate Conferencing (VCS to UCM)

User communicate and education on ALL experience changes is critical

High-Level Migration Strategy Implement

§  Create software strategy for new design §  Upgrade existing components to new versions required for the design §  For new devices implement them with the versions required for the design

§  Map Features/Functionality and User Requirements to the New Architecture

High-Level Migration Strategy Software Strategy & Feature/Functionality/User Requirements

§  Dial-plan §  Conferencing design (dedicated or

shared resources) §  Interop with H.323 endpoints §  Recording §  Unified Mobility/Find-Me

§  Provisioning §  Scheduling §  Management §  Directory/Phone Book §  WebEx Integration §  Remote Access (MRA) / B2B

Cisco strategic direction to utilize CUCM as the unified voice and video call control platform

Video as easy as voice. Reduce complexity and provide a best possible user experience.

Key Takeaways

Additional Resources

§  Cisco dCloud is a self-service platform that can be accessed via a browser, a high-speed Internet connection, and a cisco.com account

§  Customers will have direct access to a subset of dCloud demos and labs

§  Restricted content must be brokered by an authorized user (Cisco or Partner) and then shared with the customers (cisco.com user).

§  Go to dcloud.cisco.com, select the location closest to you, and log in with your cisco.com credentials

§  Review the getting started videos and try Cisco dCloud today: https://dcloud-cms.cisco.com/help

dCloud

Customers now get full dCloud experience!

§  http://dcloud.cisco.com

§  Cisco dCloud provides powerful self-service capabilities

§  Repeatable demonstrations and customized labs with complete administrative access.

Preferred Architecture for Video On Cisco Demo Cloud

§  Cisco Advanced Services offers Strategy & Architecture services to assist customer in planning and preparing for an (architecture) migration

§  Cisco Advanced Services offers Plan, Design, & Implement (PDI) services to help customers with any migrations

§  Cisco Services provides Cloud and Managed services for customers who are looking to migrate to a “cloud” architecture

§  Private Cloud §  Hybrid (On-premise and Cloud) §  Managed On-premise §  Integration with Cloud Conferencing Services (e.g. CMR Cloud)

Cisco Advanced Services

§  CTS-Man to TMS §  CTMS to TPS

§  VCS-C to UCM §  TPS behind UCM & Conductor

§  VCS-C/E to Expressway Core/Edge

§  Cisco Unified Communications Manager Upgrade http://www.cisco.com/web/solutions/vnlanding/comm_manager_upgrade.html

§  Cisco TelePresence Conductor with Unified CM – Deployment Guide http://www.cisco.com/c/dam/en/us/td/docs/telepresence/infrastructure/conductor/config_guide/xc3-0_docs/TelePresence-Conductor-Unified-CM-Deployment-Guide-XC3-0.pdf

§  Cisco Collaboration Meeting Rooms (CMR) Premises – Solution Guide (v4.0) http://www.cisco.com/c/dam/en/us/td/docs/telepresence/infrastructure/solutions/cmrpremises/cmr-premises-solution-guide-r4-0.pdf

§  Cisco Preferred Architecture for Enterprise Collaboration http://www.cisco.com/c/en/us/td/docs/solutions/CVD/Collaboration/enterprise/collbcvd.html

Additional Publications

§  Give us your feedback and you could win a Plantronics headset. Complete the session survey on your Cisco Connect Toronto Mobile app at the end of your session for a chance to win

§  Winners will be announced and posted at the Information desk and on Twitter at the end of the day

You must be present to win!

Complete your session evaluation – May 14th

Thank you.