preferred architecture and designd2zmdbbm9feqrf.cloudfront.net/2016/anz/pdf/brkcol-2101.pdf ·...

Preferred Architecture and DesignSergio Aguilera – Consulting Systems Engineer

• 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

AgendaJoin me on

Spark

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:

Endpoints

Call Control ConferencingEdge

ServicesApplications

Bandwidth

Management

Post-Sales

processPre-Sales

Process

Collaboration Solutions Design Guidance

Preferred Architecture

Overview

Cisco Validated

Design (CVD)

• Design Overview Document

• Targeted to Pre-Sales

• What with some of the Why !

• Detailed Deployment Guidance

• Targeted to Post-Sales

• What, Why, and How !

• Process Driven Guide

Available at www.cisco.com/go/ucsrnd

• Detailed Design Guidance

• What and Why.

• Reference outside the scope of PA

Pre-Sales

Process

Solution Reference

Network Design (SRND)

http://www.cisco.com/go/ucsrnd

Call Control

Prime Collaboration Deployment

Applications

Unity Connection

TelePresenceManagement Suite

Prime Licensing Manager

Third-Party Solution

Internet

MPLS WAN

Remote Site

Mobile/Teleworker

PSTN

Integrated Services Router

WebExCisco

Conferencing

TelePresence Server Conductor

Endpoints

Collab Edge

Integrated / Aggregated Services Router

DMZ

Expressway-E

ISDN Video Gateway

CUBE

Expressway-C

Headquarters

Instant Message and Presence

Unified Communications

Manager

Call Control

Design Objectives

• Centralised Call Processing

• Centralised IM&P Services

• Consolidated Endpoint Registration

• Common feature set across endpoints

• Central “Dial Plan” Authority

• High Availability and Redundancy

IM / Presence

VideoVoice

Content Sharing

CLOUD

ON PREMISES

HYBRID

Cisco Unified

Communications

Manager (CUCM)

Call Control – Cisco Unified Communications ManagerThe Heart of Cisco Collaboration

Publisher Subscriber

Sub-Cluster #3


Sub-Cluster #2

Subscriber Pair #2

Primary Secondary

Call Control with IM&P – Cluster Design

DB Sync

CUCM Cluster CUCM IM&P Cluster

SIP

Up to 21 Nodes

CTI/QBE

SOAP API XML

…

Subscriber Pair #1

Primary Secondary

Subscriber Pair #8

Primary Secondary

MoH Pair

TFTP Pair

Publisher


Sub-Cluster #1

Up to 6 Nodes

Design Objectives

• Call Processing and IM&P with 1:1 Redundancy

• Single TFTP Subscriber Pair

• Single MoH Subscriber Pair

Dial Plan

Call Routing

Directory

+61 2 6216 0600User Input Mapping

(Transformations)

Mobile

Voicemail

Restrictions

Design Objectives

• Endpoint Addressing

• Dialing Habits

• Call Routing

• Directory Integration

• Class of Services (CoS) - Restrictions

What is a Dial Plan About?

Endpoint Addressing

Subscriber Pair #2

Primary Secondary

Subscriber Pair #1

Primary Secondary

MoH Pair

TFTP Pair

Publisher

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

DN: +61 7 3238 1111SIP URI: [email protected]

DN: +61 2 6216 0600

DN: +61 3 9659 XXXXSIP URI: [email protected]

[email protected]

CUCM Cluster

mailto:[email protected]



Dialing Habits – Numbering Example

Site +E.164 Abbr. Intra-

Site1

Abbr. Inter-

Site2

Call

Park3

CMR

