brkevt 2800 telepresence overview

© 2013 Cisco and/or its affiliates. All rights reserved. BRKEVT-2800 Cisco Public

Overview of Cisco TelePresence

Solution and Deployments Michael Thomma

Technical Marketing Engineer

[email protected]

BRKEVT-2800


Housekeeping

3

Overview of Cisco TelePresence Solution and Deployments

This session provides an overview for all components of a TelePresence

deployment. Subsequent breakout sessions will cover specific components

of the TelePresence solution in depth.

This session will walk the audience through a case study of deploying

TelePresence in a new enterprise. Endpoints, call control, multipoint, and

management design decisions will be explained. Problems and challenges

will be highlighted with solutions and reference architectures that are

recommended.

This breakout will cover the following Cisco products: voice and video

endpoints, Unified CM, VCS, TelePresence Server, MCU, TMS and Webex

integration for TelePresence.

Goal for this session:

• Learn how to deploy a unified solution which includes voice and video endpoints,

conferencing, and scheduling. Understand the decisions made based on how the technology

works.

• Learn how a enterprise can be deployed in such a way that future expansion (both

geographically and in number of users) can be accommodated.

• Design a dialplan which preserves user simplicity and integrates with all endpoints and

external infrastructure (PSTN).

4.4 Released April 4th, 2012 CTS 1.8


TelePresence/Video Sessions

4

BRKEVT-2801 Integrating Voice and Video Call Routing and Dial Plans Wednesday 14:00

BRKEVT-2400 Scheduling Best Practices for Cisco Telepresence Friday 11:30

BRKEVT-2319 Business to Business Video Thursday 9:00

BRKEVT-2317 Video Content: Unlock the Power of Video with "Capture, Transform, Share" Solution Friday 9:00

BRKEVT-2800 Overview of Cisco TelePresence Solution and Deployments Tuesday 16:15

BRKEVT-2803 Designing and Deploying Multipoint Conferencing for Telepresence Video Thursday 14:00

BRKEVT-2805 Understanding and Troubleshooting EX-Series Personal Telepresence Systems and C-Series Codecs Wednesday 16:30

COCEVT-2577 Inside Cisco IT: The Do’s, Don’ts and Lessons Learned during Five Years of Video Deployment Thursday 11:30

LTREVT-2300 Enterprise Medianet: Video Applications and Network Design Lab Wednesday 9:00

BRKARC-1006 Planning, Building & Deploying Cisco's Remote Expert Solution Tuesday 11:15

BRKEVT-2802 Deploying TelePresence and Video Endpoints on Unified Communications Manager Tuesday 14:15

BRKEVT-2804 Monitoring and Troubleshooting Network Impairments in Video Deployments Tuesday 14:15

TECEVT-2674 Conferencing and Scheduling Design for Cisco Telepresence Monday 14:15


TelePresence Architecture Overview

Campus

Branch

Conferencing Call Control

Endpoints

Scheduling

And

Management

Monitoring Recording

and

Streaming

Endpoints Conferencing

WAN

Internet

Global

B2B Inter-

Network

External Connections

Mobile Office


Agenda

6

Introduction

‒ Pillars of Cisco solution, Terminology, Use Cases

Users and Endpoints

‒ User needs and expectations, endpoint differentiators, recent releases

Deploying on the Network

‒ CDP, QoS, Bandwidth Requirements, Media Resiliency

Call Control

‒ Unified CM, How VCS fits, dial plan

Conferencing

‒ Types of conferences, TS, MCU, CTMS, Conductor

Scheduling and Management

‒ TMS 14.1,TMS extensions, interaction with infrastructure and endpoints

Q&A, Roadmap

10 min

20 min

15 min

20 min

25 min

15 min

15 min


I understand

7

2 00 00 59 59 58 57 56 55 54 53 52 51 50 49 48 47 1 46 45 44 43 42 41 40 Hours Minutes

39 38 37 36 35 34 33 32 31 30 Seconds

Introduction


Introduction

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

Expanding TelePresence to a Pervasive Video Solution

9

Web

Collaboration

Desktop Video

Pervasive Video

Soft Clients Multipurpose

Video

Fully Immersive


• 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

10


Introduction

Terminology - ActivePresence and OBTP (One Button to Push)

11

User schedules TelePresence

rooms in Outlook User receives confirmation

email

Participants enter their

TelePresence Rooms One button press

to launch call

