Cloud Collaboration Platform

Understanding Cisco Cloud and Hybrid Collaboration Vanessa Sulikowski - Distinguished Systems Engineer Cisco Collaboration Cloud and Hybrid Platform Cisco Collaboration Cloud

Iteration Hybrid Services Security Ecosystem Continuous delivery Ties together today’s User messaging and Partners, developers Software Platform core collaboration content encrypted in & administrators as products with cloud transit and at rest first class citizens Cisco Spark Service - Extended

One Experience

Message Meeting Call

1:1 and team messaging in virtual rooms Audio, video, and web meetings Voice and video calling via a cloud based PBX1 Persistent Chat, Content Sharing, Iteration Before/during/after-meeting messaging and content Make calls within or outside organisation via the PSTN

OPEN PLATFORM

APPLICATION PARTNER SPARK HYBRID INTEGRATION SERVICES SERVICES APIs Interconnect Cloud + Prem Cisco Spark Architecture Integrated Cloud Services

Message Meeting Call Unified Platform Common Build, Deploy, Operate Approach: Devops, CI/CD, Openstack, Unified Serviceability

Common Identity, Directory & Contacts

Common Security Strategy

Common Admin Portal

Common Media

Common PSTN & SIP Edge (Webex)

Common Device Management

Integrated Call Control Spark Call + Spark RTC 6 Enterprise Grade Security – High Level

Data in motion encryption: Encrypted signalling audio/video HTTPS Encrypted Media (sRTP/SRTP-EKT)

Data at rest (Persistent Storage) Key Management Server Content Server Separate DB Stores KMS/Content Stored Content – always fully encrypted

End-To-End Encryption with AES-256GCM symmetric key: Ephemeral Keys - rotation Encrypted Messaging Encrypted Content Encrypted Room Titles

Client 1 Client 2 7 Flexibility of Cloud and Premise, Together

Cloud Design Public Cisco Approach: Cloud Collaboration Cloud Horizontal Scale Partner or Collaboration Edge Architecture Smaller Nodes Premise Ephemeral Storage Infrastructure Unified Communications Active-Active Monitoring Endpoints Metrics & Apps Cisco Cloud Collaboration Platform

Cloud Tropo Collaboration Platform Hybrid Services Integrations Customer Premise

rd Spark Cisco UC 3 Party Spark Web RTC Clients Clouds and HTML5 Services Cisco TP

Enterprise Apps. Custom & Business Apps via API Bots Future Collaboration Service Delivery - Premises & Cloud

Cloud Services Public Cloud Services

Customer Partner Cisco Private Cloud / On Collaboration Cloud Collaboration Cloud Premises Fusion Fusion Hybrid Collaboration – Enabling new Experiences Connect existing Cisco calling capabilities to Cisco Spark capabilities in the cloud Cisco Collaboration Cloud

Collaboration Cloud Services Call Control Identity/SSO Rooms Notification/Alerts Media/Transcoding Messaging Interop Content Sharing Management Calendar Future Cloud Collaboration Infrastructure Metrics & Reporting File Metadata Remote Spark Users Storage Storage Billing & Provisioning

Custom REST Applications based APIs Widgets Hybrid Cloud

Collaboration Cloud Services Enterprise Call Control Identity/SSO Rooms Conductor TS Notification/Alerts Media/Transcoding Video Endpoints Messaging Interop Content Sharing Expressway-E Expressway-C Management Calendar Future Unified CM Cloud Collaboration Infrastructure Jabber Metrics & Reporting File Metadata Remote Users Storage Storage Billing & Provisioning

Custom REST Applications based APIs Widgets Cisco Hybrid Services Components Allow customers to integrate premises applications with those in the Cisco cloud

(e.g. Cisco Call Control, Microsoft Exchange, Microsoft Active Directory)

Pocket

Cisco Cisco Spark Service Collaboration Message | Meeting | Call Cloud

Cisco Hybrid

Cisco Expressway Directory Connector Cisco On-Premises & Unified MS Exchange Active Directory Partner Hosted HCS Communications Boardroom Hybrid Services Cisco Spark + Hybrid Services

One Experience

Message Meet BYO Call

HCS Delivered Services Open Platform Communications Manager Hybrid Call Services (Call Aware and Call Connect) Services Calendar and Directory Service Business Edition Series Easy Content Sharing & Unified Call History