(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

65872

DNs

12XX

*.com

company.com.au

User Dials “1200”

User Dials [email protected]

User Dials “65872”

1XXX

http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/srnd/collab11/collab11/dialplan.html


Route / SIP Pattern – Example

User dials a

DN or URI

start with the 1st RG an continue to

hunt through the Route List

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

1st Choice 2nd Choice

Route List

SIP Trunk SIP TrunkPSTN

Gateway

PSTN

Gateway

Route

Group 2

Route

Group 1

Top down or

circular

Top down or

circular

Cisco Unified CM selects the best

pattern match

(SIP) Route

Pattern

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

Conferencing

TelePresence Server

Conductor

CUCM

Call Control

Applications

Unity Connection

Collab Edge

Internet

PSTN

DMZ


Mobile/Teleworker

Expressway-E

ISDN Video Gateway

CUBE

Expressway-C

SIP TDM

SIP Trunks – Why are they important ?

SIP Trunks are used to communicate with other components in PA, such as:

• Cisco Unity Connection (CUC) – Voicemail Application

• Conductor – Conferencing

• CUBE – SIP PSTN Gateway

• Expressway – B2B Calls

• External Video Gateways

SIP Trunk RecommendationsDesign 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 OfferSupport

Use of FQDN in SIP Requests – Example

INVITE [email protected]

RPID: sip:[email protected]



(“Fully Qualified…” turned on)

-or-



(“Fully Qualified…” turned off)

180 Ringing

RPID: [email protected]

180 Ringing

RPID: [email protected]

(“Fully Qualified…” turned on)

-or-

180 Ringing


(“Fully Qualified…” turned off)

Alice

10.10.10.210.10.10.1

Bob


sip:[email protected]








Bandwidth Management

Evolution of Collaboration Landscape

1. Fixed, Hardware-Based

Endpoints

2. Managed networks

1. Mobile, Software-Based

Endpoints

2. Unmanaged networks

Call Control

Remote Sites

Central

Site

On-premiseUC Services

MPLSVPN

Cloud Services

ManagedWAN Internet

DMVPN

B2B

B2C

Home/Mobile Users

QoS-capable

Bandwidth Management – Design Objectives

“Smart” Media TechniquesProfiling and Prioritisation

• Use Media Resilience to reduce impact of packet loss

• Apply Rate Adaptation to reduce network congestion

• Consolidate mechanisms to identify and classify collaboration media

• Simplify policies for Queuing and Scheduling

...

?

P1

LTRF1

P2P3

P4

P5

... ...

P1

LTRF1

P2 P4

...Encoder Decoder

P5

ACK LTRF1OOS (P4)

R2...

LTRF

Repair-P

...

Encoder Decoder

0111010001

1000011001

0001100

1110010101

1011010010

1010010

1001000100

0011001011

1011110

R1 FEC

FECR1

R2

Admission Control

• Build a Self-Regulatingsystem supporting supporting “Opportunistic Video”

• Use Call Admission Control (CAC) as last option

Bandwidth Management – “Smart” Media TechniquesMedia Adaptation and Resilience Implementation (MARI)

Make network congestion less likely to occur

Recover more efficiently from packet loss

Optimise use of available network resources

Goals

Media ResilienceEncoder Packet

PacingGradual Decoder

Refresh (GDR)

LTRF with Repair

FEC

Rate Adaptation

Mechanisms

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

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

http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/srnd/collab11/collab11/cac.html

Bandwidth Management – Traffic Flow IdentificationCisco Jabber Example

• Jabber classification based on UDP port ranges and ACL’s:

o Audio streams of all calls (voice-only and video) marked EF

o Video streams of Jabber video calls marked AF42

• Clients enabled for RTCP to avoid lip-sync issues

5061

UDP Ports

17xxx – 20xxx

21xxx – 24xxx

ACL

AF42

CS3

DSCP

EF

Ingress

Policy1

Bandwidth Management – Queuing and Prioritisation

PQ

Audio of IP Phones

oth

er

qu

eu

es

EF

AF41

Audio of Video

Video of Video

Video

CBWFQ

BW

Assig

ned

to L

LQ

Cla

sses

EF

AF42

Audio of Jabber

Video of Jabber

AF41 WRED thresholds(i.e., drop AF41 last)

AF42 WRED thresholds(i.e., drop AF42 first)

EF

EF

• Audio/EF is mapped to the priority queueo Includes audio streams from video

endpoints and Jabber clients (voice-only and video calls)

• Video streams of video calls (AF41) and video streams of Jabber calls (AF42) are mapped to the same CBWFQ

• WRED is configured on the video queue:o min-max thresholds for AF42:

~10% - ~30% of queue limit

o min-max thresholds for AF41: ~45% - 100% of queue limit

Conferencing


Applications

Unity ConnectionPrime Licensing

Manager


Internet

MPLS WAN

Remote Site

Mobile/Teleworker

PSTN


WebExCisco

Endpoints

Collab Edge


DMZ

Expressway-E

ISDN Video Gateway

CUBE

Expressway-C

Headquarters


Call Control

Conferencing



Manager


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

Appliances Blade

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 on VMWare (TRC & Specs Based)

8-core

1 to 10 ports at 720p

30vCPU


TelePresence Server on

VMWare

MM410v

Rack-Mount


1 to 54 ports at 720p per blade

1 to 432 ports at 720p per chassis

MM410v

Blade Server

MM310


1 to 24 ports at 720p per cluster

MM320



1 to 60 ports at 720p per blade


MM820

Telepresence Server Multistream – User Experience

Dual Screen Systems

• Provides “People + People” Experience

Single Screen System

• Supports “Active Presence” Experience Without Multistream

With Multistream

Without 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

shared for ad-hoc, rendezvous

and scheduled conferencesOptimised Resource

Management

Central point of management

for all conferencing needs

Conductor and CUCMHow Does The Model Change?

Added Conductor

Uses Multiple IP addresses (65 Max.)

• Management IP

• Location specific IPs

• IP address for Instant Meetings

• IP address for Personal CMR

• Emulates MCU API, looks

like MCU to UCM

• Utilises B2BUA

• Accepts SIP Signalling

Conference Bridge in UCM configuration

Individual bridges

SIP trunk in UCM configuration

TelePresence Management Suite

Extension for Microsoft Exchange (TMSXE)o Schedule Meetings via Microsoft Outlook


Provisioning Extension (TMSPE)o Smart Schedulero Personal Meeting Room Provisioning

Cisco

TMS Core

Platform


Core Platform (TMS)o Schedulingo Phonebooks

TelePresence Management Suite (TMS)

TelePresence Management Suite (TMS) Architecture

• TMS in active/passive mode

• External SQL Server used by both TMS nodes

• TMSPE is co-resident with TMS

• TMSXE must be deployed separately

Active Nodes

Passive Nodes

TMS/TMSPE

TMS/TMSPETMSXE

TMSXE

Exchange

Servers

Scheduling

request

Network Load

BalancerSingle virtual

IP address

address for

managementSQL

Active

Directory

TelePresence Multiparty Licensing Overview• 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)

