Preferred Architecture and Design

Sergio Aguilera – Consulting Systems Engineer

 Join me on
Spark
Agenda
• What is the Collaboration “Preferred Architecture”?
• Preferred Architecture Sub-Systems
• Call Control
• Bandwidth Management
• Conferencing
• Collaboration Edge
• Core Applications

• Simplified Sizing
• Key Takeaways and Q&A
What is “Preferred
Architecture”?
Collaboration Preferred Architecture Strategy
• Preferred Architecture provides prescriptive design guidance that simplifies
and drives design consistency for Cisco Collaboration deployments
• The Preferred Architecture is divided into five sub-systems
o Makes the overall architecture easier to understand
o Allows products to be categorised based on function

Sub-Systems:

Bandwidth Edge
Call Control Conferencing Applications
Management Services

Endpoints
Collaboration Solutions Design Guidance
Available at www.cisco.com/go/ucsrnd
Preferred Architecture Solution Reference Cisco Validated
Overview Network Design (SRND) Design (CVD)

Pre-Sales Pre-Sales Post-Sales

Process
• Design Overview Document
• Targeted to Pre-Sales
• What with some of the Why !
Process
• Detailed Design Guidance
• What and Why.
• Reference outside the scope of PA
process
• Detailed Deployment Guidance
• Targeted to Post-Sales
• What, Why, and How !
• Process Driven Guide
Call Control
 Headquarters
Prime Collaboration TelePresence
Deployment Management Suite Expressway-E

CUBE Cisco
WebEx
Unity Connection
Prime Licensing
Manager Applications
DMZ Mobile/Teleworker
Unified
Instant Message Communications Expressway-C
and Presence Manager
Internet

Integrated / Aggregated Third-Party Solution

Services Router PSTN
Call Control
Integrated
TelePresence Server Conductor Services Router
ISDN Video Gateway

MPLS WAN
Remote Site
Conferencing Collab Edge

Endpoints
Call Control – Cisco Unified Communications Manager
The Heart of Cisco Collaboration
Design Objectives
• Centralised Call Processing
• Centralised IM&P Services
• Consolidated Endpoint
Registration
Voice Video

IM / Presence Content Sharing

• Common feature set across
endpoints
CLOUD Cisco Unified • Central “Dial Plan” Authority
HYBRID Communications
ON PREMISES
Manager (CUCM) • High Availability and
Redundancy
Call Control with IM&P – Cluster Design
CUCM Cluster CUCM IM&P Cluster
DB Sync
Design Objectives
Publisher Sub-Cluster #1
• Call Processing and
Subscriber Pair #1 IM&P with 1:1
Publisher Subscriber Redundancy
SIP
TFTP Pair Sub-Cluster #2
Primary Secondary
CTI/QBE
• Single TFTP
Subscriber Pair #2 Subscriber Pair
SOAP API XML

MoH Pair
Publisher Subscriber • Single MoH
Primary Secondary Sub-Cluster #3 Subscriber Pair
…
Subscriber Pair #8

Up to Publisher Subscriber
21 Nodes Primary Secondary Up to 6 Nodes
Dial Plan
What is a Dial Plan About?
Design Objectives
• Endpoint Addressing
• Dialing Habits
• Call Routing
• Directory Integration
Directory
• Class of Services (CoS) - Restrictions
Mobile

+61 2 6216 0600 Voicemail

User Input
Mapping
Call Routing
(Transformations)

Restrictions
Endpoint Addressing
Publisher
DN: +61 2 6216 0600
TFTP Pair Subscriber Pair #1
Primary Secondary
DN: +61 7 3238 1111 Subscriber Pair #2
SIP URI: tracy@company.com.au MoH Pair
Primary Secondary
Design Objectives
• Use fully qualified E.164
Number with leading “+”
as Directory Numbers
(DN)
• Provision up to five (5)
alphanumeric SIP URIs
as aliases to primary DN

CUCM Cluster

DN: +61 3 9659 XXXX

SIP URI: mel-mx800@company.com.au
mel-carlton@company.com.au
Dialing Habits – Numbering Example
Site +E.164 Abbr. Intra- Abbr. Inter- Call CMR
Site1 Site2 Park3 (Conferencing)4
CBR +61 2 6216 XXXX 6XXXX 86XXXX 4XXX 88XXXXX
BNE +61 7 3238 XXXX 7XXXX 87XXXX 4XXX 88XXXXX
MEL +61 3 9659 XXXX 3XXXX 83XXXX 4XXX 88XXXXX

1. Abbreviated Intra-site – Site specific short dial plan mapping to +E.164

2. Abbreviated Inter-site – Use Intra-Site Code + Abbr. Intra-site Number
3. Call Park – Single (Global) call park range
4. Conferencing – Single (Global) CMR range
CUCM Call Routing Logic
• CUCM matches the most specific pattern – Longest-match logic
• Directory Numbers (DNs) act as a ‘route pattern’ that matches a single number
• For more information on CUCM routing logic, refer to the Collaboration SRND:
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/srnd/collab11/collab11/dialplan.html

Route Patterns
User Dials 1XXX
“1200”
12XX

User Dials *.com

peter@company.com.au
company.com.au
DNs
User Dials
“65872” 65872
Route / SIP Pattern – Example
User dials a
DN or URI Cisco Unified CM selects the best
pattern match

(SIP) Route
Pattern

Route List

start with the 1st RG an continue to

1st Choice 2nd Choice
hunt through the Route List

Route Route
Group 1 Group 2
Trunks or Gateways within the Route
Top down or Top down or Group are selected based on a top
circular circular down or circular rotation

PSTN PSTN
SIP Trunk SIP Trunk
Gateway Gateway
Directory Integration
Design Objectives
• Integrate into organisation's corporate LDAP directory to enable:
o User Provisioning
o User Authentication

o Contact Source – Jabber

• Manage User Parameters

o User ID

o First Name & Last Name

o Telephone Number (E.164 format)

o SIP URI
Directory Integration – User Synchronisation
Class of Service (CoS)
Design Objectives
• Classes of Service (CoS)
are used to control access
to “Services”
• Minimise number of
differentiated Classes of
Service (CoS)
• Define CoS in CUCM
using:
o Partitions
o Calling Search Spaces
(CSS)
SIP Trunking
SIP Trunks – Why are they important ?
Unity
Connection
CUBE

SIP Trunks are used to

Applications Mobile/Teleworker communicate with other
CUCM
Expressway-E
components in PA, such as:
Internet
• Cisco Unity Connection
DMZ
Third-Party Solution
(CUC) – Voicemail Application
Call Control
• Conductor – Conferencing
PSTN
Conductor • CUBE – SIP PSTN Gateway
Expressway-C • Expressway – B2B Calls
• External Video Gateways
TelePresence Server

