brkevt 2803 multipoint conference

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

Designing and deploying multipoint

conferencing for telepresence video

Richard Murphy

[email protected]

BRKEVT-2803


Abstract

Over the last few years video adoption in Enterprises has increased remarkably, for both internal and

external calls. This session is intended for Cisco partners and customers who have already deployed

Cisco Telepresence and Video Conferencing for point-to-point video calls and want to add an

architecture for multipoint video in an environment made of H.323 and SIP endpoints, HD and SD

systems, with single or triple screens. The purpose is to learn how to build a multipoint architecture in

order to provide a seamless experience to devices with different video capabilities. As a part of this

architecture, this session will focus on the Cisco MCU, Cisco TelePresence Server and Cisco

TelePresence Conductor infrastructure products.


Agenda

Portfolio Overview

Use Case 1 – Video Communication Server centric customer

Use Case 2 – Unified CM centric customer

Use Case 3 – Unified CM and VCS customer

Bring it all together

Reference Material


TelePresence Architecture Overview

Campus

Branch

Conferencing Call Control

Endpoints

Scheduling &

Management Monitoring Recording &

Streaming

Endpoints Conferencing

WAN

Internet Global

B2B Inter-

Network

External Connections

Mobile Office

5


TelePresence/Video Sessions

6


Conferencing Bridge Portfolio What do I choose?

MSE 8000 MSE MCU 8420 MSE MCU 8510 MSE TS 8710

MCU 4501 MCU 4505

MCU 4203 MCU 4205 MCU 4210 MCU 4215 MCU 4220

MCU 4520 MCU 4515 MCU 4510

MCU 5310 MCU 5320 5300 stack

TS 7010

CTMS

Conductor

ISR G2

7


Infrastructure Portfolio

8

Conferencing Platform Form Factors

TelePresence Server MCU

7010

24ports at 720p30 or

12 ports at 1080p30

8710

24ports 720p30 or

12 ports 1080p30

4 blade cluster

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

15 ports at 1080p30

5310, 5320



Note: 8710, 8510, and 8420 blades requires the MSE 8000 chassis

SD is less than 720P


Infrastructure Portfolio What products do I choose?

9


Infrastructure Portfolio Simplification

10

Primary Conferencing Platform to consider

TelePresence Server MCU

7010

8710

5310 or 5320

8510

NOTE: 8710 and 8510 require the MSE 8000 chassis


Infrastructure Portfolio What is the difference?

11

Active Presence

Continuous Presence

Conference Pins Cascading

Lecture Mode VCS Integration

UCM Integration

SIP

H323

On Screen List of Participants

Auto Attendant

Immersive support

TIP

HD

SD


TelePresence Server Overview • Summary of Unique features

TelePresence Server

Description Flagship Conferencing

product of portfolio

Application Immersive experience

with Active Presence

Quality Up to Full HD (1080p) for

single screen, triple

screens, and 3rd party

endpoints

Unique

Features

TIP support, also supports

H.323 and SIP

Scalability Up to 12 Full HD screens

Up to 24 HD screens

Active Presence

12


MCU Overview • Summary of Unique features

5300 or 8510 MCU

Description Feature rich and robust

conferencing product

Application Everyday use for ad hoc,

rendezvous, or scheduled

meetings

Quality • SD up to HD for single

screen and 3rd party

endpoints.

• H323 and SIP support

Unique

Features

50+ layouts, highly

configurable

Scalability Up to 45 FullHD (8510) or

20 FullHD (5300s) ports

13

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

Use Case 1

Campus

Multipoint

VCS

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 Cisco VCS-C for call control Single screen personal and multipurpose endpoints Single MCU for internal conferencing

3rd party PBX


VCS and MCU Conference Resource Choice

15

MCU Solution

5310 or 5320

MCU

Signaling Media

VCS

Endpoints

Newest hardware platform. (Released March 2012.)

Low cost entry point solution

Flexibility – ports and expansion

Runs same software code as other MCUs in the portfolio

CTI-5310-MCU-K9 or CTI-5320-MCU-K9


