Manualshelf

Release Notes

ManualsBrandsCisco Manualsvideo conferencing systemsCisco TelePresence Management Suite (TMS) Version 15
41424344454647484950
Resolved issues
Cisco TelePresence Management Suite Release Notes Software Release Notes (14.4.1) Page 42 of 61
Identifier Description
CSCuf32756 The setting Systems > Navigator > select a TelePresence Server> Settings > Extended
Settings >Port Reservation has been changed to Limit Ports to Number of Scheduled
Participants for consistency with the MCU products.
CSCty88233 Resolved the issue where Cisco TMS did not set a port limit for TelePresence Servers. This is only
supported for TelePresence Servers running software version 2.2 or later.
CSCue94672 Resolved the issue where the Database Scanner Service did not automatically refresh managed
systems.
Phone Books
Identifier Description
CSCue28933 Resolved the issue with the Cisco TMS Provisioning Directory phone book source where it was
not possible to expand the root directory to view any subfolders containing provisioning users.
CSCue22884 Resolved the issue where searching on the TMS Endpoints phone book source could return an
incorrect number of entries.
Monitoring
Identifier Description
CSCug37698 Resolved issue where some Java/browser combinations were sometimes very slow or unable to
run Conference Control Center.
CSCug28886 Resolved the issue where having a blank TelePresence Server password caused commands
sent to participants in a conference hosted on a TelePresence Server via Conference Control
Center to fail.
Reporting
Identifier Description
CSCud95025 Resolved the issue where Cisco TMS could not resolve feedback from Cisco TelePresence MCU
5300 series MCUs. This resulted in no Call Detail Records (CDRs) being created if Cisco TMS did
not recognize the cause code reported by the MCU.
CSCue00174 Resolved the issue with creating a pdf report via Booking > List Conferences > Conference
Report where the generated pdf could include blank pages and some data was illegible.
CSCud78269 Resolved the issue where generating CDR reports when the logged in user's language was
Japanese included TANDBERG instead of CISCO in the title of the report.
Time Zones
Identifier Description
CSCud89551 Resolved the issue where creating a weekly recurrent conference as a user in for example, time
zone GMT+11, when the Cisco TMS server was in for example, time zone GMT-5, led to the
conference being saved on the incorrect date.
This occurred only when selecting a day for the recurrence, and when the user time zone and the
server time zone were on a different day.