Brkevt 2800

Overview of Cisco TelePresence
Solution and Deployments

BRKEVT-2800
Michael Thomma
Technical Marketing Engineer
mithomma@cisco.com

2014 Cisco and/or its affiliates. All rights reserved. BRKEVT-2800 Cisco Public
Overview of BRKEVT-2800
3
This session provides an overview for all components of a TelePresence
deployment including: endpoints, call control, conferencing, and
scheduling/management. Subsequent breakout sessions will cover specific
components of the TelePresence solution in depth. Recent releases/products
and new features and functionality will be introduced and explained.

Throughout this presentation, use cases will be referenced to demonstrate
deploying TelePresence in different environments. Endpoints, call control,
multipoint, and management design decisions will be explained. This breakout
will cover CUCM, VCS, TelePresence Server, Conductor, TMS, and endpoints.
Your Collaboration Agenda For Cisco Live!
4
Session Number Session Name Speaker Day
BRKUCC-2343 Call Admission Control and Quality of Service for Collaboration Glen Lavers Tuesday
BRKEVT-2800 Overview of Cisco TelePresence Solution and Deployments Michael Thomma Tuesday
BRKUCC-2934
Implementation and Management of Cisco's Enterprise Session Border
Controller - Cisco Unified Border Element Darryl Sladden Tuesday
BRKCOL-2020 Cisco Interoperability with Microsoft Tobias Neumann Tuesday
BRKCOL-2023 Architecting Unified Communications to enable Workspace Transformation Vanessa Sulikowski Tuesday
BRKUCC-2344 Deploying Cisco Jabber on Mobile Devices Seongho Hong Tuesday
BRKUCC-2801 Cisco Expressway at the Collaboration Edge design session Kevin Roarty Tuesday
BRKUCC-2008 Enterprise Dial Plan Fundamentals Johannes Krohn Wednesday
BRKUCC-2444 Introduction to Common Identity for Collaboration Paulo Jorge Correia Wednesday
BRKCOL-2777 Emerging Video Technologies: H.265, SVC, and WebRTC Mo Zanaty Wednesday
BRKEVT-2400 Scheduling Best Practices in Telepresence and Collaboration Aniello Zanfardino Wednesday
BRKEVT-2803 Designing and deploying multipoint conferencing for telepresence video Richard Murphy Wednesday
BRKUCC-2340 Best practices to enable rich-media Collaboration between businesses Viraj Raut Wednesday
BRKEVT-2804 Monitoring and troubleshooting network impairments in video deployments Aamer Akhter Wednesday
BRKUCC-3000 Advanced Dial Plan Design for Unified Communications Networks Johannes Krohn Thursday
BRKCOL-2111 Capture Transform Share Robert Morris Thursday
BRKEVT-2802
Deploying TelePresence and Video Endpoints on Unified Communications
Manager Kevin McMenamy Thursday
BRKUCC-2800 Extend the Reach of Your Cisco Video Solution with Cisco Jabber Guest Darin Dunlap Thursday
BRKCOL-2114 What you need to know about Webex Enabled TelePresence Andrew Bell Thursday
BRKCOL-2369 Integrating Audio Visual Systems with TelePresence Codecs Enrico Conedera Thursday
BRKUCC-3420 Advance concepts to Common Identity for Collaboration Paulo Jorge Correia Friday
BRKUCC-2943 Enabling Cisco Jabber for Virtual Environments Sijin Abdulkarim Friday
Conferencing
Call Control
Edge UC Applications
Internet
MPLS WAN
PSTN /
ISDN
Headquarters
Remote Site
Mobile Worker Management
TS
Conductor
Endpoints
Prime
Collaboration
Unified CM
Unity
Connection
Contact
Center
TS
TS
Collaboration Architecture Overview
TMS
ISR G2
VCS-C
VCS-E
CUBE
ISR G2
Other UC
Applications
UC App
DMZ
CUPs
Agenda
Introduction
Pillars of Cisco solution, Terminology, Use Cases
Users and Endpoints
User needs and expectations, Endpoint Differentiators, New Endpoints and Software Releases
Deploying on the Network
CDP, Media Resiliency
Call Control
Unified CM, How VCS fits, Expressway, Dial Plan
Conferencing
Types of Conferences, TelePresence Server, MCU, Conductor
Scheduling and Management
TMS 14,TMS Extensions, Interaction with Infrastructure and Endpoints, WebEx Enabled TelePresence
(WeT)
Q&A, Roadmap

6
Introduction
7
Introduction
Expanding TelePresence to a Pervasive Video Solution
8
Challenges
Keeping the focus on the experience and not the technology being used
Making video as easy and reliable as voice communications
Innovating new ways to collaborate
Web
Collaboration
Pervasive Video
Soft Clients Multipurpose
Video
Fully
Immersive
Desktop Video
Interoperability
Intercompany
WebEx
New
experiences
Doing more,
better
Low TCO
Standards-
based
Investment
protection
Scalability
One button
to push
Active Presence
Intuitive controls
Integrated
scheduling
Ad hoc flexibility
Natural
communication
High definition
Face-to-face,
in person
experience
Low latency
Wideband audio
Simplicity Quality Reliability Collaboration
Introduction
Pervasive video characteristics
9
Introduction
Terminology - OBTP (One Button to Push)
10
User schedules
TelePresence rooms in
Outlook
User receives
confirmation email
Participants enter
their TelePresence
Rooms
One button
press to
launch call
OBTP:
Users and Endpoints
11
Users and Endpoints
TC and TX/CTS Endpoints
12
EX90
Profile 65 Profile 55
EX60
Profile 42
CTS 500-32
CTS/TX endpoints TC based endpoints (SX/EX/MX/C series)
(all run TC software)
C20
SX20
CTS 1100 TX 13x0-65
CTS 3xx0 TX 9xx0
MX200/300
C90
C40 C60
Latest Endpoint Release:
CTS: 1.10.3 (41) Nov 2013
TX: 6.1.0 (90) Nov2013
Latest Endpoint Release:
TC: 7.0.2 Jan 2013
Users and Endpoints
Determining the Proper Experience for Users
How immersive must the experience be?
Resolution, mono/stereo/spatial audio
Screen size, camera quality
Will the user share content? If so what type of content?
Doc cam, H.239 and BFCP
Motion vs sharpness
Will they be mobile?
VPN home offices and non-VPN offices
BYOD
What environment will the endpoint be in?
Personal space, dedicated room
How simple must it be?
Users and Endpoints
Ciscos Consistent User Experience
14
Cisco Touch 8
Cisco TelePresence Server
Consistent user experience is more intuitive

