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
House Keeping Notes

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
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
Session Objectives

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.
Icons used in this presentation
Unified
Communications
Manager
Directory Generic
Server or DHCP Server
Expressway Core Immersive TelePresence
(formerly VCS Control) Phone Book
System (CTS / TX Series)

Multipurpose TelePresence
AnyConnect Cisco IOS
Expressway Edge or System (Profile, MX, SX, C Series)
VPN Client Router with
Unified Border Element
VPN Client
(CUBE)
Personal TelePresence
TelePresence System (EX Series)
Advanced Generic
Management Security Firewall / NAT
Suite or Prime Appliance Unified IP Video Phone
Collaboration (ASA) (8900, 9900, DX 650 Series)

TelePresence PC client BYOD client

Server or MCU Home Branch Large (Jabber for (Jabber for
Office Office Office Windows / IOS / Android)
Mac)

TelePresence Network
Conductor
Acronyms used in this presentation
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
Agenda
§  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
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 Every Every

Room Desk 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
Prime TMS
ISDN
IP Phones UC Manager (Voice)
CUPC MCU VCS Control VCS Expressway
Video Advantage TS
IP Communicator
Internet

PSTN

T1 EX Movi

CTS
Single
T3 MXP, SX, Profile Series

CTS
Triple •  TelePresence and UC endpoints control, B2B connectivity, bridging,
typically deployed on separate UCM scheduling and management
clusters •  Different dial plans (numerical vs.
B2B UC Manager
Exchange (TelePresence) •  Limited interoperability between alpha-numeric centric)
CUBE
endpoints (TelePresence Server was •  Different methods of provisioning,
SIP the bridge between these formerly management and monitoring
H.323 CTMS non-interoperable worlds)
•  Feature inconsistency across the
SCCP, MGCP, CTSMAN •  Lots of product functional overlap in portfolio
ISDN
every category: endpoints, call
 Architectural Evolution
Circa 2011 – 2013
Prime TMS
UC Manager 8.6 – 9.0
IP Phones (Combined Voice & TelePresence) WebEx-enabled
Jabber Windows TelePresence
VCS Control VCE Expressway
Jabber Mac OS X

Internet
EX Series

Any Endpoint
TX Series Lync
EX Movi
Series
Conductor TS and/or MCU
for scheduled
PSTN
TMS
MXP, SX and C Series
IP PSTN CUBE
TS and/or MCU for
ad hoc and rendezvous

SIP
H.323
SCCP, MGCP,
ISDN
 Architectural Evolution
2014
Prime
IP Phones
DX Series UC Manager 9.1 – 10.x
(Combined Voice & TelePresence) Cloud-enabled
Jabber Win, Expressway-C Expressway-E TelePresence
Mac, iOS and Android

Internet
EX Series

SX, MX and VCS Control Any Endpoint

C Series
EX Jabber Win,
Lync
Series Mac, iOS and
Android
TX Series
Conductor
TS and/or MCU
for scheduled PSTN
TMS
TS and/or MCU
for ad hoc, rendezvous IP PSTN
SIP CUBE
H.323
SCCP, MGCP,
ISDN
 Architectural Evolution
2015
Prime
IP Phones
DX Series UC Manager 9.1 – 10.x
(Combined Voice & TelePresence) Cloud-enabled
Jabber Win, Expressway-C Expressway-E TelePresence
Mac, iOS and Android

Internet
EX Series

SX, MX and VCS Control Any Endpoint

C Series
EX Jabber Win,
Lync
Series Mac, iOS and
Android
TX Series

Conductor
TMS PSTN

TS and/or MCU
for ad hoc, rendezvous
IP PSTN
SIP & scheduled CUBE
H.323
SCCP, MGCP,
ISDN
Cisco Unified Collaboration Architecture
Edge
Scheduled
Meetings
HD Video
Infrastructure
Webex
Mobility Remote & Mobile
Ad Hoc
Access

IM &
Expressway

Messaging &
Queuing
Presence

Telephony
SIP and Legacy
PSTN Services

CUBE / ISR-VG

Interop and
Legacy Video

VCS
Best Practice for CUCM Video Deployment
§  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
Design Guidance
Cisco Preferred Architecture
§  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.
Dialing Options for CUCM
Phonebook Sources

