Polycom CMA System Deploying Visual Communications Administration Guide

Transcription

1 Polycom CMA System Deploying Visual Communications Administration Guide April B

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 Required Skills Polycom Visual Communications How to Create the Polycom Visual Communications Experience Network Topology Network Requirements Management System Endpoints Conferencing Platform Distributed Media Application System Database Features of the Polycom Visual Communications Experience Seat Capacity and Licensing Management Server Licensing Polycom CMA Desktop Client Licenses Directory Services Enterprise Directory Users Groups Rooms User, Group, and Room Management Authentication Security Device Provisioning Device Softupdate Conference Management Settings Environment with Polycom CMA and Polycom RMX Systems. 13 Environment with Polycom CMA, Polycom DMA, and Polycom RMX Systems Localization Polycom, Inc. 1

4 Deploying Visual Communications Administration Guide 2 Deployment Process Overview Pre-installation Planning Phase Define Desired Visual Communications Experience Design System Complete Standard Pre-installation Process and Documents Determine Device Management Requirements Installation Phase Post-installation Phase Polycom CMA System Deployment Install and Configure the Polycom CMA System Integrate the Polycom CMA System into the Network Set Up Primary, Alternate, and Neighboring Gatekeepers Set Up Sites, Site Links, Services, and Dial Rules Set Up Conference Templates Set Up Local, Global Address Book, and Enterprise Directory Services Polycom DMA Installation and Integration Install and Configure the Polycom DMA Conferencing System. 23 Integrate the Polycom CMA and DMA Systems Create Polycom CMA System Conference Templates Polycom RMX 2000 System Installation and Integration Assess Polycom RMX 2000 Conferencing System Needs Install and Configure the Polycom RMX 2000 Conferencing System 25 Integrate the Polycom CMA and RMX 2000 Systems Create Polycom RMX System Profiles Endpoint Installation and Integration Polycom CMA Desktop Deployment Verify User Accounts Deploy Polycom CMA Desktop Polycom HDX Systems Polycom HDX System Deployment Standard Endpoints Supported Set Up Automatic and Scheduled Provisioning and Softupdates 35 Third-Party Endpoint Support Polycom, Inc.

5 Contents 7 Testing the Deployment A Polycom HDX System Configuration Files B System Security and Port Usage Polycom, Inc. 3

6 Deploying Visual Communications Administration Guide 4 Polycom, Inc.

7 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 may require: 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. 5

8 Deploying Visual Communications Administration Guide 6 Polycom, Inc.

9 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: The Polycom Converged Management Application (CMA ) Desktop client an easy-to-use video and audio conferencing application that lets your users see and hear the people they call on their desktop system. Automatic device provisioning for dynamically-managed Polycom CMA Desktop clients and Polycom HDX systems Scheduled device provisioning for standardly-managed and legacy devices Automatic device softupdates for dynamically-managed Polycom CMA Desktop clients and Polycom HDX systems Scheduled device softupdates for standardly-managed and legacy devices On-demand conferencing using embedded MCUs or external MCUs Conference scheduling via the Polycom CMA system Web Scheduler or the optional Polycom Scheduling Plugins for Microsoft Outlook or IBM Lotus Notes Advanced routing to distribute audio and video calls across multiple media servers (MCUs), creating a single seamless resource pool Gatekeeper, alternate, and neighboring 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 Polycom, Inc. 1

10 Deploying Visual Communications Administration Guide 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 How to Create the Polycom Visual Communications Experience This section describes 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. Network Topology The following diagram shows the network topology for a basic, standard deployment of Polycom hardware platforms and software applications to create the Polycom Visual Communications experience. In this configuration, a Polycom CMA system manages the endpoints and devices within a single private IP address space of an enterprise network. In this case, remote users can access the enterprise video network, but only through a virtual private network (VPN). And only, if in all aspects the VPN is configured such that the endpoint appears to be on the same network as the server. Customers using a VPN for remote access are responsible for ensuring 2 Polycom, Inc.

11 Polycom Visual Communications their VPN provides full access for the client to contact the server. Polycom Global Services cannot provide support for VPN configuration and traffic analysis. Network Requirements To ensure system performance and reliability, Polycom recommends deploying its 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 (Polycom RMX or Polycom MGC devices) 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. Management System The Polycom Visual Communications experience requires the Polycom CMA system as the network gatekeeper and management 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. Endpoints The Polycom Visual Communications experience is supported by Polycom CMA Desktop clients and Polycom HDX endpoint systems operating in dynamic management mode. While your network configuration may include other audio and video endpoints (see Endpoint Installation and Integration on page 27), 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 2000 multimedia conferencing platforms. The Polycom RMX 2000 conferencing platform is a scalable multimedia IP processing media server optimized for high definition audio and video conferencing across enterprise and service provider networks. It is an architecture built for high-speed IP networks and designed to support Polycom, Inc. 3