Users require less training for new rollouts,
reducing time and resources normally needed
for user training
The user is being trained, but in a
way that seems natural.
Cisco Touch 12
Jabber for iPad
Jabber for Windows
Users and Endpoints
15
Users and Endpoints
TX9000 series
16
What weve kept from the CTS and T3:
Spatial wideband audio
65 Plasma displays
2-seat table segments
One Button to Push
SIP and TIP over SIP support
Allows up to 18 participants with TX9200
Central wiring tray to avoid trenching
Front panel access to codecs and cabling

Series Product Family Endpoints
TX Immersive TX9000, TX9200, TX1310
MX Multipurpose MX200, MX300
SX Solutions SX20
EX Executive EX60, EX90
DX Smart Desk Phone DX650
C Integrator C20, C40, C60, C90
What weve improved on:
Flat reflective light panel
Less-intrusive camera cluster
Choice of table color: Maple or Dark Walnut
42 LED content screen
Easier assembly
Easier access to power and network connections

Supported on CUCM 8.5 and above
Users and Endpoints
What is it?
The newest IP phone from Cisco (it also does video!)
Introducing the DX650
17
Supported on CUCM 7.1.5, 8.5, 8.6, 9.0 and above
Main features:
7-inch multitouch screen
Bluetooth
2 USB 2.0 ports
HDMI output up to 1920 x 1200
Android 4.0
PoE
1080p30 Full HD video

Users and Endpoints
Main features:
55 screen with 1080p60 video resolution
Multisite capable (3+1) (requires option key)
Dual display output
New Touch 10 Interface
10 bright & sharp (IPS) screen
Hard buttons for easy access
Wheel base, Floor stand, Wall mount
Based on SX20 codec
Introducing the MX300 G2
18

Supported on TC7 and later
Available Now!
Users and Endpoints
Introducing the Speaker Track 60
19

Will be Supported with C40, C60 and
C90 codecs on TC 7.0.1 or later
Main features:
Superior HD video quality 1080p60
Exceptional zoom capability 10x optical, 20x with
digital
Low latency, direct switching between speakers
Both cameras can be used independently when
Speaker Track 60 is off
Exceptional accuracy in tracking of active speakers,
including facial recognition
Recognition of partial faces
Vertical and horizontal tracking
Dual hunting camera capable

Available 1H CY14
20
Users and Endpoints
URI dialing in Jabber for Windows
Video added to Jabber for iPhone (already present in iPad)
Jabber for Mac now supported on Apple OS X Mavericks 10.9
Jabber for iPad now supported on IOS 7
Jabber for Windows 9.2 Localizations:

Jabber Update
21
Jabber for Windows: 9.6(0) Dec 2013
Jabber for Mac: 9.2(1) Sep 2013
Jabber for iPad: 9.3(4) Nov 2013
Jabber for iPhone: 9.5 Oct 2013
Jabber for Android: 9.1(3) June 2013
No video
(voice and IM)
Arabic Italian Bulgarian
Catalan (Spain) Japanese Romanian
Chinese (China) Korean Croatian
Chinese (Taiwan) Norwegian Slovak
Czech Polish Slovenian
Danish Portuguese (Brazilian) Serbian
Dutch Portuguese (Portugal) Russian
English Spanish Finnish
French Swedish Hungarian
German Thai Hebrew
Greek Turkish
Comparison of Cisco video capable endpoints
22
Jabber DX 650 EX Series MX Series Profiles TX 1310 TX 9x00
Capacity
Content
Sharing
Resolution
Remote
Registration
External
Screen
OBTP
Headset
/Handset
Embedded
Multisite
1 person
Depending on
client computer
Depending on
client computer
Up to 720p
With VPN
connection
1 person
Up to 1080p30
With VPN
connection
EX90 only
Up to 1080p60 Up to 1080p30 Up to 1080p60 Up to 1080p60 Up to 1080p60
With traversal
connection
With traversal
connection
With traversal
connection
EX90 only Audio only Audio only Audio only
1 person
Depends on system
and environment
Up to 6 people Up to 18 people
Depends on system
and environment
Aux audio input Aux audio input
SIP and TIP
23
What is TIP?
TelePresence Interoperability Protocol (TIP) evolved from a protocol Cisco designed and created to overcome
challenges faced in multiscreen/multichannel TelePresence environments.
Is TIP proprietary?
Cisco created, then transferred ,TIP to the IMTC (International Multimedia Teleconferencing Consortium) to license
royalty-free. Today several third party vendors have implemented TIP on their endpoints and infrastructure.
What is the relationship between SIP and TIP?
TIP relies on an initial call negotiation using SIP. SIP is responsible for negotiating the RTP and RTCP IP
addresses and ports. These RTP/RTCP channels are used not just for media, but also for the TIP signaling
messages. TIP will take over after SIP and re-negotiate things like the number of video and audio streams,
multiplexing of multiple media streams, etc.
H.323
MGCP
SCCP
ISDN
TIP
TIP is used in conjunction with SIP
SIP Invite
SIP Trying, Ringing, 200 OK
RTP/RTCP negotiated by this point via SIP SDP
TIP negotiation
Users and Endpoints
Standards Support
24
CTS/TX endpoints support SIP for call setup and media negotiation
starting in release 1.7.4 and later (available for nearly 3 years)
H.264 baseline profile when TIP is not used
Single screen support only (CTS 3x00 and TX 9x00 will only use center screen)
CUCM 8.5 or later required
No configuration necessary for this. If TIP fails to negotiate endpoint will fallback to standard SIP
TC based endpoints support standard H.323 and SIP for call setup/media
negotiation
H.261, H.263, H.263+, H.264
Receive and transmit up to 1080p 30fps (60fps on some endpoints)