§  Using TMS phonebook sources for endpoints supporting folders (MX/SX/C)
§  Jabber and Unified CM only endpoints to use UDS (TX/IX/DX)
Calling someone – Old School v’s Millennials

Dial a number Dial a URI

Same as dialing a phone or Matches email and IM

look up in directory. experience
Either way, easy and familiar Scales beyond organization
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)
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
URI: boardroom@cisco.com

DN: 2001
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
URIs and DNs
Primary URI
•  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

28
Alpha URI vs. Number
How to Differentiate Between a Number and an Alpha URI
•  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
29
Calling URIs
Calling Search Space
•  URIs can be called if the URIs’ User dials
partition is member of calling CSS “+4961007739764” DN
\+4961007739764
•  CSSs can contain DN and URI
partitions \+4961007739123

•  partitions can contain DNs and URIs

•  CSS/partition logic for URIs is
Directory URI
identical to DN logic Device
jkrohn@cisco.com
User dials
alice@cisco.com
“jkrohn@cisco.com”

30
CUCM Video Conferencing
Considerations
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
Conferencing
Types of Conferences

Description

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

CMR Personal A conference that requires callers to dial a predetermined number or URI
(rendezvous) to reach a shared conferencing resource.

A conference planned in advance with a predetermined start and stop

CMR Scheduled
time.
Conferencing
Components for Conferencing
Component Description

Manages and allocates conferencing resources

Cisco TelePresence Conductor
requested from Unified CM

Provides voice and video conferencing.

Cisco TelePresence Server Available on dedicated hardware platforms and on virtual
machine.

Cisco TelePresense Management Management for endpoint reporting and calendar

Server integration.
Conferencing on CUCM

§  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 UCM
CMR Instant and CMR Personal

§  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
Prime TMS
MCU / TS

UC Manager
EX Series VCS Control VCS Expressway

SX, MX, C, Internet

Profile Series

TX/IX Series
Any Endpoint

onal
Jabber Win,
Insta

CMR
C MR

CTS/TX Lync EX
MXP Series Mac, iOS and
Single Pers
nt

Android

Conductor
PSTN

SIP
IP PSTN
H.323
SCCP, MGCP, ISDN Pool 1 Pool 2
Management TelePresence Servers
SIP and API Control
Conferencing on UCM
Scheduling through Conductor
§  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

Dedicated Resources Shared Resources

•  100% guaranteed scheduled conferences. •  Simplest deployment, TelePresence Servers
•  Similar to previous TMS deployment with are dynamically allocated for any type of
directly managed TelePresence Servers. conference.

•  Single TS, in single Bridge Pool, in single •  Scheduled conferences are best-effort
Service Preference. TMS can have multiple service just as Instant and Permanent
Service Preferences in a prioritized list. conferences are.

•  Based on Conductor IP Zone, so possible •  If utilization is high, additional TelePresence

loss of conference placement intelligence if Servers can be deployed.
using IP Zones with directly managed •  Takes advantage of Optimized Conferencing.
bridges.
Conferencing on UCM
Scheduling through Conductor
TMS UCM Conductor

SIP
SIP and API control

Pool 3 Pool 4 Pool 5

Pool 1 Pool 2

Single Bridge per Pool

Scheduling – dedicated CMR Instant, CMR Personal and

bridge scheduling - shared bridge
CUCM Video Conferencing
Licensing
CUCM Video Endpoint Licensing

Cisco TelePresence Room License:

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

SX10

SX20

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

SX80
Cisco Collaboration 10 Licensing Summary
Personal Multiparty
Allows for up to 4 parties in a video Personal Multiparty ü + + + +
conference; included in CUWL Pro
WebEx Conferencing ü + + + +
WebEx Conferencing
One Named User license for both Unity Connection ü ü + + +
WebEx Meeting Center (1 year) AND
WebEx Meetings Server; included in
CUWL Pro Expressway ü ü ü N/A N/A

Expressway Remote Worker Jabber UC ü ü ü N/A N/A

Firewall traversal for voice and video;
included in UCL Enhanced & above CPE & CPE &
Jabber IM/P Hosted ü Hosted ü ü ü ü
-------------------------
Firewall traversal for IM&P; included
with all UCM licenses Prime Collaboration ü ü ü ü ü

Prime Collaboration # of Devices Supported Multiple Multiple Two / One One One

