Designing and Deploying Multiparty Conferencing for On Premise Telepresence Video Richard Murphy

Transcription

1

2 Designing and Deploying Multiparty Conferencing for On Premise Telepresence Video Richard Murphy BRKCOL-2803

3 Abstract Cisco has a strategy that enables comprehensive multiparty conferencing to any user on any device with a consistent user experience in a rich collaboration environment. This session is intended for Cisco partners and customers who want to understand the key multiparty infrastructure products within the Cisco on premise video architecture. By attending this session you will learn how to design a Cisco s recommended multipoint architecture and understand the components and features of this solution. The discussion will start by introducing the products, and later focus on how to design and implement them into common architectures based on specific scenarios while identifying best practices and design considerations. This session will focus on the Cisco TelePresence Server, both hardware and software platforms, the Cisco TelePresence Conductor, integration into the Cisco Unified Communication Manager, CMR on premise, TMS and TMSPE as it relates to CMR. This session will not focus or go into depth on CMR Cloud or CMR Hybrid. 3

4 Agenda Portfolio Overview Designs and Architectures Collaboration Meeting Room On-Premise (CMR) Personal Multiparty Licensing Acano Acquisition 4

5 Portfolio Overview 5

6 Choosing the Right Option Guidance for Video Conferencing Focused Customers 1 Cloud WebEx or Spark customer Greenfield conferencing CMR Cloud Interop including S4B 2 Multiparty licensing CMR Premise or Hybrid Customer Ad-hoc escalation Multistream Triple Screen Support On-Prem 3 Rich Skype for Business (S4B) conferencing interoperability Public Sector: JITC and FIPS certifications Scalable on premise Audio and video conferencing Spark & WebEx Conferencing TP Server (Mulitparty Licensing) Acano (CUWL licensing) Hybrid Services (long term direction) 6

7 MultiParty Overview Terminology Multipoint Control Unit or MCU is often used as a generic term for any video bridge. Within Cisco the term MCU refers to a specific line of legacy video bridges: Terminology TelePresence Server (TS) MCU Cisco Products Cisco Multiparty Media 310 Cisco Multiparty Media 320 *Cisco Multiparty Media 400v Cisco Multiparty Media 410v Cisco Multiparty Media 820 Cisco TelePresence Server on Virtual Machine (vts) *Cisco TelePresence Server 7010 Cisco TelePresence Server 8710 *Cisco TelePresence MCU 4501 *Cisco TelePresence MCU 4505 *Cisco TelePresence MCU 4510 *Cisco TelePresence MCU 4515 *Cisco TelePresence MCU 4520 Cisco TelePresence MCU 5310 Cisco TelePresence MCU 5320 Cisco TelePresence MCU MSE 8510 blade *End of Sale devices 7

8 MultiParty Overview Choices TelePresence Server Support for wide range of codecs Optimized conferencing ActiveControl support Multiple layouts and PIN support Available in hardware and VMWare Supports multiscreen and single screen endpoints Uses new Flex API for advanced features Basic Cascading Multistreaming (SVC) support Personal Multiparty Licensing MCU H.323 and SIP support Auto Attendant Basic cascading No TIP support No optimized conferencing Legacy API 8

9 Conferencing MCU vs TS TS has more Functionality than MCU and is the Preferred Platform. MCU still fits Niche Deployments Customers Can Migrate Feature Auto Attendant Cascading Conductor Support ClearPath TS 310/ Virtual TS MCU 5300 MCU 8510 Cisco MCU Requires Port License Cisco MCU Conversion (PLC) key PLC key - $0 item 5310 L-MCU5300-UPG-PAK 53x0 then select L-300-PLC 1 Full HD port = 1 TS Screen 5320 License = 1 SMP license Requires Conductor Cisco TelePresence Server 320 Optimized Conferencing CMR Hybrid ActiveControl Multistreaming (SVC) Requires TSMO key on Supervisor TSMO key - $0 item 8510 L-8000-CHLIC-PAK then select L-8000-TMSO SD ports = 1 TS Screen License = 1 SMP License

10 Conferencing TelePresence Server Experience Single screen experience in release 2.3 and later Multiscreen experience Single ActivePresence Prominent Equal 10

11 TelePresence Server Platforms TelePresence Server on VMWare (specs based) TelePresence Server on VMWare Appliances Blade 8-core 410v to 10 ports at 720p 1 to 64 ports at 720p 1 to 12 ports at 720p 1 to 24 ports at 720p 30vCPU 410b to 24 ports at 720p to 60 ports at 720p 3x0 Stacked 1 to 20 ports at 720p 1 to 64 ports at 720p 1 to 48 ports at 720p 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 and based on version TS 4.3. See release notes for further detail. 11

12 TelePresence Server TelePresence Server on Virtual Machine (vts) Three variants of vts: MultiParty Media 410v Only supported on specific UCS platform Up to *32 screen licenses (64 HD ports) Co-residency not supported (ships as dedicated UCS box) 8-core vts Supported in TS release 3.1 and later Up to 5 screen licenses (10 HD ports) Supported on BE6k, BE7k, and specs-based Can be co-resident with other apps 30vCPU High Density VM Previous to 4.1 was referred to as 16-core Up to 10 screen licenses (20 HD ports) Supported on BE6k, BE7k and specs-based Co-residency not supported *Capacity numbers are based on version TS

13 8 x MM410v Blades per Chassis 8 x MM410v Blades per Chassis TS 8710 MM820 blade HD port capacity with content 40 TelePresence Server Scale Increases 60 TS 4.3 TS 4.2 (3.75) TS 4.1 (2.29) TS 4.1 TS % % % % % % % Shared BE6000H/BE7000H + Co-res apps Dedicated BE6000H/BE7000H MM 400v MM 410v Server MM 410v Blade Server MSE

14 Multiparty Media 820 Comparison to 8710 MSE 8710 MM 820 Part Number CTI-8710-TS-K9= CTI-820-MEDIA-K9= Price USD List $62,340 $62,340 Maximum number of screen licenses per blade Maximum number of screen licenses per cluster Blades per cluster 4 2 Conference Participant 1080p 720p 480p 360p Note maximum participants 104 in a conference and 200 per blade and cluster x increase Software versions All 4.2 or higher Modes Local or Remote Remote Multistreaming support No Yes H.265 ready No Yes 14

15 Conductor required Conductor is a required component with the vts, MM310, MM320, and MM820. It is recommended to be used with MSE 8710 blade. Conductor Virtual TS MM 310 MM 320 MM 820 SIP only No H.323 support Requires VCS for Interworking (H.323 < -- > SIP) H.323 SIP VCS 15

16 What does TelePresence Conductor do? Conference Virtualization Consistent User Experience Share resources for Ad hoc, Instant Scheduled Conferences Ability to Scale Resource Management/Conference Bridge Selection Which Gives us? Knows all the available and used ports and optimizes resources. Intelligent Bridge selection Automatic cascading of Conferences across Telepresence Servers Centralized Conference Provisioning and Administration Easy Administration of large Deployments Single configuration applied to any conferencing resource Ad hoc and Rendezvous Conference support 16

