Cisco Cisco TelePresence Management Suite (TMS) Version 15 Release Notes
Limitations
Cisco TMS Release Notes (14.2.2)
Page 29 of 33
Identifier
Description
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.
Booking
n
In mixed Cisco Unified CM / Cisco VCS deployments, infrastructure systems must be deployed on
the Cisco VCS side to be bookable by Cisco TMS.
the Cisco VCS side to be bookable by Cisco TMS.
n
You must let a minimum of one occurrence in a conference series follow the original recurrence
pattern, or Cisco TMS will not be able to update all occurrences as one series.
pattern, or Cisco TMS will not be able to update all occurrences as one series.
n
Using setup and teardown buffers for conferences is incompatible with Cisco TMSXE, Smart
Scheduler, and any other clients using Cisco TelePresence Management Suite Extension
Booking API. Further API limitations are listed in the documentation of each affected extension as
well as Cisco TelePresence Management Suite Extension Booking API Programming Reference
Guide.
Scheduler, and any other clients using Cisco TelePresence Management Suite Extension
Booking API. Further API limitations are listed in the documentation of each affected extension as
well as Cisco TelePresence Management Suite Extension Booking API Programming Reference
Guide.
Monitoring
and
reporting
and
reporting
n
Conferences using FindMe and Multiway may cause duplicates in Conference Control Center and
Reporting.
Reporting.
n
When making an ad hoc call which involves an endpoint which is registered to Cisco Unified CM,
the system may appear twice in Conference Control Center.
the system may appear twice in Conference Control Center.
WebEx
n
Advanced recurrence patterns are not supported for WebEx Enabled TelePresence.When
booking from the
booking from the
New Conference
page, select to include WebEx before specifying the
recurrence pattern, and only the supported patterns will be made available for selection.
n
Deleting a recurrent meeting series while one instance is ongoing will delete the meeting in Cisco
TMS but not in WebEx. This is because WebEx does not allow changes to ongoing meetings, this
includes deletion.
TMS but not in WebEx. This is because WebEx does not allow changes to ongoing meetings, this
includes deletion.