BRKEVT 2803 Multipoint Conference

BRKEVT-2803
Designing and deploying multipoint conferencing for telepresence video

Richard Murphy ricmurph@cisco.com
BRKEVT-2803
2013 Cisco and/or its affiliates. All rights reserved.
Cisco Public
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.
BRKEVT-2803
Cisco Public
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
BRKEVT-2803
Cisco Public
TelePresence Architecture Overview

Campus
Call Control Conferencing Scheduling & Management Monitoring Recording & Streaming
Endpoints
External Connections
Branch
Endpoints
WAN
Conferencing
Global B2B InterNetwork
Internet
Mobile Office
BRKEVT-2803
Cisco Public
TelePresence/Video Sessions
BRKEVT-2803
Cisco Public
Conferencing Bridge Portfolio

What do I choose?
Conductor
MSE 8000
MSE MCU 8420
MSE MCU 8510
MSE TS 8710
TS 7010
MCU 4203
MCU 4205
MCU 4210
MCU 4215
MCU 4220
CTMS
MCU 4501
MCU 4505
MCU 4510
MCU 4515
MCU 4520 ISR G2
MCU 5310
BRKEVT-2803
MCU 5320
5300 stack
Cisco Public 7
Infrastructure Portfolio
Conferencing Platform Form Factors TelePresence Server
7010
2 to 96 ports at 360p30 2 to 20 ports at 1080p30
MCU
5310, 5320
24ports at 720p30 or 12 ports at 1080p30
4501, 4505, 4510, 4515, 4520
8710 Note: 8710, 8510, and 8420 blades requires the MSE 8000 chassis
24ports 720p30 or 12 ports 1080p30 4 blade cluster
6 to 40 ports at 720p30 3 to 20 ports at 1080p30 8510 80 ports at 480p30 15 ports at 1080p30
8420
40 ports at 720p15/480p30
4203, 4205, 4210, 4215, 4220
SD is less than 720P

6 to 40 ports at 720p15/480p30
BRKEVT-2803 2013 Cisco and/or its affiliates. All rights reserved. Cisco Public
What products do I choose?
BRKEVT-2803
Cisco Public
Simplification
Primary Conferencing Platform to consider
TelePresence Server
7010
MCU
5310 or 5320
8710
8510
NOTE: 8710 and 8510 require the MSE 8000 chassis

BRKEVT-2803 2013 Cisco and/or its affiliates. All rights reserved. Cisco Public 10
What is the difference?
SIP Active Presence Auto Attendant Immersive support Continuous Presence UCM Integration Conference Pins H323 Lecture Mode On Screen List of Participants SD
Cascading
TIP
VCS Integration HD
TelePresence Server Overview

Summary of Unique features
TelePresence Server
Description Application Quality Flagship Conferencing product of portfolio Immersive experience with Active Presence Up to Full HD (1080p) for single screen, triple screens, and 3rd party endpoints TIP support, also supports H.323 and SIP Up to 12 Full HD screens Up to 24 HD screens
Active Presence
Unique Features Scalability
BRKEVT-2803
Cisco Public
12
MCU Overview
Summary of Unique features
5300 or 8510 MCU

Description Application Feature rich and robust conferencing product Everyday use for ad hoc, rendezvous, or scheduled meetings SD up to HD for single screen and 3rd party endpoints. H323 and SIP support 50+ layouts, highly configurable Up to 45 FullHD (8510) or 20 FullHD (5300s) ports
Quality
Unique Features Scalability
BRKEVT-2803
Cisco Public
13
Use Case 1
Campus
Multipoint
The Challenge
VCS 3rd party PBX
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
BRKEVT-2803
Cisco Public
14
VCS and MCU

Conference Resource Choice
MCU VCS
MCU Solution
5310 or 5320
CTI-5310-MCU-K9 or CTI-5320-MCU-K9
Signaling Media
Endpoints
Low cost entry point solution Flexibility ports and expansion Runs same software code as other MCUs in the portfolio
Newest hardware platform. (Released March 2012.)

MCU 5300 Port Counts

Non-stacked
Model Mode
LIC-5300-4PL
MCU 5310 nHD SD HD Full HD MCU 5320 nHD SD HD
Video Ports
24 20 10 5 48 40 20
Audio-only ports
0 0 10 5 0 0 20
Ports activated per LIC-53004PL

8 4 2 1 8 4 2
Full HD
10
10
Full HD HD SD nHD
BRKEVT-2803
Up to 1080p30 or 720p60 Up to 720p30, or w448p60 Up to w448p30 Up to w360p30

