Polycom CMA System Deploying Visual Communications Administration Guide

Transcription

1 Polycom CMA System Deploying Visual Communications Administration Guide Version February A1

2 Trademark Information Polycom, the Polycom logo design, ReadiManager SE200, SoundStation, ViewStation, Vortex, and VSX are registered trademarks of Polycom, Inc. Global Management System, Instructor FS, ipower, PathNavigator,People+Content, People on Content, Polycom Converged Management Application (CMA ), Polycom EagleEye, Polycom HDX 4000, Polycom HDX 7000, Polycom HDX 8000, Polycom HDX 9000, Polycom HDX 9001, Polycom HDX 9002, Polycom HDX 9004, Polycom MGC, Polycom RMX 1000, Polycom RMX 2000, Polycom RSS 2000, Polycom Video Border Proxy (VBP ), PowerCam, SoundStructure, StereoSurround, and VS4000 are trademarks of Polycom, Inc. in the United States and various other countries. Allother trademarks are the property of their respective owners. Patent Information The accompanying product is protected by one or more U.S. and foreign patents and/or pending patent applications held by Polycom, Inc Polycom, Inc. All rights reserved. Polycom, Inc Willow Road Pleasanton, CA USA 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. Under the law, reproducing includes translating into another language or format. As between the parties, Polycom, Inc., retains title to and ownership of all proprietary rights with respect to the software contained within its products. The software is protected by United States copyright laws and international treaty provision. Therefore, you must treat the software like any other copyrighted material (e.g., a book or sound recording). Every effort has been made to ensure that the information in this manual is accurate. Polycom, Inc., is not responsible for printing or clerical errors. Information in this document is subject to change without notice.

3 Contents About This Guide v Required Skills v 1 Polycom Visual Communications How to Create the Polycom Visual Communications Experience Management System Endpoints Conferencing Platform Network Requirements Database Enterprise Directory Features of the Polycom Visual Communications Experience Seat Capacity and Licensing Directory Services Authentication Security Device Provisioning Device SoftUpdate Localization User Management Deployment Process Overview Pre-installation Planning Phase Installation Phase Post-installation Phase Polycom, Inc. iii

4 Deploying Visual Communications Administration Guide 3 Polycom CMA System Deployment 4 Polycom RMX Installation and Integration 5 Endpoint Installation and Integration Polycom CMA Desktop Deployment Polycom HDX Systems Polycom HDX System Deployment Standard Endpoints Supported Third-Party Endpoint Support Testing the Deployment A Polycom HDX System Configuration Files A System Security and Port Usage Port Usage Index iv Polycom, Inc.

5 About This Guide This guide describes how to deploy the Polycom Visual Communications experience specifically the Polycom products that enable the experience. Required Skills Deploying the Polycom Visual Communications experience requires planning and elementary knowledge of video conferencing and video conferencing administration. Also, the Polycom Visual Communications experience requires: An external domain name server An external Microsoft SQL database server An external Microsoft Active Directory server This document assumes that these systems are already deployed and that the administrators for these applications are available to aide the administrator deploying the Polycom Visual Communications experience. Polycom, Inc. v

6 Deploying Visual Communications Administration Guide vi Polycom, Inc.

7 1 Polycom Visual Communications The Polycom Visual Communications experience is enabled by an integrated suite of Polycom hardware devices and software applications that allow you to quickly implement high-quality video and audio conferencing. This integration of Polycom products makes them faster to deploy and easier to manage. But these integrated products also provide the most requested video-conferencing functionality Polycom has to offer and may include: Scheduled device provisioning for standardly managed devices and automatic device provisioning for dynamically managed devices like Polycom Converged Management Application (CMA ) Desktop clients and Polycom HDX systems Scheduled device softupdates for standardly managed devices and automatic device softupdates for dynamically managed devices like Polycom CMA Desktop clients and Polycom HDX systems Conference scheduling via the Polycom CMA system Web Scheduler or the optional Polycom Scheduling Plugins for Microsoft Outlook or IBM Lotus Notes On-demand conferencing for endpoint users Gatekeeper functionality Access to global user and room directories for on-demand and scheduled calls. Directory services include: Presence and contact list functionality for dynamically managed devices like Polycom CMA Desktop clients and Polycom HDX systems Global Address Book functionality for standardly managed devices H.350 and LDAP directory functionality. H.350 defines a directory services architecture for multimedia conferencing for H.323, H.320, SIP and generic protocols. Device monitoring and management Conference monitoring and management An optional high-availability, redundant management server configuration Polycom, Inc. 1

