Cisco Unified MeetingPlace, Release 7.0 -- Restrictions for Directory Service

From DocWiki

Jump to: navigation, search

Main page: Cisco Unified MeetingPlace, Release 7.0

Up one level: Configuration

  • Cisco Unified Communications Manager 4.x and earlier releases are not supported.
  • The following restrictions apply to Directory Service users (users whose isLocalUser user profile field is set to No):
    • Because the user is not authenticated locally, the User ID, User password, and Profile password fields cannot be modified through Cisco Unified MeetingPlace by the user or by the system administrator.
    • The following password-related fields on the Usage Configuration Page do not apply to Directory Service users: Change profile password (days), Minimum user password length, Change user password (days), and Maximum profile login attempts.
    • The user profile fields that are populated by Cisco Unified Communications Manager or through Directory Service filters can be modified through Cisco Unified MeetingPlace. Nevertheless, such modifications need to be manually updated in the LDAP directory, or in Cisco Unified Communications Manager when LDAP integration is not in use. Otherwise, those modifications will be lost during the next Directory Service user update.
    • The user is always authenticated externally. Therefore, if the connection fails between Cisco Unified MeetingPlace and the authenticating device, the user cannot log in to Cisco Unified MeetingPlace.
      • If Cisco Unified Communications Manager fails, then you can use a redundant Cisco Unified Communications Manager for authentication only. On the Directory Service Configuration Page, temporarily change the AXL URL field to specify the redundant Cisco Unified Communications Manager, and set the Update users interval field to the largest available value (Six months) to temporarily stop the database synchronization. When you select the largest available value, the Cisco Unified MeetingPlace system ignores the Set Cisco Unified Communications Manager sync schedule to match update users interval setting even if you have it checked.
      • When you switch the AXL URL field back to the primary Cisco Unified Communications Manager, make sure that you also set the Update users interval field to the previous value.
      • The Update users interval field change is required because user updates, imports, and deletions are not supported from a redundant Cisco Unified Communications Manager, even if it is integrated with the same LDAP directory as the primary Cisco Unified Communications Manager. This is because Directory Service user updates are tied to a field that is unique to each Cisco Unified Communications Manager server.
    • The maximum lengths of some user profile fields are shorter in Cisco Unified MeetingPlace than in Cisco Unified Communications Manager. Make sure that the Cisco Unified Communications Manager user field lengths do not exceed the maximum number of characters stated in Table 3.

Table: Maximum Length of Directory Service User Fields
Cisco Unified MeetingPlace Field Cisco Unified Communications Manager Field Maximum Number of Characters

First name

First name (FirstName)


Last name

Last name (LastName)


User ID

User ID (UserId)


E-mail address

Mail ID (EmailAddress)


Main phone number

Telephone Number (PhoneNumber)


  • The following restrictions apply to user profile deletions, because to determine which user profiles to delete, the system periodically checks Cisco Unified Communications Manager for inactive user entries and deletes those user profiles from Cisco Unified MeetingPlace.
    • If you delete a user from Cisco Unified Communications Manager, the corresponding user profile remains in Cisco Unified MeetingPlace. You must manually delete or deactivate the user profile in Cisco Unified MeetingPlace.
    • If you replace the LDAP directory with which Cisco Unified Communications Manager is integrated, then all Directory Service users from the first LDAP directory will remain in Cisco Unified MeetingPlace database until you manually delete them.
      To avoid this database clutter, you can delete all entries in the database by entering the dbupdate command before you switch from one LDAP directory to another.

Caution! Deleting all database entries is an irreversible operation. Before you run the dbupdate command, consider backing up and archiving the database. See Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server.

Related Topics

Rating: 0.0/5 (0 votes cast)

Personal tools