Cisco Prime Unified Provisioning Manager

Table Of Contents

Release Notes for Cisco Unified Provisioning Manager 8.6

Contents

Introduction

SUPPLEMENTAL LICENSE AGREEMENT

New Features in Cisco Unified Provisioning Manager 8.6

Product Documentation

Known Problems

Resolved Problems

Obtaining Documentation and Submitting a Service Request

Release Notes for Cisco Unified Provisioning Manager 8.6

---

Contents

These release notes provide:

•Introduction

•SUPPLEMENTAL LICENSE AGREEMENT

•New Features in Cisco Unified Provisioning Manager 8.6

•Product Documentation

•Known Problems

•Resolved Problems

•Obtaining Documentation and Submitting a Service Request

Introduction

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

SUPPLEMENTAL LICENSE AGREEMENT

SUPPLEMENTAL LICENSE AGREEMENT FOR CISCO SYSTEMS NETWORK MANAGEMENT SOFTWARE: CISCO UNIFIED PROVISIONING 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.

New Features in Cisco Unified Provisioning Manager 8.6

Cisco Unified Provisioning Manager 8.6 adds the following:

•The ability to add, update, and delete devices through batch provisioning.

•Security Enhancements:

–Logged-in user sessions with audit logging.

–Locking and unlocking user accounts after failed logins.

–Device passwords stored in Provisioning Manager are now encrypted using the AES-128 bit algorithm.

•Support for a corporate email address in the voicemail product.

•Support for space and apostrophe in subscriber IDs.

•Performance improvements when using the Ordering and Service Area user interface.

•Directory Number Block report.

•Subscriber ID search that is not case-sensitive.

•Support for the following analog voice gateways:

–VG202

–VG204

–VG224

•Support for analog phones.

•Support for the following new phone types:

–Cisco E20

–Cisco Dual Mode for Android

–Cisco ATA 187

–Cisco Cius

•Support for Cisco Unified Communications Manager 8.6(1).

•Support for Cisco Unified Communications Manager Express 8.6.

•Support for Cisco Unity Connection 8.6(1).

•Support for Cisco Unity Express 8.6.

•Support for Cisco Unified Presence 8.6(1).

Product Documentation

---

Note We sometimes update the printed and electronic documentation after original publication. Therefore, you should also review the documentation on Cisco.com for any updates.

---

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 8.6	On Cisco.com at the following URL: http://www.cisco.com/en/US/products/ps7125/products_device_support_tables_list.html
Release Notes for Cisco Unified Provisioning Manager 8.6	On Cisco.com at the following URL: http://www.cisco.com/en/US/products/ps7125/prod_release_notes_list.html
Installation Guide for Cisco Unified Provisioning Manager 8.6	On Cisco.com at the following URL: http://www.cisco.com/en/US/products/ps7125/prod_installation_guides_list.html
User Guide for Cisco Unified Provisioning Manager 8.6	On Cisco.com at the following URL: http://www.cisco.com/en/US/products/ps7125/products_user_guide_list.html
Programmer Guide for the Cisco Unified Provisioning Manager Northbound Interface 8.6	On Cisco.com at the following URL: http://www.cisco.com/en/US/products/ps7125/products_programming_reference_guides_list.html

Known Problems

Table 2 describes problems known to exist in this release.

---

Note To obtain more information about known problems, access the Cisco Software Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs. (You will be prompted to log into Cisco.com).

---

Table 2 Known Problems in Provisioning Manager 

Bug ID	Summary	Explanation
CSCtq26704	Change owner for a phone fails when more than one Application Server settings are configured on Cisco Unified Communications Manager (or Cisco Unified Communications Manager Business Edition).	Change owner for a phone fails when a Phone service has a voicemail associated to it along with multiple Application Server configurations in Cisco Unified Communications Manager (or Cisco Unified Communications Manager Business Edition). Workaround: Cancel the phone service (along with the line and voicemail), then provision the services again for the new owner.
CSCtr71649	The Provisioning Manager User Guide lists the command usage for the CUPM-restore.bat utility incorrectly.	The Provisioning Manager User Guide lists the command usage for the CUPM-restore.bat utility incorrect in the following sections: •Restoring the Single-Machine Provisioning Manager Database, Step 6. •Restoring Provisioning Manager for a Distributed Database, Step 6. Workaround: The correct command is CUPM-restore.bat <username> <password> <directory>\<file name to be restored from>
CSCtr67475	The maximum size of the speed dial database field is 1024 characters.	The Speed Dial provisioning attribute can have up to 100 speed dial settings. Each speed dial has the following settings: index, directory number, label, and label ASCII. When you add multiple speed dial settings, if the settings exceed 1024 total characters, the order cannot be submitted and you will encounter a database error saying that the field limit has been reached. This applies to Add Phone and Change Phone orders. Workaround: Limit the length of the label and ASCII label fields or remove some speed dials.
	Batch provisioning cannot set Enable Cisco Unified Mobile Communicator for Cisco Dual Mode for Android.	For Cisco Dual Mode for Android phone, you cannot use batch provisioning to set the Enable Cisco Unified Mobile Communicator attribute. Workaround: None.
	Search page hangs if you click the browser back button after a subscriber search.	When using the Search Subscribers page, if you click the browser's Back button after performing a search for all subscribers, after the results are displayed, the page hangs. Workaround: None.