Cisco Public 16
5300 Series Hardware features

Console LCD
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
Stacking
Stacking connector on back 1 connector (only connect 2 together)
Ethernet
Special cable, Orderable with system or as Spare.

When Stacked only Primary Ethernet is required to be connected.
Back
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.
BRKEVT-2803
Cisco Public
17
VCS and MCU

MCU VCS
MCU Solution
5310 or 5320
Stack of 5310 or 5320
1) 2)
Single 5320 supports up to 10 Full HD, 20 HD, 40 SD, or 48 nHD Stacked 5320 supports up to 20 Full HD, 40 HD, 80 SD or 80 nHD
Supports expansion for 2 devices Low cost of entry to Multipoint solution

Signaling Media
Endpoints
8510
1) Single 8510 supports up to 10 Full HD, 20 HD, 40 SD Supports expansion to multiple blades in MSE 8000 Cluster up to 3 blades
VCS and MCU

Configuration Steps
MCU
VCS
1) Change default passwords and add secondary admin account
Signaling Media
Endpoints
2) Install Encryption Key and disable HTTP access
BRKEVT-2803
Cisco Public
19
MCU
VCS
VCS and MCU

Configuration Steps
3) Register the MCU to the VCS via H323 and/or SIP
Endpoints
4) Optional: Configure static conference and parameters
5) Call the conference ID and PIN or Auto Attendant
BRKEVT-2803
Cisco Public
20
Conferencing
Types of conferences 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.
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. 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.
VCS and MCU

Conferences
Conference Type Scheduled bridge Scheduling and Management Scheduled Options Using TMS either directly or via an integration, for instance with Microsoft Exchange
Conference Type Non Scheduled VCS

Ad hoc/Rendezvou s bridge
Options 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.
Note: Not recommended to mix scheduled and non scheduled for a single MCU. Better to dedicate a single MCU for each type of conference.
Refer to management breakout session, BRKEVT-2400 Scheduling Best Practices for Cisco Telepresence for more details
VCS and MCU

Conference scaling
MCU VCS
How do you increase scale?
Clustering
Signaling
Media
Endpoints
Up to 2 MCU 5300s per cluster
Cascading
Up to 3 blades per cluster
Cascade Speakers on Primary MCU Support H.323 cascading only Link Increases Port capacity of the conference
Requires video port on each MCU for Cascade
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
VCS and TS
Choice
TelePresence Server VCS
Can I use a TelePresence Server?
Form Factor Options Appliance - 7010

Signaling Media
MSE Blade - 8710

Endpoints
ActivePresence
*FullHD or HD resolution
24
Immersive Experience
* TS2.3 or below
VCS and TelePresence Server

Configuration
1) Change default password and add secondary admin account 2) Install Encryption Key and disable HTTP access 3) Set HD Mode (FullHD 1080p or HD 720p), enable 60fps
BRKEVT-2803
Cisco Public
25

Configuration
4) Register the TS to the VCS via H.323 and/or SIP
BRKEVT-2803
Cisco Public
26

Configuration
5) Configure conference and parameters
Note: Rendezvous Conferences Only
6) Call the conference ID and PIN


Conferences
Conference Type Scheduled bridge Scheduling and Management Scheduled Options Using TMS either directly or via an integration, for instance with Microsoft Exchange
Conference Type Non Scheduled VCS

Rendezvous bridge
Options Rendezvous - statically configured conference on a TelePresence Server Ad hoc not supported
Note: Not recommended to mix scheduled and non scheduled for a single MCU. Better to dedicate a single MCU for each type of conference.
Refer to management breakout session, BRKEVT-2400 Scheduling Best Practices for Cisco Telepresence for more details
VCS and TS
Conferences
TelePresence Sever VCS
How do you increase scale?
Clustering
Standalone Unit only

Signaling
Media
Add licenses up to 12
Endpoints
Cascading
Cascade Not supported configuration Link
Up to 4 blades per cluster
Slot 10 can not be used in a cluster
7010 - LIC-TPSRV-1SL
1 Full HD (1080p), 2 HD( 720p)
8710 - LIC-8710-1SL
1 Full HD (1080p), 2 HD( 720p)
MCU and TelePresence Server

