Cisco Unified Provisioning Manager

Table Of Contents

Release Notes for Cisco Unified Provisioning Manager 1.0

SUPPLEMENTAL LICENSE AGREEMENT

Product Documentation

Known Problems

Obtaining Documentation, Obtaining Support, and Security Guidelines

Release Notes for Cisco Unified Provisioning Manager 1.0

---

These release notes are for use with Cisco Unified Provisioning Manager (Provisioning Manager).

These release notes provide:

•SUPPLEMENTAL LICENSE AGREEMENT

•Product Documentation

•Known Problems

•Obtaining Documentation, Obtaining Support, and Security Guidelines

SUPPLEMENTAL LICENSE AGREEMENT

SUPPLEMENTAL LICENSE AGREEMENT FOR CISCO SYSTEMS NETWORK MANAGEMENT SOFTWARE: CISCO UNIFIED OPERATIONS MANAGER.

IMPORTANT-READ CAREFULLY: This Supplemental License Agreement ("SLA") contains additional limitations on the license to the Software provided to Customer under the End User License Agreement between Customer and Cisco. Capitalized terms used in this SLA and not otherwise defined herein shall have the meanings assigned to them in the End User License Agreement. To the extent that there is a conflict among any of these terms and conditions applicable to the Software, the terms and conditions in this SLA shall take precedence.

By installing, downloading, accessing or otherwise using the Software, Customer agrees to be bound by the terms of this SLA. If Customer does not agree to the terms of this SLA, Customer may not install, download or otherwise use the Software.

ADDITIONAL LICENSE RESTRICTIONS:

•Installation and Use. The Software components are provided to Customer solely to install, update, supplement, or replace existing functionality of the applicable Network Management Software product. Customer may install and use the following Software components:

–Cisco Unified Provisioning Manager: May be installed on a server in Customer's network management environment.

For each Software license granted, Customers may install and run the Software on a single server to manage the number of IP phones specified in the license file provided with the Software, or as specified in the Software License Claim Certificate. Customers whose requirements exceed the IP phone limit must purchase upgrade licenses or additional copies of the Software. The IP phone limit is enforced by license registration.

•Reproduction and Distribution. Customers may not reproduce nor distribute the Software.

DESCRIPTION OF OTHER RIGHTS AND LIMITATIONS.

Please refer to the Cisco Systems, Inc. End User License Agreement.

Product Documentation

---

Note The originally published printed and electronic documentation is included with your product. Any changes after original publication are reflected on Cisco.com, where you will find the most up-to-date documentation.

---

Table 1 describes the product documentation that is available.

Table 1 Product Documentation 

Document Title	Available Formats
Supported Devices Table for Cisco Unified Provisioning Manager 1.0	On Cisco.com at the following URL: http://www.cisco.com/en/US/products/ps7125/products_device_support_table09186a00807db1c1.html
Release Notes for Cisco Unified Provisioning Manager 1.0	•In PDF on the product CD-ROM •On Cisco.com at the following URL: http://www.cisco.com/en/US/products/ps7125/prod_release_note09186a00807db225.html
Installation Guide for Cisco Unified Provisioning Manager 1.0	•In PDF on the product CD-ROM •On Cisco.com at the following URL: http://www.cisco.com/en/US/products/ps7125/products_installation_guide_book09186a00807bd201.html
User Guide for Cisco Unified Provisioning Manager 1.0	•In PDF on the product CD-ROM •On Cisco.com at the following URL: http://www.cisco.com/en/US/products/ps7125/products_user_guide_book09186a00807bd204.html

Known Problems

Table 2 describes problems known to exist in this release.

Table 2 Known Problems in Provisioning Manager 

