Polycom CMA System Release Notes What’s New in This Release The Polycom CMA scheduling and management system version 5.3 includes the following new features. • Enhanced TANDBERG Endpoint Support • Overbooking Dial-in Participants • Polycom Scheduling Plugin for Microsoft Outlook Installation Changes • Enhanced Polycom RMX Support Each of these features is discussed in more detail in the following sections.
Polycom CMA System Release Notes Version 5.3 a. Dynamic Management and Standard Management are mutually exclusive functionality. b. Scheduling (Dial In Only) and Scheduling (Dial In and Dial Out) are presented as mutually exclusive functionality. c. Standard CMA monitoring does not involve using SNMP. It includes endpoint monitoring (online/offline status) and alerts. d. Command and Control means the Polycom CMA system can send a Reboot command, and the endpoint can receive and act on the command. e.
Polycom CMA System Release Notes Version 5.3 Polycom Global Address Book Access With Polycom CMA system version 5.3, users of the TANDBERG 150, 990, 880, and 770 MXP endpoints can access the Polycom Global Address Book, so they can see the endpoints in the Global Address Book. The timing of the endpoint’s connection with the Global Address Book can affect the success of its connection.
Polycom CMA System Release Notes Version 5.3 Polycom Scheduling Plugin for Microsoft Outlook Installation Changes Several improvements have been made to the installation process for the Polycom Scheduling Plugin for Microsoft Outlook. • The plugin is now suitable for silent installation. • The installation process now includes a wizard. • The installation process no longer requires administrative rights on the client system.
Polycom CMA System Release Notes Version 5.3 Note You cannot at this time set the https option on the Polycom Scheduling Plugin for Microsoft Outlook via a silent installation. Enhanced Installation Wizard To install the Scheduling Plugin for Outlook 1 Ensure that Microsoft Outlook is closed. 2 If this is not your first installation of the Scheduling Plugin for Outlook, go to Start > Control Panel > Add or Remove Programs and remove the previous version of the Scheduling Plugin for Outlook.
Polycom CMA System Release Notes Version 5.3 On the Conf Settings tab: Conf Settings Auto Redial Instructs the Polycom RMX to automatically redial IP and ISDN participants that have been abnormally disconnected from the conference. It is important to note that the Polycom CMA system administrator should manually synchronize these settings in the CMA system conference template to those in its associated RMX profile.
Polycom CMA System Release Notes Version 5.3 Installation and Upgrade Notes Installation of new Polycom CMA systems is managed through Polycom Global Services. For more information, please contact your Polycom representative. Before installing or upgrading a system to this release, carefully review the following notes: • Only Polycom CMA systems running version 5.0 can be upgraded to version 5.3. • If you receive a new Polycom CMA system with version 4.
Polycom CMA System Release Notes Version 5.3 System Requirements The following table describes the requirements for the Polycom CMA system 5.0 web scheduling and system operations client. Product Supported Versions Microsoft Windows Operating System 2003 SP2, XP SP3, or Vista™ SP2 Internet Browser • Microsoft Internet Explorer OR v6.0, 7.0, or 8.0 • Mozilla Firefox OR v3.5 or 3.6 • Apple Safari v3.2 or 4.0 Adobe Flash Player v9.x or 10.0.
Polycom CMA System Release Notes Version 5.3 Product Supported Versions Polycom ViewStation FX/EX/4000 6.0.5 Note Support for ViewStation endpoints is planned to end in the next major release of the Polycom CMA system. Polycom PVX 8.0.2 and higher Polycom QDX 6000a 4.0 Polycom VVX 1500 UC 3.3.0 or higher Network Devices Polycom RMX 1500 7.0.1 and higher Polycom RMX 2000 6.0 and higher Polycom RMX 4000 6.0 and higher Polycom RMX 1000 2.1 and higher Polycom MGC 9.0.1.
Polycom CMA System Release Notes Version 5.3 Product Supported Versions Cisco Gatekeeper 12.4 Microsoft SQL Serverc,d,e,f 2005 SP3, Standard or Enterprise edition, 32 or 64 bit 2008, Standard or Enterprise edition, 32 or 64 bit Clustering supported. Microsoft Active Directoryg 2003 Domain Functional Level w/ Domain Controller Windows Server 2003 SP2; multiple domain controllers 2008 Domain Functional Level w/ Domain Controller Windows Server 2008; single domain controller only a.
Polycom CMA System Release Notes Version 5.3 The Cisco IOS or Avaya CM gatekeeper may require additional configuration to integrate with the Polycom CMA system. See the product documentation for the Cisco IOS or Avaya CM gatekeeper to determine how to configure it as a neighboring gatekeeper. Polycom RMX Platform Integration A system administrator must plan carefully when integrating a Polycom RMX conferencing platform with a Polycom CMA system as both systems manage conference settings and templates.
Polycom CMA System Release Notes Version 5.3 Auto-extend Conference The RMX system has an "ENABLE_AUTO_EXTENSION" flag that, when set, allows conferences running on the RMX system to be automatically extended as long as there are participants connected. The CMA system does not recognize this setting, so the CMA system will end a conference scheduled through it regardless of the value of this flag. Resolved Issues The following table lists the resolved issues in this Polycom CMA system release.
Polycom CMA System Release Notes Version 5.3 Issue # Description SSGSE-8603 Enabling Single Sign-On LDAP configuration may give a Netbios error.
Polycom CMA System Release Notes Version 5.3 Issue # Description SSGSE-8262 SSGSE-7634 SSGE-972 Signing into a Polycom CMA Desktop client fails intermittently when the Automatic Discovery option on the Polycom CMA system is enabled for Single Signon integration in environments with a non-continuous domain namespace. SSGSE-8229 SSGE-1032 The refresh button on the Global Address Book page does not work. SSGSE-8201 Production phones outside a trial group are forced to upgrade their software version.
Polycom CMA System Release Notes Version 5.3 Issue # Description SSGSE-7648 Some Polycom HDX endpoints are being displayed with a device type of Other in the Endpoint Monitoring View and other UI screens. SSGSE-7542 MCU capabilities screen displays a 'Monitoring Level' configuration that only actually applies to endpoints.
Polycom CMA System Release Notes Version 5.3 Issue # Description SSGSE-6830 SSGE-1115 The Polycom CMA system terminates scheduled conferences at the scheduled time regardless of ENABLE_AUTO_EXTENSION setting on the Polycom RMX system. The v5.0 Polycom CMA System Release Notes incorrectly indicate that the Polycom CMA system will take action based on this setting.
Polycom CMA System Release Notes Version 5.3 Category Issue # Found in Release Active Directory SSGSE-7206 Active Directory SSGSE-6876 Description Workaround 5.0 If the Polycom CMA system loses connection to the Active Directory server, Polycom CMA Desktop users who have local credentials cannot login either. None 4.1.4 The integration to Microsoft Active Directory may be performed as "Domain Name\LDAP user" as opposed to "Netbios Name\LDAP user" (for example, 'team3.
Polycom CMA System Release Notes Version 5.3 Category Issue # Found in Release Conference Management SSGSE-7878 Conference Management Description Workaround 5.0 The Polycom CMA system does not send an email alert to the administrator or scheduler if a scheduled conference fails to launch. None SSGSE-7728 5.0 In the Conference Management page, for a conference hosted on a Polycom RMX v 6.0 bridge with multiple ISDN participants, one of the participant details may display “Unknown.
Polycom CMA System Release Notes Version 5.3 Category Issue # Found in Release Content Sharing SSGSE-4824 Dashboard: MCU Status Pod Description Workaround 4.1.0 The content for scheduled conferences that are cascaded over multiple MCUs (MGCs or RMXs) is not viewable on the endpoints. None SSGSE-6949 5.0 Time extensions for scheduled conferences do not reflect the port usage into the dashboard.
Polycom CMA System Release Notes Version 5.3 Category Issue # Found in Release Directory SSGSE-6077 External database Description Workaround 5.0 If dynamically managed endpoints search for rooms that were created locally on the Polycom CMA system, the search results will not return anything when using cn or displayname. Room searches on the Active Directory server will work. Search for locally created rooms by SN and SAMAccountName. SSGSE-9174 SSGE-1130 5.
Polycom CMA System Release Notes Version 5.3 Category Issue # Found in Release Gatekeeper/ Global Address Book SSGSE-6933 Gatekeeper/ Scheduling Description Workaround 5.0 Deleting a fully registered non-dynamically managed endpoint from a Polycom CMA system and re-adding it manually (via Add command) does not register the endpoint with the Polycom CMA system gatekeeper and Global Address Book. After adding the endpoint to the system manually, reboot the endpoint. SSGSE-6881 5.
Polycom CMA System Release Notes Version 5.3 Category Issue # Found in Release Interop SSGSE-7416 InteropTANDBERG Interop- Description Workaround 5.0 The administrator may receive notifications for updating third-party components once logged into the UI. The CMA system will not allow these updates. None SSGSE-9031 5.3 The CMA system Get Serial Numbers function lists all non-T150 TANDBERG endpoints, including C-Series endpoints. None SSGSE-7313 5.0 Using Polycom CMA Desktop client v5.
Polycom CMA System Release Notes Version 5.3 Category Issue # Found in Release InteropCMAD SSGSE-4660 InteropCMAD/ Device Management Description Workaround 4.1.0 When using Polycom CMA Desktop, if a user selects the group "All" in the Directory and enters an underscore ("_") in the search string, the Polycom CMA system will return the list of local users created on the server. None SSGSE-6891 5.
Polycom CMA System Release Notes Version 5.3 Category Issue # Found in Release Interop-MCU SSGSE-7187 Interop-MGC Description Workaround 5.0 In some cases a conference cannot be copied after it has been terminated. This happens because when the conference terminates, the bridge sends notifications about participants being removed from the conference before the notification about the terminated conference itself.
Polycom CMA System Release Notes Version 5.3 Category Issue # Found in Release Description Workaround Interop-RMX SSGSE-8512 VNGFE-2972 4.1.4 RMX 2000 guest participants who are scheduled via a CMA system have H.323 IDs not E.164 aliases. None Interop-RMX SSGSE-8464 5.0 The Polycom CMA system does not warn the user that scheduling will fail when adding an RMX system that is configured for 'Fixed Resource Capacity.' None Interop-RMX SSGSE-8340 5.
Polycom CMA System Release Notes Version 5.3 Category Issue # Found in Release Interop-RMX SSGSE-6803 Interop-RMX Description Workaround 5.0 The Polycom CMA system is not aware of the value for the "ENABLE_AUTO_EXTENSION" flag on the Polycom RMX system. When the conference scheduled end time comes, the CMA system will send a Conference Terminate event to an RMX system to end the conference, regardless of the value of this flag.
Polycom CMA System Release Notes Version 5.3 Category Issue # Found in Release InteropTANDBERG SSGSE-7289 InteropTANDBERG Description Workaround 5.0 The TANDBERG 6000 E is unable to send H.239 content in H323 calls when it is registered to the Polycom CMA system. The endpoint also stops transmitting video when this occurs. None SSGSE-8323 SSGSE-8439 5.
Polycom CMA System Release Notes Version 5.3 Category Issue # Found in Release Interop-VBP SSGSE-5063 Interop-View Description Workaround 4.1.0 The Polycom CMA system's IP Call Detail Record for any inbound call traversing a Polycom VBP device shows a 'Source' System Name that is the earliest gatekeeper registrant to the VBP - which may not be the System Name of the endpoint that actually placed the call. None SSGSE-7514 5.
Polycom CMA System Release Notes Version 5.3 Category Issue # Found in Release Localization SSGSE-7596 Logging Description Workaround 5.0 If the font size is changed for a language other than English, the change does not take effect immediately. Log out, close the browser, and start a new browser session. SSGSE-8626 5.0 String or binary data in the EXXX_LOG is truncated. None Logging SSGSE-6646 5.0 jserver logs are retained for only 12 hours. None Messages SSGSE-6213 5.
Polycom CMA System Release Notes Version 5.3 Category Issue # Found in Release Polycom Scheduling Plugin for IBM Lotus Notes SSGSE-6500 Polycom Scheduling Plugin for Microsoft Outlook SSGSE-6531 Polycom Scheduling Plugin for Microsoft Outlook SSGSE-6458 5.
Polycom CMA System Release Notes Version 5.3 Category Issue # Found in Release Polycom Scheduling Plugin for Microsoft Outlook SSGSE-5202 Provisioning Description Workaround 4.1.0 The Polycom Scheduling Plugin for Microsoft Outlook is available in the Download list even if there is no license for the plugin. However, the plugin will not connect to the the Polycom CMA system without a license and cannot be used. None SSGSE-8962 SSGE-1143 5.
Polycom CMA System Release Notes Version 5.3 Category Redundancy Issue # Found in Release SSGSE-3709 4.0.0 Description Workaround Redundancy may not work appropriately after multiple power failures. In redundant mode with the secondary server acting as the active server, a hard power failure of the secondary server may cause redundancy to fail, and failover to the primary server may not occur correctly.
Polycom CMA System Release Notes Version 5.3 Category Issue # Found in Release Reporting SSGSE-6486 Reporting Description Workaround 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 SSGSE-6250 5.0.0 When the Endpoint Usage report is exported in Microsoft Excel format, it includes only the first 1000 entries.
Polycom CMA System Release Notes Version 5.3 Category Issue # Found in Release Scheduling SSGSE-6669 Scheduling Scheduling/ Cascading Description Workaround 5.0 When more than 15 conferences are scheduled to launch at exactly the same time, additional conferences (16th and more) can take a few minutes to launch, thereby delaying the start of the conference(s). None SSGSE-4831 4.1.0 In scheduled conferences that cascade, ISDN calls will not connect if the conference template has H.239 enabled.
Polycom CMA System Release Notes Version 5.3 Category Issue # Found in Release System SSGSE-8996 System Access SSGSE-7597 Description Workaround 5.3 Extending the duration of a conference by 5 minutes only adds 2 minutes to the conference. None 5.0 A user with operator permissions cannot be deleted from the Polycom CMA system if the user has a favorites list. An administrator must: 1. Log into the system as an administrator and edit the operator’s account to change his/her password. 2.
Polycom CMA System Release Notes Version 5.3 Category Issue # Found in Release UI SSGSE-8351 UI Description Workaround 5.0 The Alias filter on the Endpoint > Monitor View page only searches E.164 aliases and does not search H.323 IDs. None SSGSE-7977 5.0 If an ISDN line is down, the CMA system does not send an alert even though it does shows the line is down. None UI SSGSE-7921 5.
Polycom CMA System Release Notes Version 5.3 Category Issue # Found in Release UI SSGSE-7594 UI Description Workaround 5.0 Cause codes may not appear clearly in the View Participant Details pop-up. Go to View Details > Call Info > Sites to view the cause codes for the endpoints. SSGSE-7552 5.0 MGC and GW/MCU device's site does not update when the device's subnet is added to a site. Delete the GW/MCU and MGC. After re-registration the UI will display the site correctly. UI SSGSE-7538 5.
Polycom CMA System Release Notes Version 5.3 Category Issue # Found in Release 5.0 Description Workaround On the Network Device > Monitor View page, the Gatekeeper registration and Device Managed status may be incorrect for an RMX system. Check the Device Status of the RMX for the correct status. If there is an IP address conflict when adding a Polycom VBP device (i.e.
Polycom CMA System Release Notes Version 5.3 Category Issue # Found in Release UI SSGSE-6721 UI Description Workaround 5.0 In the Network Device > Monitor View, the state "Serbia and Montenegro" is displayed, but that state no longer exist. Serbia and Montenegro are now two separate states with two different international dialing prefixes. None SSGSE-6545 5.
Polycom CMA System Release Notes Version 5.3 Category Issue # Found in Release UI SSGSE-6248 UI/ Accessibility Description Workaround 5.0 When software revisions are applied to devices through a Polycom VBP connection, the device will update correctly but the device information will still report the previous software version. None SSGSE-6109 5.0 When tabbing through the internal pages, the Views and Actions labels can be accessed, but not individual views or actions.
Polycom CMA System Release Notes Version 5.3 Category Issue # Found in Release UI/ Site Topology SSGSE-6332 Upgrade Description Workaround 5.0 The Polycom CMA system does not save Active Directory users’ Site Topology preferences. None SSGSE-9088 SSGE-1128 5.0 Multiple bridges lost gatekeeper registration with CMA system. PN_Log.txt stops reporting info after upgrade from 4.1.4 to 5.0. None Upgrade SSGSE-8309 5.0 After upgrading to CMA 5.
Polycom CMA System Release Notes Version 5.3 The following table lists some of the known limitations of the Polycom CMA system when interoperating with partner gatekeepers and endpoints. Issue # Description Comment CSC-6 Cisco/Busy signal is heard on Cisco phones when VSX or HDX disconnects. An endpoint issue related to issue VIDEO-57092, which is marked Will Not Fix.
Polycom CMA System Release Notes Version 5.3 Copyright Information © 2010 Polycom, Inc. All rights reserved. No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of Polycom, Inc. Polycom, Inc. retains title to, and ownership of, all proprietary rights with respect to the software contained within its products.
Polycom CMA System Release Notes Version 5.3 Appendix A: SQL Server Configuration to Prevent Random Database Disconnection Polycom CMA and ReadiManager SE200 systems connected to an external database sometimes experience problems with random disconnection from the Microsoft SQL server. A subset of database connections from a Polycom CMA or ReadiManager SE200 system may drop, and a drop can remain unnoticed until a user performs an operation that attempts to use the connection.
Polycom CMA System Release Notes Version 5.3 3 Select the relevant instance. For default, select Protocols for MSSQLSERVER. 4 Double click TCP/IP. 5 Select the field that corresponds to the KeepAlive setting. 6 Type in the number of milliseconds the Microsoft SQL server should wait before sending subsequent KeepAlive messages. NOTE: The tested value is 3600000 (once every hour). 7 Restart Microsoft SQL server.
Polycom CMA System Release Notes Version 5.3 Appendix B: Polycom CMA System Operating System Updates The following tables shows the operating system patches applied to the Polycom CMA system in this release.
Polycom CMA System Release Notes Version 5.
Polycom CMA System Release Notes Version 5.3 Appendix C: Polycom CMA System End-User License Agreement Please read the Polycom End User License Agreement below and click on the Accept button below to continue. END USER LICENSE AGREEMENT FOR POLYCOM® SOFTWARE IMPORTANT-READ CAREFULLY BEFORE USING THE SOFTWARE PRODUCT: This End-User License Agreement ("Agreement") is a legal agreement between you (and/or any company you represent) and either Polycom (Netherlands) B.V.
Polycom CMA System Release Notes Version 5.3 2. OTHER RIGHTS AND LIMITATIONS. 2.1 Limitations on Reverse Engineering, Decompilation, and Disassembly. You may not reverse engineer, decompile, modify or disassemble the SOFTWARE PRODUCT or otherwise reduce the SOFTWARE PRODUCT to human-perceivable form in whole or in part, except and only to the extent that such activity is expressly permitted by applicable law notwithstanding this limitation.
Polycom CMA System Release Notes Version 5.3 2.7 Confidentiality. The SOFTWARE PRODUCT contains valuable proprietary information and trade secrets of POLYCOM and its suppliers that remains the property of POLYCOM. You shall protect the confidentiality of, and avoid disclosure and unauthorized use of, the SOFTWARE PRODUCT. 2.8 Dual-Media Software. You may receive the SOFTWARE PRODUCT in more than one medium.
Polycom CMA System Release Notes Version 5.3 5. UPGRADES. If the SOFTWARE PRODUCT is labeled as an upgrade or update, you must be properly licensed to use the software identified by POLYCOM as being eligible for the upgrade or update in order to use the SOFTWARE PRODUCT. A SOFTWARE PRODUCT labeled as an upgrade or update replaces and/or supplements the software that formed the basis for your eligibility for the upgrade or update.
Polycom CMA System Release Notes Version 5.3 DISCLAIMED. POLYCOM NEITHER ASSUMES NOR AUTHORIZES ANY OTHER PERSON TO ASSUME FOR IT ANY OTHER LIABILITY IN CONNECTION WITH THE SALE, INSTALLATION, MAINTENANCE OR USE OF THE SOFTWARE PRODUCT. NO ADVICE OR INFORMATION, WHETHER ORAL OR WRITTEN, OBTAINED BY YOU FROM POLYCOM OR THROUGH OR FROM THE SOFTWARE PRODUCT SHALL CREATE ANY WARRANTY NOT EXPRESSLY STATED IN THIS AGREEMENT.
Polycom CMA System Release Notes Version 5.3 9. DISCLAIMER. Some countries, states, or provinces do not allow the exclusion or limitation of implied warranties or the limitation of incidental or consequential damages for certain products supplied to consumers, or the limitation of liability for personal injury, so the above limitations and exclusions may be limited in their application to you.
Polycom CMA System Release Notes Version 5.3 Consistent with 48 C.F.R. §12.212 or 48 C.F.R. §§227.7202-1 through 227.7202-4, as applicable, the Commercial Computer Software and Commercial Computer Software Documentation are licensed to United States Government end users (1) only as Commercial Items and (2) with only those rights as are granted to all other users pursuant to the terms of this Agreement. 12. Third Party Software.
Polycom CMA System Release Notes Version 5.3 This SOFTWARE PRODUCT includes Berkeley DB Java Edition software. Copyright (c) 2002, 2008 Oracle. All rights reserved. Oracle is a third party beneficiary of this Agreement. *** ORACLE AMERICA, INC. LICENSE TERMS Java Platform, Standard Edition Embedded, version 6.0 1 Java Technology Restrictions.
Polycom CMA System Release Notes Version 5.3 These license terms are an agreement between you and Polycom. Please read them. They apply to the software included on this server. The software also includes any separate media on which you received the software. The software on this device includes software licensed from Microsoft Corporation or its affiliate.
Polycom CMA System Release Notes Version 5.3 b. Client Access Licenses (“CALs”). These license terms include 5 CALs unless a higher number of CALs is indicated on the Certificate of Authenticity for the server software. Please select the number of Windows User CALs and Windows Device CALs (not to exceed a combined total of 5 or such higher number) and write them in the spaces provided below. No CALs are valid until those spaces are completed. You may not change them once completed.
Polycom CMA System Release Notes Version 5.3 You may reassign a Windows CAL from one device to another device, or from one User to another User, if the reassignment is made (A) permanently away from the one device or User, or (B) temporarily to accommodate the use of the Windows CAL by a loaner device while a permanent device is out of service, or the use of the Window CAL by a temporary worker while a regular employee is absent.
Polycom CMA System Release Notes Version 5.3 Additional CAL Requirements. (i) Single Licensee. Only you can use Windows CALs, TS CALs, and any future Premium Services CALs with server software. (ii) Version Matching. Each required CAL must be version Windows Server 2003 or a later version. (iii) Administration. Up to 2 Users or devices may access or use the server software at the same time, without acquiring any CALs, solely for administration of the server software.
Polycom CMA System Release Notes Version 5.3 a. Consent for Internet-Based Services. The software features described below connect to Microsoft or service provider computer systems over the Internet. In some cases, you will not receive a separate notice when they connect. You may switch off these features or not use them. For more information about these features, visit http://www.microsoft.com/windowsxp/downloads/updates/sp2/docs/p rivacy.mspx.
Polycom CMA System Release Notes Version 5.3 (1) you must disclose all the information necessary for replication of the tests; (2) you must disclose the date(s) when you did the benchmark tests and version information for all Microsoft software products tested; (3) your benchmark testing was performed in accordance with the product documentation and/or Microsoft's support Web sites, and uses the latest updates, patches, and fixes available for the .
Polycom CMA System Release Notes Version 5.3 • APPROVED ADDITIONAL TEXT IF EMBEDDED SYSTEM IS AUTHORIZED TO BE LEASED UNDER THE OEM LICENSE AGREEMENT: LEASED HARDWARE.
Polycom CMA System Release Notes Version 5.3 11. LIABILITY LIMITATIONS. You can recover from Microsoft and its affiliates only direct damages up to two hundred fifty U.S. Dollars (U.S. $250.00), or equivalent in local currency. You cannot recover any other damages, including consequential, lost profits, special, indirect or incidental damages.
Polycom CMA System Release Notes Version 5.