ISDN Video Gateway

Collab Edge
Conferencing

SIP TDM
SIP Trunk Recommendations
Design Objectives
• Minimise number of SIP profiles
o Consider default profiles first
o Provision SIP profile per group of
equivalent trunks
• Recommended SIP profile
settings:
o Set “Use Fully Qualified Domain
Name in SIP Requests” on all
trunks
o Enable “SIP OPTIONS Ping” for
real-time status monitoring
o Enable “Best Effort” Early Offer
Support
Use of FQDN in SIP Requests – Example
10.10.10.1 10.10.10.2

INVITE bob@company.com.au INVITE bob@company.com.au

RPID: sip:alice@company.com.au RPID: sip:alice@company.com.au
(“Fully Qualified…” turned on) Bob
-or-
INVITE bob@company.com.au
RPID: sip:alice@10.10.10.1
(“Fully Qualified…” turned off)

180 Ringing 180 Ringing

RPID: bob@company.com.au RPID: bob@company.com.au
Alice (“Fully Qualified…” turned on)
-or-
180 Ringing
RPID: sip:bob@10.10.10.2
(“Fully Qualified…” turned off)
Bandwidth Management
Evolution of Collaboration Landscape
On-premise Call Control 1. Fixed, Hardware-Based
UC Services Endpoints
2. Managed networks
Central
Site

Cloud Services
B2B
QoS- 1. Mobile, Software-Based
Endpoints
capable 2. Unmanaged networks
B2C
Managed
WAN Internet
MPLS DMVPN
VPN

Remote Sites Home/Mobile Users

 Bandwidth Management – Design Objectives
Profiling and Prioritisation “Smart” Media Techniques Admission Control
LTRF1 LTRF1

P5 P5
P1 P3 P1
P2 P4 P2 P4
... ... ... ...
Encoder Decoder
?
OOS (P4) ACK LTRF1

Encoder Decoder

LTRF 0111010001
1000011001
R1 FEC

Repair-P R1 0001100
1001000100
0011001011
1011110
FEC
1110010101

... ... R2 1011010010

1010010

R2

• Consolidate mechanisms to
identify and classify
collaboration media
• Simplify policies for Queuing
and Scheduling
• Build a Self-Regulating
• Use Media Resilience to
system supporting supporting
reduce impact of packet loss
“Opportunistic Video”
• Apply Rate Adaptation to
• Use Call Admission Control
reduce network congestion
(CAC) as last option
Bandwidth Management – “Smart” Media Techniques
Media Adaptation and Resilience Implementation (MARI)
Goals Mechanisms

Make network congestion Media Resilience

less likely to occur Encoder Packet
Pacing
Gradual Decoder
Refresh (GDR)

Recover more efficiently LTRF with Repair

from packet loss
FEC

Optimise use of available

network resources Rate Adaptation

ClearPath Whitepaper - http://www.cisco.com/c/dam/en/us/td/docs/telepresence/endpoint/software/clearpath/clearpath_whitepaper.pdf

SRND Bandwidth Management Section - http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/srnd/collab11/collab11/cac.html
Bandwidth Management – Traffic Flow Identification
Cisco Jabber Example

• Jabber classification based on

UDP Ports DSCP UDP port ranges and ACL’s:
o Audio streams of all calls (voice-
17xxx – 20xxx EF only and video) marked EF
21xxx – 24xxx AF42
Ingress
1 o Video streams of Jabber video
Policy calls marked AF42
5061 CS3
ACL • Clients enabled for RTCP to
avoid lip-sync issues
Bandwidth Management – Queuing and Prioritisation
AF41 WRED thresholds
(i.e., drop AF41 last)
• Audio/EF is mapped to the
Audio of priority queue
IP Phones EF
o Includes audio streams from video
EF PQ endpoints and Jabber clients (voice-
Audio of only and video calls)
Video EF
• Video streams of video calls

BW Assigned to LLQ Classes

Audio of EF
Jabber (AF41) and video streams of
Jabber calls (AF42) are mapped
to the same CBWFQ
AF41
Video of
Video
Video
CBWFQ
• WRED is configured on the
video queue:
Video of o min-max thresholds for AF42:
Jabber AF42 ~10% - ~30% of queue limit
o min-max thresholds for AF41:
~45% - 100% of queue limit
queues

AF42 WRED thresholds

other

(i.e., drop AF42 first)

Conferencing
 Headquarters
Prime Collaboration TelePresence
Deployment Management Suite Expressway-E

CUBE Cisco
WebEx

Prime Licensing Unity Connection

Manager Applications
DMZ Mobile/Teleworker
Unified
Instant Message Communications Expressway-C
and Presence Manager
Internet

Integrated / Aggregated Third-Party Solution

Services Router PSTN
Call Control
Integrated
TelePresence Server Conductor Services Router
ISDN Video Gateway

MPLS WAN
Remote Site
Conferencing Collab Edge

Endpoints
Conferencing – Design Objectives
Flexible Architectures to support various conference types such as:
Ad-hoc (Instant), Rendezvous (Permanent) and Scheduled

Dynamic Optimisation of conferencing resources leveraging

TelePresence Conductor and TelePresence Server

Simplified Conferencing Experience leveraging

TelePresence Management Suite (TMS)

Resiliency – High Availability (HA) for all conferencing components

TelePresence Server Platforms
TelePresence Server on TelePresence Server on
VMWare (TRC & Specs Based) VMWare
Appliances Blade

8-core MM410v
Rack-Mount MM310

1 to 10 ports at 720p 1 to 12 ports at 720p

1 to 54 ports at 720p
MM820
1 to 24 ports at 720p per cluster

MM410v MM320 1 to 60 ports at 720p per blade

30vCPU Blade Server 1 to 120 ports at 720p per cluster

1 to 24 ports at 720p
1 to 48 ports at 720p per cluster
1 to 20 ports at 720p

1 to 54 ports at 720p per blade

1 to 432 ports at 720p per chassis

Note: For simplicity, only capacity for 720p is shown. TS is capable of many other resolutions and frame rates with differing limits on capacity.
All numbers represent remotely managed mode (Conductor required) capability. See release notes for further detail.
Telepresence Server Multistream – User Experience
Dual Screen Systems
• Provides “People +
People” Experience
Single Screen System
• Supports “Active Without Multistream
Presence” Experience Without Multistream

