Thank you for attending the Cisco Plus Canada Roadshow

Transcription

1 Thank you for attending the Cisco Plus Canada Roadshow and join the conversation Access today s presentations at cisco.com/ca/ciscoplus

2 Unifying Voice & Video with Communications Manager

3 Generally Accepted Accounting Principals (GAAP) and Forward-Looking Statements Many of the products and features described herein remain in varying stages of development and will be offered on a when-and-if-available basis. This roadmap is subject to change at the sole discretion of Cisco, and Cisco will have no liability for delay in the delivery or failure to deliver any of the products or features set forth in this document. Actual performance and environmental costs of Cisco products will vary depending on individual customer configurations and conditions.

4 Product Focus for this Presentation All shipping by end of CY11 60 / 90 MX200 / C-Series TE 4.1 TC 5.0 TC 5.0 CTS / 1.8 Desktop Video Personal Multipurpose and Solution Components Immersive Unified Communications Manager (UCM) 8.6 Video Communications Server / Expressway (VCS) 6.1 / 7.0 Telepresence Server 7010/ Telepresence MCU 4500/ / 4.3

5 Unified Communications with Enhanced Video and TelePresence Services Video Communications Server (VCS) Expressway Firewall Traversal Inter-Company and Teleworker Unified Cisco TelePresence Conductor SIP Communications Multipoint Services 3rd-party video endpoints H.323 video endpoints SIP to H.323 interworking Microsoft OCS interoperability via Advanced Media Gateway 3 rd Party / H.323 Endpoints

6 Desktop Video and TelePresence Endpoints Portfolio Supported on UC Manager 8.6 Immersive Solution Platforms CTS-3210 CTS-3010 Multipurpose Quick Set 20 C40, C60, C90 Desktop Cius Cisco Personal Series CTS-500 Series MX Series Profile Series CTS-1300 Series Web 8900, 9900 Series Jabber, CUPC, CUCILync Web Collaboration Desktop Video Telepresence Interoperability / Inter-Company

7 April 2010: At Acquisition Close Separate solutions - bridged together via TelePresence Server UC Endpoints UC Manager VCS Control CTS 500 Profile CTS 3010 TelePresence Server SIP H.323 Media CTS endpoints only supported proprietary MUX protocol Minimal interoperability between UC Manager and VCS Control TelePresence Server (or MXE) required to bridge between these worlds

8 What We ve Been Up To Areas of integration focus since acquisition close Medianet Cisco Discovery Protocol, auxiliary VLANs, Auto QoS, location awareness (now) Mediatrace and Metadata (planned for CY12) Provisioning and registration of TANDBERG endpoints on UC Manager in UC Manager 8.5(1) and C-Series in UC Manager 8.6(1) MX200 in UC Manager 8.6(2) Interoperability between UC Manager and VCS SIP trunking Alpha-numeric URI routing BFCP, encryption and media negotiation enhancements TelePresence MCU on UC Manager UCM endpoints can now use TelePresence MCU as ad hoc conferencing resource Standards-based H.264 support on CTS endpoints CTS endpoints now natively compatible with standards-based H.264 endpoints and MCUs TIP and One Button to Push scheduling extended to TANDBERG endpoints and C-Series interoperable with CTMS and schedule able by CTS-Manager CTS endpoints schedule able by TMS TIP protocol succession to standards-bodies

9 Endpoints Can Now Be Deployed Perspective: Telepresence endpoints on UCM and VCS. Other scenarios omitted UC endpoints CTS UC Manager VCS Control VCS Expressway Internet here C-Series / MX200 SIP H.323 here Movi C-Series / MX200 and here TelePresence and UC endpoints on the same UCM cluster,, MX200 and C-Series endpoints can now be deployed on UC Manager Any-to-any native interoperability between all endpoints UCM-VCS SIP Trunking enhancements for maximum interoperability Movi

10 Multipoint Devices Can Now Be Deployed Perspective: Telepresence multipoint devices on UCM and VCS. Other scenarios omitted UC Manager VCS Control VCS Expressway Internet here here and here CTMS MCU TS TS MCU SIP H / 8500 series MCUs deployed on UCM for Conf / Join / Barge features on UC endpoints 4500 / 8500 series MCUs deployed on VCS for Add Participant / Join Participant features on VCS endpoints 4500 / 8500 series MCUs deployed on VCS, or trunked to UCM, for rendezvous/scheduled dial in meetings (single-screen only) 7010 / 8700 series TelePresence Servers deployed on VCS, or trunked to UCM, for rendezvous/scheduled dial in meetings (single-screen or TIP) CTMS deployed on UCM for rendezvous/scheduled dial in conferences (TIP only)