As more endpoints join it becomes harder

to maintain an immersive experience

Issue How do you maintain an immersive experience in

a multipoint meeting with many endpoints

Answer ActivePresence: Preserve ability to see multiple endpoints, but show active speaker full-screen to maintain focus

OBTP


Introduction Terminology for presentation

12

EX90

Profile 65 Profile 55

EX60 MX200/300

Profile 42

1100

13x0-65

500-32

3xx0

CTS/TX endpoints SX/EX/MX/C series based endpoints (all run TC software)

C20 C40

C60 C90

SX20

9xx0

© 2013 Cisco and/or its affiliates. All rights reserved. BRKEVT-2800 Cisco Public 13

Introduction

Use Case 1

Campus

Multipoint

Call Control

The Challenge 500 users, single site

IP PBX already in place for audio needs

Several existing non-Cisco video endpoints

Video enable employees for internal communication

The Solution Single screen personal and multipurpose endpoints

Single multipoint platform for internal conferencing

The following three use cases will be referenced throughout the

presentation. These use cases will demonstrate deployment

decisions in three different customer environments.

3rd party PBX

• Cisco is committed to giving customers options to fit their individual needs.

• Unlikely everyone in this room will deploy everything we cover in this 2 hour presentation EXACTLY as shown.

• Take what is relevant to your customers, your deployment, from this presentation and build upon that to fit your specific needs.


Introduction

Use Case 2

Campus

Multipoint

Call Control

The Challenge 750 users, single site

No pre-existing video or audio deployment

No remote workers

Video enable employees for internal communication

Voicemail required

Instant messaging client needed for workers

The Solution Desktop TelePresence endpoints for Managers, video

enabled IP phones and soft clients for employees

Multipurpose TelePresence installed in existing

conference rooms

Multipoint for rendezvous and ad hoc conferencing only

Optional B2B capcabilities

Voicemail Presence


Introduction

Use Case 3

Campus

Multipoint

Call Control

The Challenge 20,000 Users

Remote workers on video

Immersive experience required

Redundancy with scale

The Solution Single screen and immersive SIP endpoints

Video enabled IP phones for employees

Multipurpose TelePresence installed in existing

conference rooms

Chassis based conferencing solution with localized

resources in branch offices

Voicemail

WAN

Internet

Presence

Branch

Teleworker

Conferencing Management Scheduling

Multipoint

Users and Endpoints


Users and Endpoints

Determining 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?


User and Endpoints

Cisco User Experience

18

Cisco Touch 8

Cisco Jabber Video

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 iPad


Users and Endpoints

Comparison of Cisco video capable endpoints

Jabber 99xx EX Series MX Series Profiles TX 1310 TX 9x00

Capacity

Content

Sharing

Resolution

Remote

Registration

External

Content 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 448p

With VPN

connection

Audio only

EX90 only

Up to 1080p30 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


Endpoints

Introducing the TX9000 series

What we’ve 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 Desktop EX60, EX90

C Integrator C20, C40, C60, C90

What we’ve 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, 8.6, 9.0, and 9.1


Users and Endpoints

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

SIP and TIP

21

H.323 SIP 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

• CTS/TX endpoints support SIP for call setup and media negotiation starting

in release 1.7.4 and later

‒ 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

• EX, MX, SX, and all C series 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)

Standards Support

22

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

http://www.cisco.com/en/US/docs/telepresence/interop/endpoint_interop.html


Endpoints

When will a Cisco endpoint use TIP?

23

TX/CTS to CTMS TIP

TX/CTS to TX/CTS TIP

TX/CTS to TS TIP (can fallback to SIP)

TX/CTS to SX/EX/MX/C series SIP

TX/CTS to MCU SIP

TX/CTS to any other video endpoint SIP

SX/EX/MX/C series to CTMS TIP

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.


Users and Endpoints

Content sharing

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)

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

Benefit of separate media channel for content

allows users to customize their experience

In case of content channel failure, fallback is to

switched or composite main video

Composite Switched

Requires TX6 software on endpoint*


Users and Endpoints

• 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

Annotation

25


Users and Endpoints

Free Jabber

26

26

www.ciscojabbervideo.com

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

• Check release notes for further details

Significant endpoint features by release

27

Release Product Features/Functionality Release Date*

TE6 EX60, EX90

• CUCM Encryption

• CUCM Ad hoc conferencing

• Shared Line support

• BlueTooth Headset support