CTS/TX will
always transmit at
30fps, but can
receive any frame
rate
http://www.cisco.com/en/US/docs/telepresence/interop/endpoint_interop.html
Users and Endpoints
When will a Cisco endpoint use TIP?
25
TX and CTS triple-screen endpoints are capable of using standard SIP signaling to
negotiate media. However, only center display is active, and the three cameras will
switch based on active speaker.
Since SIP and TIP both support HD video and content sharing, user does not
need to (and will not) know which protocol is being used behind the scenes.
TIP

TX/CTS to TX/CTS
TX/CTS to CTMS
TC endpoint to CTMS
TX/CTS to TS (TelePresence Server)

SIP

TX/CTS to TC endpoint
TX/CTS to DX
TX/CTS to MCU
TX/CTS to any other video endpoint

Users and Endpoints
Content sharing allows users in a video call to share
additional media in a separate video stream
(presentation, doc camera, etc)
H.323 uses H.239
SIP uses Binary Flow Control Protocol (BFCP)
TIP uses a method called Auto-Collaborate

Content sharing
26
Endpoint Content Resolution
C60/C90 Up to 1080p30/WUXGA
C40 Up to WXGAp30
SX20 Up to 1080p15
EX90 SVGA (800 x 600) to WUXGA (1920 x 1200)
EX60/MX200/MX300 SVGA (800 x 600) to 1080p (1920 x 1080)
CTS 500-32
TX 1310
TX 9x00
Up to 1080p30
*

Up to 1080p30
*

Up to 1080p30
*
All other CTS endpoints XGA (1024 x 768)
Benefit of separate media channel for content
allows users to customize their experience
In case of content channel failure, fallback is
Composite or Switched video
Composite Switched
Requires TX6 software on endpoint
*
Users and Endpoints
Annotation
27
TX6 release adds support for annotation
Supported on CTS500-32, TX13x0, and TX 9xx0
Supported in TIP and standards based SIP calls
Endpoints that support Annotation can take a snapshot of what is
currently being shared, and annotate on it
Any system in a TelePresence conference that can view a
presentation can view the annotated presentation
Users cannot save their annotated presentation after the call is finished
Free Cisco Jabber Video is open to the public, in all markets
Users can download Cisco Jabber Video and make HD video calls instantly
Certain features of Jabber Video are absent in the free client, these include:
- Presence - Company domain addressing
- Policy controls - Integrated directories/phonebooks
- MCU multipoint - Provisioning

Users and Endpoints
Free Jabber
28
28
www.ciscojabbervideo.com
29
CDP is a data-link layer (layer 2) protocol and runs on all Cisco-
manufactured equipment that includes: routers, bridges, access servers,
switches, and endpoints.
A Cisco device enabled with CDP sends out periodic interface updates to
a multicast address in order to make itself known to neighbors.
CDP allows two systems to learn about each other, even if they use
different network layer protocols.
CDP is used by endpoint to discover its assigned VLAN

Cisco Discovery Protocol (CDP)
CDP Support (min version)
CTS/TX Endpoints 1.0
EX/MX/SX/Profile Endpoints TC5
E20 TE4.2
Network Services
CDP
Discover VLAN
DHCP (UDP ports 67,68)
Option 150 (CUCM Address)
Option 242 (TMS address)
NTP (UDP port 123)
DNS (UDP port 53)
HTTP (TCP ports 80, 443, 8080, 6970)
Obtain configuration and firmware
Additional Services and Ports Used
31
Voice/Video Services
SIP
UDP port 5060
TCP ports 5060, 5061
RTP
UDP ports 16384 - 32768
Video Bandwidth Requirements
Environmental Factors that affect bandwidth:
CTS/TX Endpoints
TC Endpoints
Lighting Motion Color / Patterns
Endpoint Settings
Quality Setting / Optimal Definition
Profile / Call Rate
Things to consider:
Is network protocol overhead included in quoted bandwidth requirements?
This usually adds ~20 percent to total bandwidth

Is the quoted bandwidth requirement the average or maximum bit rate?
Average rates can be used unless video is being deployed on an overlay network, in which case the
maximum values may be necessary to use

Video Bandwidth Requirements

33
References:
Cisco Jabber for Windows:
http://www.cisco.com/en/US/docs/voice_ip_comm/jabber/Windows/9_2/JABW_BK_C9731738_00_jabber-windows-install-config_chapter_010.html#JABW_RF_B03374D0_00

Cisco TX series:
http://www.cisco.com/en/US/docs/telepresence/tx_sw/6_0/admin/guide/tx_sw_features.html#wp1060124

