New aspects of Cisco UC Interoperability #CiscoPlus
What is integration? Is my home phone integrated with your home phone? Is my corporate email system federated with yours? Does integration imply connecting two of the same type of system or different systems? The objective: Let me collaborate with Anyone Anywhere
Cisco Collaboration Architecture Devices Collaboration Applications Client Services Collaboration Services Medianet Services Network Services Desktop Mobile In-Room Client Services Framework Presence / Location Session Mgmt Scheduling and Calendaring Workflow Transcoding Auto-Discovery Conferencing Enterprise Social Software Messaging COMMUNICATION Medianet Services Interface Real-time Messaging Real-time Data Sharing Authoring Recording/Playback Transrating Auto-Configuration CONTENT Customer Care IP Communications Telepresence Lightweight APIs Metadata Tagging Social Graphing Semantic Processing Search Transcribing Resource Control Transport Signaling QoS Security Services Identity Policy AAA Encryption Federation Management Services Operations Administration Maintenance Provisioning
Session Management
What is a Session Management Edition cluster? CUBE CUBE CUBE H323 Trunk MGCP Trunk SIP Trunk A CUCM cluster and SME cluster use exactly the same software A CUCM cluster is typically used to register 10,000s of Phones An SME cluster is typically used as a platform for Trunk and Dial Plan aggregation Both CUCM and SME support Voice, Video and Encrypted calls Support for SME deployments was introduced with UC version 7.1(2) UC version 8.5 introduces a number of features that enhance SME functionality : Improved SIP Trunk and H323 Inter Cluster Trunk functionality Improved through-cluster routing SIP Normalization and Transparency scripts
Why deploy Session Management Edition? An SME cluster at the core of your network allows you to flexibly manage your UC system as it grows and changes. PSTN Voicemail System CUBE CUBE Conferencing System Unified CM Session Management Edition Cluster H323 MGCP SIP CUCM Clusters with H323 QSIG Trunks to SME PBXs/ CUCM Clusters with SIP Trunks to SME CUCM Clusters with H323 Trunks to SME PBXs with MGCP QSIG Trunks to SME PBXs with MGCP Q931 Gateway Trunks CUCM/PBX with SIP QSIG Trunks to SME Leaf Unified CM Clusters/ Leaf UC Systems An SME cluster can interconnect 1000 s of UC systems using SIP, H323, or MGCP Trunks SME allows you to reduce UC system complexity by centralizing your dial plan and call routing rules in the SME cluster which in turn allows you to simplify the dial plan and management of the connected UC systems
Reasons for deploying an SME cluster PSTN Voicemail System CUBE CUBE Conferencing System Unified CM Session Management Edition Cluster H323 MGCP SIP CUCM Clusters with H323 QSIG Trunks to SME PBXs/ CUCM Clusters with SIP Trunks to SME CUCM Clusters with H323 Annex M1 Trunks to SME PBXs with MGCPTrunks to SME PBXs with MGCP Q931 Gateway Trunks CUCM/PBXs with SIP QSIG Trunks to SME A centralized Dial Plan in SME allows you to : Globalize and Normalize the called and calling numbers used by all Leaf systems Manage overlapping number ranges in Leaf systems Configure find me call routing using Route List and Route Groups Re-route calls via the PSTN when the device cannot be reached via and IP path SME Mobility features allow you to offer Single Number Reach functionality to devices on 3 rd Party UC systems SME Normalization scripts allow you to modify any inbound or outbound SIP message and SDP body content simplifying interoperability with 3 rd party UC systems
SME cluster - PBX aggregation SME migration to a CUCM cluster PSTN CUBE CUBE PSTN PSTN PSTN PSTN PSTN PSTN Phase 1 PBX Aggregation PSTN Phase 2 Centralized IP PSTN PSTN CUBE CUBE CUBE CUBE Phase 3 PBX decommissioning Phase 4 CUCM cluster
Extend and Connect Architecture & Call Flow Jabber Use Case CUCM Cisco Jabber client CTI Enterprise DN: 3000 CSF/Jabber device DVO-Enabled Office Phone 3000 Home Phone 4155551212 PSTN Remote Destination: 4155551212 Remote Destination: 9195551313 Cisco User PBX Phone 9196661313 3 rd Party PBX CTI applications have limited monitoring and call control capabilities for remote destinations
Extend and Connect Architecture & Call Flow CTI Remote Device Use Case CUCM CTI Enterprise DN: 3000 3 rd -Party client Cisco User Office Phone 3000 Home Phone 4155551212 PSTN Remote Destination: 4155551212 CTI Remote Device DVO-Enabled Remote Destination: 9195551313 PBX Phone 9195551313 3 rd Party PBX CTI applications have limited monitoring and call control capabilities for remote destinations
MS Lync Integration
Different options exist How to choose the right one? Full Microsoft UC Solution UC Gateway Blended: Microsoft Desktop + Cisco Phone Full Cisco UC Solution Cisco UC Integration for MOC or Lync Customer Deployment scenario Cisco Jabber 13
Cisco Unified Clients Cisco Soft Client Architecture Cisco Webex Connect Cisco Unified Personal Communicator Cisco UC Integration for Microsoft Cisco UC Integration for RTX Cisco Quad Phone Developer & Integrator SDK Cisco Unified Infrastructure Services
Cisco Jabber Introduction Cisco Enterprise Call Control Instant Messaging Jabber Technology Video & Desktop Share Engine Application Integration (MS Office) Cisco Secure Remote Access Conferencing Cisco Jabber & CuciLync Webex Collaboration Environment Cisco Unity Connection Voice Messaging
Cisco BYOD Architecture One network, One policy, Unified Management Good
Different options exist How to choose the right one? Full Microsoft UC Solution UC Gateway Blended: Microsoft Desktop + Cisco Phone Full Cisco UC Solution Cisco UC Integration for MOC or Lync Customer Deployment scenario Cisco Jabber 17
Cisco Collaboration Architecture Devices Collaboration Applications Client Services Collaboration Services Medianet Services Network Services Desktop Mobile In-Room Client Services Framework Presence / Location Session Mgmt Scheduling and Calendaring Workflow Transcoding Auto-Discovery Conferencing Enterprise Social Software Messaging COMMUNICATION Medianet Services Interface Real-time Messaging Real-time Data Sharing Authoring Recording/Playback Transrating Auto-Configuration CONTENT Customer Care IP Communications Telepresence Lightweight APIs Metadata Tagging Social Graphing Semantic Processing Search Transcribing Resource Control Transport Signaling QoS Security Services Identity Policy AAA Encryption Federation Management Services Operations Administration Maintenance Provisioning
Cisco UC Integration for Microsoft What is the Cisco Integration for Microsoft The UC Integration provides a Cisco UC client with controls exposed with the Microsoft client interface Provides phone presence to OCS/Lync Supports Microsoft Office Communicator R2 and Microsoft Lync 2010 Runs on Microsoft Windows XP SP3, Windows Vista 32/64bit and Windows 7 32/64bit Provides soft phone audio and video and desk phone control using UC manager call control Visual voicemail with Cisco Unity or Unity Connection Desktop collaboration using Cisco MeetingPlace and Webex Calling from Microsoft Office, Internet explorer and other applications
Cisco UC Integration for Microsoft Lync Microsoft Client Microsoft Office Communicator Microsoft Lync (shown) User Experience Simply drag or right click a contact to start a voice, video or collaboration session Conversation Voice, Video and Conference calling and in Call Controls Cisco Communication Panel Voicemail, Communications History, Soft phone / Desk phone control Options & Dial pad
Cisco UC Integration for Microsoft Lync High Definition Video for Rich Interactions Video calls both in Softphone and Desk Phone mode Point to Point & Multipoint calls High quality, standards-based H.264 video CIF, VGA and HD resolutions supported Interoperable with Cisco and 3rd party video solutions Leverages CUCM CAC to manage video traffic on the WAN
Cisco UC Integration for Microsoft Lync Phone Presence Availability in Lync is updated to reflect Softphone/Hardphone state Shows your current Softphone/Hardphone state to your contacts Users showed On the phone also for calls to Video Bridge, VC stations or any other video system (Cisco or Third Party)
Microsoft & Cisco Interoperability Use cases and Scenarios SIP-Trunk / Direct-SIP Audio OCS 2007 / Lync 2010 (no media bypass) Lync Clients Front-End Pool Mediation Server Pool CUCM RTaudio OCS 2007 / Lync 2010 (no media bypass), none G.711 on IP-PBX G.711 Lync Clients Front-End Pool Mediation Server Pool CUCM Transcoder RTaudio G.711 G.729/iLBC The two call flows above show the signaling and media paths in a SIP-trunk interoperability scenario. Lync Mediation Server ONLY supports G.711, requires additional transcoding resource if any other codec is used in such an scenario. With CUCM 8.x and above a MTP is not required in this configuration.
Microsoft & Cisco Interoperability Use cases and Scenarios SIP-Trunk / Direct-SIP Audio Lync 2010 (with media bypass) Lync Clients Front-End Pool Mediation Server Pool CUCM G.711 G.711 MTP With the introduction of Media Bypass in Lync 2010 the Lync client can initiate direct G.711 not requiring media to be transcoded in the Mediation Server. Signaling still has to flow via the Mediation Server. Media Bypass mandatorily requires all media to come from a single IP address. Which is the reason why a MTP has to be inserted into this scenario.
Video Integration with MS
Microsoft Lync 2010 - video capabilities summary Point to Point video call: o Still uses the RTVideo codec as default - CIF, VGA and HD (with Quad Core CPU) as possible resolutions o Single codec supported for interoperability with standard VC is H263 (max resolution is CIF@15fps) Multi-Point video call using Internal A/V MCU: o Support RTVideo codec only o Support CIF and VGA as resolutions (No HD) o Support Voice Activated Switching only (no Continuous Presence) o Utilize Microsoft CCCP as protocol to create, extend and manage the Multi-party Video Conference Content Sharing: o Use Microsoft specific solution both for Point to Point and Multi-Point calls (no BFCP support)
VCS and B2BUA Service Introduction VCS X7.0 introduces the concept of Back to Back User Agent (B2BUA): Service running on Lync-OCS Gateway VCS Keep standard based and OCS / Lync signalling separate Recommended scenario (Old way still supported in X7.x, not in X8.x) Simplified configuration (one menu with all the options listed together) Publishing VCS Presence into OCS/Lync is supported and strongly recommended to have a full User Experience Allows interoperability with OCS/Lync Clients connected from Internet through Microsoft Edge Server AMG is supported and improved in terms of features support (Call Transfer, Hold and Multi-way) End to End encryption for Media and Signaling
Lync / VCS Deployment Guide http://www.cisco.com/en/us/docs/telepresence/infrastructure/vcs/config_guide/ Cisco_VCS_Microsoft_OCS_2007_R2_and_Lync_2010_Deployment_Guide_X7-1.pdf
UC Gateway Solution for MS Video Interop UC Gateway Video Communication Server (VCS) Advanced Media Gateway (AMG) Scalable and resilient Interoperability with Microsoft OCS 2007 R2 and Lync 2010 Transcodes Microsoft RTV to HD or VGA standard compliant video codec
MS Office Integration
Microsoft & Cisco Interoperability Microsoft Applications enabled with Cisco Collaboration Microsoft SharePoint 2007 Cisco Presence Light-Ups W or d Microsoft Outlook 2007 Cisco Click to IM/Call
Microsoft & Cisco Interoperability Microsoft Applications enabled with Cisco Collaboration Microsoft Outlook 2010 Supported in CUPC 8.0(3) Cisco Presence Light-ups Cisco Click to IM/Call
Cisco Jabber
Introducing Cisco Jabber for Windows Cisco Jabber is our new UC and Collaboration client: User Interface and experience built to be highly intuitive. Full Office integration Standards based Interoperability Based on the second generation CSF, optimized in terms of memory and resource utilization Range of extensibility points and application integrations Also available for Mac
Voice & Video Call Control Jabber for Windows provides two call control options Enterprise Call control (ECC) o ECC allows a customer to integrate Jabber for Windows with Unified Communications Manager. o ECC provides control of a Cisco desktop phone as well as soft phone operation. o URI dialling planned with CUCM 9.0 Cloud Call Control [subject to change] o Only available in cloud deployment o Provides computer to computer calling between two users of the Webex cloud
Voice & Video Call Control Desk phone Control Soft phone Operation Users can select mode of operation using the system tray icon. Drop down list will provide a list of hardware/software associated to user. Users can be configured to use just desk phone, just soft phone or both.
The Cisco Precision Video Engine Precision Video Engine is a H.264 AVC software library designed to handle voice and video related tasks This library is based on the Video Engine used in the Cisco Movi product (*) Provides full HD interoperability between Jabber desktop clients and any standard based VC systems PVE also provides audio codecs G.711a/u, G.722, G.729a, ilbc (and subject to change AAC-LD, G.722.1) PVE supports frame size QCIF to 720p based on attached camera. Note: HD 720p will be possible using DUAL CORE CPU! (*) Note Movi has been recently renamed Cisco Jabber Video for TelePresence
Desktop Sharing Video Desktop Share is based on the BFCP standard. Video Desktop Share allow you to share your desktop not only with other Jabber clients but also Telepresence Systems and Rooms...how many customer are waiting for this? CUCM 8.6.x needed for BFCP support Point to Point and Multipoint (MCU based) scenario are possible Other Jabber Clients Personal Telepresence Systems Telepresence Rooms
Desktop Sharing Some Screen shot from Tobias Lab...
Searching for Contacts Search and dial bar Recent Contacts Returned Local Contacts Returned [subject to change] Auto detect AD/LDAP (on premise) Recommended pre 8.6(2) Client provides search across multiple contact record sources. UC Manager UDS Service (on premise) Recommend for 8.6(2) + Client uses predictive search to refine resolution list as you type. Webex Corporate Directory (Cloud) Directory Contacts Returned
Solution Summary Suggested approach for customer, advantages with Cisco standards based IPT/Video (LCS/OCS can be easily migrated to Jabber) Full Office integration Designed with the goal to optimize resource utilization (CSF2G) Supports standard based audio and video codecs High Definition 720p (with a Dual Core CPU), also for calls to Video Conference systems BFCP Desktop Sharing with any standard Video Device
Q&A
We value your feedback. Please be sure to complete the Evaluation Form for this session. Access today s presentations at cisco.com/ca/plus Follow @CiscoCanada and join the conversation #CiscoPlus