Cisco Cisco TelePresence Management Suite (TMS) Version 15 Release Notes
Limitations
Cisco TMS Release Notes (14.2.1)
Page 28 of 33
Identifier
Description
CSCud66234 Inconsistencies with Call Detail Records when using billing codes.
CSCud81781 User Call Detail Records do not work correctly.
CSCue18466 Cisco TMS does not resolve systems correctly. For example, if endpoint A and endpoint B are
connected to the same MCU conference, attempting to mute or disconnect endpoint A actually
mutes or disconnects endpoint B. This occurs only when using an E.164 dial plan.
mutes or disconnects endpoint B. This occurs only when using an E.164 dial plan.
CSCue18575 Cisco TMS allows overbooking of ports on a Cisco (Radvision) MCU.
CSCue26779 Cisco TMS consumes ports after a conference has been moved to a different MCU. This only
occurs for recurrent conferences, if an instance is moved to a different MCU.
CSCue50533 It is not possible to book a conference using H.323 direct mode for a Cisco TelePresence T3
system.
CSCue66084 Searching a phone book created from source Manual List or All Systems does not search all
entries correctly.
CSCue92568 Cisco TMS incorrectly gives a No HTTP Response error for Polycom systems when their
credentials are out of sync.
CSCuf00874
The provisioning phone book still contains entries for users that have been removed from the
group that syncs with the provisioning phone book source.
group that syncs with the provisioning phone book source.
CSCuf21982
Cisco TMS changes the call direction to dial in when scheduling an One Button To Push
conference using a dial out Participant Template.
conference using a dial out Participant Template.
CSCuf30845
Cisco TMS is unable to generate Call Detail Records from the TANDBERG ISDN Gateway.
CSCuf34881
It is not possible to remove a large number of event notifications for a user in a single operation.
CSCuf57343
Changing the password for a system in
Systems > Navigator >
select a system running TC or TE
software
> Settings > Edit Settings > Network Settings >
H323 Password/SIP Password erases
the password and does not set the new password.
CSCuf81178
It is not possible to move a participant to an Operator Conference if Cisco TMS is configured with
a setup/teardown buffer of more than 3 minutes.
a setup/teardown buffer of more than 3 minutes.
CSCuf93871
TMSNG database access becomes slow due to log table purge taking place during business
hours.
hours.
Limitations
Feature
Limitation
Time zone
support
support
n
The Cisco TMS server time zone cannot be changed.
n
trying to change a system running TE or TC software to the time zone UTC+04:00 (Moscow, St.
Petersburg, Volgograd) you will get an error: Could not update all settings. Details: System did not
accept time zone UTC+04:00 (Moscow, St. Petersburg, Volgograd)
Administrators experiencing this issue should manually set the time zone on the system. The
offset will be different in Cisco TMS, but there should be no issues with booking or conference
start/end times.
Petersburg, Volgograd) you will get an error: Could not update all settings. Details: System did not
accept time zone UTC+04:00 (Moscow, St. Petersburg, Volgograd)
Administrators experiencing this issue should manually set the time zone on the system. The
offset will be different in Cisco TMS, but there should be no issues with booking or conference
start/end times.
A time zone mismatch error will show on these systems in Cisco TMS.