Model Mode Video

Ports

Audio-only

ports

Ports activated

per LIC-5300-

4PL

MCU 5310 nHD 24 0 8

SD 20 0 4

HD 10 10 2

Full HD 5 5 1

MCU 5320 nHD 48 0 8

SD 40 0 4

HD 20 20 2

Full HD 10 10 1

MCU 5300 Port Counts Non-stacked

LIC-5300-4PL

HD Up to 720p30, or w448p60

Full HD Up to 1080p30 or 720p60

SD Up to w448p30

nHD Up to w360p30

16


5300 Series Hardware features

1U 19’ rack unit (5310 or 5320) 2U for a stack.

Fans are at the front to enable front to back cooling

‒ Fits with the Data Center models for cooling (cold

/warm aisle)

Front

Back

Console LCD

Stacking Ethernet

Stacking connector on back

‒ 1 connector (only connect 2 together)

‒ Special cable, Orderable with system or as Spare.

When Stacked only Primary Ethernet is required to be

connected.

‒ Front LCD panel of the secondary MCU will show

different information in a stack.

Stacking is configured on both units. Once in a stack

(cluster), all configuration is done on the Primary MCU.

17


VCS and MCU Conference Resource Choice

18

MCU Solution

1) Single 5320 supports up to 10 Full HD, 20 HD, 40 SD, or 48 nHD 2) Stacked 5320 supports up to 20 Full HD, 40 HD, 80 SD or 80 nHD

5310 or 5320

8510

Stack of

5310 or 5320

1) Single 8510 supports up to 10 Full HD, 20 HD, 40 SD

• Supports expansion for 2 devices • Low cost of entry to Multipoint solution

• Supports expansion to multiple blades in MSE 8000 • Cluster up to 3 blades

MCU

Signaling Media

VCS

Endpoints


VCS and MCU Configuration Steps

19

MCU

Signaling Media

VCS

Endpoints 1) Change default passwords and add secondary admin account

2) Install Encryption Key and disable HTTP access


VCS and MCU Configuration Steps

20

4) Optional: Configure static conference and parameters

5) Call the conference ID and PIN or Auto Attendant

3) Register the MCU to the VCS via H323 and/or SIP

MCU VCS

Endpoints


Conferencing

Non Scheduled Conferences

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

Types of conferences

Note: A resource used for scheduled conferences should not be also used for ad hoc conferences in order to guarantee port availability for scheduled calls. Therefore Cisco recommends that MCUs used for scheduled conferences are never used for ad hoc calls and separate MCUs are provided for ad hoc conferencing.

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.

21


VCS and MCU Conferences

22

Conference Type Options

Scheduled

• Using TMS either directly or via an

integration, for instance with

Microsoft Exchange

Note: Not recommended to mix scheduled and non scheduled for a single MCU. Better to dedicate a single MCU for each type of conference.

Scheduled

bridge

Ad

hoc/Rendezvou

s bridge

VCS

Scheduling and

Management


Non Scheduled • Auto Attendant

• Ad hoc - Dynamic escalation using

Multiway.

• Rendezvous - either statically

configured on an MCU or

dynamically created by MCU on

dialing a conference number.

Refer to management breakout session, BRKEVT-2400 “Scheduling Best Practices for Cisco Telepresence” for more details


VCS and MCU Conference scaling

23

MCU

Signaling

Media

VCS

Endpoints

• Speakers on Primary MCU • Support H.323 cascading only • Increases Port capacity of the conference • Requires video port on each MCU for Cascade

Cascade Link

Up to 3 blades per cluster

LIC-5300-4PL 1 Full HD, 2 HD, 4 SD or 8 nHD ports on MCU 5300

LIC-8420-2PL 1 license provides 1 HD, 2 SD or 4 nHD ports

2 licenses required for 1 Full HD port

How do you increase scale?

Clustering

Cascading

Up to 2 MCU 5300s per cluster


VCS and TS Choice

24

TelePresence

Server

Signaling

Media

VCS