—	Some special characters cannot be used in the Alias field of a Distribution List.	The following special characters are not supported for use in the Alias field of a Distribution List: " ^ * % : + Workaround: None.
CSCtn22838	When canceling a shared line, the location is listed as N/A for voicemail and email.	When a canceled shared line order is completed, the voicemail, email, and unified messaging may show the location as N/A. This occurs when the original subscriber and the move-to subscriber are in two different Domains. The correct behavior is to display a valid Service Area in the Subscriber's record. Provisioning Manager should automatically pick a line that shares the same directory number and move the voicemail, email, and unified messaging to the subscriber who owns the line. Workaround: None.
CSCtn21473	Some Line provisioning attributes are not rolled back when a Change Line or a Move Services order fails.	If a Change Line or a Move Services order fails, not all of the Line's provisioning attributes are rolled back to their previous configuration. Workaround: Run a subscriber synchronization in Provisioning Manager on the line's Call Processor.
CSCtl50035	The View Order Details page displays incorrect old location details.	When there are multiple Move Service orders and one of the orders fails, a new order is created to roll back the completed services. The View Order Details page for the rollback order displays the original Service Area details instead of the new Service Area. Workaround: None.
CSCso79103	Cannot configure transformation CSS for outbound calls in H323 gateways.	Provisioning Manager does not provision the following H323 gateway fields in Cisco Unified Communications Manager: Called Party Transformation CSS Use Device Pool Called Party Transformation CSS Calling Party Transformation CSS Use Device Pool Calling Party Transformation CSS This problem occurs in all versions of Cisco Unified Communications Manager. Workaround: None.
CSCtg27940	The Last updated by column on the Infrastructure Configuration user interface always displays admin.	The Last updated by column in the Infrastructure Configuration user interface displays admin regardless of which user updates the configured instance. The Manage Orders search page displays the correct username for the user who placed the infrastructure configuration change. Workaround: None.
CSCtg28294	Concurrently running addUser and add batch files corrupts the addUser entries.	When uploading more than one batch file simultaneously (one file is an addUser batch file and the other is an add batch file), some of the addUser batch entries become corrupted. Workaround: Remove the corrupted batch projects and reupload the batch files one at a time. Make sure to wait for the first one to finish before starting the next.
CSCtu02458	After performing distributed upgrade to 8.6, the database backup procedure fails.	After performing distributed upgrade to 8.6, the postgres superuser role is removed. So database backup and administrative functions cannot be performed. Workaround: You can follow the steps given below to regain the superuser privileges for the postgres user: Prerequisites: •Stop the postgres service before executing these steps. •Create the system environment variable PGDATA and set the value to <Installation directory>\pgsql9.0\data. •Ensure that PGSQL_HOME environment variable is set to <Installation directory>\pgsql9.0. Do the following: 1. From the command line move to the following directory: <Installation directory>/pgsql9.0/bin> 2. Enter runas /env / user:cupmuser cmd.exe. 3. Enter the password for cupmuser that was provided during the upgrade. 4. Enter the following: postgres.exe --single postgres alter role postgres superuser 5. Press ctrl+c to close the backend window. You can restart the services and then perform the back up.

In Provisioning Manager, you create Call Processors and Unified Message Processors. Call Processors are proxies for each instance of a Cisco Unified Communications Manager or Cisco Unified Communications Manager Express. Unified Message Processors are proxies for each instance of Cisco Unity, Cisco Unity Express, or Cisco Unity Connection.

Problems can occur while obtaining the data from these devices, due to known problems in certain versions of these devices.

Table 3 lists the known problems and the related device bug IDs. When a related bug is fixed, the problem will no longer exist in Provisioning Manager.

Table 3 Known Problems in Call Processor and Unified Message Processor Devices 