8 Deploying Visual Communications Administration Guide How to Create the Polycom Visual Communications Experience This section describes some of the Polycom hardware platforms and software applications that can be integrated to create the Polycom Visual Communications experience. However, Polycom products are scalable to environments of any size, so customers can choose the products that work best for them to implement high-quality video conferencing. Management System The Polycom Visual Communications experience requires the Polycom CMA system. While your network configuration may include a ReadiManager system, ReadiManager systems don t support the visual communication experience of automatic provisioning, automatic softupdate, and presence. The Polycom CMA system must be placed behind an enterprise firewall. Endpoints The Polycom Visual Communications experience is supported by Polycom CMA Desktop clients and Polycom HDX endpoint systems in dynamic management mode. All 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 2 Polycom, Inc.

9 Polycom Visual Communications 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. While your network configuration may include other audio and video endpoints (see Endpoint Installation and Integration on page 29), they are supported in standard mode and are not eligible for automatic provisioning, automatic softupdate, and presence. Conferencing Platform The Polycom Visual Communications experience requires one or more Polycom RMX multimedia conferencing platforms. While your network configuration may include one or more Polycom MGC bridges, they don t support the endpoint systems required for automatic provisioning, automatic softupdate, and presence. Network Requirements To ensure system performance and reliability, Polycom recommends deploying our server products in a high quality IP network with very little packet loss (preferably 0%) and low latency. In systems with Enterprise Directory integration, the network between the Polycom CMA system and the enterprise directory should have less than 200 ms round-trip latency and less than 4% round-trip packet loss. The network between the Polycom CMA system and the conferencing platforms (RMX or MGC) should have less than 200 ms round-trip latency and less than 2% round-trip packet loss. Round-trip packet loss is the percent of ICMP packets lost in a round trip from one point in the network to another point and back again. Round-trip latency is the number of milliseconds an ICMP packet takes to travel from one point in the network to another point and back again. Database For easier management, you may integrate your Polycom CMA system with an external database. This integration allows your database to grow as needed and provides you with a toolset for managing your database. An external database is required for non-redundant and redundant Polycom CMA 5000 system configurations. Otherwise an external database is optional. The Polycom CMA system external database requires a Microsoft SQL Server 2005 system with: At least 1 gigabyte (GB) of memory (2 GB recommended) At least a 1 gigahertz (GHz) processor (2 GHz recommended) Polycom, Inc. 3

10 Deploying Visual Communications Administration Guide At least 4 GB of disk space (2 GB for each of the 2 databases) in addition to the 1 GB required by the database engine Enterprise Directory For easier user, group, and room management, we strongly recommend integrating your video conferencing systems with an enterprise directory. The Polycom Visual Communications experience supports only a Microsoft Active Directory implementation of an LDAP directory. To take full advantage of the Polycom CMA system, the enterprise Microsoft Active Directory must: Have Global Catalog turned ON. The Global Catalog enables searching for Active Directory objects in any domain without the need for subordinate referrals, and users can find objects of interest quickly without having to know what domain holds the object. Use universal groups. The Global Catalog stores the member attributes of universal groups only. It does not store local or global group attributes. Have a login account that has read access to all domains in the Active Directory that the Polycom CMA system can use. We recommend an account with a adminstrative username and a non-expiring password. Also, to allow Polycom HDX systems to dial ISDN phone numbers from the directory, the phone numbers must be stored in one of the following formats: Country Code.Area Code.Number Country Code.(National Direct Dial Prefix).Area Code.Number The enterprise directory is not managed by nor editable by the Polycom CMA system or endpoint users. Features of the Polycom Visual Communications Experience Seat Capacity and Licensing Management Server Licensing The seat capacity for a Polycom CMA 5000 system scales from 500 to 5,000 devices. The entry-level Polycom CMA 5000 system has a baseline capacity of 500 client access licenses. Additional licensing is offered in 100, 500, and 1000 license pack sizes. 4 Polycom, Inc.

11 Polycom Visual Communications The seat capacity for a Polycom CMA 4000 system scales from 200 to 400 devices. The entry-level Polycom CMA 4000 system has a baseline capacity of 200 client access licenses. Additional device licensing is offered in 100 license pack size. With your system order, you will receive one or more License Certificates. You must activate each License Certificate to receive an activation key, which you then enter in the Polycom CMA system. When applied to the system, an expansion license pack augments the device license count. For example, applying a 1000-device expansion license pack to a baseline Polycom CMA 5000 system will yield a total license count of 1500 concurrent licenses. Where applicable, the number of concurrent calls supported by a Polycom CMA system is derived from the number of device licenses at a 3/10 ratio (calls/devices). For example, a system licensed for 5000 devices supports up to 1500 concurrent calls in routed mode and 3000 calls in direct mode. Device licenses are consumed based on a 1:1 basis for any managed device (endpoints, MCU, GK, GW including personal endpoints, IP blades, and more) that can be added to the system by any means, including the user interface, registration for management services, or registration for Global Address Book services. Note Device licenses are consumed by managed devices, not by users. You may add any number of local or enterprise users to the Polycom CMA system. Polycom CMA Desktop Client Licenses Licensing for the Polycom CMA Desktop client is included with the Polycom CMA system. When a Polycom CMA Desktop client is provisioned by the Polycom CMA system, it automatically consumes a license. That license is then reserved for that Polycom CMA Desktop client. However, you can configure the Polycom CMA system to automatically released a Polycom CMA Desktop client license after a set number of days of inactivity. Licenses consumed by registered devices are never automatically released. To release a license from a registered device, an administrator must manually delete the device from the system. Directory Services Currently, the Polycom CMA system can integrate with two exclusive directory services structures an enterprise (LDAP) directory or a global address book (GDS) to which local users, groups, and rooms may be added. Polycom, Inc. 5

