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

Transcription

1 Release Notes Polycom Converged Management Application (CMA ) System Version Polycom announces the general release of its Polycom Converged Management Application (CMA ) System Version scheduling and management system. This document provides the latest information about this release. Topics Introducing the Polycom CMA System Release... 2 The Polycom CMA System 4.0 Release... 2 System Requirements... 6 Installation and Upgrade Notes... 7 Interoperability... 7 Polycom Device Version Requirements... 7 Microsoft Windows Vista... 7 Strategic Global Partners... 8 ipower Support... 8 RMX Integration... 8 Resolved Issues... 9 Known Issues... 9 Where to Get the Latest Product Information Copyright Information 2008 Polycom, Inc. All rights reserved C1 (February 2009) Polycom Inc West 121st Avenue Westminster, CO U.S.A. Trademark Information Polycom, the Triangles logo, ReadiManager, SoundPoint, SoundStation, ViaVideo, VoiceStation, and Vortex are registered trademarks of Polycom, Inc. ConveneT TM, Global Management System TM, ipower TM, MGC TM, People+Content TM, People On Content TM, Polycom Conference Suite TM, Polycom HD Voice TM, Polycom PathNavigator TM, Polycom VideoPlus TM, Polycom VoicePlus TM, PVX TM, RAS TM, ReadiConvene TM, RMX 2000 TM, RSS TM, V2iU TM, VS4000 TM, VSX TM, and VTX TM are trademarks of Polycom, Inc. Other product and corporate names may be trademarks of other companies and are only used as a fair use reference without intent to infringe.

2 Introducing the Polycom CMA System Release Polycom is pleased to announce the release of its Polycom Converged Management Application (CMA ) system version scheduling and management system. The Polycom CMA system version includes: Support for the new Polycom HDX system version 2.5 Ability to invoke the Tandberg management user interface for supported models Release of Scheduling Plugins for Microsoft Outlook and IBM Lotus Notes in Korean and Simplified Chinese Release of online help systems for the Polycom CMA system scheduling interfaces including the Web Scheduler and scheduling plugins. The Polycom CMA System 4.0 Release The Polycom CMA system version 4.0 is an expansion of the ReadiManager 3.0 system with several new features that make it easier to deploy and use. The CMA system includes the newly reengineered, browser-agnostic, system web interface, but also includes the following features: New, more powerful and scalable platform The Polycom CMA system resides on a more powerful platform a Polycom-branded Dell PowerEdge 1950 Server. Polycom offers two Polycom CMA system models. The Polycom CMA 4000 system, which has 1 microprocessor and 1 hard drive, supports up to 400 concurrently registered endpoints and 240 concurrent calls. Integration with a corporate directory and an external database is optional. The Polycom CMA 4000 system is not available in redundant configurations. The Polycom CMA 5000 system, which has 2 microprocessors and 2 hard drives, can integrate support up to 5000 concurrently registered endpoints and 1500 concurrent calls. Integration with a corporate directory (Microsoft Active Directory) and an external database (Microsoft SQL Server) is required. The Polycom CMA 5000 system is available in an optional redundant configuration. Polycom CMA Desktop The Polycom CMA Desktop client, which is bundled with the Polycom CMA system, is a PC-based application for communicating over video and voice, and sharing content. The Polycom CMA Desktop client allows enterprise users to simply point and click to collaborate with colleagues over video. Integrated presence-awareness allows users to verify contact availability and status, and seamless enterprise directory integration simplifies management and ensures contact list accuracy. Centrally deployed through the Polycom CMA system, Polycom CMA Desktop clients are licensed and managed in the same manner as other dynamically managed telepresence and room-based video conferencing systems. However, Polycom CMA Desktop licenses may be reclaimed after reaching a set inactivity threshold. Polycom CMA Desktop clients are a licensed component of the Polycom CMA system, in accordance with the industry-recognized CAL (Client Access License) deployment model. In this first release, Polycom CMA Desktop devices can only be called on an ad hoc basis, although the device users may be scheduled. In a future release, users will be able to schedule Polycom CMA Desktop devices. 2

