The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
The following procedure applies for both CUCI-MOC and CUCI-Lync.
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:
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:
Standard CTI Enabled
Standard CTI Allow Control of Phones supporting Connected Xfer and conf
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.
Make sure that the user is associated with the relevant desk phone before you perform the following steps.
The following table provides a feature comparison between Cisco Unified Communications Manager and Cisco Hosted Collaboration Solution.
Cisco Unified Communications Manager | Cisco Hosted Collaboration Solution | |
---|---|---|
Device Authentication/Encryption |
Yes |
|
Signaling Authentication (phone) |
Yes |
No |
Signaling Encryption (phone) |
Yes |
No |
Signaling Encryption (gateway) |
Yes |
No |
Media Encryption SRTP (phone) |
Yes |
No |
Media Encryption SRTP (gateway) |
Yes |
No |
Visual Indication of Device Authentication/Encryption |
Yes |
No |
SIP based Authentication |
Yes |
Yes (Manual configuration required) |
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.
Step 1 | Navigate to . | ||
Step 2 | Click Find | ||
Step 3 | Click the Cisco UC Integration for Microsoft Office Communicator client that you want to configure. | ||
Step 4 | Click the Device Security Profile parameter. | ||
Step 5 | Select the Cisco Unified Client Services Framework - Standard SIP Secure parameter that you configured in Stage 1: Add new phone security profile. | ||
Step 6 | Click Save. | ||
Step 7 | Click Apply Config.
This parameter indicates the security mode of the cluster. A value of 0 indicates Nonsecure (phones register in nonsecure mode [no security]); a value of 1 indicates Mixed (the cluster allows the registration of both secure and nonsecure devices). The default value is 0. |