Bug ID	Summary	Explanation
CSCsg24674 CSCsg59272	A batch order that contains duplicate MAC addresses fails.	If you placed a phone batch order that contains MAC addresses that already exists on the Cisco Unified CallManager, the order fails. Workaround: Make sure your batch file does not contain MAC addresses that have been provisioned in Provisioning Manager or are duplicated in the file.
CSCsh01500	An order on a dependent product should be blocked if the parent product is processing an order.	When a product has an outstanding running order, any orders on its child product fail. For example, if a change phone order is running, canceling a line on the phone fails. Workaround: Abort the failed order. After the order against the parent product completes, place the order on the child product again.
CSCsh86065	Searching for a deleted subscriber by directory number after a Domain synchronization displays an error.	If a subscriber is deleted from Cisco Unified CallManager and then a synchronization is performed, Provisioning Manager does not delete the subscriber. Provisioning Manager only deletes the subscriber's associated products. Because the products do not exist for subscribers that have been deleted in Cisco Unified CallManager or Cisco Unity, when you search using their telephone number an error occurs. Workaround: Search using the subscriber's ID or name.
CSCsh94693	You cannot place an order for a phone if the phone's MAC address is already registered to Cisco Unified CallManager Express but it is not configured in Cisco Unified CallManager Express.	If you try to provision a phone through Provisioning Manager with the same MAC address as one that is already registered but not configured in Cisco Unified CallManager Express, the order fails. Phones that are registered with Cisco Unified CallManager Express but not configured, occupy slots (ephone-x). A list of registered phones with corresponding MAC addresses can be seen with the show ephone registered command. This issue occurs with Cisco Unified CallManager Express 3.3, 3.4, and 4.0. Workaround: For phones on Cisco Unified CallManager Express 3.3 and 3.4, you will have to disconnect the phones from the network, so that the registration of the phones is lost. A new Phone order can then be placed with the same MAC address. For phones on Cisco Unified CallManager Express 4.0, auto registration of the phones should be turned off. So, for phones already registered but not configured, a reset <mac-address of phone> command must be issued from the telephony service before ordering a phone with the same MAC address.
CSCsh95213	On partially failed orders, the Cancel Service button is not present.	When part of an order with more than one product produces an error, the products which were successfully provisioned as part if this failed order cannot be canceled from the Subscriber Record (the Cancel Service button is not present). Once this order is aborted by the administrator, the order goes to the Hold state and the Cancel Service button is visible for the products. The problem is that this affects all the previous products added through partially failed orders. Even if there is one failed order in the system, all the products that were earlier provisioned through orders that are in the Hold state cannot be canceled. Workaround: Make sure all the orders for a subscriber, that produce an error, are aborted by the administrator.
CSCsh96288	Unable to place change phone orders (new phone type, new MAC address) through batch provisioning.	Batch orders fail in the following instances: •If you do not use upper case letters for all MAC addresses. •If you are entering a change phone order for changing phone type and you do not list the new phone button template. Workaround: Make sure that the remainder of the failed order is aborted by the administrator. When entering batch orders, remember the following: •For all operations in the batch file, always use upper case letters when entering a MAC address. •To change the phone type, you must provide the new phone button template in the batch file.
CSCsh98606	The DNAutoReservation rule does not work correctly.	Do not use the DNAutoReservation rule. Workaround: None.
CSCsh99061	The DNReservationTimeout rule does not work correctly.	The DNReservationTimeout rule cannot be configured at the Domain level. The DNReservationTimeout rule is a global rule that is only set in the Customer Domain Template. Also, the value for the DNReservationTimeout rule is specified in days and minutes (not days and hours). Workaround: None
CSCsi01071	Users not assigned the Advanced Assignment authorization role can specify MAC addresses when ordering products.	Only users assigned the Advanced Assignment role are suppose to be able to assign MAC addresses during order entry for a phone product. Currently other authorization roles are also able to assign MAC addresses. Workaround: None.
CSCsi06355	You cannot cancel a phone that has a line on a shared phone.	Canceling a phone order fails if the phone is shared and the phone has a line, that is the first line for the subscriber. Workaround: 1. Make sure that the remainder of the failed order is aborted by the administrator. 2. Restart the Provisioning Manager server. 3. Perform a subscriber synchronize for the subscriber. 4. Cancel the phone again.

Provisioning Manager synchronizes the data in Cisco Unified CallManagers with Call Processors in Provisioning Manager. There can be problems obtaining the data from Cisco Unified CallManagers data due to known problems in certain versions of Cisco Unified CallManagers.

Table 3 lists the known problems and the related Cisco Unified CallManager bug ID. When a related bug is fixed, the problem will no longer exist in Provisioning Manager.

Table 3 Known Problems in Call Processor Devices 