• Benefits:

o Full access to all TS resources

o Simplify TS deployment

TMS/PE

TelePresence Conductor

All Multiparty Licenses

TelePresence Servers

All resources available for any meeting

Minimum Requirements:

Conductor 4.0 (posted 2nd Sept ‘15)

TMS 15.0 (posted 2nd July ‘15)

TMSPE 1.5 (posted 3rd Sept ‘15)

TS 4.2 (posted 28th August ‘15)

Call Flow – Ad-hoc (Instant) Conference

TelePresence Conductor routes the call(s) to the TelePresence

Server hosting the relevant conference

Unified CM routes the call(s) to


TelePresence Conductor creates the conference on

a TelePresence Server

Unified CM initiates an instant

conference on Conductor

Endpoint creates an instant

conference requesting to join three participants

Instant conference request

Instant conference initiated by UCM

Conductor creates conference on TS

UCM routes call(s) to Conductor

Conductor routes call(s) to TS

HostUnified CM

(UCM) ConductorTelePresence Server

(TS)

Other Participants

Call Flow – Rendezvous (Permanent) Conference

TelePresence Conductor routes

the call to the TelePresence

Server

TelePresence Conductor matches the called number

to an alias and creates a

conference on TS

Unified CM routes the call to

TelePresence Conductor via SIP

trunk

Unified CM matches the dialed string to a (SIP) route pattern

or route string

Endpoint dials a permanent

conference alias (URI or DN)

Dial conference alias(URI or DN)

UCM routes call toConductor