17 Conferencing Endpoints Conductor deployment SIP Trunk(s) configured in CUCM to Conductor Conductor CUCM Call Control SIP B2BUA Pools of MCUs and TelePresence Servers sit behind Conductor Conductor added as a conference bridge in CUCM TS Resource Pool Cisco TelePresence Conductor MCU Resource Pool Ad hoc, CMR & Scheduled calls by CUCM registered endpoints use conductor to find a multipoint resource *TS 7010 MM 310 and 320 MSE TS 8710 Virtual TS /4x0v MM820 * EOS announced products MCU 5300 Series MSE MCU 8510 *MCU 4200 Series *MCU 4500 Series *MSE MCU 8420 SIP H.323 HTTPs 17

18 Conductor Platforms Variant Free TelePresence Conductor [Essentials] (VM only) Conductor Clustering Capacity Support Price (Part number) 1 x standalone MCU or TS (non clustered or non stacked) No TAC support, use communities and forums Free (Download.OVA) Mid-Market TelePresence Conductor [Select] (VM only) (up to 2) Variable # of standalone/clustered MCUs and/or TSs (50 Call sessions) TAC support with contract USD List $7,995 (R-VMCNDTRM-K9) L-CNDTR-UG-PAK Full TelePresence Conductor (VM only) (up to 3) 30 x standalone/clustered MCUs and/or TSs (2400 Call sessions) TAC support with contract USD List $40,560 (R-VMCNDTR-K9 or CTI-CNDTR-K9) Able to upgrade from Free Conductor -> Midmarket Conductor -> Full Conductor Same software shared across all variants. Option keys used to differentiate types of Conductor. 18

19 Preferred Architecture 19

20 Collaboration Architecture Overview Headquarters Prime Collaboration TMS VCS-C VCS-E Unified CM CUBE Management Conductor Call Control Edge Internet Mobile Worker ISR G2 ISR G2 TS MPLS WAN TS TS Other UC Applications Unity Connection IM and Presence Conferencing UC Applications Gateway Endpoints PSTN / ISDN Remote Site SIP Trunk(s) 20

21 Collaboration Architecture Overview Headquarters Prime Collaboration TMS VCS-C VCS-E Unified CM CUBE Management Conductor Call Control Edge Internet Mobile Worker ISR G2 ISR G2 TS MPLS WAN TS TS Other UC Applications Unity Connection IM and Presence Conferencing UC Applications Gateway Endpoints PSTN / ISDN Remote Site SIP Trunk(s) 21

22 Collaboration Preferred Architectures & CVDs PA Overview PA CVD Cisco Validated Design Cisco Validated Design Applications Pre-Sales Process Design Overview Document Targeted to Presales What (w/ Some Why)! Post-Sales process Detailed Design and Deployment Guidance Post Sales Design and Deployment What, Why, and How! Process Driven Guide Post-Sales Process Detailed, Deployment Guidance Post Sales Design and Deployment What, Why, and How! Process Driven Guide Plugs into the PA CVD 22

23 Architectures and Designs 23

24 Conferencing Types of conferences Ad hoc Impromptu meetings, they are not scheduled beforehand,nor require an administrator to initiate them. Suitable for smaller, on-the-fly, meetings. A point-to-point call escalated to a multipoint call is considered ad hoc. Rendezvous/Instant/Personal CMR Also called meet-me/permanent/static conferences, requires endpoints to dial in to a pre-determined number. Often used for recurring meetings which involve different endpoints each time. Scheduled Conference Provides a guarantee that endpoints and multipoint resources will be available at a certain time. Endpoints join manually or are automatically connected by the multipoint resource. TelePresence Server (TS) Ad Hoc * Rendezvous Scheduled Cisco Multipoint Control Unit (MCU) Ad Hoc Rendezvous Scheduled 24 * Requires Conductor

25 Recommended Deployment Ad hoc and Rendezvous SIP Trunk Registration Endpoints Expressway-E Cluster Expressway-C Cluster UCM Cluster Internet Conferencing architecture: TelePresence Server is primary bridging platform Conductor Cluster Multiple TelePresence Servers Home/Remote Worker Conductor in front of all bridges Everything registered to UCM 25

26 CUCM Integration 26

27 Unified CM Conference Bridge Connectivity UCM 8.6 and 9.x design Supported in UCM 8.6 and 9.x Required separate physical bridges Supported MCU for both types TS Rendezvous only No bridge cascading support Ad hoc Conference Bridge in UCM Rendezvous SIP trunk in UCM Conference Bridge in UCM configuration Individual bridges SIP trunk in UCM configuration 27

28 Method of Integration Back to Back User Agent (B2BUA) B2BUA Back to Back User agent is a logical network element in SIP applications. SIP is a signaling protocol to manage multimedia (VoIP) telephone calls. A back-to-back user agent operates between both end points of a phone call or communications session and divides the communication channel into two call legs and mediates all SIP signaling between both ends of the call, from call establishment to termination. As all control messages for each call flow through the B2BUA, a service provider may implement value-added features available during the call. In the originating call leg the B2BUA acts as a user agent server (UAS) and processes the request as a user agent client (UAC) to the destination end, handling the signaling between end points back-to-back. A B2BUA maintains complete state for the calls it handles. Each side of a B2BUA operates as a standard SIP network element as specified in RFC Source: 28

29 Conductor and UCM How does the model change? Conference Bridge in UCM configuration Eliminates the need for separate conference bridges Emulates MCU API, looks like MCU to UCM Utilizes B2BUA Accepts SIP Signaling Uses Multiple IP addresses (65 Max.) Management IP Location specific IPs IP address for ad hoc IP address for rendezvous Added Conductor SIP trunk in UCM configuration Individual bridges UCM 11.X 29

30 Conductor Configuration Concepts Conductor Virtual IP Address Location Conference Alias (not needed for ad hoc conferences) Conference Template Service Preference (can be used in multiple Conference Templates) #1 Pool TS/MCU TS/MCU (can be used in multiple SP s) #2 Pool TS/MCU TS/MCU TS/MCU TS/MCU Prioritized 30

31 Conductor How it works Ad hoc 8710 TS Device Pool, MRGL, MRG lookup to select Conductor as a Conference Bridge CUCM create.conference command sent to.2 Conference Template assigned to.2 applied Conductor Request ad hoc conference Presses Conf softkey Endpoints redirected to new conference Management: Ad hoc: Rendezvous: Service Preference applied Prioritized pool selected MCU from pool is chosen Conductor creates conference on MCU 5300 MCU SIP HTTPs Media 31 Note: Conductor does not cascade bridges for ad hoc conferences.

