Cisco Cisco TelePresence Management Suite (TMS) Version 15 Release Notes
Resolved issues
Cisco TMS Release Notes (14.3)
Page 29 of 43
Reporting
Identifier
Description
CSCud07720
Resolved the issue where Cisco TMS did not log boot events from the Cisco TelePresence
Supervisor MSE 8050 or the Cisco TelePresence ISDN Gateway.
Supervisor MSE 8050 or the Cisco TelePresence ISDN Gateway.
CSCtr32354
Resolved the issue where Cisco TMS displayed an error in
Reporting > Billing Code Statistics
,
when trying to view detailed data records for billing codes that contain certain UTF-8 characters
(for example: æ,ø,å,# and &).
(for example: æ,ø,å,# and &).
CSCud07585
Resolved the issue where a boot event for a Cisco TelePresence MCU did not show in Cisco
TMS when the MCU rebooted. Now, a boot event will always show immediately in Cisco TMS,
but if the MCU is not available yet to report a reason for its reboot, no reason will be shown in
Cisco TMS.
TMS when the MCU rebooted. Now, a boot event will always show immediately in Cisco TMS,
but if the MCU is not available yet to report a reason for its reboot, no reason will be shown in
Cisco TMS.
CSCty13851
Resolved the issue where Cisco TMS sent an incorrect “Conference ends in 5 minutes”
message for a conference stretching over several days.
message for a conference stretching over several days.
CSCtw61036
Resolved the issue where Cisco TMS didn’t generate a "Lost Response" trap log event for Cisco
VCS systems if the network connection was lost.
VCS systems if the network connection was lost.
CSCud07502
Resolved the issue in the
Reporting
pages where the date picker and date input fields used an
inconsistent date format. The date picker used an American date format (month/date), while the
date input field used a European date format (date/month).
date input field used a European date format (date/month).
CSCty67470
Resolved the issue where an SQL timeout error occurred when viewing Gateway CDR.
Booking API (Cisco TMSBA)
Identifier
Description
CSCud16387
Resolved the issue where GetDefaultConference method did not contain IP Bandwith or ISDN
Bandwith elements.
Bandwith elements.
This issue only occurred when the client specified an API version later than 3.
CSCud07675
Resolved the issue where a misleading error message was displayed if no option key was
installed. The error message was: "There are no Application Integration options installed".
installed. The error message was: "There are no Application Integration options installed".
CSCuc01451
CSCtx29637
Implemented support for ParticipantCallType Directory, allowing phone book entries to be used
as participants.
as participants.
CSCtz01880
Resolved the issue where all bookings from Microsoft Outlook (through Cisco TMSXE) and IBM
Lotus Notes (through Cisco TMSXN) failed displaying the error: "You do not have enough
licenses to book this conference" even though licenses were in place. The bookings did not
show in Cisco TMS.
Lotus Notes (through Cisco TMSXN) failed displaying the error: "You do not have enough
licenses to book this conference" even though licenses were in place. The bookings did not
show in Cisco TMS.
CSCud07475
Resolved the issue where Cisco TMS returned one too many days when booking conferences
through the booking API (Cisco TMSBA’s function GetConferencesForUser).
through the booking API (Cisco TMSBA’s function GetConferencesForUser).
TMS Tools
Identifier
Description
CSCuc65089
Resolved the issue in TMS Tools where settings for Cisco TMSPE database connections were
configurable in deployments without Cisco TMSPE.
configurable in deployments without Cisco TMSPE.