Endpoints

Can I use a TelePresence Server?

Form Factor Options

Appliance - 7010

MSE Blade - 8710

ActivePresence

Immersive Experience

*FullHD or HD resolution

* TS2.3 or below


VCS and TelePresence Server Configuration

1) Change default password and add secondary admin account


3) Set HD Mode (FullHD – 1080p or HD – 720p), enable 60fps

25



4) Register the TS to the VCS via H.323 and/or SIP

26



5) Configure conference and parameters

6) Call the conference ID and PIN

Note: Rendezvous Conferences Only

27


VCS and TelePresence Server Conferences

28


Scheduled

• Using TMS either directly or via an

integration, for instance with

Microsoft Exchange

Note: Not recommended to mix scheduled and non scheduled for a single MCU. Better to dedicate a single MCU for each type of conference.

Scheduled

bridge

Rendezvous

bridge

VCS

Scheduling and

Management


Non Scheduled • Rendezvous - statically configured

conference on a TelePresence

Server

• Ad hoc not supported

Refer to management breakout session, BRKEVT-2400 “Scheduling Best Practices for Cisco Telepresence” for more details


VCS and TS Conferences

29

TelePresence

Sever

Signaling

Media

VCS

Endpoints

Up to 4 blades per cluster

8710 - LIC-8710-1SL 1 Full HD (1080p), 2 HD( 720p)

7010 - LIC-TPSRV-1SL

1 Full HD (1080p), 2 HD( 720p)

Not supported configuration Cascade Link

Standalone Unit only

Add licenses up to 12

How do you increase scale?

Clustering

Cascading

Slot 10 can not be used in a cluster


MCU and TelePresence Server What is the difference?

30

MCU 5300 (non

Stacked)

TelePresence

Server 7010

MSE 8510 MSE 8710

Form Factor Appliance Appliance MSE 8000 blade MSE 8000 blade

Experience Single Screen CP ActivePresence Single Screen CP ActivePresence

Layouts 50+ and

customizable

4 layout families 50+ and

customizable

4 layout families

Capacity Up to 10 Full HD

or 20 HD

Up to 12 Full HD or

24 HD

Up to 15 Full HD Up to 12 Full HD

or 24 HD

Content Channels Up to Full HD *Up to HD 30fps

except for CTS,

which is

XGA@30fps

Up to Full HD *Up to HD 30fps,

except for CTS,

which is

XGA@30fps

Audio Mono Stereo and

Multichannel

Mono Stereo and

Multichannel

Clustering Yes, up to 2 in a

stack

No Yes, up to 3 Yes, up to 4

Cascading Yes, with other

MCUs only

No Yes, with other

MCUs only

No

Auto Attendant Yes No Yes No

Conference Pins Yes Yes Yes Yes

* Requires Conductor

For Your Reference


Use Case 2

Campus

Multipoint

Unified CM

The Challenge 750 users, single site No pre-existing video deployment No remote workers Video enable employees for internal communication Voicemail required Instant messaging client needed for workers

The Solution Cisco Business Edition 6000 Desktop TelePresence endpoints for Managers, video enabled

IP phones and soft clients for employees Multipurpose TelePresence installed in existing conference

rooms Two MCUs for rendezvous and ad hoc conferencing only

Unity

Connection Unified

Presence


Unified CM and MCU Conference Resource Choice

32

Stack of

5310 or 5320

MCU

Signaling

Media

Unified

CM

Endpoints API

What conference bridge can I use?

MCU 5300 MSE 8510 Blade

Communications Manager

New Video Deployment

Single Screen Systems

Ad hoc and Rendezvous Conferences

Internal Video requirements

High Bandwidth Available


Unified CM Terminology

33

Media Resource

5310 or 5320

8510

Stack of two 5300s

Media Resource = Conference Bridge

Media Resource

Group

Media Resource Group (MRG) = List of Conference Bridges

Media Resource 1

Media Resource 2

Media Resource 3

Media Resource Group List (MRGL) = Order List of MRGs

Media Resource Group List

