Cisco Unified Communications and Microsoft Integrations Darren Henwood, Technical Solution Architect Common Customer Situations Windows Phones Office IP Communicator Video Endpoints Lync (IM&P) Lync (P2P) Video Bridges 3 Agenda Office Client System Meeting Integration Integration Integration Integration 4 Office Integration 5 Outlook Integration 2010/2013 2016 6 Contact Card Integration Contact Card Integration • Cisco Jabber for Windows uses published Microsoft Office APIs to provide Cisco communications tasks directly from Office applications Presence Instantly view the availability of your contacts Chat / IM Voice/Video Launch Jabber chat Launch Jabber high definition sessions directly from video calls directly from Office Office Contact Card Contact Card 7 Microsoft SharePoint Integration Adam McKenzie 8 Requirements AD [HKEY_CURRENT_USER\Software\IM Providers\Cisco Jabber] "UpAndRunning"=dword:00000002 9 Application Interoperability Additional Integrations Powered by Cisco Jabber… Outlook Web Access (OWA) integration with Cisco Jabber Web SDK http://www.pstech.rs/business-solutions/connectors/cisco- jabber-microsoft-owa/ 10 Application Interoperability Additional integrations powered by Cisco Jabber… Jabborate integrations with Cisco Jabber Web SDK Web based user experience cross multiple platforms • Microsoft SharePoint • IBM Connections • SAP http://www.jabborate.com 11 Client Integration 12 CUCILync (incl SfB) Experience Old Experience New Experience 13 CUCILync (incl SfB) Experience IM&P (SIMPLE) • Create CSF device • Existing regions, etc • Controlled devices • Softphone • Hardphone Voice/Video (SIP) • Standard MSI 14 Simplify User Experience Registry Editor HKLM\Software\Policies\Microsoft\Office\15.0\Lync\TelephonyMode=5 15 System Integration 16 System Integration 17 Architectural Considerations 18 Platforms 19 Microsoft Lync (2010 & 2013) • SIP/SIMPLE Federation • XMPP Federation • For Microsoft Lync 2010 and Office Communication Server 2007 via a separate OCS 2007 R2 XMPP Gateway. • For Microsoft Lync 2013 via the XMPP Proxy (Edge), XMPP Gateway (Front-End) • Mediation Server (Enterprise Voice) • Remote Call Control (RCC) • RTVideo • H263 (Lync 2010 – removed in Lync 2013) • H264 SVC (Lync 2013) • RDP – Desktop sharing Microsoft Skype for Business • SIP/SIMPLE Federation • XMPP Federation • via the XMPP Proxy (Edge), XMPP Gateway (Front-End) • Mediation Server (Enterprise Voice) • Remote Call Control (RCC) Microsoft depreciated feature • RTVideo • H264 SVC • RDP – Desktop sharing (VBSS support for SfB 2016 client) Lync Online • No Federation capabilities permitted (see SfB Online Service Description) • Only option is via 3rd party broker, NextPlane (http://nextplane.net) • PSTN connectivity via 3rd party providers • Skype for Business E5 Hybrid Preview • RTVideo • H264 SVC • RDP – Desktop sharing (VBSS support for SfB 2016 client) Microsoft VIS (Video Interoperability Server) See notes: https://technet.microsoft.com/en-au/library/dn933920.aspx 23 Instant Messaging & Presence Federation 24 General Instant Messaging and Presence Capabilities Lync Client Lync Front End Lync Edge XMPP Gateway Microsoft Lync 2013 (SIP/XMPP, Microsoft Lync 2010 – Internet XMPP only available via OCS XMPP Gateway) SIP SIP/XMPP SIP/XMPP Cisco UCM IM&P Expwy-C Expwy-E (XMPP) Jabber Cisco Collaboration on premise ASA TLS Proxy (SIP) (SIP/XMPP) Internet XMPP SIP/XMPP SIP/XMPP Cisco Cisco Collaboration Cloud Jabber Cisco Webex Messenger IM&P Cloud Service (XMPP) Internet XMPP 25 General Instant Messaging and Presence Presence Model 26 General Federation Methods Static Open Example Pty Ltd _sipfederationtls._tcp.example.com _xmpp-server._tcp.example.com 27 Interdomain Instant Messaging and Presence Business to Business (Interdomain Federation) – SIP-SIMPLE Lync Client Lync Front End Lync Edge Domain company.com Recommended deployment SIP SIP SIP [email protected] Internet Cisco Jabber UCM IM&P ASA TLS Proxy (SIP) XMPP SIP SIP [email protected] Domain example.com 28 Interdomain Instant Messaging and Presence Business to Business (Interdomain Federation) – XMPP Lync Client Lync Front End Lync Edge Domain company.com Not recommended for Cisco XMPP Gateway on-premise deployment Standard XMPP federation SIP XMPP XMPP [email protected] Internet Cisco Jabber UCM IM&P Expwy-C Expwy-E XMPP XMPP XMPP [email protected] Domain example.com 29 Interdomain Instant Messaging and Presence Business to Business (Interdomain Federation) – XMPP Cloud Lync Client Lync Front End Lync Edge Domain company.com Only supported via XMPP XMPP Gateway See caveats in Appendix SIP XMPP XMPP [email protected] Internet Cisco Jabber Cisco Webex Messenger Cloud Service XMPP Domain example.com 30 Intradomain Instant Messaging and Presence Within a Business (Partitioned Intradomain Federation) Lync Client Lync Front End UCM IM&P Cisco Jabber Domain company.com Single domain for both systems SIP SIP XMPP [email protected] [email protected] • Partitioned Intra Domain Federation allows for migration or long term coexistence • Only available for Cisco UCM IM&P on premise deployments • Uses standard SIP routing mechanism • Topology can be extended to include audio and video interoperability 31 Intradomain Instant Messaging and Presence Definition of Partitioned Intradomain Federation Lync Client Lync Front End UCM IM&P Cisco Jabber XMPP Gateway Partitioned Intradomain Federation SIP SIP XMPP User only exists in one system – either Microsoft [email protected] [email protected] Lync or Cisco UCM Lync Client Lync Front End UCM IM&P Cisco Jabber XMPP Gateway Union Federation User entity exists in both system – Microsoft Lync and Cisco UCM SIP SIP XMPP ✖ [email protected] 32 Call Routing 33 Multiple Call Control Agents Call Routing Call Agent Routing Logic Lync routing logic if ( SIP URI) || (( +e164 == match tel: URI of Lync User) && (UserLicense == PlusCal)) then Do I call Bob audio or video ? Map to User SIP URI route to destination /* Reverse Number Lookup if ( destination == localURI ) then Alice elseif ( destination == remote domain ) /* Destination via SIP Trunk (Video Call Scenario) h.264 SVC (UCIF) h.264 AVC else /* Number based Enterprise Voice Routing Rtaudio G.711 35 Call Agent Routing Logic Cisco UCM routing logic I want the best Call extended to destination device using either SIP URI or number experience /* Standard SIP Media Negotiation If (destination == VIDEO CAPABLE) then Negotiate best video from SDP Alice video call else /* Destination not video capable Negotiate best audio from SDP audio call 36 Enterprise Voice Call Routing OCS 2007 / Lync 2010 & 2013 (no media bypass) Lync Client Lync Front End Lync Med. Server Cisco UCM RTaudio G.711 OCS 2007 / Lync 2010 & 2013 (no media bypass), none G.711 on IP-PBX Lync Client Lync Front End Lync Med. Server Cisco UCM IOS Transcoder RTaudio G.711 G.729/iLBC Flows show the SIP signalling and media paths in a SIP-trunk interoperability scenario Lync Mediation Server only supports G.711, requires additional transcoding resources if any other codec is used by devices connected through SIP-trunk Scenarios shown do not require the usage of a Media Termination Point (MTP) 37 Enterprise Voice Call Routing Lync 2010 & 2013 (with media bypass) Lync Client Lync Front End Lync Med. Server Cisco UCM G.711 G.711 With the introduction of Media Bypass in Lync 2010 the Lync client can initiate direct G.711 media streams. Media paths is not hair pinned through the Lync Mediation Server, no transcoding. Signalling still has to flow via the Mediation Server. Review Microsoft guidance regarding Media Bypass http://technet.microsoft.com/en-us/library/gg412740.aspx Straight forward in a centralised (single site) topology without WAN links. More complicated in a distributed topology with one or more branch - check the following: Media Bypass shall only be utilised between WAN sites without bandwidth constrains Media Bypass and Call Admission Control (CAC) are mutually exclusive Media Bypass mandatorily requires all media to be represented by a single IP address – the reason why in the above example a Media Termination Point (MTP) has to be inserted. 38 Enterprise Voice Call Routing Lync Media Bypass and CAC Media bypass and CAC both based on same site and region information For media bypass and CAC to “work” media bypass has to to be set to “Use Site and Region Information” Media Bypass CAC Result Use Site and Region Information On/Off Bypass decision based on bypass ID. CAC only for calls that are not bypassed b/c media bypass assumes “LAN like” connection to peer. CAC only applied if CAC is enabled AND bypass IDs do not match Always Bypass On Invalid Always Bypass Off All calls bypass (single bypass ID), no CAC applied Off On Mediation server always employed; CAC applied 39 Direct SIP Trunk Characteristics Lync requires Early Offer inbound/outbound Although UCM now can do early offer w/o relying on an MTP SIP profile setting: Media resource still has to be allocated (single media address in Lync GW definition) Trunk setting: For every trunk a dedicated MRGL/MRG and single media resource required On UCM SIP trunk configure IP addresses of possible mediation server peer addresses Multiple inbound SIP trunk with the same peer IP required different local signalling ports Inbound trunk selection on UCM based on remote peer and local signalling port Local signalling port defined in SIP trunk security profile 40 Enterprise Voice Call Routing Multiple Site Example (Lync to Cisco UCM) Site 1 Site 2 Site Central Site 1 Site Central Mediation Lync Front-End Site