• MWI

• Medianet mediatrace

Nov 2012

TC6

SX20, EX60, EX90, MX200,

MX300, C20, C40, C60,

C90, Profile series

• CUCM Encryption

• 1080p60 on C40/C60/C90 (recent hardware)

• CTMS Encryption

• ISDN Link support

• Medianet mediatrace

Feb 2013

TX6

CTS500-32, TX1300-47,

TX1310-65, TX9000,

TX9200

• 1080p60 and 720p60 support (not

supported on 500-32)

• 1080p30 presentation

• Annotation

• Touch snapshots

Feb 2013

*Dates subject to change


Endpoints

• CUCM Encryption

• CUCM Ad hoc conferencing

• Shared Line support

• Bluetooth Headset support (EX series only)

• MWI

• Call Forward All

• Consultative Transfer

• Remote Expert support

TE and TC software on EX series

28

TE6 Released Nov 4th, 2012

Available today on EX60

and EX90 with TE6

Available with TC 6.1 later this year

TE6 should be used for CUCM customers

who need the above Telephony features

on their EX systems today


Users and Endpoints

Summary

IP Phones (7965s) for wall mounted phones in shared workspaces

9971s with optional video camera

EX60s for managers, doubles as their laptop monitors

MX300s in existing conference rooms

All endpoints enabled for video

9971s with cameras for bulk of employees

EX90s for manager or any groups more likely to require content collaboration

Dual Profiles in multipurpose conference rooms with option for multiple mics

Immersive TX9000s at campus and each branch office with sufficient WAN BW

EX60s for personal endpoints

MX200s for multipurpose

Use Case 1

Use Case 2

Use Case 3


Agenda

30

Introduction


Users and Endpoints




Call Control


Conferencing




Q&A, Roadmap


31



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

Cisco Discovery Protocol (CDP)

CDP Support (min version)

CTS/TX Endpoints 1.0

EX/MX/SX/Profile Endpoints TC5

E20 TE4.2



Quality of Service (QoS)

On the Campus & WAN Edge

Classify and mark traffic as close to its source as technically and administratively feasible. Allow trusted hosts to mark their own traffic

Use DSCP whenever possible. DSCP provides more granularity than IP Precedence

Follow standards-based DSCP Per-Hop Behaviors to ensure interoperation and future expansion

RFC 2474 Class Selector Code Points

RFC 2597 Assured Forwarding Classes

RFC 3246 Expedited Forwarding

RFC 3662 A Lower Effort PDP (Scavenger)

RFC 4594 Configuration Guidelines for DiffServ Classes

Chro

nolo

gy

Update: With the progression of TelePresence into a much more ubiquitous technology ranging from high-end immersive systems to desktop systems and even mobile devices, our recommendation is that TelePresence should be in the Class-Based Weighted Fair Queue (CBWFQ) and receive an AF PHB.

http://www.cisco.com/en/US/docs/solutions/Enterprise/Video/qosmrn.html





Quality of Service (QoS)

34

Low-Latency Queuing. Optionally to set endpoint ports to 100Mbps, forcing the codec’s NIC to shape bursts down even further

Low-Latency Queuing with > 1MB of buffer for ports carrying multiple calls

Cisco IOS Software Class Based Weighted Fair Queuing (CBWFQ) Queuing strategy nested within a HQoS shaper policy to comply with any upstream policers. Also verify adequate Packet Per Second (pps) performance

TX 9000

Core Distribution Access WAN Handoff

WAN

TS

MCU

TCS



Summary of WAN recommendations

35

• Cisco no longer recommends placing TelePresence traffic (or any video traffic for

that matter) in the Priority Queue.

‒The PQ should be reserved for voice packets which exhibit a CBR traffic profile of small packets sent at

consistent intervals

‒Video/TelePresence exhibits a VBR traffic profile of variable sized packets at inconsistent intervals and

should be placed in the CBWFQ

• The following best practices will help protect you and give you some room for error

On a converged network

Avoid allocating more than 33% of your total circuit capacity to the PQ

Avoid allocating more than 50% of your total circuit capacity to the TelePresence queue

Reserve 25% of your total circuit capacity for your default queue traffic

On an overlay network

Avoid allocating more than 80% of your total circuit capacity to the TelePresence queue

Reserve 20% of your total circuit capacity for OAM&P overhead traffic



HQoS Shaping & Queuing Recommendation

36

TX Ring