Cisco Cisco On-Premises & Collaboration Partner Hosted HCS Cloud

Call Service Aware - makes Spark aware of calls passing through the entire enterprise UC system.

• Zero Touch Meetings: every call is also a meeting. Share your screen and send documents/messages with one click • Convenient access to your call history regardless of device or app used • Quick and easy redial or call back of missed calls, from anywhere

Requires Expressway™ C v8.7(1), Unified CM 10.5(2) Connected Calling & Mobility

Cisco Cisco On-Premises & Collaboration Partner Hosted HCS Cloud

Call Service Connect - Connect Cisco Spark & the enterprise phone system – so they behave as one

• Use Spark, Jabber or your desk phone to make and receive calls from anyone without worrying about which you or the other person is using. • Call company extensions, PSTN numbers, Spark only users, and even video bridge numbers • Make and receive voice and video calls from anywhere you have Internet access, simply and securely. • Seamlessly transfer a call to where it suits you - a different device or a room, all with no interruption

Requires Expressway™ C & E v8.7(1), Unified CM 10.5(2) SU3 Simple Scheduling

Cisco Cisco On-Premises & Collaboration Partner Hosted HCS Cloud

Calendar Service - connect your calendars & enable meeting scheduling from anywhere

• Schedule meetings from your mobile device or Microsoft Outlook simply and with no plugins • Add @webex into the location field to include your WebEx details • Add @spark to create a Spark room for all invitees, allowing the conversation to start before the meeting • Automatically provision your video rooms with OBTP if they are included in the meeting

Requires WebEx T29.13+, Expressway™ v8.7+, Exchange 2010 SP3 / 2013 / O365, TMS v15.1 for OBTP Enterprise Directory

Cisco Cisco On-Premises & Collaboration Partner Hosted HCS Cloud

Directory Services – extend enterprise directory contacts to the cloud

• Simplify the admin process for cloud services by keeping cloud & premises directories in sync (add/entitle/remove users) • Always know who you are talking to through directory accuracy and consistency • Simplicity and security with Single Sign-On

Requires Directory Connector installed on Windows Domain Server (2003,2008 R2 or 2012) with administrator user privileges Connectivity Hybrid Services Requirements HTTPS CTI/AXL

Cisco Unified CM, Business Edition, and HCS SIP

Expressway-E Directory Expressway-C Expressway-C Connector Dedicated for Connectors Cisco Unified CM

Minimum UCM Call Service Calendar Service Directory Services Requirements: - For Unified CM 10.5(2)SU3 • For Call Service Aware • Expressway-C version 8.7 (Connector) Directory Connector installed on - For HCS 10.6.X Expressway-C version 8.7 (Connector) Windows Domain Server (2003,2008 R2 • Exchange 2010 SP3 or 2013 or 2012) with administrator user • For Call Service Connect: privileges New or existing Expressway pair version 8.7 Directory Service On - Premise Directory Directory Premise WebEx Cloud Directory Connector Directory Synchronisation Collaboration Cloud Cisco Messenger Cloud

EDGE HTTPS Cloud Identity Architecture Cisco Cisco Cloud Common Identity Cloud Services Enterprise Cloud Services OAuth Spark Authorisation Message (OAuth2) WebEx Authentication HTTPS / SAML Online IdP (Local/SAMLv2) WebEx Train

Directory Connector Service HTTPS / SCIM CCA RESTful Portal API’s Spark Call

Messenger Identity Store Provisioning via Directory Connector

HTTPS Identity/SSO Cisco Active Directory Collaboration Cloud Directory Connector

• Infrastructure for premise directory synchronisation to Common Identity cloud services (CIS)

• Directory connector integrates with AD to retrieve user information to sync with CIS

• Customer installs Directory Connector in its network on a Windows Domain server (Windows Server 2003, 2008 R2, or 2012) with administrative user privilege

• Directory Connector specifies the Active Directory synchronisation agreement and attribute mappings Admin Portal DirSync User Configuration Admin Portal DirSync AD Domain Configuration Admin Portal Directory Connector Installation Cisco Directory (DirSync) Connector Directory Services Summary

Identity+SSO Cisco Collaboration cloud HTTPS

Minimum Requirements Directory Connector • Microsoft Active Directory