With Multistream
With Multistream
TelePresence Conductor – What is it used for ?
• Conference Virtualisation
• Resource management for greater scale
• Intelligent bridge selection and Automatic Cascading for large conferences
• Centralised Conference provisioning and administration

Shared
multipoint
resources

Allows multipoint resources to be Central point of management

shared for ad-hoc, rendezvous for all conferencing needs
and scheduled conferences
Optimised Resource
Management
Conductor and CUCM
How Does The Model Change?

• Emulates MCU API, looks Uses Multiple IP addresses (65 Max.)

Conference Bridge in UCM configuration like MCU to UCM • Management IP
• Utilises B2BUA • Location specific IPs
• Accepts SIP Signalling • IP address for Instant Meetings
• IP address for Personal CMR

Added Conductor

Individual
SIP trunk in UCM configuration
bridges
 TelePresence Management Suite (TMS)

TelePresence Management Suite

Core Platform (TMS)
o Scheduling
o Phonebooks
TelePresence Management Suite
Cisco Provisioning Extension (TMSPE)
TMS Core o Smart Scheduler
Platform o Personal Meeting Room Provisioning
TelePresence Management Suite
Extension for Microsoft Exchange (TMSXE)
o Schedule Meetings via Microsoft Outlook
 TelePresence Management Suite (TMS) Architecture
Active Nodes
TMSXE TMS/TMSPE

• TMS in active/passive
mode
Network Load • External SQL Server used
Balancer
Scheduling Single virtual by both TMS nodes
request IP address
Exchange Active
Servers SQL Directory address for • TMSPE is co-resident with
management
TMS
• TMSXE must be deployed
separately

TMSXE TMS/TMSPE

Passive Nodes
TelePresence Multiparty Licensing Overview
TelePresence Conductor
TMS/PE
All Multiparty Licenses
TelePresence Servers
All resources available for any meeting
• Conductor centrally manages licenses for all
TelePresence Servers (TS)
o Screen Licenses no longer required on individual TelePresence
Servers
• Two types of multiparty licenses are supported:
o Personal Multiparty (PMP)
o Shared Multiparty (SMP) – Can be used for Room-Based
Systems or Sharing amongst users
• TMS-PE provides license provisioning interface
• Ad-hoc (Instant), Rendezvous (Permanent) or Scheduled
conferences with unlimited participants (up to TS
capacity) Minimum Requirements:
Conductor 4.0 (posted 2nd Sept ‘15)
• Benefits:
TMS 15.0 (posted 2nd July ‘15)
o Full access to all TS resources TMSPE 1.5 (posted 3rd Sept ‘15)
o Simplify TS deployment TS 4.2 (posted 28th August ‘15)
Call Flow – Ad-hoc (Instant) Conference

TelePresence
Endpoint creates TelePresence
Unified CM initiates Unified CM routes Conductor routes
an instant Conductor creates
an instant the call(s) to the call(s) to the
conference the conference on
conference on TelePresence TelePresence
requesting to join a TelePresence
Conductor Conductor Server hosting the
three participants Server
relevant conference

Other
Participants

Unified CM TelePresence Server

Host (UCM) Conductor (TS)

Instant conference Instant conference initiated Conductor creates

request by UCM conference on TS

UCM routes call(s) to Conductor routes call(s)

Conductor to TS
Call Flow – Rendezvous (Permanent) Conference
TelePresence
Unified CM routes TelePresence
Endpoint dials a Unified CM matches Conductor matches
the call to Conductor routes
permanent the dialed string to a the called number
TelePresence the call to the
conference alias (SIP) route pattern to an alias and
Conductor via SIP TelePresence
(URI or DN) or route string creates a
trunk Server
conference on TS

Unified CM TelePresence Server

Host Conductor
(UCM) (TS)

Alias matched Alias matched on Conductor

Dial conference alias UCM routes call to Conductor creates conference on TS

(URI or DN) Conductor
Participants
Conductor routes call to TS

Dial conference alias UCM routes call to Conductor routes call to TS

Conductor

Dial conference alias UCM routes call to Conductor routes call to TS

Conductor
Call Flow – Scheduled Conference
Unified CM routes
User schedules
TMS uses APIs to Conductor uses call to Conductor
conference using User dials the alias
create a conference APIs to create a (dial-in, OBTP) or
Smart Scheduler. or Conductor dials
on Conductor at the conference on the Conductor dials out
User is notified of out to the user
time requested chosen TS to the user via
the meeting details
Unified CM
Collaboration Meeting
Rooms (CMRs)
Collaboration Meeting Rooms Deployment Options

Cisco® CMR Premises Cisco CMR Hybrid Cisco CMR Cloud

Cisco TelePresence® video Cisco TelePresence video Hosted by a Cisco WebEx

infrastructure on premises infrastructure on premises meeting application
at customer data centre plus Cisco WebEx® meeting
applications
CMR Premises Architecture Requirements:
Conductor 4.0 (posted 2nd Sept ‘15)
TMS 15.0 (posted 2nd July ‘15)
TMSPE 1.5 (posted 3rd Sept ‘15)
CUCM
TS 4.2 (posted 28th August ‘15)

• Conductor provisioning API utlisised

for conference setup and
configuration
Cisco TMS

TelePresence • Easy provisioning and configuration

Conductor
of Personal Collaboration Meeting
Rooms (CMRs) via TMSPE
• Personalise CMR on Self-Care
Instant and Personal Scheduled
Portal
TelePresence Server TelePresence
Pool Server Pool
• Each CMR has an associated video
SIP Media+Content HTTP(s) address (DN or URI) that is
integrated into CUCM’s dial plan
Personal CMR Provisioning
CMR Template Configuration on TMS
This template will be
created on Conductor
by TMS

Service Preference on
Conductor for this
template

PMP or SMP

Alias generated from

AD username
Number generated
from AD telephone
number

Note: CMR Template

configuration cannot be
modified from Conductor UI.
Personal CMR – Customisation
CMR Hybrid Architecture

• Integrate on-premise video

Unified CM with WebEx participants

Expressway-C Expressway-E
• Require a certificate signed
Internet by a trusted Root Certificate
Conductor
Authority on Expressway-E
• Supports WebEx, PSTN or
Cisco TMS
TSP audio options
• Supports Scheduled or
TelePresence
Server Pool Non-Scheduled
Conferences
SIP Media+Content HTTP(s)

Cisco Collaboration Meeting Rooms (CMR) Hybrid Configuration Guide

 CMR Cloud Architecture
• Conference Resources and
Unified CM
Infrastructure reside in WebEx
Cloud
Expressway-C Expressway-E