Summary	Explanation
The Media Resource Group infrastructure object does not get synchronized during an infrastructure synchronization.	The Media Resource Group infrastructure object does not get synchronized when all Media Resources in the group have been deleted. The problem is that Cisco Unified Communications Manager allows Provisioning Manager to delete all the media resources when it should not. This problem occurs in all supported versions of Cisco Unified Communications Manager. The related Cisco Unified Communications Manager bug ID is CSCtl19830. Workaround: Do not delete a media resource if it is the last member of a Media Resource Group. If you do delete it, add the media resource back in or delete the empty Media Resource Group.
The Cisco Unified 7926G phone appears as a Cisco Unified 7926 phone on several pages (for example, the Subscriber Records and Phone Inventory pages).	When provisioning the Cisco Unified 7926G phone, Cisco Unified Communications Manager sends the value 7926 instead of 7926G, so Provisioning Manager displays the phone as 7926. The related Cisco Unified IP Phone bug ID is CSCtl85070. Workaround: None.
Infrastructure Provisioning for SIPTrunk completes, but Provisioning Manager does not set the Destination Address SRV attribute.	When provisioning a SIP Trunk, Provisioning Manager does not receive a response from Cisco Unified Communications Manager for the Destination Address SRV attribute. This results in the Destination Address SRV attribute not being set. This problem occurs in all Cisco Unified Communications Manager versions prior to 8.5(1). The related Cisco Unified Communications Manager bug ID is CSCti42863. Workaround: None.
You cannot configure Extension Mobility or Voicemail on phones already provisioned, if the User Locale specified in Cisco Unified Communications Manager is something other than English United States.	When configuring Extension Mobility or Voicemail, if the User Locale attribute is not set to English United States, Cisco Unified Communications Manager sends an error message to Provisioning Manager. The error message states the following: Can't find resource for bundle. This problem occurs in all Cisco Unified Communications Manager versions prior to 8.5. The related Cisco Unified Communications Manager bug ID is CSCtl05612. Workaround: None.
Cannot remove a previously set extension from the Cisco Unity Connection device using the Provisioning Manager user interface.	When a partition is set to a value (on Cisco Unity Connection), if you want to remove it (make it blank) through Provisioning Manager, you cannot. The value remains the same. This problem occurs in Cisco Unity Connection 7.1.3. The related Cisco Unity Connection bug ID is CSCtj90755. Workaround: None.
Distribution List displays duplicate values in Provisioning Manager.	If a user (subscriber) is not a proper Active Directory (AD) entry in the Exchange server, and you use the user to create a distribution list as a member, duplicate values will be created by Cisco Unity. The same type of issue occurs if you change the owner type from Subscriber to Public Distribution List. This problem occurs in all supported versions of Cisco Unity. The related Cisco Unity bug ID is CSCtk08408. Workaround: Make sure the owner user has a proper AD entry in the Exchange server.
Subscriber synchronization does not synchronize all the users, phones, or lines in Cisco Unified Communications Manager.	When you run subscriber synchronization on Cisco Unified Communications Manager, the synchronization is successful, but it does not synchronize some of the users, phones, or lines in Cisco Unified Communications Manager. There may be a missing user or phone or line. This problem occurs in Cisco Unified Communications Manager 8.0.3, usually on deployments with more than 10,000 subscribers. The related Cisco Unified Communications Manager bug ID is CSCti80815. Workaround: None.
The mobility user ID is unset on iPhones or Nokia phones if the value is not specified on the Change Phone order.	During a Change Phone order, if the mobility user ID is not specified, its value is unset on Cisco Unified Communications Manager for Cisco IPhone or Nokia S60. This problem occurs in Cisco Unified Communications Manager 8.0 and later. The related Cisco Unified Communications Manager bug ID is CSCtj13299. Workaround: None.
The Do Not Disturb provisioning attribute does not work for Nokia S60 or Cisco Dual Mode for iPhone.	When provisioning Nokia S60 or Cisco Dual Mode for iPhone, if the Do Not Disturb attribute is set to true, the value is not set in Cisco Unified Communications Manager or in Provisioning Manager. This problem occurs in Cisco Unified Communications Manager 8.0(3) and later. The related Cisco Unified Communications Manager bug ID is CSCth72305. Workaround: None.
Placing a change order for Nokia S60 or Cisco Dual Mode for iPhone fails if a value is not entered for the Mobility User ID provisioning attribute.	When placing a change order for Nokia S60 or Cisco Dual Mode for iPhone, if you do not enter a value for Mobility User ID, an error occurs and the order fails. This problem occurs in Cisco Unified Communications Manager 8.0(3) and later. The related Cisco Unified Communications Manager bug ID is CSCth87450. Workaround: This problem has been fixed in an ES build in Cisco Unified Communications Manager version 8.0(3) (ES build 8.0.3.11002-1).
Line to end-user association does not work for the Line On Shared Phone service.	When you order a Line On Shared Phone service for a subscriber who does not have any services associated, the line-to-end-user association will not be correct. This problem occurs in Cisco Unified Communications Manager 6.x. The related Cisco Unified Communications Manager bug ID is CSCso09231. Workaround: None.
Infrastructure synchronization completes successfully even if you enter a wrong username.	When running an infrastructure synchronization, if you enter the wrong username, Cisco Unified Communications Manager does not send an unauthorization error message. This problem occurs in Cisco Unified Communications Manager 6.1(2). The related Cisco Unified Communications Manager bug ID is CSCti74620. Workaround: None.
Passing a hexadecimal value for MLPP Domain in an Extension Mobility Access order causes the order to fail.	When provisioning Extension Mobility Access, if you enter a hexadecimal value for MLPP Domain, the order fails. This problem occurs in Cisco Unified Communications Manager 8.x. The related Cisco Unified Communications Manager bug ID is CSCth31136. Workaround: None.
You cannot reset the web password or PIN for Cisco Unity Connection 2.0.1 and 2.1.	You cannot use the Reset Password function in Provisioning Manager to reset the Cisco Unity Connection web password or PIN. This problem occurs in Cisco Unity Connection 2.0.1 and 2.1. The related Cisco Unity Connection bug ID is CSCte78626. Workaround: None.
Cannot submit a VoiceRegion infrastructure configuration order.	You cannot place a VoiceRegion infrastructure configuration order through the Infrastructure Configuration feature. This problem occurs in Cisco Unified Communications Manager 8.0(1). The related Cisco Unified Communications Manager bug ID is CSCte99411. Workaround: None.
Deleting a directory number that is not present in a Cisco Unified Communications Manager from Provisioning Manager does not throw an exception.	When you delete a directory number from Provisioning Manager that is not present in a Cisco Unified Communications Manager, an error does not occur. The correct behavior is that an error should occur if the directory number is not present in the Cisco Unified Communications Manager. This problem occurs in Cisco Unified Communications Manager 8.0(1). The related Cisco Unified Communications Manager bug ID is CSCtf63188. Workaround: None.
Cannot remove member Call Pickup Groups.	Member Call Pickup Groups cannot be removed through the Infrastructure Configuration feature. This problem occurs in Cisco Unified Communications Manager 8.0(1). The related Cisco Unified Communications Manager bug ID is CSCtf64105. Workaround: None.
Call Pickup Group values are not unset using batch provisioning.	You cannot unset the following Call Pickup Group values: •Member Call Pickup Groups •Call Pickup Group Notification Policy This occurs in both batch provisioning and the user interface. This problem occurs in Cisco Unified Communications Manager 8.0(1). The related Cisco Unified Communications Manager bug ID is CSCtf46871. Workaround: None.
Directory numbers disappear after modifying a CTI Route Point.	After modifying a CTI Route Point, the directory numbers disappear in Provisioning Manager. This problem occurs in Cisco Unified Communications Manager 4.x. The related Cisco Unified Communications Manager bug ID is CSCtf93365. Workaround: None.
Directory numbers are not updated during a Line Group update.	You cannot update the directory numbers in the Line Group through the Infrastructure Configuration feature. This problem occurs in Cisco Unified Communications Manager 4.x. The related Cisco Unified Communications Manager bug ID is CSCtf72467. Workaround: None.
Running a subscriber synchronization on Cisco Unified Communications Manager, does not synchronize some phones and users in Provisioning Manager.	When you run a subscriber synchronization on Cisco Unified Communications Manager, some phones and users are not synchronized in Provisioning Manager. This problem occurs in Cisco Unified Communications Manager 4.3(2). The related Cisco Unified Communications Manager bug IDs are CSCtb79428 and CSCta94978. Workaround: None.
Unable to order a Phone when Extension Mobility is enabled.	If you order a Phone with Extension Mobility enabled, an error occurs and the order is unsuccessful. This problem occurs in Cisco Unified Communications Manager 4.3(2) SR1c. The related Cisco Unified Communications Manager bug ID is CSCtc92077. Workaround: This problem was fixed in an older version of Cisco Unified Communications Manager 4.3.2 (004.003(002.049)). You can choose to downgrade your Cisco Unified Communications Manager to the fixed version.
AAR Group must be set to provision an H323 Gateway in Cisco Unified Communications Manager.	If you perform an Add order for an H323 Gateway without setting the AAR Group, the order fails on the device. This problem occurs in Cisco Unified Communications Manager 4.1(3). The related Cisco Unified Communications Manager bug ID is CSCtc91505. Workaround: You must specify a value for AAR Group.
Enable SoftPhone Support order fails.	You cannot order Enable SoftPhone Support when the primary extension's directory number is associated with the device. This problem occurs in Cisco Unified Communications Manager 4.x and 5.x. The related Cisco Unified Communications Manager bug ID is CSCsl09935. Workaround: None.
You cannot update the Provide Outside Dial Tone setting in the Translation Pattern infrastructure object.	You cannot update a previously added Provide Outside Dial Tone setting in the Translation Pattern infrastructure object. This problem occurs in all supported versions of Cisco Unified Communications Manager. The related Cisco Unified Communications Manager bug ID is CSCsq91259. Workaround: Delete the Translation Pattern configuration and readd it.
The default codec is not set on Cisco Unified Communications Manager for the Voice Region product.	The default codec is not set for Voice Region. This problem occurs in Cisco Unified Communications Manager 4.1(3). Workaround: None.
A Voice Mail Pilot without a pilot number cannot be updated.	You cannot update a Voice Mail Pilot object that does not already have a directory number set. An error occurs and the update request fails. This problem occurs in all supported versions of Cisco Unified Communications Manager. The related Cisco Unified Communications Manager bug ID is CSCtb54938. Workaround: The Voice Mail Pilot without a pilot number can be updated after you have provided a new value for the pilot number.
The Security Profile provisioning attribute displays values for unsupported phones.	Profiles for phones that are not supported in Provisioning Manager are displayed for the Security Profile provisioning attribute. Following are the unsupported phones that are listed: •Analog Phone •ISDN BRI Phone •IP-STE •Cisco VCG Phone •Cisco VCG Virtual Phone This problem occurs in all supported versions of Cisco Unified Communications Manager. The related Cisco Unified Communications Manager bug ID is CSCtb78547. Workaround: None.
Cisco Unified Communications Manager devices that do not have Unified CM service enabled are listed as available in the Unified CM Group.	Provisioning Manager does not restrict you from adding Cisco Unified Communications Manager devices to the Unified CM Group when those devices do not have the Unified CM service enabled. This problem occurs in all supported versions of Cisco Unified Communications Manager. The related Cisco Unified Communications Manager bug ID is CSCsu11934. Workaround: You should not add as a member Cisco Unified Communications Manager devices that do not have the Unified CM service enabled.
The Gratuitous ARP provisioning attribute value changes from enabled to disabled after performing a change phone operation.	If the Gratuitous ARP provisioning attribute value is set to enabled, after performing a change phone operation, the attribute value is set to disabled. This problem occurs in Cisco Unified Communications Manager 5.x. The related Cisco Unified Communications Manager bug ID is CSCsh61703. Workaround: None.
You cannot set the Connected Line ID Presentation or Connected Name Presentation attributes for a SIP Trunk.	For the SIP Trunk attributes Connected Line ID Presentation and Connected Name Presentation SIP Trunk, you may encounter the following problems: •An error message does not appear when an incorrect configuration scenario is used. For example, if you uncheck the Remote-Party-Id field and set the Connected Line ID Presentation field and Connected Name Presentation field either to Allowed or Restricted, adding these settings succeeds with both fields set to Default. However, adding these settings should not succeed, and you should receive an error message. •You cannot update both fields. If you check the Remote-Party-Id field and try to update both the Connected Line ID Presentation and the Connected Name Presentation fields to either Allowed or Restricted, an error message appears. Workaround: To update both fields, you must delete the current SIP Trunk, then readd the SIP Trunk with both fields set.
The ASCII Label field for Service URL is not provisioned on Cisco Unified Communications Manager.	When configuring Service URL on a Phone (or Extension Mobility Access) through Provisioning Manager, the ASCII Label field for Service URL is not provisioned on Cisco Unified Communications Manager. This problem occurs in Cisco Unified Communications Manager 5.x and 6.x. The related Cisco Unified Communications Manager bug ID is CSCsm52564. Workaround: None.
The CTI Route Point Network attributes Hold Audio Source and User Hold Audio Source are not updated with the selected items when an update operation is performed.	When updating the CTI Route Point Network attributes Hold Audio Source and User Hold Audio Source, the values that are specified do not appear (or are incorrect) once the update operation is completed. This problem occurs in all supported versions of Cisco Unified Communications Manager. The related Cisco Unified Communications Manager bug ID is CSCsq25334. Workaround: None.
When updating Common Device Config, you cannot change the Softkey Template setting.	When updating Common Device Config, the value for the Softkey Template attribute cannot be updated. This problem occurs in Cisco Unified Communications Manager 6.0, 6.1(1), 6.1(2), and 6.1(3). The related Cisco Unified Communications Manager bug ID is CSCsq25334. Workaround: None.
When updating Common Device Config, you cannot update the User Locale attribute.	When updating Common Device Config, the value for the User Locale attribute cannot be updated. This problem occurs in Cisco Unified Communications Manager 6.x and 7.0. The related Cisco Unified Communications Manager bug ID is CSCsu85969. Workaround: None.
An H323 gateway setting is set to true in Provisioning Manager, but in Cisco Unified Communications Manager it is set to false.	When provisioning an H323 gateway, if the attribute Wait for Far End H245 Terminal Set is set to true, Provisioning Manager returns a false value. This problem occurs in Cisco Unified Communications Manager 5.x and 6.x. The related Cisco Unified Communications Manager bug ID is CSCsb28235. Workaround: None.
Unified Messaging Service batch orders fail.	When placing a Unified Messaging Service batch order, one of the orders may fail. This occurs for very large batch orders (10,000 phones) and during the 3:00 AM time frame. This problem occurs in Cisco Unity Connection. The related Cisco Unity Connection bug ID is CSCta60107. Workaround: Rerun the batch order in 1 to 2 minute intervals or avoid running the batch order during the 3:00 AM time frame.
You cannot add a Phone using the Provisioning Manager NBI when LDAP is enabled.	In the Provisioning Manager NBI, if the Provisioning Manager server has LDAP enabled, when you delete a line and then try to readd a phone, the order fails. This problem occurs in Cisco Unified Communications Manager 5.1(2), 5.1(3), and 6.0. The related Cisco Unified Communications Manager bug ID is CSCsl09935. Workaround: None.
The getConfiguredInfraProduct API for SIP Trunk does not return all values.	The getConfiguredInfraProduct API does not return the DTMF Signaling Method value for SIP Trunk. This problem occurs in Cisco Unified Communications Manager 5.x and 6.x. The related Cisco Unified Communications Manager bug ID is CSCsz43673. Workaround: None.
Adding a SIP Trunk fails if you do not provide values for the nonrequired attributes.	If you add a SIP Trunk without entering values for the nonrequired attribute (AAR Group, Prefix DN, Caller Name, and Call ID DN), you get an error. This problem occurs in Cisco Unified Communications Manager 4.1and 4.2. The related Cisco Unified Communications Manager bug ID is CSCsz21917. Workaround: None.
You cannot set the Connected Line ID/Name Presentation attributes for SIP Trunk.	You cannot update the following SIP Trunk attributes: •Connected Line ID Presentation •Connected Name Presentation This problem occurs in Cisco Unified Communications Manager 7.0(1). The related Cisco Unified Communications Manager bug ID is CSCsz17679. Workaround: None.
You cannot retrieve a value for the SIP Trunk attribute Destination Address is an SRV.	You cannot retrieve a value for the SIP Trunk attribute Destination Address is an SRV. This problem occurs in all supported versions of Cisco Unified Communications Manager. The related Cisco Unified Communications Manager bug ID is CSCsz17468. Workaround: None.
Not all SIP Trunk attributes are supported.	Support is missing for the following SIP Trunk attributes: •Packet Capture Mode •Packet Capture Duration •Transmit UTF-8 for Calling Party Name •Presence Group •DTMF Signaling Method This problem occurs in Cisco Unified Communications Manager 5.x, 6.x, and 7.x. The related Cisco Unified Communications Manager bug ID is CSCsz43673. Workaround: None.
The updateOrder API does not update the Voicemail Pilot value.	In the Voicemail Profile infrastructure object, the updateOrder API does not update the Voicemail Pilot value. This problem occurs in Cisco Unified Communications Manager 4.x, 5.x, and 6.0(1). The related Cisco Unified Communications Manager bug ID is CSCsz03009. Workaround: None.
You cannot unset the Network Locale value.	In the Device Pool infrastructure object, you cannot clear the Network Locale value. This occurs in both the Provisioning Manager user interface or the Provisioning Manager NBI. This problem occurs in Cisco Unified Communications Manager 6.1.3. The related Cisco Unified Communications Manager bug ID is CSCsy52746. Workaround: None.
Passing a null value for the device description in a Phone order causes the order to fail.	When ordering a Phone, if you enter nothing (a null value) for the device description, an error occurs and the order fails. This occurs when using either the Provisioning Manager user interface or the Provisioning Manager NBI. This problem occurs in Cisco Unified Communications Manager 6.x. The related Cisco Unified Communications Manager bug ID is CSCsy48420. Workaround: None.
Change orders for the Common Device Config infrastructure object, placed through the user interface or the API, do not update some attribute values.	Change orders for the Common Device Config infrastructure object, placed through the user interface or the API, do not update the following attribute values: •User Locale •Softkey Template This problem occurs in Cisco Unified Communications Manager 4.x, 5.x, and 6.x. The related Cisco Unified Communications Manager bug ID is CSCsq25334 and CSCsu85969. Workaround: None.
The Voicemail Profile infrastructure object cannot be ordered on Cisco Unified Communications Manager.	The Voicemail Profile infrastructure object cannot be configured on Cisco Unified Communications Manager. When Provisioning Manager pushes the Voicemail Profile object to Cisco Unified Communications Manager, an error occurs. This problem occurs in Cisco Unified Communications Manager 5.1(2) and 6.0(1). The related Cisco Unified Communications Manager bug ID is CSCsj39964. Workaround: None.
The Voicemail Pilot infrastructure object cannot be ordered on Cisco Unified Communications Manager.	The Voicemail Pilot infrastructure object cannot be configured on Cisco Unified Communications Manager. When Provisioning Manager pushes the Voicemail Pilot object to Cisco Unified Communications Manager, an error occurs. This problem occurs in Cisco Unified Communications Manager 5.1(2). The related Cisco Unified Communications Manager bug ID is CSCsi80077. Workaround: None.
When creating a Voice Region through the Provisioning Manager NBI, the codec is not set.	When you create a Voice Region using the user interface or the Provisioning Manager NBI, the codec setting is not set to the specified value. This problem occurs in Cisco Unified Communications Manager 5.x and 6.x. The related Cisco Unified Communications Manager bug ID is CSCsu40003. Workaround: None.
Cannot set a Directed Call Park without a partition in Cisco Unified Communications Manager.	If you have two BLF Directed Call Parks with the same number (for example, 100) but with different partitions, when you try to set the value as 100 in the device, it is set as 100 in RP instead of 100. If you create a BLF Directed Call Park without a partition and then try to configure this value, you get the following error: The specified Directed Call Park is not found. This problem occurs in Cisco Unified Communications Manager 6.x and 7.x. The related Cisco Unified Communications Manager bug ID is CSCsu79343. Workaround: This problem has been fixed in interim Cisco Unified Communications Manager 6.x and 7.x builds. To get the interim build, contact the Cisco Technical Assistance Center (TAC), at: http://www.cisco.com/en/US/support/tsd_cisco_worldwide_contacts.html.
The Label ASCII field is not set in Cisco Unified Communications Manager.	The Label ASCII field of the BLF Directed Call Park provisioning attribute is not set properly in Cisco Unified Communications Manager. This problem occurs in Cisco Unified Communications Manager 6.x and 7.x. The related Cisco Unified Communications Manager bug ID is CSCsu79308. Workaround: This problem has been fixed in an interim Cisco Unified Communications Manager 6.1(2) build. To get the interim build, contact the Cisco Technical Assistance Center (TAC), at: http://www.cisco.com/en/US/support/tsd_cisco_worldwide_contacts.html.
The BLF Directed Call Park set-only provisioning attribute does not work correctly with Cisco Unified Communications Manager.	The BLF Directed Call Park set-only provisioning attribute does not work correctly with Cisco Unified Communications Manager. This is due to a Cisco Unified Communications Manager user interface issue. This problem occurs in Cisco Unified Communications Manager 6.0(1). Workaround: None.
Device Mobility Mode is not set on Cisco Unified Communications Manager.	The Device Mobility Mode set-only provisioning attribute is not set on Cisco Unified Communications Manager. This problem occurs in Cisco Unified Communications Manager 4.3(2). The related Cisco Unified Communications Manager bug ID is CSCsw39524. Workaround: This problem has been fixed in an interim Cisco Unified Communications Manager 4.3(2) build. To get the interim build, contact the Cisco Technical Assistance Center (TAC), at: http://www.cisco.com/en/US/support/tsd_cisco_worldwide_contacts.html.
The Label ASCII field is not set in Cisco Unified Communications Manager.	The Label ASCII field of the Busy Lampfield Info provisioning attribute is not set properly in Cisco Unified Communications Manager. This problem occurs in Cisco Unified Communications Manager 7.0(1). The related Cisco Unified Communications Manager bug ID is CSCsw48333. Workaround: This problem has been fixed in an interim Cisco Unified Communications Manager 7.0(1) build. To get the interim build, contact the Cisco Technical Assistance Center (TAC), at: http://www.cisco.com/en/US/support/tsd_cisco_worldwide_contacts.html.
An infrastructure synchronization is shown as completed, even though the wrong credentials were entered for Cisco Unified Communications Manager.	An infrastructure synchronization completes, and instead of getting an error when the wrong credentials are entered for Cisco Unified Communications Manager in Provisioning Manager, you get a message telling you that synchronization has completed successfully. However, none of the infrastructure products are synchronized. This problem occurs in Cisco Unified Communications Manager 6.1(2). The related Cisco Unified Communications Manager bug ID is CSCsw51375. Workaround: None.
The Retry Video Call as Audio value is selected in Cisco Unified Communications Manager, even though the setting was not selected in Provisioning Manager.	When configuring the Retry Video Call as Audio value of an H323 Gateway to false in Provisioning Manager, the value is set to true in Cisco Unified Communications Manager. This problem occurs in Cisco Unified Communications Manager 4.3(2). The related Cisco Unified Communications Manager bug ID is CSCsq88437. Workaround: This problem has been fixed in an interim Cisco Unified Communications Manager 4.3(2) build. To get the interim build, contact the Cisco Technical Assistance Center (TAC), at: http://www.cisco.com/en/US/support/tsd_cisco_worldwide_contacts.html.
Users are not added to the User Group, and setting the Cisco Unified Communications Manager password for the users fails.	During a Phone Service order, the user is not added to the corresponding User Group (End User Group). As a result, the user cannot log into Cisco Unified Communications Manager using his password. This problem occurs in Cisco Unified Communications Manager 7.0(1). The related Cisco Unified Communications Manager bug ID is CSCsw37163. Workaround: This problem has been fixed in an interim Cisco Unified Communications Manager 7.0(1) build. To get the interim build, contact the Cisco Technical Assistance Center (TAC), at: http://www.cisco.com/en/US/support/tsd_cisco_worldwide_contacts.html.
Cannot synchronize phones for Cisco Unified Communications Manager.	In Cisco Unified Communications Manager, if you create a phone with a MAC address (for example, SEP555555555555) and try to update the MAC with the same address (for example, 555555555555), you will receive a duplicate error. If you try to update the phone with a new MAC address, the new MAC address will not be reflected in the Cisco Unified Communications Manager database. As a result, synchronizing the phone is not successful. This problem occurs in all supported versions of Cisco Unified Communications Manager. The related Cisco Unified Communications Manager bug ID is CSCsk93459. Workaround: Delete the phone in Cisco Unified Communications Manager and then recreate the phone. Then perform a subscriber synchronization in Provisioning Manager.
A duplicate MAC address error may occur.	Sometimes when placing an order for a phone service, you will get a duplicate MAC address error. This happens when a phone is ordered, cancelled, and then reordered. This problem occurs in Cisco Unified Communications Manager 4.x and 5.x. The related Cisco Unified Communications Manager bug ID is CSCsq69085. Workaround: None.
Orders fail if the phone description field contains UTF-8 characters.	If you enter UTF-8 characters (for example, Danish or German characters) in the phone description field when adding a phone, the order fails. This occurs because Cisco Unified Communications Manager does not support these special characters in the phone description field. This problem occurs in all supported versions of Cisco Unified Communications Manager. The related Cisco Unified Communications Manager bug ID is CSCsr69414. Workaround: Do not use special characters in the phone description field.
Extension Mobility Access, Extension Mobility Access with Line, and Phone Service with Extension Mobility enabled orders fail.	The following orders placed on Cisco Unified Communications Manager fail: •Extension Mobility Access •Extension Mobility Access with Line •Phone Service with Extension Mobility enabled This problem occurs in Cisco Unified Communications Manager 4.2(3) and 4.3(2). The related Cisco Unified Communications Manager bug ID is CSCsq52523. Workaround: This problem has been fixed in an interim Cisco Unified Communications Manager 4.3 build. To get the interim build, contact the Cisco Technical Assistance Center (TAC), at: http://www.cisco.com/en/US/support/tsd_cisco_worldwide_contacts.html.
Subscribers and their associated products do not appear in Provisioning Manager after a subscriber synchronization if Extension Mobility is enabled.	The products; Extension Mobility Access, Extension Mobility Access with Line, and Phone Service with Extension Mobility enabled are not synchronized during a subscriber synchronization on Cisco Unified Communications Manager. This problem occurs in Cisco Unified Communications Manager 4.3(2). The related Cisco Unified Communications Manager bug ID is CSCsq52523. Workaround: This problem has been fixed in an interim Cisco Unified Communications Manager 4.3 build. To get the interim build, contact the Cisco Technical Assistance Center (TAC), at: http://www.cisco.com/en/US/support/tsd_cisco_worldwide_contacts.html.
Cannot retrieve a subscriber from Cisco Unity Connection if the subscriber's ID contains uppercase characters.	If a subscriber ID with uppercase characters is created in Provisioning Manager, and then Provisioning Manager creates the same subscriber in a Cisco Unity Connection device, the subscriber cannot be retrieved from the Cisco Unity Connection device when Provisioning Manager queries for the subscriber. Cisco Unity Connection converts mixed-case subscriber IDs into all lowercase before saving to its database. Retrieved subscriber IDs will not match the original subscriber IDs that contain uppercase characters. This problem occurs in Cisco Unity Connection 7.0. The related Cisco Unity Connection bug ID is CSCsr05155. Workaround: This problem has been fixed in Cisco Unified Communications Manager, Business Edition Engineering Special 7.0(1.21006.1) with Cisco Unity Connection version 7.0(1)ES12. (For details, see http://ipcbu-cap.cisco.com/loads/readme/UCSInstall_UCOS_7.0.1.21006-1_readme.html.)
The description for Call Pickup Group is not displayed in Cisco Unified Communications Manager.	When configuring the Call Pickup Group in Cisco Unified Communications Manager through Provisioning Manager, the description field for the Call Pickup group cannot be set in Cisco Unified Communications Manager. This problem occurs in Cisco Unified Communications Manager 4.3(2). The related Cisco Unified Communications Manager bug ID is CSCsq88429. Workaround: This problem has been fixed in an interim Cisco Unified Communications Manager 4.3.2 build. To get the interim build, contact the Cisco Technical Assistance Center (TAC), at: http://www.cisco.com/en/US/support/tsd_cisco_worldwide_contacts.html.
The MLPP Domain field does not accept alphabetic characters.	When configuring Cisco Unified Communications Manager devices, you can enter alphabetic characters in the MLPP Domain field for common device configuration or device pool. But if you configure the common device configuration or device pool through Provisioning Manager, the MLPP Domain field cannot contain alphabetic characters. This problem occurs in Cisco Unified Communications Manager 5.x, 6.x, and 7.x. The related Cisco Unified Communications Manager bug ID is CSCsl01858 and CSCsr43379. Workaround: None.
AAR Group is a required field in H323 gateways for Cisco Unified Communications Manager.	If the AAR Group field is set to None, H323 gateways cannot be configured in Cisco Unified Communications Manager. This occurs even though the AAR Group is not a mandatory field in Cisco Unified Communications Manager. This problem occurs in Cisco Unified Communications Manager 4.3(2). The related Cisco Unified Communications Manager bug ID is CSCsm90656. Workaround: None.
Ordering Phone Service with Extension Mobility enabled results in an error.	When using batch ordering to order Phone Service (or Unified Messaging Service) with Extension Mobility enabled, a recoverable error occurs. The following error message appears: You cannot add a line to an extension mobility enabled phone while a user is logged on to that phone. This problem occurs in Cisco Unified Communications Manager 5.1(2) and 5.1(3). The related Cisco Unified Communications Manager bug ID is CSCsk41840. Workaround: In Provisioning Manager, do the following: 1. Go to Infrastructure Configuration > Set Up Devices > Call Processors > View Call Processor. 2. Select the Call Processor on which the order was placed, and perform a subscriber synchronization. 3. Go to Provisioning Dashboard > Manage Activities > My Activities > All Activities. 4. Select the Handle Recoverable Error Activity for the failed order and continue the order.
A Change Line order cannot unset some provisioning attributes.	The following provisioning attributes cannot be unset (clearing the value of an attribute or setting the value to its default) in a Change Line order: •Busy Trigger •Maximum Number of Calls •MLPP No Answer Ring Duration Also, all call forwarding provisioning attributes can be unset to false. This problem occurs in all supported versions of Cisco Unified Communications Manager. The related Cisco Unified Communications Manager bug IDs are CSCsi93796 and CSCsj55139. Workaround: This problem has been fixed in an interim Cisco Unified Communications Manager 5.x build. To get the interim build, contact the Cisco Technical Assistance Center (TAC), at: http://www.cisco.com/en/US/support/tsd_cisco_worldwide_contacts.html.
For CTI Route Points, infrastructure synchronization does not synchronize the Common Device Config value.	After adding a CTI Route Point in a Call Processor and performing an infrastructure synchronization, the Common Device Config value set in Cisco Unified Communications Manager is not synchronized with Provisioning Manager. This problem occurs in Cisco Unified Communications Manager 6.0.1. The related Cisco Unified Communications Manager bug ID is CSCsj24568. Workaround: This problem has been fixed in an interim Cisco Unified Communications Manager 6.0.1 build. To get the interim build, contact the Cisco Technical Assistance Center (TAC), at: http://www.cisco.com/en/US/support/tsd_cisco_worldwide_contacts.html.
Not set is displayed in Provisioning Manager for Phone provisioning attributes set through Provisioning Manager.	After synchronization, Phones provisioned through Provisioning Manager have their provisioning attributes set to Not set. Following are the affected provisioning attributes. •Auto Line Select •Gratuitous ARP •PC Port •PC Voice VLAN Access •Settings Access •Video Capabilities •Web Access This problem occurs in all supported versions of Cisco Unified Communications Manager. The related Cisco Unified Communications Manager bug ID is CSCsh61703. Workaround: None.
The MLPP Domain provisioning attribute does not accept special characters.	The MLPP Domain provisioning attribute setting in Provisioning Manager only supports hexadecimal values (0-9 and A-F), as originally supported in Cisco Unified Communications Manager 4.x. Cisco Unified Communications Manager 5.x and later supports ASCII characters. Provisioning Manager 1.3 does not allow ASCII characters in the attribute setting. This problem occurs in Cisco Unified Communications Manager 5.x and later. The related Cisco Unified Communications Manager bug ID is CSCsl01858. Workaround: None.
Canceling a line does not set the telephone number to a blank (empty) value on Cisco Unified Communications Manager when the directory number of the line is set as the phone number for the user.	When canceling a line, where the phone number and primary extension number are set for a user, the phone number and primary extension number of the user are not set to an empty value on Cisco Unified Communications Manager. This problem occurs in Cisco Unified Communications Manager 5.1(2). The related Cisco Unified Communications Manager bug ID is CSCsl09935. Workaround: None.
You cannot unset the No Answer Ring Duration provisioning attributes.	You cannot unset some Line provisioning attributes either through batch provisioning (using the keyword CUPM_BLANK) or through the Provisioning Manager user interface. You cannot set the following Line provisioning attributes to the default value (no value): •No Answer Ring Duration •MLPP No Answer Ring Duration This problem occurs in Cisco Unified Communications Manager 4.1(3) and 4.2(3). The related Cisco Unified Communications Manager bug ID is CSCsj55139. Workaround: None.
Subscriber synchronization and batch ordering for Cisco Unified Communications Manager 6.0(1) takes a long time to process when compared to the Provisioning Manager-supported versions of Cisco Unified Communications Manager 4.x and 5.x.	The time it takes for subscriber synchronization and batch order processing for a large number of users is longer for 6.0(1) when compared to the Provisioning Manager-supported versions of Cisco Unified Communications Manager 4.x and 5.x. This is due to the reduced AXL performance on Cisco Unified Communications Manager 6.0(1) when compared to the Provisioning Manager-supported versions of Cisco Unified Communications Manager 4.x and 5.x. This problem occurs in Cisco Unified Communications Manager 6.0(1). The related Cisco Unified Communications Manager bug ID is CSCsi41499. Workaround: None.
When a phone has two lines and line 1 is canceled and recreated using a new number, the new number is not applied.	This problem occurs on a phone with two lines. If line 1 is canceled and then recreated with a different number, the first number for line 1 is still listed as the telephone number in the user information. This problem occurs in Cisco Unified Communications Manager 5.1(1) and 6.0(1). The related Cisco Unified Communications Manager bug ID is CSCsi93796. Workaround: This problem has been fixed in an interim Cisco Unified Communications Manager 5.1.3 build. To get the interim build, contact the Cisco Technical Assistance Center (TAC), at: http://www.cisco.com/en/US/support/tsd_cisco_worldwide_contacts.html.
In the Voice Region Configuration Template, for Cisco Unified Communications Manager 5.1(1) and 6.0(1), the Default Codec cannot be set with the values Use System Default or Keep Current Setting.	When creating a Voice Region Configuration Template, the Default Codec field does not list Use System Default or Keep Current Setting. These selections are available on Cisco Unified Communications Manager 5.1(1) and 6.0(1), but are not supported in Provisioning Manager. This problem occurs in Cisco Unified Communications Manager 5.1(1) and 6.0(1). The related Cisco Unified Communications Manager bug ID is CSCsi82847. Workaround: After the voice region is created, make updates to the voice region using the Cisco Unified Communications Manager user interface.
Removing the number from the Contact Number field on the subscriber wizard does not remove the number from the Cisco Unified Communications Manager End User Telephone Number field.	When updating a subscriber's information, if you remove the number from the Contact Number field on the subscriber wizard, the Cisco Unified Communications Manager End User Telephone Number field displays the previous value. The expected behavior would be for the End User Telephone Number field to be blank. This problem occurs in Cisco Unified Communications Manager 5.1(1) and 6.0(1). The related Cisco Unified Communications Manager bug ID is CSCsi93796. Workaround: None.
Members of the CallPickupGroup and the LineGroup are not saved in the Provisioning Manager database.	Provisioning Manager cannot obtain values for the members of the CallPickupGroup and LineGroup objects during synchronization with Cisco Unified Communications Manager. However, these objects can be configured on Cisco Unified Communications Manager using Provisioning Manager. This problem occurs in Cisco Unified Communications Manager 4.1(3) and 4.2(1). The related Cisco Unified Communications Manager bug IDs are CSCsf07468 and CSCsf07560. Workaround: None.
In some cases, a change phone order changes the phone load name on Cisco Unified Communications Manager.	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 Communications Manager is using the default phone load). Also, the problem results in different situations for the Provisioning Manager supported versions of Cisco Unified Communications Manager 4.x and 5.x: •In the Provisioning Manager supported versions of Cisco Unified Communications Manager 4.x, a change phone order sets the phone load name with the default phone load name. •In the Provisioning Manager supported versions of Cisco Unified Communications Manager 5.x, only when a module load name is present does performing a change phone order set the phone's load name with the module load name. This problem occurs in all supported versions of Cisco Unified Communications Manager 4.x and 5.x. The related Cisco Unified Communications Manager bug IDs are CSCsh26744 and CSCsh58736. Workaround: None.
Change phone orders fail on Cisco Unified Communications Manager 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 keep the same MAC address, the order fails. This occurs because Cisco Unified Communications Manager does not delete the autogenerated profile on Cisco Unified Communications Manager. Therefore it is attempting to regenerate the same autogenerated profile. This problem occurs in Cisco Unified Communications Manager 4.2(1). The related Cisco Unified Communications Manager bug ID is CSCsd60519. Workaround: Before placing the change order, remove the autogenerated device profile from Cisco Unified Communications Manager.
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 does not occur.	In Cisco Unified Communications Manager, the following provisioning attributes are set to False: •Forwarded Call Information - Caller Name •Forwarded Call Information - Dialed Number These attributes must be set to True for call forwarding to occur. This problem occurs in all Provisioning Manager supported versions of Cisco Unified Communications Manager 4.x. The related Cisco Unified Communications Manager bug ID is CSCsg37872. Workaround: After creating a Service Area, set these provisioning attributes to True.
The MLPP Domain ID is not set on the Cisco Unified Communications Manager when an H323 gateway is created through Configuration Templates.	The MLPP Domain ID is not set for Cisco Unified Communications Manager. This problem occurs in all Provisioning Manager supported versions of Cisco Unified Communications Manager 4.x. The related Cisco Unified Communications Manager bug ID is CSCsh56843. Workaround: None

