Cisco Cisco TelePresence Management Suite (TMS) Version 15 Release Notes
Open issues
Cisco TelePresence Management Suite 13.2 Software Release Notes
Page 8 of 14
General
Identifier
Description
CSCtw71637 Resolved the issue where searching for a system in the top right search field in Cisco TMS by using
firstname, space, then the first letter of the second name, returned an exception or extra characters
along with the system name.
along with the system name.
CSCtu38205 Resolved the issue where the list of systems generated from
Systems > System Upgrade >
System Upgrade >
select systems
>
click Next could not be sorted by clicking on a column
heading.
CSCtq96599 Resolved the issue where editing the ISDN dial in number for an IP zone caused the same ISDN
dial in number to appear in the same field in the next IP zone viewed, if the latter did not have an
ISDN dial in number set.
ISDN dial in number set.
CSCtr32373
Resolved the issue where Cisco TMS did not use IP zones correctly to determine the most
appropriate MCU to use if the participants were all using SIP and MCU failover was activated.
appropriate MCU to use if the participants were all using SIP and MCU failover was activated.
Open issues
The following issues apply to this version of Cisco TMS.
Identifier
Summary
CSCtw61036 Cisco TMS does not generate a "Lost Response" trap log event for Cisco VCS systems if the
network connection is lost.
CSCtx29637
Using the GetConference() and SaveConference() Cisco TMS Booking API functions fail if using a
"Directory" ParticipantCallType.
"Directory" ParticipantCallType.
CSCtw63828 A user who belongs to a group which has Read Only access to a system is not able to view tickets
for that system in
Systems > Ticketing Service
.
CSCtr08909
In
Monitoring > Conference Control Center
when participants are moved from a scheduled
conference to another conference, the participants still get the end conference notifications from
the conference that they were moved from.
the conference that they were moved from.
CSCtr17122
No Duration data is displayed for Cisco VCS in
Systems > Navigator > Active Calls
tab.
CSCtr32285
In
Systems > Navigator >
select system
> Settings
tab
> Persistent Setting
, the SIP URI field is
empty even though the SIP URI has been set using
Systems > Manage Dial Plan
.
CSCtr32338
In
Systems > Navigator
, select a Cisco TelePresence Server
Settings > Extended Settings
, the
First meeting ID field has a limit of 9 digits. The Cisco TelePresence Server has a limit of 32.
In
In
Systems > Navigator
, select a Cisco TelePresence MCU
Settings > Extended Settings
, the
First meeting ID field has a limit of 19 digits. The Cisco TelePresence MCU has a limit of 32.
CSCtr32354
In
Reporting > Billing Code Statistics
, when trying to view detailed data records for billing codes
that contain certain UTF-8 characters (æ,ø,å,# and &), Cisco TMS displays an error.
CSCtr32376
When changing conference owner for a conference booked in Cisco TMS Scheduler, both previous
and current owner will see the meeting in
and current owner will see the meeting in
Schedulers > My Conferences
page.
CSCtr32413
When booking one or more endpoints and a Cisco TelePresence Content Server through the
booking API, the booking sometimes fails with a There are not enough resources on any MCU to
host your conference. Please go back and remove some of the participants, or lower the
conference bandwidth.
booking API, the booking sometimes fails with a There are not enough resources on any MCU to
host your conference. Please go back and remove some of the participants, or lower the
conference bandwidth.
CSCtr35038
When a participant is added and then disconnected using Cisco TMS
Monitoring > Conference
Control Center
from a permanent conference created on a Cisco MCU, the participant incorrectly
remians as a pre-configured participant on the Cisco MCU.
CSCtr91535
Booking an external audio ISDN dial-out using a C-series endpoint will fail.