Release Notes

Resolved issues
Cisco TelePresence Management Suite Release Notes Software Release Notes (14.4.1) Page 25 of 61
Identifier Description
CSCun79003 Resolved the issue that occurred when adding a TelePresence Conductor running XC 2.3 to
Cisco TMS. The management address stayed blank in Systems > Navigator, and a ticket
stating "The management address on the system is incorrectly configured ..." was displayed.
Phone Books
Identifier Description
CSCun25502 Resolved the issue where phone book entries that appeared in more than one phone book
could appear as duplicated in phone book searches. Duplicate entries should appear only
once in search results.
CSCuj42053 Resolved the issue where adding a new entry to a phone book set on a Polycom endpoint did
not update the phone book on the endpoint with that new entry.
CSCul84164 Reinstated the missing bandwidth options: Auto, Telephone and Max for Manual List phone
book source contacts.
Reporting
Identifier Description
CSCug10144 Reporting > Conferences > Conference Statistics > Calculate By: Utilization has been
removed as it was not possible to calculate this data by utilization, and the generated graph
was always empty.
CSCun25641 Resolved the issue where it was not possible to filter MCU Call Detail Records by Call
Protocol.
Recurrence
Identifier Description
CSCun81304 Resolved the issue where editing a recurrent conference series with recurrence pattern ' First
Day of every month' changed the recurrence pattern to 'First Sunday of every month'.
Cancelling the edit and then saving the conference changed it from a recurrent to a non-
recurrent conference.
CSCun81313 Resolved the issue where deleting the first occurrence of a recurrent series, then editing the
series to disable recurrence, deleted all occurrences of the conference. The instance that was
edited to remove recurrence should have remained as a non-recurrent conference.
CSCue26779 Resolved the issue where Cisco TMS consumed ports after a conference had been moved to
a different MCU. This only occurred for recurrent conferences, if an instance was moved to a
different MCU.
CSCtr53461 Resolved the issue where swapping the bridge for one meeting occurrence in a recurrent
series still showed that bridge as being in the conference in the List Conferences page, when
filtering on the original bridge.
CSCum41801 Resolved the issue where booking a daily recurrent conference using the End by Date option
ended the conference series the day before the date specified. This occurred if the user
booking the conference was in a time zone with a negative UTC offset.
CSCun81618 It is now possible to move an instance past a deleted or previously moved instance of the
same series.