Release Notes Polycom Converged Management Application (CMA ) System Version 4.1.2

Release Notes Polycom Converged Management Application (CMA ) System Version 4.1.2 Polycom announces the general release of its Polycom Converged Management Application (CMA ) System Version 4.1.2 (build 4.01.02) scheduling and management system. This document provides the latest information about this release. Topics Introducing the Polycom CMA System 4.1.2 Release... 2 What s New in the CMA 4.1.2 Release... 2 System Requirements... 3 System Parameters... 3 Installation and Upgrade Notes... 4 Interoperability... 4 Polycom Device Version Requirements... 4 Polycom CMA System Localization Practices... 5 Microsoft Windows Vista... 5 Strategic Global Partners... 5 ipower Support... 5 RMX Integration... 5 Resolved Issues... 6 Known Issues... 8 Where to Get the Latest Product Information... 12 Appendix A: Polycom CMA System Operating System... 13 Appendix B: SQL Server Configuration to Prevent Random Disconnection... 14 Copyright Information 2009 Polycom, Inc. All rights reserved. 3725-77600-001D3 (July 2009) Polycom, Inc. 1765 West 121st Avenue Westminster, CO 80234-2301 U.S.A. Trademark/ Patent Information Polycom, the Polycom Triangles logo, and the names and marks associated with Polycom s products are trademarks and/or service marks of Polycom, Inc., and are registered and/or common-law marks in the United States and various other countries. All other trademarks are the property of their respective owners. The accompanying product is protected by one or more U.S. and foreign patents and/or pending patent applications held by Polycom, Inc. 1

Introducing the Polycom CMA System 4.1.2 Release Polycom is pleased to announce the general release of its Polycom Converged Management Application (CMA ) system version 4.1.2 scheduling and management system. What s New in the CMA 4.1.2 Release The Polycom CMA system version 4.1.2 includes the following new features. For more information on these new features, see the Polycom CMA System Operations Guide. Pre-staged trusted machine account The Polycom CMA system now requires a pre-staged, trusted machine account, which eliminates the need for an Active Directory (AD) administrator to enter credentials at the time Integrated Windows Authentication is enabled. Removed database reconnection code that reconnected the Polycom CMA system to the database if the connection was dropped. Because of this change, Polycom requires a change to the Keep Alive settings on the Microsoft SQL Server to pace the heartbeats better. For more information, please see Appendix B: SQL Server Configuration to Prevent Random Disconnection on page 14. Auto-discovery The Polycom CMA system now has an Auto-discovery feature that allows it to discover the closest network domain controller and/or AD server. The network DNS server must have a DNS SRV record for the domain controller and/or the AD server for this Auto-discovery feature to work. If your AD does not publish the AD server and domain controller s hostname and IP address to the network DNS, you must edit the file to include them. LDAP query enhancements The Polycom CMA system has several LDAP query enhancements and options that can lessen the number of LDAP queries and improve LDAP query performance. They include: Provisionable auto-complete (ON OFF) search function Searching only indexed fields and a smaller set of attributes Limited use of wildcard searching Eliminated searching of all groups Eliminated the need to bind to a specific LDAP and AD server (server-less bind) Created secure connection between the AD server and the Polycom CMA system The Polycom CMA system s access to the AD Global Catalog can now be secured using LDAP-S via outbound TCP/UDP port 636 OR SSL via outbound TCP/UDP port 3269. To implement the secure connection, you must open the appropriate outbound port. For more information on the Polycom CMA system port usage, see the Polycom CMA System Operations Guide. Added Title, Department, City, and Phone Number fields to the Add/Edit Users dialog box and added Title, Department, and City to the Add Participants dialog box to distinguish between users with the same name. 2