12 Deploying Visual Communications Administration Guide Enterprise Directory The enterprise directory allows users to is a structure that provide people enterprise-wide directory service that provides DoD People Discovery (i.e. white pages) and DoD identity management attribute services This integration: Speeds up deployment, because the enterprise directory automatically populates the Polycom CMA system User list with enterprise directory users and assigns them scheduling permissions. Allows you to import one or more enterprise groups, so that system features can be assigned at the group level. Allows you to designated which enterprise entries are conference rooms Allows users with scheduling permissions to enter their standard network usernames and passwords to log into the management and endpoint systems and select conference participants and rooms from the company s enterprise directory. Users Local Users The Polycom CMA system allows you to add local users (i.e., users added manually to the system) and associate them with devices and roles. For local users, the Polycom CMA system manages all user information and associations. Enterprise Users When the Polycom CMA system is integrated with an enterprise directory, the Polycom CMA system manages only two pieces of user information: the device(s) assigned to the user and the role assigned to the user. The remaining user information is pulled from the enterprise directory. Note Currently, the Polycom CMA system supports only a Microsoft Active Directory implementation of an LDAP directory. When integrated with an enterprise directory, users defined to the enterprise directory are by default added to the Polycom CMA system with a Scheduler role. You can also associate enterprise users with additional roles. Integration with an enterprise directory allows users to log into the Polycom CMA system with their enterprise user IDs and passwords and immediately begin scheduling dial-in conferences. However, to dial out to enterprise users, they must be associated with devices. 6 Polycom, Inc.

13 Polycom Visual Communications Groups Groups are efficient, because they allow you to assign roles and provisioning profiles to a set of users rather than to each user individually. Local Groups The Polycom CMA system allows you to add local groups (i.e., groups added manually to the system) and associate them with with provisioning profiles and roles. For local groups, the Polycom CMA system manages all group information and associations. Enterprise Groups When the Polycom CMA system is integrated with an enterprise directory, groups defined to the enterprise directory are not automatically added to the Polycom CMA system, but you can import enterprise groups into the system. For enterprise groups, the Polycom CMA system manages only three pieces of information: the provisioning profile assigned to the group, the role assigned to the group, and whether or not the group is displayed in the endpoint s directory. The remaining group information is pulled from the enterprise directory. User Roles and Permissions The Polycom CMA system is also a role and permissions based system. Users are assigned one or more user roles User roles are assigned a set of permissions Users can access only the screens and functions available to their role(s) and associated permissions An administrator has three options when implementing user roles. Implement the system default user roles of Administrator, Operator, and Scheduler and keep the standard permissions assigned to these roles Implement the system default user roles of Administrator, Operator, and Scheduler but change the permissions assigned to the Operator, and Scheduler roles. Create unique, workflow-driven user roles and determine which permissions to assign to each user role To ensure Polycom CMA system access and stability, the default roles cannot be deleted and the Administrator role cannot be edited. Polycom, Inc. 7

14 Deploying Visual Communications Administration Guide Rooms The Polycom CMA system also manages local and enterprise rooms. You add local rooms manually. You add enterprise rooms by finding them in the enterprise directory and then associating the room with a device. Currently the Polycom CMA system does not manage virtual rooms virtual rooms are defined on a Polycom RMX or Polycom MGC MCU. Authentication The Polycom CMA system uses NTLM (version 1) authentication. NTLM is a suite of authentication and session security protocols used in various Microsoft network protocol implementations and supported by the NTLM Security Support Provider. To allow endpoints to use NTLM Single Signon technology to connect to the system and access Polycom CMA system services, you must integrate the Polycom CMA system with a Microsoft Active Directory domain controller. Note While the Polycom CMA system is supported on the Windows Vista platform with NTLM version 1 enabled, by default, Windows Vista ships with NTLM version 2 enabled. To use the Polycom CMA system and Polycom CMA Desktop client, you must enable NTLM version 1 via the Security Policies Console. The Polycom CMA system authenticates the Polycom CMA Desktop client at the time of provisioning. Security Beside implementing NTLM authentication, the Polycom CMA system also includes the following new methods of securing its operations. AES provides media encryption TLS provides secure media signaling Communications between the system and the endpoints and scheduling plugins are over an HTTPS secured connection Device Provisioning The Polycom CMA system device provisioning, which requires provisioning profiles, allows an administrator to configure one or more devices with a standard set of information the registering devices need to operate within the network. This eliminates the need to configure each device individually. 8 Polycom, Inc.