Internet • Requires on-premise CUCM

for call control and Expressway
for B2B calls
• Each CMR has an associated
video address (DN or URI) and
URL
• Supports WebEx, PSTN or
SIP Media+Content
TSP audio options

Cisco Collaboration Meeting Rooms (CMR) Cloud Deployment Guide

 Choosing the Right Option
Guidance for Conferencing Focused Customers
Cloud On-Prem
1 • WebEx or Spark 2 • Multiparty Licensing 3 • Rich Skype for Business
customer (S4B) conferencing
• CMR Premises or interoperability
• Greenfield Hybrid Customers
conferencing • Public Sector: JITC and
• Ad-hoc escalation FIPS Certifiations
• CMR Cloud Interop
including Skype for • Multistream, Active • Scalable on premise
Business (S4B) Control and Triple Audio and Video
Screen Support conferencing

Spark & WebEx Conferencing TP Server (Multiparty Licensing) Acano + CUWL (Optional)
Collaboration Edge
 Headquarters
Prime Collaboration TelePresence
Deployment Management Suite Expressway-E

CUBE Cisco
WebEx
Unity Connection
Prime Licensing
Manager Applications
DMZ Mobile/Teleworker
Unified
Instant Message Communications Expressway-C
and Presence Manager
Internet

Integrated / Aggregated Third-Party Solution

Services Router PSTN
Call Control
Integrated
TelePresence Server Conductor Services Router
ISDN Video Gateway

MPLS WAN
Remote Site
Conferencing Collab Edge

Endpoints
Cisco Collaboration Edge Architecture Components
• Cisco Expressway
Expressway-E
o Business-to-Business (B2B)
o Mobile and Remote Access
Cisco
(MRA) WebEx
CUBE
o External IM&P Federation
(XMPP)
DMZ Mobile/Teleworker
• Gateways
Expressway-C Internet
o SIP-based PSTN Connectivity –
Cisco Unified Border Element
(CUBE) Integrated/Aggregated Third-Party Solution
Services Router PSTN
o TDM-Based PSTN Connectivity
– Integrated Services Router Integrated
Services Router
(ISR) ISDN Video Gateway

o ISDN Video Gateway – ISDN MPLS WAN

3241 and MSE 8321 (Blade) Remote Site
Collab Edge
Business-to-Business
Communications
Expressway Firewall Traversal Basics
Enterprise Network DMZ Outside Network

Unified Internet
CM
Expressway-C Firewall Expressway-E Firewall
Signaling
Media

1. Expressway-E is the traversal server installed in DMZ. Expressway-C is the traversal client installed inside the
enterprise network.
2. Expressway-C initiates traversal connections outbound through the firewall to specific ports on Expressway-E with
secure login credentials.
3. Once the connection has been established, Expressway-C sends keep-alive packets to Expressway-E to maintain the
connection
4. When Expressway-E receives an incoming call, it issues an incoming call request to Expressway-C.
5. Expressway-C then routes the call to Unified CM to reach the called user or endpoint
6. The call is established and media traverses the firewall securely over an existing traversal connection
 B2B Calls Flow Example DNS
Hierarchy
SIP-to-SIP Calls

Expressway-C

Forward SIP Invite to companyB.com.au

CUCM using IP address received via DNS
Remote Edge1

Expressway-E Sends SIP 200 OK

Calls
user_y@companyB.com.au
Internet
Remote Edge2
user_x@companyA.com.au
COMPANY A
COMPANY B

Note: 1 Traversal Server 2 Traversal Client user_y@companyB.com.au

B2B Calls
Media Encryption

Applies to Neighbour, DNS, Traversal

and Default Zones* on Expressway-C
and Expressway-E Expressway-C

• Encryption Modes:
Expressway-E
o Force encrypted
o Force unencrypted
o Auto: Dependent on endpoint request
o Best Effort: will fall back to unencrypted if encryption is not available
• SIP: Media encryption mode can be configured
• H.323: Does not work with “forced encrypted” or “force unencrypted”
o Separate H.323 from SIP traversal zones if “force encrypted” is to be configured
* For Expressway zone type descriptions, refer to the “Zones and Neighbours” section of the Cisco Expressway Administrator Guide
B2B Call Media Encryption Example Inbound zone
Mixed Encryption Settings
Default Zone
Expressway-C Expressway-E
Not configurable
CM Neighbor Traversal Traversal Auto
Zone Client Zone Server Zone
TLS TLS TLS Outbound zone
Best Effort Force encr Force encr
DNS Zone
Not configurable
Best Effort
Internet RTP
TLS/SRTP TLS/SRTP TCP/RTP
Remote
• “Best Effort” and “Force Encrypted” will engage B2BUA on Edge
Expressway-C and Expressway-E
• Third media leg between Expressway-E and Remote Edge falls back to unencrypted
since Remote edge does not support encryption
• Lock icon shows closed only if all the call legs are encrypted with the exception of the
Remote Edge to endpoint call leg
Mobile and Remote
Access
Mobile and Remote Access (MRA) Overview
• Secure VPN-Less access for Jabber Clients and Hardware-Based Endpoints

Inside firewall DMZ Outside firewall

(Intranet) (Public Internet)
78xx / 88xx DX Endpoints EX Endpoints
IP Phones
CUCM
Collaboration Internet
Services Jabber
Jabber
Desktop
Mobile
CUCM IM&P Expressway-C Expressway-E
Unity Connection

Conferencing
MX Endpoints SX Endpoints

Mobile Users. Teleworkers

MRA – Split DNS SRV Record Requirements
• _collab-edge record needs to be available in public DNS
• Multiple SRV records (and Expressway-E hosts) should be deployed for HA
• A GEO DNS service can be used to provide unique DNS responses by
geographic region
_collab-edge._tls.example.co.nz SRV 10 10 8443 expwy1.example.co.nz
_collab-edge._tls.example.co.nz SRV 10 10 8443 expwy2.example.co.nz

• _cisco-uds record needs to be available only in internal DNS

_cisco-uds._tcp.example.co.nz SRV 10 10 8443 ucm1.example.co.nz.

_cisco-uds._tcp.example.co.nz SRV 10 10 8443 ucm2.example.co.nz.
MRA – Jabber Service Discovery Example

DNS SRV lookup _cisco-uds._tcp.example.co.nz

Inside firewall DMZ Outside firewall
(Intranet) (Public Internet)

✗ Not Found
CUCM
Collaboration DNS SRV lookup _collab-edge._tls.example.co.nz
Services Public DNS

✓ expwyAKL.example.co.nz
CUCM IM&P
Expressway-C Expressway-E
Unity Connection