System Requirements The Polycom CMA system web scheduling and system operations client requirements Microsoft Windows 2000, Windows 2003, Windows XP, or Windows Vista Adobe Flash Player 9.0 or 10.0 Microsoft Internet Explorer 6.0+ or 7.0, Mozilla FireFox 2.0x or 3.0x, or Apple Safari 3.x Microsoft Outlook 2000 SR1, Outlook 2003 with SP2 or SP3, or Outlook 2007 (for the Polycom Scheduling Plugin for Microsoft Outlook only) on Microsoft Windows XP or Windows Vista IBM Lotus Notes 7.x or 8.x (for the Polycom Scheduling Plugin for IBM Lotus Notes only) The Polycom CMA system System Parameters External database (optional) Microsoft SQL Server 2005 Standard or Enterprise edition (32 and 64 bit) with SP2 or SP3 For installations with an external database, the Polycom CMA system is only certified with the Microsoft SQL Server set to US-English Collation (SQL_Latin1_General_CP1_CI_AS). Polycom strongly recommends that the Polycom CMA system databases have their own database instance and not be part of a shared database instance. Enterprise directory (required for Polycom CMA 5000 systems) Microsoft Active Directory with Global Catalogs enabled and universal groups defined Polycom CMA Desktop system requirements See the Polycom CMA Desktop System Release Notes for the minimum configuration required on the client computer. The Polycom CMA system operates within the following system parameters: Directory entries Users no limit, but if the system has more than 10,000 user entries, it could experience performance issues Groups 500 total groups (local and enterprise groups combined) Devices limited to maximum number of device licenses GAB entries limited to maximum number of device licenses Room entries no limit, but if the system has more than 500 room entries, it could experience user interface performance issues. Site entries limited to 60 sites Site links based on limit of 60 sites 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 upgrading a Polycom CMA system to this release, carefully review the following notes: Only Polycom CMA systems running version 4.0.x or greater can be upgraded to version 4.1.2. The Polycom CMA system software version 4.1.2 includes any patches that may have been applied to the version 4.0.x or greater software. Do not apply patches for previous software versions to this release. After the upgrade from any 4.0.x system, you must enter new information the DNS Domain name for the network in which the domain name server and Polycom CMA system server reside on the Network Settings page. This is the DNS domain name suffix, for example polycom.com, not the fully qualified path of <hostname>.polycom.com. After the upgrade from any 4.0.x system, to enable Windows authentication on the Polycom CMA system an Active Directory administrator must pre-stage a computer account for the Polycom CMA system The computer account is required to create a trusted connection so the Polycom CMA system can perform trusted passthrough authentication. For more information, see the Polycom CMA System Upgrade Guide or Operations Guide. After the upgrade from any 4.0.x system, the Include all the Active Directory users in the Global Address Book feature is On by default. Turn it Off if you have legacy endpoints that cannot handle the larger address book size. After the upgrade from any 4.0.x system, the CMA Access via default profile allowed feature is Off by default. To allow all enterprise users default access to the system as Schedulers, turn it On. After the upgrade from any 4.0.x system, if you wish to make use of cascading entry queues that were previously defined on your Polycom MCUs, you ll need to edit each of the MCUs and click Refresh Device. The refresh will update the information on all panes of the Edit Device dialog box. Because this refresh updates the information for all device fields, you may need to re-edit the device fields to return them to the previous settings. Interoperability Polycom Device Version Requirements The Polycom CMA system can interoperate with the following Polycom product and versions. Polycom V-Series v8.7.1 or higher Polycom PVX v8.0.2 or higher Polycom HDX systems v2.0.3.1 or higher Polycom RMX 2000 v 3.0.0.94 or higher Polycom MGC v8.0.2 or higher Polycom VBP 5300 or 6400 E/S/T Polycom ViewStation SP/MP/512/H.323 v7.5.4 Polycom ViewStation FX/EX/4000 v6.0.5 Polycom CMA Desktop v4.1.0 (shipped version) Polycom DMA 7000 v1.0 or higher Polycom RSS2000 v3.0.2 or higher Polycom QDX 6000 endpoints and Polycom DMA systems are supported only as H.323 devices. 4