• Directory Connector installed on Windows Domain Active Directory Server (2003,2008 R2 or 2012) with administrator user privileges

• Directory connector integrates with AD to retrieve user information and syncs with CIS Hybrid Services Edge and Management Hybrid Services Edge

Collaboration Cloud Services Enterprise Call Control Identity/SSO Rooms DMZ Notification/Alerts Media/Transcoding Video Endpoints Messaging Interop Content Sharing Expressway-E Expressway-C Management Calendar Future Unified CM Collaboration Cloud Infrastructure Jabber Metrics & Reporting File Metadata Storage Storage Billing &

Provisioning Expressway Call Call

C Calendar

Connector

Connector Connector

Connector

XMPP

Management

Future Service Service Future

Future Service Service Future SIP Trunk SIP *Note: This is a net Common Connector Framework new Expressway-C DC for hosting connectors Directory Connector Hybrid Service Expressway-C Registration

Expressway A Cloud Collaboration Management – Hybrid Manage Hybrid Services Connector Management

Collaboration Cloud Services Call Control Identity/SSO Hybrid User Discovery / Management Service Status Subscription

Management Calendar

Expressway Call Call

C Calendar

Connector

Connector Connector

Connector

XMPP

Management

Future Service Service Future

Future Service Service Future Future Service Service Future User Status Service Trunk SIP • Interfaces with CI for hybrid entitled users Common Connector Framework • Stores hybrid service status per user DC • Notifies downstream services about any Directory Connector entitlement changes Calendar Service Calendar Service How It Works: Organiser

Open a calendar appointment The calendar service from any device automatically orchestrates the desired collaboration experiences Add the people you need to work with and type @WebEx and/or @Spark in the location field – that’s it!

Eliminate steps and save time Be more productive while mobile Calendar Service How It Works: Participants

Participants receive the …and are automatically When it’s time to meet, calendar appointment that added to a Cisco Spark everyone can easily join from contains the host’s WebEx “room” where everyone can the device of their choice personal room information… work together prior to the meeting

Be more effective and efficient when it’s time to meet! Calendaring Scheduling Integration Calendar Service Exchange Calendaring Exchange Service Calendar WebEx Cloud Expressway Exchange Collaboration Cloud Cisco Messenger Cloud

EDGE Calendar Service

Collaboration Cloud Services Call Control Identity/SSO Rooms DMZ Notification/Alerts Media/Transcoding abc.example.com Messaging Interop Content Sharing Management Calendar Future Collaboration Cloud Infrastructure Metrics & Reporting File Metadata Storage Storage Billing & Provisioning Expressway

Connector

Connector Connector Connector

Connector

Calendaring Calendaring

XMPP

Management

Future Service Service Future

Future Service Service Future SIP Trunk SIP Exchange Web Services (EWS) Common Connector Framework RESTful https DC Directory Connector Calendar Service Configuration Specifics

• Minimum Exchange 2010 SP3 required due to updates in throttling policies. See: http://msdn.microsoft.com/en-us/library/office/jj945066(v=exchg.150).aspx

• Exchange 2013 is also supported; however, Exchange 2016 is not supported.

• O365 support is currently in early field trials

• EWS Subscription Group - Each group has one streaming subscription connection containing up to 200 individual streaming subscriptions.

• Using Exchange Web Services (EWS) and an Exchange Impersonation Account

• Deploying Calendar Service: https://help.webex.com/docs/DOC-2676 Cloud Collaboration Management – Hybrid Calendar Cloud Collaboration Management – Calendar Service Expressway-C Exchange Configuration Expressway-C WebEx CMR Configuration Calendar Service Deployment

Collaboration Cloud Services Identity/SSO DMZ DC

Management Calendar

Dedicated Expressway-C

A dedicated Expressway C for Connectors • Medium OVA template – 5000 users • Large OVA template – 10000 users cas1.test.org cas2.test.org OBTP with Calendar Service OBTP for @webex today and @spark later

Calendar Service + TMS15.1 & TMSXE5.2

Solves the OBTP problem of bifurcation with @webex What it does solve: and TP systems within one TMS deployment.

What it does not solve yet:

Back to back meetings in CMR B2B meeting Cannot use Productivity Tools with Calendar Connector Migrating to new backend without meeting update Participant Participant taps Join button in goes room, to CMR. Video Endpoint: Participants click CMR link and getto org’s Cloud CMR Mobile Endpoint: Calendar Service OBTP Service Calendar Call Control Management Messaging Interop Notification/Alerts Collaboration Cloud Infrastructure Collaboration Cloud Services Storage File Identity/SSO Calendar Metadata Storage Media/Transcoding Content Sharing Provisioning Reporting Metrics Metrics & Billing Billing & Rooms Future DC Expressway Connector Expressway Directory C - E Common Connector Common Connector Framework Management Connector Enterprise Expressway

Calendaring Connector - TMS C Future Service

Connector Unified CM

Future Service Conductor Connector

Future Service

Connector TS

Future Service Video Endpoints

Connector Jabber

SIP Trunk

XMPP Calendar Services Summary • Microsoft® Exchange Premise

• Create Spark Rooms

• WebEx PMR/CMR Customer

Cisco Collaboration cloud HTTPS Requirements

• Spark paid offer (M1 or higher) Expressway • @WebEx requires T29.13+ & PMR

Exchange • Expressway™ v8.7+ Connector

• Exchange 2010 SP3 / 2013 / O365*

• TMS v15.1 and TMSXE 5.2 to provide OBTP Hybrid Call Services Call Service Aware & Connect Hybrid Services

Call Service Connect allows Spark users to call and be called by UC users

Call Service Aware Call Service Aware enables complements UC calls Spark users to make and with Desktop Sharing answer calls on UC devices Spark “Calls” history also shows ZTMs, Spark-UC & Desk Phone Control calls Spark Call Aware: Spark Client before UC Call

Room not on top Spark Client after UC Call Established

A new room Notification created if to indicate one does UC call in not exist progress

Room Caller’s moves to Avatar the top of appears the list

A new UC call UX is Ability to presented initiate desktop share Spark Client when desktop share in progress

Indication desktop share is in progress Spark Client - Desktop share recipient

Maximize Desktop share

Desktop share in progress in the recipient’s Spark client Spark Client – UC call ended

Call indication stopped Desktop share stopped Cloud Collaboration Management – Hybrid Call Cloud Collaboration Management – Call Service Call Service Aware

Collaboration Cloud Services Call Control Identity/SSO Rooms DMZ Notification/Alerts Media/Transcoding Messaging Interop Content Sharing Management Calendar Future Collaboration Cloud Infrastructure Metrics & Reporting File Metadata Storage Storage Billing &

Provisioning Expressway Call Call

Calendar Calendar

Connector

Connector Connector Connector

Connector

Management

Future Service Service Future

Future Service Service Future Future Service Service Future AXL / CTI Common Connector Framework RESTful https DC Directory Connector Call Service Aware Donald Collaboration Cloud Services Enterprise Call Control Identity/SSO Rooms Video Endpoint Notification/Alerts Media/Transcoding Messaging Interop Content Sharing Call Connector Management Calendar Future Unified CM Collaboration Cloud Infrastructure Dedicated Video Endpoint Metrics & Expressway C Daisy Reporting File Metadata Storage Billing & Storage Provisioning Media Daisy AXL / CTI Spark RESTful https App SIP Call Service Connect

Collaboration Cloud Services Expressway Call Control Identity/SSO Rooms Traversal DMZ Expressway E

Notification/Alerts Media/Transcoding XMPP

SIP Trunk SIP

HTTPProxy Media Relay Media Messaging Interop Content Sharing Management Calendar Future Collaboration Cloud Infrastructure Metrics & Reporting File Metadata Storage Billing &

Storage Provisioning Expressway Call Call

Calendar Calendar

Connector

Connector Connector Connector Connector

Connector Expressway

Management

Future Service Service Future Future Service Service Future Media Service Future C AXL / CTI Common Connector Framework RESTful https DC SIP Directory Connector Call Service Connect: Premise Device Dial Use Case

Donald Collaboration Cloud Services Example Call Control Identity/SSO Rooms Notification/Alerts Media/Transcoding 4 3 1 Messaging Interop Content Sharing Any Unified CM Expressway-E Expressway-C Unified CM Management Calendar Future registered device 2 Collaboration Cloud Infrastructure Metrics & CTI-RD Reporting File Metadata Expressway-C Daisy Storage Billing & for Connectors Storage Provisioning 1 Call initiated from a Unified CM registered device 5 2 Call presented to device and associated CTI-RD 3 CTI-RD routes [email protected] Daisy 4 Call presented to Collaboration Cloud Call Control Media 5 Call presented to Cisco Spark Call Service Connect: Cisco Spark Initiated Use Case