15 Polycom Visual Communications The Polycom CMA system supports two exclusive types of device provisioning: automatic and scheduled. Automatic and scheduled device provisioning are exclusive management scenarios. Devices enabled for automatic provisioning should not be scheduled for provisioning through the Polycom CMA system. Note Polycom recommends that all endpoints in a region (i.e., a gatekeeper zone) be managed by a single management system. Automatic Device Provisioning The Polycom CMA system is a gatekeeper, and it manages video and audio devices. However, the system also manages users, because devices are only useful when they provide access to users. Automatic device provisioning, which controls the automatic configuration of devices and the management of video resources, is also tied to users and groups. That s because some users and groups may require significantly more video resources than others. Currently, automatic device provisioning is only available for: Polycom HDX systems deployed in dynamic management mode Polycom CMA Desktop clients Note Polycom CMA Desktop client provisioning occurs on a session by session basis. How Automatic Device Provisioning Works In dynamic management mode, when a device starts up (and at designated intervals thereafter), it automatically pulls provisioning information from the Polycom CMA system. The provisioning information is sent in XML format over a secure HTTPS connection. Automatic Provisioning Profiles Automatic device provisioning is enabled at the device, but the Polycom CMA system must have automatic provisioning profiles for both the device and the site at which the device resides. So to ensure out-of-box usability, the Polycom CMA system comes with default automatic provisioning profiles for both. However, you can edit these default profiles to meet your needs or add additional provisioning profiles to assign different video resources to different groups of users. Polycom, Inc. 9

16 Deploying Visual Communications Administration Guide Profile Order and Priority Automatic provisioning profiles are associated with groups, but what about those users who belong to more than one group what determines their experience? When you add new profiles, you assign a Profile Order. The Profile Order determines which provisioning profile takes priority. So when you add provisioning profiles, you may want to assign provisioning profiles with more robust privileges a higher priority than those providing less privileges. Scheduled Device Provisioning Scheduled device provisioning is enabled at the Polycom CMA system. To schedule a device for provisioning, the Polycom CMA system must already have a scheduled provisioning profile created for the device. How Scheduled Device Provisioning Works In this standard/traditional management mode, administrators with System Setup permissions schedule provisioning for one device or a group of devices; and they can schedule provisioning to occur immediately or for a date and time in the future. The provisioning data is sent in XML format over a secure HTTPS connection. Scheduled provisioning is available for these device types: ViewStation ViewStation FX & EX V-Series (VSX systems) Some Tandberg endpoints Polycom HDX systemss deployed in standard management mode Scheduled Provisioning Profiles The Polycom CMA system does not include a default profile for scheduled provisioning. You must create a profile before you can schedule a device for provisioning. Create a different profile for each device type (Polycom HDX system or Polycom CMA Desktop client) and group of users. Some examples of when to use scheduled provisioning profiles follow. To apply a standard set of options to each new device By creating templates of standard settings for different types of devices, or for the needs of different users, you can have the Polycom CMA system apply all the settings at once. After the device is connected and registered with the Polycom CMA system, you can use a provisioning profile that defines a range of other options. 10 Polycom, Inc.

17 Polycom Visual Communications To update the password for all devices of a particular type For security purposes, you can create a provisioning profile to update the password for endpoints on a regular basis and reuse the same profile quarterly. You might have several profiles, one for each type of device you want to update. To change the IP address of the Polycom CMA system gatekeeper when the Polycom CMA system is moved Device SoftUpdate The Polycom CMA system softupdate feature, which requires a softupdate profile for the device type and model, allows an administrator to upgrade the software on one or more endpoints with a standard software package. This eliminates the need to upgrade each device 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. Note Polycom recommends that all endpoints in a region (i.e., a gatekeeper zone) be managed by a single management system. Automatic Device Softupdates Automatic device softupdate, which controls the device s software version level, is tied to the Device Type. Currently, the automatic softupdate feature is only available for these device types. Polycom HDX systems deployed in dynamic management mode Polycom CMA Desktop clients How Automatic Device Softupdate Works In dynamic management mode, when a device starts up (and at designated intervals thereafter), it automatically checks with the Polycom CMA system to determine if it should download a newer softupdate package. If a softupdate is necessary, the package is sent in XML format over a secure HTTPS connection. Automatic Softupdate Profiles Automatic softupdate is enabled at the device, but the Polycom CMA system must have an automatic softupdate profile for the device type to fulfill the process. A default automatic softupdate profile with the description CMA Desktop - shipped version is available for the Polycom CMA Desktop Polycom, Inc. 11