12 Deploying Visual Communications Administration Guide 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 Implementing a Polycom CMA system with one or more Polycom RMX 2000 bridges enables scheduled multipoint conferencing while implementing a Polycom DMA system with with one or more Polycom RMX 2000 bridges enables ad hoc multipoint conferencing. In an environment where you wish to implement both scheduled and ad hoc conferencing, you should set up two pools of RMX 2000 bridges. This allows the Polycom CMA system to schedule one pool of resources, while the Polycom DMA system has another pool of resources from which to draw. While your network configuration may include one or more Polycom MGC or Polycom RMX 1000 bridges, they don t support the automatic provisioning, automatic softupdate, and presence features. Distributed Media Application System The Polycom DMA system is a multipoint conferencing solution that uses advanced routing policies to distribute audio and video calls among multiple MCUs, creating a single resource pool. The Polycom DMA system acts much like a virtual MCU, greatly simplifying video conferencing resource management and improving efficiency. Note Although it can distribute conferences among a pool of MCUs, the Polycom DMA system doesn t currently support cascading of MCUs. Each conference is limited to the capacity of the MCU on which it resides. Logically, the Polycom DMA system is a cooperative two-node cluster. Both nodes register with the gatekeeper and can accept and process calls. In the Polycom Visual Communications experience, the Polycom CMA system is the gatekeeper. It recognizes that the H.323 gatekeeper registration requests from the DMA nodes are part of a two-node cluster. When both nodes are registered and the systems completely configured, the Polycom CMA system routes calls destined for the Polycom DMA system to the first node that it finds available. If the first node isn t available, it automatically routes the call to the second node. 4 Polycom, Inc.

13 Polycom Visual Communications You may wish to implement both scheduled multipoint conferencing (enabled by a Polycom CMA system) and ad hoc multipoint conferencing (enabled by a Polycom DMA system) using your Polycom RMX 2000 bridges. If so, you should identify two pools of RMX 2000 bridges. To do this, add all of the bridges to the Polycom CMA system, because it will act as the gatekeeper for all of the bridges. However, for those bridges that you wish to reserve for ad hoc conferencing, disable the Available to Schedule option (enabled by default) on the Polycom CMA system. In this initial release, a Polycom CMA system does not provide provisioning, softupdate, monitoring or control for a Polycom DMA system. 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: Service Pack 2 At least 1 gigabyte (GB) of memory (2 GB recommended) At least a 1 gigahertz (GHz) processor (2 GHz recommended) At least 6 GB of disk space (2 GB for each of the databases) in addition to the 1 GB required by the database engine The database size will vary depending on use, reporting levels, log levels etc. If your database size is not set to auto-grow, the 2 GB recommendation is a minimum. Polycom, Inc. 5

14 Deploying Visual Communications Administration Guide 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. 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. 6 Polycom, Inc.

15 Polycom Visual Communications 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 offers two directory services options: An enterprise (LDAP) directory A Global Address Book or global directory service (GDS) These directory services options are exclusive options, but by default the system setting for Include all Active Directory users in the Global Address Book is enabled. However, you will want to disable this feature if you have legacy devices such as VSX, ViewStation, and FX endpoints. These endpoints cannot handle the larger size Global Address Book. See the Polycom CMA System Release Notes for more information about this setting. The Polycom CMA system sets no limits on the number of local or enterprise users in the directory. However, the Global Address Book is limited to the maximum number of device licenses. Enterprise Directory For easier user, group, and room management, we strongly recommend integrating your video conferencing systems with an enterprise directory. 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. 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. Polycom, Inc. 7

16 Deploying Visual Communications Administration Guide 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. The Polycom Visual Communications experience supports only a Microsoft Active Directory implementation of an LDAP directory. Also, the enterprise directory is not changed by the Polycom CMA system or endpoint users. 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 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. For security purposes, when the Polycom CMA system is integrated with an enterprise directory, users defined to the enterprise directory are by default added to the Polycom CMA system without a role. If you wish to have enterprise users assigned a Scheduler role by default, an administrator must configure enable the CMA Access via default profile option on the Security Settings page. Integration with an enterprise directory allows users to log into the Polycom CMA system and immediately begin scheduling dial-in conferences with enterprise users. However, to dial out to enterprise users, they must be associated with devices. 8 Polycom, Inc.