3 Polycom CMA Desktop clients (like all other CMA-managed devices) must be on the same network as the Polycom CMA server. A Polycom CMA Desktop client can operate through a virtual private network (VPN), if in all aspects the VPN is configured such that the CMA Desktop client appears to be on the same network as the server. Customers using a VPN for remote access are responsible for ensuring their VPN provides full access for the client to contact the server. Polycom Global Services cannot provide support for VPN configuration and traffic analysis. Automatic Provisioning The Polycom CMA system provisioning feature allows an administrator to configure one or more endpoints with the set of information (based on administratively configured user policies) the registering devices need to operate within the network. This eliminates the need to configure each endpoint individually. The Polycom CMA system supports two exclusive provisioning processes: automatic and scheduled. Automatic and scheduled provisioning are exclusive management scenarios. Endpoints enabled for automatic provisioning should not be scheduled for provisioning through the Polycom CMA system. In dynamic management (automatic provisioning) mode, when the endpoint starts up and at designated polling intervals, it automatically pulls the device and site provisioning information from the Polycom CMA system. (Note: Site-based provisioning data is used to ensure mobile endpoints always receive the right settings to enable them to make calls.) Provisioning information is sent in XML format over a secure HTTPS connection. To enable automatic provisioning, an administrator must: Add a DNS server record to the domain name controller for the Polycom CMA system, the enterprise directory, and the external database Either create an automatic provisioning profile or accept the system default automatic provisioning profile. The administrator can also associate default provisioning profiles with a User Group, so they can partition provisioning profiles by environment (fields that are the same across all EPs), administration policy (fields that are configured to be the same across a group of EPs, perhaps all of the same family/model), and user preferences (small set of fields that can be specified on a per user/device basis). Currently, scheduled provisioning is available for most supported endpoints, while automatic provisioning is only available for Polycom CMA Desktop clients. Automatic Softupdate The Polycom CMA system softupdate feature allows an administrator to upgrade the software on one or more endpoints with a standard software package. This eliminates the need to upgrade each endpoint individually. The Polycom CMA system supports two exclusive softupdate processes: automatic and scheduled. Automatic and scheduled softupdate are exclusive endpoint management scenarios. Endpoints enabled for automatic softupdate should not be scheduled for softupdates through the system. The automatic softupdate feature is enabled at the endpoint. At start up and at designated intervals, endpoints in automatic softupdate mode automatically pull a softupdate profile and package from the Polycom CMA system. The softupdate package is sent in XML format over a secure HTTPS connection. The requirements for enabling automatic softupdate are the same as those for enabling automatic provisioning. 3

4 Currently, scheduled softupdate is available for most supported endpoints, while automatic softupdate is only available for Polycom CMA Desktop clients. Presence Service The Polycom CMA system includes a presence service that allows video endpoint users to view details about their contacts, including the availability and system capability of the contacts in their contact list. Currently, presence service is only available for Polycom CMA Desktop clients. System Guest Book When creating conferences, schedulers can add guest participant (participants not available from the local directory, enterprise directory, or Global Address Book) to conferences. Now, schedulers can also save guest participants to the system Guest Book so the guest participant s information is saved and the guests can be added more easily to future conference. Tandberg MXP Endpoint Support The Polycom CMA system supports gatekeeper and GAB registration, scheduled provisioning and scheduled softupdate of key fields on Tandberg MXP Series endpoints, including the 990, 880 and 770. Tested and supported versions include: F5.0, 5.3, 6.0, 6.3, and 7.0. The Polycom CMA system supports gatekeeper and GAB registration on Tandberg 6000, Edge95, 1700, 1500 endpoints. Direct Mode When in Direct Mode, the Polycom CMA system does not route selected H.225 call signaling messages (i.e., SETUP, CALL PROCEEDING, ALERTING, CONNECT, and NOTIFY) through the Polycom CMA system gatekeeper. The advantage of this selection is that scheduled point-to-point conferences stay connected should the gatekeeper reboot. The disadvantage is that after a reboot, the gatekeeper does not manage bandwidth requirements for ongoing conferences and cannot monitor ongoing conferences. Also, Simplified Dialing, Least Cost Routing, Conference On Demand, and MCU board hunting do not work when the system is in direct mode. Scheduler Select An MCU Option By manipulating the conference template set up, Polycom CMA system administrators can allow schedulers to request a specific MCU type or specific MCU when scheduling a conference. While the Polycom CMA system defaults to Auto MCU Selection, different conference template options may allow schedulers to request Any MCU, Any MGC, Any RMX, or an individual RMX and MGC MCU defined to the Polycom CMA system. Enhanced Site Topology The Polycom CMA system now offers a graphical view of sites and site links and the ability to automatically generate functional multi-site links. The Site Topology page supplements the existing Sites and Site Links pages, and the functions and data available on the Sites and Site Links pages are also available on the Site Topology page. That means the administrator can: Add, edit, or delete sites and site links on the Site Topology page and Generate multi-site links automatically on the Site Topology page Make and save layout and presentation modifications View Tooltips that provide the pertinent data about sites and site links 4

