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.
A managed user in Cisco Unified Communications Domain Manager cannot be pushed to the Cisco Unified Communications Manager.
If the Cisco Unified Communications Manager “LDAP Directory Name” is configured on the LDAP server, configure that LDAP on the Cisco Unified Communications Manager (with the DirSync service off) in order for the user from this LDAP server to be able to be pushed to Cisco Unified Communications Manager.
Configure the “CUCM LDAP Directory Name” field on the Cisco Unified Communications Domain Manager at LDAP Management > Ldap Server.
Configure the LDAP on Cisco Unified Communications Manager. For more information, refer to the LDAP System Configuration procedures in your Cisco Unified Communications Manager Administration Guide.
When trying to configure a 10.5(2) UC App in Cisco Unified Communications Domain Manager 10.6(1), 10.5 is not available as the UC App Version.
Make sure that HCM-F has been upgraded to 10.6(1) and that the HCM-F device on Cisco Unified Communications Domain Manager 10.6(1) has the version set to v10_6.
Problem: You have upgraded a UC application from version 10.0 to 10.5 and you have upgraded Cisco Unified Communications Domain Manager (Unified CDM) to version 10.6(1). You try to change the UC application version to 10.5 in Unified CDM, but are unable to save the change.
Explanation: The Server Type field on the Base tab, which is new for Unified CDM 10.6(1), is not enabled and the Version field on the Publisher tab is not visible.
Resolution: Take the following steps:
Note | The command stops and restarts Unified CDM, and enables the Server Type field. |
Log in to Unified CDM as a provider administrator.
Navigate to
.Select the server on which the UC application was upgraded.
On the Base tab, complete the Server Type field.
On the Publisher tab, update the Version field.
Click Save.
Problem: An LDAP user that is synchronized from Cisco Unified Communications Domain Manager (Unified CDM) appears in Cisco Unity Connection as a local user.
Explanation: The Ldap Type field in the default CUC User Template in Quick Add Subscriber is blank or the field is not available in Advanced Subscriber Management.
Resolution option 1: Set the Ldap Type field in the template and apply the template to the Quick Add Subscriber group that contains the LDAP customer.
Log in to Unified CDM as a provider administrator.
Select the hierarchy for the LDAP user.
Navigate to
.In the list of templates, click Default CUC User Template. The template opens.
Click
.Rename the cloned template if necessary.
Enter 3 in the Ldap Type field, and then click Save.
Navigate to
.In the list of groups, click the group that contains the LDAP user.
In the Default CUC User Template field, select the template you created in step 7.
Resolution option 2: Set the Ldap Type field through Advanced Subscriber Management.
Log in to Unified CDM as a provider administrator.
Select the hierarchy for the subscriber.
Navigate to
.In the list of policies, click SubscriberAdvancedDefault.
In the Voicemail section, move CUCUser.LdapType from the Available list to the Selected list.
Click Save. The Ldap Type field is now available to configure for subscribers.
Repeat steps 4 through 6 for the SubscriberAdvanced-SiteFDP policy.
Navigate to
.Click the subscriber that you want to push to Cisco Unity Connection.
Click the Voicemail tab.
Enter 3 in the Ldap Type field, and then click Save.