18 Deploying Visual Communications Administration Guide client. Default automatic softupdate profiles are not available for other endpoint systems. To create an automatic softupdate profile, you upload the software package and create a profile for the update. Automatic Softupdate Versions After creating an automatic softupdate profile, you can use the Version to use and Allow this version or newer selections to manage the roll out of softupdate packages. These selections also allow you to manage the release of multiple software packages for the same device type. Some important things to note about software versions Newer software is identified by the version number. If the Allow this version or newer selection is enabled, when a dynamically managed endpoint polls the Polycom CMA system, the system will compare the current software version number with the packaged software version numbers. The Polycom CMA system will send the software package with the highest version number to the endpoint. You can also use the Version to use selection to roll devices back to older software versions. If you change the Version to use selection to an older software version and clear the Allow this version or newer selection, the Polycom CMA system will send the specifically identified software package to the endpoint even if it is an older version. Note Currently to roll back a Polycom CMA Desktop client to an older version, you must first remove the existing Polycom CMA Desktop client via the Windows Add or Remove Software selection. Then you can install the older software package. Scheduled Softupdates The scheduled softupdate feature is enabled at the Polycom CMA system. An administrator with System Setup permissions can schedule softupdates for one device or a group of devices to occur immediately or for a date and time in the future. Scheduled softupdates are available for these device types. ViewStation ViewStation FX & EX V or VSX Series Some Tandberg endpoints Polycom HDX systems deployed in standard management mode 12 Polycom, Inc.

19 Polycom Visual Communications Localization The products that create the Polycom Visual Communications experience are localized into Simplified Chinese, French, International Spanish, German, and English. The individual products may also be localized into other languages, as they are also distributed individually. User Management The Polycom CMA system manages the following user management entities: Name Description Comments Users list Groups list Rooms list Global Address Book System Guest Book Presence service contacts Displays local and enterprise user accounts. Local users are added to the system manually. Enterprise users appear in the Users list when you associate the Polycom CMA system with an enterprise directory. Displays local and enterprise groups. Local groups are added to the system manually. Enterprise groups appear in the Groups list when you associate the Polycom CMA system with an enterprise directory and then import the enterprise groups. Displays local and enterprise rooms. Local rooms are added to the system manually. Enterprise rooms appear in the Rooms list when you associate the Polycom CMA system with an enterprise directory and then search for the room in the enterprise directory. Automatically populated by devices that register with the gatekeeper function of the Polycom CMA system. You can edit a device in this list and associate the device with a user. Entries added to the system Guest Book when Polycom CMA system schedulers enable the Save to Guest Book option when they add a guest participant to a conference. For dynamically managed endpoint systems only. Presence service contacts are XMPP buddy entries saved as contacts by both buddies and stored with the presence service. Entries saved as contacts by both buddies and stored with the presence service share presence status. For Polycom endpoint systems, such as Polycom HDX systems, these local and enterprise user, group, and room entries may appear in the endpoint s directory and/or contacts. For more information, see the endpoint system s product documentation For Polycom CMA Desktop systems, these local and enterprise user, group, and room entries may appear in the endpoint system s directory and/or contacts list. For Polycom endpoint systems, such as Polycom HDX systems, Global Address Book entries may appear in the endpoint s directory and/or contacts. For more information, see the endpoint system s product documentation Polycom CMA Desktop systems cannot access the Global Address Book. The Guest Book is only available to people scheduling conferences via the Polycom CMA system Web Scheduler. Not listed in the Polycom CMA system interface. Stored in the system database as the XMPP_db file. Polycom, Inc. 13

20 Deploying Visual Communications Administration Guide Some additional settings may affect whether or not entries appear in an endpoint s directory: When Directory Viewable is enabled for a local or enterprise group (the default setting), the group appears in the endpoint system s directory. When Allow Directory Changes is enabled at the endpoint, Polycom HDX systems can manage their own set of local and enterprise users, groups, and rooms or their own local contacts. When you can specify a default contact group (also called the Default LDAP Group), the members in this default contact group appear in the endpoint systems contact list. The following illustration shows the relationship between the Polycom CMA system user management entities and those of the dynamically managed endpoints. 14 Polycom, Inc.

21 2 Deployment Process Overview The process for deploying the Polycom Visual Communications experience has three phases: pre-installation planning, installation, and post-installation. The following flow chart illustrates these phases, which are discussed in more detail in this chapter. Polycom, Inc. 15