5 Use the graphical Site Topology page as a dashboard to view real-time alarms and select an alarm to and see the message behind it H.350/LDAP-based Directory Services The Polycom CMA system can now store video dialing information in H.350 format. H.350 was developed to address the problems experienced when building and scaling Voice over IP (VoIP) and IP-videoconferencing networks. H.350 uses Lightweight Directory Access Protocol (LDAP) to provide a uniform way to store and locate end-user and endpoint information in directories that are seamlessly linked to, and built upon, identity management systems already in place within an enterprise network. Currently the Polycom CMA system only supports a Microsoft Active Directory implementation of LDAP. Also, the Polycom CMA system can only use its internal H.350 data; it cannot connect to an external H.350 database. The Polycom CMA system uses Java to integrate with the Microsoft Active Directory, which supports only NTLM version 1 for encryption between the Polycom CMA system client and the active directory server. Microsoft Windows Vista support The Polycom CMA system, the Polycom CMA Desktop client, and the Scheduling Plugin for Microsoft Outlook can now run on computers running the Microsoft Windows Vista (NTLM v1) operating system. Enhanced Localization and Internationalization Additional language support has been added to the Polycom CMA system. Besides French, International Spanish, German, English, and Japanese, the Polycom CMA system interface and scheduling documentation is now localized into Simplified Chinese and Korean. Also, the Polycom CMA system now supports localized enterprise directories. In this release, the Scheduling Plugin for Lotus Notes has not been localized into Simplified Chinese or Korean and the online help for the scheduling applications has not been localized into Japanese, Simplified Chinese, or Korean. PDF versions of the scheduling guides are available in these languages. On systems using Internet Explorer versions 6 or earlier, Polycom CMA Desktop supports passwords using ASCII characters only. In order to use Polycom CMA Desktop with unicode user names and passwords (including Chinese characters), you must install Internet Explorer 7.0 or later. Some name and description fields in the Polycom CMA system interface are English-only. These include GAB user names, automatic and scheduled provisioning profile names, RMX profile names, and conference template descriptions. ISDN Support The Polycom CMA system now supports ISDN endpoints. If the RMX 2000 hosting the call supports ISDN, the ISDN service on the RMX dials the ISDN endpoint and puts it into conference. If the RMX 2000 hosting the call does not support ISDN, the Polycom CMA system sends the call through a gateway that can dial the ISDN endpoint and put it into conference. Also, the Polycom CMA system allows you to reserve ISDN endpoints as dial-in devices using an entry queue. 5