While the Polycom CMA system can interoperate with the Polycom products and versions listed above, in a dynamic management environment it supports the automatic provisioning, automatic softupdate, and presence features only with Polycom CMA Desktop systems and Polycom HDX systems v2.5.0 or higher. Polycom CMA System Localization Practices The Polycom CMA system and its documentation is localized according to the following practices: For major releases, the Polycom CMA system interface and the scheduler documentation is localized into French, German, Internation Spanish, Simplified Chinese, Japanese, and Korean. For minor releases, the Polycom CMA system interface and scheduler documentation may be localized into French, German, Internation Spanish, Simplified Chinese, Japanese, and Korean. For maintenance releases, the Polycom CMA system interface and scheduler documentation are not localized. System administration documentation is not localized. Microsoft Windows Vista The Polycom CMA system and Polycom CMA Desktop are now supported on the Windows Vista platform with NTLM version 2 enabled. However, the current release of Polycom HDX systems support only NTLM version 1. If you have a Polycom HDX system operating in dynamic management mode, you must allow NTLM version 1 on the Domain Controller via the Domain Security Settings. Strategic Global Partners Polycom partners with the leading platform providers to ensure co-development and interoperability in many environments and deliver a high quality collaborative experience. For that reason, the Polycom CMA system has been qualified to neighbor with the Cisco IOS Software Gatekeeper v12.3 and 12.4 and the Avaya Communications Manager 5.0 SP1 Gatekeeper. The Polycom CMA system can route H.323 calls to neighboring regions managed by the Cisco IOS or Avaya CM gatekeeper. To enable call routing to these neighboring gatekeepers, you must create a Polycom CMA system region and dialing rule. (For more information on regions and dialing rules, see the Polycom CMA System Operations Guide.) Then, if the Polycom CMA system is unable to resolve a dialed address for a call, from its list of directly registered endpoints, the system invokes the appropriate dial rule to identify the neighboring gatekeeper to which the call should be forwarded. 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. There are some interoperability limitations for the Polycom CMA system interaction with these neighboring gatekeepers. See Known Issues on page 8 for more information about these limitations. ipower Support The Polycom CMA system does not support ipower devices. RMX Integration A system administrator must plan carefully when integrating a Polycom RMX conferencing platform with a Polycom CMA system as both systems manipulate conference settings and templates. Refer to the Polycom CMA System Operations Guide for more information on creating new conference 5

templates. Refer to the Polycom RMX Administrator s Guide for more information on creating RMX profiles. The Polycom CMA system administrator must manually synchronize the settings in the conference template and its associated RMX profile. If you re using a Polycom CMA system, do all scheduling and monitoring through it to avoid resource conflicts. While the MCU may have on-board scheduling capabilities, scheduling conflicts can occur when both the Polycom CMA system and MCU are used simultaneously to control the same MCU. Resolved Issues The following table lists the resolved issues in this Polycom CMA system release. # Issue SSGSE-5181 SSGSE-5115 SSGSE-5101 SSGSE-5100 SSGSE-5082 SSGSE-5060 SSGSE-5050 SSGSE-5037 SSGSE-5029 SSGSE-5011 SSGSE-5010 SSGSE-4904 SSGSE-4902 SSGSE-4897 SSGSE-4894 SSGSE-4890 SSGSE-4864 SSGSE-4781 SSGSE-4658 SSGSE-4624 SSGSE-4528 SSGSE-4130 Creating a group with a space as its name "erases" the Groups screen which does not recover after rebooting the system. Lotus Notes: Always get "Can't start Flex" error in the Calendar view before scheduling a meeting. The group is still displayed in the endpoint directory when the Directory Viewable of this group is set to be No on the Polycom CMA system. The members of Enterprise Group still can be viewed on endpoint directory though this Enterprise Group is not directory viewable on Polycom CMA system. Cannot add participants to conferences scheduled using the Scheduler Plugins for IBM Lotus Notes or Microsoft Outlook. Active Directory users belonging to groups that are imported as 'enterprise groups' into the Polycom CMA system and assigned a provisioning profile, still get the default profile. Apache Web server crashes; reboot needed to restore service. Customer upgraded to 4. 1.0 and can no longer schedule LifeSize endpoints. Changing domain controller from auto to specify requires password change. Device status shows device online when it is not. The Polycom CMA system Call Status is not reported correctly. It shows the call is active when it is not. Polycom CMA system is unable to integrate with LDAP. Polycom CMA system showing Apache & MSSQL disable on Services after reboot the Polycom CMA system. After upgrade to v4.1.0, no longer able to edit or delete reservations created prior to upgrade because the Edit & Delete buttons in the UI are not there for those reservations. Unexplained E164 numbers are displayed for endpoints in the Admin view. Customer cannot get Polycom CMA Desktop system 4.1.0 to login to Polycom CMA system with a local account. Legacy Polycom HDX system soft updates failing for security customer. When Display Name in Global Directory option is unchecked on the endpoint, the Polycom CMA system will ignore the option and display name in directory anyway. Upgrade to 4.1 failed because of a lack of domain admin rights Problems scheduling meet me recurring conferences on SE200 Security Scan Issue: Directory Listing CMA Address book, on HDX 2.0.3 and VSX 9.0.1 if display name in global directory is not checked, endpoint does not register to GAB - (note - test on all 2.0.3 and up versions of HDX *Security* SSL Server Supports Weak Encryption Vulnerability 6