22 Deploying Visual Communications Administration Guide Pre-installation Planning Phase During the pre-installation planning phase, you will work with the Polycom sales and support teams to perform the tasks described here. During this phase, the Polycom sales and support teams will require assistance from a knowledgeable network administrator from your company. Task 1: Define Desired Visual Communications Experience Your Polycom sales representatives will discuss with you the wide range of visual communication experiences supported by the integrated suite of hardware devices and software applications that Polycom has available. From these options, you will define the specific visual communications experiences you may wish to provide to your end user. Task 2: Design System To create your customized visual communications experience using Polycom products, you will work with Polycom sales and support representatives to: Identify and document the network environment into which the products will be installed The network diagram developed during this phase describes the LAN, WAN, public and private VLAN equipment in the path of the Polycom CMA system and other video network equipment. This network diagram will also include IP addresses, firewall restrictions, ports open or closed on firewalls, and H.323-aware firewalls. At a minimum, this will include the location of endpoints, routers, and firewall restrictions to identify potential problem areas. Select the products required to provide the experience desired Verify that the network infrastructure supports the products selected. This network infrastructure must include a domain name server, a Microsoft SQL database server, and a Microsoft Active Directory server. As part of this network infrastructure, your Microsoft SQL Server 2005 database server and Microsoft Active Directory enterprise server must be deployed on the network. Task 3: Complete Standard Pre-installation Process and Documents Next, working with a Polycom project manager, you will complete the standard pre-installation process and documents that guide the installation process and ensure everything is prepared for deployment. 16 Polycom, Inc.

23 Deployment Process Overview When completing these forms, you should also include plans for the other elements of a typical deployment such as: One or more Polycom RMX or Polycom MGC MCUs A Polycom MGC bridge designated as an ISDN gateway A Polycom VMC system for conference recording and streaming A Polycom VBP system as a firewall/nat The pre-installation documents include: Site survey-- Describes the Polycom CMA and Polycom RMX system configurations, the interoperability with other Polycom products, network details, firewall details, and advanced configuration. Endpoint inventory--the endpoint details to include are the make, model, IP address, ISDN number, and software version. A Polycom CMA system has many features that have been tested and certified on third-party endpoints, so include those endpoints as well. Enterprise directory integration plan--a Polycom CMA system requires specific information for integration with your enterprise directory. Your enterprise directory administrator should be available to provide this information. External DB integration plan--a Polycom CMA system also requires specific information for integration with the Microsoft SQL Server 2005 database. Your database administrator should be available to provide this information. Polycom CMA System Getting Started Guide First Time Setup worksheet. Task 4: Determine Device Management Requirements Determine what methods of device management you want to implement. Automatic provisioning, scheduled provisioning, automatic softupdate, scheduled softupdate. Installation Phase During the installation phase, the Polycom support team will install the integrated suite of Polycom hardware devices and software applications that you choose to implement. It is during this phase that the Polycom support team will require assistance from the administrators of your domain name server, Microsoft SQL database server, and Microsoft Active Directory server. The remaining chapters in this document describe the tasks required during the installation phase. Polycom, Inc. 17

24 Deploying Visual Communications Administration Guide Post-installation Phase After installation, see Chapter 2 of the Polycom CMA Operations Guide for instructions on how to complete the implementation and customization of your Polycom CMA system. 18 Polycom, Inc.