policy-map WAN-EDGE

class VOIP

priority 1000

class video

bandwidth 12500

class CALL-SIGNALING

bandwidth x

class TRANSACTIONAL

bandwidth y

class BULK-DATA

bandwidth z

class class-default

fair-queue

Packets in

Packets out

policy-map HQoS-50Mbps

class class-default

shape average 50000000 1000000

service-policy WAN-EDGE

Class-

Based

Shaper

• Queuing policies will not engage unless the interface is congested

• A shaper will guarantee that traffic will not exceed the contracted rate

• A nested queuing policy will force queuing to engage at the contracted sub-line-rate to prioritize packets prior to shaping

Updated Recommendations: Assign video to the CBWFQ

Use HQoS+Shaping on all WAN

interfaces

CBWFQ

Scheduler

FQ

Call-Signaling CBWFQ

Transactional CBWFQ

Bulk Data CBWFQ

Default Queue

1 Mbps

VOIP

Policer

1 Mbps PQ (FIFO) for VOIP

TelePresence CBWFQ

GigE interface with a sub-line-rate

access service (e.g. 50 Mbps)



Environmental Factors that affect bandwidth:

• Lighting

• Motion

High definition bandwidth requirements

• Color/pattern

• Quality setting/Optimal definition profile

Select TelePresence Endpoint---->Maintain and Operate---->Admin Guide

http://www.cisco.com/cisco/web/psa/maintain.html?mode=prod&level0=280789323

CTS/TX SX/EX/MX/C Series






How to Preserve User Experience in Non-Ideal Networks?

39

SiSiSiSiSiSi

SiSiSiSiSiSi

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 LTRF’s

• When a frame is lost, encoder creates “Repair-P” differential frame based on last synchronised 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 sync’ed LTRF

OOS (P4)



Media resiliency - Forward Error Correction (FEC)

43

R2

• 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

...

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

44

• 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

LTRF and Repair-P 1.6 TC 4.0

FEC TC 4.0

Dynamic Rate Adjustment 1.7 TC 4.0

Call Control


Call Control

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 MCS and UCS servers

• Uses a variety of voice and video protocols

including SCCP, SIP, H.323, and MGCP

Cisco CUCM and Cisco VCS

46

Cisco VCS

• Designed specifically 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

47

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, 3rd party video, IPv4 to IPv6, Jabber

Video)

VVVV

VCS-C VCS-E

PSTN

Internet

Unity CUPS Contact Center

CUCM

VCS


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

48

CUCM

VCS-C VCS-E

VCS-C VCS-E

VCS Only Deployment

Vision Recommendation Most functionality


Call Control

Dial Plan – E.164 and URIs

49

E.164 An ITU-T (International Telecommunication Union)

recommendation that defines the public

telecommunication numbering plan used in the PSTN.

It also defines the format of telephone numbers.

URI Uniform resource identifier (URI) is a string of

characters used to identify a name or a resource.

Such identification enables interaction with

representations of the resource over a network.

408-555-1234 [email protected] or

[email protected]

Alphanumeric URI

E.164 Based URI

E.164


Call Control

Common URI concerns

50

Registration with URI Issue:

Can endpoint register with URI?

What this affects:

Calls to that endpoint. If an endpoint cannot

register a URI, then anyone trying to call that

endpoint needs to dial a E.164 DN number

Support

CUCM 9.0 allows endpoints to

register with a DN and have a URI

alias. This allows users to reach this

endpoint by dialing a URI or DN.

Dialing URIs Issue:

Most CUCM endpoint user interfaces are

not capable of dialing URIs

What this affects:

CTS/TX endpoints are limited to dialing

E.164 numbers. If CTS/TX is trying to

reach a URI destination on VCS, FindMe

must be used

Support

CTS release 1.10/TX6 allows users to dial

E.164 or URIs using the Cisco Touch 12.

99xx phones have this ability in 9.3(1).


Call Control

CUCM release 9.0 URI support

51

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 alias’s 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

EX90

DN: 5551234

Primary URI: [email protected]

URI: [email protected]

SIP

EX90 dials

[email protected]

CUCM blends

Bob’s DN and

URI for caller ID

9971

9971 sees call

coming from

[email protected]

and “5551234”

DN: 5559876

Primary URI: [email protected]

Can be changed

in CUCM 9.1

mailto:[email protected]





Call Control

CUCM Inter-Cluster routing

52