Media Resource Group 1

Media Resource Group 2

Media Resource Group List

MRGL are assigned to endpoints using Device Pools

UK 5320

USA 5310

Japan 5320

=

=

=

Device Pool


UCM configuration Conference Bridge Setup Ad hoc

34

1. Add Conference Bridge

2. Add Conference Bridge To MRG

3. Add MRG to MRGL

4. Add MRGL to Device Pool

UCM Configuration Video

Ad Hoc


UCM configuration Conference Bridge Setup Rendezvous

36

1. Add SIP trunk to the Bridge

4. Add Route List for this Route Pattern

3. Add Add Route Groups to Route List

2. Add trunk to Route Group

UCM Configuration Video

Rendezvous


Unified CM Conference Bridge Connectivity

Supports Ad hoc and Rendezvous Conferences

Requires UCM 8.6 or higher, UCM 9.0 for encrypted links

MCU version 4.3 or higher

Requirements Limitations

Cascading not supported

38


Unified CM and MCU MCU Configuration

39

1) Change default password and add secondary admin account


4) Set the “Incoming Calls to unknown conferences or Auto

Attendants” to “Disconnect Caller”.

3) Enable Media Port Reservation

• Guaranteed ports for the conference • No Oversubscription allowed

• Sets the default action when endpoints call into the MCU using a number that does not correspond to any configured conference.


Unified CM and TS Integration

40

TelePresence

Server

Signaling

Media

Unified CM

Endpoints API

Can I use a TelePresence Server?

Ad hoc conferences are not supported

Rendezvous conferences are supported

Cascading not supported

Scheduling not supported by TMS

Technically Yes, but does not fit the use case requirements.


Use Case 3

Campus

Multipoint

Unified CM

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

Unity

Connection

WAN

Internet

Unified

Presence

Branch Teleworker VCS

Conferencing Management

Scheduling

Conductor Video http://www.youtube.com/watch?v=4-C7F2fTEYE

http://www.youtube.com/watch?v=4-C7F2fTEYE




What is this?

43


What is Cisco TelePresence Conductor?

Hardware:

Same Hardware platform as Video Communication Server

Serial numbers are different between Conductor and VCS.

Note: TelePresence Conductor application will not co-exist with the VCS application

Software

Same base software platform as Video Communication Server but unique application built on the

base software.

Key point

Conductor is not a VCS and a VCS is not a Conductor!

44


What is Cisco TelePresence Conductor?

Software (VM version)

Available as a Virtual Machine (UCS or Spec based)

‒ Cisco UCS C200 – M2, UCS C210 – M2, or UCS B200 – M2 with:

Processor supporting AESNI feature

6GB of RAM per VM

132GB disc space per VM (for a 4GB virtual disc 1 and a 128GB virtual disc 2)

R2XX-LBBU (Raid disk battery backup to enable cache)

Four hard disks (450GB SAS 15K RPM 3.5in HDD/hot plug/C200 drive sled)

PCI card Intel Quad port GbE Controller (E1G44ETG1P20)

‒ VM Host operational and running ESXi 4.1 or ESXi 5.0 Update 1

6GB of RAM per TelePresence Conductor VM

132GB disc space per VM (for a 4GB virtual disc 1 and a 128GB virtual disc 2)

2 Cores reserved per TelePresence Conductor VM; each core >= 2GHz processor

Documentation

http://www.cisco.com/en/US/docs/telepresence/infrastructure/conductor/config_guide/Cisco_TelePresence_Conductor_Vi

rtual_Machine_Deployment_Guide_XC2-0.pdf

Virtualized Conductor

45

http://www.cisco.com/en/US/docs/telepresence/infrastructure/conductor/config_guide/Cisco_TelePresence_Conductor_Virtual_Machine_Deployment_Guide_XC2-0.pdf






What does TelePresence Conductor do?

• Whether using a Ad hoc Conferences or Rendezvous Conferences

• Consistent User Experience • Knows all the available and used ports

• Intelligent Bridge selection

• Automatic cascading of MCUs

