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 2 server pool server pool To keep media local to a site each site requires a local media resource Multiple sites require multiple trunks … and multiple MRGs, MRGLs and media resources … and multiple SIP secuirty profiles, because unique identification of each trunk on Cisco UCM based on the signalling port (UCM side trunk identification based on peer IP address and local signalling port)
41 Enterprise Voice Call Routing Multiple Site Example (Lync to Cisco UCM) with Redundancy
Site 1 Site 2b Site
Site 2a Site Central
Site 1b Site Site 1a Site
Site 2
Lync Front-End Mediation server pool server pool Two sites with Lync to Unified CM SIP trunk redundancy already require: 4 trunks, 4 MTPs/TRPs 4 MRGS, 4 MRGLs
2 SIP trunk security profiles 42 Enterprise Voice Call Routing Multiple Site Example
Site 1
Site 2 Site Central Site 1 Site
WAN Site 2
Lync Front-End Mediation server pool server pool Unified selects trunk to Lync based on called destination (+E.164 prefix) MTP (assumed) local to Lync client selected Alternate media IP definition in Lync trunk configured in same site as Lync client -> bypass activated Local media 43 Enterprise Voice Call Routing Multiple Site Example
Site 1
Site 2 Site Site 1 Site
Site 2
Lync Front-End Mediation server pool server pool Unified selects trunk to Lync based on called destination (+E.164 prefix), but Lync client moved to other site MTP (assumed) local to Lync client selected Alternate media IP definition in Lync trunk configured not in same site as Lync client -> no media bypass Mediation server in media path Media hairpins through central site 44 Enterprise Voice Call Routing Multiple Site Example
Site 1
Site 2 Site Site 1 Site
Site 2
Lync Front-End Mediation server pool server pool False assumption about Lync client location could lead to even worse media path: Unified CM selects trunk with MTP local to (assumed) location of Lync client: Site 2 Lync rejects media bypass, because MTP not local to IP address of Lync client Mediation server in media path, Media hairpins through remote and central site
45 Dial Plan Considerations
46 Enterprise Voice Call Routing Addressing Requirements Explicit (deterministic) routing requires split address ranges +E.164 prefixes per call control Impossible to migrate users between call controls w/o changing phone numbers In reality +E.164 addresses distributed between call control domains Complex (worst case: per destination) routing needs to be maintained … or number hunting can be used; risk: loops, complex troubleshooting +61399883101
+61399883201 +61399883102 +613998831XX +61399883202 +613998832XX
+61399883203 +61399883103
47 Enterprise Voice Call Routing Call Forking w/Dual Call Controls
48 Enterprise Voice Call Routing Call Forking w/dual Call Controls – Where to Implement Forking? On Communications Manager PSTN destination and Lync destination
PSTN
On Lync (SimRing) PSTN destination and IP Phone destination Inbound call from PSTN has to to to Lync PSTN No call anchoring on UCM All inbound calls hairpinned/forked through Lync
Both Sides (UCM SNR & Lync SimRing) Loops! PSTN Multiple call legs to same destinations!
49 Video Interoperability
50 51 Driving Standards & Interoperability
52 Video Interoperability
53 TelePresence Server Customers
54 Customer Committed to SfB Conferencing Interop
* Same architecture is valid for VCS as Call Control
55 Customer with Jabber Deployed
56 Expressway - High Level Architecture
57 Call routing
58 Calling Video Devices from Lync client
59 Calling Lync users from Video Devices
60 Content Sharing Interoperability
61 Acano Spaces
Space address: [email protected]
Great for video centric organisations!
Pros: Great video experience! Geographic distribution of calls
Cons: Requires high number of ports New user behaviour for Lync users 62 Acano Dual Home
Video Layout w/Continous Presence Skype Gallery View
ONE Conference – across two meeting places
63 Content Sharing (v1.8 +)
ACANO
Full content support on Sharing from Lync works as normal. video endpoint – both Lync/Skype receives content as a separate receive and send RDP/Content stream (popout)
64 High Level Architecture
CUCM
Expressway Expressway Edge Core
Acano Acano Edge Core
Lync Edge Lync FE
65 Call Flow [email protected] CUCM or 4. Call routed to registered endpoint VCS
3. Call Bridge redirects Acano call to CUCM trunk Core
1. Calls: [email protected] 2. Search rule redirects Lync FE call to the Call Bridge [email protected]
66 Expressway Acano
• Video experience everywhere • Lync/SfB external calling
• Investment in vTS, MCU, etc. • Content Sharing bi-directional
• Multistream • Dual Home • Personal Meeting Rooms • Drag & Drop from Lync/SfB • All the vTS/MCU features
67 Meeting Integration
68 CMR Cloud - Connect Your Way Cisco WebEx Personal Rooms with Cloud-Based WebEx Video Bridge
WebEx ® Cloud
® Desktop Cisco WebEx Mobile Jabber® Mobile Collaboration
Third-Party, ® Standards-Based WebEx Desktop Cisco TelePresence Lync & SfB Endpoints Telepresence Endpoints Jabber Desktop 69 Lync Interoperability
70 Lync Interoperability
. Supports on-premises and cloud-registered Lync 2010, 2013, and Skype for Business clients . Delivers two-way content sharing (Lync to meeting in separate content channel) . Enables Lync users to start meeting as host and join before host
Standards-based Video Endpoint URI Format:
71 Summary
72 Cisco Interoperability with Microsoft
•Identify your requirements and select the right scenario for your environment User experience Technical feasibility Complexity Operational implications •Understand the pros and cons of the selected scenario •“Mileage” of certain functionalities might vary when applied to a real life environment …Media Bypass in multi site deployment
•Cisco remains committed to support interoperability scenarios 73 Q & A Complete Your Online Session Evaluation Give us your feedback and receive a Cisco 2016 T-Shirt by completing the Overall Event Survey and 5 Session Evaluations. – Directly from your mobile device on the Cisco Live Mobile App – By visiting the Cisco Live Mobile Site http://showcase.genie-connect.com/ciscolivemelbourne2016/ – Visit any Cisco Live Internet Station located throughout the venue Learn online with Cisco Live! T-Shirts can be collected Friday 11 March Visit us online after the conference for full access to session videos and at Registration presentations. www.CiscoLiveAPAC.com Thank you
Appendix - Migration
78 Instant Messaging and Presence - Migration Within a Business (Partitioned Intradomain Federation) Domain company.com Active Directory Single domain for both systems Lync Client Lync Front End UCM IM&P Cisco Jabber
SIP SIP XMPP
[email protected] [email protected] • Full Contact Search available to each end-user regardless of whether they exist on Cisco or Microsoft • The end-user is not aware what back end the buddy resides on • Temporary Presence subscription’s not working in both directions (during search the user’s presence is “not available”) unless user is added to the buddy list • Once added to the buddy list, users can exchange presence and instant messaging • Recommended to utilise “msRTCSIP-primaryuseraddress” attribute as IM contact address • LDS supported for complex AD scenario 79 Instant Messaging and Presence - Migration Migration – Quick Start Guide: ① Prior to any migration, set Max Contacts/Watchers to ⑤ Run once from any Front-End Server unlimited on UCM IM&P DisableAccount-exe –s/{AD server} –f/{Input file} –I/debug – This is to ensure all contact lists are successfully migrated r/NORMAL ② Provision Migrating users on UCM IM&P ⑥ Validate that the account update has propagated to OCS/Lync ③ Use the OCS/Lync tool to backup migrated users’s contact lists ⑦ Run from one Front-End Server in each pool: OCS/Lync 2010 use dpimpexp.exe, Lync 2013 use Export- DisableAccount.exe –s/{DB Instance} –I/debug –r/NORMAL CSUserData ⑧ Import contacts into UCM IM/P using BAT tool ④ Run once from any Front-End Server ⑨ Reset max contacts/watchers limit on UCM IM&P after ExportContacts.exe –s/{AD Server} –f/{Input file} – I/debug – r/NORMAL import ⑩ Migrated users now able to log into into UCM IM&P Documentation http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/im_presence/interdomain_federation/10_5_1/CUP0_BK_I07B7052_00_integration- guide-interdomain-federation-105.html Software Download – Migration utility https://software.cisco.com/download/release.html?mdfid=286269517&flowid=50462&softwareid=282074312&release=10.5(2a)&relind=AVAILABL E&rellifecycle=&reltype=latest 80 Instant Messaging and Presence - Migration New Functionality in Cisco UCM 10.x • msRTCSIP-primaryuseraddress or mail directory attribute supported as JabberID • Multiple domains supported on single UCM IM&P system Single or multi server environment • Pre 10.x default URI format sAMAccountName@domain • Post 10.x advanced configuration allows for selecting either msRTCSIP-primary useraddress or mail as URI
• Multiple domains supported including for partitioned intra domain federation • Security Certificates enhanced to reflect multi domain operations • Cisco Jabber 10.6 versions of clients required
81 Instant Messaging and Presence - Migration Advanced UCM IM&P Presence Configuration Advanced mapping of directory attribute to be used as JabberID (either email address or for migration msRTCSIP- Presence -> Settings -> Advanced Configuration primaryuseraddress
82 Instant Messaging and Presence - Migration Partitioned Intradomain Federation – Configuration Details
Domain company.com Active Directory Single domain for both systems msRTCSIP-prim.u.addr. msRTCSIP-prim.u.addr. [email protected] [email protected] [email protected] [email protected]
ldap(s)/https Lync Client Lync Front End UCM IM&P Cisco Jabber
SIP Routing SIP Static route *@company.com -> XMPP <- Static route *@company.com Static route *@company.de -> https <- Static route *@company.de [email protected]
Address Book Server
83 Instant Messaging and Presence - Migration Partitioned Intradomain Federation – Message Routing UCM (advanced routing) ① Client requests to initiate Active Directory communication with 1 3 [email protected] ② UCM IM&P identifies user as not 4 local from user database 5 ③ With advanced routing UCM IM&P queries existence of users from directory – reducing unnecessary traffic (mistyped Lync Client Lync Front End UCM IM&P Cisco Jabber URI etc.) 2 ④ Upon positive response from directory UCM IM&P routes SIP SIP Routing messages to Lync front-end SIP XMPP ⑤ Lync Front-End delivery [email protected] message to Lync client
84 Instant Messaging and Presence - Migration Partitioned Intradomain Federation – Message Routing Lync ① Client requests to initiate Active Directory communication with 1 [email protected] ② Lync identifies user as not local 3 from user database 4 ③ Lync routes all none local users via SIP trunk (incl. mistyped URIs) – Cisco UCM will handle possible routing loops Lync Client Lync Front End UCM IM&P Cisco Jabber ④ Cisco UCM IM/P deliver message after conversation from SIP to XMPP to Jabber SIP Routing client SIP 2 XMPP
85 Instant Messaging and Presence - Migration Partitioned Intradomain Federation – Lync Address Book
New Cisco Jabber user Active Directory UCM Cluster LDAP sync [email protected] Lync enabled users imported to addressbook Lync only imports RTC enabled into addressbook Lync Adressbook Server For new Cisco Jabber users never LDAP configured on Lync before migration – msRTCSIP-primaryuseraddress must be set Addressebook download to client User imported with msRTCSIP… attribute Lync Client Cisco Jabber imported into Lync addressbook – new Cisco Jabber user searchable for Lync users User imported with msRTCSIP… attribute imported into Cisco UCM via LDAP sync
[email protected] 86 Instant Messaging and Presence - Migration Partitioned Intradomain Federation – External Federation
Domain company.com Active Directory Single domain for both systems Lync Client Lync Front End UCM IM&P Cisco Jabber
• Both systems are using the same DNS SRV records for SIP SIP XMPP external federation [email protected] [email protected] • Required protocol based Lync Edge Expwy-E records have to be owned by a single system ASA TLS proxy DNS SRV Records Who handles DNS SRV Records • User experience impacted _sipfederationtls._tcp. federation for _sipfederationtls._tcp. when split by protocol _xmppserver._tcp. company.com? _xmppserver._tcp. Internet
87 Instant Messaging and Presence Business to Business (Interdomain Federation) – XMPP Cloud
• Connection lost under load Connection are lost when Lync XMPP Gateway is under load. The gateway will close the connection, log that there was an error talking to the far side but give no explanation as to why. Under modicum of load (around 90 messages/second), connections can be lost as far as every 2.3 minutes. Increasing the load to around 250 messages/second connections can be dropped every 10 seconds. This leads to delays in delivery and outright packet loss. • No id-on-xmppAddr support (RFC3920) The Lync XMPP Gateway does not look for id-on-xmppAddr in the certificate. Information will be ignored. • No presence update after a subscription Intermittent: Directly after the Lync contact accepts the Webex Messenger user subscription, an unavailable is sent from the Lync contact, no available presence is sent until the Lync contact resigns in. • Messages routed to wrong client Lync XMPP Gateway does not follow the XMPP rules for addressing of messages which can lead to messages unexpected delivered to the wrong client in a multiple client per user situation. • Webex Messenger user showing as offline when online Lync XMPP Gateway does not correctly track presence with multiple clients logged in for a single user. If a user has two clients connected and the Lync user sess him as online, then logs out one of the clients the Lync user will see Webex Messenger user as offline. • No Group Chat support Lync XMPP Gateway does not understand MUC or Group Chat protocol. Lync users can not join or be invited to a group chat session.
88 Thank you
89