Cisco Cisco TelePresence Management Suite (TMS) Version 15 Release Notes

Page of 10
 
Resolved issues 
Cisco TelePresence Management Suite 13.2.2 Software Release Notes 
Page 2 of 10 
Resolved issues 
The following issues were found in previous releases and were resolved in 13.2.2: 
Booking 
 
Identifier 
Bug Description  
CSCub45522  Resolved the issue when booking a conference where Japanese characters in an external 
participant dial-in name were replaced with ‘???’. This fix will only work for newly created 
conferences: all participants already saved prior to upgrading to 13.2.2 will continue to display ‘???’ 
instead of the Japanese characters. 
CSCuc81304  Resolved the issue where an error was displayed when booking a conference with a Cisco 
TelePresence T3 System, when the preferred Cisco TelePresence Server for the T3 is also 
managed by the same Cisco TMS.  
The error occurred when selecting 
Booking > New Conference >
 Add the participants 
Connection Settings >
 Distribution: Best Impression.
 
CSCua87774  Resolved the issue where a stack trace error was displayed when attempting to book a recurrent 
conference in 
Booking > New Conference
. This occurred when clicking on Add Participants, if 
the user booking the conference had restricted booking permissions set, and another user had 
previously booked a conference for the same time period with the same systems.  
 
CSCua81843  Resolved the issue where point-to-point conferences scheduled from Cisco TMS with a bandwidth 
of 1920k and above were downspeeded to 384k if the dialing participant was a Polycom system.
 
Systems Management  
 
Identifier 
Bug Description  
CSCuc81348  Added further settings to Configuration Templates for F9.x and TC5.x software.
 
CSCuc81357  Resolved the issue where changing to secure management in Cisco TMS did not update affected 
systems until 
Administrative Tools > Network Settings > TMS Services>
 Enforce Management 
Settings on Systems 
>
 Enforce Now was clicked.  
CSCuc81292  Resolved the issue where the incorrect name could appear in Configuration Templates for E20 and 
systems running TC software.  
Phone Books 
 
Identifier 
Bug Description  
CSCuc13591  Resolved the issue where an endpoint that is in H.323 direct call setup mode, and has no SIP, H323 
ID or E.164 alias, will not appear in the Cisco TMS Endpoints phone book source. 
Monitoring 
 
Identifier 
Bug Description  
CSCub01168  Java 7 introduced a defect (Java bug ID 6997116) which caused conferences in 
Conference 
Control Center
 not to load.  
This was partly fixed in Java 7 update 7, but there were still image loading issues that have now 
been resolved with a Java rendering function change in Cisco TMS.