Cisco Cisco TelePresence Management Suite (TMS) Version 15 Release Notes
Resolved issues
Cisco TMS Release Notes (14.2.2)
Page 24 of 33
Identifier
Description
CSCua28639
Resolved the issue with 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.
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.
CSCtx29067
It is now also possible to use a 10 digit base ISDN number starting with any digit in
Systems >
Navigator >
select an MCU
> Settings > Extended Settings >
ISDN Gateway DID First
Number.
CSCtr32338
Character limit for
Systems > Navigator > Extended Settings >
First Meeting ID for MCU and
TelePresence Server increased to 19. Leading zeroes are supported.
CSCuc88003
Resolved the issue where Cisco TMS was unable to handle a search in
Systems >
Configurations Templates > Configuration Templates > Select Advanced Settings
.
CSCub31632
Resolved the issue where Cisco TMS failed to import Billing Codes from a text file.
CSCty74386
Resolved the TMS Scheduler issue where adding a phone book entry as the first participant
followed by a dial-out number would lead to the phone book entry replacing all other participant
addresses.
followed by a dial-out number would lead to the phone book entry replacing all other participant
addresses.
CSCud39079
Improved Cisco TMS’ handling of database deadlocks.
Resolved in 14.0
The following issues were found in previous releases and were resolved in 14.0:
Booking
Identifier
Description
CSCua62217
Resolved the issue where an error could appear in the log-web.txt log when adding a non-Cisco
TMS-managed participant (dial-in, dial-out, phone book entry, user) to a One Button To Push
conference.
TMS-managed participant (dial-in, dial-out, phone book entry, user) to a One Button To Push
conference.
CSCty98098
Resolved the issue where confirmation emails were not received when booking a One Button To
Push conference which included at least one non-Cisco TMS-managed participant (dial-in, dial-
out, phone book entry, user).
Push conference which included at least one non-Cisco TMS-managed participant (dial-in, dial-
out, phone book entry, user).
CSCty94156
Resolved the issue where a SIP conference scheduled on an MCU in Cisco TMS did not register
as SIP if H323 was disabled on the MCU.
as SIP if H323 was disabled on the MCU.
This happened because SIP registration was dependent on the H323 MCU prefix setup,
meaning it would fail if H323 was turned off on the MCU.
meaning it would fail if H323 was turned off on the MCU.
CSCtx64185
Resolved the issue where Cisco TMS did not register SIP participants as taking up resources in
stored bookings on an MCU, which made it possible to overbook SIP participants on the MCU in
subsequent bookings.
stored bookings on an MCU, which made it possible to overbook SIP participants on the MCU in
subsequent bookings.
CSCua26100
Resolved the issue where in
Booking > New Conference >
Recurrence Settings the calendar
sometimes did not display in the
Recurrence Settings
pop up window.