TC Endpoints, look for Optimal Definition in admin guides:
http://www.cisco.com/en/US/docs/telepresence/endpoint/ex-series/tc6/administration_guide/ex-series-administrator-guide-tc63.pdf
How to Preserve User Experience in Non-Ideal Networks?
34
Si Si Si Si Si Si
Si Si Si Si Si Si
Old/ QoS-unaware
Network Devices
Small packet buffers
Loss Bursts
Repair scheme
worsens things
Link Failures
Sudden decrease
of bandwidth
Bad Links
Continuous packet
loss (<5%)
Low-speed Links
Serialization delay
affects frame jitter
Long-Term Reference Frames
Repair-P Frames
Dynamic Rate Adjustment
Encoder Shaping
Gradual Decoder Refresh
Repair-P Frames
Forward Error Correction
Media resiliency Gradual Decoder Refresh (GDR)
Serialization delay on low-speed links can cause large I-frames to arrive too late and be
discarded
Solution: Gradual Decoder Refresh (GDR) distributes intra picture data over N frames
GDR frames contain a portion of intra macroblocks and a portion of predicted macroblocks
Once all N frames have been received, decoder has fully refreshed the picture
Encoder
Decoder
Predicted portion
Intra-macroblock portion
Media resiliency typical packet loss scenario
Loss of a P-frame triggers request for a new I-frame
Encoding and transmitting large I-frame takes time
If any of the I-frame packets get lost, restart the process
Flickering/pulsing of video when new I-frame arrives
Video freeze or artifacts when multiple packets are lost
...
?
P1
I1
P2
P3
P4 P5
P3
Out of Sync (OOS)
P1 P2 P4 I1 I1 I1 P5
...
...
P1
I1
P2 P4 P5
...
Encoder Decoder
Media resiliency Long Term Reference Frames and Repair-P Frames (LTRF/LTRP)
Keep encoder and decoder in sync with active feedback messages
Encoder instructs decoder to store raw frames at specific sync points as Long-Term
Reference Frames (part of H.264 standard)
Decoder uses back channel (i.e. RTCP) to acknowledge LTRFs
When a frame is lost, encoder creates Repair-P differential frame based on last
synchronized LTRF
...
?
P1
LTRF1
P2
P3
P4
P5
P3 P1 P2 P4 P5
...
...
P1
LTRF1
P2 P4
...
Encoder Decoder
P5
ACK LTRF1
Long-Term Reference Frame
(not actually sent on the wire)
Repair-P Frame
Built from last synced LTRF
OOS (P4)
Media resiliency - Forward Error Correction (FEC)
38
Defined in RFC 5109, allows decoder to recover from limited amount of packet loss (up to
~5%) without losing synchronization
Can be applied at different levels (1 FEC packet every N data packets) to protect important
frames in lossy environments
Trade-off is bandwidth increase
R2
...
LTRF
Repair-P
...
Encoder
Decoder
011101000
110000110
010001100
111001010
110110100
101010010
100100010
000110010
111011110
Binary XOR R1 FEC
Binary
XOR
FEC
R1
R2
Media resiliency summary
39
Combining all these techniques has been shown to preserve acceptable
user experience even in high packet loss situations (up to 10-15%)
Many of these mechanisms are currently implemented in Cisco
TelePresence endpoints:
CTS/TX Series EX/MX/SX/C Series
Encoder shaping 1.2 TC 4.0
GDR 1.6 TC 5.0
LTRF and Repair-P 1.6 TC 4.0
FEC TC 4.0
Dynamic Rate Adjustment 1.7 TC 4.0
Introduction
Pillars of Cisco solution, Terminology, Use Cases
Users and Endpoints
User needs and expectations, Endpoint Differentiators, New Endpoints and Software Releases
CDP, Bandwidth Requirements, Media Resiliency
Call Control
Unified CM, How VCS fits, Expressway, Dial Plan
Conferencing
Types of Conferences, TelePresence Server, MCU, Conductor
TMS 14,TMS Extensions, Interaction with Infrastructure and Endpoints, WebEx Enabled TelePresence
(WeT)
Q&A, Roadmap

Agenda
40
Call Control
41
Call Control
Cisco CUCM and Cisco VCS
42
Cisco CUCM
Software-based call processing system built on Linux
Started as a video PBX in 1997
Supports 30,000 endpoints in a cluster
Runs on Cisco UCS servers
Uses a variety of voice and video protocols including
SCCP, SIP, H.323, and MGCP
Cisco VCS
Designed initially for video deployments
Two types:
VCS Control
VCS Expressway
Supports 2500 registrations on single VCS,
10,000 in a cluster
Call Control
Cisco Unified Communications Solution
43
IP Telephony
(PSTN Gateways, IP phones, Toll Bypass,
Voice BRI/PRI/T3/FXO/FXS, Provisioning)
Unified Messaging
(Unity Voicemail, Jabber Chat, Speech Connect,
Voice IVR, Email integration, Click to Call)
Contact Center
(Enterprise/Express, Agent Presence, Routing
Logic)
Mobility
(Single Number Reach, Barge, Shared Lines)
TelePresence
(Provisioning/managing of CTS, E, SX, EX, MX,
TX and C series endpoints)
Business to Business
(Expressway Traversal)
CUCM
Additional Video Services
(H.323 to SIP, 3
rd
party video, IPv4 to IPv6,
Jabber Video)
VCS-C VCS-E
Unity CUPS
Contact
Center
CUCM
VCS
Internet
PSTN
Remote Registrations
(Without VPN)
Call Control
Reasons for a VCS only deployment
H.323 endpoints
Existing voice PBX in place (non-Cisco)
Video only deployment
Mostly room based systems
TMS needed for provisioning

VCS only environment
44
CUCM
VCS-C VCS-E
Vision Recommendation Most functionality
VCS-C VCS-E
VCS Only Deployment
Fully Supported
DMZ Enterprise Network
1. VCS-E is the traversal server installed in DMZ. VCS-C is the traversal client installed inside the enterprise network.
2. VCS-C initiates traversal connections outbound through the firewall to specific ports on VCS-E with secure login
credentials.
3. Once the connection has been established, VCS-C sends keep-alive packets to VCS-E to maintain the connection
4. When VCS-E receives an incoming call, it issues an incoming call request to VCS-C.
5. VCS-C then routes the call to CUCM to reach the called user or endpoint
6. The call is established and media traverses the firewall securely over an existing traversal connection

CUCM
Firewall VCS-E Firewall VCS-C
Outside Network
Media
Signaling
How VCS Traversal Works
Internet
Call Control
Problem:
Remote CUCM endpoints require VPN connection to register
Mobile clients rely on additional app (AnyConnect)
VPN isn't always needed (or possible)

Solution:
Evolve VCS software to allow CUCM endpoints to take advantage of traversal
technology
Evolution of traversal technology with Unified CM
46
Call Control
A New Feature and a New Product
47
Available Now
New Feature: Mobile and Remote Access
Connect remotely with Jabber and TC endpoints
Register directly to UCM 9.1.2 (or higher)
Voice, Video, IM&P, Directory, Visual Voicemail outside the
network without a VPN

New Product: Cisco Expressway C and Expressway E
Based on same OS as VCS-C and VCS-E
Same GUI, SIP Stack as VCS-C and VCS-E
Supported with limited scale on existing VCS appliance via
upgrade and new option key