Summary	Explanation
Provisioning Manager cannot synchronize users that were created on Cisco Unified CallManager 5.0.4 and that have phones or device profiles associated to them.	If you create a user in Cisco Unified CallManager 5.0.4 with an associated phone or device profile, the user will not be added into Provisioning Manager when a subscriber synchronization is performed. This defect is present in Cisco Unified CallManager 5.0.4. The related Cisco Unified CallManager bug ID is CSCse43192. This issue is fixed in Cisco Unified CallManager 5.0.4.2103-1 and later. For more information regarding this issue, contact TAC. For information on contacting TAC, see the following: http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html Workaround: None.
Members of the CallPickupGroup and the LineGroup are not saved in the Provisioning Manager database.	Provisioning Manager cannot obtain the values of the members for the CallPickupGroup and LineGroup objects during synchronization with Cisco Unified CallManager. However, these objects can be configured on Cisco Unified CallManager using Provisioning Manager. This applies to the following versions of Cisco Unified CallManager: •4.0(2) •4.1(3) •4.2(1) •5.0(4) The related Cisco Unified CallManager bug IDs are CSCsf07468 and CSCsf07560. Workaround: None.
The default value is not set to True for the following: •Forwarded Call Info - Caller Name •Forwarded Call Info - Dialed Number Because of this, call forwarding will not occur.	In Cisco Unified CallManager [release 4.0(1), 4.1(3), 4.2(1), 5.0(2)] the following provisioning attribute are set to False: •Forwarded Call Information - Caller Name •Forwarded Call Information - Dialed Number These attributes should be set to True. They must be set to true for call forwarding to occur. The related Cisco Unified CallManager bug ID is CSCsg37872. Workaround: After creating a Service Area, set these provisioning attributes to True.
In some cases, synchronization is not successful when trying to synchronize Cisco Unified CallManager 5.0.	There are two issues causing this problem: •Provisioning Manager cannot support RoutePatterns that are configured to use a gateway as the destination. The related Cisco Unified CallManager bug ID is CSCsh36013. •Provisioning Manager cannot support RoutePatterns whose configured RouteLists are deleted manually from Cisco Unified CallManager. The related Cisco Unified CallManager bug ID is CSCsh29825. Workaround: None.
In some cases, a change phone order changes the phone load name on Cisco Unified CallManager.	When performing a change phone order, a phone load name is set on the phone. This problem occurs if the phone load name was originally not set (which means that Cisco Unified CallManager is using the default phone load). Also, the problem results in different situations for Cisco Unified CallManager 4.x and 5.x. •In Cisco Unified CallManager 4.x, a change phone order sets the phone load name with the default phone load name. •In Cisco Unified CallManager 5.x, only when Module Load Name is present does performing a change phone order set the phone's load name with Module Load Name. The related Cisco Unified CallManager bug IDs are CSCsh26744 and CSCsh58736. Workaround: None.
The MLPP Domain ID is not set on the Cisco Unified CallManager when an H323 gateway is created through Configuration Templates.	The MLPP Domain ID is not set for all 4.x versions of Cisco Unified CallManager. The related Cisco Unified CallManager bug ID is CSCsh56843. This issue is fixed in Cisco Unified CallManager 5.0.x. Workaround: None
Performing a change order on a phone where networkLocale is set, deletes the phone in Cisco Unified CallManager.	When you run a change order on a phone, the phone is deleted if networkLocale is present in the phone. This defect is present in Cisco Unified CallManager 4.1(3)SR3. The related Cisco Unified CallManager bug ID is CSCsd82084. This issue is fixed in Cisco Unified CallManager 4.1(3)SR4. Workaround: None
Change phone order sets the User Locale and Network Locale to None.	If after synchronizing a subscriber you perform a phone change order, the User Locale and Network locale are set to None. This occurs because the provisioning of Network Locale and User Locale through the AXL API is not supported on all versions of Cisco Unified CallManager. •User Locale is not supported on Cisco Unified CallManager 4.0 AXL API. •Network Locale is not supported on Cisco Unified CallManager 4.0 and 4.1 AXL API. The related Cisco Unified CallManager bug ID is CSCsd82084. Workaround: None.
Canceling a shared phone for a subscriber does not disassociate the phone in Cisco Unified CallManager.	A canceled shared phone remains associated in the users account on the Cisco Unified CallManager, if the subscriber has only one phone in the Cisco Unified CallManager. This defect is present in Cisco Unified CallManager 5.0.4. The related Cisco Unified CallManager bug ID is CSCsh48876. Workaround: None.
Change phone orders fail on Cisco Unified CallManager 5.0.4 when Extension Mobility is on and using the same MAC address.	If you perform a change phone order on a phone that has Extension Mobility set and keeping the same MAC address, the order fails. This occurs because Cisco Unified CallManager 5.0.4 does not delete the auto-generated profile on Cisco Unified CallManager. Therefore it is attempting to re-generate the same auto-generated profile. The related Cisco Unified CallManager bug ID is CSCsd60519. WorkAround: Before placing the change order, remove the auto-generated device profile from Cisco Unified CallManager.
You cannot set the Cisco Unified CallManager PIN for subscribers on Cisco Unified CallManager 5.0.4.	When the Cisco Unified CallManager PIN is changed (or reset) in Provisioning Manager, it does not get changed in Cisco Unified CallManager. This problem is present in Cisco Unified CallManager 5.0.4. The related Cisco Unified CallManager bug ID is CSCsh88651. Workaround: None.

Obtaining Documentation, Obtaining Support, and Security Guidelines

For information on obtaining documentation, obtaining support, providing documentation feedback, security guidelines, and also recommended aliases and general Cisco documents, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:

http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html

This document is to be used in conjunction with the documents listed in the "Product Documentation" section.

Copyright © 2007 Cisco Systems, Inc. All rights reserved.