11 Scheduling Perspective: Telepresence endpoints on UCM and VCS. Other scenarios omitted CTS CTS-MAN UC Manager or VCS Control TMS VCS Expressway Internet Movi SIP H.323 C-Series C-Series CTS-MAN 1.8 can now schedule, C-Series and MX200 endpoints registered to UCM or VCS CTS-MAN 1.8 supports CTMS and TelePresence Server 7010 / 8700 as bridge types TMS 13.1 can now schedule CTS endpoints registered to UCM /C-Series/MX200 must be registered to VCS when using TMS 13.1 TMS 13.1 supports TelePresence Server 7010 / 8700 and MCU 4500 / 8500 as bridge types Movi

12 ,, MX200 and C-Series on UCM 8.6 Perspective: When registered to UC Manager Remaining Gaps Register endpoints to VCS when these features are required Encryption (planned for TE6.0/TC6.0 release in 1HCY2012) Ad hoc conferencing Add Participant and Join features (planned for TE6.0/TC6.0 release in 1HCY2012) Alpha-numeric URI registration (planned for UCM 9.0 release in 1HCY2012) H.323 registration (No plans to support on UCM. Continue to use VCS for H.323 endpoints) IPv6 (planned for later release) Registering through VCS Expressway (Teleworker) (use Cisco 800 series IOS router Virtual Office solution for endpoints on UCM) TMS scheduling and management of TE/TC endpoints on UCM (planned for TMS 13.2 release in 1HCY2012) Movi support on UCM (Movi PVE in Jabber release planned for 1HCY2012)

13 TelePresence Endpoints in UCM 8.6 CTS and introduced in UCM 8.5(1) Also back ported to 7.1(5) and 8.0(3) introduced in UCM 8.5(1) Additional enhancements in 8.6(1) and 8.6(2) and C-Series introduced in UCM 8.6(1) MX200, Profile 42 (C40) and CTS-Manager support introduced in 8.6(2) and also available in latest 8.6(1) device pack

14 UC Manager Line-Side Features Supported on,, MX200 and C-Series

15 Features Supported / Not Supported Perspective:,, MX200 and C-Series endpoints registered to UC Manager Networking & QoS Cisco Discovery Protocol Auxiliary VLANs Medianet: AutoQoS / Smartports DSCP and 802.1p as per UCM service parameters Discard 802.1Q/p tagged frames received on PC port RTP port range as per UCM service parameters 802.1X Aux-VLAN override and MAC-Auth Bypass x 802.1X Proxy-EPOL Logoff 802.1X Supplicant Provisioning DHCP Option 150 Automatic configuration and firmware downloads HTTP port 6970, not TFTP device defaults and device specific loads HTTP/SSH enable/disable x HTTP/SSH username/password (planned for TE/TC6.0) Registration and Signaling Auto-Registration SIP - Non Secure SIP - Digest Authentication x SIP TLS (planned for TE/TC6.0) Primary UCM node x Secondary/Tertiary UCM nodes x SRST Register using E.164 (Directory Number) x Register using Alpha-numeric URI (planned for TE/TC6.0) x H.323 Service Control Events Reset / Restart / Check Config x Firmware downloads in background x Call Preservation

16 Features Supported / Not Supported Perspective:,, MX200 and C-Series endpoints registered to UC Manager Directories Corporate Directory Personal Favorites / Speed dials x Personal Directory x TMS-style hierarchical phone books x UCM-TMS common directory integration Localization User Interface Local (chosen locally on the phone, not provisioned in UCM) x Network locals (tones / cadences) Enhanced Shared Line Appearances ( only) Remote State Notifications Hold / Resume cbarge Unified Mobility Hand-off from mobile to desk x Hand-off from desk to mobile Calling Features Enbloc dialing x Off-Hook dialing - KPML x Forced Auth Codes / Client Matter Codes Alpha-numeric URI dialing +, * and # character dialing Hold / Resume Transfer Blind Attended x Early Attended Line Appearance Multiple calls on single line appearance (1 active, 4 held) x Multiple Line Appearances Call Forwarding Busy, No Answer, No Coverage, Unregistered x All supported only on (planned for TE6.0 on ) x Park / Pickup Music on Hold Unicast x Multicast

