Cisco Cisco Unified Provisioning Manager 8.5 White Paper
Deployment Guide
© 2010 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information.
Page 7 of 53
●
Infrastructure configuration management authorization role
●
Enhancements to the call pickup group (CPG) infrastructure configuration
●
Ability to use batch provisioning for the call pickup group
●
Ability to use batch provisioning to configure subscriber passwords
●
Ability to update the Cisco Unity Connection PIN and web password using the
DefaultUnitySubscriberPassword rule
●
Ability to set subscriber passwords using the Provisioning Manager northbound interface
●
Option to install on Cisco Unified Computing System (UCS)
●
Support for Cisco Unified Communications Manager Business Edition 8.0
●
Support for Cisco Unified Communications Manager 8.0
●
Support for Cisco Unified Communications Manager Express 8.0
●
Support for Cisco Unity 8.0
●
Support for Cisco Unity Express 8.0
●
Support for Cisco Unity Connection 8.0
●
Support for the following Cisco Unified IP Phones:
◦
Support for Cisco Unified Client Services Framework
◦
6901
◦
6911
◦
8961
◦
9951
◦
The following provisioning attributes:
◦
Cisco Camera
◦
Module 3
◦
Module 3 Load Name
The major new features are discussed in detail in the following sections.
LDAP Synchronization
This feature is important in LDAP environments. Prior to 2.1, UPM can only get LDAP subscribers from
Communications Manager when it is LDAP integrated. This is a pass-through method of synchronizing all LDAP
subscribers known by Communications Managers. When provisioning new users in Communications Manager, you
need to be sure the subscribers’ user IDs exactly match the user IDs in Communications Manager or it will reject the
order. UPM 2.1 allows end users to configure UPM to synchronize users/subscribers from an external LDAP server.
With this feature, UPM can populate its subscriber database with user IDs directly from an associated LDAP source.
Configuring and scheduling LDAP synchronization are done through domain configuration.
A filter query can be configured at the domain level to allow UPM to get only user IDs that belong in a specific
domain, as opposed to importing the entire LDAP directory into each domain. Complex filters can be created based
on the available fields in Active Directory.
There are options to control how UPM removes the users. The “Always Delete” option can be configured when a
user is no longer in the LDAP directory; then the user will be removed from UPM and the user’s services will be
moved to the global namespace. The “Delete if user has no services” option prevents a user from being deleted if
the user still has associated services. These optional settings can help remove unused services and free up
directory numbers after employees have left a company.