• Single configuration applied to any conferencing resource

Conference Virtualization

Resource Management/Conference Bridge Selection

Centralized Conference Provisioning and Administration

What does this mean? What does this mean? What does this mean?

• Ad Hoc and Rendezvous Conference support

46


Conductor Connectivity Points

Call Control

Cisco TelePresence

Conductor

MCU Resource Pool

MCU 4200 Series

MCU 4500 Series

TelePresence Server (TS 7010 & MSE 8710) Support in XC2.0 with TS 3.0

MSE 8420 SD MCU MSE 8510 HD MCU

Management

TelePresence Resource Pool

MCU 5300 Series

Basic Conductor Scheduling Support in TMS14.1.1

Conductor with UCM Support in XC2.0

Conductor HW or VM

XC2.0 or higher

NEW ! VCS

SIP Trunk

Endpoints

Registers to either, UCM preferred

Ad hoc Rendezvous

NEW !

Registration

47


Conductor Overview Key Concepts

48

1. Conference Alias – Matches the destination dial string and connects to a template

2. Conference Template – Defines actions for conference bridge

3. Service Preference – Ordered list of Bridge pools

5. Conference bridge – Communication parameters to bridges

6. Auto Dialed Participant – Dial string to add a device to the conference automatically

4. Conference bridge pool – Grouping of conference bridges


Unified CM Terminology

49

Locations

Locations = Bandwidth Management

UCM locations are linked to Conductor configuration

Video Bandwidth

Immersive Video

Bandwidth

Between Locations

Inside Locations

Locations

Locations is Call Admission Control (CAC)


Conductor and UCM How does the model change?

50

Added B2BUA in Conductor

Uses Multiple IP addresses

Looks like MCU to UCM

UCM and Conductor Configuration Video

Unified CM locations


Conductor How it works – Ad hoc

52

SIP Media HTTPs

CUCM Conductor

8710 TS

5300 MCU

172.16.50.1 Management: 172.16.100.1 Ad hoc: 172.16.100.2 Rendezvous: 172.16.100.3

172.16.100.20

172.16.100.50

Note: Conductor does not cascade MCUs for ad hoc conferences.


Conductor How it works - Rendezvous

53

SIP Media HTTPs

CUCM Conductor

8710 TS

5300 MCU

172.16.50.1 Management: 172.16.100.1 Ad hoc: 172.16.100.2 Rendezvous: 172.16.100.3

172.16.100.20

172.16.100.50

For simplicity only single call is shown

Note: Conductor can cascade rendezvous conferences with MCUs only.

Scale Video

http://www.youtube.com/watch?v=lnZEMaSwAGU&feature=g-hist&context=G2d6fc37AHT1dKagASAA






TelePresence Conductor Specification

Maximum supported service and configuration

‒

NOTE: *A lecture (chair/guest) conference will require 2 conference templates (Lecturer and Participant).

Services/Configuration Parameter

Utilised Conference Bridges 30 MCUs or TelePresence

Servers (2400 concurrent calls)

Concurrent Active Conferences 1,200 Conferences

Preconfigured Conference Template 1000 Conferences

Preconfigured Conference Aliases *1,000 Aliases

Preconfigured Auto-dialed Participants 20,000 Users

Preconfigured Auto-Dialed Participants per Conference Template 5,000 participants per conference

template

55


Primary MSE

• 29 Cascaded MCUs in a single call

• 30 TelePresence Servers in 30 different calls at once.

*Clustered – 23 TelePresence Servers

• A combination of both up to 30 conference bridges or 2400

endpoints in a single call

2400 endpoints in a call

Conductor Scale

How many conference bridges

have been tested?

In a single call

VCS and/or Unified CM *TS supports a maximum of 104 calls per cluster 56


TelePresence Server Capacity Changes

57

SD is less than 720P

TS 2.2

12

16

TS 2.3

12

24

• 4 extra

licenses

• 8 extra HD

screens

TS 3.0 +

12

24

48

New Resource

Optimization Model

for main and content

