Technical information

Polycom CMA System Release Notes
Version 5.3
19
Content
Sharing
SSGSE-4824 4.1.0 The content for scheduled
conferences that are cascaded
over multiple MCUs (MGCs or
RMXs) is not viewable on the
endpoints.
None
Dashboard:
MCU Status
Pod
SSGSE-6949 5.0 Time extensions for scheduled
conferences do not reflect the
port usage into the dashboard.
Extended confs (port usage) is
treated as ad hoc by the CMA
system and are not tracked,
therefore they do not show in the
expected port usage graphs.
None
Database SSGSE-5105 4.1.0 When a Polycom CMA system
experiences an unexpected
disconnection from the external
database it does not
automatically re-establish
connection and some data loss
may be experienced.
A Polycom CMA system will
show a System Alert if the
database connectivity is lost. Log
into the Polycom CMA system UI
and re-start the server to
re-establish full database
connectivity. No workarounds for
potential data loss.
Device
Management
SSGSE-7592 5.0 After a Polycom CMA system
reboot, Polycom HDX endpoints
in dynamic management mode
may not re-register all the
services correctly.
Power cycle the endpoints.
Device
Management
SSGSE-5692 5.0 The status information of network
devices (RMX, MGC, VBP) may
be out-of-synchronization.
None
Dial Rules SSGSE-7591 5.0 When creating a dialing rule, the
routing action may get saved as
“Route" even if the selection is
"Block".
Edit the dialing rule and manually
change the routing action to the
desired value."
Dial Rules SSGSE-4582 4.1.0 If dial prefixes overlap with the
initial digits of endpoints' E.164
alias, the calls using the same
set of preliminary digits may fail /
connect to the incorrect devices.
Plan your dial rules and E.164
rules prior to implementing them,
and ensure they don’t overlap.
Category
Issue #
Found in
Release Description Workaround