Call Control
Cisco VCS Compared to Cisco Expressway
48
Feature Comparison
Cisco VCS Family
(VCS-C/VCS-E)
NEW - Cisco
Expressway Series
(Expr-C/Expr-E)
Mobile and Remote Access Y Y
Video / TelePresence Device Registration & Provisioning Y N
Video Session Management & Call Control Y N
Video Interworking (IPv4 to IPv6, H.323-SIP, Microsoft
Interop, Standards-based 3rd Party Video endpoints)
Y
1
Y
Business to Business Video Y Y
Jabber Guest Y Y
WebEx Enabled TelePresence Y N
2
Enhanced Security Y N
1
VCS required for Intra-domain Federation (FindMe)
2
Expressway-C cannot have TS or MCU registered to it
Feature Comparison
Cisco VCS Family
(VCS-C/VCS-E)
NEW - Cisco
Expressway Series
(Expr-C/Expr-E)
Mobile and Remote Access Y Y
Video / TelePresence Device Registration & Provisioning Y N
Video Session Management & Call Control Y N
Video Interworking (IPv4 to IPv6, H.323-SIP, Microsoft
Interop, Standards-based 3rd Party Video endpoints)
Y
1
Y
Business to Business Video Y Y
Jabber Guest Y Y
WebEx Enabled TelePresence Y N
2
Enhanced Security Y N
Call Control
Both VCS and Expressway run x8.1 software
49
Solution designed for and sold exclusively
with UCM 9.x and above
Subset of X8.1 features
No additional cost for server software license
for CUCM 9.1+ customers

New
Offering
X8.1
Expressway-C
Or Core
Expressway-E
Or Edge
VCS-Control
No Change
VCS-Expressway
No Change
Cisco VCS
Cisco Expressway
Specialized video applications for video-only
customer base (GK, SIP Proxy, interworking,
traversal)
Superset of X8.1 features
No changes to existing licensing model
Call Control
Expressway Series
50
Call Control
Cisco Expressway Licensing
No Additional Cost for Virtual Edition
Fixed and Mobile Users at no additional cost
Mobile and Fixed Endpoint registration
IM & Presence
Video and Audio Media Sessions
No Cost with UCM 9.x
Business to Business Concurrent Sessions
Business to Business Video and Audio
Media Sessions
Expressway Rich Media Session $750 a
la carte
CUCM
Firewall
Expressway-E
Firewall
Expressway-C
Similar to
Traversal Calls
Internet
Expressway
Firewall Traversal
AnyConnect
VPN
Layer 3 VPN Solution
Secures the entire device and its
contents
AnyConnect allows users access
to any permitted applications &
data
New Offering
Session-based firewall traversal
Allows access to collaboration
applications ONLY
Personal data not routed
through enterprise network
Call Control
Cisco Jabber Remote Access Options
Unified CM &
applications
Unified CM &
applications
Call Control
Versions Required:
Cisco Expressway X8.1
Cisco Unified CM 9.1.2
Cisco TelePresence TC 7.0
(7.1 recommended)
Jabber depends on platform

No support for Cisco Unified CM 8.6
ICE (STUN/TURN) support not included in
Cisco Unified CM 10.0, on roadmap for 10.5
Expressway solution version requirements
The X8.1 release delivers three key
capabilities enabling the Expressway
Mobile and Remote Access Feature
XCP Router for XMPP traffic
HTTPS Reverse proxy
Proxy SIP registrations to UCM
Call Control
What can a Jabber client do with Expressway?

Make voice and
video calls
Instant Message
and Presence
Access visual
voicemail
Search corporate
directory
Launch a web
conference
Share
content
Inside firewall
(Intranet)
Outside firewall
(Public Internet)
DMZ
Expressway
E
Expressway
C
Unified CM
Internet
Protocol Security Service
SIP TLS Session Establishment
Register, Invite, etc. via UCM
Media SRTP Audio, Video, Content Share,
Advanced Control
(RTP/SRTP, BFCP, iX/XCCP)
HTTPS TLS Logon,
Provisioning/Configuration,
Contact Search, Visual
Voicemail
XMPP TLS Instant Messaging, Presence
Call Control
Expressway protocol workload summary
Inside firewall
(Intranet)
Outside firewall
(Public Internet)
DMZ
Expressway
E
Expressway
C
Unified CM
Internet
Unified CM IM&P
Conference Resources
Other UC Infrastructure & Resources
Call Control
Expressway Hybrid Deployment - Cloud based IM&P
webex
Messenger
Protocol Security Service
SIP TLS Session Establishment
Register, Invite, etc. via UCM
Media SRTP Audio, Video, Content Share,
Advanced Control
(RTP/SRTP, BFCP, iX/XCCP)
HTTPS TLS Logon,
Provisioning/Configuration,
Contact Search, Visual
Voicemail
XMPP TLS Instant Messaging, Presence Conference Resources
Other UC Infrastructure & Resources
Inside firewall
(Intranet)
Outside firewall
(Public Internet)
DMZ
Expressway
E
Expressway
C
Unified CM
Internet
Unified CM IM&P
Call Control
Starting with CUCM 9.0 endpoints can have an alphanumeric URI alias associated with their Directory
Number
Dialing either the URI or the DN will route call to endpoint
URIs can be associated with SIP or SCCP endpoints
The endpoint itself has no notion of their associated URI, they still register with DN
User portion (left-hand side) of URI is case sensitive, host portion is case insensitive
Endpoints can have up to 5 URI aliass associated with their DN
One URI is considered the primary URI. This will be used for calling party id
Each URI can be in a separate partition
CUCM release 9.0 URI support

57
EX90
DN: 5551234
Primary URI: bob@cucm.cisco.com
URI: bob.home@cucm.cisco.com