Conferencing
TLS Handshake, trusted certificate verification
HTTPS:
get_edge_config?service_name=_cisco-
uds&service_name=_cuplogin
Voice and Video
Gateways
Voice and Video Gateways Portfolio
ISR 4451-X

ISR 4431 ASR 1004/6 RP2

3900 E-Series ISR-G2 ASR 1002-X

(3925E, 3945E)
CSR1000v
ASR 1001-X (vCUBE)
ISR 4351

3900 Series ISR-G2

(3925, 3945)
SIP-Only (CUBE) Voice Gateways
ISR-4K (4321, 4331)

TelePresence ISDN
2900 Series ISR-G2 GW MSE 8321
(2901, 2911, 2921, 2951)

TelePresence
800/1861 ISR ISDN GW 3241

Analog, Digital and SIP (CUBE) TelePresence ISDN Gateways

Voice Gateways
Voice and Video Gateways Recommendations
Deployment Best Practices
• TelePresence Video Gateways • PSTN Connectivity
o Deploy dedicated ISDN Video Gateways o Central Site TDM-Based
Deploy ISR router with ISDN
ISR / ASR (CUBE)
Primary Rate (PRI) modules
o Central Site SIP Trunk-Based
Deploy ISR or ASR router in
DMZ DMZ and enable Cisco Unified
Internet
ISR / ASR Router
Border Element (CUBE)
Third-Party Solution
PSTN
functionality
o Remote Sites
ISDN Video Gateway ISR Router
MPLS WAN Deploy ISR router with Analog or
ISDN Basic / Primary (BRI/PRI)
Central Site
Remote Site Rate modules
Core Applications
 Headquarters

Prime Collaboration TelePresence

Management Suite Expressway-E
Deployment

CUBE Cisco
WebEx

Prime Licensing Unity Connection

Manager
Applications
DMZ Mobile/Teleworker
Unified
Instant Message Communications Expressway-C
and Presence Manager
Internet

Integrated / Aggregated Third-Party Solution

Services Router PSTN
Call Control
Integrated
TelePresence Server Conductor Services Router
ISDN Video Gateway

MPLS WAN
Remote Site
Conferencing Collab Edge

Endpoints
Core Applications
Key Benefits
» Cisco Unity Connection enables voicemail and unified messaging
across a wide-range of end-user platforms

» Cisco Prime Collaboration Deployment (PCD) eases deployment of new

infrastructure components, enabling faster initial setup

» Cisco Prime Licensing Manager (PLM) single tool to enable license

workflows and manage licensing for collaboration infrastructure
components.
Core Applications – Cisco Unity Connection (CUC)
Architecture Overview
Directory
• Redundant Unity Connection nodes
Unity Connection
Publisher Directory
synchronisation LDAP
• SIP Trunk integration to Unified CM
Unified CM
• Integrations to directory and e-mail:
Messaging
» LDAP Directory
Subscriber (On-Premise or
Cloud-Based)
» Microsoft Exchange
Mailbox
SIP synchronization
Microsoft • Voicemail Access via
Exchange
Voicemail access o Telephone User Interface (TUI)
Via TUI, VUI or
Visual Voicemail o Voice User Interface (VUI)
o Visual Voicemail
Email access to
voicemail • Email access to voicemail (Single Inbox /
(Single Inbox) Unified Messaging (UM))
TUI, VUI or Email
SIP (SMTP/HTTPS)
REST/HTTPS
Core Applications – Prime Collaboration Deployment
Design Objectives
CM_Pub IM&P_Pub UCXN_Pub
VM VM VM
• Simplify CUCM, CUCM IM&P and
VMWare
CM_Sub IM&P_Sub UCXN_Sub CUC deployments by enabling
EXSi
VM VM VM automated, unattended installation of
host CM_Sub IM&P_Sub server nodes
VM VM
• Facilitate configuration of common
network and security settings.

.iso
.iso
.iso

•
Prime Collaboration Deployment (PCD) •
x
x
• x
• x
Core Applications – Prime Licensing Manager (PLM)
Architecture Overview
Unified CM Unity Connection
• Cisco Prime License Manager (PLM)
enables license fulfilment:

Publisher
» Electronic [requires Internet connectivity]
Publisher
OR
» Manual license file request

• Licenses received (over the network or via

email)
• Licenses applied to system and
Cisco.com propagated to synchronised application
Prime License instances.
Manager
Simplified Sizing
Preferred Architecture (PA) Simplified Sizing

• The Cisco Preferred Architecture for Enterprise

Collaboration Cisco Validated Design (CVD)
presents some examples that simplify the sizing
process
• Refer to the latest Enterprise Collaboration CVD at
http://www.cisco.com/go/cvd/collaboration
Traditional Sizing for Cisco Collaboration
Collaboration Sizing Tool (CST)
http://tools.cisco.com/cucst
PA Simplified Sizing vs Collaboration Sizing Tool
Deployment within the
PA Sizing Assumptions?

Use PA Use Collaboration

Simplified Sizing Sizing Tool
Key Takeaways
• The Collaboration Preferred Architecture (PA) helps Customers and Partners
understand the overall Collaboration Architecture and its components
• The Collaboration Preferred Architecture (PA) provides general design best
practices and follows a modular, prescriptive approach to simplify deployments
• The Collaboration Preferred Architecture (PA) provides simplified sizing options
for typical deployments and is built to scale.
• For deployments outside of the Preferred Architecture (PA), refer to the
Collaboration Solution Reference Network Design (SRND) guide.
• For detailed deployment guidance (“the how”), refer to the Enterprise
Collaboration Cisco Validated Design (CVD).
 Continue the Conversation using Cisco Spark
• Sign up free for Cisco Spark at http://www.ciscospark.com/
• Download the application from iOS App Store, Google Play Store,
or from http://download.ciscospark.com/
• Visit https://spark.aguilera.com.au/brkcol-2101 or use the QR Code
to join the CLMEL16 BRKCOL-2101 Spark room and continue the
conversation
 Collaboration Track at Cisco Live MELBOURNE