Conductor creates conference on TS

Conductor routes call to TS

HostUnified CM

(UCM)Conductor

TelePresence Server (TS)

Alias matched Alias matched on Conductor

Conductor routes call to TSDial conference alias

Participants

UCM routes call toConductor

Conductor routes call to TSDial conference alias UCM routes call toConductor

Call Flow – Scheduled Conference

Unified CM routes call to Conductor

(dial-in, OBTP) or Conductor dials out

to the user via Unified CM

User dials the alias or Conductor dials

out to the user

Conductor uses APIs to create a

conference on the chosen TS

TMS uses APIs to create a conference on Conductor at the

time requested

User schedules conference using Smart Scheduler. User is notified of

the meeting details

Collaboration Meeting Rooms (CMRs)

Collaboration Meeting Rooms Deployment Options

Cisco TelePresence® video

infrastructure on premises

at customer data centre

Cisco® CMR Premises

Hosted by a Cisco WebEx

meeting application

Cisco CMR Cloud

Cisco TelePresence video

infrastructure on premises

plus Cisco WebEx® meeting

applications

Cisco CMR Hybrid

+

CMR Premises Architecture

• Conductor provisioning API utlisisedfor conference setup and configuration

• Easy provisioning and configuration of Personal Collaboration Meeting Rooms (CMRs) via TMSPE

• Personalise CMR on Self-Care Portal

• Each CMR has an associated video address (DN or URI) that is integrated into CUCM’s dial plan

CUCM

Scheduled TelePresence Server Pool


Instant and Personal TelePresence Server

Pool

Cisco TMS

SIP Media+Content HTTP(s)

Requirements:

Conductor 4.0 (posted 2nd Sept ‘15)

TMS 15.0 (posted 2nd July ‘15)

TMSPE 1.5 (posted 3rd Sept ‘15)

TS 4.2 (posted 28th August ‘15)

This template will be created on Conductor by TMS

Service Preference on Conductor for this template

Alias generated from AD username

Number generated from AD telephone number

Note: CMR Template configuration cannot be modified from Conductor UI.

PMP or SMP

Personal CMR ProvisioningCMR Template Configuration on TMS

Personal CMR – Customisation

CMR Hybrid Architecture

• Integrate on-premise video with WebEx participants

• Require a certificate signed by a trusted Root Certificate Authority on Expressway-E

• Supports WebEx, PSTN or TSP audio options

• Supports Scheduled or Non-Scheduled Conferences

Unified CM

TelePresence Server Pool

Expressway-C Expressway-E

Conductor

Cisco TMS

Internet

SIP Media+Content HTTP(s)

Cisco Collaboration Meeting Rooms (CMR) Hybrid Configuration Guide

http://www.cisco.com/c/en/us/support/conferencing/telepresence-management-suite-tms/products-installation-and-configuration-guides-list.html

CMR Cloud Architecture

Unified CM


Internet

SIP Media+Content

• Conference Resources and Infrastructure reside in WebEx Cloud

• 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 TSP audio options

Cisco Collaboration Meeting Rooms (CMR) Cloud Deployment Guide

http://www.cisco.com/c/en/us/support/conferencing/webex-meeting-center/products-installation-and-configuration-guides-list.html

On-Prem

Spark & WebEx Conferencing

Cloud

1 2 3

Choosing the Right OptionGuidance for Conferencing Focused Customers

• Rich Skype for Business (S4B) conferencing interoperability

• Public Sector: JITC and FIPS Certifiations

• Scalable on premise Audio and Video conferencing

• WebEx or Spark customer

• Greenfield conferencing

• CMR Cloud Interop including Skype for Business (S4B)

• Multiparty Licensing

• CMR Premises or Hybrid Customers

• Ad-hoc escalation

• Multistream, Active Control and Triple Screen Support

Acano + CUWL (Optional)TP Server (Multiparty Licensing)

Collaboration Edge


Applications

Unity Connection




Internet

MPLS WAN

Remote Site

Mobile/Teleworker

PSTN


WebExCisco

Conferencing




Manager

Call Control

Headquarters

