Cisco Cisco Unified Provisioning Manager 8.5 白皮書
© 2011 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information.
Page 52 of 71
●
Object name is required when canceling products
●
Phone button template is required when ProductName is Phone (or a bundle containing a phone) or
Extension Mobility Access (or a bundle containing an extension mobility access) and Phone Type is not a
virtual phone (CTI Port) and when ordered in a service area associated with Cisco Unified Communications
Manager only
●
Cisco Unity devices (Cisco Unity, Cisco Unity Connection, and Cisco Unity Express) do not support all
products and services. If the batch action file is configured for a product that is not supported by the device
in the specified service area, batch provisioning will fail
●
Product attributes that require user input during the manual order entry process are required to
successfully complete the equivalent order in a batch project. Examples include:
◦
Phone Type: Type of phone (for example, Cisco 7960, Cisco 7912) if ordered product is a phone or a
bundle that contains a phone
◦
Line Type: Type of line (for example, autoassigned line or chosen line) if ordered product is a line or a
bundle that contains a line
◦
Directory Number: Required when ProductName is Line and Type is Chosen Line. Additionally, ordering
a product with a dependency that is not met by the order itself (for example, ordering a single line)
requires a column specifying the dependent object
◦
Route Partition: Required when ProductName is Line and Order Type is Change
For additional guidelines, please refer to the User Guide for Cisco Unified Provisioning Manager at
http://www.cisco.com/en/US/docs/net_mgmt/cisco_unified_provisioning_manager/1.3/user/guide/infrstct.html#wp1
150270
.
Dealing with LDAP-Integrated Cisco Unified Communications Manager
Cisco Unified Provisioning Manager supports LDAP-integrated call managers for Communications Manager
Versions 5.x and later. When adding an Active Directory-integrated Communications Manager to Cisco Unified
Provisioning Manager using the CallProcessor wizard, you have the option of selecting the LDAP directory
integration to be one of synchronization or of synchronization and authentication. This value must exactly match
the value configured in Cisco Unified Communications Manager. If Cisco Unified Communications Manager is
integrated with an external LDAP, subscribers are not created through Provisioning Manager; instead they are
synchronized through Cisco Unified Communications Manager. When placing an order in Cisco Unified
Provisioning Manager, if a subscriber is not available on Cisco Unified Communications Manager, the workflow
subsystem waits for a predefined period of time (24 hours by default) for the subscriber to be available on Cisco
Unified Communications Manager and then continues processing the order. The 24-hour period can be configured
on Provisioning Manager in the ipt.properties file. Change the following two settings and restart Cisco Unified
Provisioning Manager:
●
dfc.oem.extdir.retries: 24
●
dfc.oem.extdir.retry_interval: 3600