6 Also new in the Polycom CMA system: Device Policy Groups transitioned Device policy groups have been transitioned to other sections of the Polycom CMA system. The functions provided by the device policy groups are now managed elsewhere. Maximum bit rate. Maximum bit rate can be set at the endpoint. For Polycom CMA Desktop systems and Polycom HDX system endpoints version 2.5 or greater, the Polycom CMA system can provision this endpoint setting. Also, the Polycom CMA system Site Link page has a configurable setting for the maximum bandwidth per call that over-rides the endpoint. This setting applies to all calls placed over the given site link. Set Alternate Routing Policies. Device policy groups allowed administrators to set alternate routing policies for a group of endpoints. These alternate routing policies included: IP only allow bit rate reduction, IP only requested bit rate, and IP with reduction and then ISDN. The Polycom CMA system: Will always allow bandwidth reduction. Administratively, this makes more sense because disallowing bandwidth reduction results in call setup failure when there is insufficient IP bandwidth to satisfy the requested. Will no longer support device policy group filters for dial rules, such as IP only a requested bit rate. Use the site-based filter for dial rules. Will no longer offer failover to ISDN when there is insufficient IP bandwidth. Use the endpoint s dialing order to control failover from IP to ISDN. Dial Plan. Device policy groups could also be used to limit the applicability of a dial rule to only those endpoint with a given device policy group. The ability to use device policy groups for dial rule filtering has been eliminated. However, you can still limit the applicability of a dial rule to a specified site remains. This Polycom CMA system 4.0 release also resolves some defects. For more information on the fixed defects, see Resolved Issues on page 9. 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 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) Microsoft Internet Explorer 6.0+ or 7.0, Mozilla FireFox 2.0x, or Apple Safari 3.x Microsoft Outlook 2000 SR1, Outlook 2003 SP2, or Outlook 2007 (for the Polycom Scheduling Plugin for Microsoft Outlook only) on Microsoft Windows XP IBM Lotus Notes 7.x (for the Polycom Scheduling Plugin for IBM Lotus Notes only) 6

7 The Polycom CMA system External database (optional, but recommended) Microsoft SQL Server 2005 SP2 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) The Polycom CMA system databases should have their own database instance, and should not be part of a shared database instance. Enterprise directory (required) 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. Installation and Upgrade Notes Installation of new Polycom CMA systems is managed through Polycom support. For more information, please contact your Polycom representative. Only a version 4.0 Polycom CMA system can be upgraded to version If the system being upgraded had patches applied, with the exception of the E.164 Patch , you must reapply the most current version of those patches to the system after the upgrade. (The E.164 Patch is included in version Polycom CMA system.) Patches and the instructions to load them are available at If a patch is not available there, contact Polycom Global Services. Interoperability Polycom Device Version Requirements Polycom V-Series (all software versions) Polycom VSX-Series (all software versions) Polycom ViewStation SP 6.x or higher Polycom RMX or higher Polycom RMX or higher Polycom ViewStation 7.x or higher Polycom ViewStation FX/EX 5.x or higher Polycom PVX or higher Polycom MGC or higher Polycom HDX systems or higher Polycom HDX Systems Polycom HDX systems operating in dynamic management mode (that is, configured with automatic provisioning) no longer create entries in the Polycom Global Address book. Microsoft Windows Vista As stated previously, the Polycom CMA system and Polycom CMA Desktop are supported on the Windows Vista platform with NTLM version 1 enabled. By default, Windows Vista ships with NTLM version 2 enabled. In this case, to use the Polycom CMA system and Polycom CMA Desktop client, you must enable NTLM version 1 via the Security Policies Console, as described here. Changing this setting requires administrator rights to the desktop. 1. From the Windows Start menu, select Run. 2. In the Run dialog box, type: secpol.msc 7

8 The Security Policies Console displays the Local Security Settings page. In the console tree, Local Policies > Security Options is selected 3. From the Policy list, right click on the Network security: LAN Manager Authentication level policy and select Properties. 4. Change the Send LM & NTLM responses selection to Send LM & NTLM use NTLMv2 session security if negotiated. 5. Click OK and close the Security Policies Console. We will provide guidance to IT departments that have implemented Windows Vista on how to push these settings out, so that end users will not need to make these changes themselves. In a future release, we expect to make changes on the server that will eliminate the need to change this setting. 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 ReadiManager 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 9 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 an RMX MCU 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 templates. Refer to the 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, you should do all scheduling and monitoring through it to avoid resource conflicts. While the MCU may have on-board scheduling capabilities, scheduling conflicts can occur if there is not full two-way sharing of information between the management system and the MCU. 8