SIP
EX90 dials
alice@cucm.cisco.com
CUCM blends
Bobs DN and
URI for caller ID
9971
9971 sees call
coming from
bob@cucm.cisco.com
and 5551234
DN: 5559876
Primary URI: alice@cucm.cisco.com
Can be
changed in
CUCM 9.1
Call Control
H.265 (HEVC) pass-through by CUCM
H.264 SVC pass-through by CUCM
SIP Trunk status can be monitored in RTMT
Flexible DSCP and Video Promotion
Allows better QoS treatment of media when desktop video endpoint is in call with
immersive video endpoint.
Self-provisioning by end users
Video Enhancements in CUCM 10.0
58
Conferencing
59
Conferencing
Many, many options
CUCM
VCS
Call control
Conductor
TMS
Additional
applications
Endpoint
characteristics and
capabilities
CTMS
MCU
Telepresence Server
MSE
8000
Multipoint
platforms
PVDMs
Conferencing
Ad hoc Conference
Impromptu meetings, they are not scheduled beforehand ,nor require an administrator to initiate them. Suitable for
smaller, on-the-fly, meetings. A point-to-point call escalated to a multipoint call is considered ad hoc.
Rendezvous Conference
Also called meet-me/permanent/static conferences, requires endpoints to dial in to a pre-determined number. Often
used for recurring meetings which involve different endpoints each time.
Scheduled Conference
Provides a guarantee that endpoints and multipoint resources will be available at a certain time. Endpoints join
manually or are automatically connected by the multipoint resource.
Types of conferences
61
TelePresence
Server (TS)
Ad Hoc
Rendezvous
Scheduled
Cisco
TelePresence Multipoint
Switch (CTMS)
Cisco Multipoint
Control Unit (MCU)
Ad Hoc
Rendezvous
Scheduled
Ad Hoc
Rendezvous
Scheduled
Embedded
Conferencing
(Multisite)
Ad Hoc
Rendezvous
Scheduled
Conferencing
Embedded conferencing - Multisite
62
Endpoints capable of Multisite:
C40
C60
C90
CUCM Endpoint Configuration
EX90
SX20
MX300 G2
Part Numbers:
LIC-P65-C90-MS
LIC-P55DC60-MS
LIC-EX90-MS
LIC-INTP-C90-MS
TC based Endpoint Configuration
Conferencing
One platform for all video conferencing
63
PVDM3
No content channel
No encryption
Max 4CIF resolution on transcoded video
Limited codec support
No support for H.263
MCU
H.323 and SIP support
Auto Attendant
Basic cascading
No TIP support
No optimized conferencing
Legacy API

CTMS
Only supports TIP endpoints (and 9971)
No transcoding all endpoints must negotiate same
resolution
No layouts, full screen active speaker only
EoS (Jan 2014)

TelePresence Server
Support for wide range of codecs
Optimized conferencing
ActiveControl support
Multiple layouts and PIN support
Available in hardware and VMWare
Supports multiscreen and single screen endpoints
Uses new Flex API for advanced features

Conferencing
Supports H.323, SIP, and TIP
Recent software upgrades has increased per blade port count
Can be trunked to CUCM, registered to VCS, or managed by Conductor
Features Active Presence
Supports TIP in release 2.1 and later
1080p30 and 720p60 support in 2.2
Supports 3rd party multiscreen solutions
Flagship Cisco multipoint solution

64
Conferencing
TelePresence Server is the only multipoint platform that supports
both Cisco and non-Cisco multiscreen systems
TelePresence Server is the only multipoint platform that supports
H.323, SIP, and TIP (no option keys necessary)
TelePresence Server protocol support
65
Version
1.0
H.323
H.239
2.1
H.323
H.239
FECC
SIP
BFCP
RTCP
TIPv6
2.2
H.323
H.239
FECC
SIP
BFCP
RTCP
TIPv6
TIPv7
3.0
H.323
H.239
FECC
DTMF
SIP
BFCP
RTCP
TIPv6
TIPv7
1.2
H.323
H.239
FECC
(for layout
control)
3.1
H.323
H.239
FECC
DTMF
SIP
BFCP
RTCP
TIPv6
TIPv7
ActiveControl
Cisco Clearpath
Conferencing
66
TelePresence Server Platform Form Factors
TelePresence Server
on VMware
Appliances Blade
7010
8 to 97 ports at 360p30
8710
310
320
8-core/16vCPU
10-core/20vCPU
Note: For simplicity, only capacity for 360p30 and 1080p30 are shown. TS is capable of many other resolutions and frame rates with differing limits on capacity.
All numbers represent remotely managed mode (Conductor required) capability. See release notes for further detail.
Conferencing
TelePresence Server Experience
67
Single screen experience in
release 2.3 and later
Single
ActivePresence
Prominent
Equal
Multiscreen experience
Version
2.2

Version
2.3

Version
1.0 2.1

Version
3.0

16
Conferencing
TelePresence Server (7010 and 8710) licensing and capacity changes
68
Up until TS 2.2, max of 16 screen licenses could be utilized on a single 7010 or 8710 blade
Release 2.3 made the following changes:
Max number of useable licenses was decreased from 16 to 12
The port count for 720p30 calls was increased from 16 ports to 24 ports
These enhancements effectively gave existing customers 8 additional HD ports at no cost
For existing 8710 customers who had a fully licensed 16 port TS, the now unnecessary 4
licenses could be used for future expansion on new 8710s
16
Optional
optimization of
resources
discussed later
OR
or or
12
24
12 or
24
12
Full HD= 1080p30
/ 720p60
HD = 720p30
Conferencing
TelePresence Server Deployment
69
TS
Conductor
Ad Hoc
TS
H.323 HTTP(s) SIP
Rendezvous
VCS
CUCM
VCS
CUCM
Scheduled
Conferencing
Several models:
8510 and 8420 blade
Standalone 5300 series
Standalone 4500 series
Standalone 4200 series (EoS)
Depending on model MCU can run in nHD, SD, HD, HD+, or Full
HD mode
Support H.323, SIP, H.239, BFCP, FECC, DTMF
Supports resolutions from QCIF up to 1080p in 4:3 and 16:9 ratios
Over 50 different layout options
MCU
70
Port Mode Quality
nHD 360p30
SD W448p30
HD 720p30 / w448p60
HD+ 1080p30 (asymmetric)
Full HD 1080p30 / 720p60
Conferencing
All Cisco video endpoints are supported on both
TelePresence server and MCU
CTS/TX with MCU
71
MCU
CTS 1100
TX 9000
CUCM
CTS 500-32
VCS
CTS 500-37 called into 4501 MCU
CTS endpoints are supported on MCU series starting with 1.7.4
In any deployment with CTS 3xx0 or TX 9xx0 triple screen systems,
TelePresence Server is still the recommended multipoint solution
MCU
CUCM added ad hoc conference bridge support for 4200, 4500, 8420, 8510,
5310 and 5320 MCUs in version 8.6
CUCM version 8.6.2 added support for encrypted calls to MCU
MCU version 4.2 or later is required to be added as a CUCM conference bridge
Ad hoc CUCM conference bridge
72
CUCM
MCU
SIP
HTTP(s)
MCU API Used by CUCM