channel.

TPS 8710

Recovers unused

DSP resources

Note: The numbers shown are for a single appliance or blade.

16 licenses 12 licenses 12 licenses

New - SD

support


TelePresence Server configuration Operation mode configuration

Set “Remotely managed” for Operation mode for TelePresence Conductor to manage TelePresence Server

Uses new API on TS

Note: For more detail, please refer to TelePresence Server 3.0 API guide 58


TelePresence Server Optimization of resources

59

Conductor 2.0

Without Conductor

Full HD (1080p30)

HD (720p30)

SD (480p30)

With Conductor

TS 3.0

Once full, additional

endpoints cannot join

12 22

Locally Managed mode


TelePresence Conductor configuration Conference templates configuration

Create “conference template” for TelePresence Server

• Select participant quality, Content Quality, Optimize Resources

Maximum Video Quality

Reclaim Resources after 5 seconds

Maximum Content Quality

• Full HD (1080p 30fps / 720p 60fps video, multi-channel audio)

• HD (720p 30fps video, stereo audio) • SD (wide 448p 30fps video, mono audio)

• Full HD (1080p 30fps / 720p 60 fps) • HD (720p 30fps) • 1280 x 720p 15fps • 1280 x 720p 5fps • Off 60


MSE 8710 Design Options

61

SD clusters • Limited advantage above 2 blades • No call increase after 3 blades Recommend Splitting blades • Make two 2 blade clusters Cluster 1 96 Ports

Cluster 2 96 Ports

Note: TS has a limitation of 104 calls


Sizing and Licenses TS 3.0 Release Note Charts

62

Main Video Audio Content Screen

Licenses

480p30 Mono In main video ¼

480p30 Stereo 720p5 1/3

720p30 Stereo 720p5 ½

1080p30 Stereo 720p15 1

720p60 Stereo 720p15 1

1080p30 Stereo 720p30 1 ½

1080p30 Stereo 1080p30 2

Three-screen 1080p30 Multichannel 720p30 3

Three-screen 1080p30 Multichannel 1080p30 4

Cluster Size SD HD Full HD

1 Blade 48 SD Calls 24 HD Calls 12 FullHD Calls

10 audio-only

calls

10 audio-only calls 10 audio-only

calls


8 audio-only

calls


calls



calls



calls

Do your math correctly for planning purposes !

• Full HD is 1080p30 for main, stereo, 720p15 for content • HD is 720p30 for main, stereo, 720p5 for content • SD is 480p30 for main, mono, in main video for content

How single screen endpoints with 1080p30

main video with 1080p30 content can I have in

a single blade?

Note: CTS/TX systems content channel supports up to XGA@30fps


Sizing and Licenses Conductor

Conductor manages the licenses automatically.

Encryption Key install on TS

Overall status of TS

Resource Allocation

63


Putting the puzzle together How do these part integrate?

64

TelePresence Server

TelePresence MCU

Unified Communications Manager

TelePresence Conductor


Use Case 3

Campus

Multipoint

Unified CM

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

Unity

Connection

WAN

Internet

Unified

Presence

Branch Teleworker VCS

Conferencing Management

Scheduling


Configurations Steps for Conductor to Unified CM

66

Unified CM VCS

2. Build SIP trunk between UCM and Conductor

3. Add Conductor as a Conference Bridge along with MRG, MRGL, and assigning it to a device pool which is linked to an endpoint.

4. Add Conductor as a Rendezvous Bridge via SIP trunk with Route Pattern, Route List, etc

5. Add MCU and TS to Conductor

1. Endpoints registered to VCS or UCM

6. Associate Conference Bridges to Pools, Service Preferences, and to a Templates MCU TelePresence

Server

Endpoints

Summary of Configuration Steps

7.Create Conference Alias for Ad hoc calls.

For Your Reference


Supported Configurations Clustering

67

Unified CM VCS

MCU TelePresence

Server

EMEA

Centralized Call Control

MCU TelePresence

Server

Primary Ad hoc

Registration

SIP Trunk