Endpoints

Collab Edge


DMZ

Expressway-E

ISDN Video Gateway

CUBE

Expressway-C

Cisco Collaboration Edge Architecture Components


WebExCisco

Collab Edge

Internet

MPLS WAN

Remote Site

Mobile/Teleworker

PSTNIntegrated/Aggregated

Services Router


DMZ

Expressway-E

ISDN Video Gateway

• Cisco Expressway

o Business-to-Business (B2B)

o Mobile and Remote Access (MRA)

o External IM&P Federation (XMPP)

• Gateways

o SIP-based PSTN Connectivity –Cisco Unified Border Element (CUBE)

o TDM-Based PSTN Connectivity – Integrated Services Router (ISR)

o ISDN Video Gateway – ISDN 3241 and MSE 8321 (Blade)

CUBE

Expressway-C

Business-to-Business Communications

DMZEnterprise Network

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

Unified

CM

Firewall Expressway-E FirewallExpressway-C

Internet

Outside Network

Media

Signaling

Expressway Firewall Traversal Basics

DNSHierarchy

[email protected]

Expressway-C

Expressway-ECalls [email protected]

Forward SIP Invite to companyB.com.au using IP address received via DNS

Sends SIP 200 OK

COMPANY B

Internet

COMPANY A

[email protected]

B2B Calls Flow Example SIP-to-SIP Calls

Note: 1 Traversal Server 2 Traversal Client

Remote Edge1

CUCM

Remote Edge2

• Encryption Modes:

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

Expressway-E

Expressway-C

B2B Calls Media Encryption

Applies to Neighbour, DNS, Traversal and Default Zones* on Expressway-Cand Expressway-E

* For Expressway zone type descriptions, refer to the “Zones and Neighbours” section of the Cisco Expressway Administrator Guide

http://www.cisco.com/c/en/us/support/unified-communications/expressway-series/products-maintenance-guides-list.html

• “Best Effort” and “Force Encrypted” will engage B2BUA on 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

B2B Call Media Encryption Example Mixed Encryption Settings

CM Neighbor

Zone

Best Effort

TLS

Traversal

Client Zone

Force encr

TLS

Traversal

Server Zone

Force encr

TLS

Default Zone

Auto

Not configurable

DNS Zone

Best Effort

Not configurable


TLS/SRTP TLS/SRTP TCP/RTP

Inbound zone

Outbound zone

RTP

Remote Edge

Internet

Mobile and Remote Access

Mobile and Remote Access (MRA) Overview

• Secure VPN-Less access for Jabber Clients and Hardware-Based Endpoints

Inside firewall (Intranet)

Collaboration

ServicesInternet

DMZ

Expressway-EExpressway-C

CUCM

Outside firewall(Public Internet)

CUCM IM&P

Unity Connection

Conferencing

Jabber

DesktopJabber

Mobile

78xx / 88xx

IP PhonesDX Endpoints

MX Endpoints SX Endpoints

Mobile Users. Teleworkers

EX Endpoints

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

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

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


Collaboration

Services

CUCM

Public DNS

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

Not Found ✗

expwyAKL.example.co.nz✓

TLS Handshake, trusted certificate verification

DNS SRV lookup _collab-edge._tls.example.co.nz


DMZ

HTTPS:

get_edge_config?service_name=_cisco-

uds&service_name=_cuplogin


MRA – Jabber Service Discovery Example

CUCM IM&P

Unity Connection

Conferencing

Voice and Video Gateways

Voice and Video Gateways Portfolio

Analog, Digital and SIP (CUBE)

Voice Gateways

2900 Series ISR-G2 (2901, 2911, 2921, 2951)

3900 Series ISR-G2 (3925, 3945)

3900 E-Series ISR-G2 (3925E, 3945E)

800/1861 ISR

ISR 4451-X

ISR 4431

ISR-4K (4321, 4331)

ISR 4351

TelePresence ISDN GW 3241

TelePresence ISDN GW MSE 8321

TelePresence ISDN Gateways

SIP-Only (CUBE) Voice Gateways

ASR 1004/6 RP2