25 3 Polycom CMA System Deployment To provide the fully integrated Polycom Visual Communications experience, perform the Polycom CMA system installation and configuration tasks described in this chapter. Perform these installation tasks as directed in the Polycom CMA System Getting Started Guide and configuration tasks as directed in Chapter 2 of the Polycom CMA System Operations Guide. Task 1: Install and Configure the Polycom CMA System To install and configure the Polycom CMA system 1 Add the DNS service record for the Polycom CMA system to the domain name server. 2 Verify that the same domain name server has entries for both the external database server and the Active Directory server. 3 Install the Polycom CMA system as directed in the Polycom CMA System Getting Started Guide. Leave the Polycom CMA system pointed to its internal database. 4 Connect the system to the network as detailed in the network diagram. 5 If you have an existing internal ReadiManager SE200 database to transfer to this new Polycom CMA system as an internal database (Polycom CMA 4000 systems only): a On the ReadiManager SE200 system, back up the internal database to a USB memory drive. See Chapter 14 of the ReadiManager Operations Guide for more information. b On a local computer, download DBUpgrade.exe (available at from the Polycom CMA 4000 system. c Using the serial console on the Polycom CMA 4000 system server, copy the database files from the USB memory drive to the system. d Shutdown the ReadiManager SE200 system. Polycom, Inc. 19

26 Deploying Visual Communications Administration Guide e Using the serial console on the Polycom CMA 4000 system server, restore the ReadiManager and Logger databases to the system. See Chapter 15 of the Polycom CMA Operations Guide for more information. Note Do not reboot at this time. f g On the local computer, run DBUpgrade.exe to integrate the system with the restored database and clear the former IP address configuration. When prompted for an IP address, enter the IP address of the Polycom CMA 4000 system. Using the serial console on the Polycom CMA 4000 system server, reboot the system. 6 If you have an existing internal ReadiManager SE200 database to transfer to this new Polycom CMA system as an external database: a b c d e f g On the ReadiManager SE200 system, back up the internal database to a USB memory drive. See Chapter 14 of the ReadiManager Operations Guide for more information. Copy the database files from the USB memory drive to the external database server. Shutdown the ReadiManager SE200 system. On the Polycom CMA system, run DBSetup.exe (available at to set up the external database. Restore the ReadiManager and Logger databases onto the external database server according to SQL Server Management Studio procedures or your company s restoration procedures. On the Polycom CMA system, run DBUpgrade.exe (available at to integrate the system with the restored database and clear the former IP address configuration. Go to System Setup > Server Settings > Database and select the Use an external SQL Server database check box. 7 Configure the system for redundancy as required. (Optional for Polycom CMA 5000 systems only.) 8 License the system. 20 Polycom, Inc.

27 Polycom CMA System Deployment Task 2: Integrate the Polycom CMA System into the Network To integrate the Polycom CMA system into the network 1 Configure the connection to the external database. (Optional for Polycom CMA 4000 systems.) 2 Configure the connection to the external LDAP directory. (Optional for Polycom CMA 4000 systems.) Task 3: Set Up Sites, Site Links, Services, and Dial Rules To set up the sites, site links, services and dial rules for your system 1 Add sites. 2 Add site links. 3 Generate multisite links. 4 Create dial plan services. 5 Create dial rules. 6 Create the least call routing tables. Task 4: Set Up Local, Global Address Book, and Enterprise Directory Services To set up local, GAB, and enterprise directory services 1 Import enterprise groups. 2 Add local and GAB users. 3 Add local groups as needed. 4 Add rooms. Polycom, Inc. 21

28 Deploying Visual Communications Administration Guide 22 Polycom, Inc.

29 4 Polycom RMX Installation and Integration To provide the fully integrated Polycom Visual Communications experience, perform the Polycom RMX conferencing system installation and configuration tasks described in this chapter. Perform these installation tasks as directed in the Polycom RMX System Administration Guide. Task 1: Install and Configure the Polycom RMX Conferencing System The next step in deploying the Polycom visual communications experience is to install an Polycom RMX conferencing platform. Polycom RMX 2000 Conferencing Platform The Polycom RMX 2000 conferencing platform is a scalable multimedia IP processing media server optimized for audio and video conferencing. It is a architecture built for high-speed IP networks and designed to support Polycom HDX systems and applications. The Polycom RMX 2000 conferencing platform is the primary conferencing platform for medium to large scale deployments. When integrating the Polycom RMX 2000 conferencing platform with a Polycom CMA system, consider the following: The Polycom RMX 2000 platform is an IP device that supports H.323 protocol The Polycom RMX 2000 platform is an MCU only and does not offer gateway services Polycom RMX 1000 Conferencing Platform The Polycom RMX 1000 system is a high-performance conference platform that provides multipoint video and audio conferencing to small-to-medium sized organizations and enterprise branch offices. The Polycom RMX 1000 Polycom, Inc. 23

30 Deploying Visual Communications Administration Guide system localizes network communications, optimizes traffic efficiency, and minimizes WAN costs. It s a perfect conferencing solution for the edge of the network in large, distributed IP networks. To install a Polycom RMX conferencing platform 1 Install the Polycom RMX system as directed in the Getting Started Guide. for the selected RMX system. 2 Connect the Polycom RMX system to the network as detailed in the network diagram. 3 Configure the Polycom RMX system, but do not configure the Gatekeeper field. Task 2: Integrate the Polycom CMA and RMX Systems To integrate the Polycom CMA and RMX Systems 1 Manually add the Polycom RMX system to the Polycom CMA system as directed in the Polycom CMA Operations Guide. 2 In the Polycom RMX Management application, configure the Gatekeeper field of the Polycom RMX system so that it points to the Polycom CMA system as described in the Polycom RMX Administrator s Guide. Note In the Device > Admin/Monitor View, a Polycom CMA system displays MCUs as two separate Device Types, the MCU type and a GW/MCU device. The GW/MCU designation represents the network interface. Task 3: Create Conferencing Experiences Using Polycom RMX Profiles One of the goals of the Polycom RMX MCU is to simplify the decisions that schedulers must make when scheduling a conference. To achieve this goal, conference parameters that could previously be set on a conference-byconference basis via the conference template are now set at the administrator level either through system flags or named conference profiles. Each profile is a standard set of conference parameters that is referenced by the conference template used when scheduling the conference. System Flags System flags are parameters found in the system.cfg file. Parameters in this file specify such things as: Conference termination settings 24 Polycom, Inc.

31 Polycom RMX Installation and Integration Conference ID minimum and maximum length Auto extension settings Polycom RMX Profiles Profiles are configuration files that reside on the Polycom RMX. Conferences that use an Polycom RMX device must specify a profile, because the Polycom RMX device uses the conference parameters and values from this profile to initiate and manage the conference rather than values specified in a conference template. Parameters in the profile specify: General information such as line rate, encryption, auto termination, and H.239 settings Video settings such as mode (presentation or lecture) and layout IVR settings So to create different video conferencing experiences, create different Polycom RMX profiles that the scheduler can select when scheduling a conference. Some Profile Rules When multiple Polycom RMX bridges are registered to a single Polycom CMA system: Define one or more common profiles on each Polycom RMX device registered to a single Polycom CMA system using the same profile name and same profile parameter values. Associate only common profiles with conference templates in the Polycom CMA system to ensure that only common profiles may be scheduled for conferences that may be hosted on an Polycom RMX bridge. Ensure that for Any MCU templates the conference template parameters are compatible with the specified Polycom RMX profile. Miscellaneous All Polycom CMA system scheduled conferences for Polycom RMX devices require a conference password for authentication of attendees. The conference password must be 4-digit number. The Polycom CMA system assigns a conference password, but advanced schedulers can modify it as desired. The conference password is provided to all conference attendees in the conference notification . This same conference password will also be assigned to Polycom MGC conferences as the conference alias. The Polycom RMX has conference profiles that determine most conference parameter values rather than relying on the conference template assigned during scheduling. Within the Polycom CMA system, a single Polycom RMX unit within a single chassis is presented as two separate device types: Polycom, Inc. 25

32 Deploying Visual Communications Administration Guide The Polycom RMX control unit is shown as an RMX device type. The Polycom RMX IP Service for each installed IP Blade is shown as a GW/MCU device type. The Polycom RMX must be registered with the gatekeeper before it can be added to Polycom CMA system. To create different conferencing experiences, create different Polycom RMX profiles >> In the RMX Management application, create a profile for each unique conference experience that you wish to make available to the end-user as described in the Polycom RMX Administrator s Guide. Task 4: Create Polycom CMA System Conference Templates Conference templates allow you to create various combinations of settings to apply to scheduled conferences. For scheduled conferences that land on Polycom RMX devices, the conference template explicitly identifies the RMX profile which identifies the settings the Polycom RMX should use to control the conference. Remember that the RMX profile may override settings specified when scheduling a conference through the Polycom CMA system. To ensure consistent and expected behavior, make sure to synchronize and lock down RMX profiles and Polycom CMA system conference templates. Task 5: Set Up Automatic and Scheduled Provisioning and Softupdates To set up automatic provisioning and softupdate 1 Create automatic provisioning profiles for endpoints that the Polycom CMA system supports in dynamic management mode. 2 Edit the Site Provisioning Details for each site to add the additional automatic site provisioning details. 3 Set up automatic softupdate profiles for endpoints that the Polycom CMA system supports in dynamic management mode. To set up scheduled provisioning and softupdates 1 Create scheduled provisioning profiles for endpoints that the Polycom CMA system supports in standard mode. 2 Create scheduled softupdate profiles for endpoints that the Polycom CMA system supports in standard mode. 26 Polycom, Inc.

33 Polycom RMX Installation and Integration 3 Schedule provisioning and softupdates for endpoints that the Polycom CMA system supports in standard mode. Polycom, Inc. 27

34 Deploying Visual Communications Administration Guide 28 Polycom, Inc.

35 Endpoint Installation and Integration 5 The Polycom Visual Communications experience requires the Polycom Converged Management Application (CMA ) system and video endpoints that support automatic provisioning, automatic softupdate, and presence. This chapter lists the video endpoints supported by the Polycom CMA system. Polycom CMA Desktop Deployment After you ve installed the Polycom CMA system, you can distribute the Polycom CMA Desktop client application to users. Note You can brand the Polycom CMA Desktop client with your company logo or a design of you choice. See the Polycom CMA System Operations Guide. To deploy the Polycom CMA Desktop client, you can: Copy the link for the Polycom CMA Desktop client from the Polycom CMA system Downloads page into an that you can send to users. See Option 1: Distribute the Polycom CMA Desktop client via an link on page 30. Provide users access to the Polycom CMA system, from which they can download the client. See Option 2: Distribute the Polycom CMA Desktop client via the management system on page 31. Distribute the.msi or.exe installation file as a desktop management or group policy object to a location on client systems and provide directions to users on how to run the executable. See Option 3: Distribute the Polycom CMA Desktop client via a desktop management or group policy object on page 32. Polycom, Inc. 29