Donald Collaboration Cloud Services Example Call Control Identity/SSO Rooms X Notification/Alerts Media/Transcoding 2 3 4 Messaging Interop Content Sharing 5 Any Unified CM Expressway-E Expressway-C 5 Unified CM Management Calendar Future registered device 4 Collaboration Cloud Infrastructure Metrics & CTI-RD Reporting File Metadata Expressway-C Daisy Storage Billing & for Connectors Storage Provisioning 1 Call initiated from Cisco Spark to Donald 1 2 2 Call forked to Cisco Spark and [email protected] 3 Call routed to Unified CM for [email protected] Daisy Donald 4 Call presented to device and associated CTI-RD 5 CTI-RD routes [email protected] Call Service Connect: Cisco Spark URI Dial Use Case

Belle Collaboration Cloud Services Example Call Control Identity/SSO Rooms Notification/Alerts Media/Transcoding 2 3 4 Messaging Interop Content Sharing Any Unified CM Expressway-E Expressway-C Unified CM Management Calendar Future registered device Collaboration Cloud Infrastructure Metrics & Reporting File Metadata Expressway-C Daisy Storage Billing & for Connectors Storage Provisioning 1 SIP URI dial from Cisco Spark to [email protected] 1 2 Call sent [email protected] (not using Cisco Spark) 3 Call routed to Unified CM for [email protected] Daisy 4 Call presented to device Call Service Deployment

Collaboration Cloud Services Call Control Identity/SSO DMZ DC An existing Expressway C/E pair used for B2B, MRA (Calls are equal weight) Expressway-E Expressway-C Management

Dedicated Expressway-C

A dedicated Expressway C for Connectors • Medium OVA template – 5000 users • Large OVA template – 10000 users ucm1.example.com ucm2.example.com Call Service Deployment Guidelines & Recommendations Call Service Deployment

Collaboration Cloud Services Traversal Zone Call Control Identity/SSO SIP Trunk Cloud SIP URI

SIP Destination Expressway-E Expressway-C Management CTI-RD DNS Zone Neighbor Zone

Dedicated Expressway-C

DMZ DC Call Service Connect End-to-End Enterprise Settings

DNS zone • A single SIP URI Domain name is defined per Organisation

• This is used to build the cloud services URI for each used Traversal zone

• Domain can only be defined ONCE

• Full cloud services URI is:

• Suffix call.ciscospark.com for all UCM neighbour cloud services URIs zone 10.5(2) Connector Configuration Minimum Each CM cluster provisioned on call connector

• Configure a SIP Trunk to Expressway-C and SIP route pattern to route the appropriate domain via SIP Trunk (currently ciscospark.com)

• User needs to be an application user with: • Standard CTI Allow Control of All Devices • Standard CTI Enabled • AXL API Access

• On each UCM cluster the CFQDN has to be set to a unique value

• If multiple CFQDNs are configured then the 1st is considered Call Service Connect End-to-End CTI-RD, remote Destinations

DNS zone • CTI Remote Device needs to be provisioned

• User’s primary extension as DN (shared line)

• Rerouting CSS has to have access to route to Spark Traversal zone • CSS only used if per user CoS is enabled

• CTI-RD to be added to user’s list of controlled devices • Call connector uses this to select CTI-RD for remote destination provisioning UCM neighbour zone • Cloud services URI automatically provisioned as remote destination by call connector Note: the above is subject to change (more automation) Call Service Connect End-to-End Spark to Expressway

DNS zone • SIP Destination per Org is configured in Cloud Collaboration Management

• Configured destination can be IP, host, or DNS SRV Traversal zone • Expressway-E certificate must match configured host/SRV

• Mutual TLS (MTLS) authentication is required for Call Service Connect UCM neighbour zone • MTLS can not be used on port 5061 if Expressway-E is used for MRA • Use different port instead (5062) Expressway Configuration Summary 8.7(1) Minimum • Configure a Traversal Zone Pair on Expressway-C and Expressway-E ─ Pre-existing server/client pairs can be used