32 Conductor How it works Rendezvous 8710 TS Based on endpoint s CSS, CUCM matches a Route Pattern or SIP Route Pattern in an allowed partition CUCM Conductor matches conference alias (might be a generic alias with wildcards) Conductor Conductor creates conference on TS For simplicity only single call is shown Multiple endpoints dial pre-determined DN or URI SIP INVITE sent to.3 Management: Ad hoc: Rendezvous: Conference template is applied Service Preference applied Prioritized pool selected TS from pool is chosen Any subsequent calls to that same DN or URI, conductor will direct to the same TS conference 5300 MCU SIP HTTPs Media 32 Note: Conductor can cascade rendezvous conferences.

33 Multiparty Design Redundancy SIP Trunk Registration Endpoints Expressway-E Cluster Expressway-C Cluster UCM Cluster Internet Conductor Cluster Multiple TelePresence Servers Home/Remote Worker 33

34 Recommended Deployment Ad hoc/rendezvous Allows for single conductor or link to fail and calls are processed Clustered Management Ad hoc Rendezvous All configuration parameters except IP addresses are sync d Sync Configuration Primary Ad hoc Primary Rendezvous Secondary Ad hoc Secondary Rendezvous Ethernet Management Ad hoc Rendezvous Ad hoc and Rendezvous TelePresence Servers 34

35 Multiple UCM Clusters and Conductor UCM Berlin Conductor supports up to 3 in a cluster Multiple UCMs connect to the cluster Use local resources for adhoc and rendezvous meetings.1 Mgmt Conductor Hamburg Conductor: 65 IP addresses 1 for management 64 for locations UCM Munich Location Berlin Location Hamburg Location Munich Conf Bridge.2 Adhoc.4 Adhoc.6 Adhoc Conf Bridge Sip Trunk.3 Rendezvous.5 Rendezvous.7 Rendezvous Sip Trunk Berlin Pool UCM Hamburg Munich Pool Location Berlin uses Berlin Pool Location Hamburg uses Hamburg Pool Conf Bridge Location Munich uses Munich Pool Hamburg Pool Sip Trunk 35

36 Conductor Location Trunks TS Conductor Has multiple trunks configured back to UCM Trunk 1 Trunk 2 Auto Dial Participant: Recording Server (TCS) Conductor Location Trunk 3 Conference Team Meeting All SIP trunk destinations for a Location are equivalent and will use any of the configured destinations for outdial calls and continue to use same destination as long as the destination is reachable (no load balancing) Automatically chooses a new SIP trunk destination, if the current destination becomes unreachable (monitor destination availability by SIP Option ping and response) Chooses available trunk and uses it till it becomes unavailable New in XC3.0 36

37 Conductor and TS Minimum Communication Requirements SIP Trunk Configuration Ensure Destination port match SIP Security Profile Match TCP or TLS (recommended) Location Trunk Configuration Ensure port match Secured Signaling Optional but still recommended If this key is not installed the media is not encrypted between endpoint and TS. Signaling is encrypted by default and the key does not impact this functionality when using TS 4.2 or higher software revision. Conductor TelePresence Server Create TS bridge definition Use Unique Conductor User for TS credentials Ensure TLS 5061 is configured as the port Encryption Key installed TLS service enabled Unique Conductor User 37

38 Conductor and TS Encryption key changes An encryption key is no longer required to use TelePresence Server version 4.2 or later. The message on the Conference bridge status page has changed from "Encryption key installed" to "Signaling encryption enabled". Before TelePresence Server version 4.2, signaling encryption was enabled only if the encryption key was installed. The term "Encryption Key" is replaced with "Media Encryption Key" beginning in version 4.2. Encryption keys installed in TelePresence Servers running a software version earlier than 4.2 are automatically converted to media encryption keys when upgrading to version 4.2 or later. Below or higher 38

39 Conductor Conference Placement 39

40 Conference Placement Conference configuration > Global settings Available with March With XC 4.1 Favor CMRs: selects the bridge with the most spare capacity (better for conferences with staggered start times) Favor Scheduled: selects the bridge with the fewest conferences currently running (better for conferences that start at the same time). Default: Favor Scheduled 40

41 Conference Placement Conference configuration > Global settings Conference 1 starts Favor CMRs (most spare capacity) Conductor chooses TS2 multiple endpoints join updated capacity 30 Capacity: TS1 12 screen licenses TS2 48 screen licenses TS3 24 screen licenses TS1 TS2 TS3 Free=12 Free=24 Free=30 Total= 12 Total=48 Total=24 41

42 Conference Placement Conference configuration > Global settings Conference 1 starts Favor CMRs (most spare capacity) Conductor chooses TS2 multiple endpoints join updated capacity 30 Capacity: TS1 12 screen licenses TS2 48 screen licenses TS3 24 screen licenses TS1 TS2 TS3 Conference 2 starts Conductor chooses TS2 because it has the most capacity multiple endpoints join updated capacity 22 Free=12 Free=30 Free=22 Free=24 Total= 12 Total=48 Total=24 42

43 Conference Placement Conference configuration > Global settings Favor CMRs (most spare capacity) Conference 1 starts Conductor chooses TS2 multiple endpoints join updated capacity 30 Capacity: TS1 12 screen licenses TS2 48 screen licenses TS3 24 screen licenses TS1 TS2 TS3 Conference 2 starts Conductor chooses TS2 because it has the most capacity multiple endpoints join updated capacity 22 Free=12 Free=22 Free=24 Free=6 Conference 3 starts Conductor chooses TS3 because it has the most capacity at conference start. Total= 12 Total=48 Total=24 43

44 Conference Placement Conference configuration > Global settings Conference 1 starts Favor Scheduled (fewest conferences) Conductor randomly chooses because of equal number of conferences For this example, TS1 is chosen Capacity: TS1 12 screen licenses TS2 48 screen licenses TS3 24 screen licenses TS1 TS2 TS3 Number of Conferences = 1 Number of Conferences = 0 Number of Conferences = 0 Total= 12 Total=48 Total=24 44

45 Conference Placement Conference configuration > Global settings Conference 1 starts Favor Scheduled (fewest conferences) Conductor randomly chooses because of equal number of conferences For this example, TS1 is chosen Conference 2 starts Conductor chooses TS2 or TS3 chooses because of equal number of conferences For this example, TS2 is chosen Capacity: TS1 12 screen licenses TS2 48 screen licenses TS3 24 screen licenses TS1 TS2 TS3 Number of Conferences = 1 Number of Conferences = 1 Number of Conferences = 0 Total= 12 Total=48 Total=24 45

46 Conference Placement Conference configuration > Global settings Conference 1 starts Favor Scheduled (fewest conferences) Conductor randomly chooses because of equal number of conferences For this example, TS1 is chosen Conference 2 starts Conductor chooses TS2 or TS3 chooses because of equal number of conferences For this example, TS2 is chosen Conference 3 starts Conductor chooses TS3 because has the least number of conference. Capacity: TS1 12 screen licenses TS2 48 screen licenses TS3 24 screen licenses TS1 TS2 TS3 Number of Number of Number of Conferences Conferences Conferences = 1 = 1 = 1 Total= 12 Total=48 Total=24 46

