Technical information

Polycom CMA System Release Notes
Version 5.3
33
Reporting SSGSE-6486 5.0 If a Polycom CMA Desktop client
calls a Polycom VVX system with
an IP address, H.323/E.164
alias, and H.323 ID, the
Endpoint Usage Report's
outbound graph shows three
different destinations for the
single VVX call.
None
Reporting SSGSE-6250 5.0.0 When the Endpoint Usage
report is exported in Microsoft
Excel format, it includes only the
first 1000 entries.
Export the file in .
csv
format to
see all entries.
Reporting SSGSE-5759 5.0 Conferences that fail to launch
are still displayed in the
Conference Detail Report with
"Total Scheduled Participants"
and "Total Actual Participants"
blank.
None
Reporting SSGSE-3309 4.0.0 Disconnecting a participant from
a conference and then
reconnecting them results in an
extra CDR record.
None
Room SSGSE-7428 5.0 Users cannot search for rooms
created locally on the CMA
system by H.350 common name,
given name, or display name.
None
Room SSGSE-7422 5.0 A virtual room created on the
CMA system and assigned to a
group can log into the system.
None
Scheduling SSGSE-7553 5.0 Guests or other conference
participants with both an IP
address and E.164 alias land on
the MCU with only the IP
address.
None
Scheduling SSGSE-7550 5.0 If two Polycom RMX systems are
cascaded and one of them is in
secure mode, scheduled
conferences will fail.
None
Scheduling SSGSE-7281 5.0 If a scheduled conference is set
for an MCU that is not currently
registered to the Polycom CMA
system gatekeeper, the
conference will not launch.
None
Category
Issue #
Found in
Release Description Workaround