Create Conference
Modify Conference
Destroy Conference
Device Query (keepalive)
(trunk created
behind the scenes)
Conferencing
MCU - Deployment
73
VCS
CUCM
MCU
VCS
CUCM
Ad Hoc
Rendezvous
MCU
Scheduled
H.323
HTTP(s)
SIP
Conductor
Requires Port License Conversion (PLC) key
PLC key - $0 item
L-MCU5300-UPG-PAK then select L-300-PLC
1 Full HD port = 1 TS Screen License
Requires Conductor

Requires TSMO key on Supervisor
TSMO key - $0 item
L-8000-CHLIC-PAK then select L-8000-TMSO
5 SD ports = 1 TS Screen License
Conferencing
Same hardware, only software and licensing is changed
MCU migration to TelePresence Server
74
5310
5320
8510
310
320
8710
Cisco MCU
Requires Port License Conversion (PLC) key
PLC key - $0 item
L-MCU5300-UPG-PAK then select L-300-PLC
1 Full HD port = 1 TS Screen License
Requires Conductor

Requires TSMO key on Supervisor
TSMO key - $0 item
L-8000-CHLIC-PAK then select L-8000-TMSO
5 SD ports = 1 TS Screen License
5310
5320
8510
310
320
8710
Cisco MCU
Conferencing
Cisco TelePresence Conductor
75
Manages TelePresence Server (vTS, 310, 320, 7010, 8710) and MCU (42xx, 45xx, 53xx,
8420 & 8510) conference resources
Supports ad hoc and rendezvous conferences
Dialled conference aliases are agnostic of the MCU or TS that the conference is hosted on
Resilient solution providing service continuity if a power failure affects a CUCM/VCS/MCU/
TelePresence Conductor
Whole process is transparent to the end user

CUCM or VCS
Conductor
Full
Cascaded
Meeting
Example:
Shipping since Nov 2011
Conferencing Design
Conductor XC 1.0 Conductor release
Conductor acted as policy service to VCS
MCU/TS registered to VCS
Conductor instructed VCS to route calls to MCU/TS
Conductor XC 2.0 introduced Conductor as a
B2BUA
MCU/TS SIP trunk directly to Conductor (not VCS)
H.323 calls are interworked via VCS
Both deployment methods fully supported (CUCM
deployment still recommended choice though)
Conferencing with VCS as call control
76
CPL H.323 HTTPs SIP
VCS
Conductor
VCS
Conductor
Conductor
Conductor acts as SIP B2BUA
Supported with XC 2.0 and
Unified CM 8.6.2 and later
Future development focused on
this deployment
Cisco VCS still fully supported
and integrated via SIP trunk to
CUCM

Integration with call control
77
CUCM Conductor
VCS
CPL H.323 HTTPs SIP
Conferencing
Conductor
78
Support for TelePresence Server
Support for direct integration with CUCM
SIP B2BUA puts Conductor in the signaling path
Why add another box?
Improvements to logging
Limited TMS scheduling support
Allows CUCM multipoint resources
to be shared for both ad hoc and
rendezvous conferences
Advanced features like
optimized resources on the
TS are possible
Central point of
management for all
conferencing needs
Shared
multipoint
resources
Conferencing
Example of optimization of resources
79
Conductor 2.0
Without
Conductor
Full HD
(1080p30)
HD
(720p30)
SD
(480p30)
With
Conductor
TelePresence Server 3.0
Once full, additional
endpoints cannot join
12
20
No PR
Key
No PR
Key
No PR
Key
Conferencing
Conductor deployment

80
CUCM
Conductor
VCS-C
Conductor added as a
conference bridge in CUCM
SIP Trunk(s) configured in CUCM to Conductor
Ad hoc calls by CUCM
registered endpoints use
conductor to find a
multipoint resource
Endpoints registered to VCS
can still use Multiway to invoke
a Conductor behind CUCM
Pools of MCUs and
TelePresence Servers sit
behind Conductor
Certain users are configured with
custom conference experiences
(specific layouts, resolutions, port limits)
H.323 HTTPs SIP
81
82
Cisco TMS and Cisco CTS-Manager
83
Provisioning and configuration of endpoints
Provides hierarchal directories and phonebooks for
endpoints
Booking and scheduling of endpoints and infrastructure
(conferncing, recording, etc)
Runs on windows server 2003, 2003 R2, 2008 and 2008 R2
Robust APIs available for 3
rd
party applications to schedule and
monitor systems
Available as software (can be run in VMWare)
CTS-Manager
TMS
Linux based application based on same VoiceOS as CUCM
Monitors and schedules Cisco TelePresence CTS, TX, and
TC based endpoints
Integrates with Exchange and Lotus Domino
Available as standalone UCS server and as a VM
Cisco TMS
84
Operating System:
Windows Server 2003 32-bit
Windows Server 2008 32- or 64-bit
Hardware Platform
TMSXE
Cisco TelePresence Management Suite
Extension for Microsoft Exchange
TMS and TMS extensions
85
TMSXE
TMSXN
TMSBA
TMSPE
Windows Server 2008
Windows Server 2008 R2
Integrates TMS with Microsoft
Exchange (2007, 2010) via EWS
TMSXN
Extension for Lotus Notes
Windows Server 2000
Windows Server 2003
Windows Server 2008
Integrates TMS with IBM Lotus
Domino Server 7.0.x, 8.0.x, 8.5.x
TMSBA
Extension Booking API
Optional feature of TMS
Provides a Web Services API that
interfaces with the TMS booking
engine
TMSPE
Provisioning Extension
Windows Server 2003
&
VCS x7.1 or later
Enables provisioning of telepresence
users and endpoints for large-scale
deployments and setting VCS
FindMe options in single user portal
Separate Server than
TMS
Separate Server than
TMS
Option Key on TMS
Replaces older TMS
Agent Legacy. Both are
supported in TMS 13, only
TMSPE supported in 14.1
Dashboard
86
Management of
telepresence
infrastructure
System
Trouble tickets
Conference
Status Indicator
System
Reporting
Directly managed endpoint
TMS is in constant contact with endpoint (HTTP, SNMP)
Devices are shown in TMS Navigator
Can be scheduled (OBTP, Automatic Connect, Manual etc)