ASR 1002-X

ASR 1001-XCSR1000v (vCUBE)

Voice and Video Gateways Recommendations


Central SiteRemote Site

ISR / ASR Router

ISR Router

DMZ

ISDN Video Gateway

ISR / ASR (CUBE)

MPLS WAN

PSTN

Internet

Deployment Best Practices

• TelePresence Video Gateways

o Deploy dedicated ISDN Video Gateways

• PSTN Connectivity

o Central Site TDM-BasedDeploy ISR router with ISDN Primary Rate (PRI) modules

o Central Site SIP Trunk-BasedDeploy ISR or ASR router in DMZ and enable Cisco Unified Border Element (CUBE) functionality

o Remote SitesDeploy ISR router with Analog or ISDN Basic / Primary (BRI/PRI) Rate modules

Core Applications



Internet

MPLS WAN

Remote Site

Mobile/Teleworker

PSTN


WebExCisco

Conferencing


Endpoints

Collab Edge


DMZ

Expressway-E

ISDN Video Gateway

CUBE

Expressway-C

Headquarters



Manager

Call Control


Unity Connection


Applications

Core Applications

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

Key Benefits

• Redundant Unity Connection nodes

• SIP Trunk integration to Unified CM

• Integrations to directory and e-mail:

» LDAP Directory

» Microsoft Exchange

• Voicemail Access via

o Telephone User Interface (TUI)

o Voice User Interface (VUI)

o Visual Voicemail

• Email access to voicemail (Single Inbox /

Unified Messaging (UM))

Core Applications – Cisco Unity Connection (CUC)

Directory synchronisation

Unified CM

Unity Connection

Publisher

Subscriber

LDAP

Directory

Mailbox

synchronization

Voicemail access

Via TUI, VUI or

Visual Voicemail

Email access to

voicemail

(Single Inbox)

SIP

Messaging(On-Premise or

Cloud-Based)

Microsoft

Exchange

SIPTUI, VUI or REST/HTTPS

Email (SMTP/HTTPS)

Architecture Overview

Core Applications – Prime Collaboration Deployment

• x• x• x• x

VMWare

EXSi

host

.iso.iso

.iso

CM_Sub

VM

CM_Sub

VM

IM&P_Pub

VM

IM&P_Sub

VM

IM&P_Sub

VM

UCXN_Pub

VM

UCXN_Sub

VM

Prime Collaboration Deployment (PCD)

CM_Pub

VM

Design Objectives

• Simplify CUCM, CUCM IM&P and CUC deployments by enabling automated, unattended installation of server nodes

• Facilitate configuration of common network and security settings.

Core Applications – Prime Licensing Manager (PLM)Architecture Overview

• Cisco Prime License Manager (PLM)

enables license fulfilment:

» Electronic [requires Internet connectivity]

OR

» Manual license file request

• Licenses received (over the network or via

email)

• Licenses applied to system and

propagated to synchronised application

instances.

Unified CM Unity Connection

PublisherPublisher

Prime License

Manager

Cisco.com

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

http://www.cisco.com/go/cvd/collaboration

Traditional Sizing for Cisco Collaboration

Collaboration Sizing Tool (CST)

http://tools.cisco.com/cucst

http://tools.cisco.com/cucst

PA Simplified Sizing vs Collaboration Sizing Tool

Deployment within the

PA Sizing Assumptions?

Use PA

Simplified Sizing

Use Collaboration

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 Codeto join the CLMEL16 BRKCOL-2101 Spark room and continue the conversation

http://www.ciscospark.com/

http://download.ciscospark.com/

https://spark.aguilera.com.au/brkcol-2101

Collaboration Track at Cisco Live MELBOURNETrack 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

BRKUCC-2008 10th March 2016 8:30 AM Leveraging SIP to Simplify Dial Plans Both Inside and Outside the Enterprise

BRKUCC-2006 11th March 2016 2:00 PM

Deploying SIP Trunks with Cisco Unified Border Element (CUBE/vCUBE)

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

Contact Centre

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

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

Collaboration

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