# Issue SSGSE-4129 SSGSE-3805 SSGE-498 SSGE-493 SSGE-452 SSGE-489 SSGE-508 SSGE-405 *Security* SSL Server has SSL V.2 enabled vulnerability Enhancement request: Log when users sign into the system. The Polycom CMA system is showing the Apache and MS SQL services as disabled after rebooting the system. After upgrading to Polycom CMA system version 4.1.0, users are not able to delete conference reservations created prior to the upgrade. Polycom CMA system version 4.1.0 upgrade failed due to lack of domain administrator privileges. Can t bind to Active Directory. Returning error The server requires binds to turn on integrity checking if SSL\TLS are not already active on the connection. The following table lists the resolved issues in the version 4.1.0 Polycom CMA system release. # Issue SSGSE-3728 SSGSE-3627 SSGSE-3606 SSGSE-3580 SSGSE-3553 SSGSE-3501 SSGE-390 SSGE-385 SSGE-380 SSGE-373 SSGE-367 SSGE-362 SSGE-354 SSGE-351 SSGE-341/ SSGE-357 When there are 60 or more sites, the Generate Multi-site Links function does not work. Significant network latency between the Polycom CMA system and the endpoints may cause the endpoints to go on- and off-line frequently. Automatic Provision: Deleting a profile that belongs to a group 1) Gives no warning about deleting a profile with which users are associated and 2) Does not apply the default profile to the users associated with the profile 3) May result in users not being able to place calls. Scheduled gateway conferences do not show up on the conference summary report Users can still login even if the database connection is lost. Administrative users can assume ownership of any conference and then the original owner cannot see/access it. When importing enterprise groups, the selected group never shows up in the list. When attempting to re-add the group, it no longer shows in the list. In System Setup --> Server Settings --> Custom Logo, the Upload button for Current Logo works properly but the Upload button for CMA Desktop Logo does not respond. On Polycom HDX systems version 2.0.3 and VSX systems version 9.0.1, if a display name in the global directory is not checked, the endpoint does not register to the Global Address Book. Cannot send email to conference participants, the error is '@ 0 @ is not a valid email address'. ISDN guest participants who are scheduled for a Polycom RMX conference are added to the conference at the overall conference speed and not the speed designated for the participant. Cannot successfully start point-to-point calls on a Polycom HDX system when it is in Security Mode, even though management functions work properly. Conferences scheduled using a Polycom CMA system conference template that has H.264 enabled do not launch on MGC. Able to schedule conferences through Outlook Plug-in and the conference starts but the meeting does not show up on the Outlook Calendar. Polycom CMA system device management shows "IP Address Conflict" instead of "Incorrect Password" when wrong password is entered on a registered device. 7

Known Issues The following table lists the known issues in this Polycom CMA system release. # Issue Workaround VNGR-9878 SSGSE-5150 SSGSE-5120 SSGSE-5119 SSGSE-5117 SSGSE-5111 SSGSE-5057 SSGSE-5030 SSGSE-5000 SSGSE-4914 SSGSE-4834 SSGSE-4829 SSGSE-4777 In some situations, server-managed softupdates of VSX devices fails usually due to upgrade and downgrade key and option key issues. Cannot add a Polycom RMX 2000 v4.0 system through the Polycom CMA system interface because of a malformed XML string coming from the Polycom RMX 2000. The Polycom RMX 2000 can register with the gatekeeper. In a redundant Polycom CMA 5000 system, when replying to RAS messages the system doesn't use the virtual IP for the V²IU to handle them. Polycom CMA system does not push the GAB to Tandberg endpoints. Dial In & In Person participants in scheduled conference are not displayed correctly Lotus Notes: Adding users to conference can create duplicate or missing entries Polycom CMA system remote video feed does not work consistently. When endpoints automatically register to the CMA they cannot be managed. CMA should not continue to try and request an endpoint softupdate to a version that has already been requested and rejected. During conference scheduling, operator not able to add a dial in guest if the selected guest is H.320 (ISDN). CMA needs to extend the timeout for waiting on HDX to switch to softupdate mode Not all of the Polycom CMA Desktop and HDX system services up and running after a Polycom CMA system upgrade. Because the endpoints communicate with the Polycom CMA system based on their polling cycle, if the Polycom CMA system is rebooted, there may be a period of time when the endpoint is not registered for presence or directory services. When the RMX is rebooted or restarted, the Polycom CMA system and RMX sometimes don t re-establish communications correctly. After the RMX is restarted or rebooted, the Polycom CMA system will sometimes continue to show the RMX as off-line when in fact it is online. Polycom HDX systems v 2.5.0 are not displaying contacts in the Contacts list when it displays that it has successfully added a contact. Contact Polycom Global Services Via the RMX 2000 administrative interface, select the Default EQ, view its Properties, and click OK. Wait for the endpoint to poll the server or reboot the endpoint. Reboot the Polycom CMA system. 8