9 Resolved Issues The following table lists the resolved issues in this Polycom CMA system release. # Issue SSGSE-3746 SSGSE-3731 SSGSE-3741 Customer Beta-Issue Unicode username and password in double-byte languages are causing NTLM authentication issues A general effort was made to improve performance in the area gatekeeper device registrations and initial system startup. Group names now support Unicode characters. The E164 number generation algorithm is now based on the user s telephone number (as opposed to being completely random). Known Issues The following table lists the known issues in this Polycom CMA system release. # Issue Workaround SSGSE-3706 SSGSE-3729 SSGSE-3728 SSGSE-3709 SSGSE-3653 SSGSE-3638 SSGSE-3627 SSGSE-3623 SSGSE-3612 Call failures may occur if the number of concurrent calls exceeds Internal load testing suggests that when the concurrent call level reaches 1000, additional calls may not be successful and/or current calls may be impacted. Functionality is lost if the CMA web interface is used with a Flash Player version greater than 9 In some situations, server-managed softupdates of VSX devices fails usually due to upgrade and downgrade key and option key issues. You are prompted to install backplane drivers after imaging a Polycom CMA 4000 server When there are 60 or more sites, the Generate Multi-site Links function does not work. 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. Significant network latency between the Polycom CMA system and the endpoints may cause the endpoints to go on- and offline frequently. 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. Microsoft OS patches that resolve this issue will be included in Polycom CMA system version If you experience an issue prior to the release, contact Polycom support for OS patch updates. Re-install flash player version 9. Contact Polycom Global Services The system will search for, and ultimately locate, the necessary driver, so no intervention is required. If you wish to automatically generate multi-site links, confine your number of sites to 59 or less. 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. 9

10 # Issue Workaround SSGSE-3606 SSGSE-3588 SSGSE-3580 SSGSE-3572 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. Scheduling failure message states Insufficient MCU Resources when the problem is really Insufficient Bandwidth Scheduled gateway conferences do not show up on the conference summary report If network is lost during set up of the redundant server, the virtual IP configuration will be incorrect. Check if a provisioning profile is assigned to a group prior to deleting it. If it s already been deleted, assign the group to a new, existing, provisioning profile. Reboot servers. SSGSE-3553 Users can still login even if the DB connection is lost. If logs indicate the database is down, restore the database before attempting normal system use. SSGSE-3533 SSGSE-3521 SSGSE-3501 SSGSE-3481 SSGSE-3456 SSGSE-3447 SSGSE-3386 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. Administrative users can assume ownership of any conference and then the original owner cannot see/access it. 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 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. SSGSE-3359 Apache logs are not automatically rotated. Clean up old logs manually. Note the logs do no grow quickly. SSGSE-3340 SSGSE-3309 SSGSE-3299 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 SSGSE-3294 Duplicate CDRs for a Polycom CMA Desktop ad hoc call. This is not a valid option for Polycom CMA Desktop at this time. Disregard the record. Use standard characters for system name. SSGSE-3280 Large, recurring conferences scheduled for NOW fail to launch. Do not schedule recurring conferences to start NOW. SSGSE-3160 SSGSE-2771 SSGSE-1810 Can't associate Polycom CMA Meeting Form with video specific calendar in outlook Conference Monitoring does not list current conferences after a failover. CDRs for ad hoc point-to-point calls are duplicated, as there is no means for the server to associate the records. Use the Future Only filter and they will appear. Manually edit files. 10

11 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 AVA-707/ CSC-5/ SSGSE-2202 AVA-708 AVA-726 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 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. An endpoint issue related to issue VIDEO-57092, which is marked Will Not Fix. Open issue Open issue Open issue Open issue Open issue AVA-715 No audio heard after Avaya phone is taken off hold. Enhancement request. The ReadiManager 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 ReadiManager system does not currently support audio shuffling. Enhancement request. Currently, the ReadiManager 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 11