Track Session ID Date Time Title
Video BRKEVT-2665 9th March 2016 8:30 AM Designing for Video in Every Workspace
BRKUCC-2666 9th March 2016 2:30 PM Enabling Federation and External Collaboration with Expressway
BRKUCC-2664 10th March 2016 8:30 AM Directories Services and Single Sign-On for Collaboration
BRKCOL-2616 10th March 2016 12:50 PM Enabling Quality of Service with Cisco SDN
BRKUCC-2676 11th March 2016 8:45 AM Upgrading and Migrating to Cisco Unified Communications Manager
BRKUCC-2480 9th March 2016 12:50 PM Jabber Everywhere Deploying the Best Experience
BRKCOL-2101 9th March 2016 8:30 AM Preferred Architecture and Design
Unified Communications
BRKUCC-2008 10th March 2016 8:30 AM Leveraging SIP to Simplify Dial Plans Both Inside and Outside the Enterprise
Deploying SIP Trunks with Cisco Unified Border Element (CUBE/vCUBE)
BRKUCC-2006 11th March 2016 2:00 PM Enterprise
BRKUCC-2042 10th March 2016 2:30 PM Securing Unified Communications and Certificate Deep Dive
BRKUCC-3662 11th March 2016 2:00 PM Troubleshooting Jabber Like a TAC Engineer
BRKCOL-2020 10th March 2016 8:30 AM Cisco Unified Communications and Microsoft Integrations
BRKCCT-2059 11th March 2016 2:00 PM Designing Cisco Contact Centres for Medium to Large Enterprises
BRKCCT-2019 10th March 2016 12:50 PM Designing and Deploying Contact Centre Express
Contact Centre
BRKCCT-2663 10th March 2016 2:30 PM Customising your Contact Centre with Finesse and CUIC
BRKCCT-2661 10th March 2016 4:30 PM Recording and Video Enabling the Contact Centre
BRKUCC-1661 8th March 2016 2:00 PM Introduction to Collaboration Anywhere
BRKUCC-2671 10th March 2016 4:30 PM Cisco Collaboration Enabling Workspace Transformation
BRKCOL-2778 9th March 2016 2:30 PM Evolution of Collaboration Protocols
Collaboration BRKUCC-2677 10th March 2016 12:50 PM Designing Collaboration Meeting Rooms
Accelerate and Assure Collaboration Deployments with Cisco Prime
BRKUCC-2670 11th March 2016 8:45 AM Collaboration
BRKCOL-2010 8th March 2016 4:00 PM Understanding Cisco and Apple Integration
BRKUCC-2675 9th March 2016 4:30 PM Understanding Cisco Cloud and Hybrid Collaboration
Cloud BRKCOL-2070 9th March 2016 12:50 PM Cloud Based Unified Communications for Small Business
BRKCOL-2620 10th March 2016 2:30 PM Deploying Hybrid Conferencing and Cloud Connected Audio
Q&A
Complete Your Online Session Evaluation
Give us your feedback and receive a
Cisco 2016 T-Shirt by completing the
Overall Event Survey and 5 Session
Evaluations.
– Directly from your mobile device on the Cisco Live
Mobile App
– By visiting the Cisco Live Mobile Site
http://showcase.genie-connect.com/ciscolivemelbourne2016/
– Visit any Cisco Live Internet Station located
throughout the venue
Learn online with Cisco Live!
T-Shirts can be collected Friday 11 March Visit us online after the conference
for full access to session videos and
at Registration presentations.
www.CiscoLiveAPAC.com
Thank you
Appendix
 Call Control
Multi-Cluster Considerations
 Multi-Cluster Scenario Design Objectives
• Multi-Cluster model is based on
Cluster #1 multiple iterations of the
CUCM CUCM IM&P Centralised Call Processing Model
CUCM
• Consider Multiple Clusters due to
Publisher the following:
Subscriber Subscriber Publisher
Pair Publisher Subscriber • Administrational Separation
Pair • Geographic Footprint
CUCM IM&P • Deploy SIP Trunk Full Mesh to
Cluster #2
avoid session traversal through
CUCM CUCM IM&P
individual clusters
Subscriber
Publisher • Leverage Inter-cluster Lookup
Publisher
Subscriber Subscriber
Cluster #N
Service (ILS) for
Pair Publisher
• SIP URI Replication
• Directory Number (DN) replication via
Global Dial Plan Replication (GDPR)
SIP ILS XMPP
Call Control – Call Routing
Local Route Group (LRG)
• LRG introduced with Unified CM 7.0
• Concept: move the site specific egress gateway selection policy from the route
pattern to the calling devices’ device pool
• “Standard Local Route Group” used as placeholder in route list definition
• Dynamically replaced with route group configured on calling device’s device pool when
routing the call
• Allows for site un-specific route patterns  route pattern count reduction
• Restriction pre 10.0: we only have single LRG
• What if we want to use LRG based egress GW selection, but e.g. need to
differentiate between emergency calls and ‘regular’ PSTN calls?
Call Control – Base Configuration
FQDN Processnode References
• All nodes of a cluster are managed under “System/Server”
• Options:
• IP address
• Hostname (no domain)
• Fully Qualified Domain Name (FQDN, includes DNS domain portion)

• Processnode references exposed to external entities

• Endpoint configuration files (Unified CM groups for registration)
• UDS service discovery
• ...
FQDN Processnode References
Why not IP addresses?
• IP address processnode references are used by Jabber to build HTTPS URLs to accesss
services
• Certificate validation during TLS connection setup
• Validity: validity period
• Trust: direct (imported into trust store) or indirect (certificate issued from trusted CA)
• Identity: subject of the certificate (or subject alternate name) needs to match the intended
communication peer

• Final identity check fails if host connects to an IP address, because cert subjects
(typically) are domain names
• Certificates with IP address subject alternate name not an option
• CA validation of IP addresses questionable
• Incorrect treatment of IP address SANs by some browsers

• IP address processnode references cause Jabber certificate validation to fail

FQDN Processnode References
Why not Hostnames ?

• Exposed hostnames need to get fully qualified by clients

• Which domain should be used?
• Presence domain?
• Domain learned by client via DHCP?

• What if the customer has site with multiple DNS domains?

• domain learned by client via DHCP: cbr.company.com.au
• DNS domain of Unified CM cluster: uc-cluster.company.com.au
• Problem: client uses wrong FQDN to connect to servers
FQDN Processnode References
FQDN is the best solution

• Pros:
• Solves certificate validation problems
• Solves multi-domain problems

• Cons:
• Creates DNS dependency
• DNS becomes critical foundation service for UC

• Recommendation: set server names (Unified CM admin GUI under

System/Server) to FQDNs!
Enterprise Parameters
Recommended Settings
• Global settings determining fundamental behaviour of CUCM

• Identification
• Cluster ID: unique cluster identification
• Service URLs: make sure that URLs refer to FQDNs