# Issue Workaround SSGSE-4630 SSGSE-4587 SSGSE-4371 SSGSE-3720 SSGSE-3709 SSGSE-3653 SSGSE-3638 SSGSE-3623 SSGSE-3612 SSGSE-3588 SSGSE-3572 SSGSE-3533 SSGSE-3521 SSGSE-3481 SSGSE-3456 SSGSE-3447 SSGSE-3386 Cannot dial dynamically-managed endpoint by E.164 from endpoint on gatekeeper. When using the recovery DVD, "ghosting" can succeed or fail and it looks the same either way (exits without any message). RMX UI port usage is different with CMA's reserved video ports. Users should not be able to add the same guests twice to the guest book or to a scheduled conference. 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. Endpoints in ad hoc calls can be added to a schedule now conference without warning. Sometimes in larger conferences, participant s names appear outside the UI pane. Point-to-point ad hoc calls cannot be terminated when in direct mode. The system cannot be upgraded while in HTTPS mode if using Mozilla Firefox. Scheduling failure message states Insufficient MCU Resources when the problem is really Insufficient Bandwidth If network is lost during set up of the redundant server, the virtual IP configuration will be incorrect. Upgrades can cause devices to appear twice, one without an address During a system upgrade, the redirect to the upgrade process screen doesn t occur. Lecture mode chairperson information is not passed to the MGC Sometimes when an RMX goes down, the Polycom CMA system does not see it Some ISDN endpoints area codes are not showing on the UI when in point-to-point ad hoc calls. A Polycom CMA Desktop added to an ongoing conference shows as ISDN 1. Disable simplified dial in. 2. Change simplified prefix from 9 to something else (e.g. 98) that no other end points alias on the neighbored GK begins with this prefix. 3. Create a dial rule that its priority number is bigger than the "Alias" default Dial rule as a Route to Trusted Neighbor. Give it a prefix (e.g. 12) and in the rule set to remove x characters where x is the length of the prefix. If user wants to change CMA max CP resolution, then change RMX CP resolution flag and reboot RMX and CMA. If a power failure occurs when the secondary is acting as primary and the system becomes unresponsive, reboot the unresponsive server. In general, the primary server should always be the active server. If a failover from the primary server to the secondary server occurred, once the primary server s back online and available, use the Switch Server functionality to restore the primary to its active role. Check endpoint status before scheduling them in a call starting now. Use a font size of 10, 11 or 12. Do the upgrade using Microsoft Internet Explorer or Apple Safari browser. Reboot servers. Delete duplicate device. Go to the URL/flex and you will be redirected properly. If there are issues with conferences, check the associated RMX. Polycom CMA Desktop scheduling is not supported, so they should only show as in person in conferences. 9

# Issue Workaround SSGSE-3359 SSGSE-3340 SSGSE-3309 SSGSE-3299 SSGSE-3294 SSGSE-2771 SSGSE-2051 SSGSE-1810 SSGE-596 SSGE-584 SSGE-572 SSGE-569 SSGE-565 SSGE-549 SSGE-532 SSGE-529 SSGE-525 SSGE-502 SSGE-490 SSGE-487 Apache logs are not automatically rotated and grow too large. Send message appears like a valid option for Polycom CMA Desktop, but doesn t work Disconnecting a participant from a conference and then reading them results in an extra CDR record. Serial console allows non-printable characters in the system name Duplicate CDRs for a Polycom CMA Desktop ad hoc call Conference Monitoring does not list current conferences after a failover. Outlook Plugin: Delete the previous version plugin scheduled conf CDRs for ad hoc point-to-point calls are duplicated, as there is no means for the server to associate the records. CMA5000, with SQL cluster. SQL reports CleanSE200Tables errors in SQL logs. Redundant CMA5000 V4.1 - When replying to RAS messages doesn't use the virtual IP avoiding V²IU to handle them. CMA-Server is producing a job failure on the SQL Server regarding the 'CleanSE200Tables' job. CMA4000 - Changes to neighbor gatekeeper statements do not take effect until the server is rebooted. Qualys scan reports security vulnerabilities CMA- Provisioning of the Time Zone for HDX does not work properly and Fails if you set to GMT +0 CMA 5000: how to set up a Tandberg EP (MXP990) to use Global Directory. CMA Scheduling - 'Add Guest' allows two participants with identical email addresses to be added to a conference but 'Add from Guest Book' does not. CMA UI issue - CMA End Point / Monitor View, end point Call Info TX and RX video info is reversed. During conference scheduling, operator not able to add a dial in guest if the selected guest is H.320 (ISDN). CMA- CMA Desktop. When Active directory users log in they are not able to get into Presence. CMAD Presence not working in CMA Desktop due LDAP user has a space between user names. Apache logs must be removed manually.. This is not a valid option for Polycom CMA Desktop at this time. Disregard the record. Use standard characters for system name. Use the Future Only filter and they will appear. Manually edit files. 10