A URI is owned by one CUCM cluster

Integrated Lookup Service (ILS) handles URI routing between clusters

ILS can provide URI Syncing, which is the exchanging of URI route strings between member

clusters in the network

Each cluster replicates its URIs and route string to its neighbors

Hub and spoke replication topology

ILS discovery service allows CUCM to find remote clusters without manual configuration

URI syncing can also use URIs imported (CSV file) from non-CUCM clusters, like VCS

CUCM 9.0 released August 2012


Call Control

CUCM Inter-Cluster routing

53

EX90 SIP

EX90 dials

“[email protected]”

CUCM URI Routing Logic

Is LHS a DN?

-route based on existing translation rules, registered DNs, and route patterns

Does whole URI match a local URI in the CSS?

-route to local endpoint

Does URI match an entry in ILS?

-route based on route string provided by ILS, using SIP Route Patterns and Trunks

Does RHS of URI match a SIP route pattern?

-route according to SIP route pattern

ILS

[email protected]?

Send to “us.cucm.cisco.com”

ILS Route String

CUCM sends call to

us.cucm.cisco.com

cluster

uk.cucm.cisco.com

us.cucm.cisco.com

Steve


Customers now have a choice, these

endpoints can register to CUCM or VCS

Following features are supported on CUCM:

CUCM TFTP Support

Shared directory support

E.164 and alphanumeric URI dialing

Native voicemail, call forwarding, music on

hold, Cisco Unified Mobility support

CTI/remote-cc for Remote Expert and

desktop control (EX only)

Ad hoc conferencing on UCM (EX/E20 only)

Enhanced Shared Lines on UCM: resume

held call, Barge, etc. (EX/E20 only)

Call Control

SX/MX/EX/C series and E20 on CUCM

54

E20 (TE 4.1) CUCM 8.5(1)

EX, C series (TC5) CUCM 8.6(1)

MX, SX (TC5) CUCM 8.6(2)

CUCM

Minimum versions for CUCM registration


Users and Endpoints

Summary

CUCM business edition 6000 9.1

CUCM as call control and

registration of all Cisco endpoints

Optional VCS-C to be bundled with

BE6k for non-Cisco endpoints or to

enable B2B calling with the addition

of a VCS-E

Voicemail, Unified Presence also

bundled with BE6k

Cluster CUCM for Cisco endpoint call control

and registration

Cluster of VCS-C for any non-Cisco or H.323

endpoints

VCS-E used for B2B video communications

VCS-C for call control and endpoint

registration

Endpoints register via SIP and/or

H.323

Neighbor zone to existing PBX for

audio calls

Use Case 1

Use Case 2

Use Case 3


Agenda

56

Introduction


Users and Endpoints




Call Control


Conferencing




Q&A, Roadmap

Conferencing


Conductor

Conferencing

Many, many options

CTMS

MCU

Telepresence Server

MSE

8000

CUCM VCS

TMS

Endpoint characteristics

and capabilities

Call control

Additional

applications

Multipoint

platforms


Conferencing

TelePresence Conferencing Platform Form Factors

TelePresence Server CTMS MCU

7010

16 ports at 720p30 or

12 ports at 1080p30

8710

16 ports 720p30 or

12 ports 1080p30

UCS 210 M2

48 ports at 720p30 or 1080p30

MCS 7845-I3

MCS 7845-I2

MCS 7845-H2

48 ports at 720p30 or 1080p30

4203, 4205, 4210, 4215, 4220

4501, 4505, 4510, 4515, 4520

8420

8510

6 to 40 ports at 720p15/480p30

6 to 40 ports at 720p30


40 ports at 720p15/480p30

80 ports at 480p30

10 ports at 1080p30

5310, 5320




Conferencing

TelePresence Conferencing Platform Form Factors

TelePresence Server CTMS MCU

7010


12 ports at 1080p30

8710

16 ports 720p30 or

12 ports 1080p30

UCS 210 M2

48 ports at 720p30 or 1080p30

MCS 7845-I3

MCS 7845-I2

MCS 7845-H2

48 ports at 720p30 or 1080p30

4203, 4205, 4210, 4215, 4220

4501, 4505, 4510, 4515, 4520

8420

8510

6 to 40 ports at 720p15/480p30



40 ports at 720p15/480p30

80 ports at 480p30

10 ports at 1080p30

5310, 5320



7010


12 ports at 1080p30

8710