Rendezvous

Ad hoc Primary Rendezvous

Conductor1 Conductor2 Sync

Configuration

Note: Reference Deployment guide for cluster configuration details. http://www.cisco.com/en/US/products/ps11775/products_installation_and_configuration_guides_list.html

Maximum of 3 Conductors in a cluster

Synchronizes configuration parameters

Design for primary conference connections from UCM are to separate Conductors


Supported Configurations With UCM Locations

68

Unified CM VCS

MCU TelePresence

Server

EMEA

Centralized Call Control

North America

MCU TelePresence

Server

Unified CM

MCU TelePresence

Server

APAC

Not Supported – Breaks Location Model

– Conductor works with 1 cluster only

Supported Design

Not Supported – Cascade Breaks Location Model

Cascade Link

Ad hoc

Registration SIP Trunk

Rendezvous


Multiway Adhoc Conferencing

3-way call established on an MCU intelligently

selected by TelePresence Conductor

Two way call in progress

An incoming call from a third person

Activate MultiWay (press Join)

Original call on hold

Note: Reference the deployment guide for step by step instructions : http://www.cisco.com/en/US/products/ps11775/products_installation_and_configuration_guides_list.html

Endpoint registration point • Unified CM – Ad hoc conference

• MCU 4.3 or higher

• UCM 8.6 or higher

• Merge and Join (TE6)

• C - Series

• Conference button

• 9971 phone

• VCS – Multiway

• VCS X4.0 or higher

• Endpoints must support Multiway

Supported Configurations • VCS + Conductor

• Unfied CM + Conductor

• VCS Sip trunk to Unfied CM + Conductor

Melissa Katie

Ben

69


Supported Configurations Different video services example with UCM

Unified CM VCS

MCU TelePresence

Server

HD Resource Pool

Ad hoc

Registration

SIP Trunk

Rendezvous

HD Endpoints

Unified CM VCS

MCU TelePresence

Server

SD Resource Pool SD Endpoints

TX9000

Profile 55”

EX90

E20

9971

Note: TX9000 and 9971 only registers with UCM 70


Supported Configurations Different video services example with VCS

VCS

MCU TelePresence

Server

HD Resource Pool

Ad hoc

Registration

SIP Trunk

Rendezvous

HD Endpoints

VCS

MCU TelePresence

Server

SD Resource Pool SD Endpoints

Profile 55”

EX90

E20

9971

71


Use Cases Summary

MCU 5300s series registered to UCM as a conference bridge

MSE 8510 blade could also be used

Cascading not support, but clustering is on MSE 8510 blade and

on the MCU 5300s

Conductor orchestrates the conference bridges.

TelePresence Server and MCUs are supported in this design.

Centralized call control to keep location/CAC model.

Clustering of Conductors for redundancy.

Clustering supported on MSE 8510 blades and MSE 8710 blades

MCU 5300 series

Stack for increased scale

Use Case 1

Use Case 2

Use Case 3

Reference Material


Conductor

XC 2.0 Release notes

http://www.cisco.com/en/US/docs/telepresence/infrastructure/conductor/release_note/Cisco_TelePresence_Conductor_Release_N

otes_XC2-0.pdf

Optimized Conferencing for Cisco Unified Communications Manager release notes

http://www.cisco.com/en/US/docs/telepresence/infrastructure/conductor/release_note/Optimized_conferencing_for_Cisco_Unified_

CM_release_note.pdf

XC2.0 API Guide

http://www.cisco.com/en/US/docs/telepresence/infrastructure/conductor/api_guide/Cisco_TelePresence_Conductor_API_Guide_X

C2-0.pdf

XC 2.0 Virtual Machine Guide

http://www.cisco.com/en/US/docs/telepresence/infrastructure/conductor/config_guide/Cisco_TelePresence_Conductor_Virtual_Ma

chine_Deployment_Guide_XC2-0.pdf

Documentation

74

For Your Reference

http://www.cisco.com/en/US/docs/telepresence/infrastructure/conductor/release_note/Cisco_TelePresence_Conductor_Release_Notes_XC2-0.pdf





