Deploying Visual Communications Administration Guide · 2017. 9. 21. · Deploying Visual Communications Administration Guide 6 Polycom, Inc. Task 2: (Optional) Create a DNS Alias

Wave 2 | April 2010 | 3725-00000-003A

Deploying Visual Communications Administration Guide

© 2010 Polycom, Inc. All rights reserved.

Polycom, Inc.4750 Willow RoadPleasanton, CA 94588-2708USA

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.

Trademark Information

Polycom®, the Polycom “Triangles” logo, and the names and marks associated with Polycom’s products are trademarks and/or service marks of Polycom, Inc., and are registered and/or common-law marks in the United States and various other countries.

All other trademarks are the property of their respective owners.

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

Contents

About This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Required Skills . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Polycom Solution Support Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

1 Dynamic Device Management . . . . . . . . . . . . . . . . . . . . . . . 3Dynamic Device Management Supported Configurations . . . . . . . . . . . . . . 3Deploying Dynamic Device Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Configure DNS Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Create a DNS service record for the Polycom CMA system . . . . . . 5(Optional) Create a DNS Alias Record for the Polycom VBP Device 6(Optional) Set Up Split DNS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Configure the Polycom CMA System . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Install and Configure the Polycom CMA System . . . . . . . . . . . . . . . 7Set Up Local, Global Address Book, and Enterprise Directory Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Set Up Automatic Provisioning and Softupdates . . . . . . . . . . . . . . . 8

Install and Configure the Polycom VBP Device (optional) . . . . . . . . . . 9Install and Configure the Polycom VBP Device . . . . . . . . . . . . . . . . 9Add the Polycom VBP Device to the Polycom CMA System . . . . 10Finish the Polycom VBP Device Configuration . . . . . . . . . . . . . . . 11Test the Polycom VBP Device Configuration . . . . . . . . . . . . . . . . . 11

Deploy Polycom HDX Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Deploy Polycom CMA Desktop Clients . . . . . . . . . . . . . . . . . . . . . . . . . 14

Deploy the CMA Desktop Client . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Provide Endpoint Users Information to VBP Users . . . . . . . . . . . . 17

2 Polycom-enabled Unified Communications . . . . . . . . . . . . . 19Polycom-enabled Unified Communications Overview . . . . . . . . . . . . . . . . 20

Polycom RPX Telepresence Interoperability . . . . . . . . . . . . . . . . . . . . . 20Authentication and Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Polycom Products that Enable Unified Communications . . . . . . . . . . . . . . 21Unified Communications Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Point-to-Point Call Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22


ii Polycom, Inc.

Polycom RMX Multipoint Conferencing Use Cases . . . . . . . . . . . 24Polycom HDX MP Option Multipoint Conferencing Use Cases . 25

Deployment Process for Office Communications Server . . . . . . . . . . . . . . 26Prepare for the Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Configure Authentication in Office Communications Server . . . 27Add Conference Rooms with Polycom HDX Systems to Active Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Enable Conference Rooms in Office Communications Server . . . 28Add Contacts to the Conference Room Local Address Book . . . . 28Configure the Office Communications Server Server Pool Encryption Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Deployment Process for Polycom HDX Systems . . . . . . . . . . . . . . . . . . . . . 31Register Polycom HDX Systems with the Office Communications Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Configure the Polycom HDX System LAN Properties . . . . . . . . . 33Configure the Global Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Configure Display Options for Contact List . . . . . . . . . . . . . . . . . . 34Configure AES Encryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Test Your Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Deployment Process for Polycom RMX Systems . . . . . . . . . . . . . . . . . . . . . 37Deployment Process for Polycom DMA System . . . . . . . . . . . . . . . . . . . . . . 38

Set the Routing for the Polycom DMA 7000 System . . . . . . . . . . . 38Create a Security Certificate for the Polycom DMA 7000 System 39

Set Up Numerical Dialing to Virtual Meeting Rooms . . . . . . . . . . . . . . . . . 41

3 Polycom® Conferencing for Microsoft® Outlook® . . . . . . . . . . . . 47Polycom Products that Enable Polycom Conferencing for Outlook . . . . . 48Microsoft Products that Enable Polycom Conferencing for Outlook . . . . 49Polycom Conferencing for Outlook User Scenarios . . . . . . . . . . . . . . . . . . . 49Deploying Polycom Conferencing for Outlook . . . . . . . . . . . . . . . . . . . . . . 51

Configure DNS Entries Polycom Conferencing for Outlook . . . . . . . . 51Enable Remote Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Configure the Polycom the Infrastructure Mailbox and Devices . . . . 54

Create the Polycom Infrastructure Account and Mailbox . . . . . . 55Configure Microsoft Exchange Integration with Polycom RMX Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Configure Calendaring Settings for Polycom DMA System . . . . . 58Configure Calendaring Settings for Polycom RSS System . . . . . . 59

Configure Mailboxes for Room-based HDX Systems . . . . . . . . . . . . . . 60Option 1: Enable the user account for the room mailbox . . . . . . . 62Enable the user account associated with the room mailbox . . . . . 62Modify the room mailbox settings . . . . . . . . . . . . . . . . . . . . . . . . . . 62Option 2: Use a Service Account with a Single Room Mailbox . . 64Create the service account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Contents

Polycom, Inc. iii

Grant the service account the permission to manage the Room Mailbox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64Option 3: Use a Single Service Account for Multiple Room Mailboxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Configure Mailboxes for Polycom HDX Desktop Systems . . . . . . . . . 67Configure Polycom HDX System Calendaring Settings . . . . . . . . . . . . 68(Optional) Configure Polycom CMA System Automatic Provisioning of Calendaring Service Settings on Polycom HDX systems . . . . . . . . . . . 72Configure and Install the Polycom Conferencing Add-In . . . . . . . . . . 72

Configure Polycom Conferencing Add-in Preferences For Installation to Client PCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72Install Polycom Conferencing Add-in for Outlook to Client PCs 73Deploy Customization Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73Test Polycom Conferencing for Outlook Deployment . . . . . . . . . 73

A Polycom HDX System Configuration Files . . . . . . . . . . . . . . 75

B Exchange Calendar Polling Information . . . . . . . . . . . . . . . 77Polycom HDX System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77Polycom DMA System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77Polycom RMX System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77Polycom RSS System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

C Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79


iv Polycom, Inc.

Polycom, Inc. 1

About This Guide

This guide describes how to deploy the Polycom® Unified Communications experience—specifically the Polycom products that enable the experience.

Because this document’s primary purpose is to describe a process, it tells you what to do and when to do it for the products deployed in your environment. Please refer to the product documentation for the appropriate Polycom product for information on why or how to do something. You can find Polycom product documentation online at http://www.polycom.com/support.

Required SkillsDeploying 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 Solution Support ServicesPolycom Implementation and Maintenance services provide support for Polycom solution components only. Additional services for supported third-party Unified Communications (UC) environments integrated with Polycom solutions are available from Polycom Global Services, and its certified Partners, to help customers successfully design, deploy, optimize and manage Polycom visual communication within their third-party UC

http://www.polycom.com/support

http://www.polycom.com/support


2 Polycom, Inc.

environments. UC Professional Services for Microsoft Integration is mandatory for Polycom Conferencing for Microsoft Outlook and Microsoft Office Communications Server integrations.

Please see http://www.polycom.com/services/professional_services/index.html or contact your local Polycom representative for more information.

http://www.polycom.com/services/professional_services/index.html

Polycom, Inc. 3

1Dynamic Device Management

You can configure your video conferencing system for dynamic device management (include automatic provisioning, automatic softupdates, and presence) of some Polycom endpoints. This chapter describes how to implement dynamic device management.

This chapter includes the following sections:

• “Dynamic Device Management Supported Configurations” on page 3

• “Deploying Dynamic Device Management” on page 4

Dynamic Device Management Supported ConfigurationsTo implement dynamic device management, you must have a Polycom CMA system and several video endpoints. The endpoints that can be dynamically managed include:

• Polycom CMA Desktop clients

• Polycom HDX systems

Figure 1-1 shows a basic network diagram for dynamic device management. Note that a Polycom VBP device with Access Proxy enabled is optional in this configuration. Figure 1-2 shows a network diagram that includes a Polycom VBP device with Access Proxy enabled.


4 Polycom, Inc.

Figure 1-1 Architecture for Dynamic Device Management without a Firewall Device

Figure 1-2 Architecture for Dynamic Device Management with a Firewall Device

Deploying Dynamic Device ManagementDynamic device management allows for automatic provisioning and updating of some Polycom endpoints.

Complete the following tasks to deploy dynamic device management.

• “Configure DNS Records” on page 5

• “Configure the Polycom CMA System” on page 7

• “Install and Configure the Polycom VBP Device (optional)” on page 9

• “Deploy Polycom HDX Systems” on page 12

• “Deploy Polycom CMA Desktop Clients” on page 14

Dynamic Device Management

Polycom, Inc. 5

Configure DNS RecordsComplete the following tasks to configure DNS records for your deployment.

• “Create a DNS service record for the Polycom CMA system” on page 5

• “(Optional) Create a DNS Alias Record for the Polycom VBP Device” on page 6

• “(Optional) Set Up Split DNS” on page 6

Task 1: Create a DNS service record for the Polycom CMA system You must configure your DNS so that it can resolve queries for the Polycom CMA system by its host name and/or IP address as assigned on the Network page. The DNS should also have entries for your Active Directory server (if different from the DNS) and for the external database server being used by the Polycom CMA system.

To implement dynamic management mode, which enables automatic provisioning, automatic softupdate, and presence, you must add the DNS service record (SRV record) for the Polycom CMA system. The lookup key for this service record is _cmaconfig._tcp. So the record will resemble this:

_cmaconfig._tcp.customerdomain.com 86400 IN SRV 0 443 cma5000.customerdomain.com