16 ports 720p30 or

12 ports 1080p30 8510

80 ports at 480p30

10 ports at 1080p30

5310, 5320




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

Endpoints capable of Multisite:

C40

C60

C90

Embedded conferencing - multisite

62

Embedded

Conferencing

(Multisite)

Ad Hoc

Rendezvous

Scheduled

CUCM Endpoint Configuration

EX90

SX20

Part Numbers:

LIC-P65-C90-MS

LIC-P55DC60-MS

LIC-EX90-MS

LIC-INTP-C90-MS


Conferencing

• Clustering -Combining similar multipoint resources into a single

conferencing resource who’s capacity is the combination of all

individual instances

-Stacking: A form of clustering that does not rely on a chassis

based architecture (like the MSE 8000). With stacking, two

appliance models can be combined in to a single cluster through

use of a special “stacking” cable between the two devices.

Currently only supported on the Cisco 5300 series MCUs.

Clustering, cascading, and stacking

63

Device Clustering Cascading

TelePresence

Server

CTMS

MCU

• Cascading -Having two or more separate conferencing resources (can

be standalone or clustered resources) call to each other to

increase capacity. Cascading more than two resources is

accomplished in a hub and spoke architecture.

*Requires TelePresence Server (8710) or MCU (8510) blades in a MSE

8000 chassis, or 5300 series

*

*


Conferencing

Cisco TelePresence Server

64

Two models:

8710 blade

Standalone 7010

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


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)


INVITE sip:[email protected]:5060 SIP/2.0

Via: SIP/2.0/TCP 172.19.236.70:5060;branch=z9hG4bK23a64c83c7a6

From: "Michael Thomma" <sip:[email protected]>;tag=115695~552e7c5a-df83-490f-83fc-4077ebe372ef-30056562

To: <sip:[email protected]>

Date: Tue, 31 May 2011 22:26:02 GMT

Call-ID: [email protected]

Supported: timer,resource-priority,replaces

Min-SE: 1800

User-Agent: Cisco-CUCM8.6

Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY

CSeq: 101 INVITE

Expires: 180

Allow-Events: presence, kpml

Supported: X-cisco-srtp-fallback

Supported: Geolocation

Call-Info: <sip:172.19.236.70:5060>;method="NOTIFY;Event=telephone-event;Duration=500"

Cisco-Guid: 4129111680-0000065536-0000004651-1189876652

Session-Expires: 1800

P-Asserted-Identity: "Michael Thomma" <sip:[email protected]>

Remote-Party-ID: "Michael Thomma" <sip:[email protected]>;party=calling;screen=yes;privacy=off

Contact: <sip:[email protected]:5060;transport=tcp>;video;audio;x-cisco-tip;x-cisco-multiple-screen=1

Max-Forwards: 67

Content-Length: 0

Conferencing TelePresence Server – support for TIP

66

CUCM 8.5, CTS 1.7.4, and TS 2.2 or later is required to take advantage

of the “x-cisco-tip” and “x-cisco-multiple-screen” SIP headers

If CTS endpoint is pre-1.7.4 or CUCM version pre-8.5, you still need to

manually configure CTS endpoints on TS

x-cisco-tip;x-cisco-multiple-screen=1


Conferencing

TelePresence Server Experience

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 licensing and capacity changes

68

16

Optional

optimization of

resources

discussed later

• 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

OR

or or 12 24

12 or

24 12

Full HD= 1080p30 /

720p60

HD = 720p30


Conferencing

TelePresence Server - deployment

69

VCS

TS

Conductor CUCM

VCS

Ad Hoc

CUCM

TS

H.323 HTTP(s) SIP

Rendezvous

Scheduled


Conferencing

CTMS

70

Software-based solution

Schedulable with CTS-Manager

CUCM communication via SIP trunk

Scheduled and Non-Scheduled meeting support

Voice Activated Switching

Supports up to 48 screens in a single instance

Supports up to 440 screens in a network multipoint meetings (hub and spoke cascading)

H.264 -1080p, 720p, 360p & CIF video support

AAC-LD, G.722 & G.711 audio support

Flow Control

Distributed deployment with geographical selection (CTS-Manager required)

Release 1.9 is the last major release for CTMS


Conferencing

• SX/EX/MX/C series endpoints running TC5 or later can use CTMS for

multipoint meetings

• CTS release 1.8 or later is required for TC5 endpoint interop on CTMS