http://www.cisco.com/en/US/docs/telepresence/infrastructure/conductor/release_note/Optimized_conferencing_for_Cisco_Unified_CM_release_note.pdf



http://www.cisco.com/en/US/docs/telepresence/infrastructure/conductor/api_guide/Cisco_TelePresence_Conductor_API_Guide_XC2-0.pdf











Conductor

Conductor with UCM

http://www.cisco.com/en/US/docs/telepresence/infrastructure/conductor/config_guide/Cisco_TelePresence_Conductor_with_Cisco

_Unified_Communications_Manager_Deployment_Guide_XC2-0.pdf

Conductor with UCM clustering guide

http://www.cisco.com/en/US/docs/telepresence/infrastructure/conductor/config_guide/Cisco_TelePresence_Conductor_Clustering_

with_Cisco_Unified_CM_Deployment_Guide_XC2-0.pdf

Conductor with VCS

http://www.cisco.com/en/US/docs/telepresence/infrastructure/conductor/config_guide/Cisco_TelePresence_Conductor_Cisco_Tele

Presence_VCS_Deployment_Guide_XC2-0.pdf

Conductor with VCS clustering guide

http://www.cisco.com/en/US/docs/telepresence/infrastructure/conductor/config_guide/Cisco_TelePresence_Conductor_Clustering_

with_Cisco_VCS_Deployment_Guide_XC2-0.pdf

Conductor and Multiway

http://www.cisco.com/en/US/docs/telepresence/infrastructure/vcs/config_guide/Cisco_TelePresence_Multiway_Deployment_Guide

_X7_XC2.pdf

Deployment Guides

75

For Your Reference

http://www.cisco.com/en/US/docs/telepresence/infrastructure/conductor/config_guide/Cisco_TelePresence_Conductor_with_Cisco_Unified_Communications_Manager_Deployment_Guide_XC2-0.pdf





http://www.cisco.com/en/US/docs/telepresence/infrastructure/conductor/config_guide/Cisco_TelePresence_Conductor_Clustering_with_Cisco_Unified_CM_Deployment_Guide_XC2-0.pdf






http://www.cisco.com/en/US/docs/telepresence/infrastructure/conductor/config_guide/Cisco_TelePresence_Conductor_Cisco_TelePresence_VCS_Deployment_Guide_XC2-0.pdf






http://www.cisco.com/en/US/docs/telepresence/infrastructure/conductor/config_guide/Cisco_TelePresence_Conductor_Clustering_with_Cisco_VCS_Deployment_Guide_XC2-0.pdf





http://www.cisco.com/en/US/docs/telepresence/infrastructure/vcs/config_guide/Cisco_TelePresence_Multiway_Deployment_Guide_X7_XC2.pdf

http://www.cisco.com/en/US/docs/telepresence/infrastructure/vcs/config_guide/Cisco_TelePresence_Multiway_Deployment_Guide_X7_XC2.pdf


MCU and TelePresence Server

TelePresence MCU Deployment guide

http://www.cisco.com/en/US/docs/telepresence/infrastructure/mcu/install_guide/Cisco_TelePresence_MCU_Deployment_guide_1-

31.pdf

TelePresence Server Deployment guide

http://www.cisco.com/en/US/docs/telepresence/infrastructure/ts/deployment_guide/Cisco_TelePresence_Server_Deployment_Gui

de_2.3.pdf

Deployment Guides

76

For Your Reference

http://www.cisco.com/en/US/docs/telepresence/infrastructure/mcu/install_guide/Cisco_TelePresence_MCU_Deployment_guide_1-31.pdf




http://www.cisco.com/en/US/docs/telepresence/infrastructure/ts/deployment_guide/Cisco_TelePresence_Server_Deployment_Guide_2.3.pdf






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

77

brkevt 2803 multipoint conference

Documents

install encryption key

change default password

unique features scalability

ad hoc conferencing

ad hoc conferences

internet branch wan

media resource group

video communication server