• Call Routing
• URI Lookup Policy: RFC 3261 URI case sensitivity
• set to “Case Insensitive”
• Organisation Top Level Domain (OTLD): routing of numeric SIP URIs
• set to main domain, e.g. “company.com.au”
• Cluster Fully Qualified Domain Name (CFQDN): routing of numeric SIP URIs
• space separated list of all Unified CM nodes in the cluster
• Wildcarded if all cluster members are in same domain/zone (example: *.us-
cluster.company.com.au)
Always Set CFQDN and OTLD

• Set OTLD to match single(!) corporate domain name

• Make sure to set the CFQDN to match host names of all cluster nodes
• DNS naming structure might help
• e.g.: *.anz-cluster.company.com.au for pub. anz-cluster.company.com.au, sub1.anz-
cluster.company.com.au , …
• Keep in mind that fallback routing based on RHS is implemented for:
• Alpha URIs not found locally
• Numeric URIs with RHS = OTLD not found in numeric lookup
Call Control – DNS Requirements
DNS Requirements
• Jabber certificate validation requires DNS for UC services
• Recommendation:
• Enable DNS forward (A record) and reverse (PTR record) lookup for all UC servers
• Potentially zone per cluster:
• pub.anz-uc.example.org
• tftp1.anz-uc.example.org
• tftp2.anz-uc.example.org
• sub1a.anz-uc.example.org
• sub1b.anz-uc.example.org
• Dedicated zone for cluster simplifies configuration of cluster fully qualified domain name
(CFQDN):
• *.anz-uc.example.org
DNS for UDS Based Service Discovery
• DNS SRV records are required for Jabber service discovery
• On-prem service discovery looks for _cisco-uds._tcp.company.com.au
• Recommendation:
• SRV record for each Unified CM subscriber
• Best load balancing of initial UDS requests during registration

• DNS SRV load balancing only used for intial UDS request.
• Further UDS requests are load balanced by Jabber over all UDS nodes in
cluster learned from UDS
• Example:
_cisco-uds._tcp.company.com.au 86400 IN SRV 10 10 8443 sub1a.anz-uc.company.com.au
_cisco-uds._tcp.company.com.au 86400 IN SRV 10 10 8443 sub1b.anz-uc.company.com.au
_cisco-uds._tcp.company.com.au 86400 IN SRV 10 10 8443 sub2a.anz-uc.company.com.au
_cisco-uds._tcp.company.com.au 86400 IN SRV 10 10 8443 sub2b.anz-uc.company.com.au
Call Control – Certificate Management
Certificate Requirements
Base Concepts

• Certificate exchange part of TLS connection setup

Serial
• Certifcate Validity: expiration date, signature valid? Signature
• Certificate Trust: is the signing entity trusted? Issuer
• Self-signed certs: import cert into trust store Subject
• Issuing CA trusted Validity
• Identity: does the certificate identity match the Subject Public Key
identity of the intended communication peer?
Jabber Certificate Validation
• Required Certificates
• Unified CM IM&P: Tomcat, XMPP
• Unified CM: Tomcat, CallManager
• Unity Connection: Tomcat
• WebEx Meetings Server: Tomcat

• Options:
• Users ignore certificate validation pop-ups and accept certs  invalidates security
concepts
• Install above certificates in the Enterprise Trust store of all clients
• Use CA (public/private) issued certificates: only trust with CA has to be established
Certificate Recommendations
• CA issued certificates simplify the deployment
• With self-signed certificates to establish trust all certificates have to be cross-imported
or deployed to clients via GPO
• Use multi-server certificates to minimise the management overhead
• Private CA avoids policy constraints of public CAs; e.g. single certificate per
FQDN
Bandwidth Management
 Bandwidth Management – Traffic Flow Identification
CUCM Service Parameters and SIP Profile Configuration

System  Service Parameters  Cisco CallManager Service Device  Device Settings  SIP Profile
Conferencing
Conductor Platforms

Variant Conductor Clustering Capacity TAC Support

Free TelePresence
Conductor [Essentials]
(VM only)
 1 x standalone TS
NO
(Use communities & forums)

Mid-Market TelePresence 30 x standalone or clustered

Conductor [Select]
(VM only)
 (up to 2) TS
(50 Call sessions)
YES

Full TelePresence 30 x standalone or clustered

Conductor
(VM only)
(up to 3) TS
(2400 Call sessions)
YES

• Ability to upgrade from Free Conductor -> Midmarket Conductor -> Full Conductor
• Same software shared across all variants. Option keys used to differentiate types of Conductor.
 TelePresence Conductor
Configuration Concepts

Conductor Unified CM Conductor Virtual IP Address

Conf. Alias Route Pattern

Location
Service Route List/MRGL
Preference
Conference Alias (not needed for instant conferences)
Conf. Bridge Route Group/MRG
Pool
Conference Template
Conf. Bridge Conference Bridge

Service Preference (can be used in multiple Conference Templates)

#1 Pool TS TS
(can be used in
multiple SP’s)
TS TS
Prioritised
#2 Pool TS TS
 Conductor Clustering
Unified CM Instant Conductor
Media Resource Group
Conductor 1
Media Bridge1 10.1.1.1 10.1.1.1

Media Bridge2 10.1.2.1

10.1.1.2 • 65 IP addresses per
Conductor server
• Up to 3 nodes in a cluster
Permanent
Conductor 2
Trunk • Up to 30 bridges per cluster
10.1.2.1
Trunk IP1 10.1.1.2 • Max RTT of 30 ms between
cluster nodes
Trunk IP2 10.1.2.2 10.1.2.2
 Conductor Clustering
Unified CM Instant Conductor
Media Resource Group
Conductor 1
Media Bridge1 10.1.1.1 10.1.1.1

Media Bridge2 10.1.2.1

10.1.1.2 • 65 IP addresses per
Conductor server
• Up to 3 nodes in a cluster
Permanent
Conductor 2
Trunk • Up to 30 bridges per cluster
10.1.2.1
Trunk IP1 10.1.1.2 • Max RTT of 30 ms between
cluster nodes
Trunk IP2 10.1.2.2 10.1.2.2
Conductor – Instant Conference Configuration
Unified CM Conductor

Template

Service
Preference
MRGL

Pool
MRG

Endpoint Media TelePresence

Location TelePresence
Bridge Server
Servers
Conductor – Permanent Conference Configuration
SIP
Unified CM Conductor
Route Alias
Pattern

Route
Pattern

Route
Template
List

Route Service
Group Preference

SIP Pool
Location
Trunk
Endpoint

TelePresence
TelePresence
Server
Servers
Mobile and Remote
Access
 MRA – Protocol Workload Summary

Inside firewall DMZ Outside firewall