CTMS version requirements for SX/EX/MX/C series support

71

CTMS

CTS 1.8 CTS 1.8

TC5

CTMS 1.8

CUCM 8.6

CUCM

SIP Media

VCS

TC5


SIP

Conferencing

• CUCM Registration ‒ Call Protocol : SIP

‒ Call rate: 3075 Kbps

‒ TIP mode: Auto

• VCS Registration ‒ SIP Protocol Required

TC5 on CTMS details

72

• Video: H264

HD Video is compatible with CTS versions 1.8 and above only

LTRP and CABAC are NOT supported

• Audio: AAC-LATM

Sends and Receives single stream in each direction

• Presentation:

Video at 5 fps

Audio mixed with main audio

Call Control

Media

• Supported

OBTP

IVR

• Not Supported

Roster List

Features

CTMS

TIP


Conferencing

• Always SIP trunked to CUCM

• It is possible to cascade up to 11 CTMS’s (scheduled or non-scheduled)

enabling 440 endpoints in a single conference

CTMS Deployment

73

CTMS CUCM

Rendezvous

SIP

Scheduled

Requires CTS-Man

• Current CTMS customers are encouraged to migrate

conferencing to TelePresence Server


Conferencing

MCU

74

Several models:

8510 and 8420 blade

Standalone 5300 series



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

5300, 4500, and 4200 all run same software

Port Mode Quality

nHD 360p30

SD W448p30

HD 720p30 / w448p60

HD+ 1080p30 (asymmetric)

Full HD 1080p30 / 720p60


MCU

Capacity

75

8510

4203

5310

4205

4210

4215

4220

4501

4505

4510

4515

4520

8420

5320

nHD (360p30)

SD (w448p30)

HD (720p30 / w448p60)

HD+ (1080p30 assymetric)

Full HD (1080p30 / 720p60)

6

12

20

30

40

40

12

NA

NA

NA

NA

80

20

40

NA

NA

NA

NA

NA

NA

NA

NA

NA

NA

NA

80

24

48

0

0

0

0

0

0

6

12

20

30

40

20

10

20

0

0

0

0

0

0

3

6

10

15

20

20

NA

NA

0

0

0

0

0

0

3

6

10

15

20

15

5

10


MCU

• CUCM added ad hoc conference bridge support for 4200, 4500, 8420,

8510, and 5300 MCU’s 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

76

CUCM MCU

SIP (trunk created

behind the scenes)

HTTP(s)

MCU API Used by CUCM

Create Conference

Modify Conference

Destroy Conference

Device Query (keepalive)


Conferencing

• New in-call menu with options for:

‒ Lock/unlock conference

‒ Add participants

‒ View roster list on-screen

‒ Mute, control volume, stop/start video or

disconnect certain participants

‒ Send DTMF tones to a certain participant

• Increased 1080p port count on 8510 blades

• Tighter integration with CUCM, KPML

support

• API improvements

• Pass-through content mode to save video

ports

Cisco MCU 4.3 release

77

Released February 2012


Conferencing

• All of our video endpoints are supported on

both TelePresence server and MCU!

CTS/TX with MCU

78

• 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

CTS 1100

CTS 3010

CUCM CTS 500-32

VCS

CTS 500-37 called into 4501 MCU


MCU

MCU

Conferencing

MCU - deployment

79

VCS

MCU

Conductor CUCM

VCS Ad Hoc

CUCM

H.323 HTTP(s) SIP

Scheduled

Rendezvous


Conferencing

TelePresence Conductor

Manages MCU (42xx, 45xx, 53xx, 8420 & 8510) and TelePresence Server (7010 and 8710)

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

Cisco TelePresence Conductor

80

Shipping since November 2011

Whole process is transparent to the end user

CUCM or VCS Conductor

Full

Cascaded

Meeting

Example:


Conferencing

• Support for TelePresence Server

• Support for direct integration with CUCM

• SIP B2BUA puts Conductor in the signaling path

Conductor – XC 2.0

81

XC2.0 released December 2012

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


Conductor

• Available with initial XC 1.0 Conductor

release

• Conductor is invoked as a Policy Server

from VCS using CPL (Call Processing

Language)

• Multipoint devices are registered to

VCS using SIP or H.323

Integration with call control

82

CPL H.323 HTTPs

VCS Conductor

SIP


Conductor

Integration with call control

83

CUCM 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

VCS

CPL H.323 HTTPs SIP


