The previous blog provides the lab overview on integrating Cisco Jabber and Microsoft Lync so that Jabber and Lync users can communicate with each oth
The previous blog provides the lab overview on integrating Cisco Jabber and Microsoft Lync so that Jabber and Lync users can communicate with each other. We will focus on ‘1.0 Cisco IM&P Configuration’ in this blog, as shown in the following configuration flow.
1.0 Cisco CUCM IM&P Configuration
1.1 SIP Routing Node and Services for Federation
There are two deployment modes for the Jabber and Lync federation, chat-only or chat+calling. This lab is scoped for chat-only. Chat+calling further requires the Cisco Expressway gateway.
Chat-only mode requires to choose an IM&P node as the routing node. I chose IMP01 as the routing node in this lab. The routing node shall have ‘Cisco SIP Proxy’ service enabled for the federation; while the other nodes shall have ‘Cisco SIP Proxy’, ‘Cisco XCP SIP Federation Connection Manager’ and ‘Cisco XCP Router’ services enabled. Please refer to Reference 1 for details. It would be no harm to enable the required services on all cluster nodes in the lab environment. However, it is recommended to disable unnecessary services in production, due to compute resource utilisation and precisely control the high availability.
1.2 Enable Partitioned Intradomain Federation with Lync
- Log onto IMP01, the IMP routing node we chose;
- Navigate through Cisco Unified CM IM and Presence Administration > Presence > Settings > Standard Configuration;
- Tick ‘Enable Partitioned Intradomain Federation with LCS/OCS/Lync‘; and
- Leave ‘Partitioned Intradomain Routing Mode’ as ‘Basic Routing Mode‘ for this lab, which is the default option. The other option is ‘Advanced Routing Mode’.
Basic routing cannot tell which users are valid Lync users and simply route all unlicensed IM&P users within the designated service domain to the Lync server.
Advanced routing can tell Lync users by their valid Lync SIP address stored in the Cisco IM&P database. It helps reduce the traffic between Cisco IM&P and MS Lync, but adding storage usage on Cisco IM&P.
1.3 Intradomain Federation Setup Wizard
- Start the intradomain federation setup wizard from Cisco Unified CM IM and Presence Administration > Presence > Intradomain Federation Setup;
- The wizard will ask a few Lync topology questions and automatically generate the required static routes, access control lists and TLS peer configuration for us.
Select ‘Lync Server 2010, 2013 (Enterprise, Standard Edition) in our case.
Fill in Lync details. The required information can be retrieved from ‘Lync Server Mangement Shell’, by running ‘get-CsSite’ command. In our case:
- Lync Server Version: Standard
- Load Balancer: NO
- Register ID: S01E01LYC01.altairx.lan
- Site ID: 1
Add each Lync front end server. We only have one, S01E01LYC01.altairx.lan in our case.
Add the presence domain, we are doing an intradomain federation, using ‘altairx.lan’ for both Cisco IM&P and MS Lync.
The wizard generates IM&P configuration for review. If not using the wizard, we can also configure manually from:
- Static routes: Presence > Routing > Static Routes;
- ACLs: System > Security > Incoming ACLs;
- TLS Peers: System > Security > TLS Peer Subjects;
- TLS Context: System > Security > TLS Context Configuration > Use ‘Default_Cisco_UP_SIP_Proxy_Peer_Auth_TLS_Context‘ template; and
- Listener ports: System > Applicaiton Listeners.
Cisco IM&P and MS Lync shall trust each other’s certificates to allow successful peer authentication. We will cover the certificate requirements in subsequent articles in this series.
The following tasks shall be completed on Lync. However, do NOT follow the following Cisco ‘Instructions for Lync Commands’, it has missing commands and optional steps. I will walk you through the Lync side of configuraiton in the next blog.
- Installation Guide for Cisco Unified Communications Manager and IM and Presence Service Release 11.5(1): https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/install/11_5_1/cucm_b_installation-guide-cucm-imp-1151.html