Resolved Problems

Table 4 describes problems that were fixed in this release.

---

Note To obtain more information about resolved problems, access the Cisco Software Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs. (You will be prompted to log into Cisco.com).

---

Table 4 Problems Resolved in Provisioning Manager  

Bug ID	Summary	Explanation
CSCtn23424	Distribution List batch change order failed for Distribution List member information.	You could not modify a Distribution List in batch provisioning using the column headers Add-New-Members or Remove-Members. Now you can modify a Distributed List infrastructure object accordingly.
CSCtn22627	Could not provision a Distribution List on Cisco Unity using the submitConfigTemplate API.	You could not provision the Distribution List infrastructure object on a Cisco Unity device using the Configuration Template API. Now you can provision the Distribution List infrastructure object using the Configuration Template API.
CSCtn21507	Change Phone and Move Service for Nokia phone failed when the DND Option attribute was empty.	Change Phone order for a Nokia S60 phone failed if you set the attribute DND Option to an empty value. Also, the Move Service operation (with Apply New SA Settings selected) on a Nokia S60 phone failed when the phone was moved to a Service Area where the DND Option value was empty. Now the Change Phone order and the Move Service operations for a Nokia S60 phone work correctly.
CSCtn20298	The Voicemail Display Name value would change when a service was moved.	When a move service operation was run on a voicemail and the Apply New SA Setting was selected, the voicemail display name of the service would change. Now the voicemail display name does not change.
CSCtn08676	Prebuilt Cisco IOS templates that contain a dollar sign as part of a command line did not allow you to update any keyword settings.	If you imported a prebuilt Cisco IOS template that contained a dollar sign ($) as part of a Cisco IOS command line, you could not update any keyword settings once this prebuilt item was saved as a member of a template. Now entering a dollar sign does not affect updating keyword settings.

Obtaining Documentation and Submitting a Service Request

For information on obtaining documentation, submitting a service request, and gathering additional information, 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

Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0.

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

Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)

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