For more information about DNS, DNS records, and how DNS works, see Microsoft Technet (http://technet.microsoft.com/en-us/library/cc772774(WS.10).aspx).

http://technet.microsoft.com/en-us/library/cc772774(WS.10).aspx


6 Polycom, Inc.

Task 2: (Optional) Create a DNS Alias Record for the Polycom VBP DeviceIf your deployment includes a Polycom VBP device, you must create a DNS alias record for the Polycom VBP device. This DNS record will be an A (alias) record in the IN (Internet) class for the IP address assigned to Polycom VBP device's Provider-side interface. This alias record allows endpoint systems in the internet space to resolve the Polycom VBP device's DNS name and request secure proxy services to the Polycom CMA system.

The Domain Name zone file for your DNS server will already have a record for your company’s domain. Add the following A record alias to the server host definitions:

<vbp.domain.com.> IN A <VBP_IP_Subscriber_interface>

Task 3: (Optional) Set Up Split DNSFor customers with employees who move between their work and home offices, you may consider implementing a split DNS. A split DNS splits your DNS zone so client systems can use the same host name to access the system from internal and external domains.

Refer to your DNS server documentation to implement a split DNS. Usually it involves editing your DNS zone file to:

• Specify the Polycom CMA system IP address for devices that query for the hostname from within the enterprise.

• Specify the Polycom VBP Subscriber (WAN) side IP address for devices that query for the hostname from outside the enterprise.

This configuration requires a Polycom CMA system and a Polycom VBP device with Access Proxy enabled.


Polycom, Inc. 7

Configure the Polycom CMA SystemComplete the following tasks to install and configure the Polycom CMA system for your deployment.

• “Install and Configure the Polycom CMA System” on page 7

• “Set Up Local, Global Address Book, and Enterprise Directory Services” on page 8

• “Set Up Automatic Provisioning and Softupdates” on page 8

Task 1: Install and Configure the Polycom CMA System

To install and configure the Polycom CMA system

1 If applicable, verify that the same domain controller has entries for both the external Microsoft SQL Server database server and the Microsoft Active Directory server.

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

3 Connect the system to the network as detailed in the network diagram.

4 License the system.

5 (Optional) Configure the connection to the external database.

An external database is required if you are using CMA 5000.

6 (Optional) Configure the connection to the external LDAP directory.

7 (Optional) Configure the system for redundancy as required. Available for Polycom CMA 5000 systems only.

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

9 As needed, set up an alternate gatekeeper and neighbored gatekeepers.

10 As needed, set up the sites, site links, multisite links, services, dial rules, and call routing tables for your system.


8 Polycom, Inc.

Task 2: Set Up Local, Global Address Book, and Enterprise Directory Services

To set up local, Global Address Book, and enterprise directory services

1 Import enterprise groups.

2 Add local and Global Address Book users.

3 Add local groups as needed.

4 Add rooms.

5 Verify User Accounts.

For the Polycom CMA system to automatically provision a dynamically- managed endpoints (Polycom HDX system or Polycom CMA Desktop client), they must have a valid user account associated with them. Therefore, you must verify that the endpoint 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 3: Set Up Automatic Provisioning and Softupdates

To set up automatic provisioning and softupdate on the Polycom CMA system

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.


Polycom, Inc. 9

Install and Configure the Polycom VBP Device (optional)Complete these tasks if your deployment includes a Polycom VBP device.

• “Install and Configure the Polycom VBP Device” on page 9

• “Add the Polycom VBP Device to the Polycom CMA System” on page 10

• “Finish the Polycom VBP Device Configuration” on page 11

• “Test the Polycom VBP Device Configuration” on page 11

Task 1: Install and Configure the Polycom VBP Device

To install and configure the Polycom VBP device network settings

1 Consult the product documentation and install the Polycom VBP device.

2 Log into the Polycom VBP device and configure it as described in the product documentation and according to the requirements for your network design. Do the following:

a Go to the Network page:

» In the Subscriber Interface Settings section, enter the public network IP (WAN) address and subnet mask for the Polycom VBP device. (This is Port #1 on most Polycom VBP devices, but see the hardware guides to verify which interface port is used on your VBP model.)

» In the Provider Interface Settings section, enter the private network IP (LAN) address and subnet mask for the Polycom VBP device. (This is Port #2 on most Polycom VBP devices, consult your hardware guides to verify which interface port is used on your VBP model.) The Polycom CMA system must also be accessible on this network.

» In the Network Settings section, enter the subscriber-side (WAN) upstream router as the Default Gateway and enter the Primary DNS Server, and Secondary DNS Server.

b Go to VoIP ALG > H.323:

» In the Gatekeeper mode section, select WAN/Provider-side gatekeeper mode.

» In the WAN/Provider-side gatekeeper mode settings, enter the IP address of the Polycom CMA system in the WAN/Provider-side GK address.

» In the Stale Time section, enable Delete stale clients and set Stale time to 15.

» In the H.460.18 Support section, enable H.460.18 support and set Keep-alive time to 45 seconds.


10 Polycom, Inc.

c Go to System > Network Information and verify that your network routes are set up.

The Access Proxy must have Routes entered, via the System > Routes page, so that it knows the gateway through which it can reach any required host on the Provider (LAN) side that are not on the same subnet as the Polycom VBP device.

For example, required hosts on the Provider (LAN) side include the Polycom CMA system, any H.323 device, and any computer that is used to manage the Access Proxy.

» eth0 is your subscriber-side interface (This is Port #1 on the Polycom VBP device.)

» eth1 is your provider-side interface (This is Port #2 on the Polycom VBP device.)

» The Gateway (as set on the Network page) must be on the subscriber-side interface. This is the route that gets users to and from the private network.

Task 2: Add the Polycom VBP Device to the Polycom CMA System

To add the Polycom VBP device to the Polycom CMA system

1 Install the Polycom CMA system as directed in the Polycom CMA System Getting Started Guide. We recommend setting the system’s Default Gateway to the network IP of the corporate data firewall/NAT device.

2 Connect the Polycom CMA system to the network as detailed in the network diagram and complete the installation as described in the Polycom CMA System Operations Guide.

3 Log into the Polycom CMA system and go to Network Device > VBPs.

a Add the Polycom VBP device to the Polycom CMA system as described in the Polycom CMA System Operations Guide. Ensure that the Polycom VBP device IP falls into subnet mask range for the system.

b Copy the HTTPS certificate for the Polycom CMA system to the Polycom VBP device as described in the Polycom CMA System Operations Guide.

4 Go to Admin > Dial Plan and Sites > Sites.

a Verify that the provider-side IP address subnet for the Polycom VBP device is not part of a defined site; so that it falls within the Internet VPN definition. To do this, select each site, click Edit, and then view the Subnets tab.

OR


Polycom, Inc. 11

Add a site with a limited subnet specifically for the Polycom VBP device. This allows you to better control devices within the subnet. For details about adding a site, see the Polycom CMA System Operations Guide.

b If your configuration includes remote Polycom HDX endpoints, select Edit Site Provisioning Details for the site that includes the Polycom VBP device. In the Firewall Settings, clear Used Fixed Ports and select Enable H.460 Firewall Traversal.

Task 3: Finish the Polycom VBP Device Configuration

To finish the Polycom VBP device configuration

1 On the Polycom VBP device, go to System > Access Proxy and enable these three new access proxies:

— An HTTP proxy, that uses port 443

— An LDAP proxy that uses port 389

— An XMPP proxy that uses port 5222.

For each Access Proxy, select the Polycom VBP device certificate (usually vbpcrt.pem) as the Subscriber Certificate and the Polycom CMA system certificate (also vbpcrt.pem) for the Provider Certificate.

Task 4: Test the Polycom VBP Device Configuration

To test the Polycom VBP device configuration

1 From the Polycom VBP device, you should be able to send an ICMP ping (System > Network Test Tools) to the Polycom CMA system IP and receive a response.

2 From the Polycom VBP device, you should be able to send an ICMP ping to a few LAN endpoints and receive a response.

3 From the Polycom VBP device, you should be able to send an ICMP ping to a public IP and get a response.

Note These settings allow the Polycom HDX endpoints to traverse the firewall, but have no affect on Polycom CMA Desktop traversal.

Notes • These are self-signed, default certificates. You can install signed certificates, if your security team instructs you to do so.

• These default certificates use a different "hash" algorithm for each session, which makes the SSL encryption unique for each Access Proxy connection.


12 Polycom, Inc.

Deploy Polycom HDX SystemsIn dynamic management mode, you can simply install a Polycom HDX system onto the network. The setup wizard for a Polycom HDX system in dynamic management mode is configured to automatically discover the Polycom CMA system via its DNS service record and register with the Polycom CMA system. The endpoint system then prompts the user to complete the system setup. If the user accepts, the endpoint system pulls provisioning and softupdate data from the Polycom CMA system and then restarts to implement the downloaded provisioning data.

For existing Polycom HDX system installations, use the administrator’s interface to point the endpoint at the Polycom CMA system. For more information on this option, see the Administrators Guide for Polycom HDX Systems.

If this automatic provisioning process doesn’t work in your environment, for example in a static IP environment or in some 802.1 networks, you have two options.

• On the Polycom HDX system, go to System > Admin Settings > Global Services > Provisioning Service to enable automatic provisioning with the Polycom CMA system. For more information, see the Administrators Guide for Polycom HDX Systems.

• Create a USB boot device that contains the minimum information required for automatic discovery, provisioning, and softupdate.

To create a USB boot device

1 On a computer, create a /usb_oob/general directory.

2 Use a text editor to create the following .dat files within the /usb_oob/general directory. These files provide the minimum information required for automatic discovery.

— provisionserveraddress.dat should contain just the IP address of the Polycom CMA system, for example 172.60.23.4

Notes • If a Polycom HDX system is running in dynamic management mode, it cannot be simultaneously registered with Office Co mm muni cations Server and the presence service provided by the Polycom CMA system. Polycom HDX systems can obtain presence services from only one source: Office Communications Server or the presence service provided by CMA.

For more information about registering your HDX system with an Office Communications Server or server pool, see “Deployment Process for Polycom HDX Systems” on page 31.

• If you want to disable dynamic management (automatic provisioning) for a Polycom HDX system, you must use the HDX setup wizard, see the Administrators Guide for Polycom HDX Systems for more information.


Polycom, Inc. 13

— ldapuserid.dat should contain just the User ID for the user i.e., his or her network login, for example jsmith

— ldappassword.dat should contain just the password for the user i.e., his or her network password

— userdomain.dat should contain just the domain that includes the Polycom HDX system

3 Copy the /usb_oob/general directory onto a USB storage device.

To use a USB boot device

1 Install the Polycom HDX system as described in the accompanying printed set up guide, but do not turn on the device.

2 Connect the USB boot device to the system’s USB port and turn on the Polycom HDX system.

3 Complete the setup wizard. Do not remove the USB boot device until the system has completed the setup wizard.

Note These files provide the minimum information required for automatic discovery in most situations. Appendix A lists all of the .dat files that the Polycom HDX system can read from the USB device. Depending upon your environment, you may need some of these additional .dat files.


14 Polycom, Inc.

Deploy Polycom CMA Desktop ClientsAfter you’ve installed the Polycom CMA system, you can distribute the Polycom CMA Desktop client application to users.

Complete the following tasks to distribute CMA Desktop clients to users within your deployment.

• “Deploy the CMA Desktop Client” on page 14

• “Provide Endpoint Users Information to VBP Users” on page 17

Task 1: Deploy the CMA Desktop ClientTo deploy the Polycom CMA Desktop client to users, you have the following distribution options:

Option 1: Distribute the Polycom CMA Desktop client via an email link

You can copy the link for the Polycom CMA Desktop client from the Polycom CMA system Downloads page and paste it into an email that you can send to users. To do this:

1 Log into the Polycom CMA system and go to the Downloads page.

2 Copy the Polycom CMA Desktop link (for example, http://10.47.9.136/SoftUpdate/vvl/CMADesktop_4_1_1_1010/CMADesktop.exe), and paste it into the email to users.

3 In the email, instruct users to click the link and run the .exe installation program. Include the IP address of the Polycom CMA system along with usernames and passwords (if required) in the email.

If you integrated with Active Directory, you do not need to include usernames and passwords in your email.

We recommend remote users initially set up the Polycom CMA Desktop client while directly connected to the network. Then when using CMA Desktop remotely through a firewall, they must replace the system

For endpoints on the public network that will be accessing the system through a firewall, include the IP address of the Polycom VBP system rather than the Polycom CMA system.

IMPORTANT • On a Windows XP system, the user installing the Polycom CMA Desktop must sign in with administrative privileges. On a Windows Vista or Windows 7 system, the user installing the Polycom CMA Desktop must sign into the Administrator account.

• The following procedures assumes you have implemented DNS lookup and Windows authentication for single signon.


Polycom, Inc. 15

Option 2: Distribute the Polycom CMA Desktop client via the management system

You can provide users access to the Polycom CMA system, from which they can download the Polycom CMA Desktop client. To do this:

1 Type the IP address of the Polycom CMA system into an email to be sent to users. Include usernames and passwords (if required) in the email.




2 In the email, instruct users to log into the Polycom CMA system, go to the Downloads page, download the Polycom CMA Desktop (shipped version), and run the Polycom CMA Desktop .exe installation program.

Option 3: Distribute the Polycom CMA Desktop client via a .zip file

You can zip the .exe installation file for the Polycom CMA Desktop client and send it in an email to users. To do so:

1 Log into the Polycom CMA system, go to the Downloads page, and click Download for the Polycom CMA Desktop (shipped version).

2 Save the Polycom CMA Desktop client installation file to your local system and zip it.

3 Copy the .zip file and paste it into an email to users.

4 In the email, instruct users to open the .zip file and run the Polycom CMA Desktop .exe installation program. Include the IP address of the Polycom CMA system along with usernames and passwords (if required) in the email.





16 Polycom, Inc.

Option 4: Distribute the Polycom CMA Desktop client via a Silent Install

Using the Microsoft Windows Installer (msiexec.exe) you can distribute the .msi 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. To do this:

1 Log into the Polycom CMA system and go to the Downloads page.

2 Copy the Polycom CMA Desktop link (for example, http://10.47.9.136/SoftUpdate/vvl/CMADesktop_4_1_1_1010/CMADesktop.exe).

3 Open a new browser window and paste the link into the Address field.

4 Edit the Address line, change CMADesktop.exe to Polycom CMA Desktop.msi and press ENTER.

5 In the File Download dialog box, click Save.

6 In the Save As dialog box, browse to the location to which to save the report and click Save.

7 Build a desktop management or group policy object that:

— Writes the .msi installation file to a directory (for example, C:\temp) on the user’s local system.

— Uses the Windows Installer (msiexec) to perform a command line installation of the program. The following is an example of using the installer from the directory where Polycom CMA Desktop.msi resides:

msiexec /qn SBSERVERTYPE=2 SBSERVERADDRESS=<CMA_IP_address> /l* CMA_install.txt /i “Polycom CMA Desktop.msi”

When running the installation from a directory other than the directory where the executable resides, include the full path in the command:

msiexec /qn SBSERVERTYPE=2 SBSERVERADDRESS=<CMA_IP_address> /l* CMA_install.txt /i “c:\temp\Polycom CMA Desktop.msi”

8 In an email to users, include the IP address of the Polycom CMA system along with usernames and passwords (if required) in the email.



Note To install Polycom CMA Desktop silently on a Microsoft Windows XP system, users must have local administrator privileges. On Microsoft Windows Vista or Windows 7 systems they must also specify that the command prompt should run with administrator privileges, even when they are logged in with administrator privileges.


Polycom, Inc. 17


Task 2: Provide Endpoint Users Information to VBP UsersFor endpoint users on the public network that will be accessing the system through a firewall, provide the information they need to access the video conferencing system through the Polycom VBP system. Include the DNS name of the Polycom VBP system (rather than the Polycom CMA system), usernames and passwords (as required), and instructions on how to enter the information at the endpoint.


18 Polycom, Inc.

Polycom, Inc. 19

2Polycom-enabled Unified Communications

This chapter describes how to implement Polycom-enabled unified communications, which integrates Polycom systems with the Microsoft infrastructure for presence-based real-time instant messaging (IM), voice, video, and data communications. It includes instructions for configuring the Microsoft Office Communications Server 2007 components and integrating and configuring the Polycom components required for this solution.


• “Polycom-enabled Unified Communications Overview” on page 20

• “Deployment Process for Office Communications Server” on page 26

• “Deployment Process for Polycom HDX Systems” on page 31

• “Deployment Process for Polycom RMX Systems” on page 37

• “Deployment Process for Polycom DMA System” on page 38

• “Set Up Numerical Dialing to Virtual Meeting Rooms” on page 41

Note This guide does not describe or provide full administration or maintenance processes or procedures for Microsoft Office Communications Server 2007. For any questions or assistance on Microsoft Office Communications Server 2007, see the Microsoft documentation and/or Microsoft Support Services.


20 Polycom, Inc.

Polycom-enabled Unified Communications OverviewPolycom-enabled unified communications includes multiple Polycom products that integrate with Office Communications Server 2007 R2 to provide seamless functionality for Office Communicator users.

This solution makes it simple for users in the Office Communications Server 2007 network:

• To see the presence status of Polycom HDX systems, for example on their Office Communicator 2007 client or on a presence-enabled IP phone. Users of Polycom HDX systems in companion mode can log on via single signon (shared user credential) to access the OCS Contacts, Contact Groups, and directory search options. Also, with the improved QWERTY virtual keyboard support, searching for people is now much easier.

• To launch video calls by clicking on presence-enabled contacts and see the availability status of Polycom video and telepresence solutions.

• To launch on-demand voice, video, and unified (voice and video) conferences that include other standards-based video and voice endpoints using the Polycom RMX 2000™ or 4000 real-time media conferencing platform.

• Logistical support for large scale deployment of Polycom HDX systems in an Office Communications Server environment. The Polycom CMA system provisions the Office Communications Server integration and Polycom Conferencing for Outlook settings, while the Polycom DMA system provides scalable, fault-tolerant multipoint conferencing.

• To launch video calls by clicking links included in meeting invitations provided by the Polycom Conferencing for Outlook Add-in.

With Office Communications Server, the solution supports expanded enterprise environments, enhanced security features, and industry-leading high definition resolution.

Polycom devices connect to Office Communications Server using session initiation protocol (SIP).

Polycom RPX Telepresence InteroperabilityThe Polycom Video Network Operations Center (VNOC) can cascade a Polycom RMX 2000/4000 system that is hosting a Polycom RPX Telepresence conference to a Polycom RMX 2000/4000 system in a Office Communications Server environment. In this case, the VNOC uses its managed Polycom RMX system to link (via H.323) the Telepresence Suite to a meeting room on the Polycom RMX system.

For more information on this configuration, see the Polycom Multipoint Best Practices for Telepresence Deployment Guide.

Polycom-enabled Unified Communications

Polycom, Inc. 21

Authentication and SecurityThe Polycom HDX systems in this solution use NTLM for authentication and Transport Layer Security (TLS) to secure transmissions.

The Polycom RMX systems in this solution should be configured to use TLS to secure transmissions between the RMX and the Office Communications Server.

Within a deployment that includes a Polycom RMX system, calls require that the Polycom HDX system have AES encryption set to Off.

Polycom Products that Enable Unified CommunicationsThe following table describes the products the support or enhance the Polycom integration with Microsoft Office Communications Server 2007 R2.

Product Version Description

Systems

Polycom RMX 2000 or 4000 system

v6.0 Provides MCU conferencing resources for Polycom-enabled Unified Communications.

Polycom DMA 7000 system

v2.0 Virtualizes MCU conferencing resources for Polycom-enabled Unified Communications. Highly recommended for deployments that include two or more Polycom RMX systems.

Polycom CMA 4000 or 5000 system

v5.0 Enables automatic provisioning of Polycom HDX endpoint systems. Recommended for remote management of endpoints.

Polycom RSS v6.0 Enables recording of video-enabled Polycom conferences.

Endpoints

Polycom HDX system v2.6 Video endpoint systems that can be fully integrated into a Microsoft Communications Server 2007 environment.

Polycom CX 100, 200, 300, 700, and 5000

All Voice endpoint systems that can be fully integrated into a Microsoft Communications Server 2007 environment.


22 Polycom, Inc.

Unified Communications ScenariosThe solution described in this document supports Microsoft Office Communications Server 2007 R2 Standard Edition and Enterprise Edition, Expanded Configuration, with or without a third-party hardware load balancer. This document assumes that Enterprise Edition is being used.

The sections below outline the use cases supported by this solution.

Point-to-Point Call Use Cases 1 An Office Communicator user (with or without a Microsoft RoundTable

or Polycom CX5000 device) can:

a See a Polycom HDX system registered with Office Communications Server in the contact list and see its presence status (Available, Busy, or Offline).

b From the contact list, make a video call to the Polycom HDX system, with H.263 video (CIF resolution) and G.711 audio, at up to 30 fps.

c From the contact list, make an audio call to the Polycom HDX system, and then click the camera button and escalate to video.

d Call or video call an ordinary (not Polycom HDX) contact list entry with a Companion Mode Polycom HDX system registered to the same Office Communications Server account. The call rings at both devices (call forking), and the recipient can answer using either device.

e Use a contact list in Microsoft Outlook or Sharepoint to initiate each of the preceding calls (the Exchange or Sharepoint server must have been provisioned with Office Communications Server).

f Call a Polycom CX700 phone user. Have the phone user transfer the call to a Polycom HDX system. Then click the camera button and escalate to video.

2 A Polycom HDX system user (registered with Microsoft Office Communications Server) can:

a See contacts registered with Office Communications Server (including other Polycom HDX systems) in the contact list.

The contact list must have been populated in advance. See “Add Contacts to the Conference Room Local Address Book” on page 28.

b Call an Office Communicator user in the favorites list.

c Call a Polycom HDX system in the favorites list.

Note To support CX phones or numeric dialing from an Office Communicator client, Office Communications Server must have the Enterprise Voice option implemented, and the users must be enabled for enterprise voice. See Microsoft’s Office Communications Server 2007 Enterprise Voice Planning and Deployment Guide.

http://technet.microsoft.com/en-us/library/bb894702.aspx

http://technet.microsoft.com/en-us/library/bb894702.aspx


Polycom, Inc. 23

d Call a Microsoft Office Communicator user with a Companion Mode Polycom HDX system registered to the same Microsoft Office Communications Server account. The call rings at both devices (call forking), and the recipient can answer using either device.

e Call a Microsoft Office Communicator user with a Polycom CX100 or CX200 USB phone, establishing an audio connection with the Polycom CX phone.

f Call a Polycom CX700 phone user, establishing an audio connection with the Polycom CX phone.

3 An Office Communicator user with a Polycom CX100/200 USB phone can use Office Communicator to:

a Call a Polycom HDX system, establishing an audio connection with the Polycom CX phone.

b Place the call on hold and take it off hold.

c Forward calls to a Polycom HDX system.

4 A Polycom CX700 phone user (registered with Office Communications Server) can use its touch screen to:

a Find a Polycom HDX system (registered with Office Communications Server) in the favorites list and see its presence status (Available, Busy, or Offline).

b Call the Polycom HDX system.

c Place the call on hold and take it off hold.

d Transfer a call from another Polycom CX phone to a Polycom HDX system.

e Transfer a call from an Office Communicator user to a Polycom HDX system.

f Forward audio calls to a Polycom HDX system.


24 Polycom, Inc.

Polycom RMX Multipoint Conferencing Use Cases 1 An Office Communicator user (with or without a Microsoft RoundTable

or Polycom CX5000 device) can:

a Make an audio call to the SIP URI of a Polycom RMX meeting room. Then click the camera button and escalate to video (H.263 CIF, up to 30 fps, with G.711 or Siren audio).

The SIP URI is the E.164 address of the meeting room plus the domain name of Office Communications Server. For example:

[email protected]

Or if numeric dialing has been enabled:

755386

b Save the called meeting room (which appears in the Recent Contacts list without presence information) to the contact list or a group folder in it.

c Access a passcode-protected conference by using the Office Communicator keypad to send DTMF tones to the Polycom RMX.

2 An Office Communicator user with a Polycom CX100/200 USB phone can use Office Communicator to:

a Make an audio call to a Polycom RMX meeting room as described in case 1, establishing an audio connection with the Polycom CX phone.

b Place the call on hold and take it off hold.

c Forward calls to a Polycom RMX meeting room.

3 A Polycom CX700 phone user (registered with Office Communications Server) can use its touch screen to:

a Make an audio call to the SIP URI of a Polycom RMX meeting room.

b Save the called meeting room (which appears in the Recent Contacts list without presence information) to the contact list or a group folder in it.

c If the user has a Office Communicator registered to the same account as the phone, save the called meeting room to its contact list.

d Place the call on hold and take it off hold.

e Transfer a call from another Polycom CX phone to a Polycom RMX meeting room.

f Forward calls to a Polycom RMX meeting room.

4 A Polycom HDX system user (registered with Office Communications Server) can:

a Make a video call to the SIP URI of a Polycom RMX meeting room.

b Save the called meeting room to the local address book.


Polycom, Inc. 25

5 A user with an H.323 or ISDN (H.320) video endpoint can make a video call to the dial-in number of a Polycom RMX meeting room.

6 A user with a PSTN phone can make an audio call to the phone number of a Polycom RMX meeting room.

7 A Polycom RMX meeting room user or administrator can dial out to any of the SIP, H.323, ISDN (H.320), and PSTN devices in the preceding items.

Multipoint conferences on the Polycom RMX system support any combination of SIP, H.323, ISDN (H.320), and PSTN participants up to the system’s port capacity.

Polycom HDX MP Option Multipoint Conferencing Use Cases 1 Multiple Office Communicator users (with or without Microsoft

RoundTable or Polycom CX5000 devices) can:

a See a Polycom HDX system with the MP option (and registered with Office Communications Server 2007) in the contact list and see its presence status (Available, Busy, or Offline).

b Make a video call to the Polycom HDX system and join a multipoint conference.

2 Multiple Polycom HDX system users (registered with Office Communications Server) can:

a See a Polycom HDX system with the MP option (and registered with Office Communications Server) in the contact list and see its presence status (Available, Busy, or Offline).

b From the contact list, make a video call to the Polycom HDX system and join a multipoint conference.

3 A Office Communicator user with a Polycom CX100/200 USB phone can use Office Communicator to make an audio call to a Polycom HDX system (as described in Point-to-Point Call Use Cases) and join a multipoint conference.

4 A Polycom CX700 phone user (registered with Office Communications Server 2007) can use its touch screen to make an audio call to a Polycom HDX system (as described in Point-to-Point Call Use Cases) and join a multipoint conference.

5 A user with an H.323 or ISDN (H.320) video endpoint can make a video call to the dial-in number of a Polycom HDX system and join a multipoint conference.

6 A user with a PSTN phone can make an audio call to the phone number of a Polycom HDX system and join a multipoint call.

Multipoint conferences on the Polycom HDX system support any combination of SIP, H.323, ISDN (H.320), and PSTN participants up to the system’s port capacity.


26 Polycom, Inc.

Deployment Process for Office Communications Server This section describes how to configure Office Communications Server as required for this solution. You must perform these tasks in this order:

1 “Prepare for the Implementation” on page 27

2 “Configure Authentication in Office Communications Server” on page 27

3 “Add Conference Rooms with Polycom HDX Systems to Active Directory” on page 27

4 “Enable Conference Rooms in Office Communications Server” on page 28

5 “Add Contacts to the Conference Room Local Address Book” on page 28

6 “Configure the Office Communications Server Server Pool Encryption Setting” on page 30

Note Your Microsoft Office Communicator users should already be properly configured in Microsoft Active Directory and Microsoft Office Communications Server.

See your Microsoft Active Directory and Office Communications Server administrators or the Microsoft web site if you have questions regarding the configuration of Microsoft Active Directory and Office Communications Server 2007.


Polycom, Inc. 27

Task 1: Prepare for the ImplementationBefore beginning, the person deploying this solution must have:

• Prior knowledge and experience with Office Communications Server components.

• Access to Office Communications Server product documentation and relevant software.

• Prior knowledge and experience with the Polycom RMX 2000/4000 and HDX systems.

• Access to Polycom RMX 2000/4000 and HDX systems product documentation and relevant software.

Task 2: Configure Authentication in Office Communications Server The Polycom HDX and RMX 2000/4000 systems support only NTLM authentication, not Kerberos. For this solution, you must enable NTLM in Office Communications Server.

To set authentication correctly in Office Communications Server

1 Navigate to Start > All Programs > Administrative Tools > Office Communications Server 2007 R2 to open the Office Communications Server management console.

2 In the tree, expand Enterprise pools, right-click the server pool entry, and select Properties > Front End Properties.

3 In the Front End Properties dialog box, select the Authentication tab.

4 Set Authentication protocol to either NTLM or Both NTLM and Kerberos. Then click OK.

Task 3: Add Conference Rooms with Polycom HDX Systems to Active Directory In Active Directory, you must first create a conference room user for each conference room that will have a Polycom HDX system. You can use a script, the Active Directory Users and Computers management console, or custom software for this purpose. The procedure below describes adding a conference room user manually in the Active Directory Users and Computers management console.

If your deployment will also include Polycom Conferencing for Outlook, there are additional considerations when creating this user account, see “Configure Mailboxes for Room-based HDX Systems” on page 60.


28 Polycom, Inc.

To add a conference room user to the Active Directory:

1 Go to Start > Run and open the Active Directory Users and Computers console by entering:

dsa.msc

2 In the console tree, select Users > New > User.

3 In the New User wizard, enter the required conference room user information and click Next.

4 Set the user password. We recommend that you also set the Password never expires option.

5 Click Next and then Finish.

6 Repeat for each conference room that has a Polycom HDX system.

Task 4: Enable Conference Rooms in Office Communications Server After adding the conference room users to the Active Directory, you must enable and configure them in Office Communications Server.

To enable a conference room user in Office Communications Server 2007

1 Open the Office Communications Server management console and expand Users list.

2 Right-click the conference user, and select Enable for Communications Server.

3 In the Enable Office Communications Server Users Wizard, select the correct server and click Next.

4 In the Specify Sign-in Name dialog box, select the format used to generate the conference room’s SIP URI and click Next.

5 In the Enable Operation Status dialog box, click Finish.

Task 5: Add Contacts to the Conference Room Local Address BookYou can use the LCSAddContacts script from the Microsoft Office Communications Server 2007 Resource Kit to add a list of contacts to the local address books of conference rooms with Polycom HDX systems.

Note If these conference room users have an expiring password, you must keep track of the users and passwords and make sure to update the accounts as required. We recommend setting the passwords to never expire.


Polycom, Inc. 29

Office Communications Server will provide real-time presence information for these contacts, called buddies in some applications. A Polycom HDX system can have up to 200 such contacts per conference room user.

The script accepts two text files as parameters — a users list file and a file of contacts for the users. If you used the LCSEnableConfigureUsers.wsf script to enable and configure conference room users, you can reuse the users.txt file that it used.

To add a list of contacts to each conference room user

1 Create a users.txt file that specifies the conference room users you enabled and configured in Office Communications Server.

The users file can contain distinguished names or SIP addresses. If it contains the distinguished name of a container or user group, all the users in that container or user group are enabled and configured.

Here are some examples of users file entries:

dn:OU=HdxConfRms,DC=polycom,DC=comdn:CN=WestConf2,CN=Users,DC=eng,DC=polycom,DC=com sip:[email protected]:[email protected]:[email protected]

2 Create a contacts.txt file containing the list of contacts to be added to the conference room users in the users.txt file. The contacts in the file must be active and enabled Microsoft Office Communications Server users.

For each entry in the contacts.txt file, specify the name to display in the contacts list followed by the SIP address of that contact. For example:

JanDuncan sip:[email protected] sip:[email protected] sip:[email protected]…

3 If you have not already, download and install the Office Communications Server 2007 R2 Resource Kit Tools from the following URL:

http://www.microsoft.com/downloads/details.aspx?familyid=9E79A236-C0DF-4A72-ABA6-9A9602A93ED0&displaylang=en

Note Polycom recommends that the Office Communications Server be configured to allow no more than 200 contacts per user (the default setting). The HDX system displays only 200 contacts per user. If the Office Communications Server user has more than 200 contacts, the HDX system will not display them consistently.



30 Polycom, Inc.

4 At a command prompt, navigate to the \wmisamples subdirectory in your resource kit installation. For example, C:\Program Files\Microsoft Office Communications Server 2007 R2\ResKit\wmisamples.

5 Run the script by entering (all on one line):

cscript lcsaddcontacts.wsf /usersFile:users.txt /contactsFile:contacts.txt [/contactsGroup:<contactsGroupName>] [>contactslog.txt]

The optional /contactsGroup parameter lets you specify a group name for the contacts being added. If you omit it, the contacts are added to the default group, All Contacts.

The script writes detailed output to the command console, showing the result of each operation for each user. Optionally, you can use the redirection operator (>), as shown above, to redirect the output to a log file.

Task 6: Configure the Office Communications Server Server Pool Encryption SettingBoth the Microsoft Office Communications Server server pool and the Polycom HDX system need to be configured to support encryption in order for calls to connect with some level of encryption. If both components have encryption turned off, calls connect without encryption. If one component is set to require encryption and the other is not, calls fail to connect, see “Media Encryption Scenarios” on page 35 for more detailed information.

To change the Pool Properties encryption setting


2 In the tree, expand Enterprise pools, right-click the server pool entry, and select Properties > Pool Properties.

3 Change the media encryption level to the level you want to use for your deployment. Polycom recommends setting this level to Support Encryption.

4 Click OK to save your changes.


Polycom, Inc. 31

Deployment Process for Polycom HDX SystemsYour Polycom HDX system should be installed according to standard installation procedures. See the Setting Up the System guide for your model of Polycom HDX system, which describes how to set up the hardware. Then perform the following tasks:

• “Register Polycom HDX Systems with the Office Communications Server” on page 31

• “Configure the Polycom HDX System LAN Properties” on page 33

• “Configure the Global Directory” on page 33

• “Configure Display Options for Contact List” on page 34

• “Configure AES Encryption” on page 35

• “Test Your Deployment” on page 36

Task 1: Register Polycom HDX Systems with the Office Communications ServerIntegration with Office Communications Server allows the Polycom HDX system user to see a list of Office Communications Server contacts, see if the contacts are online, and call them without knowing or remembering their addresses. Contacts appear in the directory and can also be displayed on the home screen.

To configure a Polycom HDX system to register with the Office Communications Server

1 Open a browser window and in the Address field enter the Polycom HDX system IP address or host name.

2 Go to Admin Settings > Network > IP Network and select SIP.

3 Configure these settings in the SIP Settings section of the IP Network screen.


32 Polycom, Inc.

Settings Description

Transport Protocol The protocol the system uses for SIP signaling. The SIP network infrastructure in which your Polycom HDX system is operating determines which protocol is required, so set it to the transport protocol specified for the Office Communications Server—either TLS or TCP.

• TCP provides reliable transport via TCP for SIP signaling.

• TLS provides secure communication of the SIP signaling. TLS is available only when the system is registered with a SIP server that supports TLS. When you choose this setting, the system ignores TCP/UDP port 5060.

User Name Specify the system’s SIP name. This is the SIP URI.

If you leave this field blank, the system’s IP address is the SIP user name along with the domain (@host) designation.

In an Office Communications Server environment, specify users’ name for the conference room created for the Polycom HDX system in “Enable Conference Rooms in Office Communications Server” on page 28.

Password When enabled, allows you to specify and confirm a new password that authenticates the system to the Registrar Server.

SIP Registrar Server

Specify the IP address or DNS name of the SIP Registrar Server.

In an Office Communications Server environment, specify the IP address or DNS name of the Office Communications Server server.

By default for TCP, the SIP signaling is sent to port 5060 on the registrar server. By default for TLS, the SIP signaling is sent to port 5061 on the registrar server.

To specify a different port, add it to the address as shown here:

10.11.12.13:5070

If you leave this field blank, the Proxy Server is used.

Proxy Server Specify the DNS name or IP address of the SIP Proxy Server. If you leave this field blank, the Registrar Server is used. If you leave both fields blank, no Proxy Server is used.

By default for TCP, the SIP signaling is sent to port 5060 on the proxy server. By default for TLS, the SIP signaling is sent to port 5061 on the proxy server.

To specify a different port, add it to the address as shown here:

10.11.12.13:5070


Polycom, Inc. 33

4 Click Update.

Once the Polycom HDX system registers with the Microsoft Office Communications Server 2007, you can continue on to “Configure the Polycom HDX System LAN Properties” on page 33.

Task 2: Configure the Polycom HDX System LAN PropertiesTo register with Office Communications Server, the Polycom HDX system must be accessible via a DNS server for the Office Communications Server and must have a valid domain name setting.

To configure the Polycom HDX system LAN properties


2 Go to Admin Settings > LAN Properties.

3 If needed, enter the Domain Name for the domain to which the Polycom HDX system belongs.

4 If needed, in the DNS Servers field enter the IP address for a DNS that the Polycom HDX system and Office Communications Server have in common.

5 Click Update.

Task 3: Configure the Global DirectoryOnce you’ve enabled SIP and specified the Office Communications Server as your SIP Registrar Server, you must configure the Office Communications Server as your Global Directory Server.

To choose a directory server


2 Go to Admin Settings > Global Services > Directory Servers.

Directory: Microsoft Office Communications Server

Specifies whether the SIP Registrar Server is an Office Communications Server. Enabling this setting activates integration features such as the Microsoft global directory and Office Communicator contact sharing with presence.

Settings Description


34 Polycom, Inc.

3 Enable the Microsoft Office Communications Server option.

A green check mark in the Registration Status field indicates the Polycom HDX system is registered with the Office Communicator Server.

4 Click Update.

Task 4: Configure Display Options for Contact List

To configure the display options for contact list information


2 Go to Admin Settings > Global Services > Directory Servers.

3 In the Microsoft Office Communications Server section of the Directory Servers page, configure these settings:

4 Click Update.

Setting Description

Display Contacts Specifies whether to display your contacts on the contact list home screen and in the directory.

Show My Offline Contacts

Specifies whether to include offline contacts on the contact list home screen or in the directory.


Polycom, Inc. 35

Task 5: Configure AES EncryptionAES encryption is a standard feature on all Polycom HDX systems.

Calls from a Polycom HDX system to a Polycom RMX system using Microsoft Office Communications Server require that the Polycom HDX system have encryption set to Off.


2 Go to Admin Settings > General Settings > Security.

3 In the AES Encryption drop-down menu, select Off.

Media Encryption Scenarios

The following table describes call encryption between Office Communicator users and Polycom HDX systems based on the specified encryption settings for each product:

Office Communications Server Setting

Polycom HDX system setting

Office Communicator calls a Polycom HDX system

Polycom HDX system calls an Office Communicator user

Supported Off Audio-only and video calls are unencrypted.

Audio-only and video calls are unencrypted.

When Available Audio-only and video calls are encrypted.

Audio-only and video calls are encrypted.

If deployment includes an RMX system, the call is disconnected.

Required for All Calls or Required for Video Calls


Both audio-only and audio/video calls are encrypted. If set to Required for Video Calls, analog and ISDN audio calls are not allowed.



36 Polycom, Inc.

Task 6: Test Your Deployment

Required Off The Polycom HDX system answers the call. The call is then disconnected by Office Communicator. The following message is displayed on the Polycom HDX system:

Far site disconnected, please wait. Call cleared.

The Polycom HDX system disconnects the call and displays the following message:

Far Site requires Encryption, please enable encryption on your system.









Off Off Audio-only and video calls are unencrypted.

Audio-only and video calls are unencrypted.




Polycom HDX system rejects the call.

The Polycom HDX system disconnects the call and displays the following message:

Far site does not support encryption, Encryption is required for this call.

Office Communications Server Setting

Polycom HDX system setting

Office Communicator calls a Polycom HDX system

Polycom HDX system calls an Office Communicator user


Polycom, Inc. 37

Deployment Process for Polycom RMX SystemsThe RMX 2000/4000 can host multiple video endpoints in a single conference, as well as host multiple conferences simultaneously. For these reasons, the RMX 2000/4000 is configured as a gateway device rather than a single user in the Office Communications Server.

See Appendix H of the Polycom RMX 2000/4000 Administrator’s Guide for detailed steps on how to deploy a Polycom RMX 2000/4000 system for use with the video conferencing solution.


38 Polycom, Inc.

Deployment Process for Polycom DMA System

Task 1: Set the Routing for the Polycom DMA 7000 System If you’re including a Polycom DMA 7000 system in this solution, perform the following procedure to enable the Polycom DMA system to receive Office Communications Server calls.

To set the Polycom DMA 7000 system as a trusted host with a static route


2 In the tree, expand Enterprise pools, right-click the server pool entry, and select Properties > Front End Properties.

3 In the Front End Properties dialog box, select the Host Authorization tab and click Add.

The Add Authorized Host dialog box is displayed.

4 Select FQDN and enter the fully qualified domain name associated with the Polycom DMA 7000 system’s virtual interface.

5 Select the Throttle As Server and Treat As Authenticated check boxes. Then click OK.

6 In the Front End Properties dialog box, select the Routing tab and click Add.

The Add Static Route dialog box appears.

7 In the Domain field, enter the fully qualified domain name to use for the Polycom DMA 7000 system.

8 To use encrypted SIP signaling, set Transport field to TLS. Then click OK.

Note Always refer to the system by the fully qualified domain name of its virtual interface. The system’s IP addresses should be available only on the DNS server.

Note If you enable TLS security, you must also install a security certificate on the Polycom DMA 7000 system and configure the system to use TLS. See “Create a Security Certificate for the Polycom DMA 7000 System” on page 39.

In addition, you should install security certificates on your Polycom RMX MCUs and configure them to use TLS. See Appendix H of the Polycom RMX 2000/4000 Administrator’s Guide.


Polycom, Inc. 39

The Polycom DMA 7000 system is now set as a trusted host, and calls from an Office Communicator client to a SIP address in the Polycom DMA system’s domain will be routed through that system.

Task 2: Create a Security Certificate for the Polycom DMA 7000 System If your solution includes a Polycom DMA 7000 system and you elected to use TLS transport, you must install a security certificate on the Polycom DMA 7000 system so that Office Communications Server trusts it. This can be accomplished in two ways:

• Purchase and install a certificate from a commercial Trusted Root Certificate Authority (CA) such as VeriSign or Thawte. Use the procedures in the Polycom DMA system’s online help for Certificate Management to create a Certificate Signing Request and to install the certificate(s) received from the CA.

• Request and obtain a certificate from your enterprise CA. You can do this in two ways:

— If your organization permits the submission of certificate requests directly to the enterprise’s CA server, use the Office Communications Server Certificate Wizard. From it, you can then download an export file of the certificate to your PC for later installation on the Polycom DMA system. This procedure is described below.

— If certificate requests must be submitted through the enterprise’s CA team or group, use the procedures in the Polycom DMA system’s online help for Certificate Management to create a Certificate Signing Request and to install the certificate(s) received from the CA team or group.

Note Before you proceed, make certain that:

• You have all the fully qualified domain names (FQDNs) of the system for which you’re creating a certificate. A two-node system has three: one virtual and two physical; a single-node system has two: one virtual and one physical.

• These host names are in the primary DNS server of the environment and resolve correctly to the Polycom DMA system.

If the host information in DNS is wrong, the certificates will not work.


40 Polycom, Inc.

To request a security certificate for the Polycom DMA system in Office Communications Server


2 In the tree, expand Enterprise pools and the server pools list, right-click the pool front end entry, and select Certificate.

The Office Communications Server Certificate Wizard appears.

3 Follow the steps in the wizard, making the following choices:

a Select Send request immediately to an online certification authority.

b Select Mark cert as exportable.

c Set Subject name to the fully-qualified domain name (FQDN) of the Polycom DMA system’s virtual interface.

d Enter the FQDN(s) of the physical interface(s) in the Alternate name field.

e Select a certificate authority from the list, choosing the local Office Communications Server front end entity.

f Skip assignment, selecting Assign certificate later.

g When done, click Finished to close the Wizard.

To export the received security certificate from Office Communications Server to your computer

1 In the Office Communications Server tree, expand Enterprise pools and the server pools list, right-click the pool front end entry, and select Certificate.

The Office Communications Server Certificate Wizard appears.

2 Follow the steps in the wizard, making the following choices:

a Select Export a certificate to a *.pfx file.

b Select the certificate you created for the Polycom DMA system.

c Specify a path and name for the *.pfx file on your computer and select Include all certificates in the certification path if possible.

d Enter a password. Be sure to record what it is.

e Click Finished to download the file and close the wizard.

Once the *.pfx file is on your PC, you can upload it to the Polycom DMA system and install it, using the procedures in the Polycom DMA system’s online help for Certificate Management.


Polycom, Inc. 41

Set Up Numerical Dialing to Virtual Meeting RoomsWhen you enable numerical dialing for a virtual meeting room (VMR) on an RMX or DMA, you:

• Enable HDX or Office Communicator users to dial a number to call into a meeting room rather than a full SIP URI. This greatly simplifies dialing, especially with the HDX remote.

• Enable a common dialing plan for VMRs across Office Communications Server and H.323 infrastructures. This means that a single number can be inserted into a calendar invitation and it will be valid for Office Communications Server endpoints and H.323 endpoints.

Perform the following steps to set up numerical dialing into VMRs in the Office Communications Server infrastructure:

• “Configure the RMX/DMA as a Routable Gateway” on page 41

• “Configure an Office Communications Server Voice Route to the RMX/DMA” on page 42

• “Configure Office Communicator Users for Enterprise Voice” on page 43

You can remove numerical dialing capability at any time and return to enabling Office Communicator or HDX users to dial to meeting rooms using a matching URI, see “To Remove Numeric Dialing Capability” on page 44.

Configure the RMX/DMA as a Routable Gateway

The RMX system (or the DMA system) must be set as a routable voice gateway in the Office Communications Server infrastructure. This does not restrict the RMX system to just voice operation, rather it means that the RMX system or the DMA system can be set as a destination for a voice route in the Office Communications Server infrastructure.

The Office Communications Server infrastructure uses the WMI class MSFT_SIPTrustedAddInServiceSetting to store information for each voice gateway in the infrastructure. Typically, these gateways are Office Communications Server Mediation Servers, but in this case, the RMX or DMA is set as a voice gateway by creating a new instance of the class MSFT_SIPTrustedAddInServiceSetting.

Polycom recommends using the Office Communications Server 2007 R2 Resource Kit Tools to accomplish this.

To set up the RMX/DMA as a Voice Gateway

1 If you have not already, download and install the Office Communications Server 2007 R2 Resource Kit Tools from the following URL:





42 Polycom, Inc.

2 Open a command prompt and navigate to where you installed the Office Communications Server 2007 RS resource kit. For example, C:\Program Files\Microsoft Office Communications Server 2007 R2\ResKit\.

3 Run the following command:

cscript OCSTrustEntry.vbs /action:add /type:trustedservice /fqdn:<your FQDN> /service:MediationServer /port:5061 /version:4 /routable:TRUE

where <your FQDN> is the FQDN of your RMX or DMA system.

The script automatically generates the GUID discover the proper Active Directory container to store the object.

Your RMX system (or DMA system) is now established as a trusted gateway by all Office Communications Server pools in the domain. It appears in the list of voice gateways when you establish a voice route.

4 Ensure that your DMA or RMX is not in the Authorized Hosts list for your Office Communications Server.

The TrustedService object that you just created needs to be the only trusted entry for this particular RMX/DMA. For each Office Communications Server pool, you must do the following:

a From the Office Communications Server management console, navigate to your server pool.

b Right-click the pool name and select Front End Properties. Then select the Host Authorization tab.

c Make sure the same RMX or DMA for which you created an TrustedService instance using the instructions above is not also in the list of authorized hosts. If it is, you MUST delete it. It is necessary to completely remove the entry from the list.

Configure an Office Communications Server Voice Route to the RMX/DMA

The Voice Route to the RMX (or DMA) must be configured in the Office Communications Server.

The Office Communications Server infrastructure enables the establishment of a voice route to a voice gateway. Typically, this means that all SIP INVITEs to phone numbers which match a particular pattern will be routed to a specific gateway. In this example, all INVITEs to numbers which start with 73 will be routed to RMX210 (DNS name rmx210.r13.vsg.local2).

Note It may take up to five minutes for these changes to be replicated from Active Directory to the Office Communications Server repository.


Polycom, Inc. 43

To establish a Voice Route to the RMX/DMA Voice Gateway


2 Right-click Forest. Then select Properties > Voice Properties.

3 Select the Routes tab in the Office Communications Server Voice Properties dialog.

4 Choose Add in the Routes tab.

5 Fill in the information in the Add Route dialog. In this example, the regex expression ^73 causes this route to be applied to all numbers starting with 73.

6 In the Add Route dialog, choose Add to set the destination gateway. The RMX gateway set up in Step 1 above, appears in the drop down list of gateways.

7 In Phone Usages section of the Add Route dialog, select a Phone Usage record for this route.

8 In the Edit Route dialog, click OK to save the route.

9 On the RMX which has been set up as the gateway, create meeting rooms which start with 73 (e.g., 73111). On the Office Communicator or HDX, dial 73111 and verify that the Office Communicator or HDX connects to the meeting room.

Configure Office Communicator Users for Enterprise Voice

Ensure that your Office communicator users are enabled for Enterprise Voice. You do this in the Office Communications Server management console.

To Configure Office Communicator Users for Enterprise Voice


2 Expand the Enterprise pool or Standard Edition server node where your users reside.

3 Expand the pool or server where your users reside, and then click the Users node.

4 In the right pane, right-click one or more users whom you want to configure, and then select Configure users.

5 On the Welcome to the Configure Users Wizard page, click Next.

6 On the Configure User Settings page, click Next.


44 Polycom, Inc.

7 On the Configure Meeting Settings page, click Next.

8 On the Configure User Settings specify meeting policy page, click Next.

9 On the Configure Enterprise Voice page, select Change Enterprise Voice Settings for selected users, and then click Enable Enterprise Voice. Click Next.

10 On the Configure Enterprise Voice Settings and Location Profile page, select Change Enterprise Voice Policy for selected users.

11 Select an Enterprise Voice policy from the list.

12 Select Change location profile for selected users.

13 Select a location profile from the list, and then click Next.

14 On the Ready to Configure Users page, review the settings, and then click Next.

15 On the Configure Operation Status page, verify that the operation succeeded, and then click Finish.

To Remove Numeric Dialing Capability

1 Remove any voice routes to the RMX/DMA which have been defined.

2 Remove the trusted service definition which you created in “To set up the RMX/DMA as a Voice Gateway” on page 41.

a Open a command prompt and navigate to where you installed the Office Communications Server 2007 RS resource kit. For example, C:\Program Files\Microsoft Office Communications Server 2007 R2\ResKit\.

b Run the following command to list each trusted service definition:

cscript OCSTrustEntry.vbs /action:list /type:trustedservice

An example of a returned TrustEntry is shown in Table 2-1.


Polycom, Inc. 45

Table 2-1 Example TrustEntry

c Find the TrustEntry that includes your FQDN and use the value of the name: property in the next step. This is the GUID of the TrustEntry.

d Run the following command:

cscript OCSTrustEntry.vbs /action:remove /type:trustedservice /CN:<GUID>

where <GUID> is the value of the name: property of the TrustEntry you listed in the previous step.

3 Add a Matched URI route to the RMX/DMA by right-clicking the Office Communications Server Pool, selecting Properties > Front End Properties > Route.

4 Add a host authorization for the RMX/DMA by right-clicking the OCS Pool, selecting Properties > Front End Properties > Host Authorization.

TrustEntry[6]: CN={56A93378-FEA9-4EAE-845D-AAF0BD8073C0},CN=Trusted Services,CN=RTC Service,CN=Services,CN=Configuration,DC=ocs2,DC=eng,DC=westminster,DC=polycom,DC=com objectClass: top container msRTCSIP-TrustedService cn: {56A93378-FEA9-4EAE-845D-AAF0BD8073C0} distinguishedName: CN={56A93378-FEA9-4EAE-845D-AAF0BD8073C0},CN=TrustedServices,CN=RTC Service,CN=Services,CN=Configuration,DC=ocs2,DC=eng,DC=westminster,DC=polycom,DC=com instanceType: 4 (0x4) whenCreated: 7/2/2009 8:36:57 PM whenChanged: 7/2/2009 8:36:57 PM name: {56A93378-FEA9-4EAE-845D-AAF0BD8073C0} objectCategory: CN=ms-RTC-SIP-TrustedService,CN=Schema,CN=Configuration,DC=ocs2,DC=eng,DC=westminster,DC=polycom,DC=com dSCorePropagationData: 1/1/1601 msRTCSIP-TrustedServicePort: 5073 (0x13D1) msRTCSIP-TrustedServerFQDN: QAOCS.ocs2.eng.westminster.polycom.com msRTCSIP-TrustedServiceType: Microsoft.Rtc.Applications.Cas msRTCSIP-TrustedServerVersion: 4 (0x4) msRTCSIP-Routable: True msRTCSIP-ExtensionData: TlsTarget=QAOCS.ocs2.eng.westminster.polycom.com


46 Polycom, Inc.

5 Wait about five minutes for Office Communicator to replicate Active Directory settings to its repository so that changes will take effect.

To Set Up Simultaneous Numerical and Matched URI Routing

You can simultaneously set up an RMX/DMA for both numerical and Matched URI dialing. If you want to do this, follow these instructions:

1 Set the RMX/DMA as a trusted service (MediationServer) using the instructions in “To set up the RMX/DMA as a Voice Gateway” on page 41.

2 Set up a matching URI route to the RMX/DMA by right-clicking the OCS Pool, selecting Properties > Front End Properties > Routing Tab.

3 Also set up a voice route to the same RMX/DMA using instructions in “To establish a Voice Route to the RMX/DMA Voice Gateway” on page 43.

Note

You cannot also add this DMA/RMX as an authorized host using the Front End Properties > Host Authorization tab. There can only be one trusted service entry for the RMX/DMA even though there are two different routes to the RMX/DMA (i.e., Matched URI and voice route).

Also, only TLS connections to the DMA/RMX will work, TCP connections will not work.

Polycom, Inc. 47

3Polycom® Conferencing for Microsoft® Outlook®

Polycom Conferencing for Microsoft Outlook, which requires the Polycom Conferencing Add-in for Outlook, offers an integrated and enhanced experience for all of those involved in video conferencing.

• It allows IT departments and video administrators/operators to offer users a simple, familiar procedure for scheduling video- and audio-enabled meetings, which requires less IT support. Thus, it maximizes the use of visual communication assets and their return on investment (ROI).

• It allows conference organizers to use Microsoft Outlook and its usual meeting request workflow to schedule video- and audio-enabled meetings. It also allows conference organizers to include recording and streaming into the conference, when required.

• It allows meeting participants to track their video- and audio-enabled meetings on the same calendar that they track their other meetings. It also allows meeting participants to simply click a link in an email meeting request to join conferences on their associated video or audio endpoint system.


— “Polycom Products that Enable Polycom Conferencing for Outlook” on page 48

— “Microsoft Products that Enable Polycom Conferencing for Outlook” on page 49

— “Polycom Conferencing for Outlook User Scenarios” on page 49

— “Deploying Polycom Conferencing for Outlook” on page 51


48 Polycom, Inc.

Polycom Products that Enable Polycom Conferencing for Outlook

System Version Description

Polycom HDX systems v2.6 Monitor the Microsoft Exchange calendar of the configured account and display on-screen notifications of meetings. Users can join meetings via these notifications.

Polycom RMX 2000 or 4000 systems

v6.0 Monitors the Exchange mailbox for the Polycom Conferencing service and hosts Polycom Conferencing for Outlook conferences. Displays meeting information at the start of a meeting, called the Gathering Phase.

Polycom Conferencing Add-in for Outlook

v1.0 Allows Outlook users to schedule meetings that include video, audio, and recording. Allows invitees to join a video-enabled meeting by clicking a link.

Polycom CMA 4000 or 5000 system

v5.0 Provisions Polycom HDX systems for Polycom Conferencing for Outlook functionality and routes H.323 calls to the appropriate Polycom RMX or DMA system.

Polycom CMA Desktop v5.0 Allows users to join video-enabled meetings by clicking a link in a meeting invitation.

Polycom DMA 7000 system

v2.0 Monitors the Exchange mailbox for the Polycom Conferencing service and determines the appropriate Polycom RMX system to host a given Polycom Conferencing for Outlook conference.

Polycom RSS 4000 system

v6.0 Via a connection from the Polycom RMX system, records Polycom Conferencing for Outlook conferences in H.323 format when selected in the Polycom Conferencing Add-in.

Polycom VBP-S/T system

v9.1.5.1 Enables H.323 Polycom HDX systems to support Polycom Conferencing for Outlook in a remote small office/home office (SOHO) network.

Polycom® Conferencing for Microsoft® Outlook®

Polycom, Inc. 49

Microsoft Products that Enable Polycom Conferencing for Outlook

Polycom Conferencing for Outlook User Scenarios

Primary Polycom Conferencing for Outlook Scenario:

1 Organizer creates a new meeting request via his Outlook client.

2 Organizer adds meeting participants to the To... field in the invitation - these can be people or conference room(s). Optionally conference rooms can be added to the Resource field, depending on the user’s preferred workflow.

3 Organizer sets the time of the meeting; this can be a specific time or a recurring meeting.

4 Organizer clicks the Polycom icon to make the meeting conferencing-enabled.

System Version Description

Microsoft Active Directory

2003 or 2008

Enables account logins and integrates with Microsoft Exchange.

Note that Polycom products currently support only a single-forest Active Directory deployment.

Microsoft Exchange 2007 with SP1

Hosts mailboxes and calendars. SP1 is required for the ‘Manage Full Access Permissions’ function.

Exchange Web Services must be enabled.

Microsoft Office Communications Server

2007 R2 Provides login and instant message functionality for Microsoft Office Communicator clients.

Microsoft Office Communicator

2007 Can join video-enabled meetings by clicking a link in a meeting invitation.

DNS N/A Permits call routing to Polycom RMX and DMA systems and DMA subscription to Exchange for mail notifications.

Microsoft Office 2007 Microsoft Outlook and Microsoft Word® 2007 are required for sending Polycom Conferencing for Outlook invitations. Users of older versions of Microsoft Office can receive invitations.


50 Polycom, Inc.

5 Organizer sends the meeting request.

6 Organizer receives meeting accept/reject notifications from invited participants, conference rooms and the calendaring infrastructure system.

Organizing a Polycom Conferencing for Outlook Meeting

1 Microsoft Outlook users with Exchange accounts and the Polycom Conferencing Add-in for Outlook can:

a Use Outlook and the Conferencing Add-in to create a new Polycom conference with one or more attendees and/or conference rooms.

In this case:

» Conference invitees and conference rooms receive Outlook meeting requests, which they can accept or decline using standard Outlook and Exchange workflows.

» Conference participants receive meeting reminders on their desktops via Outlook, and onscreen on both Room-based and User-based Polycom HDX systems using the Polycom Conferencing for Outlook feature.

b Use Outlook and the Conferencing Add-in to edit or cancel a Polycom Conferencing for Outlook meeting.

This results in a new notification being sent to participants to inform them of the revision or cancellation of the meeting. When the meeting is removed from an Exchange User or Room calendar, the HDX monitoring that account will cease to display the meeting at the next polling cycle, see “Exchange Calendar Polling Information” on page 77.

Optional Polycom Conferencing for Outlook Extensions:

1 Organizer sets an option for the meeting to be recorded. A secondary option after enabling recording is to enable streaming.

2 Organizer may update the meeting time after initial meeting creation.

3 Organizer may cancel the meeting after initial meeting creation.

4 Organizer may invite to the meeting an invitee that does not have a video device.

5 Invitee rejects the meeting request via his Outlook client.


Polycom, Inc. 51

Deploying Polycom Conferencing for OutlookComplete the following tasks to deploy Polycom Conferencing for Outlook:

• “Configure DNS Entries Polycom Conferencing for Outlook” on page 51

• “Enable Remote Users” on page 53

• “Configure the Polycom the Infrastructure Mailbox and Devices” on page 54

• “Configure Mailboxes for Room-based HDX Systems” on page 60

• “Configure Mailboxes for Polycom HDX Desktop Systems” on page 67

• “Configure Polycom HDX System Calendaring Settings” on page 68

• “(Optional) Configure Polycom CMA System Automatic Provisioning of Calendaring Service Settings on Polycom HDX systems” on page 72

• “Configure and Install the Polycom Conferencing Add-In” on page 72

• “Test Polycom Conferencing for Outlook Deployment” on page 73

Configure DNS Entries Polycom Conferencing for OutlookFor a Polycom devices to work correctly in a Polycom Conferencing for Outlook deployment, they must subscribe to the Exchange Server for notifications when meeting invitations are sent to the Polycom Conferencing Mailbox it is monitoring. This registration will only succeed if the DNS server used by Exchange (usually, the nearest Active Directory Domain Controller provides DNS services for an Exchange Server) has an A record that resolves the Fully Qualified Domain Name of the system’s Virtual IP address.


52 Polycom, Inc.

For example, Company A’s DMA has a Virtual IP address of 10.1.1.222 and Virtual System name PolycomDMAVirtual.companya.local.

The DNS server used by Company A’s Exchange Server has an A record resolving 10.1.1.222 to PolycomDMAVirtual.companya.local.

If the DMA system does not receive confirmation of its subscription attempt from the Exchange Server, the DMA dashboard displays ‘Subscription Pending’ as its Exchange integration status. This is a normal status for up to two minutes while the first-time registration process occurs. If the Exchange Server is able to resolve the DMA system’s Virtual IP address as an FQDN but the DMA system still displays the ‘Subscription Pending’ status, there may be a firewall between DMA and the Exchange Server preventing connectivity.


Polycom, Inc. 53

Enable Remote UsersPolycom Conferencing for Outlook supports both H.323 clients (Polycom HDX systems) and Microsoft Office Communicator clients (see “Polycom-enabled Unified Communications” on page 19).

While the Polycom Conferencing for Outlook experience for H.323 and Office Communicator users inside the enterprise network is similar, the experience of remote users is slightly different depending on the deployment. Specifically:

• Polycom HDX system to Office Communications Server calls traversing an Edge Server are not supported. Thus, while it is possible to configure a SOHO Polycom HDX system so that it can view a particular calendar, the function to click a link to join a meeting will not work.

• Polycom HDX system H.323 calls are supported if the SOHO Polycom HDX system is registered to a Polycom VBP-S or VBP-S/T device which proxies the Polycom HDX system’s registration to a Polycom CMA system gatekeeper inside the enterprise network.

To ensure that remote users can create and receive meeting invitations:

Verify the Exchange Server servicing any external connections has Outlook Anywhere enabled:


54 Polycom, Inc.

Configure the Polycom the Infrastructure Mailbox and DevicesPolycom infrastructure devices (Polycom RMX, Polycom DMA, and Polycom RSS) monitor a single Exchange mailbox that is automatically scheduled into Polycom Conferencing for Outlook meetings.

Polycom infrastructure devices respond to meeting invitations sent to this address and provide accept/decline feedback to the meeting organizer.

The Polycom infrastructure account will always accept meeting invitations except when a conflict in Virtual Meeting Room numbers exists. These numbers are randomly generated by the Polycom Conferencing Add-in for Outlook and are unlikely to collide. If this occurs, the meeting organizer must cancel the meeting and send a new invitation. For details on other scenarios that may cause the Polycom DMA system or Polycom RMX system to reject meeting invitations, please see the Administrator Guides for those products.

Complete the following tasks to set up your Polycom Infrastructure Integration

• “Create the Polycom Infrastructure Account and Mailbox” on page 55

• “Configure Microsoft Exchange Integration with Polycom RMX Systems” on page 56

• “Configure Calendaring Settings for Polycom DMA System” on page 58

• “Configure Calendaring Settings for Polycom RSS System” on page 59

Notes • The Polycom infrastructure account’s acceptance of a meeting is not capacity-aware. It is possible to schedule more participants into conferences than the infrastructure can support, so the administrator must carefully plan a deployment to ensure appropriate resources are in place.

• The Polycom Conferencing Add-in for Outlook generates random Virtual Meeting Room (VMR) identification numbers. It does not permit scheduling of static meeting rooms that use the same VMR numbers recurrently.


Polycom, Inc. 55

Task 1: Create the Polycom Infrastructure Account and MailboxIn Microsoft Exchange, create a standard user mailbox and account, using an email address such as [email protected]. Polycom infrastructure devices (Polycom RMX system, Polycom DMA system, and RSS) will monitor this account.

Polycom Infrastructure Mailbox Requirements:

• A standard User Mailbox that is dedicated to Polycom use.

You cannot use a room mailbox for the Polycom infrastructure mailbox. A dedicated mailbox is important because the Polycom DMA system deletes all messages from the Inbox when it checks this mailbox for meeting invitations.

• A password that is set to never expire.

For organizations where a permanent password is not possible, the password for the account will need to be re-entered in each infrastructure device whenever it expires or is changed by the Active Directory administrator.

This e-mail account is automatically included in meetings created Polycom Conferencing for Outlook, see Figure 3-1 for an example of configuring a Polycom infrastructure mailbox.

Figure 3-1 Example of a Polycom infrastructure account.


56 Polycom, Inc.

Task 2: Configure Microsoft Exchange Integration with Polycom RMX SystemsThe Polycom RMX system monitors the Exchange account you configured in “Configure the Polycom the Infrastructure Mailbox and Devices” on page 54.

The Polycom RMX system’s Gathering Phase feature depends on the Polycom RMX system’s ability to directly access the Exchange server mailbox to determine information such as the name of a given meeting, and what attendees are participating.

Polycom RMX 2000/4000 Administrator’s Guide.To configure Exchange integration with a Polycom RMX system:

1 Using a Web browser, connect to the RMX.

2 Select Setup > Exchange Integration Configuration.

The Exchange Integration Configuration dialog displays.

3 Mark the Enable Service check box.

4 Complete the fields listed in Table 3-1.

5 Mark the Accept Appointments check box, if your deployment does not include a DMA system, shown in Figure 3-2.

If your deployment includes a DMA system, leave the Accept Appointments check box unchecked, shown in Figure 3-3. When a DMA system is present, it accepts appointments on behalf of the RMX.

Table 3-1 Configure Exchange integration in the RMX system.

Exchange Web Services Url

Specify the full URL path to the Exchange Web Service, including the Exchange.asmx service on the Exchange server.

Domain This is the logon domain of the user in either NETBIOS or DNS name notation. For example, in an Active Directory domain named companya.local with a NETBIOS name of COMPANYA you could enter either companya.local or COMPANYA.

User Name This is the Active Directory account’s user name only, with no domain information included

Password The password for the user account.

Primary SMTP Mailbox

This must match the Primary SMTP Address for the account in Exchange (one account may have multiple associated SMTP addresses). This is displayed as the Mail field in Active Directory.


Polycom, Inc. 57

Figure 3-2 Example Polycom RMX system and Microsoft Exchange Integration without a DMA system.

Figure 3-3 RMX configuration with Exchange when using a DMA system.

Tip You can use the Microsoft Exchange Management shell to list the full Exchange Web Services URL.

Use a command prompt to navigate to the installation directory of the Microsoft Exchange Management shell, and type:get -WebServicesVirtualDirectory |fl.

The Exchange Web Services URL is included in the returned list.


58 Polycom, Inc.

Task 3: Configure Calendaring Settings for Polycom DMA SystemThe DMA system needs to subscribe to the Exchange Server to receive notifications when meeting invitations are sent. It monitors the Polycom infrastructure account you created, see “Configure the Polycom the Infrastructure Mailbox and Devices” on page 54.

Be sure you have properly configured DNS before continuing, see “Configure DNS Entries Polycom Conferencing for Outlook” on page 51 for more information.

To configure calendar settings for the DMA system:

1 In a Web browser, connect to the DMA system.

2 Go to Configuration > Conference Setup > Calendaring Service.

3 Check the Enable Calendaring Service check box.

4 Specify the login credentials for the system on the Exchange server. Use the Polycom infrastructure account you configured, see “Configure the Polycom the Infrastructure Mailbox and Devices” on page 54.

5 If you have multiple Exchange servers behind a load balancer, under Accept Exchange notifications from these additional IP addresses, add the IP address of each individual Exchange server.

6 Click Update.

A dialog box informs you that the configuration has been updated.

7 Click OK.

Figure 3-4 Example Polycom DMA system and Microsoft Exchange integration.


Polycom, Inc. 59

Task 4: Configure Calendaring Settings for Polycom RSS SystemThe Polycom RSS system needs to subscribe to the Exchange server to receive notifications of which meeting invitations have requested that the meeting be recorded.

It monitors the Polycom infrastructure account you created, see “Configure the Polycom the Infrastructure Mailbox and Devices” on page 54.

To configure calendar settings for a Polycom RSS system:

1 In a Web browser, connect to the RSS system.

2 Go to System Config > Service Setting > Calendar Configuration.

3 Check the Enable Calendar Integration check box.

4 Complete the provided fields, see the RSS documentation for more details.

Figure 3-5 Example Polycom RSS system and Microsoft Exchange integration.


60 Polycom, Inc.

Configure Mailboxes for Room-based HDX SystemsYou need to configure an Exchange room mailbox and an Active Directory account (used to authenticate with Exchange) for each room-based HDX in your deployment.

The Room Mailbox (sometimes referred to as the Resource Mailbox) is scheduled via the Outlook client when users wish to hold a meeting in the room. Scheduling a video-enabled Polycom Conferencing for Outlook conference uses the same workflows as reserving a conference room for a meeting without video. The Polycom HDX system located in the conference room monitors the Exchange calendar of this Room object to view the meetings scheduled for the conference room, both video-enabled and not.

You can configure mailboxes for HDX room systems in three ways, see Table 3-2.

1 Enable the user account associated with the room mailbox.

The enabled Active Directory account can be used to authenticate with Polycom CMA system for automatic provisioning if the same credentials are used for both the Provisioning Service and Calendaring Service configurations in the Polycom HDX system.

2 Associate a service account to a single mailbox and grant that account full manage permissions.

3 Associate a service account to multiple mailboxes and grant that account full manage permissions.

By default, Room Mailboxes are linked to disabled Active Directory accounts. If your company’s policy prohibits enabling the Active Directory accounts linked to Room Mailboxes, see “Option 2: Use a Service Account with a Single Room Mailbox” on page 64 or “Option 3: Use a Single Service Account for Multiple Room Mailboxes” on page 66.

Note In many environments, User and Room accounts are likely to already be configured. However, room mailboxes and accounts associated with a room-based HDX need additional configuration.


Polycom, Inc. 61

Table 3-2 Available features with different HDX room mailbox configurations.

An Exchange mailbox with enabled user account

An Exchange mailbox with a disabled user account managed by a service account

Multiple Exchange mailboxes with disabled user accounts managed by a single service account

Polycom Conferencing for Outlook

Presence (either with CMA or Office Communications Server)

(only with Office Communications Server)

CMA Automatic Provisioning

CMA Softupdate

Note If your environment includes both a Polycom CMA system and Office Communications Server, presence and directory are provided by Office Communications Server.


62 Polycom, Inc.

Option 1: Enable the user account for the room mailboxThis section assumes you have already created the room mailbox.

Task 1: Enable the user account associated with the room mailbox

To enable the user account for a room mailbox:

1 In Active Directory, enable the account associated with the room mailbox.

2 Set the user account password to never expire.

For organizations where a permanent password is not possible, the password for the account will need to be re-entered in each infrastructure device whenever it expires or is changed by the Active Directory administrator.

Task 2: Modify the room mailbox settingsThe Subject and Description information needs to be included in the meeting invitation (some default Exchange configurations hide this information). The Polycom HDX system uses this data to display information and complete calls.

Optionally, you can also add the organizer’s name to the meeting invitation.

You can modify these settings using Microsoft Exchange Powershell or Microsoft Office Web Outlook.

For details on using Microsoft Exchange Powershell, see http://technet.microsoft.com/en-us/library/bb123778(EXCHG.80).aspx

To use Microsoft Exchange Powershell to modify the mailbox settings:

1 View the settings for the Room Mailbox.

Get-MailboxCalendarSettings <ExchangeMailbox> | fl

For example: Get-MailboxCalendarSettings zeusroom | fl

— By default, the DeleteSubject value is set to True. This setting must be set to False.

— By default, the DeleteComments value is set to True. This setting must be set to False.

— By default, the AddOrganizerToSubject value is set to True and will add the organizer's name to the subject line. Changing this setting is optional.

2 Set the Room Mailbox properties (0 configuration equates to False):

Set-MailboxCalendarSettings -id <ExchangeMailbox> -DeleteComments:0 -DeleteSubject:0 -AddOrganizerToSubject:0

http://technet.microsoft.com/en-us/library/bb123778(EXCHG.80).aspx


Polycom, Inc. 63

To use Office Outlook Web Access to Configure the Mailbox Settings:

1 Log in to Outlook Web Access using the Room’s credentials.

2 Click Options.

3 Select Resource Settings from the Options bar and scroll down to Resource Privacy Options.

The two settings highlighted in red correspond to the required Exchange Powershell commands above - the blue setting corresponds to the optional setting.


64 Polycom, Inc.

Option 2: Use a Service Account with a Single Room MailboxThis section assumes you have already created the room mailbox.

If your organization has a requirement to keep room accounts disabled, you can set up an Active Directory user account with rights to manage the Room Mailbox in Exchange.

This configuration results in two accounts in the Microsoft deployment:

• One Primary account that is disabled in Active Directory with an associated Exchange Mailbox.

• One Service account that is enabled in Active Directory without a directly assigned Exchange Mailbox.

Task 1: Create the service accountThis Active Directory account may be named starting with SRV-, or another naming scheme fitting with your organization’s deployment. The configuration is similar to any standard user account, and no Exchange mailbox is directly associated.

To create the service account for your room mailbox:

1 Use Active Directory to create the service account you will use to manage the room mailbox.

Task 2: Grant the service account the permission to manage the Room MailboxYou can do this either with the Exchange Management Console of the Exchange Management Shell.

To Use the Exchange Management Console to grant permission:

1 Navigate to the resource mailbox to which you want to grant permissions.

2 Right-click the mailbox and select Manage Full Access Permission.


Polycom, Inc. 65

Figure 3-6 Select Manage Full Access Permission of the Room Mailbox.

3 In the Manage Full Access Permission dialog box, click Add and add the Active Directory service account to the list.

In Figure 3-7, the SRV-apolloroom is a service account that has no directly assigned Exchange Mailbox, but it is given permission to manage the Room Mailbox assigned to the apolloroom user.

Figure 3-7 Select the service account you created.


66 Polycom, Inc.

To Use the Exchange Management Shell to Grant Permissions:

Run the following Exchange Management Shell command to grant the service account full access permissions for the Room Mailbox:

Add-MailboxPermission -Identity '<conference room primary SMTP address>' -User '<domain>\<hdxActiveDirectoryAccountUserName>' -AccessRights 'FullAccess' –InheritanceType ‘All’

Option 3: Use a Single Service Account for Multiple Room MailboxesYou can use one service account for all Polycom HDX systems in the Polycom Conferencing for Outlook deployment.

The steps for this approach are the same as mentioned in “Option 2: Use a Service Account with a Single Room Mailbox” on page 64, with the exception that you can grant the same service account permission to manage multiple mailboxes.

In Figure 3-8, the SRV-AllHDX-CompanyA service account is being used to manage multiple conference rooms. Only the association between Aphrodite and SRV-AllHDX-CompanyA is shown, but this same association could be duplicated for other rooms. For example, SRV-AllHDX-CompanyA could manage dozens of conference rooms within Company A, such as the Poseidon Room, the Hestia Room, and more.

Figure 3-8 Using a service account for all HDX conference rooms.

Note If you create one service account for multiple room mailboxes, you will not be able to take advantage of presence information, see “Available features with different HDX room mailbox configurations.” on page 61.


Polycom, Inc. 67

Configure Mailboxes for Polycom HDX Desktop Systems Each HDX desktop system in your deployment needs to be configured to use an individual user’s Active Directory account and Exchange Mailbox for authentication with Exchange.

Optionally, the Active Directory account can be used to authenticate with Polycom CMA system for automatic provisioning.

There is no additional Exchange configuration necessary to for user accounts to be integrated with an HDX system.


68 Polycom, Inc.

Configure Polycom HDX System Calendaring SettingsYou must configure calendar settings for each HDX system in your deployment.

When configuring calendar settings for a Polycom HDX, you need to specify the Room Mailbox and the Active Directory user name for the service account that manages the mailbox.

If you are using a Polycom CMA system, these settings can be dynamically managed, see “(Optional) Configure Polycom CMA System Automatic Provisioning of Calendaring Service Settings on Polycom HDX systems” on page 72 instead.

To configure the calendar service on an HDX system:

1 In a Web browser, connect to the HDX system.

2 Go to Admin Settings > Global Services > Calendaring Service.

3 Check the Enable Calendaring Service check box.

4 Complete the fields listed in Table 3-3.

For complete documentation on configuring calendaring settings for an HDX system, see the Administrator’s Guide for Polycom HDX Systems.

Table 3-3 Calendar Settings in the Polycom HDX system.

Server Address

This is the fully qualified domain name (FQDN) of the Microsoft Exchange Client Access Server. If your organization has multiple Client Access Servers behind a network load balancer, then the Exchange Server Address would be the FQDN of the Client Access Servers’ Virtual IP Address.

If required, an IP address can be used in place of an FQDN but Polycom recommends using the same FQDN that is used for Outlook clients.

Domain This is the logon domain of the user in either NETBIOS or DNS name notation. For example, in an Active Directory domain named companya.local with a NETBIOS name of COMPANYA you could enter either companya.local or COMPANYA.

User Name This is the Active Directory account’s user name only, with no domain information included

Password The password for the user account.

Mailbox (Primary SMTP)

This must match the Primary SMTP Address for the account in Exchange (one account may have multiple associated SMTP addresses). This is displayed as the Mail field in Active Directory.


Polycom, Inc. 69

5 Click Update.

Example Calendar Settings

Figure 3-9 shows the configuration using the method described in “Option 1: Enable the user account for the room mailbox” on page 62. The zeusroom Active Directory account is enabled and no service accounts are required. As a User, Dwight’s Active Directory account is enabled as well.

Figure 3-9 Using an enabled user account assigned to a room mailbox.


70 Polycom, Inc.

Figure 3-10 shows the ‘individual service accounts’ strategy discussed in “Option 2: Use a Service Account with a Single Room Mailbox” on page 64. The integration between the apolloroom Mailbox and the SRV-apolloroom service account is reflected in the HDX as below.

Figure 3-10 Using a service account to manage a single mailbox.

Figure 3-11 shows, the ‘shared service account for all HDXs’ strategy discussed in “Option 3: Use a Single Service Account for Multiple Room Mailboxes” on page 66. The integration between the Aphrodite Room and the SRV-AllHDX-Company A service account is shown. Remember that this service account may also be managing other Room Mailboxes simultaneously.

Figure 3-11


Polycom, Inc. 71

Figure 3-12 shows the calendar settings of the Polycom HDX system assigned to user Dwight Schrute, which reside on the LAN inside Company A’s corporate network.

Figure 3-12 User-based Calendar Settings in the Polycom HDX System

Figure 3-13 shows the configuration for a SOHO user. When configuring a remote HDX user, be sure to use a publicly-routable Exchange server address, see Figure 3-13. Microsoft Outlook Anywhere must be enabled, see “Enable Remote Users” on page 53.

Figure 3-13 Calendar configuration for a SOHO User.


72 Polycom, Inc.

(Optional) Configure Polycom CMA System Automatic Provisioning of Calendaring Service Settings on Polycom HDX systems

You can use the Polycom CMA system to automatically provision a Polycom HDX system when using dynamic management mode, see “Deploying Dynamic Device Management” on page 4.

To use the Polycom CMA system to automatically provision a Polycom endpoint system, the endpoint system must use the same credentials (username and password) to access both the Exchange server and the Polycom CMA system. Only then can the Polycom CMA system automatically provision a calendaring service-enabled endpoint system.

See the Polycom CMA System Operations Guide for more information.

Configure and Install the Polycom Conferencing Add-InThe Polycom Conferencing Add-In software and its templates must be installed on each Microsoft Outlook client.

For complete documentation, see the System Administrator Guide for the Polycom Conferencing Add-in for Microsoft Outlook.

Complete the following tasks:

• “Configure Polycom Conferencing Add-in Preferences For Installation to Client PCs” on page 72

• “Install Polycom Conferencing Add-in for Outlook to Client PCs” on page 73

• “Deploy Customization Files” on page 73

• “Test Polycom Conferencing for Outlook Deployment” on page 73

Task 1: Configure Polycom Conferencing Add-in Preferences For Installation to Client PCsAdministrators can configure the client experience of the Polycom Conferencing Add-in before deploying the client to users. For details on how to configure preferences as an administrator, refer to the System Administrator Guide for the Polycom Conferencing Add-in for Microsoft Outlook.

Note You must use an enabled resource account (Room Mailbox) in order to take advantage of CMA Automatic Provisioning, see “Configure Mailboxes for Room-based HDX Systems” on page 60


Polycom, Inc. 73

Task 2: Install Polycom Conferencing Add-in for Outlook to Client PCsThe Conferencing Add-in can be installed in a number of ways, depending on the administrator’s preference. After customizing preferences as described in Task 1:, the administrator can provide the file to users via existing software deployment processes, using a link to a network location where the file resides, by using a software installation program like Microsoft SMS, or by using a Group Policy Object. For specifics regarding your environment’s preferred software delivery method, consult the documentation for your software delivery product.

For an example deployment method using Microsoft Active Directory and Global Policy, refer to the System Administrator Guide for the Polycom Conferencing Add-in for Microsoft Outlook.

Task 3: Deploy Customization FilesAfter the installation described in Task 2:, the customization files created in Task 1: can be deployed to the appropriate folder locations on client PCs. The Add-in must already be installed on the client PC, to ensure these file paths have been created. For an example of one possible deployment method using Microsoft Active Directory and Global Policy, refer to the System Administrator Guide for the Polycom Conferencing Add-in for Microsoft Outlook.

Task 4: Test Polycom Conferencing for Outlook Deployment• Walk through scheduling and joining a meeting.

• For more details on the on-screen experience with an Polycom HDX system, please see the Polycom HDX system documentation.


74 Polycom, Inc.

Polycom, Inc. 75

APolycom HDX System Configuration Files

The following table lists all of the .dat files that the Polycom HDX system can read from the USB boot device.

You can either put these files in a /usb_oob/general directory or in a /usb_oob/<serial_number> directory on a USB storage device.

• Provisionable configuration files in the /usb_oob/general directory are copied to the Polycom HDX system unconditionally.

• Provisionable configuration files in the /usb_oob/<serial_number> directory are copied to Polycom HDX system only when the <serial_number> matches the serial number of the endpoint.

• If the same file exists in both the /usb_oob/general and /usb_oob/<serial_number> directories, the copy in the /usb_oob/<serial_number> directory takes priority.

.dat File Name Description Value Range Content Example

langwithcntry Language and country Text string English/en

connecttomylan Enable or disable LAN interface False, True

lanportspeed LAN speed Auto, 10_Mbps, 100_Mbps, 1000_Mbps

landuplexmode LAN duplex Auto, Full, Half

dot1xenabled Enable or disable 802.1X authentication

False, True

dot1xid 802.1X authentication user id Text string johnsmith

dot1xpwd 802.1X authentication password Text string johnsmithpassword

vlanmode Enable or disable VLAN False, True

vlanid VLAN ID Integer in [2,4094]

100


76 Polycom, Inc.

dhcp_flg Enable or disable DHCP client Client, Off

hostname Host name of the Polycom HDX system

Text string hdx334

userdomain Domain of the user account used to log into the provisioning server

Text string polycom.com

domainname Domain of the Polycom HDX system, which will be set by the network itself if DCHP is provisioned

Text string

ipaddress IP address of the Polycom HDX system

IP address 172.18.1.222

subnetmask Subnet mask of the Polycom HDX system

255.255.255.192

defaultgateway IP address of the default router IP address 172.18.1.65

dnsserver DNS server IP address 172.18.1.15

dnsserver1 Alternate DNS server IP address



provisionserveraddress IP address of the Polycom CMA server

IP address or host name

polycomCMA.polycom.com

ldapuserid LDAP user id Text string johnsmith

ldappassword LDAP password Text string johnsmithpassword

.dat File Name Description Value Range Content Example

Polycom, Inc. 77

BExchange Calendar Polling Information

Polycom HDX SystemWhen actively viewing the endpoint's calendar onscreen, the Polycom HDX system polls the Exchange server for updates every 20 seconds. When viewing any other screen, or when the Polycom HDX system is in standby, polling occurs every five minutes.

Polycom DMA SystemPolycom DMA system uses the Push Notification feature of Exchange Web Services to receive notifications of new or updated calendar events in the Polycom Conferencing Mailbox as they are created. Upon receiving a push notification, Polycom DMA system connects to Exchange to download the meeting details. When doing this, Polycom DMA system processes the new event and also requests a refreshed view of all calendar events occurring in the next 24 hours.

In the absence of these notifications, Polycom DMA system connects to the Exchange server every five minutes to retrieve the number of events scheduled to occur on the current calendar day, which it reports on the Dashboard under Calendaring Service as Meetings scheduled today.

Polycom RMX SystemThe Polycom RMX system polls the Exchange server for updates every 15 seconds. When polling, the RMX considers events two hours in the past and 24 hours into the future.


78 Polycom, Inc.

Polycom RSS SystemThe Polycom RSS system polls the Exchange server every 30 seconds.

Polycom, Inc. 79

CTroubleshooting

No longer able to access the Polycom Conferencing Add-In

It is possible for the Polycom Conferencing Add-In to become disabled. If this occurs, navigate to Help > Disabled Items in Microsoft Outlook and enable the Polycom Conferencing Add-In again.

Polycom HDX systems display conference times but no details

Most likely, the Exchange Powershell commands to change the default Exchange behavior of deleting meeting information after acceptance have not been completed. Review the Exchange Powershell commands in “Modify the room mailbox settings” on page 62 and verify that they have been performed correctly.


80 Polycom, Inc.

Polycom, Inc. 81

Index

Aauthentication

Office Communications Server 27Polycom Unified Communications 21

Ccalendar settings

Polycom DMA system 58Polycom HDX system 68Polycom RMX system 56Polycom RSS system 59

conference room accountsHDX with Office Communications Server 27HDX with Polycom Conferencing for Outlook

60configuration files

Polycom HDX system 75

DDisplay Contacts (setting) 34dynamic device management

deploying 4

Eencryption

Office Communications Server 30Polycom HDX and Office Communications

Server 35Exchange server polling

Polycom DMA system 77Polycom HDX 77RMX system 77RSS system 78

Mmailbox

HDX desktop systems 67

HDX room-based systems 60, 62Polycom infrastructure 54

NNTLM 21

OOffice Communications Server

authentication 27contact display options 34deployment process 26

Ppolling

Exchange calendar 77Polycom CMA Desktop Clients

deploying 14Polycom Conferencing Add-In

configure 72Polycom Conferencing for Outlook

Microsoft products 49Polycom products 48user scenarios 49

Polycom Unified Communicationsproducts that support 21use cases 22

Sservice accounts

Polycom HDX room-based systems 64, 66Show My Offline Contacts (setting) 34

TTLS 21troubleshooting 79


82 Polycom, Inc.

Documents

Deploying Visual Communications Administration Guide · 2017. 9. 21. · Deploying Visual Communications Administration Guide 6 Polycom, Inc. Task 2: (Optional) Create a DNS Alias