Cisco Cisco TelePresence Management Suite (TMS) Version 15 Release Notes
Resolved issues
Cisco TelePresence Management Suite Release Notes Software Release Notes (14.4.2)
Page 26 of 65
Identifier
Description
CSCuo49879
All current products now display Manufacturer: Cisco instead of Tandberg.
CSCuo49882
Resolved the issue seen when selecting time zone: 'GMT -03:00 Buenos Aires, Georgetown,
Montevideo' on an endpoint running Cisco TelePresence TC v 7.1. The following error ticket
displayed for the system in Cisco TMS: "Time Zone set in TMS for system is different from Time
Zone on system. - In TMS: (UTC-03:00) Buenos Aires, Georgetown, On System: (UTC) Dublin/
Edinburgh/ Lisbon/ London". Trying to push the correct time zone to the system from Cisco
TMS failed with the error: "Could not update all settings. Details: System did not accept time
zone GMT-03:00 (Buenos Aires, Georgetown)".
Montevideo' on an endpoint running Cisco TelePresence TC v 7.1. The following error ticket
displayed for the system in Cisco TMS: "Time Zone set in TMS for system is different from Time
Zone on system. - In TMS: (UTC-03:00) Buenos Aires, Georgetown, On System: (UTC) Dublin/
Edinburgh/ Lisbon/ London". Trying to push the correct time zone to the system from Cisco
TMS failed with the error: "Could not update all settings. Details: System did not accept time
zone GMT-03:00 (Buenos Aires, Georgetown)".
CSCun25307
Warnings about H.323 gatekeeper mode have been removed for bridges behind a
TelePresence Conductor.
TelePresence Conductor.
CSCun27576
Resolved the issue where searching for a system using the host name could fail.
CSCun79003
Resolved the issue that occurred when adding a TelePresence Conductor running XC 2.3 to
Cisco TMS. The management address stayed blank in
Cisco TMS. The management address stayed blank in
Systems > Navigator
, and a ticket
stating "The management address on the system is incorrectly configured ..." was displayed.
Phone Books
Identifier
Description
CSCun25502
Resolved the issue where phone book entries that appeared in more than one phone book
could appear as duplicated in phone book searches. Duplicate entries should appear only
once in search results.
could appear as duplicated in phone book searches. Duplicate entries should appear only
once in search results.
CSCuj42053
Resolved the issue where adding a new entry to a phone book set on a Polycom endpoint did
not update the phone book on the endpoint with that new entry.
not update the phone book on the endpoint with that new entry.
CSCul84164
Reinstated the missing bandwidth options: Auto, Telephone and Max for Manual List phone
book source contacts.
book source contacts.
Reporting
Identifier
Description
CSCug10144
Reporting > Conferences > Conference Statistics >
Calculate By: Utilization has been
removed as it was not possible to calculate this data by utilization, and the generated graph
was always empty.
was always empty.
CSCun25641
Resolved the issue where it was not possible to filter MCU Call Detail Records by Call
Protocol.
Protocol.
Recurrence
Identifier
Description
CSCun81304
Resolved the issue where editing a recurrent conference series with recurrence pattern ' First
Day of every month' changed the recurrence pattern to 'First Sunday of every month'.
Cancelling the edit and then saving the conference changed it from a recurrent to a non-
recurrent conference.
Day of every month' changed the recurrence pattern to 'First Sunday of every month'.
Cancelling the edit and then saving the conference changed it from a recurrent to a non-
recurrent conference.
CSCun81313
Resolved the issue where deleting the first occurrence of a recurrent series, then editing the
series to disable recurrence, deleted all occurrences of the conference. The instance that was
edited to remove recurrence should have remained as a non-recurrent conference.
series to disable recurrence, deleted all occurrences of the conference. The instance that was
edited to remove recurrence should have remained as a non-recurrent conference.