What is the difference?
MCU 5300 (non Stacked) Form Factor Experience Layouts Capacity Appliance 50+ and customizable Up to 10 Full HD or 20 HD TelePresence Server 7010 Appliance 4 layout families Up to 12 Full HD or 24 HD MSE 8510 MSE 8000 blade 50+ and customizable Up to 15 Full HD MSE 8710 MSE 8000 blade 4 layout families Up to 12 Full HD or 24 HD
For Your Reference
Single Screen CP ActivePresence
Single Screen CP ActivePresence
Content Channels Up to Full HD
*Up to HD 30fps except for CTS, which is XGA@30fps

Stereo and Multichannel No No No Yes
Up to Full HD
*Up to HD 30fps, except for CTS, which is XGA@30fps

Stereo and Multichannel Yes, up to 4 No * Requires Conductor No Yes
Audio Clustering Cascading Auto Attendant Conference Pins

BRKEVT-2803
Mono Yes, up to 2 in a stack Yes, with other MCUs only Yes Yes
Mono Yes, up to 3 Yes, with other MCUs only Yes Yes
Cisco Public
30
Use Case 2
Campus
Unity Connection Multipoint
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
Unified Presence
Unified CM
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
BRKEVT-2803
Cisco Public
31
MCU
Unified CM and MCU

What conference bridge can I use?
Unified CM
Communications Manager New Video Deployment Single Screen Systems Ad hoc and Rendezvous Conferences Internal Video requirements High Bandwidth Available
BRKEVT-2803 2013 Cisco and/or its affiliates. All rights reserved.
Signaling Media API
Endpoints
MSE 8510 Blade
MCU 5300
Cisco Public
Unified CM
Terminology
5310 or 5320
Media Resource Group 1 Media Resource Group List Media Resource Group 2
Media Resource
Stack of two 5300s
Media Resource = Conference Bridge
8510 Media Resource Group List (MRGL) = Order List of MRGs
Media Resource Group
Media Resource 1 Media Resource 2 Media Resource 3
UK 5320
=
=
USA 5310 Japan 5320
Media Resource Group List
Device Pool
Media Resource Group (MRG) = List of Conference Bridges

BRKEVT-2803
MRGL are assigned to endpoints using Device Pools

Cisco Public 33
UCM configuration
Conference Bridge Setup Ad hoc 1. Add Conference Bridge
3. Add MRG to MRGL
2. Add Conference Bridge To MRG
4. Add MRGL to Device Pool
BRKEVT-2803
Cisco Public
34
UCM Configuration Video

Ad Hoc
UCM configuration
Conference Bridge Setup Rendezvous 1. Add SIP trunk to the Bridge
3. Add Add Route Groups to Route List
4. Add Route List for this Route Pattern 2. Add trunk to Route Group
BRKEVT-2803
Cisco Public
36
UCM Configuration Video

Rendezvous
Unified CM
Conference Bridge Connectivity
Requirements Supports Ad hoc and Rendezvous Conferences Requires UCM 8.6 or higher, UCM 9.0 for encrypted links MCU version 4.3 or higher Limitations Cascading not supported
BRKEVT-2803
Cisco Public
38
Unified CM and MCU

MCU Configuration
1) Change default password and add secondary admin account
2) Install Encryption Key and disable HTTP access

3) Enable Media Port Reservation
Guaranteed ports for the conference No Oversubscription allowed
4) Set the Incoming Calls to unknown conferences or Auto Attendants to Disconnect Caller.
Sets the default action when endpoints call into the MCU using a number that does not correspond to any configured conference.
Cisco Public 39
BRKEVT-2803
Unified CM and TS
Integration
TelePresence Server Unified CM
Can I use a TelePresence Server?
Technically Yes, but does not fit the use case requirements.
Ad hoc conferences are not supported Rendezvous conferences are supported Cascading not supported
Signaling Media API
Scheduling not supported by TMS

Endpoints
2013 Cisco and/or its affiliates. All rights reserved. Cisco Public 40
BRKEVT-2803
Use Case 3
Campus
Scheduling Conferencing Management
The Challenge
20,000 Users Remote workers on video Immersive experience required Redundancy with scale
Multipoint
Unity Unified Connection Presence
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
Unified CM
VCS
Internet Branch WAN
Teleworker
BRKEVT-2803
Cisco Public
41
Conductor Video
http://www.youtube.com/watch?v=4-C7F2fTEYE
What is this?
BRKEVT-2803
Cisco Public
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!
BRKEVT-2803
Cisco Public
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)
Virtualized Conductor
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
What does TelePresence Conductor do?