Conferencing

Example of optimization of resources

84

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 22


Conferencing

Conductor deployment

85

CUCM Conductor

VCS

SIP H.323 HTTPs

Conductor added as a “conference bridge” in CUCM

SIP Trunk 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)


Users and Endpoints

Summary

5320 MCU for ad hoc conferences

5320 MCU for rendezvous

conferences

Pay as you grow licensing on

MCUs and ability to stack for

increased scale

MSE 8000 in centralized site with 8710 TelePresence

Servers blades

7010 TelePresence Servers in branch offices for

localized resource

Conductor trunked to CUCM as ad hoc and rendezvous

service

8710s registered to VCS for scheduled conferences

5310 MCU

Multiway used for ad hoc calls

Use Case 1

Use Case 2

Use Case 3



88



• 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 3rd party applications to schedule and monitor

systems

• Available as software (can be run in VMWare)

Cisco TMS and Cisco CTS-Manager

89

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

90

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

91

TMSXE

TMSXN

TMSBA

TMSPE

Windows Server 2008

Windows Server 2008 R2

Integrates TMS with Microsoft Exchange

(2007, 2010) via EWS

TMSXN Cisco TelePresence Management Suite

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 Cisco TelePresence Management Suite

Extension Booking API

Optional feature of TMS Provides a Web Services API that

interfaces with the TMS booking engine

TMSPE Cisco TelePresence Management Suite

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

92

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

93

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

94

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

13.1 Released July 2011

14.1 Released Dec 2012



• “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

• With 13.2 or later:

‒ All CTS/TX endpoints can be scheduled on TS or MCU

‒ CTS/TX endpoints can be scheduled to call directly to non-TIP endpoints

TMS support for TX/CTS endpoints

95

Ensure all CTS/TX endpoint scheduled by TMS are running version 1.7.4 or later before enabling this feature



TMS call launch options

96

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

Automatic

Connect

One Button to

Push

Manual Connect No Connect Reservation

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



• 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

97

TC5 TC5

CTS 1.7.0 or later CTS 1.8


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

98

TMS/TMSXE: 13.1.2 / 3.0 and later

TMSXE



Sneak Peak!

99



• TMS is the scheduling platform moving forward for TelePresence

• TMS supports endpoints registered to CUCM and/or VCS

Key Takeways

100


Agenda

101

Introduction


Users and Endpoints




Call Control


Conferencing




Q&A, Roadmap


TelePresence/Video Sessions

102

BRKEVT-2801 Integrating Voice and Video Call Routing and Dial Plans Wednesday 14:00

BRKEVT-2400 Scheduling Best Practices for Cisco Telepresence Friday 11:30

BRKEVT-2319 Business to Business Video Thursday 9:00

BRKARC-1006 Planning, Building & Deploying Cisco's Remote Expert Solution Tuesday 11:15

BRKEVT-2317 Video Content: Unlock the Power of Video with "Capture, Transform, Share" Solution Friday 9:00

BRKEVT-2800 Overview of Cisco TelePresence Solution and Deployments Tuesday 16:15

BRKEVT-2802 Deploying TelePresence and Video Endpoints on Unified Communications Manager Tuesday 14:15

BRKEVT-2803 Designing and Deploying Multipoint Conferencing for Telepresence Video Thursday 14:00

BRKEVT-2804 Monitoring and Troubleshooting Network Impairments in Video Deployments Tuesday 14:15

BRKEVT-2805 Understanding and Troubleshooting EX-Series Personal Telepresence Systems and C-Series Codecs Wednesday 16:30

TECEVT-2674 Conferencing and Scheduling Design for Cisco Telepresence Monday 14:15

COCEVT-2577 Inside Cisco IT: The Do’s, Don’ts and Lessons Learned during Five Years of Video Deployment Thursday 11:30

LTREVT-2300 Enterprise Medianet: Video Applications and Network Design Lab Wednesday 9:00


Call to Action

• Visit the Cisco Campus at the World of Solutions to experience Cisco innovations in action

• Get hands-on experience attending one of the Walk-in Labs

• Schedule face to face meeting with one of Cisco’s engineers

at the Meet the Engineer center

• Discuss your project’s challenges at the Technical Solutions Clinics

103

brkevt 2800 telepresence overview

Documents

total circuit capacity

cisco telepresence solution

latency queuing

media resiliency

call control

cisco solution

dial plan

conferencing types