Cisco Cisco Unified Provisioning Manager 8.6 發佈版本通知

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.