Cisco UC Integration for Microsoft Office Communicator provides interoperability with Microsoft Office Communicator Server 2007 (OCS) and the Microsoft Office Communicator (MOC) client. Cisco UC Integration for Microsoft Lync provides interoperability with Microsoft Lync 2010 and the Microsoft Lync 2010 client. Cisco UC Integration for Microsoft Office Communicator/ Cisco UC Integration for Microsoft Lync uses the Client Services Framework (CSF) and incorporates it into a tab integration of MOC. This tab integration allows for the use of audio functionality of existing Unified Communications Manager endpoints, both acting as work phone.

Note

Lync 2013 is not in the scope of this document. As a general rule, you should use the latest version of the Cisco IC Integration applications. As of this writing, the latest versions are: CUCI-Lync Release 10.6 CUCI-MOC Release 8.0.3 Check the relevant product pages on Cisco.com for the latest release information.

The Cisco Unified Communications (UC) Integration for Microsoft Office Communicator client provides the voice features and the MOC client provides the IM and Presence (provided directly to OCS).

Similarly, the Cisco UC Integration for Microsoft Lync client provides the voice features and the Lync client provides the IM and Presence (provided directly to Lync 2010).

With the introduction of Microsoft Lync, the Cisco offering has been updated to include support for both OCS and Lync solutions. Lync, like OCS, consists of a client and a server with a Cisco UC Integration for Microsoft Lync CSF-based integration into the Lync client just as the Cisco UC Integration for Microsoft Office Communicator solution integrates into the MOC client.

Following is a list of supported work phone features:

• Right-click call or conference from a contact list or IM session. See Limitations and considerations for more information.

• Call from MOC/Lync search. See Limitations and considerations for more information.

• Direct dial through keypad: Numbers to dial should be the same as if initiating a call from an HCS IP Phone.

• Do Not Disturb (DND): Set through MOC/Lync or IP Phone.

• Session Initiation Protocol (SIP) call control.

• Work phone features: DTMF, call waiting, mute, transfer (blind, consultative), conference, redial, hold, volume, hang up, park, shared line retrieval, headset/speakers switch.

• Start IM from conversation window.

• Conversation information: Call status, participants, participant availability (OCS), duration.

• Call forwarding.

• Single number reach.

• Placed, missed, and received calls in client call history.

• Call survival in case of MOC/OCS/Lync failure.

• Active Directory provides phone numbers for Cisco UC Integration for Microsoft Lync and MOC.

• LDAP must be synchronized with Unified Communications Manager and OCS/Lync server.

• User IDs, devices, and directory numbers match in the Active Directory server, Microsoft Lync Server or OCS and Cisco Unified Communications Manager server.

• It is recommended that phone numbers are defined in +E.164 format for each user in the Active Directory.

• The user phone number within HCS (Unified Communications Manager) is configured in a private number plan. This requires Application Dialing Rules and Directory Lookup Dialing Rules to be configured in the Unified Communications Manager.

• Application Dial Rules and Directory Lookup Dial Rules

Desktop hardware minimum requirements

Following components are part of the Cisco UC Integration for Microsoft Office Communicator architecture:

• Microsoft Office Communicator (MOC)

  • Client for Office Communications Server

  • Downloads contact details from the Address Book Server (a component of OCS)

  • Address Book is made up of Active Directory users

• Office Communications Server (OCS)

  • Microsoft server providing Instant Messaging and Presence information

• Cisco UC Integration for Microsoft Office Communicator

  • Integrates with MOC through the Office Communicator Automation API for Contact, IM and Presence information

  • Integrates with Client Services Framework (CSF) to communicate with Cisco infrastructure and LDAP

• Client Services Framework (CSF)

  • Provides back-end integration to Unified Communications Manager and Active Directory

  • Implements work phone, desk phone control, LDAP integration, Media Termination, and so on

The following figure provides an overview of the Cisco UC Integration for Microsoft Office Communicator desktop architecture.

Figure 1. Cisco UC Integration for Microsoft Office Communicator desktop architecture

The Cisco UC Tab UI is embedded in MOC/Lync UI allowing interaction with Cisco UC Integration for MOC/Lync.

