Cisco Cisco Unified Provisioning Manager 8.6 Release Notes

Page of 26
 
22
Release Notes for Cisco Unified Provisioning Manager 8.6
OL-25476-01
  Known Problems
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.
Table 3
Known Problems in Call Processor and Unified Message Processor Devices (continued)
Summary
Explanation