17 Polycom Visual Communications 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. 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. The Polycom CMA system sets a limit of 500 groups. 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. Polycom, Inc. 9

18 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 conferencing platform. The Polycom CMA system sets a limit of 500 rooms in the directory. User, Group, and Room Management The Polycom CMA system manages the following user, group, and room management entities: Name Description Comments Users list Groups list Rooms list Global Address Book System Guest Book 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 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 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. 10 Polycom, Inc.

19 Polycom Visual Communications Name Description Comments Presence service contacts 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. Not listed in the Polycom CMA system interface. Stored in the system database as the XMPP_db file. 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. Authentication The Polycom CMA system and the Polycom CMA Desktop uses NTLM version 1 or 2 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 authenticate endpoint users with NTLM Single Signon technology before they can connect to the system and access Polycom CMA system services, you must enable the Use Integrated Windows Authentication option on the Polycom, Inc. 11

20 Deploying Visual Communications Administration Guide LDAP page. To configure this feature, an Active Directory administrator must enter their AD credentials so that the Polycom CMA system can create a trusted machine account to perform trusted passthrough authentication. Note 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. 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. 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. For more information on device provisioning, see the Polycom CMA System Operations Guide. 12 Polycom, Inc.

21 Polycom Visual Communications 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. For more information on device softupdate, see the Polycom CMA System Operations Guide. Conference Management Settings Depending on the Polycom products you have in your visual communications network, you can standardize and manage conference settings or properties in several different ways. Environment with Polycom CMA and Polycom RMX Systems If you have a Polycom CMA system that is used to schedule conferences on one or more Polycom RMX MCUs, you must: Create RMX profiles with standard conference settings on each of those MCUs. RMX profiles allow you to define a variey of conference types and include parameters such as Bit Rate, Video Layout, Encryption, etc. Create Polycom CMA system conference templates that link to one of the RMX profiles. These templates allow schedulers to create, save, and schedule identical conferences and provide settings that supplement the RMX profile settings. However, note that RMX profile settings can override Polycom CMA system settings. Environment with Polycom CMA, Polycom DMA, and Polycom RMX Systems If you introduce a Polycom DMA system, into an environment with a Polycom CMA system, you must decide which RMX MCUs are dedicated to the Polycom DMA system and which are Available to Schedule by the Polycom CMA system. Polycom, Inc. 13

22 Deploying Visual Communications Administration Guide Conference templates are used to create users conference rooms, which define a user s conference experience. A conference template specifies a set of conference properties, such as the line (bit) rate and video display mode. You can create a Polycom DMA system conference template in two ways: Specify the individual conference properties directly in the Polycom DMA system, creating a standalone template independent of the profiles available on the Polycom RMX 2000 MCUs. Link the template to an RMX profile that exists on some or all of the Polycom RMX 2000 MCUs. 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. 14 Polycom, Inc.

23 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

24 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 includes 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.

25 Deployment Process Overview When completing these forms, you should also include plans for the other elements of a typical deployment such as: A Polycom DMA system to distribute audio and video calls across multiple media servers (MCUs), 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 system configurations, the interoperability with other Polycom products, network details, firewall details, and advanced configuration. The device details to include are the make, model, IP address, ISDN number, alias and software version. Endpoint inventory--the endpoint details to include are the make, model, IP address, ISDN number, alias 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 must implement. Automatic provisioning, scheduled provisioning, automatic softupdate, scheduled softupdate. Polycom, Inc. 17

26 Deploying Visual Communications Administration Guide 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 active 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. 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.

27 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

28 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.

29 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 Primary, Alternate, and Neighboring Gatekeepers To set up the primary, alternate, and neighboring gatekeepers 1 Set primary gatekeeper settings. Be aware that changing the default open registration settings to more restrictive settings may mean that devices cannot automatically register with the gatekeeper and that calls sent through the gatekeeper may be blocked. 2 As required, set up an alternate gatekeeper. 3 Set up neighboring gatekeepers so that the Task 4: 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 5: Set Up Conference Templates To set up conference templates on the Polycom CMA system 1 Assess your t. 2 Add site links. 3 Generate multisite links. Polycom, Inc. 21

30 Deploying Visual Communications Administration Guide Task 6: 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. 22 Polycom, Inc.