Cisco UC Integration provides windows management, client security, third-party integration and CSF integration. CSF provides call control, user authentication, Message Waiting Indicator (MWI), media, and so on. Cisco UC Integration for Microsoft Office Communicator/ Cisco UC Integration for Microsoft Lync Tab, Cisco UC Integration for Microsoft Office Communicator/ Cisco UC Integration for Microsoft Lync and CSF do not require special permissions and run using Standard User permissions.

Note	Cisco UC Integration for Microsoft Office Communicator/ Lync Installer installs all necessary client-side components.

¹ - Used to download the cnf.xml file at registration or resets.

² - LDAP connection is to the Microsoft OCS server.

Ports used by Cisco UC Integration for Microsoft Lync

The following steps describe how to deploy Cisco UC Integration for Microsoft Office Communicator/Lync

Deployment of OCS or Lync for integration with HCS requires the user phone number that is stored in Active Directory to be in +E.164 format. The user phone number within HCS (Unified Communications Manager) is configured in a private number plan. This requires Application dial rules and Directory lookup dial rules to be configured in the Unified Communications Manager.

Application dial rules map numbers in the OCS address book to a number format that can be correctly dialed within the context of the Cisco Unified Communications Manager configuration; that is, application dial rules map +E.164 numbers to the private numbering plan.

Conceptual and task-based information on Application dial rules are available in the Cisco Unified Communications Manager Administration Guide, Release 10.0(1) at:

http:/​/​www.cisco.com/​c/​en/​us/​td/​docs/​voice_ip_comm/​cucm/​admin/​10_0_1/​ccmcfg/​CUCM_​BK_​C95ABA82_​00_​admin-guide-100.html.

Directory lookup dial rules transform caller identification numbers into numbers that can be looked up in the directory; that is, to transform the private number into the +E.164 format number as stored in Active Directory, to identify the caller as a contact.

Conceptual and task-based information about Directory lookup dial rules is available in the Cisco Unified Communications Manager Administration Guide, Release 9.1(1) at

http:/​/​www.cisco.com/​en/​US/​docs/​voice_ip_comm/​cucm/​admin/​9_1_1/​ccmcfg/​CUCM_​BK_​A34970C5_​00_​admin-guide-91_​chapter_​011101.html.

For more details about the dial rules that are required for Cisco UC integration, see the Configuring Servers for Cisco UC Integration for Microsoft Lync available at

http:/​/​www.cisco.com/​en/​US/​docs/​voice_ip_comm/​cucimoc/​8_5/​english/​installguide/​config_​servers.html - wp1073533.

The following procedure applies for both CUCI-MOC and CUCI-Lync.

Configure Microsoft Office Communicator Administration Toolkit

Before you install the client on the user's computer, you require the CSF client configuration file. You must update the configuration file to point to the TFTP servers. You can configure other optional elements if required. The following link provides specific information to install the Cisco UC Integration for Microsoft Lync:

http:/​/​www.cisco.com/​en/​US/​docs/​voice_ip_comm/​cucimoc/​8_5/​english/​installguide/​deploying_​installation.html

Note	You require the CUCIMOC-SampleCUCSFAdminData.bat batch file to configure the CSF client for Lync.

The following steps describe the Cisco UC Integration for Microsoft Office Communicator/Lync installation process.

You can enable this feature for new and existing users. When you enable the setting for a new user, the user is automatically added to the following three standard Computer Telephony Integration (CTI)-related permission groups:

1. Standard CTI Enabled

2. Standard CTI Allow Control of Phones supporting Connected Xfer and conf

3. Standard CTI Allow Control of Phones supporting Rollover Mode

Existing users have a default setting of True for this feature but are not added to the three standard CTI-related permission groups.

The following table provides a feature comparison between Cisco Unified Communications Manager and Cisco Hosted Collaboration Solution.

As per the Cisco Hosted Collaboration Solution service description document, you must provision any SIP-based authentication manually on the Cisco Unified Communications Manager. The Cisco Unified Communications Domain Manager server does not provision this feature.

There are two configuration stages in the provisioning phase.

1. Stage 1: Add new phone security profile

2. Stage 2: Assign profile to client