Cisco Cisco Unified Provisioning Manager 8.6 Release Notes

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: 

.

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.