17 Features Supported / Not Supported Perspective:,, MX200 and C-Series endpoints registered to UC Manager Conferencing Multisite (embedded) x Multiway (when registered to UCM) (planned for TE/TC6.0) Multiway (when registered to VCS) DTMF RFC 2833 x KPML (planned for TE/TC6.0) srtp Media Encryption TIP x When registered to UCM (planned for TE/TC6.0) When registered to VCS and C-Series only Single-screen, single audio stream profile Voic Voic pilot provisioned by UCM ( only, series support planned for TE6.0) Message Waiting Indication ( only, series support planned for TE6.0) Contact Center CTI Monitoring of device availability x CTI Remote Call Control (remote-cc) (planned for TE/TC6.0) Licensing CUWL and CUCL x Release Keys and Option Keys provisioned in UCM XML / Java Applications Experimental Java apps on x Extension Mobility One Button to Push, C-Series and MX200 x Using CTS-Manager Using TMS (when registered to VCS) On Touch 8 On OSD UI

18 CDP and VLAN Details

19 CDP and Auxiliary VLANs Perspective:,, MX200 and C-Series endpoints registered to UC Manager Prior to CDP, TANDBERG endpoints supported 802.1Q, but had to be manually configured Tagged (with VLAN ID specified) Untagged Default = Untagged CDP introduced in release TE4.0, and / C-Series release TC5.0 Auto (use CDP) Automatically enabled when CUCM provisioning mode is selected Manual (equivalent to Tagged in previous releases) User must manually set the VLAN ID. If VLAN ID is received from CDP the ID received from CDP will take precedence over the manually configured value Off (equivalent to Untagged in previous releases Ignores VLAN ID received from CDP Default = Off to preserve existing behavior for installed base customers upgrading to TE4.1 and TC5.0 For more information TE4.1 Administrators Guide TC5.0 Administrators Guide

20 802.1Q/p and DSCP Perspective:,, MX200 and C-Series endpoints registered to UC Manager Endpoint will advertise itself to the switch using CDP Capability TLV = Host/Phone (0x90) AutoQoS Switch can automatically extend trust to the endpoint trust-cos recommended for endpoints that have a PC port (, 60, 90) trust-dscp recommended for endpoints that do not have a PC port (MX200, C20/40/60/90) PC Port Ethernet frames arriving on PC port with 802.1Q/p headers will be dropped (as opposed to stripping the header and forwarding untagged) DSCP values and RTP ports Endpoint will use DSCP and 802.1p values assigned by UC Manager DSCP for Audio Calls (EF) maps to 802.1p CoS 5 DSCP for TelePresence Calls (CS4) maps to 802.1p CoS 4 Endpoint will use RTP port range assigned by UC Manager

21 Bootstrapping Perspective:,, MX200 and C-Series endpoints registered to UC Manager Upon bootup from factory default state (VLAN mode = Off by default) 1. Do an untagged DHCP request, receive an address in the Data VLAN 2. Prompt the user for language choice and provisioning mode 3. If CUCM mode selected: a) set VLAN mode = Auto b) restart network stack c) do a tagged DHCP request (with option 150) to receive a new address in the Aux VLAN 4. Look for DHCP Option 150 in Aux VLAN DHCP Offer. a) if present, proceed to step 5 b) otherwise prompt user for CUCM provisioning address 5. Download configuration and firmware from UCM via HTTP port 6970, upgrade firmware and reboot if necessary 6. Register with UC Manager Save above settings for all subsequent reboots

22 Media Encryption Details

23 Media Encryption Example Scenarios UC Manager CTS TLS TLS VCS Control VCS Expressway Internet 9971 TLS TLS no TLS C-Series Point-2-Point CTS //C on UCM //C on VCS VTG endpoints (e.g. 9971) CTS Encrypted (dtls) Non-Secure 1 Encrypted (SDES) Encrypted (SDES) (audio-only 2 ) //C on UCM Non-secure 1 Non-Secure 1 Non-Secure 1 Non-Secure 1 SIP H planned for TE/TC6.0 2 planned for 1HCY12 //C on VCS Encrypted Non-Secure 1 Encrypted (SDES) Encrypted (SDES) (audio-only 2 ) Video telephony endpoints (e.g. 9971) Encrypted (audio-only) Non-Secure 1 Encrypted (SDES) (audio-only 2 ) Encrypted (SDES) (audio-only 2 )

24 Media Encryption Example Scenarios UC Manager VCS Control VCS Expressway Internet TLS TLS TLS CTMS MCU TS MCU Multipoint CTMS TS 7000/8700 MCU 4500/8500 CTS Encrypted (dtls) Encrypted (dtls) Encrypted (SDES) //C on UCM Non-secure 1 Non-Secure 1 Non-Secure 1 SIP H planned for TE/TC6.0 2 planned for 1HCY12 //C on VCS Video telephony endpoints (e.g. 9971) N/A Encrypted (SDES) Encrypted (SDES) /C Non-secure 1 N/A Encrypted (SDES) (audio-only 2 ) Encrypted (SDES) (audio-only 2 )