BRKUCC-2677 10th March 2016 12:50 PM Designing Collaboration Meeting Rooms

BRKUCC-2670 11th March 2016 8:45 AM

Accelerate and Assure Collaboration Deployments with Cisco Prime

Collaboration

BRKCOL-2010 8th March 2016 4:00 PM Understanding Cisco and Apple Integration

Cloud

BRKUCC-2675 9th March 2016 4:30 PM Understanding Cisco Cloud and Hybrid Collaboration

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

Complete Your Online Session Evaluation

Learn online with Cisco Live!

Visit us online after the conference

for full access to session videos and

presentations.

www.CiscoLiveAPAC.com

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

T-Shirts can be collected Friday 11 March

at Registration

http://www.ciscoliveapac.com/

http://showcase.genie-connect.com/ciscolivemelbourne2016/

Thank you

Appendix

Call Control Multi-Cluster Considerations

Multi-Cluster Scenario

Subscriber Pair

Publisher

Publisher

Subscriber

CUCM IM&PCUCM

Subscriber Pair

Publisher

Publisher

Subscriber

CUCM IM&PCUCM

Subscriber Pair

Publisher

Publisher

Subscriber

CUCM IM&P

CUCM

SIP

Cluster #2

Cluster #1

Cluster #N

Design Objectives

• Multi-Cluster model is based on multiple iterations of the Centralised Call Processing Model

• Consider Multiple Clusters due to the following:

• Administrational Separation

• Geographic Footprint

• Deploy SIP Trunk Full Mesh to avoid session traversal through individual clusters

• Leverage Inter-cluster Lookup Service (ILS) for

• SIP URI Replication

• Directory Number (DN) replication via Global Dial Plan Replication (GDPR)

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

• ...

• IP address processnode references are used by Jabber to build HTTPS URLs to accesssservices

• 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 ReferencesWhy not IP addresses?

• 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 ReferencesWhy not Hostnames ?

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

FQDN Processnode ReferencesFQDN is the best solution

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

Enterprise ParametersRecommended Settings

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

• Certificate exchange part of TLS connection setup

• Certifcate Validity: expiration date, signature valid?

• Certificate Trust: is the signing entity trusted?

• Self-signed certs: import cert into trust store

• Issuing CA trusted

• Identity: does the certificate identity match the identity of the intended communication peer?

Base Concepts

Serial

Signature

Issuer

Subject

Validity

Subject Public Key

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 IdentificationCUCM 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

Conductor [Select]

(VM only) (up to 2)

30 x standalone or clustered

TS

(50 Call sessions)

YES

Full TelePresence

Conductor

(VM only)(up to 3)

30 x standalone or clustered

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.

Conductor Virtual IP Address

Location

Conference Alias

Conference Template

Service Preference

#1 Pool TS

TS

TS

#2 Pool

Prioritised

TS

TS

TS

(can be used in

multiple SP’s)

(can be used in multiple Conference Templates)

(not needed for instant conferences)

TelePresence ConductorConfiguration Concepts

Conductor Unified CM

Conf. Alias Route Pattern

Service

Preference

Route List/MRGL

Conf. Bridge

Pool

Route Group/MRG

Conf. Bridge Conference Bridge

Conductor Clustering

Media Resource GroupConductor 1

Conductor 2Trunk

10.1.1.1

10.1.2.1

10.1.1.2

10.1.2.2

Instant

Permanent

Media Bridge1

Media Bridge2

Trunk IP1

Trunk IP2

10.1.1.1

10.1.2.1

10.1.1.2

10.1.2.2

Unified CM Conductor

• 65 IP addresses per Conductor server

• Up to 3 nodes in a cluster

• Up to 30 bridges per cluster

• Max RTT of 30 ms between cluster nodes

MRG

Template

Service

Preference

Pool

MRGL

Endpoint Media

BridgeLocation TelePresence

ServerTelePresence

Servers


Conductor – Instant Conference Configuration

Conductor – Permanent Conference Configuration

Endpoint

Route

Pattern

TelePresence

Server

SIP

Route

PatternAlias

Template

Service

Preference

Pool


SIP