47 Cascading with TelePresence Server 47

48 Cascading with TelePresence Server Requires following versions: TelePresence Server 4.0(1.57) and later Conductor XC2.4.1 and later Only available in remotely managed mode (requires Conductor) Each cascade link uses 720p 30fps main video, stereo audio, and 720p 30fps content quality Single stream cascade of active speaker video Allows for up to 2,342 participants in a single conference with a maximum roster list of 500 participants. TelePresence Server to MCU cascade is not supported, only Telepresence Server to TelePresence Server 48

49 Cascading Demo Host Host Host Cascade Cascade Cascade vts has 8 HD ports available (Optimized Conf disabled for demo) Conductor Settings: Conference type: Lecture Number of hosts to reserve: 3 Maximum number of cascades: 2 49

50 Cascading with TelePresence Server Conductor Event Log 50

51 Cascading with TelePresence Server Conf 1 Conf 1 Cascade links Conf 1 Conf 2 Conf 3 Conf 3 Conf 3 Conf 3 Conf 1 Conf 2 Conf 2 Conf 1 Conf 3 Conf 1 Conf 1 Conf 2 Conf 2 Hub and spoke topology Conf 1 Conf 1 Conf 2 Only single primary TS in any given conference supported Same TS can be primary in 1 conference and secondary in another conference Max number of hops between endpoints = 3 51

52 Cascading with TelePresence Server Conductor Configuration Allows each conference created with this template to increase in size by ways of up to two cascades Means 2 extra ports will be reserved for each conference using this template (whether or not a cascade is invoked) Does not reserve any cascade ports on potential secondary TS s Does not impact cascade link as it is hardcoded to 720p30. 52

53 Cascading with TelePresence Server TelePresence Server GUI New type of connection Cascade denotes connection to another TelePresence Server 53

54 Optimized Conferencing 54

55 Recommended Deployment Ad hoc/rendezvous SIP Trunk Registration Endpoints Expressway-E Cluster Expressway-C Cluster UCM Cluster Internet Conductor Cluster Multiple TelePresence Servers Home/Remote Worker 55

56 Optimized Conferencing Before Optimized Conferencing TS standalone and uses locally managed mode Fixed Configuration of ports Full HD limited to 1080p30/stereo/720p15 HD limited to 720p30/stereo/720p5 Participants are free to connect at resolutions below these maximums at each service level but they will always use one whole resource. ex.: 9971 connection uses Full HD or HD port 12 Ports 24 Ports With Optimized Conferencing Uses TS remotely managed mode with Conductor Supports conferences of different quality levels on a TS 1080p, 720p, 480p, 360p for main video 1080p and 720p content up to 30fps increased capacity <= 104 participants in a TS conference For the first time main video quality modes below 720p are available to participants allowing administrators to provide lower cost and higher scale services. Requires Conductor to orchestrate the resources.

57 TelePresence Conductor configuration Conference templates configuration Maximum Video Quality Full HD (1080p 30fps / 720p 60fps video, multi-channel audio) HD (720p 30fps video, stereo audio) SD (wide 448p 30fps video, mono audio) 360p (360p 30 fps video, mono audio) Audio Only (no video, mono audio) Reclaim Resources after 5 seconds Maximum Content Quality Full HD (1080p 30fps / 720p 60 fps) HD (720p 30fps) 1280 x 720p 15fps 1280 x 720p 5fps Off 57

58 Optimized Conferencing (Example) Conductor with TelePresence Server 4.0 and TS4.1 Conductor Conference Template Optimization Profile Description 480p Conductor TS maximizeefficiency High scale, lower resolution at lower bandwidths thresholds 720p 0.8 Screen Licenses Used favorefficiency Balance of scale and experience, favors scale favorexperience* maximizeexperience *Default Optimization Profile Balance of scale and experience, favors resolution Lower scale, highest possible resolution at given bandwidth 720p 1080p Conductor TS 1.5 Screen Licenses Used 58

59 Example Optimized Conferencing TelePresence Server Standalone (7010, 8710) TelePresence Server with Conductor Audio Once full, additional endpoints cannot join 2Mbps 700kbps 3Mbps 3Mbps Audio 2Mbps 2Mbps 700kbps 370kbps 384kbps 384kbps 384kbps 2Mbps 384kbps 384kbps 384kbps 768kbps 768kbps 768kbps 768kbps 9 Mbps 9 Mbps 1 SL ½ SL Total participants: 20 (1080p30+C) (720p30+C) (480p30+C) (480p30) Total participants: 76 ⅓ SL ¼ SL C = HD 720p5 Content Channel 59 Optimization Profile: favorexperience

60 New experiences on TelePresence Server 60

61 Transparent name labels Active Speaker Indicator Overflow indicator Audio participant avatar Recording Indicator 61

62 Customization of the TelePresence Server 62

63 User experiences New in TS4.3 Available in March with TS 4.3 New Default Lobby and PIN Entry Screens New Default Audio Prompts New audio prompts now appear at the following events: PIN entry PIN entry where guest PIN is blank Incorrect PIN entered PIN retry limit hit Welcome screen Only participant with chair privilege joins conference. If Wait For Chair is disabled the audio prompt will occur when any participant joins. Guest waiting for chair to join before conference start Exit lobby 63