25 Alpha-Numeric URI Details

26 Alpha-Numeric URI Example Scenario UC Manager VCS Control VCS Expressway CTS Internet Register with E.164 only Register URI and E.164 C-Series Movi URI only 2 3 Register URI and E.164 URI only Movi C-Series UCM to VCS To: bob@cisco.com From: Alice @cisco.com Bob sees call coming from: Alice @cisco.com 1 SIP H.323 user Alice dials bob@cisco.com 4 User can call Alice back at: VCS and routes call to UCM

27 Alpha-Numeric URI Caveats CTS endpoints, UC endpoints, PSTN (H.320, Mobile) endpoints cannot dial alpha-numeric URIs. To enable this, VCS must either: VCS endpoints must register with both a SIP alpha-numeric URI and an H.323 E.164 address or else they have no way to be called from these types of endpoints VCS must translate E.164 addresses to alpha-numeric URIs (e.g. via ENUM) Directory lookups which contain alpha-numeric URIs are dial able by CTS 1.8 endpoints. However, UC Manager only has a single field (telephonenumber) which may contain either a numeric number or an alpha-numeric URI, but not both, so you have to choose which one you want to use for each user entry in the directory CTS endpoints plan to support dialing alpha-numeric URIs in CY12 via the Touch 12 user interface

28 Ad Hoc Conferencing Details

29 MultiSite Perspective: TTG endpoints registered to UCM or VCS UC Manager CTS VCS Control VCS Expressway Internet Movi Movi 90 Profile 52 Dual (C60) C-Series / MX200 SIP H.323 Media Multisite Host Multisite-capable endpoints can host multisite meetings, and any endpoint can participate in Multisite meetings, regardless of whether they are registered to UCM or VCS 90, C40, C60, C90 endpoints are Multisite-capable

30 Multiway Perspective: TTG endpoints registered to UCM or VCS UC Manager CTS VCS Control VCS Expressway Internet MCU Movi Movi 90 C-Series / MX200 C-Series / MX200 SIP H.323 Media Multiway Initiator Multiway meetings can only be initiated by TTG endpoints registered to VCS, but any endpoint can be a participant in a Multiway meeting Ad hoc initiation support on,, MX200 and C- Series endpoints registered to UCM is planned for TE/TC6.0

31 UC Manager Ad Hoc Conf/Join/Barge Perspective: TTG endpoints registered to UCM or VCS, invited to an ad hoc conference by a UC endpoint UC Manager CTS VCS Control VCS Expressway Internet 9971 MCU Movi Movi 90 C-Series / MX200 C-Series / MX200 SIP H.323 Media Conference Initiator UC endpoints can use their Conf / Join / Barge softkeys and invoke an ad hoc conference on an MCU which is directly registered to UC Manager. MCU(s) must be dedicated to UC Manager for this feature Any endpoint can be a participant, regardless of where they are registered Ad hoc initiation support on,, MX200 and C-Series endpoints registered to UCM is planned for TE/TC6.0 Ad hoc initiation support on CTS endpoints is planned for 2HCY12

32 Voic Integration Details

33 Unity Voic Integration Perspective: TTG endpoints registered to UCM and VCS CTS Unity UC Manager VCS Control VCS Expressway Internet Movi Movi 90 C-Series / MX200 C-Series / MX200 SIP H.323 Endpoints registered to either VCS or UCM call the on UCM. Call forwards to voic on Busy No Answer. receives MWI notification from Unity and can press the messages button to retrieve its messages In order to reply to the sender or call-back the sender, sender must have provided its numeric address to Unity. VCS can source re-write the callers URIs to the numeric alias assigned to the users FindMe account only if directly integrated with Unity

34 Endpoints: Moving Forward

35 Series Endpoint Priorities for CY12 Personal TelePresence + Unified Communications Higher demand for ad hoc meetings and personalized experiences

36 Key Takeaways VCS and CUCM form the core control for all endpoints VCS remains a key component of the video architecture moving forward CUCM now offers wider support for both endpoints and MCUs to register/trunk directly Cisco is dedicated to providing a rich, collaborative experience across it s portfolio, leveraging interoperable standards based protocols

37 Q&A

38 We value your feedback. Please be sure to complete Event Eval Form. Access today s presentations at cisco.com/ca/ciscoplus and join the conversation

39