Cisco Cisco TelePresence Management Suite (TMS) Version 15 Release Notes
Resolved issues
Cisco TelePresence Management Suite 13.2 Software Release Notes
Page 6 of 14
Reporting
Identifier
Bug Description
CSCtw32913 Resolved the issue where if the user language was set to Japanese, clicking Conference Report
from
Booking > List Conferences
generated a PDF with corrupted field format.
CSCtx47627 Resolved the issue where exporting any report to pdf resulted in corrupt formatting if the user
language was set to Japanese
CSCtx40081 Resolved the issue where the Conference Id was duplicated in the Endpoint CDR reporting under
Systems > Navigator >
select an endpoint
> Logs
tab
> Call Log.
This occurred for ad hoc calls
where the call was made on an endpoint within 3 minutes of the previous conference including that
endpoint ending.
endpoint ending.
Booking
Identifier
Bug Description
CSCtx11536 Resolved the issue where Cisco TMS did not redial participants the number of times specified in
Administrative Tools > Configuration > Conference Settings > Conference
Connection/Ending Options > Connection Attempts for Scheduled Calls
Connection/Ending Options > Connection Attempts for Scheduled Calls
when the participants
failed to connect when the conference started.
CSCtx45425 Resolved the issue where it was possible to save a recurring weekly conference with invalid extra
occurrences added in between the weekly occurrences.
CSCtx45434 In Cisco TMS Scheduler the wording for Record Conference in French (Enregistrer la
conference) has been changed. The wording is now Enregistrer le flux audio/video.
CSCtx11035 Resolved the issue where modifying the first occurrence of a recurrent series, and then modifying
the series (from a different occurrence) and selecting the option of Only the occurrences with no
modifications, still overwrote the individual modification of the first occurrence.
modifications, still overwrote the individual modification of the first occurrence.
CSCtx45428 Resolved the issue where it was not possible to book audio calls on a Cisco E20 endpoint from
Cisco TMS.
This occurred because the number of possible audio calls defaulted to 0 for endpoints which didn’t
report their audio capability to Cisco TMS.
From version 13.2 Cisco TMS will default the number of audio calls to 1 instead of 0 if an endpoint
does not report this information.
This occurred because the number of possible audio calls defaulted to 0 for endpoints which didn’t
report their audio capability to Cisco TMS.
From version 13.2 Cisco TMS will default the number of audio calls to 1 instead of 0 if an endpoint
does not report this information.
CSCtw94864 Resolved the issue where it was not possible to change the layout for a cascaded conference
booked using a conference template.
This only occurred if the participants in the template had been amended since it was originally
created.
This only occurred if the participants in the template had been amended since it was originally
created.
CSCtw91412 Resolved the issue where a conference booked using a conference template could initiate on a
different MCU port and therefore with a different dial-in number than the one it was originally
allocated on.
allocated on.
CSCtu30313 Resolved the issue where it was not possible to launch a conference from Cisco TMS on a
TANDBERG Classic MCU running Dx.x software. Although it was possible to complete the booking
of the conference on the MCU, the conference would fail to launch.
This issue occurred in Cisco TMS versions 13.1, 13.1.1, and 13.1.2.
of the conference on the MCU, the conference would fail to launch.
This issue occurred in Cisco TMS versions 13.1, 13.1.1, and 13.1.2.
CSCtw83700 Resolved the issue where an error occurred when entering two or more correctly separated email
addresses under
Booking > New Conference >
add participants using the
Add Participants
pop-
up window and click OK
> Conference Information
tab > Send E-mail to: field.
CSCtx45439 Resolved the issue where it was not possible to move a recurrent meeting series into the future and
save it, using the Start time/End time fields in
Booking > New Conference
after using the
Recurrence Settings
pop-up window. Viewing and clicking OK in the
Recurrence Settings
pop-up
window after editing the Start time/End time fields reset the meeting series back to the original
start date.
start date.