(Intranet) (Public Internet)
Protocol Security Service
SIP TLS Session Establishment – Register,
CUCM
Invite, etc.
Collaboration
RTP SRTP Media – Audio, Video and Content
Services Internet Sharing

CUCM IM&P HTTPS TLS Logon, Provisioning/Configuration,

Expressway-C Expressway-E Contact Search, Visual Voicemail
Unity Connection
XMPP TLS Instant Messaging, Presence
Conferencing
 MRA Global Deployment Topology & Geo DNS
DNS SRV lookup
_collab-edge._tls.example.com Geo DNS

expwy.us.example.com expwy.jp.example.com
US Europe Asia SIP Trunk
expwy.uk.example.com
SIP Line

Expressway
Expressway Traversal
edge access
Asia SME
SME global EU SME
aggregation US SME

Unified CM
regional
clusters RTP PAR LON TKY
CBR BGL

DFW AMS HKG

Voice and Video
Gateways
Centralised IP PSTN Access With Local GW As Backup
Calling Search Space
CBRInternational Device LRG_PSTN1 LRG_PSTN2
Pool
Partition PSTNInternational CUBE1
CBRPhone CUBE_AUS_PSTN GW_CBR_PSTN

Device Pool set to MELPhone CUBE_AUS_PSTN GW_MEL_PSTN

CBRPhone
Route Pattern \+! Route List RL_PSTN

Phone in CBR PSTNInternational

LRG_PSTN_1

LRG_PSTN_2
Calling Search Space
MELInternational
CBR_GW
Route Group Trunk
Partition PSTNInternational
GW_CBR_PSTN Trunk_To_CBR_GW
Device Pool set to
GW_MEL_PSTN Trunk_To_MEL_GW
MELPhone MEL_GW

Phone in MEL First choice for CBR users Backup for CBR users

First choice for MEL users Backup for MEL users

Core Applications
 Cisco Unity Connection – Design Considerations

• Unity Connection Cluster Deployment (publisher + subscriber)

Sub Pub
» Nodes: Must be the same OVA size and integrate to the same Unified CM cluster.
X » Connectivity: Maximum RTT = 150 ms. For every 50 voice messaging ports 7 Mbps of
bandwidth is required.

• Unified CM Integration
» Dual SIP trunks, route group with ‘Top Down’ algorithm for call routing: Unity Connection
subscriber 1st (primary), publisher 2nd (backup).
» Visual Voicemail – UC Service: Set the Unity Connection publisher as the primary
voicemail service and subscriber as the secondary service within the UC service profile.

• Capacity Planning
» Reserve 20% of total system ports for dial out/non-answering operations (message
notification, MWI, etc.)
 Refer to the
Core Applications – Deployment Overview CVD

1. Provision the Unity Connection Cluster – Deploy two node cluster for high availability

Alternatively » Determine OVA configuration size (based on number of users) and network and security parameters for
use Prime each node (hostname, IP address/mask, default gateway, DNS, NTP, username/password, etc.).
Collaboration
Deployment » Deploy/install publisher, add subscriber details under cluster configuration, then deploy the subscriber.
2. Configure Unified CM for Unity Connection Integration – Configure SIP trunks, call routing, and
voicemail settings for integration to Unity Connection cluster.
» Configure two SIP trunks (one per Unity Connection node) and call routing constructs (Route Pattern/List/
Group).
» Configure voicemail constructs (Voicemail Pilot number, MWI on/off, Voicemail Profile).
3. Unity Connection Base Configuration – Configure Unity Connection to enable Unified CM
integration, user provisioning, and voicemail capabilities.
» Configure phone systems settings, ports (port codec, port groups), and call routing to enable integration
with Unified CM.
» Enable directory sync with Active Directory and configure templates for user provisioning of mailboxes
and self enrollment.
 Refer to the
CVD
Core Applications – Deployment Overview
4. Enable Single Inbox – Unified messaging feature enabling synchronisation of voice messages

in Unity Connection with user’s Microsoft Exchange mailbox.
» Configure Unified Messaging Services account and role in Active Directory/Exchange, and configure Unity
Connection settings (SMTP, authentication method/protocol, and user enablement).
» Install ViewMail for Outlook (available at Cisco.com), configure email account and Unity Connection server.
5. Enable Visual Voicemail – Provide visual access to voicemail boxes for listing and playing messages
» Configure appropriate Unity Connection settings: Class of service (CoS) and API options settings
» On Unified CM configure voicemail UC service for each Unity Connection node and add the services to a
UC Service Profile.
6. Voicemail in SRST Mode – Configure branch ISRs with SRST to route calls to Unity Connection voicemail
system via PSTN when IP WAN is down.
» Configure call forward no answer/busy and POTS dial-peer to route calls via the PSTN to Unity Connection.
» Ensure Redirected Dialed Number Information Service (RDNIS) is configured and carrier propagates so that
callers are directed to the appropriate voicemail box rather than the automated attendant prompt.
7. HTTPS Interworking of two or more Unity Connection Clusters – Configure HTTPS networking to
enable directory information sharing and message exchange between multiple clusters.
Simplified Sizing
Simplified Sizing – Additional Tools
Virtual Machine Placement Tool (VMPT)

http://www.cisco.com/go/vmpt
Simplified Sizing – Additional Tools
Cisco UC Virtualisation DocWiki

http://docwiki.cisco.com/wiki/Unified_Communications_in_a_Virtualized_Environment
 Simplified Sizing – Additional Tools
Collaboration Design Zone
• Cisco Collaboration Solutions Design Guidance:
http://www.cisco.com/go/ucsrnd
» Cisco Collaboration Systems 10.x Solution Reference Network Designs (SRND)
» Cisco Collaboration Systems 11.0 Solution Reference Network Designs (SRND)

• Cisco Enterprise Preferred Architecture:

http://www.cisco.com/go/cvd/collaboration
» Cisco Preferred Architecture for Enterprise Collaboration, Design Overview
» Cisco Preferred Architecture for Enterprise Collaboration, CVD
Q&A
Complete Your Online Session Evaluation
Give us your feedback and receive a
Cisco 2016 T-Shirt by completing the
Overall Event Survey and 5 Session
Evaluations.
– Directly from your mobile device on the Cisco Live
Mobile App
– By visiting the Cisco Live Mobile Site
http://showcase.genie-connect.com/ciscolivemelbourne2016/
– Visit any Cisco Live Internet Station located
throughout the venue
Learn online with Cisco Live!
T-Shirts can be collected Friday 11 March Visit us online after the conference
for full access to session videos and
at Registration presentations.
www.CiscoLiveAPAC.com
Thank you