Cisco Prime Collaboration Standard;

UCL
included with CUCM CUWL CUWL UCL UCL
Enhanced Plus /
Professional Standard Basic Essential
Enhanced
ü = 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!

RECOMMENDED ENTERPRISE

Personal Multiparty Personal Multiparty Enterprise

Basic Advanced Agreement
Included with Per host, perpetual Per host, perpetual
CUWL-Pro
Ideal formost
Good for small Pervasive video for all
Deployments
meetings
4 people per meeting Unrestricted meeting size Unrestricted meeting size
1 host license 1 host license Unrestricted host licenses
High-definition Video Full HD Video Unrestricted video quality
Meeting Type: Meeting Type: Meeting Type:
Ad-hoc Ad-hoc Ad-hoc
Personal CMR Personal CMR Personal or Device CMR
Scheduled Scheduled
Reach: Reach:
Lync interoperability Lync interoperability
External participants External participants
Personal Multiparty Activations
Activations Each Personal Multiparty Basic license Each Personal Multiparty Advanced license
includes: includes:

8 Screen Licenses on first order + 11 Screen Licenses on first order +

Telepresence Server
1 Screen License for every 30 users 1 Screen License for every 15 users (rounded up)

TelePresence Conductor** 1 Full Conductor License 2 Full Conductor Licenses

1 Lync interop license on first order

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

*Expressway Rich Media Session 5 RMS licenses on first order +

None
(RMS E or C) 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 Traditional Mix Strategic Direction
VCS-Centric UCM-Centric VCS+UCM

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)

Conductor or VCS-C/UCM for

Adhoc & Rendezvous
Conferencing Control VCS-C UCM 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

VCS-E and/or
Remote Access VCS-E ASA
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

Focused on numeric (DN) dialing which can be

Dialing Behavior URI or Alias based dialing and IP dialing
aliased with URIs

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

Device feature
N/A – done by TMS Native
management

Partitions, calling search spaces, filters, calling and

Zones, subzones, transforms, search rules,
Dial plan handling called party transformations, route patterns, URI
regex
aliases

User routing rules “FindMe” application Shared Line or Single Number Reach

Global, regional, inter-cluster, on local trunks and

Bandwidth control (CAC) Subzones, pipes and links
device network topologies

Trunks Zone Trunk/Partitions/Calling Search Spaces

Hunt pilot queuing, routing, announcements, contact

Call Queuing N/A
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)!
Endpoint
Device Device OBTP TMS Directories/ Immersive
Registration Provisioning Management scheduling* Phone Books VOIP Jabber (CTS/TX)
On Campus UCM/UDS
endpoints on UCM/Prime UCM/Prime TMS or TMS (from 14.4 √ √ √
UCM with TP ep´s only)

Remote via
No IP access to
Expressway to UCM/Prime UCM/Prime the device UCM/UDS √ √ √
UCM
On Campus
Not Not Not
endpoints on VCS TMS TMS TMS TMS supported supported supported
Control
Remote via
No IP access to No IP access to Not Not Not
Expressway to TMS(PE) the device the device TMS supported supported supported
VCS Control
* TMS can schedule any endpoint into a conference, but OBTP is only available to campus devices
High-Level Migration Strategy
Planning

§  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
Implement
§  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
Software Strategy & Feature/Functionality/User Requirements
§  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
§  Dial-plan §  Provisioning
§  Conferencing design (dedicated or §  Scheduling
shared resources) §  Management
§  Interop with H.323 endpoints §  Directory/Phone Book
§  Recording §  WebEx Integration
§  Unified Mobility/Find-Me §  Remote Access (MRA) / B2B
Key Takeaways

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.
Additional Resources
 dCloud

Customers now get full dCloud experience!

§  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
Preferred Architecture for Video
On Cisco Demo Cloud

§  http://dcloud.cisco.com
§  Cisco dCloud provides powerful
self-service capabilities
§  Repeatable demonstrations and
customized labs with complete
administrative access.
Cisco Advanced Services
§  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
§  CTS-Man to TMS §  VCS-C to UCM §  VCS-C/E to Expressway
§  CTMS to TPS §  TPS behind UCM & Conductor Core/Edge

§  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)
Additional Publications
§  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
Complete your session evaluation – May 14th
§  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!
Thank you.