# Issue Workaround SSGE-480 SSGE-451 SSGE-450 SSGE-449 SSGE-417 SSGE-400 SSGE-361 SSGE-361 SSGE-356 SSGE-355 SSGE-355 SSGE-350 SSGE-350 SSGE-344 SSGE-344 CMAD clients are unable to log in to the Presence Server with because the LDAP username has a space in it. End time warning not always showing on endpoint when scheduled from CMA HTTP URL and other information is missing from the device record when an ampersand is in the system name for an endpoint Polycom CMA system remote video feed does not work intermittently Voice calls received by VSX units from VTX phones integrated with VSX show as H323 calls in the Call Info pane of the Polycom CMA system. Calls transferred from a Cisco IP phone to the RMX are dropped when neighbored with CMA. Gatekeeper registration timeout function is not functional. "Registration Timeout (days):" does not function as stated. Unable to manage a VSX in Security Mode. CMA displays IP address conflict error. Cannot successfully schedule a non-aes encrypted device to be connected to an encrypted RMX conference. Polycom CMA system cannot successfully schedule a non-aes encrypted device to be connected to an encrypted RMX conference. Presence not working in Polycom CMA Desktop when there is a space in the username. Presence not working in their AD because they have spaces between user names - first last, and can't change their configuration. If participants are scheduled as dial-in on the Polycom CMA system for conference to be hosted on RMX1000, the RMX1000 dials out to the participant. RMX1000 dial-in participants scheduled as dialin via Polycom CMA system end up as dial-out. The following table lists some of the known limitations of the Polycom CMA system when interoperating with partner gatekeepers and endpoints. # Issue Comment CSC-6 CSC-3 CSC-2/ SSGSE-2200 Cisco/Busy signal is heard on Cisco phones when VSX or HDX disconnects. Call Type in conference management screen indicates an incorrect type Bit Rate in conference management screen is incorrect An endpoint issue related to issue VIDEO-57092, which is marked Will Not Fix. Open issue Open issue 11

# Issue Comment AVA-707/ CSC-5/ SSGSE-2202 AVA-708 AVA-726 Mute indication not displayed in conference management screen when muting occurs. Avaya/Video protocol and format on the conference management screen always displays as AUTO. Avaya/RMX2000/CDR/Destination field is blank on the CDR when the Avaya softphone or hardphone dial into a conference. Open issue Open issue Open issue AVA-715 No audio heard after Avaya phone is taken off hold. Enhancement request. The Polycom CMA system does not currently support audio shuffling. AVA-716 AVA-709/ CSC-4 Endpoints do not negotiate video when the Avaya softphone transfers a call. Incorrect call duration for an ad hoc conference. Enhancement request. The Polycom CMA system does not currently support audio shuffling. Enhancement request. Currently, the Polycom CMA system shows duration for scheduled conferences only, not ad hoc conferences. Where to Get the Latest Product Information To view the latest Polycom product documentation, visit the Support section of the Polycom website at www.polycom.com/support. 12

