Cisco Cisco TelePresence Management Suite (TMS) Version 15 Release Notes
Open issues
Cisco TelePresence Management Suite 13.2.2 Software Release Notes
Page 4 of 10
Open issues
Identifier
Summary
CSCua28639 Incorrect distribution of participants in cascaded conference template: If you create a conference
template with No Distribution routing, then create another conference template with Best Impression
routing which requires cascading, the number of participants distributed to each MCU in the second
conference template is incorrect.
This is resolved in a forthcoming release of Cisco TMS.
routing which requires cascading, the number of participants distributed to each MCU in the second
conference template is incorrect.
This is resolved in a forthcoming release of Cisco TMS.
CSCtr17122
In
Systems > Navigator >
select a Cisco VCS
> Active Calls
tab, the Duration column does not
show any data when there are active calls on the Cisco VCS.
CSCtw61036 Cisco TMS does not generate a "Lost Response" trap log event for Cisco VCS systems if the
network connection is lost.
This is resolved in a forthcoming release of Cisco TMS.
This is resolved in a forthcoming release of Cisco TMS.
CSCtx29637
Using the GetConference() and SaveConference() Cisco TMS Booking API functions fail if using a
"Directory" ParticipantCallType.
This is resolved in a forthcoming release of Cisco TMS.
"Directory" ParticipantCallType.
This is resolved in a forthcoming release of Cisco TMS.
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.
conference that they were moved from.
CSCtr32285
In
Systems > Navigator >
select system
> Settings
tab
> Persistent Settings
, the SIP URI field is
empty even though the SIP URI has been set using
Systems > Manage Dial Plan
.
This is resolved in a forthcoming release of Cisco TMS.
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.
This is resolved in a forthcoming release of Cisco TMS.
This is resolved in a forthcoming release of Cisco TMS.
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.
This is resolved in a forthcoming release of Cisco TMS.
This is resolved in a forthcoming release of Cisco TMS.
CSCtr32376
When the conference owner for a conference booked in Cisco TMS Scheduler is changed, both the
previous and the new current owner will see the meeting in the
previous and the new current owner will see the meeting in the
Scheduler > My Conferences
page.
CSCtr35038
When a participant is added to and then disconnected from a permanent conference created on a
Cisco TelePresence MCU, using Cisco TMS
Cisco TelePresence MCU, using Cisco TMS
Monitoring > Conference Control Center,
the
participant incorrectly remains as a pre-configured participant on the MCU.
CSCtr91647
Cisco TMS always adds a Cisco TelePresence MCU for point-to-point calls with C-series endpoints
if the IP bandwidth for the conference is set to more than 6000 Kbps. This occurs even though the
field External MCU Usage in Routing is set to Always, except point to point (
if the IP bandwidth for the conference is set to more than 6000 Kbps. This occurs even though the
field External MCU Usage in Routing is set to Always, except point to point (
Administrative
Tools > Configuration > Conference Settings > Advanced Conference Options
pane).