64 User experiences New in TS4.3 Available in March Conference Templates -> Advanced Parameters Custom Audio Prompts All text and voice prompts can be localized via the API. The customized audio file must be: 16 bit 16 khz sample rate WAV PCM format Maximum length 40 seconds Mono track Have the custom parameter point to a web server to access the files to play. Example JSON { "customwelcomescreenaudio":" "usecustomwelcomescreenaudio":true } 64

65 User experiences New in TS4.3 Available in March PROMPT NAME DEFAULT AUDIO CUSTOM AUDIO API COMMAND DEFAULT TEXT CUSTOM TEXT API COMMAND PIN entry PIN entry 2 Incorrect PIN entered Please enter the security PIN followed by # or press # to continue customoptionalpinentryaudio [empty] customoptionalpinentrymessage Please enter the security PIN followed by # custompinentryaudio [empty] custompinentrymessage You have not entered the PIN correctly, please try again custompinincorrectaudio [empty] custompinincorrectmessage Welcome to conference Welcome to the conference customwelcomescreenaudio [conference name] welcomescreenmessage Only chair in conference You are the only call in this conference customonlyparticipantaudio [empty] customonlyvideoparticipantmessage Guest waiting for chair to join Please wait until the host joins customwaitingforchairadio [empty] customwaitingforchairmessage Exit lobby 1 Exit lobby 2 PIN retry limit The conference has ended. Thank you for joining. customconferenceendedexitaudio [empty] customconferenceendedexitmessage This call has been disconnected. Thank customparticipantdisconnectedexitmes you for joining. customparticipantdisconnectedexitaudio [empty] sage You have not entered the PIN correctly. This call will be disconnected. Thank you for joining. custompinfailedexitaudio

66 User experiences New in TS4.3 Custom Lobby Screen Background (Preview Feature) Designed as a preview of the functionality Not recommended for production use Can be disable by Cisco in the future Limited assistance from TAC Support in remotely managed mode only Default Customized Available in March Can be used to display a customized background For example: Corporate Logo Separate background image per conference Up to 5 images in use at once Image requirements PNG Format 1920x1080 resolution 5MB max file size Example JSON { "custombackgroundimageurl":" } 66

67 Locally Managed mode Deprecated New in TS 4.3 TelePresence Server 4.2 was the last release to support Locally managed mode. From this release, 4.3(0.153) onwards Locally managed mode is no longer supported. TS 7010 and 8710 standalone use locally managed mode Fixed Configuration of ports Full HD limited to 1080p30/stereo/720p15 HD limited to 720p30/stereo/720p5 Participants are free to connect at resolutions below these maximums at each service level but they will always use one whole resource. ex.: 9971 connection uses Full HD or HD port 12 Ports 24 Ports 67

68 Multistreaming 68

69 Multstream User Experience Dual-Screen Endpoint Available with CE 8.0 Supports people+people experience Second display can show participants video when content is not being shared Without Multistream With Multistream 69

70 Multistream User Experience Single-Screen Endpoint Available with CE 8.0 Without Multistream With Multistream 70

71 Transcoded only Video TS 4.0 and lower In previous releases of TS, every call would be transcoded Each video stream is: Decoded by the TS Scaled as appropriate Composited into a layout Re-encoded into single video stream H.264 AVC TelePresence Server Decoders Compositor Scalers Encoder H.264 AVC Benefits Greatest possible interoperability No need for participants to drop to highest common resolution Drawbacks Increased latency due to decode/re-encode Limited layout options on receiving endpoint 71

72 Multistream Video Some endpoints have the capability to send multiple video streams to a bridge This can include multiple copies of the same stream at different resolutions 1080p, 720p and 360p H.264 SVC Switching Fabric H.264 SVC The bridge can then forward on (switch) the different resolutions to each endpoint depending on which streams they request The endpoint can locally compose these streams in a wide variety of combinations H.264 SVC Benefits Drawbacks Low latency, better video quality due to no decode/re-encode Requires endpoint support Wider variety of layout options for endpoint Requires higher bandwidth in certain situations In a multistream only environment many endpoints would not be supported The best answer is 72

73 Hybrid Conferencing - Multistream Best of both worlds, combining benefits of Multistream with the interoperability of transcoding As of TS 4.1, support on Multiparty Media 310, 320, 4x0v, MM 820 and vts platforms Multistream is available only on certain Cisco video endpoints Support via SIP only TS must be configured in remotely managed mode (requires Conductor) TS will continue to transcode video to/from legacy endpoints, and use Multistream switching wherever possible (Hybrid Conferencing) No change in TS scale, initial release will consume same amount of resources for Multistream calls as transcoded calls Note: Multistream applies to main video but content and audio streams remain fully transcoded SX20/MX200 G2/ MX300 G2 SX80/MX700/800 Max of 4 streams Max of 16 streams Max of 4 streams Max of 16 streams Required Infrastructure Unified CM 10.5(2) or later Conductor XC3.0 or later CE8.0 (off by default) TelePresence Server 4.1 or later on mm3x0, mm4x0v, mm820 (4.2) or vts 73

74 H.264 AVC Endpoints H.264 SVC Endpoints Hybrid Conferencing TS 4.1 and later Switching Fabric LD (ex. 180p, 360p) TelePresence Server H.264 SVC HD (ex. 1080p, 720p) H.264 SVC Decoder Encoder H.264 AVC Decoder Scaler Compositor Encoder 74

75 Hybrid Conferencing Configuring Multistreaming for Hybrid Conferences CUCM Ensure Allow ix Application Media is enabled within the SIP Profile applied to any SIP trunks the calls traverse (for instance the trunk to Conductor) Conductor On the Conference Template, ensure Enable ix protocol is not set to False. No need to check the box this works by default without configuring any additional parameters 75

76 Hybrid Conferencing SDP TelePresence Server will include sip.cisco.multistream in all outbound contact headers if multistream is enabled, regardless of far end support Multistream SDP will only be advertised once a corresponding sip.cisco.multistream has been received from the far end This is to avoid interoperability problems with devices that cannot handle the new SDP 76

77 Hybrid Conferencing SDP INVITE SIP/2.0 Via: SIP/2.0/TCP :5060;branch=z9hG4bKe1b8380a Max-Forwards: 70 From: "MST" <sip: >;tag=cf521deec To: Call-ID: CSeq: 3 INVITE User-Agent: Cisco TelePresence Server v4.1(1.58) Allow-Events: kpml Allow: INVITE,ACK,CANCEL,OPTIONS,UPDATE,INFO,SUBSCRIBE,NOTIFY,BYE Contact: <sip: :5060;transport=tcp>;isfocus;sip.cisco.multistream;x-cisco-tip;x-ciscomultiple-screen=1 Route: <sip:proxy-call-id= f22d-4ba5-97ce-c9c8790f9db0@ :5060;transport=tcp;lr> Route: <sip:proxy-call-id= f22d-4ba5-97ce-c9c8790f9db0@ :5060;transport=tcp;lr> Supported: timer,record-aware,x-cisco-callinfo Call-Info: <urn:x-cisco-remotecc:callinfo>;security=notauthenticated Session-Expires: 532;refresher=uas Min-SE: 90 Content-Type: application/sdp Content-Length:

78 Hybrid Conferencing Monitoring from TelePresence Server This SX20 is sending two streams to the TelePresence Server, one at 1080p and the other at 576p. The TelePresence Server is sending back three streams, all at 576p as this endpoint is using the equal layout 78

79 On Premise Collaboration Meeting Rooms (CMR) 79

80 Collaboration Meeting Rooms (CMRs) Concept Always available, personal meeting room that s virtualized Ability to support voice, video, and content sharing Any standards based endpoint supported including Jabber Seamless integration with WebEx, allowing ability to join via WebEx in their browser or from any mobile WebEx client. CMR 80

81 Converged Architecture Supports All Deployment Models + Cisco CMR Premises Cisco CMR Hybrid Cisco CMR Cloud Cisco TelePresence video infrastructure on premises at customer data center Cisco TelePresence video infrastructure on premises plus Cisco WebEx Hosted by Cisco WebEx One meeting: Scheduled, instant, or always-on personal meeting rooms with audio, video, and data sharing Broad endpoint support: Join and participate in meetings from mobile, desktop or room system 81

82 Other Sessions of Interest Session ID Date Time Title BRKCOL-2026 Fri, Feb. 19 9:00 am Deploying Cisco WebEx in Enterprise Networks BRKCOL-2607 Thu, Feb. 18 9:00 am Understanding Cloud and Hybrid Cloud Collaboration Deployment BRKCOL-2612 Tue, Feb :15 am Understanding WebEx Collaboration Meeting Room (CMR) Hybrid and Cloud BRKCOL-2614 Tue, Feb. 16 2:15 pm Technical Overview of Preferred Architecture for Enterprise Collaboration The PDF and recording of each session is available 3 weeks after the event finishes. 82

83 CMR Premises Cisco CMR Premises 83

84 Conductor and TMSPE Increasing scale and on premise video rollout New integration between Conductor and TMSPE Will require XC2.3, TMSPE 1.2 and TMS14.4 Utilizes new provisioning API on Conductor Easy provisioning and configuration of personal meeting rooms for up to 100,000 users TMS PE uses AD groups to assign new Conductor template configuration to users Conductor has new database which is Optimized for scale of aliases and templates Optimized for faster lookup Conductor will maintain 2 databases Direct Match database Regex database Alias Match? Alias Match? TMS+TMSPE (1) New db Direct Match db (API only) (2) Existing db Regex db (WebUI) API calls 1 2 New db Existing db New Call request comes to Conductor Alias Match? Search new db first for match If yes, proceed with rest to the workflow If no, go to existing db for search Search existing db for match If yes, proceed with rest of the workflow If no, reject the call Conductor WebUI 84

85 Increased scale on aliases and templates Supported Capabilities Services/Configuration XC2.3 or higher Direct Match db (CMR) Utilised Conference Bridges 30 MCUs or TelePresence Servers (2400 concurrent calls) XC2.3 or higher Regex db 30 MCUs or TelePresence Servers (2400 concurrent calls) Concurrent Active Conferences Preconfigured Conference Template Preconfigured Conference Aliases Preconfigured Auto-dialed Participants Preconfigured Auto-Dialed Participants per Conference Template 1,200 Conferences 1,200 Conferences 100,000 Conferences 1000 Conferences 100,000 Aliases *1000 Aliases 20,000 Users 20,000 Users 10 Active Favorites per Collaboration Meeting Room 5,000 participants per conference template *Lecture conferences require 2 aliases 85

86 Setup and Configuration 86

87 Import Users from Directory Server TMS PE Requirements: TMS 14.4 TMSPE 1.2 Conductor XC2.3 87

88 CMR Setup Add Conductor to TMS PE Requirements: TMS 14.4 TMSPE 1.2 Conductor XC2.3 Create new administrator user in Conductor Only allow API access. 88

89 CMR Template Setup Requirements: TMS 14.4 TMSPE 1.2 Conductor XC2.3 89

90 CMR Template Setup continued Requirements: TMS 14.4 TMSPE 1.2 Conductor XC2.3 90

91 CMR Template Setup - continued Requirements: TMS 14.4 TMSPE 1.2 Conductor XC2.3 91

92 CMR Setup Requirements: TMS 14.4 TMSPE 1.2 Conductor XC2.3 Send to users to create CMR 92

93 User CMR setup Requirements: TMS 14.4 TMSPE 1.2 Conductor XC2.3 93

94 User CMR setup Requirements: TMS 14.4 TMSPE 1.2 Conductor XC2.3 94

95 User CMR Setup Requirements: TMS 14.4 TMSPE 1.2 Conductor XC2.3 Template 95

96 CMR Premises New Features Improvements to the CMR templates Requirements: TMS 14.6 TMSPE 1.4 Conductor XC3.0 Enhancements Allows for separate Guest Pin Set Guest Pin Length Decide whether to put guests in lobby while waiting for host 96

97 CMR Premises User setup Requirements: TMS 14.6 TMSPE 1.4 Conductor XC3.0 97

98 CMR new features Host and Guest Pin Requirements: TMS 14.6 TMSPE 1.4 Conductor XC3.0 98

99 CMR new features Host and Guest Pin Requirements: TMS 14.6 TMSPE 1.4 Conductor XC3.0 Katie Host Dials: Unified CM Conductor TelePresence Server Enters Pin: 4344 Ben Guest Dials: Enters Pin:

100 User CMR setup Requirements: TMS 14.4 TMSPE 1.2 Conductor XC

101 Verify CMR setup - TMS How do you know it was created on Conductor? Requirements: TMS 14.4 TMSPE 1.2 Conductor XC2.3

102 Verify CMR setup - TMS How do you know it was created on Conductor? Requirements: TMS 14.4 TMSPE 1.2 Conductor XC Look at Provisioning page at Rooms column 2. Export room data XLS

103 Verify CMR - Conductor How do you know it was created on Conductor? Requirements: TMS 14.4 TMSPE 1.2 Conductor XC2.3 Status -> Logs -> Event Log conferencefactory.allied_api: Level="INFO" Event="An API request has been received." HTTP_method="'PUT'" Arguments="{'conf_bundle_id': u'33a e8b-b191-1ad f'}" HTTP_client_protocol="'HTTP/1.1'" URI="'/api/2.3/confbundles/33a e8b-b191-1ad f'" UTCTime=" :00:00,257" 103

104 Instant Meeting TS

105 CMR new features Webex Instant meeting Requirements: TMS 14.6 TMSPE 1.4 Conductor XC3.0 A new template option is now available Click to enable Instant Webex meeting on CMR Premise portal page Must have Webex enabled for CMR in TMS PE Administrative Tools > Configuration -> PE Settings Host can join any time to the meeting On the MCUs, guests must always wait for a host to join. On TelePresence Server, the Guest Lobby setting of the CMR determines the guests actions needed to join 105

106 CMR Premises New Features Transition CMR Premises to CMR Hybrid with WebEx Instant meeting Requirements: TMS 14.6 TMSPE 1.4 Conductor XC3.0 Prior to TMS 14.6, PE 1.4 and Conductor XC3.0, WebEx was only available via a scheduled conference (CMR Hybrid Scheduled) Now an Instant Webex Meeting can be created and join your CMR Premise. Click Results 106

107 New Instant Webex On Premise CMR What happens to make it work 3 Use Portal, click meeting button Meeting Host (PC) WebEx Participants 5 Clients are now able to join the Webex Create Instant Meeting 3 4 TS dials into Webex meeting TMS/PE Join CMR Meeting Host dials in to create CMR Meeting Participants 2 TS Conductor 1 Meeting Host 6 Webex meeting and TS Meeting are joined together in a single conference 107

108 Active Meeting Management 108

109 Available with March Active Meeting Management This is a feature preview. Limited assistance TAC support provided Feedback tms-marketing@cisco.com Full disclaimer in the TMSPE 1.6 release notes Requirements: TMS 15.1 TMSPE 1.6 Conductor XC4.1 Introduced for hosts to control their Collaboration Meeting Room (CMR) meetings A light-weight meeting management tool, which uses a web browser interface. Browser recommendations: Windows operating system Internet Explorer version 11 or higher Mozilla Firefox version 42 or higher Microsoft EDGE version 20 or higher MAC operating system Mozilla Firefox version 42 or higher Administrative Tools > Configuration > Provisioning Extension Setting Software Requirements: TMSPE 1.6 or higher TMS 15.1 or higher Windows Server 2012 Java 8 109

110 Active Meeting Management Available with March AMM includes the following features: Participants - Displays a list of active participants in the meeting Mute/Unmute All - Mute or Unmute all participants Remove All - Remove all participants Mute/Unmute - Mute or Unmute a specific participant Remove - Remove a specific participant 110

111 Conductor Usage Report 111

112 Conductor Usage Report Version 4.1 Available with March Allows an admin a report to look at history of bridge utilization Requires XC4.1 or higher Up to 10 GB of stored information Logging is automatically enabled Report formats are csv, json, or xml and has 33 different columns of information. 112

113 Conductor Usage report Clustered Conductors Up to 3 nodes can be in a Conductor cluster. Clustering nodes can have different types of events For a comprehensive report download a report from each node in the cluster in CSV format. Merge all the reports together and sort by Time column. Event Type resource_utilization_updated conference_start conference_end participant_connected participant_disconnected Where to find Any node Node where first participant connected Any node Node where participant connected Node where participant disconnected 113

114 MultiParty Licensing 114

115 Licensing Simplification with Multiparty Named Host Personal Multiparty Advanced CUWL Pro with Personal Multiparty Basic Yesterday + Shared Model Screen Licenses TelePresence Conductor Expressway RMS TMS Named Host CUWL Pro Includes Personal Multiparty (Advanced) Today + Shared Host SMP Includes endpoint registration license UCL/CUWL Endpoint Registration License 115

116 Centralized License Management One pool of Multiparty licenses New Multiparty Licensing Mode: PMP/SMP Licensing Centralized on Conductor Conductor All Multiparty TMS/PE Cost efficient: All platform capacity available for any meeting Capacity no longer bounded by screen licenses on individual servers Screen Licenses no longer used with PMP/SMP TelePresence Servers All resources available for any meeting (scheduled, personal or ad-hoc) Simplified scale and administration: Easily add new hardware and replace current platforms without re-configuring licenses Supports service models like follow the sun All TelePresence Server platforms supported: Virtualized MM410 appliance / blade; MSE Chassis with MM 820 or 8710 blade; TelePresence Server on legacy platforms 116

117 Multiparty Licensing: What's New? Personal Multiparty (PMP) Unlimited Participants per Full HD 1080p & Content Personal Multiparty Named host meeting license Included in CUWL Pro at no additional cost Replaces Personal Multiparty Basic, Previously known as Personal Multiparty Advanced Allows the host to use video; Personal CMR, Scheduled, or Ad-hoc The host gets a personal CMR Vanity URI & E164 number for video Includes all infrastructure components to get started Includes RMS for B2B & B2C or Lync Interop Ideal for frequent video users (Jabber, 8845/65, DX70/80) 117

118 Multiparty Licensing: What's New? Shared Multiparty (SMP) Unlimited Participants per Full HD 1080p & Content Shared Multiparty - shared host meeting license One license per concurrent meeting Purchase in bulk for conference rooms already purchased or with Cisco TelePresence Endpoints for reduced price Allows anyone to use video; Personal CMR, Scheduled, or Ad-hoc Every user gets personal CMR Vanity URI & E164 number for video Includes RMS for B2B & B2C or Lync Interop CUCM TelePresence room registration license included when bundled with TelePresence room endpoint at reduced price Ideal for occasional video users and VCS customers 118

119 Multiparty Licensing What is Included License Type PMP in CUWL Pro Initial Order PMP in CUWL Pro Follow on order PMP/SMP Minimum 25 1 per Minimum 1 (CUCM TP Room license with endpoint + SMP) SMP SMP Starter Pack (optional) NA Expressway Rich Media Session (RMS) Starter of per 20 CUWL Pro 2 per 20 CUWL Pro 2 per SMP NA Conductor Enterprise Virtual Edition TMS, TMS-XE, & TMS-PE Expressway Microsoft Lync Interop license 4 with initial order NA NA 2 Initial 10 plus 25 per 250 CUWL Pro 25 per add on order order NA Device license & XE licenses 1 per 250 CUWL Pro 1 per 250 CUWL Pro NA 1 Expressway C/E 6 each - existing UWL/UCL NA NA NA 119

120 Multiparty Licensing - PMP & SMP Key updates 1. PMP and or SMP license is allocated to a conference, not a participant s call. 2. No matter how many endpoints are in the conference, it consumes one license per conference. 3. Multiparty Licensing does not support MCU, but MCU can be used with its existing licensing. 120

121 Personal and Shared Multiparty Licenses Ad-hoc Conference using Personal Device GUID match? 4 TelePresence Conductor Multiparty Licensing TMS/PE 3 GUID Unified CM Active Directory 2 Personal Device Unified CM and TMSPE integrate to the common active directory User initiates ad-hoc conference from his personal device Unified CM (10.5 or higher) retrieves user s GUID from AD and passes it to Conductor in the conference create API call Conductor matches user s GUID against the PMP users list If a match is found, use PMP. Otherwise, use SMP Personal device has the Owner ID set to the user and its line appearance associated with the user 121

122 Personal and Shared Multiparty Licenses Ad-hoc Conference using Room System No PMP match 4 TelePresence Conductor Multiparty Licensing TMS/PE 3 NULL Unified CM Active Directory 2 MX Unified CM and TMSPE integrate to the common active directory User initiates ad-hoc conference from a room system (e.g. MX800) Room system is not associated with any user and hence, no GUID will be passed to Conductor in the conference create API call Conductor can t match any PMP user SMP will be used 122

123 Upgrade / Enable Multiparty Licensing TS: Upgrade to version 4.2 or greater TelePresence Conductor Unified CM MCU: No changes needed Multiparty Licensing Conductor: Upgrade to XC4.0 (need new release key) By default Multiparty Licensing mode will be disabled Manage bridge using HTTPS Install PMP/SMP options keys Enable Multiparty License mode TMS/PE Active Directory 123

124 Multiparty License Configuration Tips Minimal System Requirements: Conductor XC4.0 TMS 15.0 TMSPE 1.5 TS 4.2 TelePresence Conductor Multiparty Licensing TMS/PE Unified CM Ensure Conductor manages TS via HTTPS only All TS bridges will either be in multiparty license mode (if multiparty license enabled on Conductor) or not (if multiparty license disabled on Conductor) at any given time. Earlier TS versions do not support multiparty licensing mode. These will be unavailable if multiparty license mode is enabled. Screen licenses no longer needed to be installed on TP bridges if being used in multiparty license mode. Active Directory 124

125 Install PMP and SMP Option keys Default setup By default the Multiparty licenses is disabled. Status screen displays 0 licenses Need to add licenses to enable admin to change status. 125

126 Install PMP and SMP Option keys Maintenance > Option keys 1 Add SMP and PMP licenses as Option keys 2 Add SMP and PMP licenses as Option keys 3 Enable Multiparty licensing and review total number of licenses and status 126

127 Install PMP and SMP Option keys Multiple PMP, SMP options keys can be installed Option keys can be installed on any node in the cluster Total of counts of options keys across the cluster will be used for reporting, compliance checking 100 PMP License 10 PMP License 10 SMP License Cluster Total PMP = 110 SMP = 10 Cluster Total PMP = 120 SMP = 30 Note: If a cluster node where the option keys are installed goes down then the option keys will continue to be counted for 30 days on the remaining nodes 100 PMP License 10 PMP License 10 SMP License 10 PMP License 10 SMP License 10 SMP License 127

128 Enable Multiparty license mode

129 Provisioning through TMSPE

130 Provisioning through TMSPE

131 Provisioning through TMSPE 5 131

132 Acano Acquisition 132

133 Choosing the Right Option Guidance for Video Conferencing Focused Customers 1 Cloud WebEx or Spark customer Greenfield conferencing CMR Cloud Interop including S4B 2 Multiparty licensing CMR Premise or Hybrid Customer Ad-hoc escalation Multistream Triple Screen Support On-Prem 3 Rich Skype for Business (S4B) conferencing interoperability Public Sector: JITC and FIPS certifications Scalable on premise Audio and video conferencing Spark & WebEx Conferencing TP Server (Mulitparty Licensing) Acano (CUWL licensing) Hybrid Services (long term direction) 133

134 Acano Value Proposition 134

135 The Challenge - Technology barriers get in the way Audio conferencing Video conferencing Web conferencing IM clients 135

136 Chat, talk, meet and share in one place And more Presence Media IM - Content 136

137 Integration the silos 137

138 Acano Deployment flexibility Acano optimized server UCS Based / Virtualized Cloud 138

139 Audio conferencing Key features: Reduced costs Integrates with existing dial plan Customizable: - Multiple ways to join - Thresholds - DTMF - IVR Detailed reporting Scalable: 10,000 audio calls on 2U server

140 Video conferencing Key features: Outstanding interoperability Unlimited team spaces Flexibility and customization Platform-independent licensing Built-in SIP NAT traversal Security Multi-tenancy Standards: SVC/H.264UC (Lync 2013) RTVideo (Lync 2010) WebM/VP8 (WebRTC) High Profile H.264 (Polycom) TIP (Cisco Immersive Telepresence)

141 Browser based Key features: Anyone can join WebRTC: Chrome, Firefox, Opera Internet Explorer, Safari via app Bidirectional content Guest access or user login

142 S4B & Lync integration Key features: Seamlessly connects Skype for Business with other video systems Dual homed conferencing Bidirectional content sharing (RDP) Scheduled conferences Buddy list integration Skype audio and video support Native support: SVC/H.264UC (Lync 2013) RTVideo (Lync 2010) Direct federation to Office365 IM and Presence Multi-party conferencing Drag and drop

143 S4B Integration User Experience Up to 5 Video participants see Correct Lync layout Full participant list Using S4B Scheduling Multiple Lync participants seen Many layouts 143

144 Architectures 144

145 The Acano platform The Swiss Army Knife Acano Manager Future Functions Third Party Integration Third Party Application XMPP CallBridge TURN WebBridge Database Load Balancer H.323 SIP Edge Acano optimized server UCS / Virtualized Cloud 145

146 Generic architecture External DMZ LAN LYNC/S4B/S4C CLIENT LYNC EDGE LYNC FRONT END LYNC/S4B CLIENT SIP TRUNK WEBRTC ACANO EDGE ACANO CORE WEBRTC SIP H.323 SIP H.323 POLYCOM VIDEO SYSTEM VIDEO CALL CONTROL EDGE VIDEO CALL CONTROL CISCO VIDEO SYSTEM VOICE - PSTN IP PBX PHONE 146

147 Cisco + Acano Architecture S4B Conferencing Interop CUCM & Expressway-C* Lync Server Lync MCU Expressway-E Acano Conferencing & Edge Services Acano App Lync/S4B Standard based video Always-on personal room or Outlook-based scheduling (Acano Outlook plug-in) Multiple layout options controlled by Acano client or DTMF S4B integration: Dual home, bidirectional RDP, S4B dragand-drop Leverage Acano client for Web client or S4B Best user experience for multiple bridge cascade 147

148 Cisco with Acano Architecture at Close Jabber Deployed CUCM IM&P CUCM & Expressway-C ASA Expressway-E Acano Conferencing & Edge Services Acano App IM&P Federation Lync/S4B Standard based video Always-on personal room or Outlook-based scheduling (Acano Outlook plug-in) Multiple layout options controlled by Acano client or DTMF Interop including S4B integration with bidirectional RDP Leverage Acano client for Web client Best user experience for multiple bridge cascade 148

149 149

150 Distributed Spaces Spaces Spaces Spaces 150

151 S4B direct federation example Skype users Skype for Consumer Remote Lync / Lync Online Lync users WebRTC / Browser based access External DMZ Firewall Direct Federation Load Balancer SIP Edge TURN WebRTC Edge Server 1x internal IP for Management 1x internal IP (other subnet) for application Firewall Internal XMPP Call Bridge Core Server 1x internal IP for Management 1x internal IP (other subnet) for application Active Directory CUCM/ Other PBX VCS-C / Call Control Video Endpoints Video Endpoints Phones Jabber 151

152 Architecture example Cisco and Lync on-prem Skype users Lync users Skype for Consumer Remote Lync / O365 Video Endpoints WebRTC / Browser based access External DMZ Firewall Lync Edge Load Balancer TURN WebRTC Edge Server (VM) 1x internal IP for Management 1x internal IP (other subnet) for application Firewall Internal XMPP Call Bridge Core Server (Appliance) 1x internal IP for Management 1x internal IP (other subnet) for application Lync FE Pool Active Directory CUCM Lync users Phones 152

153 Closing 153

154 Top 3 Key Takeaways Multiparty licensing Utilizing a single licensing model (CUWLPro) Eliminated the need for resource limitation and moves to a conference model Acano acquisition will added great interoperability with Microsoft Lync/Skype for Business Great scale Cisco on premise portfolio is alive and well 154

155 Call to Action Attend the following related sessions BRKCOL-2026, BRKCOL-2607, BRKCOL-2612, BRKCOL-2614 all sessions are listed on Visit the World of Solutions for Cisco Campus Collaboration booth area: Demos D8, D10, D11, D12 Walk in Labs Technical Solution Clinics - Collaboration Meet the Engineer Available Wednesday 9am 12pm. Lunch and Learn Topics Cisco Jabber Tuesday Cisco Prime Collaboration Thursday Hosted Collaboration Solutions with Cloud Thursday 155

156 Complete Your Online Session Evaluation Please complete your online session evaluations after each session. Complete 4 session evaluations & the Overall Conference Evaluation (available from Thursday) to receive your Cisco Live T-shirt. All surveys can be completed via the Cisco Live Mobile App or the Communication Stations 156

157 Thank you 157

158