Appendix A: Polycom CMA System Operating System The Polycom CMA system uses Microsoft Windows 2003 Server R2 x64 SP 2 with the following updates/patches applied (ordered by KB#): KB924667-v2 - Security Update for Windows Server 2003 KB925398 - Security Update for Windows Media Player 6.4 KB925902 - Security Update for Windows Server 2003 KB926122 - Security Update for Windows Server 2003 KB927891 - Update for Windows Server 2003 KB929123 - Security Update for Windows Server 2003 KB930178 - Security Update for Windows Server 2003 KB931768 - Security Update for Windows Server 2003 KB932168 - Security Update for Windows Server 2003 KB932596 - Update for Windows Server 2003 KB933566 - Security Update for Windows Server 2003 KB933729 - Security Update for Windows Server 2003 KB935839 - Security Update for Windows Server 2003 KB935840 - Security Update for Windows Server 2003 KB936021 - Security Update for Windows Server 2003 KB936357 - Update for Windows Server 2003 KB936782 - Security Update for Windows Server 2003 KB937143 - Security Update for Windows Server 2003 KB938127 - Security Update for Windows Server 2003 KB938464 - Security Update for Windows Server 2003 KB939653 - Security Update for Windows Server 2003 KB941568 - Security Update for Windows Server 2003 KB941569 - Security Update for Windows Server 2003 KB941644 - Security Update for Windows Server 2003 KB941693 - Security Update for Windows Server 2003 KB942589 - Hotfix for Windows Server 2003 KB942615 - Security Update for Windows Server 2003 KB943055 - Security Update for Windows Server 2003 KB943460 - Security Update for Windows Server 2003 KB943485 - Security Update for Windows Server 2003 KB944338 - Security Update for Windows Server 2003 KB944338-v2 - Security Update for Windows Server 2003 KB944533 - Security Update for Windows Server 2003 KB944653 - Security Update for Windows Server 2003 KB945553 - Security Update for Windows Server 2003 KB946026 - Security Update for Windows Server 2003 KB947864 - Security Update for Windows Server 2003 KB948496 - Update for Windows Server 2003 KB948590 - Security Update for Windows Server 2003 KB948881 - Security Update for Windows Server 2003 KB950759 - Security Update for Windows Server 2003 KB950760 - Security Update for Windows Server 2003 KB950762 - Security Update for Windows Server 2003 KB950974 - Security Update for Windows Server 2003 KB951066 - Security Update for Windows Server 2003 KB951072-v2 - Update for Windows Server 2003 KB951698 - Security Update for Windows Server 2003 KB951748 - Security Update for Windows Server 2003 KB952954 - Security Update for Windows Server 2003 KB953838 - Security Update for Windows Server 2003 KB953839 - Security Update for Windows Server 2003 13

Appendix B: SQL Server Configuration to Prevent Random 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. This problem is exacerbated by the fact that a Polycom CMA or ReadiManager SE200 system does not try to reconnect on its own. We have enhanced some system modules, such as the Device Manager and CDR Manager, so they do initiate a reconnection to the database, which alleviates the problem to a great extent. But there are still modules that do not. After researching the problem, we have determined that the database connection is closed by the TCP stack on the Microsoft SQL 2005 server, not by the Polycom CMA and ReadiManager SE200 systems. There is a fairly new feature in the SQL server s TCP that looks for orphaned connections. The server sends Keep Alive (heartbeat) messages to the client through each of the connections and expects acknowledgments. If no acknowledgment is received within stipulated time and after a stipulated number of re-transmissions, the server closes that particular connection. The default time for Keep Alive message to start is 30secs. If no acknowledgment is received from the client for that particular connection, the local server TCP will keep sending Keep Alives to the client and will wait for KeepAliveInterval(default 1sec) between each retransmissions. After TcpMaxDataRetransmissions(default 5) times of sends-and-no-acknowledgments, the server will close the connection with the assumption that the client is probably not operational anymore. The default setting for this feature has been found to be too aggressive and it renders easy for client systems to fatally miss successful acknowledgments every time. Temporary network latencies, systems being too busy to respond or even the low level NIC s state can cause this failure. Hence, Polycom requires a change to the Keep Alive setting on the Microsoft SQL Server to pace the heartbeats better. We have tested with various wait-time settings for the Keep Alive variable and have found exercising this feature every hour is ideal. The change of configuration on Microsoft SQL Server is on a per instance basis. So the affect should be localized and should not affect other instances in the same database. The following is the procedure: 1. From the Microsoft SQL Server Configuration Manager, select Start > All Programs > Microsoft SQL Server 2005 > Configuration Tools > SQL Server Configuration Manager. 2. Expand SQL Server 2005 Network Configuration. 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 3600000 (once every hour). 7. Restart Microsoft SQL server. 14