What does this mean? Conference Virtualization What does this mean? Resource Management/Confere nce Bridge Selection What does this mean?
Centralized Conference Provisioning and Administration
Consistent User Experience Whether using a Ad hoc Conferences or Rendezvous Conferences
Knows all the available and used ports Intelligent Bridge selection Automatic cascading of MCUs
Single configuration applied to any conferencing resource Ad Hoc and Rendezvous Conference support
BRKEVT-2803
Cisco Public
46
Conductor
Connectivity Points
Call Control VCS
NEW !
MCU Resource Pool

MCU 4200 Series MCU 4500 Series MCU 5300 Series MSE 8420 SD MCU MSE 8510 HD MCU
Cisco TelePresence Conductor

Conductor with UCM Support in XC2.0
NEW !
TelePresence Resource Pool

Registers to either, UCM preferred Endpoints Ad hoc Rendezvous
Conductor HW or VM TelePresence Server (TS 7010 & MSE 8710) Support in XC2.0 with TS 3.0
Management
Registration SIP Trunk XC2.0 or higher
Basic Conductor Scheduling Support in TMS14.1.1

BRKEVT-2803
Conductor Overview
Key Concepts
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 4. Conference bridge pool Grouping of conference bridges 5. Conference bridge Communication parameters to bridges 6. Auto Dialed Participant Dial string to add a device to the conference automatically
Unified CM
Terminology
Video Bandwidth Immersive Video Bandwidth
Locations
Between Locations
Locations = Bandwidth Management Locations is Call Admission Control (CAC)
Inside Locations
Locations
UCM locations are linked to Conductor configuration

Conductor and UCM

How does the model change?
Added B2BUA in Conductor Uses Multiple IP addresses Looks like MCU to UCM
BRKEVT-2803
Cisco Public
50
UCM and Conductor Configuration Video

Unified CM locations
Conductor
How it works Ad hoc
8710 TS
CUCM
Conductor
172.16.100.20 Management: Ad hoc: Rendezvous: 172.16.100.1 172.16.100.2 172.16.100.3
172.16.50.1
5300 MCU
172.16.100.50
SIP
HTTPs
Media
52
Note: ConductorBRKEVT-2803 does not cascade MCUs for ad hoc conferences. 2013 Cisco and/or its affiliates. All rights reserved.
Cisco Public
Conductor
How it works - Rendezvous
8710 TS
CUCM
Conductor
172.16.100.20 Management: Ad hoc: Rendezvous: 172.16.100.1 172.16.100.2 172.16.100.3
172.16.50.1
For simplicity only single call is shown
5300 MCU
172.16.100.50
SIP
HTTPs
Media
53
Note: Conductor can cascade rendezvous conferences only. All rights reserved. BRKEVT-2803 2013with Cisco MCUs and/or its affiliates.
Cisco Public
Scale Video
http://www.youtube.com/watch?v=lnZEMaSwAGU&feature=ghist&context=G2d6fc37AHT1dKagASAA
TelePresence Conductor
Specification
Maximum supported service and configuration
Services/Configuration
Utilised Conference Bridges Concurrent Active Conferences Preconfigured Conference Template
Parameter
30 MCUs or TelePresence Servers (2400 concurrent calls) 1,200 Conferences 1000 Conferences *1,000 Aliases 20,000 Users
Preconfigured Conference Aliases

Preconfigured Auto-dialed Participants
Preconfigured Auto-Dialed Participants per Conference Template
5,000 participants per conference template
NOTE: *A lecture (chair/guest) conference will require 2 conference templates (Lecturer and Participant).
BRKEVT-2803
Cisco Public
55
Conductor
Scale
In a single call
How many conference bridges have been tested?
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
VCS and/or Unified CM

BRKEVT-2803
*TS supports a maximum of 104 calls per cluster

TelePresence Server
Capacity Changes
TS 2.2
16 licenses
TS 2.3
12 licenses
TS 3.0
12 licenses
+
New Resource Optimization Model for main and content channel.
12
12
12
16
24
24
48
SD is less than 720P
4 extra licenses 8 extra HD screens New - SD support
Recovers unused DSP resources
Note: The numbers shown are for a single appliance or blade.

BRKEVT-2803
Cisco Public
57
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
TelePresence Server
Optimization of resources
Locally Managed mode
Without 12 Conductor
TS 3.0
Conductor 2.0
With Conductor
Once full, additional endpoints cannot join
22
Full HD
(1080p30)
BRKEVT-2803
HD
(720p30)
SD
(480p30)
Cisco Public 59
TelePresence Conductor configuration