• Enable Mutual TLS Authentication between Expressway-E & Collaboration Cloud ─ Port/ACL configuration for incoming connections on MTLS port (5061, will be 5062 for existing)

• Configure DNS Zone on Expressway-E ─ Allows for routing of SIP Requests between On-Prem and Cloud

• Search rules on Expressway-E for Domain URI routing (customer unique)

• Search rules on Expressway-C ─ One inbound search rule per UCM cluster, and a single outbound search rule

• Neighbour Zones on Expressway-C per UCM cluster ─ Jabber MRA zones cannot be reused due to different listening port ─ Accept preloaded SIP Route headers with home cluster FQDN Call Service Connect Deployment

Call Service Connect hybrid service calls are classified the same as MRA, B2B calls and can traverse existing Expressway C&E pairs Note: There is no traversal license cost as *.ciscospark.com calls do not count Call Service Connect follows existing MRA/B2B preferred architecture planning recommendations • Determine the total number of concurrent MRA, B2B, and Call Service Connect calls • Deploy the appropriate number of Expressway E/C pairs • There is no net new Expressway C or E required for Call Service Connect Calendar & Call Service Capacity Guidelines

Calendar Calendar CallCalendar CallCalendar ManagementCallCalendar ManagementCallCalendar 3 redundant pairs Calendar & ManagementCall ManagementCall Management Management Small/Med OVA 15,000 Users Call Connector Large OVA 30,000 Users

Up to 6 nodes Expw-C Expw-C

Site 1 Site 2 Calendar Calendar CallCalendar Calendar Calendar & CallCalendar Calendar Calendar CallCalendar ManagementCall Calendar CallCalendar ManagementCall ManagementCallCalendar ManagementCall ManagementCallCalendar ManagementCall ManagementCall Call Connector Management ManagementCall Management Management Management Multi-site Expw-C Deployment Expw-C Expw-C Expw-C Small/Med OVA 30,000 Users Large OVA 60,000 Users Offer Packaging for enabling Hybrid Services

Available in most Geos

M2 M3 M1 Everything Everything in M2, in M1, and: and: • Room Moderation • Host WebEx-powered Hybrid • Management Portal • Host 25-party meetings with screen • SSO & Dir Sync meetings with screen sharing and with external Services • Calendar Connector sharing with other participants • Call Connector Spark users • Personal Meeting Room • Scheduled Meetings

Free • Business-class Messaging • 1:1 and 3-party video calling with screen sharing • Join Spark and SIP-based meetings, SIP Dial out Summary Summary R2, or 2012 R2, 2012 or as admin Server 2003, 2008 Windows Domain installed on trusted a Directory Connector Directory Connector WebEx Cloud - Integrating Premise and Cloud and Premise Integrating Directory O365 O365 support currently in test Exchange 2010 SP3 2013 or Calendar Calendar Connector Exchange Collaboration Cloud Cisco ExpresswayX8.7.1 Call Connector HCS 10.6.x Unified CM 10.5(2) SU3 Cisco UC Future Future Connector Messenger Cloud ? Future ?

EDGE Recommended firewall ports settings

Cisco Spark

Cisco Collaboration Cloud Single shared media port deployment with “ICE” Use single port #33434 which is within existing dynamic range customers have enabled. Media/Share go through that port. Tries UDP and falls back to TCP if needed. Bandwidth and Sizing

• Enterprise Preferred Architecture: http://www.cisco.com/c/en/us/td/docs/solutions/CVD/Collaboration/enterp rise/collbcvd/sizing.html • Cisco WebEx Network Requirements: https://support.webex.com/MyAccountWeb/knowledgeBase.do?articleId= WBX264 • Cisco WebEx Requirements for Streaming Video: https://support.webex.com/MyAccountWeb/knowledgeBase.do?articleId= WBX53328 Continue the Conversation using Cisco Spark Understanding Cisco Cloud and Hybrid Collaboration

• 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 the World of Solutions Cisco Spark area for demos

• Use Cisco Spark to continue the conversation or ask any additional questions with the speaker for this session. The room name is BRKUCC-2675

• How to get added to the Cisco Spark room for this session • To opt in, send an email to [email protected] with the message “Please add me to the BRKUCC-2675 room” 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