Directly managed vs provisioned endpoints
87
2000 Devices
Direct
Managed
5000 Devices
Direct
Managed
TMS 13.2
TMS 14.1
Provisioned endpoint
Requires TMSPE
Supported on Jabber Video, E20, EX, and MX. Endpoints are authenticated against AD or local
TMS database
Cannot be scheduled (at least not with OBTP, address book can be used to have multipoint
meetings call out to any endpoint/user)
Distributes settings and phone books to users through Cisco VCS
TMS support for TX/CTS endpoints
88
TMS release 13.1 and later supports scheduling
CTS/TX endpoints
CUCM 8.5 or later is required. TMS will log into CUCM
(as an application user) and return all registered CTS
systems in CUCM
CTS 1.7.0 or later is required for TMS management
When a CTS system is added to TMS,
TMS can provide :
OBTP
Schedule P2P calls
Read system information
Monitor response status and call
status
Dialing from the endpoint
Enable Cisco CTS Native Interop setting added in TMS 13.2

Prior to 13.2:
CTS/TX endpoints could only be scheduled on TS
CTS/TX could not be scheduled for point to point calls to non-TIP devices
TMS support for TX/CTS endpoints

89
This setting is removed in TMS version 14.2. In this version
and later this setting is effectively set to Yes permanently.
Automatic connect: Cisco TMS will automatically connect all the participants
at the specified time and date.
One Button to Push: Conference dial-in information will be automatically
presented on endpoints that support One Button to Push.
Manual connect: At the specified time and date, the system listed as the VC-
Master will be prompted to begin the call. The call will automatically be
connected when the VC-Master initiates the call.
No connect: This option will reserve the room(s) and generate the call route,
but not connect the route. The conference can be started by clicking Connect
for the participants in Conference Control Center.
Reservation: This option will reserve the room(s) and will not initiate any
connections.
TMS call launch options
90
Automatic
Connect
One Button to
Push
Manual Connect No Connect Reservation
OBTP is available on the Cisco Touch 12, Touch 8, 797x IP phones and on-
screen display (OSD) with remote control
SX/EX/MX/C series on TC5 or later can use OBTP
Starting with TMS 13.2, SX/EX/MX/C series endpoints registered to CUCM can
still be scheduled via TMS

TMS One Button to Push
91
TC5 or later
TC5
CTS 1.7.0 or later
CTS 1.8 or later
User schedules
meeting
Reads event in
mailbox using EWS
Pushes content to
codec/endpoint
Codec/endpoint
pushes meeting
info to user
interface

Send meeting confirmation to user
Sends meeting
details to
multipoint device
Booking request
passed via WS to TMS
Booking API (TMSBA)
User
Interface
TMS
Exchange User
Codec/
Endpoint
Multipoint
Resource
User now has
OBTP access to
meeting
TMS calendaring integration with OBTP
92
TMS/TMSXE: 13.1.2 / 3.0 and later
TMSXE
Introducing Smart Scheduler
93
TMS 14.2 and later
TMSPE 1.1 and later
Conferencing Deployment
94
SIP HTTPs
Unified CM
VCS-C VCS-E
Conductor
TMS
TS TS TS
Internet
Scheduled Video
Conferences
SCCP PSTN
Ad hoc and
Rendezvous Video
Conferences
WebEx Enabled
TelePresence
WebEx Enabled TelePresence (WeT)
95
TelePresence and WebEx Working Together
Live, face-to-face communication
experience over the network
Share content
Personal, desktop, multipurpose,
integrated, and immersive
endpoints

Cisco TelePresence
Cisco WebEx
Meet anytime, anywhere, in real time
Deliver presentations, show
documents, and demonstrate
applications
Pass meeting control or control a
remote desktop

Cisco WebEx Enabled TelePresence
Solution overview
Unified CM
WebEx Client
OBTP
Audio, Video, and
Presentation over SIP
Scheduling in Outlook with WebEx PT, WebEx mailbox
or via TMS Smart Scheduler or Admin booking
VCS-C VCS-E
TS / MCU
TMSXE
H.323
Endpoints
TMS
Other Video
Endpoints
CTS / TX
EX, MX,
SX, C series
SIP
Media H.323
SIP TLS

Product Product version Recommended Versions
WebEx Meeting Center WBS29
TMS
TMSXE
TMS
TMSXE
TMS 14.3.2
TMSXE 3.1.2
VCS VCS-C, VCS-E X8.1
TelePresence MCU 8510, 8420*, 5300 series, 4500
series, 4501, & 4200 series*
4.4
TelePresence Server ** 8710, 7010 3.1
TelePresence Endpoints Any supported by MCU or TS All
CUCM CUCM 9.1.2 or higher
WebEx Outlook Plug-in PT WebEx Outlook Plug-in PT WBS29
Supported Product Versions
* EOS products
** MP 310/320, vTS and Conductor not supported today
In Meeting User Experience
With content sharing
Call to Action
Visit the World of Solutions:-
Cisco Campus
Walk-in Labs
Technical Solutions Clinics

Meet the Engineer

Lunch Time Table Topics, held in the main Catering Hall

Recommended Reading: For reading material and further resources for this
session, please visit www.pearson-books.com/CLMilan2014

100
Complete your online session
evaluation
Complete four session evaluations
and the overall conference evaluation
to receive your Cisco Live T-shirt
Complete Your Online Session Evaluation
101
102

Brkevt 2800

Enviado por

Dados do documento

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Brkevt 2800

Enviado por

Direitos autorais:

Formatos disponíveis

Overview of Cisco TelePresence

Solution and Deployments

Você também pode gostar