31 4 Polycom DMA Installation and Integration To distribute audio and video calls across multiple RMX 2000 media servers (MCUs), you can implement a Polycom DMA system by performing the installation and configuration tasks described in this chapter. Task 1: Install and Configure the Polycom DMA Conferencing System To install a Polycom DMA system 1 Install the Polycom DMA system as directed in the Polycom DMA System Getting Started Guide for the system. 2 Connect the Polycom DMA system to the network as detailed in the network diagram. Task 2: Integrate the Polycom CMA and DMA Systems To integrate the Polycom CMA and DMA Systems 1 Determine the H.323 prefix for the Polycom DMA system. This must be a prefix that is not used by other network devices, endpoints, services, or dial rules within the network. If you are not sure which H.323 prefixes are available: a On the Polycom CMA system, go to Admin > Dial Plan and Sites > Dial Rules and edit each dial rule to identify which prefixes are used for the dial rules. b Go to Admin > Dial Plan and Sites > Services and identify which prefixes are used for the services. c Go to Endpoint > Monitor View and identify which aliases are used for the endpoints. Polycom, Inc. 23

32 Deploying Visual Communications Administration Guide d Go to Network Device > Monitor View and identify which aliases are used for the network devices. 2 Go to Admin > Gatekeeper Settings > Primary Gatekeeper and verify that the gatekeeper registration policy is Allow Registration of All Endpoints. It must be set to this so that the Polycom DMA nodes can register with the Polycom CMA system. Also, if any of the Polycom RMX systems you will be associating with the Polycom DMA system are not registered with the the Polycom CMA system, make sure that Deny calls to/from unregistered endpoints setting is not set. 3 On the Polycom CMA system, go to Admin > Gatekeeper Settings > Alternate Gatekeeper and determine if the Polycom CMA system has an alternate gatekeeper assigned. 4 On the Polycom DMA system, configure signaling as described in the Polycom DMA System Operations Guide, designating the Polycom CMA system as the primary gatekeeper and setting the H.323 prefix and alternate gatekeeper as required. Task 3: Create Polycom CMA System Conference Templates In Chapter 3, Polycom CMA System Deployment, you created Polycom CMA system conference templates, which supplement the Polycom RMX 2000 system profiles. You may also create Polycom DMA system conference templates, but these templates will either invoke a Polycom RMX 2000 system profiles or replace it. 24 Polycom, Inc.

33 5 Polycom RMX 2000 System Installation and Integration To provide the fully integrated Polycom Visual Communications experience, you must install and configure one or more Polycom RMX 2000 conferencing systems as described in this chapter. Task 1: Assess Polycom RMX 2000 Conferencing System Needs Before you begin installing your Polycom RMX 2000 systems, you must assess your scheduled and unscheduled conferencing requirements and determine how to divide your pool of Polycom RMX 2000 systems. Task 2: Install and Configure the Polycom RMX 2000 Conferencing System To install a Polycom RMX 2000 conferencing platform 1 Install the Polycom RMX 2000 system as directed in the Getting Started Guide for the selected RMX 2000 system. 2 Connect the Polycom RMX 2000 system to the network as detailed in the network diagram. 3 Configure the Polycom RMX 2000 system, but do not configure the Gatekeeper field. 4 If you re installing multiple Polycom RMX 2000 system, repeat this procedure for each system you are installing. Polycom, Inc. 25

34 Deploying Visual Communications Administration Guide Task 3: Integrate the Polycom CMA and RMX 2000 Systems To integrate the Polycom CMA and RMX 2000 Systems 1 Manually add the Polycom RMX 2000 system to the Polycom CMA system as directed in the Polycom CMA Operations Guide. 2 If this Polycom RMX 2000 system will be part of the Polycom DMA system pool of RMX systems, in the Capabilities section of the Add Device or Edit Device dialog box, clear the Available to Schedule setting. 3 In the Polycom RMX 2000 Management application, configure the Gatekeeper field of the Polycom RMX 2000 system so that it points to the Polycom CMA system as described in the Polycom RMX 2000 Administrator s Guide. 4 If you re installing multiple Polycom RMX 2000 system, repeat this procedure for each system you are installing. 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 4: Create Polycom RMX System Profiles In Chapter 3, Polycom CMA System Deployment, you created Polycom CMA system conference templates, which supplement the Polycom RMX 2000 system profiles. In Chapter 4, Polycom DMA Installation and Integration, you created Polycom DMA system conference templates, which will either invoke a Polycom RMX 2000 system profiles or replace it. Now you must create the Polycom RMX system profiles 26 Polycom, Inc.

35 Endpoint Installation and Integration 6 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. Task 1: Verify User Accounts Before distributing the Polycom CMA Desktop client to users, verify that the users have accounts on the system. Users are typically added through integration with your enterprise directory, but can be added as local users as well. Task 2: Deploy Polycom CMA Desktop To deploy the Polycom CMA Desktop client to users within a private enterprise network, 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 29. 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 30. Polycom, Inc. 27