Conference templates configuration
Create conference template for TelePresence Server
Select participant quality, Content Quality, Optimize Resources Maximum Video Quality
Full HD (1080p 30fps / 720p 60fps video, multichannel audio) HD (720p 30fps video, stereo audio) SD (wide 448p 30fps video, mono audio)
Reclaim Resources after 5 seconds
Maximum Content Quality Full HD (1080p 30fps / 720p 60 fps) HD (720p 30fps) 1280 x 720p 15fps 1280 x 720p 5fps Off Cisco Public
BRKEVT-2803
60
MSE 8710
Design Options
SD clusters Limited advantage above 2 blades No call increase after 3 blades Recommend Splitting blades Make two 2 blade clusters
Note: TS has a limitation of 104 calls
Cluster 1 96 Ports
Cluster 2 96 Ports
BRKEVT-2803
Cisco Public
61
Sizing and Licenses

TS 3.0 Release Note Charts
Cluster Size 1 Blade SD 48 SD Calls HD 24 HD Calls Full HD 12 FullHD Calls
How single screen endpoints with 1080p30 main video with 1080p30 content can I have in a single blade?
Main Video 480p30 480p30 720p30 1080p30 Audio Mono Stereo Stereo Stereo Content In main video 720p5 720p5 720p15 Screen Licenses 1/3 1
10 audio-only calls
2 Blade 96 SD Calls 8 audio-only calls 3 Blade 104 SD Calls
10 audio-only calls
48 HD Calls 20 audio-only calls 72 HD Calls 30 audio-only calls
10 audio-only calls
24 FullHD Calls 20 audio-only calls 36 FullHD Calls 30 audio-only calls 48 FullHD Calls 40 audio-only calls
720p60
1080p30 1080p30 Three-screen 1080p30 Three-screen 1080p30
Stereo
Stereo Stereo Multichannel Multichannel
720p15
720p30 1080p30 720p30 1080p30
1
1 2 3 4
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
Cisco Public 62
4 Blade
104 SD Calls
96 HD Calls 8 audio-only calls
Note: CTS/TX systems content channel supports up to XGA@30fps

Sizing and Licenses

Conductor
Conductor manages the licenses automatically.
Overall status of TS Encryption Key install on TS
Resource Allocation
BRKEVT-2803
Cisco Public
63
Putting the puzzle together

How do these part integrate?
TelePresence MCU TelePresence Conductor
TelePresence Server
Unified Communications Manager

Cisco Public 64
Use Case 3
Campus
Scheduling Conferencing Management
The Challenge
20,000 Users Remote workers on video Immersive experience required Redundancy with scale
Multipoint
Unity Unified Connection Presence
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
Unified CM
VCS
Internet Branch WAN
Teleworker
BRKEVT-2803
Cisco Public
65
Configurations
Steps for Conductor to Unified CM
VCS Unified CM
For Your Reference
Summary of Configuration Steps 1. Endpoints registered to VCS or UCM 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
Endpoints
MCU
TelePresence Server
6. Associate Conference Bridges to Pools, Service Preferences, and to a Templates 7.Create Conference Alias for Ad hoc calls.
BRKEVT-2803
Cisco Public
66
Supported Configurations
Clustering
Centralized Call Control
EMEA VCS Unified CM
Primary Ad hoc Rendezvous Ad hoc Primary Rendezvous Registration SIP Trunk
Design for primary conference connections from UCM are to separate Conductors
Synchronizes configuration parameters
Conductor1
Sync Configuration
Conductor2
MCU
TelePresence Server
MCU
TelePresence Server
Maximum of 3 Conductors in a cluster

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

With UCM Locations
Centralized Call Control
EMEA VCS Unified CM
Not Supported
Ad hoc Rendezvous Registration SIP Trunk

Breaks Location Model Conductor works with 1 cluster only
APAC Unified CM
Supported Design
North America
MCU
TelePresence Server
Cascade Link
Not Supported Cascade Breaks Location Model
MCU TelePresence Server MCU TelePresence Server
BRKEVT-2803
Cisco Public
68
Multiway Adhoc Conferencing