Trunk

Route

Group

Route

List

Location

TelePresence

Servers

Mobile and Remote Access


Collaboration

Services

CUCM


DMZ


MRA – Protocol Workload Summary

CUCM IM&P

Unity Connection

Conferencing

Protocol Security Service

SIP TLS Session Establishment – Register,

Invite, etc.

RTP SRTP Media – Audio, Video and Content

Sharing

HTTPS TLS Logon, Provisioning/Configuration,

Contact Search, Visual Voicemail

XMPP TLS Instant Messaging, Presence

Internet

MRA Global Deployment Topology & Geo DNS

SIP Trunk

SIP Line

Expressway Traversal

Unified CM

regional

clusters

SME global

aggregation US SME

CBR

DFW

RTP PAR

AMS

LON

EU SMEAsia SME

TKY

HKG

BGL

Expressway

edge access

Geo DNS

DNS SRV lookup

_collab-edge._tls.example.com

expwy.us.example.com

expwy.uk.example.com

expwy.jp.example.com

US Europe Asia

Voice and Video Gateways

Calling Search Space

PSTNInternationalPartition CUBE1

PSTNInternational

CBRInternational

Route Pattern \+! Route List RL_PSTN

PSTNInternationalPartition

MELInternational

Calling Search Space

CBR_GW

Device Pool set to

MELPhone

Device

Pool

LRG_PSTN1 LRG_PSTN2

CBRPhone CUBE_AUS_PSTN GW_CBR_PSTN

MELPhone CUBE_AUS_PSTN GW_MEL_PSTN

Route Group Trunk

GW_CBR_PSTN Trunk_To_CBR_GW

GW_MEL_PSTN Trunk_To_MEL_GW

Phone in CBR

Phone in MEL

LRG_PSTN_2

First choice for CBR users Backup for CBR users

Backup for MEL users

LRG_PSTN_1

MEL_GW

First choice for MEL users

Centralised IP PSTN Access With Local GW As Backup

Device Pool set to

CBRPhone

Core Applications

Cisco Unity Connection – Design Considerations

• Unity Connection Cluster Deployment (publisher + subscriber)

» Nodes: Must be the same OVA size and integrate to the same Unified CM cluster.

» 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.)

Sub Pub

X

Core Applications – Deployment Overview

1. Provision the Unity Connection Cluster – Deploy two node cluster for high availability

» Determine OVA configuration size (based on number of users) and network and security parameters for

each node (hostname, IP address/mask, default gateway, DNS, NTP, username/password, etc.).

» 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

Alternatively use Prime Collaboration Deployment

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.

Refer to the CVD

Simplified Sizing

Simplified Sizing – Additional ToolsVirtual Machine Placement Tool (VMPT)

http://www.cisco.com/go/vmpt

http://www.cisco.com/go/vmpt

Simplified Sizing – Additional ToolsCisco UC Virtualisation DocWiki

http://docwiki.cisco.com/wiki/Unified_Communications_in_a_Virtualized_Environment

http://docwiki.cisco.com/wiki/Unified_Communications_in_a_Virtualized_Environment

Simplified Sizing – Additional ToolsCollaboration Design Zone

• Cisco Collaboration Solutions Design Guidance:


» Cisco Collaboration Systems 10.x Solution Reference Network Designs (SRND)

» Cisco Collaboration Systems 11.0 Solution Reference Network Designs (SRND)

• Cisco Enterprise Preferred Architecture:


» Cisco Preferred Architecture for Enterprise Collaboration, Design Overview

» Cisco Preferred Architecture for Enterprise Collaboration, CVD



Complete Your Online Session Evaluation

Learn online with Cisco Live!

Visit us online after the conference

for full access to session videos and

presentations.

www.CiscoLiveAPAC.com

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

T-Shirts can be collected Friday 11 March

at Registration

http://www.ciscoliveapac.com/

http://showcase.genie-connect.com/ciscolivemelbourne2016/

Thank you

preferred architecture and designd2zmdbbm9feqrf.cloudfront.net/2016/anz/pdf/brkcol-2101.pdf ·...

Documents