Designing and Deploying Desktop Unified Communications TECUCC-2611 Content Map Servers & Services (On Prem / SaaS) Microsoft Cisco Unified Cisco Webex Presence Server Integration Desktop Cisco On Cisco Microsoft Premise SaaS Clients Integration TECUCC-2611 © 2011 Cisco and/or its affiliates. All rights reserved. Cisco Public 2 Cisco Unified Presence TECUCC-2611 © 2011 Cisco and/or its affiliates. All rights reserved. Cisco Public 4 Content Map – On Premise Servers & Services (On Prem / SaaS) Microsoft Cisco Unified Cisco Webex Presence Server Integration Desktop Cisco On Cisco Microsoft Premise SaaS Clients Integration TECUCC-2611 © 2011 Cisco and/or its affiliates. All rights reserved. Cisco Public 5 What is Presence? . What is “Presence”? –Information about a person‟s Available willingness and availability to Away communicate Idle . Examples of presence Offline –“Busy” tone on traditional phone –Contact Centre Agent status –IM “Buddy List” status indication TECUCC-2611 © 2011 Cisco and/or its affiliates. All rights reserved. Cisco Public 6 Two Major Architectures for IM and Presence SIP XMPP TECUCC-2611 © 2011 Cisco and/or its affiliates. All rights reserved. Cisco Public 7 Unlock Potential of Presence In the Enterprise SIP/SIMPLE BORDERLESS COLLABORATION XMPP Rich B2B & B2C Dual Standards support Federation Extensible SCALABILITY Open Presence Unified Enable Business Process SECURITY POLICY COMPLIANCE Enterprise-class Presence Applications TECUCC-2611 © 2011 Cisco and/or its affiliates. All rights reserved. Cisco Public beyond IM 8 Cisco Unified Presence (Always-on Presence) CSF Clients SIP/SIMPLE REST CUCM SOAP - API‟s SIP & call webex CAXL control Cisco Unified Client Services Framework Rich Network Presence to Webex CUMA SIP UC XMPP (Telephony & Calendar CUMC integrations integrations Presence to cloud) „CUP 8.x‟ CUAE Jabber APIs serverVOS Jabber Werx Expert CUAE Plugin Advisor XMPP Agent Desktop Contact webex Centre Note: Other existing CUP functions CUPC 7.0 IM & Presence continue to be supported: (incl. MAC support) MS Exchange Federations - MS Client mode (OCS RCC) Calendaring - SIP Proxy Webex, OCS, IBM, AOL - IBM TECUCCTelephony-2611 Presence integration© 2011 Cisco and/or its affiliates. All rights reserved. Cisco Public Jabber XCP, GoogleTalk 9 What is XMPP? TECUCC-2611 © 2011 Cisco and/or its affiliates. All rights reserved. Cisco Public 10 What is XMPP? . eXtensible Messaging and Presence Protocol . XMPP is -- open standard, published by the IETF, that uses XML to exchange information. Bi-directional streaming XML (XML gives readability) . Core: IETF RFC 3920, 3921 . Goals: –Simplified clients –Federate everything TECUCC-2611 © 2011 Cisco and/or its affiliates. All rights reserved. Cisco Public 11 XMPP Basics . You have a client that connects to and authenticates to a server. 2 main types of Connections – Client to Server Connections – Server to Server Connections . Users are uniquely identified by their JID, in the form [email protected], eg [email protected] TECUCC-2611 © 2011 Cisco and/or its affiliates. All rights reserved. Cisco Public 12 Jabber ID (JID) . All Entities in XMPP must have a Jabber ID. (e.g. a server, a component, a conference room, a user on a client) . Entities are identified by their JID. JID for a user is typically made up of 3 main components: . “node@domain/resource” . node – username e.g. a client‟s username on the server or a room name for conference. domain – primary identifier; usually identifies the server (FQDN) . resource – identifier for the users specific entity. Allows a user to have multiple devices or locations. (e.g. laptop, pda, etc.) . The domain identifier is the only required identifier, node and resource identifier allow for increased granularity for user, room, or device. TECUCC-2611 © 2011 Cisco and/or its affiliates. All rights reserved. Cisco Public 13 XMPP Architecture TECUCC-2611 © 2011 Cisco and/or its affiliates. All rights reserved. Cisco Public 14 XMPP Connections / Streams . 2 main types of Connections – Client to Server Connections – Server to Server Connections . Streams –“A stream is a container for the exchange of XML elements / stanzas between two entities over a XMPP network” . TCP connection between client and server (port 5222) TECUCC-2611 © 2011 Cisco and/or its affiliates. All rights reserved. Cisco Public 15 XMPP Stream Example | ----------------------------------| ---------------------------------- | | | <stream>| <stream> | | open stream A stream starts with <stream>, |-----------------------------------|----------------------------------- | | then an open-ended series of | | <presence><presence> | | stanza <presence>, <message>, and | | <show/><show/> | | <iq> tags are sent. | | </presence></presence> | | |-----------------------------------|----------------------------------- | | | <message to = ‘foo’> | stanza When the closing </stream> tag | <message to = „foo‟> | | | <body/><body/> | | is sent, underlying TCP | | </message></message> | | |----------------------------------- | connection torn down |-----------------------------------| | ………. | more stanzas | ………. | |----------------------------------- | |</stream>|----------------------------------- | | close stream |-----------------------------------|</stream> | | |-----------------------------------| TECUCC-2611 © 2011 Cisco and/or its affiliates. All rights reserved. Cisco Public 16 Core XMPP Messages/Stanzas . „Stanzas‟ are XMPP (XML child elements of <stream>) messages sent within a Element/Stanza Types stream or XMPP session. <message> Normal, chat, groupchat, headline, error . 3 main stanzas defined in XMPP –<message> - client pushes a message <iq> Get, set, result, error (e.g. IM message) to another client. –<iq> - info/query. IQ stanza messages are <presence> available, unavailable, get/set and have an associated response. subscribe, subscribed, unsubscribe, unsubscribed, (result or error). error –<presence> - used to update or publish a users presence. TECUCC-2611 © 2011 Cisco and/or its affiliates. All rights reserved. Cisco Public 17 XMPP Stanza Attributes 5 Common Stanza Attributes: to: „ address/JID of recipient‟ from: „ address of sender‟ id: „ for tracking command/response in <iq> stanza type: „ purpose or context of message, presence or iq stanza xml:lang: default language Example XMPP Message <message> to='[email protected]' from='[email protected]/balcony' type='chat' xml:lang='en'> <body>Wherefore art thou, Romeo?</body> </message> TECUCC-2611 © 2011 Cisco and/or its affiliates. All rights reserved. Cisco Public 18 Example - Message Stanza The message stanza can contains up to three child elements <subject/> - the subject or title of the message <body/> - the main body of the message <thread/> - unique identifier linked to a conversation. Example: <message> to=„[email protected]' from=„[email protected]' type='chat'> <subject> Team meeting </subject> <body>Hey – I want to have that meeting today! </body> <thread>A4567423</thread> </message> TECUCC-2611 © 2011 Cisco and/or its affiliates. All rights reserved. Cisco Public 19 Example – Presence Stanza The presence stanza contains up to three child elements. <show/> - users availability: away, chat, dnd, normal or xa <status/> - qualifier for availability – a text string containing more information e.g. “on the phone” <priority/> - priority of this entity (defines the priority of this resource) Example: <presence> from=„[email protected]/Work' to=„[email protected]' > <show>chat</show> <status>coffee break</status> <priority>5</priority> </presence> TECUCC-2611 © 2011 Cisco and/or its affiliates. All rights reserved. Cisco Public 20 Cisco Unified Presence 8.5 Architecture TECUCC-2611 © 2011 Cisco and/or its affiliates. All rights reserved. Cisco Public 21 Cisco Unified Presence Components Unified Mobility Advantage Third Party MeetingPlace Open API Cisco Unity/Unity Carriers / Microsoft CUMA Connection Exchange other vendors IBM Lotus PBXs Sametime Cisco WebEx Jabber GoogleTalk Cisco Unified Microsoft Presence 8.5 Unified CM 6.x, 7.x, 8.x LCS/OCS LDAPv3 XMPP WebDAV/EWS LDAP SIP/SIMPLE CTI/QBE Unified Personal CSTA over SIP Communicator 8.x SCCP Third Party H.323 XMPP Unified Personal IMAP SOAP Client Communicator 7.x HTTP/HTTPS JTAPI TECUCC-2611 © 2011 Cisco and/or its affiliates. All rights reserved. Cisco Public 22 Cisco Unified Presence 8.x Architecture Cisco Unified CUMA Presence 8.x Unified CM AXL/SOAP Unified CM Unified Personal Unified Mobility Sync Agents Communicator 7.x Advantage 7.x Microsoft Cisco Calendar Exchange Expert Agent Advisor Desktop Third Party Open API ICM Unified Application SIP/SIMPLE SIP/SIMPLE Environment SIP Proxy SIP Interface Presence Engine / Instant Message Bridge XMPP Unified Personal XCP Route Fabric Communicator 8.x Third Party XMPP Third Party XMPP Client Jabber Session Manager Compliance (Spark, Adium, Pidgin, MomentIM, etc) Server Instant Messaging XDB Compliance and Expert Logging future Cisco ODBC Advisor Agent Jabber XCP PostgreSQL Desktop TECUCC-2611 © 2011 Cisco and/or its affiliates. All rights reserved. Cisco Public 23 SIP and XMPP Client Interoperability Cisco Unified Unified CM CUMA Presence 8.x Unified CM AXL/SOAP Unified Personal Unified Mobility Sync Agents Communicator 7.x Advantage 7.x Cisco Calendar Expert Agent Advisor Desktop Third Party Open API Unified Application ICM Environment SIP Proxy SIP Interface All messages, SIP Presence Engine / Instant Message Bridge and XMPP, are routed through the Jabber Unified Personal XCP Route Fabric Session Manager. Communicator 8.x Third Party