Ben
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
3-way call established on an MCU intelligently selected by TelePresence Conductor
An incoming call from a third person
VCS + Conductor
Two way call in progress
Activate MultiWay (press Join)
Unfied CM + Conductor
Original call on hold
Melissa
Katie
VCS Sip trunk to Unfied CM + Conductor
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
Different video services example with UCM
HD Endpoints VCS Unified CM
Ad hoc Rendezvous Registration SIP Trunk HD Resource Pool
TX9000 MCU Profile 55 TelePresence Server
EX90
SD Endpoints
VCS
Unified CM
SD Resource Pool
E20
MCU
TelePresence Server
9971
BRKEVT-2803 Note: TX9000 and 9971 only registers with UCM
Cisco Public
70
Different video services example with VCS
HD Endpoints VCS
Ad hoc Rendezvous Registration SIP Trunk HD Resource Pool
Profile 55 MCU TelePresence Server
EX90
SD Endpoints
VCS
SD Resource Pool
E20
MCU
TelePresence Server
9971
BRKEVT-2803
Cisco Public
71
Use Cases
Summary
MCU 5300 series Stack for increased scale
Use Case 2 Use Case 1
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
Use Case 3
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
BRKEVT-2803
Cisco Public
72
Reference Material
Conductor
Documentation
XC 2.0 Release notes
For Your Reference
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
BRKEVT-2803
Cisco Public
74
Conductor
Deployment Guides
Conductor with UCM
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
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
MCU and TelePresence Server

Deployment Guides
TelePresence MCU Deployment guide
For Your Reference
http://www.cisco.com/en/US/docs/telepresence/infrastructure/mcu/install_guide/Cisco_TelePresence_MCU_Deployment_guide_131.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
BRKEVT-2803
Cisco Public
76
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 Ciscos engineers at the Meet the Engineer center Discuss your projects challenges at the Technical Solutions Clinics
BRKEVT-2803
Cisco Public
77
BRKEVT-2803
Cisco Public
78

BRKEVT 2803 Multipoint Conference

Diunggah oleh

Informasi Dokumen

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

BRKEVT 2803 Multipoint Conference

Diunggah oleh

Hak Cipta:

Format Tersedia

BRKEVT-2803

Designing and deploying multipoint conferencing for telepresence video

2013 Cisco and/or its affiliates. All rights reserved.

2013 Cisco and/or its affiliates. All rights reserved.

2013 Cisco and/or its affiliates. All rights reserved.

TelePresence Architecture Overview

Global B2B InterNetwork

2013 Cisco and/or its affiliates. All rights reserved.

2013 Cisco and/or its affiliates. All rights reserved.

Conferencing Bridge Portfolio

MSE MCU 8420

MSE MCU 8510

MCU 4520 ISR G2

2013 Cisco and/or its affiliates. All rights reserved.

24ports at 720p30 or 12 ports at 1080p30

4501, 4505, 4510, 4515, 4520

6 to 40 ports at 720p30 3 to 20 ports at 1080p30 8510 80 ports at 480p30 15 ports at 1080p30

4203, 4205, 4210, 4215, 4220

SD is less than 720P

2013 Cisco and/or its affiliates. All rights reserved.

NOTE: 8710 and 8510 require the MSE 8000 chassis

TelePresence Server Overview

Unique Features Scalability

2013 Cisco and/or its affiliates. All rights reserved.

5300 or 8510 MCU

Unique Features Scalability

2013 Cisco and/or its affiliates. All rights reserved.

2013 Cisco and/or its affiliates. All rights reserved.

VCS and MCU

Newest hardware platform. (Released March 2012.)

MCU 5300 Port Counts

Ports activated per LIC-53004PL

Up to 1080p30 or 720p60 Up to 720p30, or w448p60 Up to w448p30 Up to w360p30

2013 Cisco and/or its affiliates. All rights reserved.

5300 Series Hardware features

Stacking connector on back 1 connector (only connect 2 together)

Special cable, Orderable with system or as Spare.

2013 Cisco and/or its affiliates. All rights reserved.

VCS and MCU

Stack of 5310 or 5320

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

VCS and MCU

1) Change default passwords and add secondary admin account

2) Install Encryption Key and disable HTTP access

2013 Cisco and/or its affiliates. All rights reserved.

VCS and MCU

4) Optional: Configure static conference and parameters

5) Call the conference ID and PIN or Auto Attendant

2013 Cisco and/or its affiliates. All rights reserved.

VCS and MCU

Conference Type Non Scheduled VCS

VCS and MCU

How do you increase scale?

Up to 2 MCU 5300s per cluster

Can I use a TelePresence Server?

Form Factor Options Appliance - 7010

MSE Blade - 8710

VCS and TelePresence Server

2013 Cisco and/or its affiliates. All rights reserved.

VCS and TelePresence Server

2013 Cisco and/or its affiliates. All rights reserved.

VCS and TelePresence Server

Note: Rendezvous Conferences Only

6) Call the conference ID and PIN