Polycom® RealPresence® Resource Manager Operations Guide

OPERATIONS GUIDE
10.1 | April 2017 | 3725-72104-001K1
Polycom® RealPresence® Resource
Manager
Copyright© 2016, Polycom, Inc. All rights reserved. No part of this document may be reproduced, translated into another
language or format, or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the
express written permission of Polycom, Inc.
6001 America Center Drive
San Jose, CA 95002
USA
Trademarks Polycom®, the Polycom logo and the names and marks associated with Polycom 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 property of their respective owners. No portion hereof may be reproduced or transmitted in any
form or by any means, for any purpose other than the recipient's personal use, without the express written permission
of Polycom.
Disclaimer While Polycom uses reasonable efforts to include accurate and up-to-date information in this document,
Polycom makes no warranties or representations as to its accuracy. Polycom assumes no liability or responsibility for
any typographical or other errors or omissions in the content of this document.
Limitation of Liability Polycom and/or its respective suppliers make no representations about the suitability of the
information contained in this document for any purpose. Information is provided "as is" without warranty of any kind and
is subject to change without notice. The entire risk arising out of its use remains with the recipient. In no event shall
Polycom and/or its respective suppliers be liable for any direct, consequential, incidental, special, punitive or other
damages whatsoever (including without limitation, damages for loss of business profits, business interruption, or loss
of business information), even if Polycom has been advised of the possibility of such damages.
End User License Agreement By installing, copying, or otherwise using this product, you acknowledge that you
have read, understand and agree to be bound by the terms and conditions of the End User License Agreement for this
product. The EULA for this product is available on the Polycom Support page for the product.
Patent Information The accompanying product may be protected by one or more U.S. and foreign patents and/or
pending patent applications held by Polycom, Inc.
Open Source Software Used in this Product This product may contain open source software. You may receive
the open source software from Polycom up to three (3) years after the distribution date of the applicable product or
software at a charge not greater than the cost to Polycom of shipping or distributing the software to you. To receive
software information, as well as the open source software code used in this product, contact Polycom by email at
OpenSourceVideo@polycom.com.
Customer Feedback We are striving to improve our documentation quality and we appreciate your feedback. Email
your opinions and comments to DocumentationFeedback@polycom.com.
Polycom Support Visit the Polycom Support Center for End User License Agreements, software downloads,
product documents, product licenses, troubleshooting tips, service requests, and more.
2
Contents
Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Polycom® RealPresence® Resource Manager Overview . . . . . . . . . . . . . . . . . . 30
RealPresence Resource Manager Features and Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . 30
Video Infrastructure Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Video Endpoint and Audio Phone Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Conference Scheduling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Directory Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Session Border Control Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Redundant Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Programmatic Access through API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Working in the RealPresence Resource Manager System . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Log In to the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Field Input Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Filter and Search in a List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Managing Bandwidth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Download Software Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Change a Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Log Out of the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Restart or Shut Down a System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Emergency Shutdown of the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
System Setup Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Adding DNS SRV Record for RealPresence Resource Manager System Services . . . . . . . . 38
Setting Up Network Device Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Configuring Conferencing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Set Up Site Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Set Up Conference Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Set Up Directory Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Configuring the Connection to an External Enterprise Directory . . . . . . . . . . . . . . . . . . . . . . . 40
Setting Up Endpoint Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Polycom, Inc.
3
Contents
Scheduled Management of Endpoints (Polycom and Third-Party) . . . . . . . . . . . . . . . . . . 41
Dynamic Management of Endpoints (Polycom Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Securing the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Configuring Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Distributing Polycom Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Network Device Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Understanding Network Device Management . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Overview of Network Device Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Service Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Service Group Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Supported Network Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Viewing Network Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Managing Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
View Network Device Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Add an Instance by IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Edit an Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
View an Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Delete an Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Managing Service Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Configuring Common Settings for a Service Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Configure Time Settings for a Service Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Configure SNMP Settings for a Service Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Integrate a Service Group with Enterprise Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Manage a Network Device within a Service Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Managing Service Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Create a Service Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Edit Service Group Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Delete Service Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Service Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Service Integration with a RealPresence DMA System . . . . . . . . . . . . . . . . . . . . 59
Integration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Dedicated User Account for Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Polycom, Inc.
4
Contents
NTP Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
MCU Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Conference Types Supported By the RealPresence DMA system . . . . . . . . . . . . . . . . . . 60
RealPresence DMA Conference Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Multi-Tenancy Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Considerations for Site Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Scheduling Capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Integrating with a RealPresence DMA Supercluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Integrating with a RealPresence DMA system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Create a Dedicated User Account on the RealPresence DMA system . . . . . . . . . . . . . . . 62
Add the RealPresence DMA system to RealPresence Resource Manager system . . . . . 63
Configure the Default Territory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Managing a RealPresence DMA System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Edit a RealPresence DMA system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Change the Service Integration for a RealPresence DMA system . . . . . . . . . . . . . . . . . . 65
Working with RealPresence DMA Pool Orders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
View Details of a RealPresence DMA system Pool Order . . . . . . . . . . . . . . . . . . . . . . . . 66
Associate a RealPresence DMA system Pool Order with an Area . . . . . . . . . . . . . . . . . . 67
Working with Endpoints Synchronized from a RealPresence DMA System . . . . . . . . . . . . . . 67
Unique H.323 Aliases Required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Monitor RealPresence DMA-Synchronized Endpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Schedule RealPresence DMA-Synchronized Endpoints in Conferences . . . . . . . . . . . . . 69
Licensing RealPresence DMA-Synchronized H.323 Endpoints . . . . . . . . . . . . . . . . . . . . 69
Threshold for Stopping Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Threshold for Deleting Inactive Synchronized H.323 Endpoints . . . . . . . . . . . . . . . . . 70
RealPresence DMA Conference Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
RealPresence DMA System Conference Templates for Multi-Tenancy . . . . . . . . . . . . . . 70
Establishing Naming Conventions for RealPresence DMA System Templates . . . . . . . . 70
Anytime Conference Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Considerations for Anytime Conference Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Configuring Auto-Terminate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Initiating Conference Dial-out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Service Integration with Session Border Controllers . . . . . . . . . . . . . . . . . . . . . 73
Supported Session Border Controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Managing Polycom VBP Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Add a Polycom VBP Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Edit a Polycom VBP Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Delete a Polycom VBP Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Identify Endpoints Using the Polycom VBP Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Polycom, Inc.
5
Contents
Managing a Polycom RealPresence Access Director System . . . . . . . . . . . . . . . . . . . . . . . . 75
Manually Add a RealPresence Access Director System . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Managing SBC Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Add an SBC Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Edit an SBC Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Delete an SBC Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Identify Endpoints Using the SBC Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Service Integration with Bridges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
View Device Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Add an MCU Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Conference Scheduling Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Edit an MCU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Delete an MCU Bridge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
View Bridge Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
View MCU Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
View MCU Conferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
View MCU Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
View MCU Meeting Rooms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
View MCU Entry Queues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
View Bridge Gateway Conferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
License Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
License Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
License Management Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Managing License for RealPresence Web Suite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Managing License for a RealPresence DMA Supercluster . . . . . . . . . . . . . . . . . . . . . . . . 89
Enable Licensing for a Network Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Online and Offline Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Allocate Licenses for Polycom RealPresence Platform Components . . . . . . . . . . . . . . . . . . . 90
Reset Allocated Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Clean Unused Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Update the Licenses of Polycom RealPresence Platform Components . . . . . . . . . . . . . . . . . 91
Configure Conferencing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Setting Up Site Topology
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Site Topology Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Managing Sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Polycom, Inc.
6
Contents
View the Graphical Site Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
View the Sites List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Add a Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
View Site Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Assign Locations to a Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Edit Site Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Delete a Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Managing Site Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
View the Site Links List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Add a Site Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Edit a Site Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Delete a Site Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Managing Site-to-Site Exclusions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
View the Site-to-Site Exclusion List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Add a Site-to-Site Exclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Edit a Site-to-Site Exclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Delete a Site-to-Site Exclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Territories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
View the Territory List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Add a Territory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Edit a Territory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Delete a Territory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Network Clouds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Multi-tenancy Considerations for Network Clouds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
View the List of Network Clouds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Add a Network Cloud . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Edit a Network Cloud . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Delete a Network Cloud . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Setting Up the Global Address Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
View the Global Address Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Enable or Disable GAB Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Set or Change the GAB Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Using Multiple Address Books . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Multiple Address Books Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Using Multiple Address Books . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Implement Multiple Address Books . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Address Book Considerations for Multi-Tenancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
View the Address Book List and Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Polycom, Inc.
7
Contents
Add an Address Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Edit an Address Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Assign Address Books to User Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Delete an Address Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Change Address Book Priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Set the Default Address Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Copy an Address Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Direct Conference Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Direct Conference Templates Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Standalone Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Considerations for Polycom MGC Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Linked Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Direct Conference Template Considerations for Multi-Tenancy . . . . . . . . . . . . . . . . . . . 123
Direct Conference Template Best Practices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
View the Direct Conference Templates List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Add a Direct Conference Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Edit a Direct Conference Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Delete a Direct Conference Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Configuring Conference Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Conference Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Specify Conference Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Disable Conference Time Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Automatically Include Conference Creator in Conference . . . . . . . . . . . . . . . . . . . . . . . 128
Overbook Dial-in Participants . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Set the Conference and Chairperson Passcode Length . . . . . . . . . . . . . . . . . . . . . . . . . 128
Customizing Text to Email Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Add Customized Text to Conference Email Notifications . . . . . . . . . . . . . . . . . . . . . . . . 129
Edit Customized Text in Email Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Conference Scheduling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Conference Scheduling Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Log into the system web interfac . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Conference Scheduler Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Scheduling Participants . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Scheduling Bridges and DMA Pool Orders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Conference Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
MCU Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Polycom, Inc.
8
Contents
Bridge Scheduling and Reassignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
DMA Pool Orders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Room ID Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Limitations When Scheduling a Conference on a DMA Pool Order . . . . . . . . . . . . . 136
Recurring Conferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Anytime Conferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Conference Scheduling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Schedule a Conference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Configure Advanced Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Schedule an Anytime Conference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
Copy an Existing Conference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
Edit a Future Conference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
Edit a Participant’s Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
View Scheduling Information for a Conference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
Managing Conferences and Participants . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Working with Conferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
View All Conferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Filter the Conference List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Delete a Conference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Export a List of Conferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Managing Active Conferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Manage an Active Conference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Write Conference Notes During a Conference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Add Additional Participants to an Active Conference . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Add Guests to an Active Conference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Add a Room to an Active Conference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
View a Participant’s Video During a Conference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Join an Active Conference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
Add a Participant from a Favorites List to an Active Conference . . . . . . . . . . . . . . . . . . 154
Terminate an Active Conference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Managing Participants within an Active Conference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Add or Save a Participant to a Favorites List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Manage a Participant’s Endpoint During a Conference . . . . . . . . . . . . . . . . . . . . . . . . . 155
View a Participant’s Details During a Conference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
Managing the Guest Book and Favorites Lists . . . . . . . . . . . . . . . . . . . . . . . . . 159
Managing the Guest Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
View the Guest Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
Polycom, Inc.
9
Contents
Add a Guest to the System Guest Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
Edit a Guest in the System Guest Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Delete a Guest from the System Guest Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Managing Favorites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Add a Favorites List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Edit a Favorites List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Delete a Favorites List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
Conference and Participant Details Reference . . . . . . . . . . . . . . . . . . . . . . . . . 165
Conference Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Conference Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Conference Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
Bridge (MCU) Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
Participants . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
Participant Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
Endpoint Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Managing Endpoints and Peripherals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
Endpoint Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
Scheduled Management of Video Endpoints (Polycom and Third-Party) . . . . . . . . . . . . 172
Password Requirements for Scheduled Management . . . . . . . . . . . . . . . . . . . . . . . 173
Dynamic Management of Video Endpoints (Polycom Only) . . . . . . . . . . . . . . . . . . . . . . 173
Presence Service for Dynamically-Managed Endpoints . . . . . . . . . . . . . . . . . . . . . . 173
Dynamic Management of Phones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
Management of H.323 Endpoints Synchronized from a RealPresence DMA System . . 174
Calendar Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
Configure the Calendar Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
Add a Connector Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
Add a Filter for Unaccepted Meetings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
Dynamically Provision Calendar Connector Information . . . . . . . . . . . . . . . . . . . . . 177
Managing Endpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
View the Endpoint List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Customize the Endpoint List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
View Endpoint Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
Download Endpoint Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
Add an Endpoint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
Add a Video Endpoint or Find an Endpoint on the Network . . . . . . . . . . . . . . . . . . . 187
Edit an Endpoint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
Delete an Endpoint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
Polycom, Inc.
10
Contents
Change an Endpoint Group Association . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
Manage an Endpoint Owner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
Manage an Endpoint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
View Call Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
View an Endpoint’s Video Feed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
Clear an Endpoint Help Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
Send a Message to an Endpoint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
Reboot an Endpoint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
Associate a User with an Endpoint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
Search for Endpoints in a Range of IP Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
Working with Endpoint Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
Add an Endpoint Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
Edit an Endpoint Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
Copy an Endpoint Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
Reboot Phones in an Endpoint Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
Refresh an Endpoint Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
View Endpoint Group Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
Delete an Endpoint Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
Set an Endpoint Group to Top Priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
Monitoring and Managing Peripherals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
Monitor Peripherals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
Use Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
Peripherals List in the Peripherals View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
Link to the Management Web Interface of a Peripheral . . . . . . . . . . . . . . . . . . . . . . . . . 202
Deleting a Peripheral . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
Display Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
Peripheral Software Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
Download an Endpoint Inventory Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
Endpoint Inventory Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
Supported Endpoints and Peripherals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
Supported Polycom Endpoints and Peripherals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
Supported Third-Party Endpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
Considerations for Third-Party Endpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
Reporting and Monitoring for Third-Party Endpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
Considerations for Cisco Endpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
Enable Cisco Endpoints Global Address Book Access . . . . . . . . . . . . . . . . . . . . . . 210
Considerations for Cisco Address Books . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
Scheduled Provisioning of Selected Cisco Endpoints . . . . . . . . . . . . . . . . . . . . . . . 210
Management of Cisco Endpoints with HTTPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
Polycom, Inc.
11
Contents
Considerations for LifeSize Endpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
Enable Management of a LifeSize Endpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
Provisioning of LifeSize Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
Scheduled Provisioning of LifeSize Endpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
Polycom Software Endpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
Add a Polycom CMA Desktop Custom Logo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
Remove a custom logo from the CMA Desktop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
Distribute Polycom RealPresence Desktop for Windows Systems . . . . . . . . . . . . . . . . . . . . 214
Distribute the client via an email link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
Distribute the client via the management system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
Distribute the client via a desktop management or group policy object . . . . . . . . . . . . . 215
Distribute the client via a .zip file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
Have users download the client from the Polycom support page . . . . . . . . . . . . . . . . . . 215
Distribute Polycom RealPresence Desktop for MAC OS Systems . . . . . . . . . . . . . . . . . . . . 215
Have users download the client from the Polycom support page . . . . . . . . . . . . . . . . . . 216
Distribute the Client for MAC OS client via an email link . . . . . . . . . . . . . . . . . . . . . . . . 216
Distribute the Mac client via the management system . . . . . . . . . . . . . . . . . . . . . . . . . . 216
Distribute the Mac client via a .dmg file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
Scheduled Endpoint Management . . . . . . . . . . . . . . . . . . . . . . . . . . 217
Scheduled Endpoint Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
Supported Endpoints for Scheduled Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
Scheduled Endpoint Management Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
Automatic Registration Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
Support HTTPs for Cisco Endpoint Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
Set Common Passwords for Endpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
Disable Common Password for Endpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
Creating Scheduled Provisioning Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
Add a Scheduled Provisioning Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
Edit a Scheduled Provisioning Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
Clone a Scheduled Provisioning Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
Delete a Scheduled Provisioning Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
Scheduling Endpoints for Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
View a List of Eligible Endpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
Schedule an Endpoint for Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
Check the Status of a Scheduled Provisioning Update . . . . . . . . . . . . . . . . . . . . . . . . . . 225
Clear the Status of Scheduled Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
Cancel a Scheduled Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
Polycom, Inc.
12
Contents
Endpoint Fields for Scheduled Provisioning Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
Scheduling Endpoint Software Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
Software Update Considerations for Multi-Tenancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
Creating Scheduled Software Updates for Endpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
List the Serial Numbers for the Endpoints to be Updated . . . . . . . . . . . . . . . . . . . . . . . . 242
Download the Required Software Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
Request Update Activation Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
Upload the Software Update for Scheduled Software Updates . . . . . . . . . . . . . . . . . . . 244
Using Scheduled Software Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
Supported Endpoints for Scheduled Software Updates . . . . . . . . . . . . . . . . . . . . . . . . . 245
Schedule the Software Update for Endpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
Scheduled Software Update View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
Endpoint List in the Scheduled Software Update View . . . . . . . . . . . . . . . . . . . . . . 246
Scheduled Software Update Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
View Scheduled Software Update Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
View List of Software Update Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
Cancel Software Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
Dynamic Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
Understanding Dynamic Endpoint Management . . . . . . . . . . . . . . . . . . . . . . . . 251
Supported Polycom Endpoints and Peripherals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
Overview of Dynamic Management Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
Configure your DNS Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
Configure Endpoints to use a Provisioning Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
Define Endpoint Naming Schemes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
Create Video Endpoint Provisioning Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
Create Provisioning Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
Create Access Control Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
Create Software Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
Selective Provisioning of Dynamically Managed RealPresence Group Series Systems . . . 254
Dynamically Manage RealPresence Immersive Studio Systems . . . . . . . . . . . . . . . . . . . . . 254
Stop Dynamic Management of an Endpoint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255
Dynamically Updating Endpoint and Peripheral Software . . . . . . . . . . . . . . . . 256
Software Update Considerations for Multi-Tenancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256
Software Update Considerations for RealPresence Desktop . . . . . . . . . . . . . . . . . . . . . . . . 257
Creating Dynamic Software Updates for Endpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257
List the Serial Numbers for the Endpoints to be Updated . . . . . . . . . . . . . . . . . . . . . . . . 258
Polycom, Inc.
13
Contents
Download the Required Software Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259
Request Upgrade Activation Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259
Upload the Software Update for Dynamic Software Updates . . . . . . . . . . . . . . . . . . . . . 260
Using Dynamic Software Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
Set a Dynamic Software Update Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262
View Dynamic Software Update Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
View Software Update Details for an Endpoint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
View Dynamic Software Update Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
Set Maintenance Window for Dynamic Software Updates . . . . . . . . . . . . . . . . . . . . . . . 267
Set up a Trial Dynamic Software Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
Create a Local Trial Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268
Create a Trial Software Update Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268
Promote the Trial Software Update Package to Production . . . . . . . . . . . . . . . . . . . . . . 268
Delete the Trial Software Update Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
Populate Domain Name for Software Endpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
Enable Software Endpoints to Save Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
Dynamic Software Updates for Peripherals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270
View Software Updates for Polycom Touch Controls . . . . . . . . . . . . . . . . . . . . . . . . . . . 270
Upload Peripheral Software Updates to the RealPresence Resource Manager System 271
Configure Peripheral Updates for Production . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272
Configure Peripheral Updates for Trial . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273
Using Dynamic Provisioning Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275
Set up Dynamic Provisioning Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275
Types of Dynamic Endpoint Provisioning Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275
Selective Provisioning of Dynamically Managed RealPresence Group Systems . . . . . . . . . 276
Working with Provisioning Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276
Create a New Provisioning Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277
Edit a Provisioning Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277
Reset a Default Provisioning Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278
Edit a Default Provisioning Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278
Reset a Provisioning Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
Clone a Provisioning Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
Delete a Provisioning Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
Network Provisioning Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280
Available Settings for a Network Provisioning Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . 280
Admin Config Provisioning Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291
Available Settings for Admin Config Provisioning Profiles . . . . . . . . . . . . . . . . . . . . . . . 291
Polycom, Inc.
14
Contents
Creating Dynamic Provisioning Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296
Activating Provisioning Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296
Prioritizing Provisioning Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296
Using Rule Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
Condition Operators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
Working with Provisioning Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298
Add a Provisioning Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298
Name the Provisioning Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299
Activate the Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299
Add a Condition to a Provisioning Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299
Associate Provisioning Profiles with a Provisioning Rule . . . . . . . . . . . . . . . . . . . . . 301
View Details of a Provisioning Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301
Edit the Priority of a Provisioning Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301
Clone a Provisioning Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302
Deactivate a Provisioning Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302
Edit a Provisioning Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303
Delete a Provisioning Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303
Dynamically Managing Endpoint Naming Schemes . . . . . . . . . . . . . . . . . . . . . 304
Using Custom Active Directory Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304
Find the Attribute Name to Use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305
Active Directory Global Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306
Define an E.164 Address Scheme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306
Define an Endpoint Naming Scheme and H.323 Alias . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308
Auto-Generate SIP URIs for Dynamically Managed Endpoints . . . . . . . . . . . . . . . . . . . . . . . 311
Using Bundled Provisioning Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313
How Bundled Provisioning Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313
Considerations for Bundled Provisioning Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314
Download a Bundled Provisioning Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314
View the List of Bundled Provisioning Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315
Edit a Bundled Provisioning Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316
Delete a Bundled Provisioning Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316
Re-associate Devices with a Different Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317
Settings included in a Bundled Provisioning Profile for an HDX . . . . . . . . . . . . . . . . . . . . . . 317
Settings included in a Bundled Provisioning Profile for a RealPresence Group System and RealPresence Immersive Studio System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324
Using Access Control Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326
Understanding Access Control Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326
Implementing Access Control Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326
Polycom, Inc.
15
Contents
Plan Implementation of Access Control List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327
Using Access Control Lists in a Multi-Tenancy Environment . . . . . . . . . . . . . . . . . . . . . . . . 327
Working with Access Control Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327
Add a New Access Control List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328
Edit an Access Control List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328
Delete an Access Control List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329
Dynamic Provisioning of Endpoints for SIP Server Integration . . . . . . . . . . . . 330
SIP Server Authentication Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330
Provisioning Endpoints with SIP Server Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331
Create Authentication Information for SIP Endpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . 331
Import SIP URI Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331
Editing SIP URI Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332
Provision SIP Settings for SIP Server Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332
Provision Group for Microsoft Lync or Microsoft Office Communications Server Integration .
334
Microsoft Directory Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334
Using Zero-Touch Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335
Configure your DHCP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335
Configure Zero Touch Provisioning Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335
Manually Associate an Endpoint’s Serial Number with a Room or User . . . . . . . . . . . . . . . . 336
Enable Calendaring Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336
Enable Polycom® Concierge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338
Integrating with Active Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338
Configuring the Calendar Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339
Configure your system with RealPresence Web Suite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339
Dynamically Provisioning Polycom Concierge Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339
Enable Dynamic Provisioning of Polycom Concierge . . . . . . . . . . . . . . . . . . . . . . . . . . . 339
Enable Calendaring for Dynamically Provisioned Endpoints . . . . . . . . . . . . . . . . . . . . . 340
Enable Dynamic Provisioning of the Calendar Connector . . . . . . . . . . . . . . . . . . . . . . . 340
SmartPairing for RealPresence Mobile and RealPresence Desktop Systems . . . . . . . . . . . 340
Program the Beacon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341
Generate SmartPairing Information for RealPresence Group Series Systems . . . . . . . . 341
Change the Beacon UUID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342
Dynamically Managing a RealPresence Access Director System . . . . . . . . . . 343
Creating a Site for the RealPresence Access Director System . . . . . . . . . . . . . . . . . . . . . . . 343
Create a RealPresence Access Director Server Provisioning Profile . . . . . . . . . . . . . . . . . . 343
Creating a Network Provisioning Profile for Endpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344
Polycom, Inc.
16
Contents
Creating an Admin Config Provisioning Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344
Creating a Provisioning Rule and Associate it with All Related Profiles . . . . . . . . . . . . . . . . 345
Creating a User Account for the RealPresence Access Director System . . . . . . . . . . . . 345
Available Settings for RealPresence Access Director Server Provisioning Profile . . . . . . . . 345
Phone Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347
Managing Audio Phones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348
Overview of Phone Management Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348
Supported Phones and Call Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349
Managing Audio Phones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350
Automatically Added Phones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350
Configure Automatically Added Audio Phones for Provisioning . . . . . . . . . . . . . . . . 350
Editing Automatically Added Phones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351
Add a Phone Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351
Edit an Audio Phone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352
Change Endpoint Group Association . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352
Change Configuration Profile Association of Audio Phones . . . . . . . . . . . . . . . . . . . . . . 353
Delete an Audio Phone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353
Set Active Directory Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354
Control Call Remotely . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354
Import Audio Phones Using CSV Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354
Create a CSV File Containing the Audio Phone Information You Need . . . . . . . . . . 354
Import the CSV File and View the Import Details . . . . . . . . . . . . . . . . . . . . . . . . . . . 356
Export and Edit Phones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356
Working with Phone Configuration Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356
Create a Phone Configuration Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357
Edit a Phone Configuration Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358
Copy a Configuration Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359
View a Configuration Profile Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359
Delete a Phone Configuration Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359
Export Configuration Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360
Audio Phone Configuration Profile Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360
Associate Configuration Profiles with Pre-defined Conditions . . . . . . . . . . . . . . . . . . . . 360
Reboot Phones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361
Register Phones to a SIP server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361
Monitor Phones Behind Firewall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362
Working with Resource Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362
Upload Resource File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362
Download Resource File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363
Polycom, Inc.
17
Contents
Delete Resource Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363
Refresh Resource Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363
Working with Phone Software Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363
Upload the Software Update for Phone Software Updates . . . . . . . . . . . . . . . . . . . . . . . 364
Set a Software Update Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364
Working with CUCM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364
Configuring Cisco Unified Communications Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . 365
Start the Cisco AXL Web Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365
Creating a User for the RealPresence Resource Manager Integration . . . . . . . . . . 366
Enabling Auto Discovery of RealPresence Resource Manager through DHCP . . . 367
Creating Phone Configuration Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367
Configuring the CUCM as a SIP server (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367
Customizing Digest User Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367
Integrating with a Cisco Unified Communications Manager . . . . . . . . . . . . . . . . . . . . . . 367
Add a Cisco Unified Communications Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368
Synchronize with the Cisco Unified Communication Manager . . . . . . . . . . . . . . . . . 369
Configure Your Phone Management Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369
User Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371
Understanding Users, Groups, and Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372
Working with Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372
Local Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372
Enterprise Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373
Assigning Roles to Enterprise Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373
Working with Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374
Local Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374
Enterprise Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374
Preparing to Use Active Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374
Working with Management Roles and Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375
Understanding User Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375
Default System Roles and Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376
Scheduler Roles, Responsibilities, and Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378
Operator Role, Responsibilities, and Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379
Device Administrator Role, Responsibilities, and Menus . . . . . . . . . . . . . . . . . . . . . 379
Auditor Role, Responsibilities, and Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379
Administrator Role, Responsibilities, and Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . 379
Customized Roles and Responsibilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380
Polycom, Inc.
18
Contents
Managing Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382
Managing Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382
Search for a User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382
View User Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383
Add a Local User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384
Edit a User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386
Assign Users to Manage an Area(s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386
Delete a Local User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387
Clear Orphan Active Directory Users/Rooms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387
Enable/Disable Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388
Unlock a User Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388
Import Local Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388
Create a CSV File Containing the User Information You Need . . . . . . . . . . . . . . . . 389
Import the CSV File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390
Handle the User Accounts with Password lost . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390
Review the Import Details File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391
Updating Users by Import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391
Adding Machine Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392
Add a Machine Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392
Edit a Machine Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393
Manage Dial String Reservations for Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394
Export User Aliases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394
Importing User Aliases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394
SIP Format: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395
H323 Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396
Importing User Aliases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397
Managing Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398
Add a Local Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398
Import Enterprise Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399
Edit a Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399
Delete a Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400
Managing User Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400
View the List of User Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401
Add a User Role . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401
Edit Permissions for a User Role . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402
Delete a User Role . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402
View the Groups and Users Associated with a User Role . . . . . . . . . . . . . . . . . . . . . . . 402
Managing Meeting Rooms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403
Local and Enterprise Meeting Rooms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403
Polycom, Inc.
19
Contents
View the Rooms List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403
Search for a Room . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404
Add a Local Room . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404
Add an Enterprise Room . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406
Edit a Room . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406
Delete a Room . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407
System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 408
Network Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409
Edit Network Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409
Virtualization Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410
Edit Virtualization Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411
Time Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411
Edit System Time Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411
System Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 412
Trial Licenses for Appliance Editions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413
Licenses for Virtual Editions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413
View Current Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413
Add System Licenses for an Appliance Edition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414
Request a Software License File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414
Update the License File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415
Sending Usage Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415
Enable or Disable User Data Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416
See the Collected Usage Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416
Reclaim Software Client Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416
Customizing System Logos . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417
Add a System Logo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417
Remove a System Logo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417
Edit the System Email Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 418
Understanding System Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419
System Dashboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419
Dashboard Panes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419
Today’s Scheduled Conferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420
Endpoint Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420
CPU/Memory/Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420
Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420
Today’s Adhoc Conferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420
Hardware Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420
Polycom, Inc.
20
Contents
Endpoint Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421
Site Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421
Service Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421
Today’s Conferences Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421
System Info . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421
Endpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 422
Pre-call Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 422
MCU Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423
Users Logged In . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424
Redundancy Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424
Resource Manager Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424
CUCM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425
DMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425
Securing the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 426
System Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 426
Managing Security Baselines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 426
Standard Security Baseline Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427
Secure Communication Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427
TLS Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427
System Hardening Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 428
Session Management Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 428
User Account Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 428
Password Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429
Sensitive Information Disclosure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429
High Security Baseline Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 430
Secure Communication Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 430
TLS Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 430
System Hardening Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431
Session Management Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431
User Account Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431
Password Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432
Sensitive Information Disclosure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432
Create a Security Baseline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433
View a Security Baseline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433
Edit a Security Baseline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433
Delete a Security Baseline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434
Apply Security Baseline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434
Audit Your System Against a Security Baseline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434
Configure Secure Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 435
Polycom, Inc.
21
Contents
Configure TLS Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 435
Configure System Hardening . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437
Session Security and User Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438
Change the System User Interface Timeout and Number of Sessions . . . . . . . . . . . . . . 438
Control Remote Connections to the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439
Enabling and Editing Log In Banners . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439
Enable Banner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439
Edit Banner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439
Set Local Account Lockout and Timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 440
Set Password Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 440
Setting Management Access Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441
Configure Management Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442
Disable Management Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442
Set Sensitive Information Disclosure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442
Reset System Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442
Security Certificates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 444
How Certificates are Used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 444
Accepted Certificates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 444
Certificate Signing Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 446
Requirements for Certificate Signing Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447
Create a Certificate Signing Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 449
Installing Certificates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450
Install a Certificate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450
View Certificates and Certificate Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 451
Removing Certificates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 452
Remove a Trusted Root CA’s Certificate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 453
Remove a Signed Certificate and Revert to Default Self-Signed Certificate . . . . . . . . . . 453
Regenerate a Default Self-Signed Certificate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454
Revert to a Legacy VVX Certificate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454
OCSP Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454
Integrating with an Enterprise Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 456
Enterprise Directory Supported Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 456
Single Forest Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 457
Multiple Domains within a Single Forest . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 457
Universal Group Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 457
Read-only Enterprise Directory Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 457
How Global Catalog Searches Work . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 458
Using the Base DN to Manage Enterprise Directory Searches . . . . . . . . . . . . . . . . . . . . 459
Polycom, Inc.
22
Contents
Examples of Base DN Filter Expressions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 459
Examples of Base DN Exclusion Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 461
Examples of Advanced Base DN Exclusion Filters . . . . . . . . . . . . . . . . . . . . . . . . . 461
RealPresence Resource Manager System and Windows Authentication . . . . . . . . . . . . . . . 462
Managing Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 462
Integrating with Enterprise Directory Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 463
Create the RealPresence Resource Manager System Service Account . . . . . . . . . 463
Create the RealPresence Resource Manager System Computer Account . . . . . . . 464
Enable Integration with the Enterprise Directory Server . . . . . . . . . . . . . . . . . . . . . . 465
Allow Delegated Authentication to Enterprise Directory Server . . . . . . . . . . . . . . . . . . . 466
Give Enterprise Users Default Scheduler Role . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 467
Change the Message for Enterprise Users without a Role . . . . . . . . . . . . . . . . . . . . . . . 467
Endpoint Directory and Directory Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 467
Removing or Include Dynamically Managed Endpoints in the Global Address Book . . . 468
Remove Enterprise Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 468
Include Enterprise Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 468
Remove or Include Guest Book Entries in the Directory . . . . . . . . . . . . . . . . . . . . . . . . . 469
Remove Guest Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 469
Include Guest Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 469
Allow Local Users to View Enterprise Directory Entries . . . . . . . . . . . . . . . . . . . . . . . . . 469
Supporting LifeSize Endpoints in Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 470
Modify Directory Listings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 470
Configure LDAP Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 470
Allow Mid-String Searches for Local Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 471
Configuring Multi-Tenancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 472
Planning For Multi-Tenancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 472
Working within a Multi-Tenancy Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473
User Roles within a Multi-Tenancy Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473
System Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473
Area Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473
Area Conference Participants . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474
Area Address Books . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474
Area User Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 475
Area Users, Rooms, and Associated Endpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 475
Area Conference Guests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 475
Using the Common Pool in a Multi-Tenancy Environment . . . . . . . . . . . . . . . . . . . . . . . 476
Area Conference Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 476
Configure Areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 476
Enable Areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 477
Polycom, Inc.
23
Contents
Create Areas for Tenants . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 477
Setting up Area Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 477
Managing the Area with System Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 478
Managing the Area with Area Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 478
Assigning Resources to an Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 478
Resources Belong to One or No Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 478
Resources Belong to One or More Areas (or no Area) . . . . . . . . . . . . . . . . . . . . . . . 479
Adding Users to An Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 479
Configuring Site Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 479
Associating Billing Codes with Conferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480
Add a New Billing Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480
Delete a Billing Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 481
Associating a Billing Code with a Conference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 481
Viewing Billing Code Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 481
Managing Areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 482
Enable Areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 482
Add an Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 482
Edit an Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 483
Viewing All Areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 483
View Information for a Specific Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 484
Remove an Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 484
Move the Contents of an Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 485
Deleting an Area and its Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 485
Customizing the Area Logos (system and CMA Desktop) for the Area . . . . . . . . . . . . . . . . . 486
Customize the System Log for an Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 486
Customize the CMA Desktop Logo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 486
System Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 488
System Redundancy Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 488
How Redundancy Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 488
Configuration Considerations for Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 489
Interoperability Considerations for Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 490
Local versus Geographic Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 490
Managing a Redundant System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 490
Manually Failover to a Redundant Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 491
Track System Failovers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 491
Discontinue Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 492
Polycom, Inc.
24
Contents
Local System Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 493
Optional: Perform a System Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 493
Ensure the Servers Can Communicate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 493
Perform Network Configuration on Both Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 494
Enable the Root User Login and SSH Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 494
Optional: Change the Redundant Interface IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . 494
Configure the System for Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495
License a Redundant System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495
Provisioning Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 496
Geographic System Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 497
Network Requirements for a Geographic Redundant System . . . . . . . . . . . . . . . . . . . . . . . . 497
Optional: Perform a System Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 498
Perform Network Configuration on Both Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 498
Enable the Root User Login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 498
Configure DNS for the Redundant Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 498
Configure DNS (Example Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 499
Configure the System for Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 500
License a Redundant System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 501
Provisioning Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 502
System Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 503
System Management and Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 504
Management and Maintenance Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 504
Administrator Responsibilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 504
Administrative Best Practices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 504
Auditor Responsibilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 505
Auditor Best Practices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 505
Recommended Regular Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 505
Track System Alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 505
Create and Archive Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 506
General System Health and Capacity Checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 506
Certificates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 506
CDR export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 506
System Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 507
Report Considerations for Multi-Tenancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 507
View Site Statistics Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 507
View Site Link Statistics Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 508
Polycom, Inc.
25
Contents
Call Detail Record Report Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 509
Modify the CDR Retention Period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 509
Schedule Archives of the CDR Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 509
View Endpoint Usage Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 510
Generate Network Device Usage Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515
Create Conference Usage Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515
Create Conference Type Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 516
RealPresence Resource Manager System SNMP . . . . . . . . . . . . . . . . . . . . . . . 519
SNMP Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 519
SNMP Framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 519
SNMP Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 520
SNMP Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 520
Configuring SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 520
Enable the SNMP Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 521
Add an SNMP Notification Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 522
Add a Security User (SNMP v3 only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 523
Enable SNMP for an Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 524
Download MIBs
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 525
Configuring Alert Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 528
Set Up Remote Alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 528
Set Up System Generated Email Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 528
Enable RealPresence Resource Manager System Remote Alerts . . . . . . . . . . . . . . . . . 529
Set RealPresence Resource Manager System Remote Alert Level Settings . . . . . . . . . 529
Set RealPresence Resource Manager System Alert Threshold Settings . . . . . . . . . . . . 531
Set Endpoint Alert Level Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 531
Configuring Remote Alert Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 533
Add a Remote Alert Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 533
Supported Device Types for Remote Alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 535
Associate a Remote Alert Profile With a User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 536
Edit a Remote Alert Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 536
Disable a Remote Alert Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 537
Delete a Remote Alert Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 537
Disable System Remote Alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 537
View and Delete Network Device Alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 537
View Endpoint Event Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 538
System Backup and Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 539
Creating System Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 539
Polycom, Inc.
26
Contents
Create an Automatic System Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 539
Create a System Backup Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 540
Restoring the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 541
Restore to Factory Default Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 542
Restore from a Backup Archive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 542
System Maintenance and Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . 544
System Log Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 544
Available System Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 545
Managing Locally Stored System Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 545
View Locally Stored System Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 545
Change Logging Level for Locally Stored Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 546
Download Locally Stored Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 547
Roll Locally Stored Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 547
Customize Jserver Log to Target Specific Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 548
Managing System Logs using a Syslog Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 549
Store System Logs on a Remote Syslog Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 549
Delete a Log from Being Stored on a Remote Syslog Server . . . . . . . . . . . . . . . . . . . . . 550
Managing Audit Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 551
View and Download Audit Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 551
Change Audit Log Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 552
Roll Audit Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 552
Backup and Delete Audit Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 552
View RealPresence Resource Manager System Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . 553
Troubleshooting Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 555
Working with Phone Management Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 556
View Phone Management Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 556
Filter Phone Management Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 556
Download Phone Management Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 557
Clear Phone Management Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 557
Troubleshooting Specific Types of Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 557
Registration Problems and Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 558
Point-to-Point Calling Problems and Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 559
MCU and Gateway Dialing Problems and Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 559
Diagnostics for your Dell Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 560
System Security and Port Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 561
Open Inbound Ports on the RealPresence Resource Manager System . . . . . . . . . . . . . . . . 561
Outbound Ports Used by the RealPresence Resource Manager System . . . . . . . . . . . . . . . 562
Internal Ports used by the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 563
Polycom, Inc.
27
Contents
Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 564
Appendix A: Working in a vCenter Environment . . . . . . . . . . . . . . . . . . . . . . . . 565
Basic Configuration Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 565
Managing Providers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 565
Add a Provider . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 565
Edit a Provider . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 566
Delete a Provider . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 566
Managing Resource Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 566
Add a Resource Group to a Provider . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 567
Edit a Resource Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 567
Delete a Resource Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 568
Instance Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 568
Delete Uploaded Images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 570
Service Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 570
vCenter Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 570
VMware APIs Used by RealPresence Resource Manager . . . . . . . . . . . . . . . . . . . . . . . 570
Instance Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 571
Two Methods for Adding VM Instances in a vCenter . . . . . . . . . . . . . . . . . . . . . . . . 571
Monitor vCenter Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 572
Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 573
References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 574
Appendix B: Supported Ciphers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 575
Polycom, Inc.
28
Getting Started
This section provides an overview of system features and configuration:
● Polycom® RealPresence® Resource Manager Overview
● System Setup Overview
Polycom, Inc.
29
Polycom® RealPresence® Resource
Manager Overview
This section provides an overview of the Polycom® RealPresence® Resource Manager system. It includes
the following topics:
● RealPresence Resource Manager Features and Capabilities
● Working in the RealPresence Resource Manager System
RealPresence Resource Manager Features and
Capabilities
The RealPresence Resource Manager is an integrated scheduling and management platform for endpoints
and video conferencing infrastructure management. In particular, it functions as the management and
licensing platform for Polycom® RealPresence Clariti™.
RealPresence Resource Manager includes the following features and capabilities:
Video Infrastructure Management
● Network device management. You can view and manage all of your Polycom video conferencing
network devices from a single interface. Network device management and system monitoring and
management including network typology by geography and visual alarm reporting.
● Service group level configuration. You can create a service group of all the Polycom network devices
within your video environment. This allows you to configure settings on a service group level.
● Licensing management. RealPresence Resource Manager system acts as the licensing interface
between the Polycom Licensing Center and your RealPresence Clariti products.
● Solution monitoring for network devices. Monitor all the network devices within your video
infrastructure environment.
● Multi-tenancy support.
Video Endpoint and Audio Phone Management
● Video endpoint management, including provisioning, updating, and troubleshooting.
● Video endpoint provisioning enables you to edit endpoint settings for the endpoints registered to the
RealPresence Resource Manager. You can take advantage of dynamic (automatic) provisioning for
Polycom endpoints, based on provisioning rules. For legacy and third-party endpoints, you can
manually schedule provisioning profiles to be sent at intervals you define.
● Dynamic software updates for dynamically managed Polycom endpoint systems and scheduled
software updates for third-party and legacy endpoints.
Polycom, Inc.
30
Polycom® RealPresence® Resource Manager Overview
● Audio phone management includes provisioning, updating, and troubleshooting.
Conference Scheduling
● Conference scheduling and monitoring on both RealPresence Resource Manager system resources
and the Polycom® RealPresence® DMA® systems (when integrated with the RealPresence Resource
Manager system).
● Advanced routing to distribute audio and video calls across multiple conferencing platforms (MCUs),
creating a single seamless resource pool, when integrated with a Polycom RealPresence DMA
system.
Directory Services
● Directory and user management including address books and presence. Integration with an
enterprise directory for user management.
● Access to user and room directories for on-demand and scheduled calls. Directory services include:
 Presence and contact list functionality for dynamically managed endpoints (except for
RealPresence Mobile clients).
 Global Address Book for a single directory structure or Multiple Address Books for multiple
managed directories.
 H.350 and LDAP directory functionality. H.350 defines a directory services architecture for
multimedia conferencing for H.323, H.320, SIP, and generic protocols.
Session Border Control Integration
Integrate with session border control systems which enable video conferencing across firewalls.
Redundant Configuration
An optional high-availability, redundant management server configuration.
Programmatic Access through API
Optional programmatic access through Application Programming Interfaces (APIs).
Working in the RealPresence Resource Manager
System
This section introduces some general information you should know when working in the RealPresence
Resource Manager system.
● Log In to the System
● Field Input Requirements
● Filter and Search in a List
Polycom, Inc.
31
Polycom® RealPresence® Resource Manager Overview
● Change a Password
● Log Out of the System
● Restart or Shut Down a System
● Emergency Shutdown of the System
Log In to the System
To log in to the RealPresence Resource Manager web interface, you need the IP address or host name of
the RealPresence Resource Manager system server and your user name, password, and domain.
For security reasons, do not save your user name and password.
User with Admin role will be locked for one minute after three (default) failed attempts, while other users
follow the rules of failed login that the Admin sets. For more information on how to set the rules, see Set
Local Account Lockout and Timeout.
To log in to the system:
1 Open a browser window and in the Address field enter the RealPresence Resource Manager
system IP address or host name.
 If prompted to install the Adobe Flash Player, click OK.
 If you receive an HTTPS Security Alert, click Continue.
 If you see a login banner, click Accept to accept the terms and continue.
If you cannot connect to the system, there may be certificate issues. Contact your RealPresence
Resource Manager system administrator.
2 When the system Log In screen appears, enter your Username and Password. If you are logging
in with your enterprise directory account, include your domain (domain/username). Local users do
not have to include a domain.
3 If necessary, select a different language from the bottom of the logging in page.
4 Click Login.
Because the RealPresence Resource Manager system is a role-based system, you see only the pages and
functions available to your system roles.
If you log in as an administrator, you see the RealPresence Resource Manager system Dashboard.
For more information about roles and the functionality associated with roles, see Default System Roles and
Permissions.
Field Input Requirements
While every effort was made to internationalize the RealPresence Resource Manager, not all system fields
accept Unicode entries. If you work in a language other than English, be aware that some RealPresence
Resource Manager fields may accept only ASCII or extended ASCII characters.
Polycom, Inc.
32
Polycom® RealPresence® Resource Manager Overview
Filter and Search in a List
In the RealPresence Resource Manager system, information is often summarized in lists or grids.
Lists that include many items may have filters or searchable fields, which allow you to view a subset of items
or search for a specific entry. The available filtering options depend on the type of information in the list. For
example in the endpoint list:
● If you click
and select Type as the filter, all the available types appear.
● You also can search endpoints by Name, IP address, Dial String, Site, and other keywords.
In general, most text filter fields are ASCII only and the RealPresence Resource Manager search function
is a case-insensitive, substring search. That means when you enter a search string, the RealPresence
Resource Manager looks for that string where ever it occurs (beginning, middle, or end) in the word or
number.
However, if the RealPresence Resource Manager system is integrated with an Active Directory, the
RealPresence Resource Manager uses the LDAP search function for searches of the directory. LDAP
searches are prefix-searches that include an appended wildcard. In this case, when you enter a search
string, the system looks for that search string only at the beginning of the indexed fields.
For example, all of the following searches for a participant will find Barbara Smithe:
Barbara
Smithe
Bar
Smi
To optimize LDAP searches, the RealPresence Resource Manager system searches only indexed LDAP
fields and a limited set of attributes. The attributes include:
ObjectCategory
memberOf
DisplayName
GivenName
Sn
Cn
Samaccountname
groupType
distinguishedName
objectGuid
These are the requested attributes to be returned by the search:
Sn
Givenname
Mail
Ou
Objectguid
Telephonenumber
Cn
Samaccountname
Memberof
Polycom, Inc.
33
Polycom® RealPresence® Resource Manager Overview
Displayname
Objectclass
Title
localityName
department
Managing Bandwidth
The RealPresence Resource Manager system manages the bandwidth between sites and the bandwidth
for calls that it schedules within the gatekeeper region it services. The sites and bandwidth management is
only possible with a RealPresence DMA system.
Users with administrator permissions can create bandwidth management policies by setting the following
limits. The RealPresence Resource Manager system applies the lowest value from the settings described
here to limit the bit rate of specific calls or conferences.
● The maximum bit rate for a call at a site. Set it by editing the site, selecting Routing/Bandwidth,
and setting the Call Max Bit Rate.
● The total bandwidth between sites. The link type and bandwidth are parameters of the site links
between two sites. Set it by editing the site link.
● The maximum speed (bit rate) for calls across a site link. This value is also a parameter of the
site links between two sites and is set by editing the site link.
● The specific speed (bit rate) of calls in a conference. This value is a parameter of the conference,
as it is inherited from the conference template. You can achieve granularity of bandwidth
management by (a) creating a variety of scheduling roles, (b) creating a variety of conference
templates with different conference speeds, (c) associating different scheduling roles with different
templates, and (d) associating different users and/or groups with the different scheduling roles.
For example, you can assign an executive user or group more bandwidth than your typical user. To
do this, create a VIP role and assign it scheduling or advanced scheduling permissions. Then create
a VIP conference template that has a higher video speed, say 4096 kpbs. Finally, associate the
executive user or group with the VIP role.
There are some things to note in these situations.
 The RealPresence Resource Manager system may reduce bandwidth or fail a call if the requested
bandwidth is not available.
 Schedulers with advanced scheduling permissions can choose to change the speed of calls in
conference by changing the value for a specific conference. However, the RealPresence
Resource Manager system only allows a connection speed when it is within the parameters set
for the site link.
 Endpoints in a conference may not be capable of transmitting at the requested speed. In this case,
they will transmit at the value they can achieve that is closest to the value set for the conference.
● The maximum speed (bit rate) for receiving calls and the preferred speed for placing calls
provisioned on the endpoint. These values are parameters of the endpoint. For endpoints in
dynamic management mode, these values are provisioned as part of an Admin Config provisioning
profile. For endpoints operating in scheduled management mode, these values can be provisioned
with a scheduled provisioning profile or modified at the endpoint itself.
Note in this case that the endpoint can request a speed when placing a call, but again the
RealPresence Resource Manager system only allows a connection speed when it is within the
parameters set for the site topology.
Polycom, Inc.
34
Polycom® RealPresence® Resource Manager Overview
Download Software Packages
For your convenience, you can download the following software packages directly from the system web
interface.
To download software packages:
1 Click Username > Download at the top-right corner of the page.
2 Click the Download button of the software that you want to download. You can download:
 Polycom RealPresence Desktop for Windows
 Polycom RealPresence Desktop for Mac
 Polycom File Verification Utility
See Backup and Delete Audit Files for details on how to use Polycom File Verification Utility.
Change a Password
For local users, RealPresence Resource Manager system password requirements (for example, password
length and password age) are managed by the RealPresence Resource Manager system administrator. For
enterprise users, RealPresence Resource Manager system password requirements are managed by
Microsoft Active Directory.
To change your system password:
1 Click Username > Change Password in the top-right corner of the page.
2 Enter your Old Password.
3 Enter a password to the New Password and Confirm Password fields.
4 For users with admin role, you can select the check box on the bottom of the dialog to apply the
same password to the admin users that you specified when adding the following servers as network
instances:
 RealPresence DMA
 RealPresence Collaboration Server
 Web Suite Services and Experience Portal
This operation does not apply to RealPresence DMA and RealPresence Collaboration Server with
service integrated.
5 Confirm the new password and click OK.
Log Out of the System
You can log out of the system at any time.
Polycom, Inc.
35
Polycom® RealPresence® Resource Manager Overview
To log out of the RealPresence Resource Manager system:
» Click Username > Log Out in the top-right corner of the page.
Restart or Shut Down a System
You have several options for an orderly shutdown or restart of a RealPresence Resource Manager system
in non-emergency situations.
The options for an orderly shutdown or restart of the system include:
● Use the Shutdown option on the Admin > Maintenance > Troubleshooting Utilities page when
you must disconnect the RealPresence Resource Manager system server for some reason; for
example, to move it. All RealPresence Resource Manager system functionality is stopped during a
Shutdown.
● If the system interface is not available and you must shut down the system, press once (but do not
hold) the power switch on the RealPresence Resource Manager system server. This is equivalent to
selecting the Shutdown option described previously.
● Use the Restart option on the same page when you must cycle the RealPresence Resource
Manager system for some reason; for example, if the system locks up or loses connection with Active
Directory.
If you have access to the RealPresence Resource Manager user interface, you can also stop future
scheduled conferences from starting automatically and wait for active conferences to end before performing
an orderly shut down or restart of the system.
During a restart, the system will drop all IP conferences. In general, ISDN conferences will not drop.
To restart or shut down the system:
1 (Optional) To stop future scheduled conferences from starting before you perform the restart or
shutdown:
a Go to Dashboard.
b Monitor the Today’s Scheduled Conferences section to determine when all active conferences
are completed.
2 Go to Admin > Maintenance > Troubleshooting Utilities and click Restart or Shutdown as
required.
In a redundant RealPresence Resource Manager system configuration, if you requested a shutdown
of the primary server, the system displays a warning indicating that it is initiating a failover.
If you select Restart, it may take the RealPresence Resource Manager system up to 10 minutes to
restart all server processes.
Emergency Shutdown of the System
You have two options to perform an emergency shutdown of a RealPresence Resource Manager system.
Use these options only when you must immediately cut power to the server.
● Press and hold the power switch on the RealPresence Resource Manager system server.
● Pull the system power cord.
Polycom, Inc.
36
Polycom® RealPresence® Resource Manager Overview
After an emergency shutdown (when you press and hold the power switch, or you pull the system cord, or
you lose power to the system), a system battery may continue to cache information until the battery runs
out. In this case, the system enters an error state. To recover, you must connect a keyboard and monitor to
the RealPresence Resource Manager system and boot the system to clear the error message. Then the
system can begin recovery.
Polycom, Inc.
37
System Setup Overview
This section describes the configuration tasks that may be required, based on your system design and
installation, to complete your implementation of a Polycom RealPresence Resource Manager system after
First Time Setup. It includes these topics:
● Adding DNS SRV Record for RealPresence Resource Manager System Services
● Setting Up Network Device Management
● Configuring Conferencing
● Configuring the Connection to an External Enterprise Directory
● Setting Up Endpoint Management
● Securing the System
● Configuring Redundancy
● Distributing Polycom Applications
Adding DNS SRV Record for RealPresence Resource
Manager System Services
To resolve queries to the RealPresence Resource Manager system using the system's host name or IP
address, you must configure the DNS server. We recommend that you configure the DNS server using the
system's fully qualified domain name (FQDN) to ensure that client systems running RealPresence Desktop
and RealPresence Mobile can access the RealPresence Resource Manager system.
The DNS should also have entries for your Active Directory server (if different from the DNS).
To dynamically manage endpoints (which includes dynamic provisioning, dynamic software updates, and
presence) out of the box, they must be able to automatically discover the RealPresence Resource Manager
system.
This means you must add the DNS service record (SRV record) for the RealPresence Resource Manager
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 0 443 Access5.customerdomain.com
The SRV record must point to the Provisioning Server (RealPresence Resource Manager system) that
endpoints will use for auto discovery for Dynamic Provisioning. Two or more provisioning servers may
co-reside on a network; however only one may be used for DNS-based discovery of provisioning services.
If more than one provisioning server is used within an environment, there is no knowledge or coordination
between these environments including, but not limited to:
● No shared directory services
● No shared management or provisioning services
Polycom, Inc.
38
System Setup Overview
● No shared scheduling
● No shared licenses
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).
Setting Up Network Device Management
You need to set up your RealPresence Resource Manager system to monitor your video conferencing
infrastructure as well as license any included Polycom infrastructure products.
● Add instance to the system for service integration, licensing, and monitoring. See Managing
Instances for details.
● Configure service groups settings. See Managing Service Groups for details.
Configuring Conferencing
You need to configure the RealPresence Resource Manager system for conference monitoring and
scheduling.
This section provides an overview of the following steps:
● Set Up Site Topology
● Set Up Conference Templates
● Set Up Directory Services
Set Up Site Topology
The video call routing setup includes site topology and bandwidth management.
You can perform the following tasks:
● Define a site for each physical location in which a LAN or an ISDN connection exists. If you use VPN
connections, you can consolidate distinct physical locations into a single logical site to simplify
management tasks. You can also define links between sites (site links).
● For each site, define the subnets in which the video endpoint systems are deployed. It is important
that the IP addresses used by the endpoints belong to only one subnet at a site.
For more information, see Setting Up Site Topology.
Set Up Conference Templates
The RealPresence Resource Manager system uses conference templates and global conference settings
to manage system and conference behavior.
The RealPresence Resource Manager system has a Default Template and default global conference
settings. You may want to create additional templates with different settings or change the global
conference settings.
For more information, see Direct Conference Templates.
Polycom, Inc.
39
System Setup Overview
Set Up Directory Services
Directory services provide information about all users, endpoints, and resources on your video
communication network.
To set up RealPresence Resource Manager system directory services:
1 For endpoints under scheduled management, set up and register endpoints.
a Set the Global Directory Server (GDS) to point to the RealPresence Resource Manager system
IP address or DNS name. Polycom recommends using the IP address to prevent data
inconsistencies.
b Register them to the Polycom RealPresence DMA system gatekeeper (when it is integrated with
your RealPresence Resource Manager system).
Most device information is automatically populated in the RealPresence Resource Manager system
through the gatekeeper registration to an integrated RealPresence DMA system or Global Address
Book access. You must review the information for these devices in the RealPresence Resource
Manager system Directory Setup page and fill in missing information.
To select endpoints when scheduling conferences, you must first associate them with a user or
conference room by editing the specific user or room settings. For more information, see Endpoint
Management.
2 For endpoints under scheduled management, set up users and associate them with endpoints.
Unless your RealPresence Resource Manager system is integrated with an enterprise directory, you
must enter all user information manually including endpoint association. If your system is integrated
with an enterprise directory, general user information (First Name, Last Name, User ID, Password,
and Email Address) is directly pulled from the directory and cannot be changed. However, you
must still associate enterprise users with endpoints. For more information, see Understanding
Users, Groups, and Roles.
3 Set up groups, add members, and associate them with provisioning profiles. For more information,
see Understanding Users, Groups, and Roles.
4 Set up rooms and associate them with endpoints. Unless your RealPresence Resource Manager
system is integrated with an enterprise directory that includes conference rooms, you must enter all
room information manually including endpoint association. For more information, see Managing
Meeting Rooms.
Configuring the Connection to an External Enterprise
Directory
Connecting to an enterprise directory enables users to enter their network usernames and passwords to log
into RealPresence Resource Manager system and dynamically managed endpoints. It also enables users
to access the enterprise directory when selecting conference participants.
Your RealPresence Resource Manager system must be connected to an enterprise directory system of
Microsoft Active Directory in order to dynamically manage the Polycom endpoints. Dynamic endpoint
management enables rule-based provisioning profiles, dynamic software updates, and Polycom®
Concierge.
If you have not yet configured your RealPresence Resource Manager system to use an enterprise directory,
you can do so at any time.
Polycom, Inc.
40
System Setup Overview
For details, see Integrating with an Enterprise Directory.
Setting Up Endpoint Management
The RealPresence Resource Manager system enables you to manage endpoints in two ways:
● Scheduled Management of Endpoints (Polycom and Third-Party)
● Dynamic Management of Endpoints (Polycom Only)
Scheduled Management of Endpoints (Polycom and
Third-Party)
Scheduled management enables you to push software updates and provisioning profiles to endpoints at
intervals that you define.
Scheduled management uses server-to-client communication over HTTP. This management technique is
more appropriate for corporate networks where both the RealPresence Resource Manager and all
endpoints are behind the same firewall.
For more information about scheduled management methods, see Scheduled Endpoint Management.
Dynamic Management of Endpoints (Polycom Only)
Dynamic management enables the endpoint to poll the RealPresence Resource Manager system
automatically to get dynamic provisioning profiles (configuration settings) and software updates on a regular
basis.
Dynamic management is client-to-server over HTTPS which makes it more secure and firewall-friendly.
Dynamic management is:
● available only for Polycom video endpoints.
● optional when your system is integrated with an enterprise directory.
● recommended when Polycom endpoints are able to automatically discover the RealPresence
Resource Manager. This means you must add the DNS service record (SRV record) for the
RealPresence Resource Manager.
In dynamic management mode, when an endpoint starts up at designated intervals thereafter, it
automatically polls the RealPresence Resource Manager system for a newer software update package or
provisioning profile. If either is found, the package is sent in XML format over a secure HTTPS connection.
Endpoints do not poll the system if they are in a call. They restart polling after the call ends.
For more information about dynamic management methods, see Understanding Dynamic Endpoint
Management.
Securing the System
By default, the RealPresence Resource Manager system uses https and a self-signed certificate for its
data interchanges. As a best practice, we recommend replacing the RealPresence Resource Manager
Polycom, Inc.
41
System Setup Overview
system self-signed certificate with a certificate from a certificate authority. For more information, see
Security Certificates.
Configuring Redundancy
You can install the RealPresence Resource Manager system with a fault-tolerant, high-availability, and
redundant configuration.
A redundant RealPresence Resource Manager system configuration requires the installation of two
RealPresence Resource Manager system servers. During First Time Setup, you are instructed to assign
these two servers physical IP addresses. Once the two system servers are installed, see System
Redundancy to finish implementing redundancy.
Distributing Polycom Applications
The RealPresence Resource Manager system enables you to download several Polycom applications for
use in specific environments. This includes two desktop video applications.
See Polycom Software Endpoints.
Polycom, Inc.
42
Network Device
Management
This section provides an introduction to the Polycom RealPresence Resource Manager network device
management functionality and operations. It includes:
● Understanding Network Device Management
● Managing Instances
● Managing Service Groups
Polycom, Inc.
43
Understanding Network Device
Management
The Polycom RealPresence Resource Manager system acts as network device management console for
systems within your video infrastructure environment.
Network devices include any infrastructure device that the RealPresence Resource Manager system
manages, licenses, or is aware of.
You can add network devices to the RealPresence Resource Manager system for monitoring, licensing, as
well as service integration, depending on the product.
You can access individual products directly from the RealPresence Resource Manager system device
management console after you have added them to the system. In addition, you can manage the time,
SNMP, and Active Directory settings for all network devices via a service group.
You must have the Device Administrator role to add new network devices to the system or edit their
properties. If your system supports multi-tenancy and areas have been enabled, users with the Area
Administrator role can also perform some device management tasks.
The remaining user roles can view network devices, but not add new ones or modify settings.
This section includes the following topics:
● Overview of Network Device Management
● Supported Network Devices
● Viewing Network Devices
Overview of Network Device Management
You can add network devices to the RealPresence Resource Manager system for monitoring, licensing, as
well as service integration, depending on the product.
● Service Integration
● Monitoring
● Service Group Administration
● Licensing
Service Integration
When you integrate a product’s services with the RealPresence Resource Manager system, it uses those
services for conference scheduling and management as well as endpoint provisioning.
Polycom, Inc.
44
Understanding Network Device Management
Monitoring
When you add an instance of a network device to the RealPresence Resource Manager, it can monitor the
system. When the RealPresence Resource Manager monitors a system, it tracks the health of the system
and you can also view whether or not the network device is available or offline.
Service Group Administration
When you add network devices to the RealPresence Resource Manager system, they are added to the
default service group. A service group is a group of network devices that can be monitored together and
inherit some server settings from the service group settings. You can manage the following settings through
service group settings: password settings, time settings, SNMP settings, and Active Directory integration
settings.
When you configure settings for a service group, the settings are inherited by supported Polycom network
devices within the group.
Licensing
The RealPresence Resource Manager provides the licensing interface between Polycom products and the
Polycom Licensing Server. Most RealPresence Clariti products can be licensed via the Polycom Licensing
Center.
Supported Network Devices
The RealPresence Resource Manager system supports these network device types:
Network Device
Service
Integration
SNMP
Monitoring
Licensing
Service
Group
Admin
RealPresence Collaboration Server
Yes
Yes
Yes (Virtual Edition Only)
Yes
Polycom MGC
Yes
No
No
No
RealPresence DMA system
Yes
Yes
Yes
Non-high availability
systems only
Yes
RealPresence Access Director
Yes
Yes
Yes
Yes
Polycom VBP
No
No
No
No
Acme SBC
No
No
No
No
RealPresence Web Suite
No
Yes
Yes
Yes
RealPresence Media Suite
No
No
Yes
No
Cisco Unified Communications
Manager
Yes
No
No
No
Polycom, Inc.
45
Understanding Network Device Management
Viewing Network Devices
Go to Network Device > Instances to view a list of all manageable and registered network devices. You
can add, edit, or delete network devices here. You can click to filter the list by the following device types.
● VBP (Video Border Proxy systems)—Displays the list of Polycom VBP systems registered to the
RealPresence Resource Manager system.
● ACME SBC (Session Border Control systems)—Displays the list of SBC systems registered to the
RealPresence Resource Manager system.
● RealPresence Collaboration Server/MGC (MCU)—Displays the list of Polycom MCUs registered
to the RealPresence Resource Manager system.
● RealPresence DMA—Displays the RealPresence DMA system registered to the RealPresence
Resource Manager system.
● RealPresence Access Director—Displays the list of RealPresence Access Director systems
registered to the RealPresence Resource Manager system.
● RealPresence Web Suite Services/Experience Portal—Displays the list of RealPresence Web
Suite Service Portals and Experience Portals registered to the RealPresence Resource Manager
system.
● Cisco Unified Communications Manager—Displays the information related to the Cisco Unified
Communication Manager, if integrated with the RealPresence Resource Manager system.
● RealPresence Media Suite—Displays the list of RealPresence Media Suite licensed by the
RealPresence Resource Manager system.
Polycom, Inc.
46
Managing Instances
An instance is a Polycom video infrastructure component (network device) that runs on a virtual machine or
a hardware appliance. When you add a component to the RealPresence Resource Manager system, you
can choose to use RealPresence Resource Manager to monitor the alarms, manage licensing for the
components, or/and integrate this component with the RealPresence Resource Manager system. You can
add both virtual and appliance edition products as instances in RealPresence Resource Manager.
If you work under vCenter environment, see Appendix A: Working in a vCenter Environment on how
to manage instances, images, and providers.
View Network Device Instance
By default, all the instances that you have added are displayed on the Instances page.
To view network device instances:
1 Go to Network Device > Instances.
2 Click
to filter the instances that you want to display. You can filter instances by Device Type,
Device Name, IP Address, or Site.
3 Select an instance that you want to view.
4 Click
to display a summary of this instance.
The Network Device list has the following fields:
Field
Description
Status
The state of the network device. Possible values include:
• Online
• Offline
• Unknown
• Device warnings
Click this icon to go to the Alert View page.
• Service Integrated
RealPresence Resource Manager uses ICMP to probe the status of instances.
Device Name
The system name of the network device.
Device Type
The type of network device.
IP Address
The IP address assigned to the network device.
Polycom, Inc.
47
Managing Instances
Field
Description
Site
The site to which the network device belongs.
Note
When areas are enabled on your system, this field shows a value of Restricted if
you do not have permission to manage the area to which the site is assigned.
Area
Available only when Areas are enabled. The area with which the network device is
associated.
Users can only view area information for the areas they have been assigned to
manage.
Add an Instance by IP
You can add existing appliance instances and virtual instances by IP address. Before you add an instance,
verify that you are using the correct IP address and that the instance is running and accessible from its own
user interface.
To add an existing instance by its IP address:
1 Go to Network Device > Instances.
2 Click
.
3 Select a device type that you want to add.
Based on the selected device type, you may see different fields under the Device Type tab. For most
device types, you need to provide Device Name, Version, IP Address, Admin User, and Admin
Password.
The format of Version is X.X.X. X and must be all numbers. For example, 6.4.0 is a correct version
number but v6.4.0 is incorrect.
4 For the device types that can be integrated, you will see the Service Integration tab, select the
check box under this tab to enable service integration.
5 For the device types that can be licensed, you will see the License Configuration tab, select the
Enable Licensing with the Polycom License Server check box to enable licensing.
6 Select IP or FQDN Address from the Add By drop-down list.
7 Click OK to add the instance to the RealPresence Resource Manager system.
See the following chapters on how to add and configure different devices:
● Integrate RealPresence DMA: Add the RealPresence DMA system to RealPresence Resource
Manager system
● Integrate RealPresence Collaboration Server or MGC: Add an MCU Manually
● Integrate RealPresence Access Director: Manually Add a RealPresence Access Director System
● Integrate VBP: Add a Polycom VBP Device
● Integrate Acme SBC: Add an SBC Device
● Integrate CUCM: Add a Cisco Unified Communications Manager
See License Management for details about license management.
Polycom, Inc.
48
Managing Instances
If working under a vCenter environment, you need to add an instance by Provider. See Appendix A:
Working in a vCenter Environment for details.
Edit an Instance
You can edit an instance.
To edit an instance:
1 Go to Network Device > Instances.
2 Select an instance you want to edit.
3 Click
.
View an Instance
You can view the summary of an instance.
To view an instance:
1 Go to Network Device > Instances.
2 Select an instance you want to view.
3 Click
.
Delete an Instance
You can delete an instance.
To delete an instance:
1 Go to Network Device > Instances.
2 Select the instance you want to delete.
3 Click
.
4 Click OK to confirm the deletion.
Polycom, Inc.
49
Managing Service Groups
A service group is a logical collection of hardware appliances and/or virtual machine instances that are
configured to work together. A service group might consist of a RealPresence DMA instance, one or more
RealPresence Collaboration Server Systems, RealPresence Web Suite Services and Experience Portals,
and others.
The instances in a service group are typically configured to work together to provide video collaboration
services to the users of various Polycom audio and video collaboration systems in your organization’s
locales. A service group could represent a service provider creating a group that serves a particular
enterprise, one campus of an enterprise, a division or geographical locale within a company, or any other
group recognized by your organization. With these related instances placed in a logical group, they can be
monitored as a unit and measured to determine usage statistics.
With a service group, you can manage and monitor multiple types of instances on a single map and view a
graphical representation of their usage.
The service group map allows you to navigate to any Polycom network device within the service group.
When you navigate to a network device to manage it, you can view the web interface for that network device
in a new tab on your browser. For example, if you have a RealPresence DMA system within your service
group, you can access the RealPresence DMA system from the service group map. The RealPresence
DMA system’s web interface displays in a new tab on your browser.
You can also set service group-level settings such as time settings, SNMP, and Active Directory integration.
This section includes the following topics:
● Configuring Common Settings for a Service Group
● Click OK.
● Managing Service Groups
Configuring Common Settings for a Service Group
You can configure common settings for a service group. When you configure settings at the service group
level, all Polycom products within the service group inherit those settings from the service group settings.
You can configure time settings, SNMP, and Active Directory integration at the service group level.
Polycom RealPresence Collaboration Server 8.5 does not support the common settings.
This section includes the following topics:
● Configure Time Settings for a Service Group
● Configure SNMP Settings for a Service Group
Polycom, Inc.
50
Managing Service Groups
● Integrate a Service Group with Enterprise Directory
Configure Time Settings for a Service Group
To configure the time settings for a service group, you can configure the group to use an NTP server
(recommended) or manually set the system time settings for the service group systems.
The common time settings only apply to the following servers in a service group:
● Polycom RealPresence Resource Manager
● Polycom RealPresence DMA
● Polycom RealPresence Access Director
● Polycom RealPresence Collaboration Server
● Polycom RealPresence Web Suite
To configure time settings for network device service group:
1 Go to Network Device > Service Groups.
2 Select the service group you want to configure from the Service Group drop-down list in the right
corner of the screen.
3 Click Time Settings.
The Time Settings dialog box displays.
4 In the Time Settings dialog, select a time zone from the System Time Zone drop-down list.
5 To use an NTP server:
a Select the Use NTP Server radio button.
b Add the IP address or host name of the server you want to use.
6 To use the system time:
a Select the Use System Time radio button.
b Configure the system date and time using the fields provided.
7 Click OK.
Configure SNMP Settings for a Service Group
You can configure what version of SNMP to use as well as set up notification receivers to help you track
network device activities.
The SNMP settings only apply to the following servers in a service group:
● Polycom RealPresence Resource Manager
● Polycom RealPresence DMA
● Polycom RealPresence Collaboration Server
● Polycom RealPresence Web Suite
Polycom, Inc.
51
Managing Service Groups
To enable SNMP for a service group:
1 Go to Network Device > Service Groups.
2 Select the service group you want to configure from Service Group drop-down list in the right
corner of the screen.
3 Go to SNMP Settings.
4 Select the Enable SNMP monitoring check box.
5 In the Agent Settings area, configure the following:
Setting
Description
SNMP Version
Specifies the version of SNMP you want to use.
v2c–Used for standard models. Uses community-based authentication.
v3–Used when you want a high security model. Requires a security user for
notifications.
Transport
Specifies the transport protocol for SNMP communications. SNMP can be
implemented over two transport protocols:
TCP–This protocol has error-recovery services, which assures message
delivery, and messages are delivered in the order they were sent. Some
SNMP managers only support SNMP over TCP.
UDP–This protocol does not provide error-recovery services, message
delivery is not assured, and messages are not necessarily delivered in the
order they were sent.
Because UDP doesn't have error recovery services, it requires fewer network
resources. It is well suited for repetitive, low-priority functions like alarm
monitoring.
Port
Specifies the port that the RealPresence Resource Manager system uses for
general SNMP messages. By default, the RealPresence Resource Manager
system uses port 161.
Community
For SNMPv2c, specifies the context for the information, which is the SNMP
group to which the devices and management stations running SNMP belong.
The RealPresence Resource Manager system has only one valid context
(public by default), which is identified by the Community name. The
RealPresence Resource Manager system will not respond to requests from
management systems that do not belong to its community.
Local Engine Id
For SNMPv3 only.
Displays the RealPresence Resource Manager system contextEngineID for
SNMPv3.
Security User
For SNMPv3 only.
Specifies the security name required to access a monitored MIB object.
You must first add a security user before you can select a user from the
drop-down list.
This name cannot be snmpuser.
6 Click Update.
Polycom, Inc.
52
Managing Service Groups
7 In the Notifications Setting area, click
.
You can configure the network devices in the service group to send SNMP messages to one or more
notification receivers (e.g., a network management system).
8 Configure the settings in the Notification Settings dialog box.
Field
Description
Enable agent
Select to enable the notification agent.
Clear to stop using this agent without deleting it.
Transport
The transport protocol for SNMP communications to the host receiver (TCP or UDP).
Address
The IP address of the host receiver (the SNMP manager to which this agent sends
notifications).
Port
The port that the RealPresence Resource Manager system uses to send
notifications. Default port–162
Notification type
The type of notification that this agent sends to the notification receiver:
• Inform–The agent sends an unsolicited message to a notification receiver and
expects or requires the receiver to respond with a confirmation message.
• Trap–The agent sends an unsolicited message to a notification receiver and does
not expect or require a confirmation message.
SNMP version
The version of SNMP used for this agent (v2c or v3).
Security user
For SNMP v3, the user name of the security user authorized to actively retrieve
SNMP data.
9 Click OK.
The agent appears in the Notification Setting list.
10 If you are using SNMPv3, add a security user. Click
security user.
in the Security User area to add a
Security users are only required if you are using SNMPv3. If you are not using SNMPv3, you can skip
these steps.
11 Configure the following settings in the Add Security User dialog box.
Field
Description
Security user
The user name of the security user authorized to actively retrieve SNMP data.
Authentication type
The authentication protocol used to create unique fixed-sized message digests of a
variable length message.
The RealPresence Resource Manager system implements communication with
authentication and privacy (the authPriv security level, as defined in the USM MIB).
Authentication type options:
• MD5–Creates a digest of 128 bits (16 bytes)
• SHA–Creates a digest of 160 bits (20 bytes)
Both methods include the authentication key with the SNMPv3 packet and then
generate a digest of the entire SNMPv3 packet.
Polycom, Inc.
53
Managing Service Groups
Field
Description
Authentication password
Confirm password
The authentication password that’s used, together with the local engine ID, to create
the authentication key included in the MD5 or SHA message digest.
Encryption type
The privacy protocol for the connection between the RealPresence Resource
Manager system and the SNMP agent.
Encryption type options:
• No encryption
• DES–Uses a 56-bit key with a 56-bit salt to encrypt the SNMPv3 packet
• AES–Uses a 128-bit key with a 128-bit salt to encrypt the SNMPv3 packet
Encryption password
Confirm password
The password that’s used, together with the local engine ID, to create the encryption
key used by the privacy protocol.
12 Click OK.
The user is displayed in the Notification Users list.
13 When finished configuring SNMP, click OK.
Integrate a Service Group with Enterprise Directory
When you integrate a service group with Enterprise Directory, you integrate each network device within the
service group with the same Enterprise Directory server and settings.
The Enterprise Directory Integration settings only apply to the following servers in a service group:
● RealPresence DMA
● RealPresence Resource Manager
● RealPresence Web Suite
After you enable the Enterprise Directory integration on RealPresence Web Suite Services Portal,
you cannot disable the integration.
To integrate a service group with Active Directory:
1 Go to Network Device > Service Groups.
2 Select the service group you want to configure from Service Group drop-down list in the right
corner of the screen.
3 Click Enterprise Directory Integration.
The Enterprise Directory Integration dialog box displays.
4 Select the Integrate with Enterprise Directory check box.
5 In the Enterprise Directory Server DNS Name section, choose one of the following:
 Select the Auto-discover radio button to have the systems auto-discover the server by querying
DNS.
 Select the FQDN radio button and manually input the FQDN enterprise directory server.
6 As needed, configure these settings.
Polycom, Inc.
54
Managing Service Groups
Setting
Description
Domain\Enterprise Directory User
ID
Domain and Enterprise Directory User ID for an account that the
RealPresence Resource Manager system can use to access the enterprise
directory server and retrieve group, user, and room information.
This User ID must have read permissions so it can search the entire forest on
the enterprise directory server.
This User ID is automatically associated with the RealPresence Resource
Manager system administrator role - by default it is the ONLY enterprise
directory User ID with this role.
Enterprise Directory User
Password
The password for the enterprise directory user account.
Security Level
The level of security on the connection between the RealPresence Resource
Manager system and the enterprise directory server. Possible values include:
• Plain No security on the connection.
• LDAPS The connection is secured over outbound port 3269 using
LDAP-S in a manner similar to https.
If the “Domain Controller: LDAP Server signing requirements” setting on
the Active Directory server is set to “Require Signing”, then you must use
LDAPS to secure the connection.
• StartTLS The connection is secured over outbound port 3268 (the same
port as Plain), but it then negotiates security once the socket is opened.
Some LDAP servers reject any unsecured transactions, so the first
command is the StartTLS negotiation command.
Use LDAP Filter
Specifies which user accounts to include (an underlying, non-editable filter
excludes all non-user objects in the directory). The default expression
includes all users that don’t have a status of disabled in the directory.
Enterprise Directory Search
BaseDN
If necessary and you understand the filter syntax, specify the top level of the
enterprise directory tree (referred to as the base DN) to search. Don’t edit
these expressions unless you understand the filter syntax.
Directory Attribute
Specify custom Active Directory Attributes. See Using Custom Active
Directory Attributes for details.
Characters to Remove
This field is only for RealPresence DMA.
You might need to strip characters from a phone number field’s value to
ensure a numeric conference room ID.
The default string includes \t, which represents the tab character. Use \\ to
remove backslash characters.
If generating alphanumeric conference room IDs, remove the following:
()&%#@|"':;,
Single spaces in the source field are preserved, but multiple consecutive
spaces are concatenated to one space.
7 Click OK.
Polycom, Inc.
55
Managing Service Groups
Manage a Network Device within a Service Group
The service group map allows you to navigate to any Polycom network device within the service group.
When you navigate to a network device to manage it, you can view the web interface for that network device
in a new tab on your browser. For example, if you have a RealPresence DMA system within your service
group, you can access the RealPresence DMA system from the service group map. The RealPresence
DMA system’s web interface displays in a new tab on your browser.
You can manage the following RealPresence products:
● RealPresence DMA
● Polycom RealPresence Access Director
● Polycom RealPresence Collaboration Server
● RealPresence Web Suite Services Portal
To manage a network device from the Service Group map:
1 Go to Network Device > Service Group.
The Service Group map displays.
2 Within the map area, Select the network device you want to manage.
3 At the top of the screen, click Manage at the top of the screen.
The web interface for the selected network device displays on a new tab in your browser.
Managing Service Groups
With a service group, you can manage and monitor multiple types of instances on a single map and view a
graphical representation of their usage.
This section includes the following topics:
● Create a Service Group
● Edit Service Group Details
Create a Service Group
Create a service group to designate appliance and virtual instances that together provide a distinct service
within your organization.
To add a new service group to the RealPresence Resource Manager system:
1 Go to Instance Deployment > Service Groups and click Add Service Group.
2 Enter a Name and Description for the new service group.
3 Click the Instance tab.
4 In the Available section, select the instance(s) that you want to add to the service group and click
the arrow icon to move the list to the Selected section.
5 Click OK to add the new service group to the list.
Polycom, Inc.
56
Managing Service Groups
Edit Service Group Details
You can edit the name and/or description of an existing service group.
To edit a service group:
1 Go to Instance Deployment > Service Groups.
2 Select the Service Group you want to edit from the Service Group drop-down list from the top-right
conner.
3 Click
besides the service group that you selected.
4 Update the Name and Description fields as necessary.
5 Add or remove instances as necessary.
6 Click OK to confirm the changes.
Delete Service Group
You can delete the existing service groups that you created.
To delete a service group:
1 Go to Instance Deployment > Service Groups.
2 Select the Service Group you want to delete from the Service Group drop-down list from the
top-right corner.
3 Click
besides the service group that you selected.
4 Click OK to confirm the delete.
Polycom, Inc.
57
Service Configuration
This section includes the topics needed to configure services for the RealPresence Resource Manager
system video conference scheduling functionality and operations. It includes:
● Service Integration with a RealPresence DMA System
● Service Integration with Session Border Controllers
● Service Integration with Bridges
Polycom, Inc.
58
Service Integration with a RealPresence
DMA System
This section describes how to integrate your system with a RealPresence® DMA system. It includes the
following topics:
● Integration Overview
● Integrating with a RealPresence DMA Supercluster
● Managing a RealPresence DMA System
● Working with RealPresence DMA Pool Orders
● Working with Endpoints Synchronized from a RealPresence DMA System
● RealPresence DMA Conference Templates
Integration Overview
You can integrate your RealPresence Resource Manager system with a single RealPresence DMA system
to take advantage of the RealPresence DMA system’s two main functions: the Conference Manager
function and the Call Server (gatekeeper and SIP proxy/registrar) function.
● Conference Manager
 Provides a highly reliable and scalable multi-point conferencing solution that distributes voice and
video calls across multiple media servers (MCUs), creating a single seamless resource pool. The
system essentially behaves like a single large MCU, which greatly simplifies video conferencing
resource management and improves efficiency.
 Supports up to 64 MCUs. MCUs can be added on the fly without impacting end users and without
requiring re-provisioning.
● Call Server
 Provides complete endpoint registration and call routing services for both H.323 and SIP
protocols. It also serves as a gateway between H.323 and SIP, enabling enterprises with legacy
H.323 devices to transition to SIP in a gradual, orderly, and cost-effective manner.
 Provides bandwidth management, and can be integrated with a Juniper Networks Session and
Resource Control Module (SRC) to provide bandwidth assurance services.
 Comes with a default dial plan that covers many common scenarios, which can easily be modified.
 Makes it possible for multiple UC environments and different video conferencing technologies to
be unified across the network into a single dial plan.
See Polycom RealPresence DMA 7000 System Operations Guide for more information.
This section includes the following topics that discuss some of the considerations when integrating a
RealPresence DMA system with your RealPresence Resource Manager system.
● Dedicated User Account for Integration
Polycom, Inc.
59
Service Integration with a RealPresence DMA System
● NTP Servers
● MCU Management
● Conference Types Supported By the RealPresence DMA system
● Considerations for Site Topology
● Scheduling Capacity
● Integrating with a RealPresence DMA Supercluster
Dedicated User Account for Integration
When you integrate with a RealPresence DMA system you need to use a RealPresence DMA user account
to authenticate the RealPresence Resource Manager system with the RealPresence DMA system. This
RealPresence DMA user account needs to meet the following requirements:
● Must have the Administrator role.
● Must be assigned gold class of service.
● Must be reserved only for integration with the RealPresence Resource Manager system.
You can also use this user account to help you track VMRs created when you schedule pooled conferences.
Any created VMRs will be associated with the RealPresence DMA user you use to integrate with the
RealPresence Resource Manager system.
NTP Servers
It’s important that you configure the RealPresence Resource Manager system and the RealPresence DMA
system to use the same NTP server. This ensures that each has the same network time as the other and
scheduled conferences start when intended.
MCU Management
A Polycom MCU system can be managed by the RealPresence Resource Manager system or the
RealPresence DMA system, not both.
If your video network includes MCUs that are managed by RealPresence Resource Manager in addition to
MCUs managed by the RealPresence DMA system, you may want to use a naming convention that includes
a qualifier that indicates to the RealPresence DMA system administrator that the MCU is directly registered
to the RealPresence Resource Manager system; for example, ResourceManager_RMX10.
Conference Types Supported By the RealPresence
DMA system
When you integrate your RealPresence Resource Manager system with a RealPresence DMA system the
following RealPresence Resource Manager system conference types are supported.
● Anytime Conferences are conferences that are initiated when the conference owner dials in and
where most other participants are dial-out participants. Conference templates for anytime
conferences are created and maintained on the RealPresence DMA system.
Polycom, Inc.
60
Service Integration with a RealPresence DMA System
● Pooled Conferences are conferences that are scheduled on resources managed by the
RealPresence DMA system. Conference templates for pooled conferences are created and
maintained on the RealPresence DMA system.
RealPresence DMA Conference Templates
You need to have created RealPresence DMA conference templates for schedulers to use when scheduling
either a pooled conference (future) or anytime conference. You do this in the RealPresence DMA system.
As a best practice, use a naming convention that helps identify the appropriate use for the conference
template. For example, you can name conference templates intended for anytime conferences with an
“anytime” prefix such as anytime_corptemplate.
Multi-Tenancy Considerations
RealPresence DMA system conference templates are not area-aware, which means they cannot be
associated with a particular area. An area scheduler can select any RealPresence DMA system conference
template to use for a conference.
As a best practice, you should use a naming convention that helps the scheduler identify the correct
template to use for his area conferences.
Considerations for Site Topology
When integrated with the RealPresence Resource Manager system, the RealPresence DMA system
inherits site topology settings from the RealPresence Resource Manager system. Site topology
configuration for both products is managed by a RealPresence Resource Manager system user with the
administrator role.
You should plan your site topology with RealPresence DMA system needs in mind. For example, when your
RealPresence DMA system uses a supercluster environment, territories have specific functional roles. It’s
important to work with your RealPresence DMA system administrator to ensure the site topology meets your
environments needs.
When your RealPresence Resource Manager system is integrated with a RealPresence DMA system, you
need to configure the primary node of the Resource Manager Default territory to be the appropriate
RealPresence DMA cluster after you integrate with a RealPresence DMA system.
See the Polycom RealPresence DMA 7000 System Operations Guide for more information.
Scheduling Capacity
When you integrate your system with a RealPresence DMA system, you can tune the scheduling capacity
of the RealPresence DMA system. You do this through the RealPresence Resource Manager system.
The number of ports used for a conference can vary according to the MCU that hosts the conference and
the number/type of endpoints that join. Because schedulers can only choose from a pre-configured
RealPresence DMA system pool order when scheduling pooled conferences, they rely on an administrator
to tune the RealPresence DMA system’s scheduling capacity to ensure efficient use of resources.
There are three ways an administrator can assess RealPresence DMA system scheduling capacity:
Polycom, Inc.
61
Service Integration with a RealPresence DMA System
● View conference reports from the RealPresence DMA system. This method is preferred and provides
the most accurate information.
● Monitor ongoing conferences to assess if resources were underbooked.
● View information on RealPresence Resource Manager CDR reports to review individual conferences.
Polycom recommends setting the RealPresence DMA system scheduling capacity more conservatively at
first and then tuning for increased conference activity.
See Edit a RealPresence DMA system on page 65.
Integrating with a RealPresence DMA Supercluster
You can integrate with a RealPresence DMA system that is deployed as a supercluster that uses
single-node clusters. Polycom does not support Integrating with a RealPresence DMA superclustered
system that uses two-server clusters at this time.
Integrating with a RealPresence DMA system
You can integrate with a RealPresence DMA system. After your system is integrated with a RealPresence
DMA, the RealPresence Resource Manager automatically detects any changes to the RealPresence DMA
system’s superclusters without needing to re-integrate.
RealPresence Resource Manager system users with the Device Administrator role can add a RealPresence
DMA system to a RealPresence Resource Manager system.
Integrating with a RealPresence DMA system involves the following tasks.
● Create a Dedicated User Account on the RealPresence DMA system
● Add the RealPresence DMA system to RealPresence Resource Manager system
● Configure the Default Territory
Create a Dedicated User Account on the RealPresence
DMA system
When you integrate with a RealPresence DMA system you need to use a RealPresence DMA user account
to authenticate the RealPresence Resource Managersystem with the DMA system. This DMA user account
needs to meet the following requirements:
● Must have the Administrator role
● Must be assigned gold class of service.
● Must be reserved only for integration with the RealPresence Resource Manager system.
To create the RealPresence DMA user account:
» Log into the RealPresence DMA system and create the appropriate user account.
For more information on creating user accounts for the RealPresence DMA system, see Polycom
RealPresence DMA System Operations Guide.
Polycom, Inc.
62
Service Integration with a RealPresence DMA System
Add the RealPresence DMA system to RealPresence
Resource Manager system
You need to integrate with the RealPresence DMA system by adding it to your RealPresence Resource
Manager system. You can add a single RealPresence DMA system for service integration and license
management. A local RealPresence DMA system cluster can also be added to RealPresence Resource
Manager for service integration.
To add a RealPresence DMA system, you should be a Device Administrator for the RealPresence Resource
Manager system.
You can add a RealPresence DMA system by IP address or by existing provider:
● Add a RealPresence DMA System by IP Address
When adding by IP address, you can choose to use RealPresence Resource Manager to do the
license management or not from the License Configuration tab.
● (vCenter Only) Add a RealPresence DMA System by Provider
See Appendix A: Working in a vCenter Environment on how to add new or existing RealPresence
DMA instance by provider under vCenter environment.
To add a RealPresence DMA system by IP address:
1 Ensure your RealPresence DMA system is reachable via ICMP.
2 Go to Network Device > Instances and click
.
3 Select RealPresence DMA as Device Type.
4 Select IP or FQDN Address in the Add By drop-down list.
5 Specify the parameters in the table below.
Field
Description
Device Type
Name
A unique name for the RealPresence DMA system.
Version
The version of the RealPresence DMA system.
Management Address
The virtual IP address or FQDN for the RealPresence DMA system.
For RealPresence DMA systems with multiple clusters, indicate the FQDN or
virtual IP of the cluster you want to use.
If your RealPresence DMA system is configured for a super cluster, be sure to
use the Virtual IP address for a cluster that is co-located with the
RealPresence Resource Manager system.
Admin User
The RealPresence DMA system user you use to authenticate the
RealPresence DMA system must have the Administrator role and gold class
of service. You should use a RealPresence DMA user that is reserved only for
integration with the RealPresence Resource Manager system.
Admin Password
Service Integration
Polycom, Inc.
63
Service Integration with a RealPresence DMA System
Field
Description
Integrate RealPresence DMA
system’s conference manager
and call server services with
RealPresence Resource
Manager system’s
conferencing and endpoint
services.
Select this check box to enable service integration.
Conference Manager (MCU
Pool Orders)
A check mark displays if the RealPresence DMA system has been enabled for
MCU pool orders (conference management).
Call Server
A check mark displays if the RealPresence DMA system has been enabled for
use as a call server (gatekeeper).
When you mark this check box, the site topology set up for the RealPresence
Resource Manager system will be synchronized to the RealPresence DMA
system. In addition, H.323 endpoints registered to the RealPresence DMA
system will be synchronized to the RealPresence Resource Manager system.
Scheduling Capacity
The percentage of available ports to schedule for this RealPresence DMA
system.
Support DMA Supercluster
Select this box if your RealPresence DMA system has been deployed as a
supercluster.
You must check this box if you want the RealPresence Resource Manager
system to take advantage of the RealPresence DMA system’s failover system
and integrate with a backup RealPresence DMA cluster if the primary
RealPresence DMA cluster goes down.
6 Click the Servers tab to specify a RealPresence DMA HA cluster if needed.
7 In the Available section, select the server(s) and click the arrow icon to move the list to the
Selected section.
8 Select the two servers in the Selected section.
9 Click OK. RealPresence Resource Manager will search the RealPresence DMA system. if it cannot
find the RealPresence DMA system, it will report an error.
The RealPresence DMA system appears in the Network Instance list.
For more information about scheduling capacity, see Scheduling Capacity.
Configure the Default Territory
You should configure the Resource Manager Default territory to be the primary RealPresence DMA cluster
after you integrate with a RealPresence DMA system.
To configure the default territory:
1 Go to Network Topology > Territories.
2 Select the Default Resource Manager Territory.
3 Click
Polycom, Inc.
.
64
Service Integration with a RealPresence DMA System
4 In the Edit Territory dialog, select a RealPresence DMA cluster to use from the Primary Cluster
drop-down list.
5 Click OK.
Managing a RealPresence DMA System
If your RealPresence Resource Manager is integrated with a RealPresence DMA system, you can view
details about the system, edit the integration settings, as well as delete the integration.
This section includes the following topics:
● Edit a RealPresence DMA system
● Change the Service Integration for a RealPresence DMA system
Edit a RealPresence DMA system
You must have the Device Administrator role in order to edit a RealPresence DMA system.
To edit a RealPresence DMA system:
1 Go to Network Device > Instances.
2 Select the RealPresence DMA system and click
.
3 In the Edit DMA dialog, edit the properties of the RealPresence DMA system.
4 Click OK.
Change the Service Integration for a RealPresence
DMA system
You can change the service integration for a RealPresence DMA system. You can disintegrate it from the
RealPresence Resource Manager system. When you do this, you can no longer use the DMA Pool Orders
associated with the RealPresence DMA system for conferences. In addition, DMA-synced endpoints that
have not been associated with users can no longer be monitored or managed by the RealPresence
Resource Manager system.
You must have the Device Administrator role in order to change the service integration for a RealPresence
DMA system.
To delete a RealPresence DMA system from a RealPresence Resource Manager system:
1 Go to Network Device > DMA.
2 Select the RealPresence DMA system and click
.
3 Click OK to confirm the deletion.
Polycom, Inc.
65
Service Integration with a RealPresence DMA System
Working with RealPresence DMA Pool Orders
When the RealPresence Resource Manager system is configured to work with a RealPresence DMA
system, conference schedulers can schedule conferences on RealPresence DMA system pool orders. DMA
Pool Orders are groups of MCU pools that are hierarchically organized.
RealPresence DMA system pool orders associated with your configured RealPresence DMA system are
automatically displayed in the RealPresence Resource Manager system.
The RealPresence DMA system administrator is responsible for setting up pool orders to be used. You
should work with your RealPresence DMA system administrator to determine the specifics about the pool
orders associated with your RealPresence DMA system. This information can also be useful for schedulers
who need to choose a pool order to use for a conference.
Some uses for RealPresence DMA system pool orders:
● The RealPresence DMA system administrator can put all MCUs in a specific site or domain into a
pool. Then, assign a pool order to all users in that site or domain (via group membership) ensuring
that their conferences are preferentially routed to MCUs in that pool.
● The RealPresence DMA system administrator could put one or more MCUs into a pool to be used
only by executives, and put that pool into a pool order associated only with those executives’
conference rooms.
● The RealPresence DMA system administrator could put MCUs with special capabilities into a pool,
and put that pool into a pool order associated only with custom conference rooms requiring those
capabilities.
For more information about pool orders, see the Polycom DMA 7000 System Operations Guide.
This section includes the following topics:
● View Details of a RealPresence DMA system Pool Order
● Associate a RealPresence DMA system Pool Order with an Area
View Details of a RealPresence DMA system Pool
Order
After you integrate your RealPresence Resource Manager system with a RealPresence DMA system, you
can view RealPresence DMA system pool orders that are available for scheduling. For example, you can
see how many ports are available in a pool order.
You cannot modify any properties of these pool orders through the RealPresence Resource Manager
system. RealPresence DMA system pool orders are created on the RealPresence DMA system by a
RealPresence DMA system administrator.
To view details a RealPresence DMA system Pool Order:
1 Go to Network Device > Instances.
2 Select a RealPresence DMA from the list.
3 Click More > DMA Pool Orders.
The DMA Pool Order Details dialog lists the details for pool orders on the selected RealPresence
DMA system. These details are configured on the RealPresence DMA system and cannot be
modified with the RealPresence Resource Manager system.
Polycom, Inc.
66
Service Integration with a RealPresence DMA System
Column
Description
Name
The unique name to identify the RealPresence DMA system Pool Order.
Actual Capacity
The total number of ports included in this RealPresence DMA system Pool
Order.
Scheduling Capacity
The number of ports available to schedule for this RealPresence DMA system
Pool Order. This number matches the scheduling capacity percentage that
was configured for this RealPresence DMA system.
4 Click Close.
Associate a RealPresence DMA system Pool Order
with an Area
When you associate a pool order with a specific area, only users belonging to that area (or able to manage
the area) can schedule conferences for that RealPresence DMA system pool order.
You need the Device Administrator role to associate a DMA pool order with an area.
Schedulers and area schedulers cannot select particular resources on which to schedule conferences.
To associate a RealPresence DMA system Pool Order with an Area:
1 Go to Network Device > Instances.
2 Select a RealPresence DMA from the list.
3 Click More > DMA Pool Orders.
4 Select the DMA Pool Order of interest and click Associate Areas.
5 In the Available Areas section, select and move the desired area(s) to Selected Areas list. You
can move the unwanted are(s) to the Available Areas list. Press Shift-click or Ctrl-click to select
multiple items in the list.
You must have the Device Administrator role to associate a RealPresence DMA system pool order
with an area. The Available Areas list is limited to the areas that you manage.
6 Click OK.
Working with Endpoints Synchronized from a
RealPresence DMA System
H.323 endpoints registered with the RealPresence DMA system’s gatekeeper automatically display in a
RealPresence Resource Manager system that has been configured with a RealPresence DMA system,
using both the RealPresence DMA system’s call server and conference manager. This allows you to track
the endpoints registered to the RealPresence DMA system.
Once RealPresence DMA-registered endpoints are synchronized to the RealPresence Resource Manager,
you can include them in scheduled management operations such as provisioning and scheduled software
updates. RealPresence DMA-registered endpoints are synchronized daily at 1 a.m. to ensure that endpoint
Polycom, Inc.
67
Service Integration with a RealPresence DMA System
data remains consistent between the RealPresence DMA system and the RealPresence Resource
Manager system. You can also modify the properties of RealPresence DMA system-synced endpoints.
If you want to schedule the RealPresence DMA endpoint in a conference, you must first associate the
endpoint with a user.
When you take any of the following actions for a RealPresence DMA system-synchronized endpoint,
RealPresence Resource Manager system considers the endpoint to be a non-dynamically managed
endpoint:
● Include the endpoint in a scheduled provisioning (may happen automatically)
● Include the endpoint in a scheduled software update
● Modify the properties of the endpoints (including associating a user)
● Add the endpoint to an address book
If the RealPresence DMA administrator deletes an endpoint from the RealPresence DMA system, it will also
be cleared from displaying in the RealPresence Resource Manager system. RealPresence
DMA-synchronized endpoints that you have associated with a user, scheduled in a conference, or
provisioned will not be cleared during a RealPresence DMA action. Endpoints that you have started to
manage in any way are seen by RealPresence Resource Manager as managed endpoints. If you want to
remove them, you need to do so using the RealPresence Resource Manager system.
Each synchronized RealPresence DMA-registered endpoint consumes a video endpoint license in the
RealPresence Resource Manager system.
Unique H.323 Aliases Required
In order for a RealPresence DMA-registered endpoint to synchronize and display in the RealPresence
Resource Manager system, it must have a unique H.323 alias. If any managed endpoint in the
RealPresence Resource Manager system has the same H.323 alias as a RealPresence DMA-registered
endpoint, the DMA-registered endpoint information will not display.
There is no automatic way to ensure unique H.323 aliases between RealPresence DMA-registered
endpoints and endpoints directly managed by the RealPresence Resource Manager system. To determine
if there is any overlap, you can export a list of the user-reserved H.323 aliases from the RealPresence
Resource Manager system and do a comparison with those listed in your RealPresence DMA system. For
more information on exporting user dialing information, see Export User Aliases.
SIP-only endpoints that register with the RealPresence DMA system instead of the RealPresence
Resource Manager system’s provisioning service do not display in the RealPresence Resource
Manager system. You must manually add them to the RealPresence Resource Manager system in
order to manage the endpoints.
This section includes the following topics:
● Monitor RealPresence DMA-Synchronized Endpoints
● Schedule RealPresence DMA-Synchronized Endpoints in Conferences
● Licensing RealPresence DMA-Synchronized H.323 Endpoints
Polycom, Inc.
68
Service Integration with a RealPresence DMA System
Monitor RealPresence DMA-Synchronized Endpoints
You can monitor H.323 endpoints that are synchronized from the RealPresence DMA system.
To monitor RealPresence DMA-synchronized endpoints:
1 Go to Endpoint > Monitor View.
2 Use the Mode column to determine if an H.323 endpoint has been synchronized from the
RealPresence DMA system. DMA-synchronized endpoints display with the following icon:
.
3 Optionally, you can filter the endpoint list to include only RealPresence DMA-Synced Endpoints.
a Click
.
b Click the Type box and select DMA-Synced Endpoints from the displayed list.
Schedule RealPresence DMA-Synchronized Endpoints
in Conferences
If you associated a RealPresence DMA-synced endpoint with a user or room, you can also schedule that
associated endpoint in conferences when you schedule that user or room.
To associate an endpoint to a user:
1 Go to Endpoint > Monitor View.
2 As needed, click
to customize the Endpoint list.
3 Select the endpoint of interest.
4 Click More > Associate User.
5 In the Last Name or Room Name field of the Associate User dialog, enter all or part of the user’s
last name and click Search.
The system displays the list of user or rooms that meet your search criteria.
6 Select the user of interest and click Close.
For additional information about scheduling conferences, see Configure Conferencing.
Licensing RealPresence DMA-Synchronized H.323
Endpoints
Synchronized H.323 endpoints consume video endpoint licenses in the RealPresence Resource Manager
system. For this reason, the RealPresence Resource Manager system also has two thresholds that allow
you to manage how many RealPresence DMA-synced endpoints you can monitor.
● Threshold for Stopping Synchronization
● Threshold for Deleting Inactive Synchronized H.323 Endpoints
Polycom, Inc.
69
Service Integration with a RealPresence DMA System
Threshold for Stopping Synchronization
All H.323 endpoints that are registered to the RealPresence DMA system’s gatekeeper are synchronized to
the RealPresence Resource Manager system as soon as you integrate your system with a RealPresence
DMA system for both conference management and call server functions. Newly-registered endpoints
continue to synchronize with the RealPresence Resource Manager system. However, the RealPresence
Resource Manager system will stop synchronizing H.323 endpoints when 80 percent of your device licenses
have been consumed. The RealPresence Resource Manager also does not synchronize a RealPresence
DMA endpoint if it detects that the endpoint is now a non-dynamically managed endpoint in the
RealPresence Resource Manager system.
See Working with Endpoints Synchronized from a RealPresence DMA System.
Threshold for Deleting Inactive Synchronized H.323
Endpoints
The RealPresence Resource Manager automatically deletes inactive RealPresence DMA-synchronized
H.323 endpoints are when the total device licenses used by the RealPresence Resource Manager exceeds
90 percent. This ensures that you always have enough device licenses for active and dynamically-managed
endpoints. An endpoint is considered inactive when the RealPresence Resource Manager system detects
that the it is not registered with the gatekeeper, the directory, Exchange, or the presence service.
RealPresence DMA Conference Templates
Anytime conferences and conferences scheduled to take place on a DMA Pool Order use conference
templates that are created and managed in the RealPresence DMA system.
This section includes the following topics:
● RealPresence DMA System Conference Templates for Multi-Tenancy
● Establishing Naming Conventions for RealPresence DMA System Templates
● Considerations for Anytime Conference Templates
RealPresence DMA System Conference Templates for
Multi-Tenancy
RealPresence DMA system conference templates cannot be assigned to a specific area. Area schedulers
will be able to select from a list of all RealPresence DMA system templates, regardless of the area to which
they manage. You should implement a template naming convention to indicate to an area scheduler which
RealPresence DMA templates apply to his purview; for example, area1_template.
Establishing Naming Conventions for RealPresence
DMA System Templates
By default, all RealPresence DMA system conference templates are made available to conference
schedulers who have permission to create pooled conferences and anytime conferences. To differentiate
Polycom, Inc.
70
Service Integration with a RealPresence DMA System
which RealPresence DMA system conference templates should be used for which conferences, you should
implement a naming convention that informs the scheduler which conference template is appropriate.
Anytime Conference Templates
For example, you could prefix a template designed for use with anytime conferences with the word
“anytime”; for example, anytimeconf_standard, anytimeconf_autoterminate, anytimeconf_nochair,
and so on.
Considerations for Anytime Conference Templates
An anytime conference is initiated when the first person calls into the conference and triggers the hosting
bridge to dial-out to the remaining conference participants.
Once an Anytime conference is configured, conferences can be started at any time by authorized
participants. The following events occur when a new Anytime conference is added:
● A participant with scheduling permissions creates a new Anytime conference and the conference is
assigned a virtual meeting room (VMR) number.
● An Chairperson passcode is automatically generated and may be required to launch an Anytime
conference (depending on your conference template).The owner receives the owner passcode
needed to launch the conference via the meeting email.
● Depending on the conference template settings, all dial-out participants are automatically called
either when first participant dials the VMR number or the conference owner dials the VMR and enters
the owner passcode.
● If the conference template requires a chairperson, dial-in participants are placed on hold until
someone dials in and enters the chairperson passcode.
● The conference continues until all participants hang up the call, unless your template includes an
auto-terminate setting.
Configuring Auto-Terminate
Anytime conferences do not have designated start and end times. As a result, the conference may be left
open and the VMR in use if the last caller does not hang up. You can mitigate this occurrence by configuring
the RealPresence DMA conference template to use a RealPresence Collaboration Server profile that has
Auto-Terminate enabled.
For more information about RealPresence Collaboration Server profiles and how to use an existing
RealPresence Collaboration Server profile for a RealPresence DMA conference template, see Polycom
RealPresence DMA System Operations Guide.
Initiating Conference Dial-out
You can configure the RealPresence DMA system conference template to define who can trigger the
dial-out to participants. You use the Conference requires chairperson setting to determine when dial-outs
are initiated. Remember to use an intuitive naming convention for RealPresence DMA system conference
templates.
Polycom, Inc.
71
Service Integration with a RealPresence DMA System
● When you enable the Conference requires chairperson setting, the dial-out process will begin
when the chairperson dials into the conference. An example name for a template with this setting
could be Anytime Conference - Chair Starts Dial-Outs.
● If you do not select this check box, the dial-out process will begin when the first person dials into the
conference. No chairperson passcode is needed. An example name for a template with this setting
could be Anytime Conference - 1st Dial-in Starts Dial-Outs.
Polycom, Inc.
72
Service Integration with Session Border
Controllers
This section describes how to perform the RealPresence Resource Manager system network device
management tasks. It includes the following topics:
● Supported Session Border Controllers
● Managing Polycom VBP Devices
● Managing a Polycom RealPresence Access Director System
● Manually Add a RealPresence Access Director System
● Managing SBC Devices
Supported Session Border Controllers
The RealPresence Resource Manager system supports the following session border controllers for specific
signaling:
● Acme SBC (SIP endpoints only)
● Polycom VBP (H.323 endpoints only)
● RealPresence Access Director (both SIP and H.323 endpoints)
Managing Polycom VBP Devices
Polycom VBP devices, when installed at the edge of the operations center, secures critical voice, video, and
data infrastructure components including VoIP softswitches, video gatekeepers, gateways, media servers,
and endpoints.
The Polycom VBP 5300 or 6400 S/T platform has an access proxy feature that provides firewall traversal
that enables the RealPresence Resource Manager system dynamic management features across a firewall.
The Polycom Video Border Proxy (VBP) device management operations include these topics:
● Add a Polycom VBP Device
● Edit a Polycom VBP Device
● Delete a Polycom VBP Device
● Identify Endpoints Using the Polycom VBP Device
Add a Polycom VBP Device
You can add a Polycom VBP device to the RealPresence Resource Manager system.
Polycom, Inc.
73
Service Integration with Session Border Controllers
To add a Polycom VBP device:
1 Go to Network Device > Instances.
2 Click
.
3 Select VBP from the Device Type drop-down list.
4 Configure these settings.
Settings
Description
Name
A unique name to identify the Polycom VBP device.
Provider-side Proxy IP Address
The Private Network IP address for the Polycom VBP device.
Subscriber-side IP Address
The Public Network IP address for the Polycom VBP device.
5 Click OK.
You can also choose to add another Polycom VBP device.
The Polycom VBP device is added to the RealPresence Resource Manager system. However, more
configuration may be necessary for the device to operate in your network. For example, you will
probably need to as described in the next topic.
Edit a Polycom VBP Device
You can edit the settings of a Polycom VBP device.
To edit a Polycom VBP device:
1 Go to Network Device > Instances.
2 Click
and select VBP as Device Type.
3 Select the Polycom VBP device of interest and click
.
4 Configure these settings as needed in the Edit Instance dialog.
5 Click OK.
Delete a Polycom VBP Device
You can delete a Polycom VBP device from the RealPresence Resource Manager system.
To delete a Polycom VBP device:
1 Go to Network Device > Instances.
2 Click
and select VBP as Device Type.
3 Select the Polycom VBP device of interest and click
.
4 Click Yes to confirm the deletion.
Polycom, Inc.
74
Service Integration with Session Border Controllers
Identify Endpoints Using the Polycom VBP Device
This procedure identifies only Polycom® HDX® systems, Polycom® RealPresence® Group Series, Polycom
CMA Desktop, Polycom RealPresence Mobile, Polycom® RealPresence Desktop, Polycom® RealPresence
Debut™, and Polycom® VVX® systems have the following characteristics:
● Registered to the RealPresence Resource Manager system
● Using the Polycom VBP firewall
● Are dynamically managed
A Polycom HDX or legacy endpoint system in scheduled management mode, registered to the
RealPresence Resource Manager system, and using the Polycom VBP firewall may also be displayed
in the Endpoint list. This entry may represent multiple endpoints, since all Polycom HDX or legacy
endpoint system operating in scheduled management mode register with the same information.
To identify which endpoints are using the Polycom VBP firewall:
1 Go to Endpoint > Monitor View.
2 Click
and select IP Address.
3 Enter the provider-side IP address of the Polycom VBP device and press Search.
The Endpoint list displays the dynamically managed endpoints that are registered to the
RealPresence Resource Manager system and using the Polycom VBP firewall. All of the endpoints
display the same IP address, which is the Provider-side IP address of the Polycom VBP device.
However, the endpoints will have different aliases and owners.
Managing a Polycom RealPresence Access Director
System
With the RealPresence Access Director system, Polycom offers a software-based edge server to securely
route communication, management, and content through firewalls without requiring special dialing methods
or additional client hardware or software.
If your video infrastructure environment includes a RealPresence Access Director system, you must ensure that
your RealPresence Resource Manager system is aware of the RealPresence Access Director system. You need to
either dynamically manage or manually add the RealPresence Access Director system to your
RealPresence Resource Manager system.
For information about dynamically managing a RealPresence Access Director system, see Dynamically
Managing a RealPresence Access Director System.
Manually Add a RealPresence Access Director System
If you are not going to dynamically manage the RealPresence Access Director system, you can manually
add it to the RealPresence Resource Manager system.
When you manually add a RealPresence Access Director system, you will not be able to monitor its status
or view any call information for calls routed from the RealPresence Access Director system.
Polycom, Inc.
75
Service Integration with Session Border Controllers
When you use the RealPresence Resource Manager system to dynamically manage a RealPresence
Access Director system, you should not manually add it to your system.
To manually add a RealPresence Access Director system:
1 Create a site that includes the subnet on which the RealPresence Access Director system resides.
You cannot use the same site for more than one RealPresence Access Director system. You must
create a unique site for each RealPresence Access Director system that you use.
See Add a Site.
2 Go to Network Device > Instances and click
.
3 Select RealPresence Access Director from the Device Type drop-down list.
4 Select IP or FQDN Address form the Add By drop-down list.
5 Configure these settings in the table below.
Field
Description
Name
A unique name to identify the RealPresence Access Director system.
Version
The version number of the RealPresence Access Director system that you are
going to add.
Management Address
The Private Network IP address for the RealPresence Access Director
system.
Admin User/Password
The user name and password of the RealPresence Access Director system.
6 In the Service Integration tab, specify the Provider-side Proxy IP Address.
7 Click OK.
The RealPresence Access Director system is added to the RealPresence Resource Manager
system.
For information about configuring the RealPresence Access Director system see the RealPresence
Access Director system documentation.
Managing SBC Devices
Polycom supports the use of the Acme Packet Net-Net Enterprise Session Director session border control
with the RealPresence Resource Manager system.
The SBC device management operations include these topics:
● Add an SBC Device
● Edit an SBC Device
● Delete an SBC Device
● Identify Endpoints Using the SBC Device
Polycom, Inc.
76
Service Integration with Session Border Controllers
Add an SBC Device
Polycom supports the use of the Acme Packet Net-Net Enterprise Session Director session border control
with the RealPresence Resource Manager system.
To add an SBC device:
1 Go to Network Device > Instances and click
.
2 Select Acme SBC from the Device Type drop-down list.
3 Select IP or FQDN Address form the Add By drop-down list.
4 Configure these settings in the table below.
Field
Description
Name
A unique name to identify the SBC.
Provider-side Proxy IP Address
The Private Network IP address for the SBC device.
Subscriber-side Proxy IP Address
The Public Network IP address for the SBC device.
5 Click OK.
The SBC device is added to the RealPresence Resource Manager system. However, more
configuration may be necessary for the device to operate in your network.
You also have the opportunity to add another SBC device.
Edit an SBC Device
You can edit the settings of an SBC device.
To edit an SBC device:
1 Go to Network Device > Instances.
2 Select the SBC device of interest and click
.
3 Configure the settings as needed in the Edit SBC dialog.
4 Click OK.
Delete an SBC Device
You can delete an SBC device from the RealPresence Resource Manager system.
To delete an SBC device from a RealPresence Resource Manager system:
1 Go to Network Device > Instances.
2 Select the SBC device of interest and click
.
3 Click OK to confirm the deletion.
Polycom, Inc.
77
Service Integration with Session Border Controllers
Identify Endpoints Using the SBC Device
This procedure identifies only Polycom HDX systems, Polycom Group Series and RealPresence Mobile
clients that are:
● Dynamically managed by the RealPresence Resource Manager system
● Using the SBC device
To identify which endpoints are using the SBC firewall:
1 Go to Endpoint > Monitor View.
2 Click
and select IP Address.
3 Enter the provider-side IP address of the SBC device and press Enter.
The Endpoint list displays the dynamically managed endpoints that are registered to the RealPresence
Resource Manager system and using the SBC firewall. All of the endpoints display the same IP address,
which is the Provider-side IP address of the SBC device. However, the endpoints will have different aliases
and owners.
Polycom, Inc.
78
Service Integration with Bridges
This section describes how to perform the Polycom® RealPresence® Resource manager system MCU
management tasks. It includes these topics:
● View Device Details
● Add an MCU Manually
● Edit an MCU
● Delete an MCU Bridge
● View Bridge Hardware
● View MCU Services
● View MCU Conferences
● View MCU Ports
● View MCU Meeting Rooms
● View MCU Entry Queues
● View Bridge Gateway Conferences
The RealPresence Resource Manager system supports managing Polycom MCUs only.
View Device Details
You can view details about a managed MCU.
To view detailed information about a managed MCU:
1 Go to Network Device > Instances.
2 As needed, click
and select RealPresence Collaboration Server or MGC as Device Type to
customize the MCU list.
3 Select the MCU of interest.
4 Click
5 Click
to view detailed information.
beside the integrated MCU to view its alerts if any.
6 Select your interested item from the More drop-down list to view other information.
Polycom, Inc.
79
Service Integration with Bridges
Add an MCU Manually
This topic describes how to add an MCU to a RealPresence Resource Manager system.
Polycom RealPresence Collaboration Server (RMX) systems cannot be managed by two management
systems at the same time. When your deployment includes a Polycom RealPresence DMA system, you can
manage an RealPresence Collaboration Server (RMX) system either in the RealPresence DMA system or
with the RealPresence Resource Manager, not both.
Back-end communication with the Polycom RealPresence Collaboration Server (RMX) system control
units and IP service blades must be enabled.
When you add an MCU device, MCU network services are added automatically at the time the IP card
registers with the RealPresence Resource Manager system.
•
•
Polycom MGC systems may only have H.323/H.320 services.
Once an MCU registers with the RealPresence Resource Manager system, if you change an MCU
service on the MCU, the update does not automatically get sent to the RealPresence Resource
Manager system. To update the system, you must refresh the device, see Edit an MCU.
When you enter network service information manually, remember that the RealPresence Resource
Manager system does not create the service at the device. The service must have already been defined at
the device. Enter information in the RealPresence Resource Manager system that matches the information
in the device.
To add an MCU bridge or find an MCU on the network:
1 Go to Network Device > Instances and click
.
2 In the Add Instance dialog, select RealPresence Collaboration Server or MGC as Device Type.
3 Select IP &FQDN Address from the Add By drop-down list.
4 Enter a Name for this instance.
•
•
If your system integrates with a Polycom RealPresence DMA system, make sure your MCU system
name includes a qualifier that indicates to the RealPresence DMA system administrator that the
MCU is directly registered to the RealPresence Resource Manager system; for example,
ResourceManager_RMX10.
A RealPresence Collaboration Server (RMX) system can be managed by the RealPresence
Resource Manager or the Polycom RealPresence DMA system, not both.
5 Specify the version of the MCU product in the Version field.
6 Specify the MCU Management Address.
7 Enter the Admin User and Admin Password for the MCU.
8 Click OK.
9 Indicate how you are integrating the MCU service.
If you want to integrate the MCU with RealPresence Resource Manager conferences instead of the
RealPresence DMA system, check the Conference Controlled by Resource Manager check box.
Polycom, Inc.
80
Service Integration with Bridges
10 Complete the Identification, Addresses, Capabilities, MCU Resources, and MCU Cascading
sections.
Pay particular attention to the Capabilities options, because these settings determine how the MCU
is used.
11 Click OK.
The RealPresence Resource Manager system will find the MCU on the network.
If the RealPresence Resource Manager system cannot find the MCU on the network, an Error dialog
appears.
If the MCU is added successfully, it will appear in the Network Device list. By default, the system:
 Adds the MCU to the applicable site.
 Sets the HTTP Port to 80.
 Makes the MCU Available to Schedule.
Conference Scheduling Requirements
If you do not define network services, you may not use an MCU or gateway in a conference. For example,
if you do not define the H.323 service on the MCU, when the RealPresence Resource Manager system tries
to schedule a video conference that requires this service, it will look for another MCU with this service. If
another MCU with this service is not available, the conference will not be scheduled.
Additionally, you must change the default entry queue setting to “standard lobby.” The default entry queue
mode is “ad hoc”. “Ad hoc” cannot be used because it allows participants to join and start a conference
before start time and consume the conference ID that is reserved for the RealPresence Resource Manager
system. Scheduled participants must be held in the standard lobby until the start time of the direct
conference to ensure the conference uses a valid conference ID.
Edit an MCU
You can edit a managed MCU.
To edit an MCU from the RealPresence Resource Manager system:
1 Go to Network Device > Instances.
2 As needed, click
and select RealPresence Collaboration Server or MGC as Device Type to
customize the MCU list.
3 Select an MCU and click
.
4 Complete the Identification, Addresses, Capabilities, MCU Resources, and MCU Cascading
sections of the Edit Instance dialog.
At a minimum, assign the MCU a Name.
Polycom, Inc.
81
Service Integration with Bridges
Field
Description
Identification
System Name
The name of the MCU.
• MCU names must be unique.
• The name must be in ASCII only and may have an unlimited number of
characters. Spaces, dashes, and underscores are valid.
• When retrieved from the MCU, the name is taken from the H.323 ID if the MCU
registered with the gatekeeper and it is a third-party system. In other cases, it
is the system name, which might be different than the H.323 ID.
Description
A free-form text field (Extended ASCII only) in which information about the MCU
can be added
Serial Number
The serial number (ASCII only) of the MCU.The serial number displays if the
MCU is registered successfully or is managed.
Software Version
The version of the software installed on the MCU (ASCII only). The MCU
provides the version number if it registered successfully or is managed.
HTTP URL
(Polycom RealPresence Collaboration Server (RMX) systems only)
The management URL for the endpoint, if available (ASCII only). This URL
enables the RealPresence Resource Manager system to start the endpoint ‘s
management system using the Manage function.
All Polycom endpoints allow device management through a browser. For these
endpoints, this field is completed when the endpoint registers with the
RealPresence Resource Manager system.
For third-party endpoints that do not register using an IP address, you must enter
the URL.
HTTP Port
(Polycom RealPresence Collaboration Server (RMX) systems only)
The HTTP port number for the MCU communications. The MCU provides the port
number if it registered successfully and is managed.
By default, in non-secure (HTTP) mode, the RealPresence Collaboration Server
uses port 80 and in secure (HTTPS) mode, the RealPresence Collaboration
Server uses port 443.
Assign Area
The area in which the MCU resides.
This field is only visible when Areas are enabled and the user manages more
than one area.
A user can only view area-specific information for an area(s) that he has
permission to manage.
Addresses
ISDN Video Number
The country code + city/area code + phone number for the MCU.
Capabilities
Polycom, Inc.
82
Service Integration with Bridges
Field
Description
Supported Protocols
The communications protocols that the MCU can support. Possible values
include:
• IP (H.323) - A standard that defines the protocols used for multimedia
communications on packet-based networks, such as IP.
• ISDN (H.320) - A standard that defines the protocols used for multimedia
communications on switched networks, such as ISDN.
• IP (SIP) - A standard that defines the protocols used for multimedia
communications on SIP networks.
The MCU automatically provides the protocols if it registered successfully or is
managed.
Polycom MGC systems may only have H.323/H.320 services.
Capabilities Enabled
Capabilities to enable on this MCU. Options are:
• MCU - The device can act as a control unit for multipoint conferences.
• Available to Schedule - Select this option to make the MCU available to users
who are scheduling conferences.
MCU Resources
Max Total Conferences
Maximum number of total conferences allowed at once on this MCU.
Max CP Conferences
Maximum number of continuous presence (CP) conferences allowed, based on
the number of licenses available.
Max Video Ports
(Not available for MGC systems)
Maximum number of video ports available on the MCU.
See View MCU Ports.
Max Total Participants
Maximum number of total MCU participants allowed at once on this MCU.
Use Entry Queue
Indicates whether the MGC device supports an IVR.
Entry Queue Numeric ID
The IP number that conference participants dial to access the IVR prompt to join
a conference.
Entry Queue ISDN Number
The ISDN number that conference participants dial to access the IVR prompt to
join a conference.
Max Voice Ports
Set this to the maximum number of audio ports configured on the RealPresence
Collaboration Server (RMX) device.
Refer to the RealPresence Collaboration Server (RMX) 2000/4000
Administrator’s Guide for more information about this field.
Notes
Up to 10 blocks of RealPresence Collaboration Server (RMX) video ports can be
converted to 50 audio-only ports, up to a maximum of 200 audio-only ports.
Not available for MGC systems.
Polycom, Inc.
83
Service Integration with Bridges
Field
Description
Max CP Resolution
Set this to the highest available video format. Choices are: HD1080, CIF, SD15,
SD30, and HD720.
Refer to RealPresence Collaboration Server (RMX) 2000/4000 Administrator’s
Guide for more information about this field.
Not available for MGC systems.
Max Bandwidth Capacity
(Kbps)
The maximum bandwidth supported by the Polycom RealPresence Collaboration
Server (RMX) MCU.
Not available for MGC systems.
5 Click OK.
6 Optionally, you can refresh the MCU to use the settings from the MCU itself. To do this, click
.
Delete an MCU Bridge
When you delete an MCU from the system, it is no longer managed and cannot be used on conferences.
To delete an MCU from the RealPresence Resource Manager system:
1 Go to Network Device > MCUs.
2 As needed, click
and select RealPresence Collaboration Server or MGC as Device Type to
customize the MCU list.
3 Select the MCU of interest and click
.
4 Click OK to confirm the deletion.
The MCU list is updated.
View Bridge Hardware
You can view the hardware properties of a managed MCU.
To view the hardware configuration of an MCU:
1 Go to Network Device > Instances.
2 As needed, click
and select RealPresence Collaboration Server or MGC as Device Type to
customize the MCU list.
3 In the MCU list, select the bridge of interest and click View Hardware from the More drop-down list.
A Hardware pane appears. It lists the hardware for the selected bridge and displays the Slot
number, Card Type, Status, Temperature, and Voltage for each piece of hardware.
View MCU Services
You can view the services provided by a managed MCU.
Polycom, Inc.
84
Service Integration with Bridges
To view the network services available on the MCU:
1 Go to Network Device > Instances.
2 As needed, click
and select RealPresence Collaboration Server or MGC as Device Type to
customize the MCU list.
3 In the MCU list, select the bridge of interest and click View Services from the More drop-down list.
A Services pane appears. It lists the network services for the selected bridge and identifies the
Service Type, Service Name, and the default setting for the network service.
View MCU Conferences
You can view the conferences hosted by an MCU.
To view information about the conferences resident on an MCU:
1 Go to Network Device > Instances.and
2 As needed, click
and select RealPresence Collaboration Server or MGC as Device Type to
customize the MCU list.
3 In the MCU list, select the bridge of interest and click View Conferences from the More drop-down
list.
A Conferences pane appears below the bridge list. It lists the conferences for the selected bridge
and identifies the conference Status, Type, Conference Name, Start Time, Bridge, and Creator.
A user can only view area-specific information for an area(s) that he has permission to manage.
View MCU Ports
The RealPresence Resource Manager system reports port numbers based on resource usage for CIF calls.
Version 8.1 and later Polycom MCUs report port numbers based on resource usage for HD720p30 calls. In
general, 3 CIF = 1 HD720p30, but it varies depending on bridge/card type and other factors.
See your RealPresence Collaboration Server (RMX) system documentation for more detailed information
about resource usage.
This option is not available for Polycom MGC systems.
To view information about the MCU ports:
1 Go to Network Device > Instances.
2 As needed, click
and select RealPresence Collaboration Server or MGC as Device Type to
customize the MCU list.
3 In the MCU list, select a bridge and click View Ports from the More drop-down list.
A Ports pane appears. It lists the ports for the selected bridge and identifies the Audio Ports
Available, CIF Ports Available, Audio Ports in Use, and CIF Ports in Use.
View MCU Meeting Rooms
You can view information about available meeting rooms:.
Polycom, Inc.
85
Service Integration with Bridges
To view information about meeting rooms:
1 Go to Network Device > Instances.
2 As needed, click
and select RealPresence Collaboration Server or MGC as Device Type to
customize the MCU list.
3 In the MCU list, select the bridge of interest and click View Meeting Rooms from the More
drop-down list.
A Meeting Rooms pane appears. It lists the meeting rooms for the selected bridge and identifies the
meeting room by Name, ID, Duration, Conference Password, Chairperson Password, and
Profile.
View MCU Entry Queues
You can view information about the available entry queues available on a managed MCU.
To view information about entry queues:
1 Go to Network Device > Instances.
2 As needed, click
and select RealPresence Collaboration Server or MGC as Device Type to
customize the MCU list.
3 In the MCU list, select the bridge of interest and click View Entry Queues from the More drop-down
list.
An Entry Queues pane appears. It lists the entry queues for the selected bridge and identifies the
entry queue by Display Name, Routing Name, ID, Profile, and Dial-In Number.
View Bridge Gateway Conferences
You can view information about gateway conferences on a managed MCU.
To view information about gateway conferences:
1 Go to Network Device > Instances.
2 As needed, click
and select RealPresence Collaboration Server or MGC as Device Type to
customize the MCU list.
3 In the MCU list, select the bridge of interest and click View Gateway Conferences from the More
drop-down list.
A Gateway Conferences pane appears below the bridge list. It lists the conferences for the selected
bridge and identifies the conference Status, Type, Conference Name, Start Time, Bridge, and
Creator.
Polycom, Inc.
86
License Management
This section provides an introduction to licensing your systems with the RealPresence Resource Manager
system. It covers the following topics:
● License Management
Polycom, Inc.
87
License Management
This section provides an introduction to licensing your systems with the RealPresence Resource Manager
system. It covers the following topics:
● License Management Overview
● Enable Licensing for a Network Device
● Online and Offline Mode
● Allocate Licenses for Polycom RealPresence Platform Components
● Update the Licenses of Polycom RealPresence Platform Components
License Management Overview
Polycom RealPresence Resource Manager is available as part of Polycom RealPresence Clariti, a Polycom
collaboration infrastructure offer that features simplified concurrent user licensing and add-on options.
RealPresence Clariti customers should consult with their Polycom representative to ensure they have the
correct licensing information before upgrading.
If you are a RealPresence Clariti customer, you must use the RealPresence Resource Manager system to
license your product. RealPresence Resource Manager to manage licenses for the following products that
support Clariti:
● Polycom RealPresence DMA, Virtual and Appliance Editions
● Polycom RealPresence Access Director, Virtual and Appliance Editions
● Polycom RealPresence Collaboration Server, Virtual Editions
● Polycom RealPresence Media Suite, Virtual and Appliance Editions
● Polycom RealPresence Web Suite Experience Portal
● Polycom RealPresence Web Suite Services Portal
Managing License for RealPresence Web Suite
If you have RealPresence Web Suite included in your system, you can run those instances in either way:
● Install the instances outside of your RealPresence Resource Manager system and manage licenses
using their existing license management process.
● Add the instances to your RealPresence Resource Manager system to manage them.
See Polycom RealPresence Web Suite Administrator Guide for instructions on how to associate the
RealPresence Web Suite Services and Experience Portals and set up licensing for those two servers within
RealPresence Resource Manager.
Polycom, Inc.
88
License Management
License features for a Polycom® ContentConnect™ solution server (for example, Base License for
ContentConnect software and High Availability) are not displayed on the License Management page
as uncounted licenses when you select the License > Allocation. However, you can point the
ContentConnect license server to RealPresence Resource Manager to retrieve uncounted licenses.
If you have a RealPresence Clariti solution subscription, you can view or download license usage data for
up to 180 days. For more information, see Update the Licenses of Polycom RealPresence Platform
Components.
Managing License for a RealPresence DMA
Supercluster
RealPresence Resource Manager manages licenses for RealPresence DMA systems in a supercluster
separately. If you have a RealPresence DMA supercluster, you must add all the RealPresence DMA
systems in a supercluster to the RealPresence Resource Manager system. In the RealPresence Resource
Manager system, you can allocate licenses for the RealPresence DMA systems in a supercluster
separately.
Enable Licensing for a Network Device
To use RealPresence Resource Manager as license server, you must enable licensing when you add the
instance of the product that you want to license.
To enable licensing:
1 Go to Network Device > Instances.
2 Select an instance of interest and click
.
3 Select a device type that you want to add.
4 For the device types that can be licensed, you will see the License Configuration tab, select the
Enable Polycom License Server Licensing check box to enable license control.
5 Click OK to save the changes.
Online and Offline Mode
Licenses for RealPresence Resource Manager system components can be managed in online or offline
mode. If the data center where the RealPresence Resource Manager system is located has connectivity to
the Internet, you must use online mode to manage licenses. If the data center does not have Internet
connectivity, you can manage the RealPresence Platform components in offline mode.
Polycom, Inc.
89
License Management
Allocate Licenses for Polycom RealPresence Platform
Components
RealPresence Resource Manager Getting Started Guide describes setting up the license server and
activating RealPresence Platform licenses within RealPresence Resource Manager, and you should
already have done that. Now you can allocate licenses for individual components of your RealPresence
Platform deployment. All license allocations for individual product are managed through the RealPresence
Resource Manager License menu.
A system component must be online within the RealPresence Resource Manager system, and the system
component time must be synchronized with RealPresence Resource Manager before licenses can be
successfully allocated to the component. In addition, the credentials for the system user configured for the
component within RealPresence Resource Manager must match the credentials for the system user as
configured within the component system.
If a license allocation fails for a newly added Polycom RealPresence virtual instance, verify that:
• The inbound ports required for license-related communications (3333 and 9333) are open on
RealPresence Resource Manager.
• The IP address configured in RealPresence Resource Manager is the correct address for the
instance. A license allocation will fail if the IP address selected for a virtual instance does not match
the instance type to which features are allocated.
If you want to re-install the old Polycom platform components or servers that have already been
licensed, you must delete the old instances from RealPresence Resource Manager before
re-installation. After the re-installation, you must re-deploy and re-allocate licenses for the instances.
To allocate licenses to a RealPresence Platform component:
1 Go to License > Allocation and do one of the following:
 Select Allocate By: Type to select a product type and see the instances of that type managed by
RealPresence Resource Manager. Then select a product instance to see a list of applicable
licenses and allocate licenses to that specific instance.
 Select Allocate By: Feature to see a list of all the activated licenses. Then select a license
feature to see the product instances to which that license is applicable and allocate the license
feature to specific instances.
For count-based license features (such as max calls), note the number available and set the
allocation input field to the number to allocate to the current instance.
2 Click Save.
3 Repeat step 1 and step 2 to allocate additional license features to the selected product instance or
allocate the selected license feature to additional product instances.
4 After allocating licenses, go to the license settings page within each product instance you licensed
to verify that the new licenses are available to the product. See the product documentation for
instructions on how to view licensing information.
For RealPresence Collaboration Server and RealPresence Access Director products, license
allocation changes take effect only after those systems have been rebooted.
Polycom, Inc.
90
License Management
Reset Allocated Licenses
You can take the allocated licenses back per instance and re-allocate the licenses for the Polycom
RealPresence Platform components.
To reset allocated licenses:
1 Go to License > Allocation.
2 Go to the feature for which you want to re-allocate the license.
3 Click Reset.
Clean Unused Licenses
You can clean all the allocated, but unused licenses that do not take effect for the Polycom RealPresence
Platform components. Use this function only when you run into problems with license allocation.
To clean un-used licenses:
1 Go to License > Allocation.
2 Click Clean.
Update the Licenses of Polycom RealPresence
Platform Components
When you buy additional features or capacity for your RealPresence Platform components, you must
allocate the newly-available licenses to your RealPresence Resource Manager license server and activate
them within RealPresence Resource Manager.
To allocate and activate newly-available licenses:
1 In the RealPresence Resource Manager management interface, go to License > Setup and copy
the System Identifier number listed on the page.
2 In a different browser window, log into the Polycom Licensing Center using the URL and
credentials sent to you.
See the Polycom RealPresence Resource Manager Getting Started Guide for information about
using the Polycom Licensing Center.
3 Click Search Servers, paste the copied system identifier number into the License Server ID field,
and click Filter.
Your RealPresence Resource Manager license server appears in the list below.
4 Click the license server ID in the list below.
The View Server page displays license information for this RealPresence Resource Manager license
server.
Polycom, Inc.
91
License Management
5 Click Map Add-Ons.
The Map Add-Ons page displays a table of license information for your organization, showing usage
and availability.
6 Find the license add-ons you want to allocate and verify that Available Units in Line Item is not
zero.
7 In the Qty to Add field of the add-ons you want to allocate, enter the number of units to allocate to
this RealPresence Resource Manager instance and click Map Add-Ons.
The View Server page returns, displaying a list of the server’s licenses. The status for
newly-allocated licenses is License not generated. The licenses must be generated (activated within
your RealPresence Resource Manager system).
8 If you allocated too many license add-on units to this RealPresence Resource Manager instance
and want to remove some, click Remove Add-Ons.
The Remove Add-Ons page lists the license add-ons available on this instance.
9 In the Quantity to Remove field of the add-ons you want to change, enter the number of units to
remove and click Remove Add-Ons.
The View Server page returns, displaying a list of the server’s licenses. The status for licenses with
newly-removed units is Copies decreasing. The removed licenses must be deactivated within your
RealPresence Resource Manager system.
10 If your RealPresence Resource Manager instance does not have access to the Internet, click
Download Capability Response to download a local copy of the license file. Note the location of
the license file when you download it to your local computer.
If your RealPresence Resource Manager system has access to the Internet, you must use the online
method to license the system and its components. The offline method for managing licenses is not
an option when Internet access is available.
11 Return to the RealPresence Resource Manager License Setup page, and do one of the following:
 Click Online if your virtual environment has access to the Internet and can use the online method
for managing licenses.
 Click Offline if your virtual environment does not have access to the Internet. Prompts guide you
through the offline update process using the license file you previously downloaded from the
Polycom Licensing Center.
12 Click Update to complete the license activation process.
The licenses should be activated within a few seconds to a minute. You may need to refresh the
browser window.
For counted licenses, you can now allocate them to the appropriate system component(s), as described in
Allocate Licenses for Polycom RealPresence Platform Components.
Polycom, Inc.
92
Configure Conferencing
This section provides an introduction to the Polycom® RealPresence Resource Manager system video
conference scheduling functionality and operations. It includes:
● Setting Up Site Topology
● Setting Up the Global Address Book
● Using Multiple Address Books
● Direct Conference Templates
● Configuring Conference Settings
Polycom, Inc.
93
Setting Up Site Topology
This section describes how to edit the default Polycom® RealPresence® Resource Manager system
topology settings to support your company’s network topology. It includes these topics:
● Site Topology Setup
● Managing Sites
● Managing Site Links
● Managing Site-to-Site Exclusions
● Territories
● Network Clouds
Site Topology Setup
Site topology information describes your network and its interfaces to other networks, including the following
elements:
● Site — A local area network (LAN) that generally corresponds with a geographic location such as an
office or plant. A site contains one or more network subnets, so a device’s IP address identifies the
site to which it belongs.
● Network clouds — A Multi-protocol Label Switching (MPLS) network cloud defined in the site
topology. An MPLS network is a private network that links multiple locations and uses label switching
to tag packets with origin, destination, and quality of service (QOS) information.
Note that MPLS clouds are not associated with an IP address ranges, so they can be used to group
multiple subnets. They could also represent a service provider.
While links to MPLS clouds have bandwidth and bit rate limitations, the cloud is infinite. In this way,
clouds reflect the way in which businesses control bandwidth and bit rate.
● Internet/VPN — A entity that represents your network’s connection to the public Internet.
● Site link — A network connection between two sites or between a site and an MPLS network cloud.
● Site-to-site exclusion — A site-to-site connection that the site topology doesn’t permit an audio or
video call to use.
● Territory — A grouping of one or more sites for which a RealPresence Resource Manager system
is responsible.
The site topology you create within the RealPresence Resource Manager system should reflect your
network design. Consider the following information and best practices when creating your site topology:
If your RealPresence Resource Manager system is integrated with a Polycom RealPresence DMA
system, the RealPresence DMA system inherits all site topology settings from the RealPresence
Resource Manager. Be sure to consult with your RealPresence DMA system admin before making
any changes, see Considerations for Site Topology.
Polycom, Inc.
94
Setting Up Site Topology
● If possible, connect all sites to an MPLS cloud. MPLS clouds are like corporate networks, used to
connect multiple subnets in multiple sites, but all servicing a company.
● Avoid cross loops or multiple paths to a site; otherwise a call may have different paths to a single
destination. The more cross, circular, and multi paths you have, the higher the number of calculations
for a conference.
● Link sites that are not connected to an MPLS cloud directly to another site that is connected to an
MPLS cloud. Do not create orphan sites.
● Calls are routed through a bridge, so bandwidth and bit rate limits for the site and subnet apply to all
calls made using that bridge.
● Reserve the Internet/VPN “site” for IP addresses that fall outside your private or corporate network
(for example remote workers), because all calls routed to the Internet/VPN site will be routed through
the site on your private or corporate network that has Internet access.
Managing Sites
Sites are the primary way you organize your video network.
This section includes the following topics:
● View the Graphical Site Topology
● View the Sites List
● Add a Site
● View Site Information
● Assign Locations to a Site
● Edit Site Settings
● Delete a Site
For information on editing a network provisioning profile, see Network Provisioning Profiles.
View the Graphical Site Topology
The RealPresence Resource Manager system site topology function uses a dynamic, embedded mapping
tool that graphically displays the sites, clouds (network and Internet), and site links (site-to-site or
site-to-cloud) in your network.
Within this global and graphical view of the video conferencing network, you can:
● Create and link up to 500 sites.
● Zoom and pan to view specific network components.
● View system and device alarms.
● View the video network capacity for sites and site links as indicated by the color and shape of its
icons.
● Filter the view by site name, territory name, IP address, network devices, and alerts.
Polycom, Inc.
95
Setting Up Site Topology
To view the graphical site topology:
» Go to Network Topology > Site Topology.
The Site Topology page appears. It graphically displays the sites and site links defined to the
RealPresence Resource Manager system.
 Hover over a map element to view information about it.
 Use the slider bar to zoom in or out on the map.
 Select or deselect elements (Site Links, Bandwidth, or Site Names) to change what is displayed
on the map.
 Click
to filter (by site name, territory name, IP address, network devices, and alerts) which
sites are displayed on the map.
View the Sites List
The Sites page (Network Topology > Sites) contains a list of the sites defined to the RealPresence
Resource Manager system.
To view the Sites list:
» Go to Network Topology > Sites.
The Sites list appears. It includes this information:
Column
Description
Site Name
Name of the site.
Description
Description of the site.
Country Code
The country code for the country in which the site is located.
Area Code
The city or area code for the site. Do not include a leading zero. For example,
the city code for Paris is 01, enter 1 in this field.
Max Bandwidth (Mbps)
The total bandwidth limit for audio and video calls.
Max Bit Rate (Kbps)
The per-call bandwidth limit for audio and video calls.
Territory
The territory to which the site belongs, which determines the RealPresence
Resource Manager system responsible for it.
Add a Site
You can define a new site in the system’s site topology and specify which subnets are associated with it.
You can define overlapping subnets within a site or between sites. Larger subnets can contain smaller ones.
When the system determines which subnet a given IP address belongs to, it chooses the subnet with the
longest IP match.
Polycom, Inc.
96
Setting Up Site Topology
For example:
Subnet1 = 10.0.0.0/8
Subnet2 = 10.33.24.0/24
The IP address 10.33.24.70 belongs to subnet2, while the IP address 10.22.23.70 belongs to
subnet1.
To add a site:
1 Go to Network Topology > Sites or Network Topology > Site Topology.
 To add a site in the Sites page, Click
.
 To add a site in the Site Topology page, go to Site Actions > Add.
2 In the Add Site dialog, enter a Site Name and Description for the site.
3 Complete the General Info, H.323 Routing, SIP Routing, Subnet, and if applicable ISDN Number
Assignment, sections of the Add Site dialog. The minimum information required is Site Name,
Description, Location, and Subnets.
Field
Description
General Info
Site Name
A meaningful name for the site, this name can be 64 characters (ASCII only)
long.
Description
A brief description (ASCII only) of the site.
Enable Mutual TLS
Enable Mutual TLS
Override ITU Dialing Rules
Check this box to override the standard dial rules established by the
International Telecommunications Union.
PBX Access Code
The access code required to enter the site’s PBX system.
Country Code
The country code for the country in which the site is located.
Area Code
The city or area code for the site. Do not include a leading zero. For example,
the city code for Paris is 01, enter 1 in this field.
# of Digits in Subscriber Number
The number of digits in a phone number. For example, in the United States,
subscriber numbers may have seven digits or ten digits depending upon the
region.
Polycom, Inc.
97
Setting Up Site Topology
Field
Description
Assignment Method
The ISDN number assignment method for the site. Possible values include:
• No Auto Assignment. Select this option when ISDN numbers are not
assigned to IP devices.
• DID (Direct Inward Dial). Select this option when you assign a range of
phone numbers received from the telephone company service.
• Gateway Extension Dialing. Select this option when you have a single
gateway phone number and a range of extensions (E.164 aliases) that are
internal to the company. In this case, calls go through a gateway. Endpoints
are differentiated by the extension at the end of the dial string.
When a site is assigned an automatic assignment method, devices without an
ISDN number are assigned one when they register. These numbers allow
inbound calls to reach specific video endpoints. After an ISDN number is
assigned to an endpoint, it is reserved for use as long as that endpoint
remains registered with the RealPresence Resource Manager system.
Note
If you do not assign ISDN numbers automatically, you cannot call IP-only
endpoints through an ISDN line.
Territory
Assigns the site to a territory, and thus to a RealPresence Resource Manager
system.
Location
Specify the geographic location of the site either by longitude + latitude or
country + city.
Total Bandwidth (Mbps)
The total bandwidth of the pipe at the site.
Call Max Bit Rate (kbps)
The maximum bandwidth that can be used for each intrasite call at the site.
The default and maximum value is 2000000 (2 GB).
ISDN Number Assignment—
Assignment Method = DID (Direct Inward Dial)
# Digits in Call Line Identifier
Enter the number of digits in the Call Line Identifier (CLID), which is the dialed
number. The maximum is 17.
• For example, in the United States, the number of digits in the CLID is often
7 for outside local calls, 4 for internal calls, or 11 for callers in a different
area code.
• This number indicates what part of the full dial string is sent to the
gatekeeper for address resolution.
# Digits in Short Phone Number
Enter the number of digits in the short form of the dialing number.
• For example, in the United States, internal extensions are usually four or
five digits.
• This number indicates what part of the dial string is sent to the gatekeeper
for address resolution in gateway + extension dialing.
ISDN Number Range - Start
The starting ISDN number to assign automatically to IP devices.
ISDN Number Range - End
The ending ISDN number to assign automatically to IP devices.
ISDN Number Assignment—
Assignment Method = Gateway Extension Dialing
Polycom, Inc.
98
Setting Up Site Topology
Field
Description
Gateway Phone Number
Phone number of the site gateway.
E164 Start
•
•
E164 End
The starting number in a range of available extensions to assign
automatically to IP devices.
When a device without native ISDN registers, a number within the start and
end range is assigned, so that the device can be called through an ISDN
line.
The ending number in the range of available extensions to assign
automatically to IP devices.
H.323 Routing
Internet calls are not allowed
Disables call routing through the Internet.
Allowed via H.323 aware firewall
Enables call routing through the Internet, using an H.323-aware firewall.
Notes
• For an outbound call to the Internet, you must enter the firewall gateway
service (e.g. a Polycom VBP appliance) code before the IP address in the
dial string.
• If you select Allowed via H.323 aware firewall you must create a site link
between this site and the Internet/VPN site.
Allowed via H.323 aware SBC or
ALG
Enables call routing via the Internet, using an H.323-aware SBC (Session
Border Control) or ALG (Application Level Gateway) server.
Note
For an outbound call to the Internet, you must enter the firewall gateway
service (for example, a Polycom VBP appliance) code before the IP address
in the dial string.
Call Signaling IP Address
IP address (IPv4 only) or host name of the SBC or ALG server.
Port
Port address of SBC or ALG server.
Send Unmodified Dial String to
SBC/ALG
Select this option if your SBC or ALG requires that the original dial string is
passed to it. For example, an H.323 Annex O dial string such as
user@company.com is passed directly to the SBC or ALG instead of resolving
company.com to an IP address.
Deselect this option if your equipment requires a dial string that is converted
from company.com to gatekeeper IP address. This option is appropriate for
the Polycom VBP.
SIP Routing
Internet calls are not allowed
Polycom, Inc.
Disables call routing through the Internet.
99
Setting Up Site Topology
Field
Description
Allowed via SIP aware firewall
Enables call routing through the Internet, using an SIP-aware firewall.
Notes
• For an outbound call to the Internet, you must enter the firewall gateway
service (e.g. a Polycom VBP appliance) code before the IP address in the
dial string.
• If you select Allowed via SIP aware firewall you must create a site link
between this site and the Internet/VPN site.
Allowed via SIP aware SBC or
ALG
Enables call routing via the Internet, using an SIP-aware SBC (Session
Border Control) or ALG (Application Level Gateway) server.
Note
For an outbound call to the Internet, you must enter the firewall gateway
service (for example, a Polycom VBP appliance) code before the IP address
in the dial string.
Call Signaling IP Address
IP address (IPv4 only) or host name of the SBC or ALG server.
Port
Port address of SBC or ALG server.
The default port is 5070.
Subnets
Subnet IP Address/Mask
Specifies the subnets within the site. For each subnet, include:
• IP Address range
• Mask Length
• Total Bandwidth
Note for sites that include a RealPresence Access Director system
If this site is used for a site that includes a RealPresence Access Director
system, be sure to include the subnet where the RealPresence Access
Director system resides.
Enterprise Directory Settings—
Endpoint Enterprise Directory security group settings
Universal Security Group Filter
Enterprise Directory Admin Group
Enterprise Directory User Group
When in secure mode, search and select groups that are provisioned to the
endpoints to represent the valid lists of users that can log in as a user or
administrator. If a user is not a member of one of the selected groups then the
user is denied access to the endpoint.
4 Click OK.
View Site Information
You can view information about existing sites.
Polycom, Inc.
100
Setting Up Site Topology
To view information about an existing site:
1 Go to Network Topology > Sites.
2 In the Sites page, select a site and go to More > Site Information.
The Site Information dialog displays the following site information.
Column
Description
Site Name
Name of the site.
Description
Description of the site.
Location
The specified location of the site identified either by longitude + latitude
or by country + city.
Bandwidth (Mbps)
The specified total bandwidth limit for audio and video calls.
Bandwidth Used
Identifies the percentage of the maximum bandwidth currently occupied
with audio and video calls.
Max Bit Rate
The per-call bandwidth limit for audio and video calls.
Device Types
Identifies the type (Bridges, DMAs, VBPs, and Endpoints) and number of
devices assigned to the site.
Alarms
Identifies the device alarms present within the site. Alarm information
includes Status, Device Name, Device Type, and Description. Click
Details to view more device details.
Subnets
Identifies the subnets within the site. Subnets information includes
Bandwidth Used, Subnet (name), and (maximum) Bandwidth.
Assign Locations to a Site
Location has not always been a required field for sites. If your existing sites do not include location
information, use the Assign Locations action to update your sites.
To assign a location to an existing site:
1 Go to Network Topology > Sites or Network Topology > Site Topology.
a In the Site Topology page, go to SITE ACTIONS > Assign Locations.
b In the Sites page, go to More > Assign Locations.
2 In the Assign Locations to Sites dialog, select the site of interest by selecting the associated
check box and click Specify Location.
3 To specify a location by city name:
a From the Enter Location By drop-down list, select Search for City.
b If you know it, select the Country name for the location.
c Enter the name of the City and click Search.
The system returns the list of cities that matches your query.
Polycom, Inc.
101
Setting Up Site Topology
d Select the appropriate city using the Country, Division, and Subdivision fields to identify it and
click Select.
4 To specify a location by latitude and longitude in decimal degrees format:
a From the Enter Location By drop-down list, select Latitude/Longitude (Decimal format).
b Enter the Latitude and Longitude coordinates in decimal degrees (for example, Baltimore has a
latitude of 39.3° and a longitude of 76.6°).
c Enter a Location Name. The system uses this location name for reference only; it does not
validated the location name against the latitude and longitude coordinates that you enter.
d Select the Country name for the location and click Select.
The system uses the coordinates you input to place the site in the proper location on its site
topology map.
5 To specify a location by latitude and longitude in DaysMinutesSeconds format:
a From the Enter Location By drop-down list, select Latitude/Longitude (DDD:MM:SS format).
b Enter the Latitude and Longitude coordinates in the required format and select
c Enter a Location Name. The system uses this location name for reference only; it does not
validated the location name against the latitude and longitude coordinates that you enter.
d Select the Country name for the location and click Select.
The system uses the coordinates you input to place the site in the proper location on its site
topology map.
Edit Site Settings
You can define a new site in the system’s site topology and specify which subnets are associated with it.
Changing network topology may affect the accuracy of reports based on this information. To retain
historical data for the current network topology, generate reports before making changes.
If your RealPresence Resource Manager system is integrated with a RealPresence DMA system, the
RealPresence DMA system inherits all site topology settings from the RealPresence Resource
Manager system. Be sure to consult with your RealPresence DMA system admin before making any
changes, see Considerations for Site Topology.
To edit settings for a site:
1 Go to Network Topology > Sites or Network Topology > Site Topology.
2 In the Sites list or Site Topology page, select the site of interest and click
Edit Site.
or SITE ACTION >
3 Edit the General Info, Site Routing, Site Subnet, and if applicable ISDN Number Assignment,
sections of the Edit Site dialog.
4 Click OK.
For information about these site settings, see Add a Site.
Polycom, Inc.
102
Setting Up Site Topology
Delete a Site
You can delete a site.
Devices that belonged to a deleted site are automatically reassigned to support Internet and VPN
calls.
To delete a site:
1 Go to Network Topology > Sites or Network Topology > Site Topology.
2 In the Sites list or Site Topology page, select the site of interest and click
Delete.
or SITE ACTION >
3 Click OK to confirm the deletion.
Managing Site Links
When you add a site link, you enter the starting and ending sites of the link and the maximum bandwidth
and bit rates available for calls (audio and video) that use the link. Links are bidirectional. After you have
created a link from Site A to Site B, you automatically have a bi-directional link from Site B to Site A, although
the link appears as unidirectional.
A link can connect two sites, or it can connect a site to an MPLS network cloud (see Network Clouds).
The bit rate can be set at the network level, the device level, and the conference level. If there is a
discrepancy between these bit rate settings, the system implements the lowest bit rate setting. The
only exception, is that the bit rate in the RealPresence Collaboration Server (RMX) profile takes
precedence over the bit rate in the conference settings.
This section includes the following topics:
● View the Site Links List
● Add a Site Link
● Edit a Site Link
● Delete a Site Link
View the Site Links List
You can view the list of site links.
To view the Site Links list:
» Go to Network Topology > Site-Links.
The Site-Links list appears.
Polycom, Inc.
103
Setting Up Site Topology
Column
Description
Site-Link Name
Name of the link
Description
Description of the link
From Site
First site reached in the call route
To Site
Final site reached through this call link
Max Bandwidth (Mbps)
The maximum available bandwidth for audio and video calls, which you set at the
gateway or router. Only applies to direct links.
Max Bit Rate (kbps)
The maximum bit rate allowed for an audio and video call. Only applies to direct links.
Add a Site Link
Before you can create a site link, you must add two or more sites to the system.
To add a site link:
1 Go to Network Topology > Site-Links.
2 In the Site-Links page, click
.
3 In the Add Site-Link dialog, enter a Site-Link Name and Description for the link and select the
starting (From Site) and ending (To Site) sites.
4 Enter the Bandwidth and Max Bit Rate and click Save.
The new link appears on the Site Links page.
Edit a Site Link
You may need to edit site links when network changes are made.
If you make a bandwidth change, the current load is not affected; however, the bandwidth available for future
conferences may be affected.
To edit a site link:
1 Go to Network Topology > Site-Links.
2 In the Site-Links list, select the link of interest and Click
.
3 In the Edit Site-Link dialog, edit the Site-Link Name, Description, Bandwidth or Max Bit Rate.
4 Click OK.
Delete a Site Link
You can remove site links from the RealPresence Resource Manager system.
Polycom, Inc.
104
Setting Up Site Topology
Avoid removing a link on which a scheduled conference depends.
To delete a site link:
1 Go to Network Topology > Site-Links.
2 In the Site-Links list, select the site link of interest and click
.
3 Click OK to confirm the deletion.
Managing Site-to-Site Exclusions
Create site-to-site exclusions to explicitly deny connection between two sites for audio or video calls.
Site-link exclusion operations include:
● View the Site-to-Site Exclusion List
● Add a Site-to-Site Exclusion
● Edit a Site-to-Site Exclusion
● Delete a Site-to-Site Exclusion
View the Site-to-Site Exclusion List
You can view a list of site-to-site exclusions.
To view the Site-to-Site exclusion list:
» Go to Network Topology > Site-to-Site Exclusion.
The Site-to-Site Exclusions list appears.
Add a Site-to-Site Exclusion
Before you can create a site link exclusion, you must add two or more sites to the system.
Exclusions are by definition bilateral. No call traffic is allowed to flow across the site-link in either direction.
To add a site-to-site exclusion:
1 Go to Network Topology > Site-to-Site Exclusions.
2 In the Site-to-Site Exclusions page, click
.
3 In the Add Site-to-Site Exclusions dialog:
a Select the first site of the From/To site pair (by clicking the appropriate button). If needed, use the
Search Site field to find the site.
b Select the second site of the From/To site pair (by enabling the appropriate check box) and click
Continue. You can select more than one site, if needed.
Polycom, Inc.
105
Setting Up Site Topology
c Review the site-to-site exclusion and if it is correct, click OK.
Edit a Site-to-Site Exclusion
You cannot edit a site-to-site exclusion; you can only delete it and then re-add it.
Delete a Site-to-Site Exclusion
You can delete a site-to-site exclusion.
To delete a site-to-site exclusion:
1 Go to Network Topology > Site-to-Site Exclusions.
2 In the Site-to-Site Exclusions page, select the exclusion of interest and click
.
3 Click OK to confirm the deletion.
Territories
A territory is a set of one or more sites for which a RealPresence Resource Manager system is responsible.
By default, there is one territory named Default Resource Manager Territory, and its primary node (the
RealPresence Resource Manager system responsible for it) is set to this system.
You should configure the Resource Manager Default territory to be the primary
RealPresence DMA node AFTER you integrate with a RealPresence DMA system.
Territory operations include:
● View the Territory List
● Add a Territory
● Edit a Territory
● Delete a Territory
View the Territory List
You can view a list of territories.
To view the Territories list:
» Go to Network Topology > Territories.
The Territories list appears.
Polycom, Inc.
106
Setting Up Site Topology
Add a Territory
You can define a new territory in the RealPresence Resource Manager system’s site topology.
To add a territory:
1 Go to Network Topology > Territories.
2 In the Territories page, click
.
3 Complete the Territory Info and Associated Sites sections of the Add Territories dialog.
Field
Description
Territory Info
Territory Name
A meaningful name for the territory (up to 128 characters).
Description
A brief description of the territory (up to 200 characters).
Primary Cluster
The primary node of the RealPresence Resource Manager system
responsible for this territory.
You can assign this territory to either a RealPresence Resource Manager or a
RealPresence DMA system.
When integrating with a RealPresence DMA system, enter the management
FQDN or IP address of the primary cluster that will manage this territory. You
should do this step AFTER you integrate with a RealPresence DMA system.
Backup Cluster
The second node, if any, of the RealPresence Resource Manager system
responsible for this territory.
You can assign this territory to either a RealPresence Resource Manager or a
RealPresence DMA system.
When integrating with a RealPresence DMA system, enter the management
FQDN or IP address of the primary backup cluster that will manage this
territory. You should do this step AFTER you integrate with a RealPresence
DMA system.
Host Conference Rooms In This
Territory
Enables this territory to be used for hosting conference rooms (VMRs, or
virtual meeting rooms).
The territory’s primary and backup clusters must both be enabled for
conference room hosting. No more than three territories may have this
capability enabled.
Associated Sites
Search Sites
Enter search string or leave blank to find all sites.
Search Result
Lists sites found and shows the territory, if any, to which each currently
belongs.
Select a site and click the right arrow to move it to the Selected Sites list.
Selected Sites
Lists sites selected and shows the territory, if any, to which each currently
belongs.
4 Click OK.
Polycom, Inc.
107
Setting Up Site Topology
Edit a Territory
You can edit an existing territory in the RealPresence Resource Manager system’s site topology.
You should configure the Resource Manager Default territory to be the primary
RealPresence DMA node AFTER you integrate with a RealPresence DMA system.
To edit a territory:
1 Go to Network Topology > Territories.
2 In the Territories page, select the territory of interest and click
.
3 Change the Territory Info and Associated Sites information of the Add Territories dialog as
needed. For information about these fields, see Add a Site.
4 Click OK.
Delete a Territory
You can delete a territory.
To delete a territory:
1 Go to Network Topology > Territories.
2 In the Territories page, select the territory of interest and click
.
3 Click OK to confirm the deletion.
Network Clouds
To simplify the network topology, define network clouds to represents a hub with many sites connected to
each other such as a private network or VPN.
The Network Clouds page contains a list of the MPLS (Multi-protocol Label Switching) network clouds
defined in the site topology.
Use the commands in the Actions list to add, edit, or delete an MPLS cloud.
Network cloud operations include:
● Multi-tenancy Considerations for Network Clouds
● View the List of Network Clouds
● Add a Network Cloud
● Edit a Network Cloud
● Delete a Network Cloud
Polycom, Inc.
108
Setting Up Site Topology
Multi-tenancy Considerations for Network Clouds
When areas are enabled for your system, sites can be assigned to areas. You must be sure that each site
within a network cloud belongs to the same area. View the Sites list to determine the area for a site, see
View the Sites List.
View the List of Network Clouds
You can view the list of network clouds.
To view the Network Cloud list:
» Go to Network Topology > Network Clouds.
The Network Clouds list appears.
Add a Network Cloud
You can add a network cloud.
To add a network cloud:
1 Go to Network Topology > Network Clouds.
2 In the Network Clouds page, click
.
3 In the Cloud Info section of the Add Network Cloud dialog, enter a unique and meaningful Cloud
Name and Description for the cloud.
4 To create a link between a site and the network cloud:
a Click Linked Sites.
b In the Search Sites field, enter all or part of the site name or location and click
.
The list of sites containing the search phrase appear in the Search Results column.
c Select one or more sites to link with the network cloud and then click the right arrow to move them
to the Selected Sites column.
Field
Description
Linked Sites
Search Sites
Enter search string or leave blank to find all sites.
Search Result
Lists sites found and shows the territory, if any, to which each belongs.
Select a site and click the right arrow to open the Add Site Link dialog.
Selected Sites
Lists sites linked to the cloud and shows the territory, if any, to which each
belongs.
5 Click OK.
Polycom, Inc.
109
Setting Up Site Topology
Edit a Network Cloud
You can edit the settings of a network cloud.
To edit a network cloud:
1 Go to Network Topology > Network Clouds.
2 In the Network Clouds page, select the network cloud of interest and click
.
3 Edit the Cloud Info or to create a link between a site and the network cloud:
a Click Linked Sites.
b In the Search Sites field, enter all or part of the site name or location and click
.
The list of sites containing the search phrase appear in the Search Results column.
c Select one or more sites to link with the network cloud and then click the right arrow to move them
to the Selected Sites column.
4 Click OK.
Delete a Network Cloud
You can delete a network cloud.
To delete a network cloud:
1 Go to Network Topology > Network Clouds.
2 In the Network Clouds page, select the network cloud of interest and click
.
3 Click OK to confirm the deletion.
Polycom, Inc.
110
Setting Up the Global Address Book
This section describes how to manage the Global Address Book in the Polycom® RealPresence® Resource
Manager system.
The Polycom Global Address Book is a system-managed endpoint directory that enables users with video
endpoints to look up and call other users with video endpoints in their video communications network.
For more information on the Global Address Book, see Endpoint Directory and Directory Settings.
This section includes these topics:
● View the Global Address Book
● Enable or Disable GAB Filter
● Set or Change the GAB Password
View the Global Address Book
You must have the Administrator role and permissions to view the Global Address Book.
To view the Global Address Book:
1 Go to Admin > Directories > Global Address Book.
2 As needed, click
or IP Address.
to customize the Global Address Book. It can be filtered by Endpoint Name
The user information found in the Global Address Book is listed in the table below.
Column
Description
Endpoint Name
The name of the registered endpoint.
GAB Display Name
The name of the registered endpoint as it will be displayed to other endpoint
users. This display name is an ASCII only field.
The GAB display name is automatically generated when the user is
associated with the endpoint. If you want to update the GAB display name,
you can do so from the Endpoint > Monitor View.
See Edit an Endpoint.
IP Address
The IP address of the endpoint.
Alias
The alias associated with the endpoint.
Primary ISDN
The primary ISDN number for the endpoint (if any).
Secondary ISDN
The secondary ISDN number for the endpoint (if any).
Polycom, Inc.
111
Setting Up the Global Address Book
Column
Description
Owner
The user associated with the endpoint.
Type
The type of the endpoint.
Enable or Disable GAB Filter
From a video endpoint system, users can locate other user’s endpoints by name in the Global Address Book
and initiate a call without knowledge of the other user’s equipment. The RealPresence Resource Manager
system will filter incompatible endpoints out of the Global Address Book (GAB) results so that the GAB
presented to H.323-only endpoints will not include ISDN-only endpoints and the GAB presented to
ISDN-only endpoints will not include H.323-only endpoints.
Global Address Book filtering applies only to Polycom endpoints. The Global Address Book is not
filtered on third-party endpoints.
To enable or disable GAB Filter,
1 Go to Admin > Directories > Global Address Book.
2 Click the Set GAB Filter button.
3 Check or cancel the Disable GAB Filtering to disable or enable GAB Filter.
Set or Change the GAB Password
You can require that endpoints be provisioned with a password in order to access the Global Address Book
on the RealPresence Resource Manager system. To do so, set a Global Address Book password as
described here. Use the same procedure to change the Global Address Book password.
Note that even if the Global Address Book is password protected, some third-party endpoints may not be
required to provide a password because they are not directory-password aware. They have unrestricted
access to the Global Address Book.
You must have the Administrator role and permissions, to set or change the Global Address Book
password.
To provision this password to endpoints, see Add a Scheduled Provisioning Profile.
To set or change the password for the Global Address Book:
1 Go to Admin > Directories > Global Address Book.
2 In the Global Address Book, click Set GAB Password.
3 In the Set Client Password dialog, enter the Old Password and the New Password. Note that the
password fields are ASCII only.
4 Confirm the new password and click Save.
Once you set this password, endpoints that are not provisioned with this password cannot access the
Global Address Book on the RealPresence Resource Manager system.
Polycom, Inc.
112
Using Multiple Address Books
This section describes how to set up multiple address books in the Polycom® RealPresence® Resource
Manager system. It includes these topics:
● Multiple Address Books Overview
● Using Multiple Address Books
● Address Book Considerations for Multi-Tenancy
● View the Address Book List and Details
● Add an Address Book
● Edit an Address Book
● Assign Address Books to User Groups
● Delete an Address Book
● Change Address Book Priority
● Set the Default Address Book
● Copy an Address Book
Multiple Address Books Overview
Users assigned the Administrator role can create multiple address books in the RealPresence Resource
Manager system. Multiple address books are subsets of the Global Address Book (GAB) and let you
manage which users (local and enterprise), endpoints, rooms, groups, and guests appear in each address
book.
Multiple address books support both the Global Address Book and LDAP protocols. Endpoints requesting
directory information using either protocol receive either the default address book or the address book
assigned to the user’s group.
If you do not want to use multiple address books, you can leave the default address book set to All Entries.
Using this default, all users will see all entries in the directory. Be sure that all groups are assigned either
the System Default or All Entries option. System Default is the default group setting.
An endpoint must be associated with a User and the User must be in a Group in order to specify an
address book.
Polycom, Inc.
113
Using Multiple Address Books
Using Multiple Address Books
Use address books to limit access to people and endpoints. For example, you can set up separate address
books for each department in your organization. Each address book would include only RealPresence
Resource Manager system users in that department and only rooms in that department’s location.
Users not assigned the Administrator or Area Administrator role (available if you have enabled areas) will
not be aware of address books. They will see only those users (local and enterprise directory), endpoints,
rooms, groups, and guests in the same address book that the user is assigned to.
For information about how address books work in a multi-tenancy environment, see Area Address Books.
Implement Multiple Address Books
You need to complete the following tasks to implement multiple address books.
To implement multiple address books:
1 Add an Address Book
RealPresence Resource Manager system users assigned the Administrator role can create
address books and associate users (local and enterprise directory), endpoints, rooms, groups, and
guests with one or more address books. This process controls where each entity appears as an
address book entry.
2 Assign Address Books to User Groups
RealPresence Resource Manager system users assigned the Administrator role can assign an
address book to a group. A group can be assigned to only one address book. This process controls
the address book that users and endpoints have access to.
3 Change Address Book Priority
RealPresence Resource Manager system users assigned the Administrator role can set the priority
of address books. The priority affects which address book a user has access to. For example, if a
user is a member of two different groups and each group is assigned a different address book, the
user can access the address book that is higher in priority.
Address Book Considerations for Multi-Tenancy
If you have enabled the Areas feature, you can only associate users and endpoints that are in the same
area that you have been assigned to manage.
Users not assigned the Administrator or Area Administrator role will not be aware of address books or be
allowed to edit them. They will see only those users (local and enterprise directory), endpoints, rooms,
groups, and guests in the same address book and area to which the user is assigned.
When you manage more than one area, you can create address books that contain users and endpoints
from each area that you manage. However, users in that address book will only be able to view users from
the area to which they also belong.
For more information about multi-tenancy, see Configuring Multi-Tenancy.
Polycom, Inc.
114
Using Multiple Address Books
View the Address Book List and Details
You can view an address book.
To view the address book list and details:
1 Go to Admin > Directories > Address Books.
The Address Book list appears, with details of the selected address book in the right pane.
Column
Description
Priority
The priority affects which address book a user sees. For example, if a user is a member
of two different groups and each group is assigned a different address book, the user
will see the address book that is higher in priority.
Address Book Name
Name of the address book.
Description
A brief description of the address book.
2 In the Address Book Details in the right pane, expand the tree to view the tiers along with users,
endpoints, rooms, groups, and guests associated with the address book.
Add an Address Book
You can add many address books to the RealPresence Resource Manager system, and each address book
can have up to 100 tiers.
Tiers are only meant to allow you to organize the address book contents. They will not be visible to endpoint
users when they access the directory. Each tier can have up to three subtiers., and you can have address
book entries at any tier level.
Associating users, endpoints, rooms, groups, and guests with an address book controls where these
entities appear. For example, if you associate user A with address book A, the user will appear as an entry
in address book A. You can associate any of these entities with more than one address book, and the entity
will appear as entry in each address book.
Groups in the RealPresence Resource Manager system control the address book users, endpoints, and
rooms have access to. To set which address book an entity has access to, see Assign Address Books to
User Groups.
To add an address book:
1 Go to Admin > Directories > Address Books.
2 Click
.
3 Complete the fields in the Add an Address Book dialog.
Field
Description
Address Book Information
Address Book Name
Polycom, Inc.
A meaningful name to identify this address book.
115
Using Multiple Address Books
Field
Description
Description
A brief description of the address book.
Address Book Tiers
New Tier
Select where you want to add a tier and click to add a new tier to the address book.
Edit Tier Name
Select a tier and click to change a tier name.
Delete
Select a tier and click to delete a tier.
4 To associate users with this address book, click Associate Users.
The Address Book/Tier column shows all of the address books the users appear in.
a Search for the users you want to associate. Use the Filter to customize the list.
b Select the users you want and click Specify Tier.
c Select the tier you want for the users and click OK.
5 To associate endpoints with this address book, click Associate Endpoints.
Only endpoints that are not associated with a RealPresence Resource Manager system user appear
in the list.
a Use the Filter to customize the list.
The Address Book/Tier column shows all of the address books the endpoints appear in.
b Select the endpoints you want and click Specify Tier.
c Select the tier you want for the endpoints and click OK.
6 To associate rooms with this address book, click Associate Rooms.
The Address Book/Tier column shows all of the address books the rooms appear in.
a Use the Filter to customize the list.
b Select the rooms you want and click Specify Tier.
c Select the tier you want for the rooms and click OK.
7 To associate groups with this address book, click Associate User Groups.
The Address Book/Tier column shows all of the address books the groups appear in.
a Use the Filter to customize the list.
b Select the groups you want and click Specify Tier.
c Select the tier you want for the groups and click OK.
8 To associate guests with this address book, click Associate Guests.
The Address Book/Tier column shows all of the address books the guests appear in.
a Use the Filter to customize the list.
b Select the guests you want and click Specify Tier.
c Select the tier you want for the guests and click OK.
9 Click OK.
Polycom, Inc.
116
Using Multiple Address Books
Edit an Address Book
You can edit an address book to add or remove users, endpoints, rooms, groups, and guests.
You can find any of these entities that are not currently associated with an address book by selecting
Current Association from any Filter, then selecting Not Associated With An Address Book.
If a group is set up with the Enterprise Directory Viewable option not selected, you can still add that group
to an address book. The group itself will not appear as an entry in the address book, but the members of
the group will.
To edit an address book:
1 Go to Admin > Directories > Address Books.
2 Select an address book.
3 Click
.
4 Edit the fields in the Edit an Address Book dialog.
Field
Description
Address Book Information
Address Book Name
A meaningful name to identify this address book.
Description
A brief description of the address book.
Address Book Tiers
New Tier
Select where you want to add a tier and click to add a new tier to the address book.
Edit Tier Name
Select a tier and click to change a tier name.
Delete
Select a tier and click to delete a tier.
5 To associate users with this address book, click Associate Users.
The Address Book/Tier column shows all of the address books the users appear in.
a Search for the users you want to associate. Use the Filter to customize the list.
b Select the users you want and click Specify Tier.
c Select the tier you want for the users and click OK.
d To delete a user from the address book, select the user and click
.
The user is removed from the address book, but remains in the RealPresence Resource Manager
system.
6 To associate endpoints with this address book, click Associate Endpoints.
Only endpoints that are not associated with a RealPresence Resource Manager system user appear
in the list.
The Address Book/Tier column shows all of the address books the endpoints appear in.
a Use the Filter to customize the list.
b Select the endpoints you want and click Specify Tier.
c Select the tier you want for the endpoints and click OK.
Polycom, Inc.
117
Using Multiple Address Books
d To delete an endpoint from the address book, select the endpoint and click
.
The endpoint is removed from the address book, but remains in the RealPresence Resource
Manager system.
7 To associate rooms with this address book, click Associate Rooms.
The Address Book/Tier column shows all of the address books the rooms appear in.
a Use the Filter to customize the list.
b Select the rooms you want and click Specify Tier.
c Select the tier you want for the rooms and click OK.
d To delete a room from the address book, select the room and click Delete.
The room is removed from the address book, but remains in the RealPresence Resource
Manager system.
8 To associate groups with this address book, click Associate User Groups.
The Address Book/Tier column shows all of the address books the groups appear in.
a Use the Filter to customize the list.
b Select the groups you want and click Specify Tier.
c Select the tier you want for the groups and click OK.
d To delete a group from the address book, select the group and click
.
The group is removed from the address book, but remains in the RealPresence Resource
Manager system.
9 To associate guests with this address book, click Associate Guests.
The Address Book/Tier column shows all of the address books the guests appear in.
a Use the Filter to customize the list.
b Select the guests you want and click Specify Tier.
c Select the tier you want for the guests and click OK.
d To delete a guest from the address book, select the guest and click
.
The guest is removed from the address book, but remains in the RealPresence Resource
Manager system.
10 Click OK.
Assign Address Books to User Groups
You can assign an address book to a group, but you cannot assign address books directly to users. Group
assignment controls to which address book users and endpoints have access. Each group can have just
one address book assigned to it, but users can be in more than one group.
Address book priority affects which address book users and endpoints can access. For example, if a user
is a member of two different groups and each group is assigned a different address book, the user will see
the address book that is higher in priority. To change priority, see Change Address Book Priority.
To assign an address book to a group:
1 Go to User > User Groups.
Polycom, Inc.
118
Using Multiple Address Books
2 Select the group you want to assign.
3 Click
.
4 In the Edit Local Group dialog, select address book you want from the Assign Address Book
drop-down list.
5 Click OK.
Delete an Address Book
You can delete an address book when it is no longer needed. Deleting an address book does not delete the
users, endpoints, rooms, groups, or guests that were in the address from the RealPresence Resource
Manager system.
Any entity that was assigned the deleted address book will have access to one of the following:
● Another address book if the entity is a member of another group that is assigned to an existing
address book.
● The default address book.
To delete an address book:
1 Go to Admin > Directories > Address Books.
2 Select the address book you want to delete.
3 Click
.
A confirmation message appears.
4 Click Yes.
Change Address Book Priority
You can change the priority of address books. The priority determines which address book a user sees. For
example, if a user is a member of two different groups and each group is associated with a different address
book, the user will see the address book that is higher in priority.
The All Entries address book always has the highest priority and None always has the lowest priority. If the
address book for one of the groups the user belongs to is changed to All Entries, the user will see all entries
regardless of the priority of the address book for the other group.
To change address book priority:
1 Go to Admin > Directories > Address Books.
2 In the Priority column of an address book, enter the priority you want.
Use only whole numbers and only numbers that fall within the total count of address books. For
example, if you have four address books, only 1 through 4 are valid priority values.
3 Click Update Priority from the More drop-down list.
The system changes the order of the address book list.
Polycom, Inc.
119
Using Multiple Address Books
Set the Default Address Book
You can set the default address book. The default address book sets the address book all new users have
access to if no address book is assigned through a group.
If you do not want to use multiple address books in the RealPresence Resource Manager system, leave the
default address book set to All Entries (the default). Using this default, all users will be able to see all entries
in the directory. Be sure that all groups are assigned either the System Default or All Entries option.
System Default is the default group setting.
If you create multiple address books, you can change the default address book to one of the address books
you created.
To set the default address book:
1 Go to Admin > Directories > Address Books.
2 Click Set Default from the More drop-down list.
3 In the Default Address Book dialog, select the option you want:
 All Entries—Default setting. All users, endpoints, groups, rooms, and guests are in one address
book and all have access to all address book entries.
 None— No directory entries will be available.
 Specify—Select the address book you want as the default.
4 Click OK.
Copy an Address Book
You can copy an existing address book as a shortcut to creating a new address book. The copy process
can copy the entire address book or just the tier structure.
To copy an address book:
1 Go to Admin > Directories > Address Books.
2 Select the address book you want to copy.
3 Click Copy from the More drop-down list.
4 In the Copy Address Book dialog, select the option you want:
 Entire Address Book—This option copies all of the tiers and the users, endpoints, rooms,
groups, and guests that are associated with the address book to the new address book.
If areas are enabled, the address is copied to the same area to which the initial address book
belongs.
 Tiers only—This option copies only the tier structure to the new address book.
5 Enter a meaningful Name and Description.
6 Click OK.
You can now edit the new address book to add or delete entries.
Polycom, Inc.
120
Direct Conference Templates
You use MCU conference templates when you schedule conferences to take place on an MCU that has
been integrated with RealPresence Resource Manager system’s conferencing service.
This section includes the following topics:
● Direct Conference Templates Overview
● View the Direct Conference Templates List
● Add a Direct Conference Template
● Edit a Direct Conference Template
● Delete a Direct Conference Template
Direct Conference Templates Overview
Direct templates are based on existing conference profiles that have been created on the MCU. You can
choose to have the template automatically synchronized with its associated RealPresence Collaboration
Server (RMX) profile by maintaining the routing name of the RealPresence Collaboration Server (RMX)
profile or download the profile directly to the RealPresence Resource Manager system.
The RealPresence Resource Manager systems does not support scheduling conferences on
third-party MCUs. Direct Conference template settings apply only to the RealPresence Collaboration
Server (RMX) and MGC devices.
Users assigned the Administrator role can add Direct Conference Templates from any MCU that is
integrated the RealPresence Resource Manager system’s conferencing services. They can also identify (by
user role) which users have access to which Direct Conference Templates. Conference schedulers can
then select from the different templates available to them to switch between different combinations of
conference settings.
Direct conference templates do not display all available RealPresence Collaboration Server (RMX)
settings. Nor or all conference settings defined in the template used by the RealPresence Resource
Manager system when setting up a direct conference.
You create a direct conference templates in two ways:
● Standalone Templates: Download a conference profile from a managed MCU creating a “standalone”
(free-standing) template independent of the profiles available on the system’s RealPresence
Collaboration Servers, Polycom RealPresence Collaboration Server (RMX) systems, or Polycom
MGC systems.
Polycom, Inc.
121
Direct Conference Templates
● Linked Templates: Link the template to a RealPresence Collaboration Server or RealPresence
Collaboration Server (RMX) profile that exists on some or all of the MCUs.
Linked conference templates are not supported for Polycom MGC systems.
Conference templates for Pooled Conferences are created and managed on the Polycom
RealPresence DMA system.
For more information about the RealPresence Collaboration Server (RMX) profile settings, see Polycom®
RealPresence® Collaboration Server (RMX®) 1500/2000/4000 Administrator’s Guide.
Standalone Templates
Standalone templates defined in the RealPresence Resource Manager system free you from having to
ensure that the exact same conference profiles exist on all the MCUs.
When it uses a standalone template for a conference, the system sends the specific properties to the MCU
instead of pointing to one of its profiles.
Considerations for Polycom MGC Systems
Standalone or “downloaded” templates are the only ones allowed for use with Polycom MGC systems.
In addition, the RealPresence Resource Manager system does not support MGC templates that use the
following dual stream settings: Hi-Res Graphics or Live Video setting.
Linked Templates
When you link a conference template to a template to a RealPresence Collaboration Server or
RealPresence Collaboration Server (RMX) profile ensures that the template’s properties match the
capabilities on the MCU selected for the conference.
This means that when you use a linked template for a conference, you must also select the specific MCU
that contains the profile on which the template is linked.
When you link a template to a profile, it’s up to you to ensure that the profile exists on the MCUs you want
to use with that template and that its settings are the same on all of them.
If do not select the MCU from which the template is based, the scheduled conference will not launch.
As a best practice, when linking templates to MCU profiles, this will make it easier for conference schedulers
to select the bridge that corresponds with the template.
This option is not supported for MGC conference profiles.
Polycom, Inc.
122
Direct Conference Templates
Direct Conference Template Considerations for
Multi-Tenancy
● When areas are enabled, the templates available for a given conference depend on the area to which
the conference owner belongs. Only templates belonging to the same area as the conference owner
are available to use when scheduling a conference.
● When areas are enabled, be sure to give your area-specific names to your templates. This is
particular helpful if you have schedulers who have been given permission to manage more than one
area.
Direct Conference Template Best Practices
The RealPresence Resource Manager system has a Default Template. Administrators with Conference
Setup permissions can some settings of a standalone template.
When scheduling a conference, the Default Template, which is available to all users, is selected by default.
Schedulers can select a different conference template from the list of templates an administrator has made
available to them. Users with advanced scheduling permissions can edit the template settings for a specific
scheduled conference. These changes apply only to the specified conference.
Use these best practices when working with conference templates.
● For the Default Template, select settings that are the lowest common values for all device types.
This ensures that all conferences scheduled with the Default Template can successfully launch on
whatever devices the system has available at the time.
● The template names Default Template and Default Audio Templates are stored in the system
database and their names are not localized into other languages. If you wish to localized their names
into your language, edit the templates and enter new names for them.
When creating new direct conference templates, give them meaningful purposes and names so that
your users can easily identify the differences between template choices. For example, identify
templates according to maximum bit rate, specific features implemented by the template (for
example, Lecture Mode or Chairperson Control).
● As a best practice, when linking templates to MCU profiles, give the template a name that includes
the bridge name, this will make it easier for conference schedulers to select the bridge that
corresponds with the template.
If your RealPresence Resource Manager system has areas enabled, be sure to give your
area-specific names to your templates. This is particular helpful if you have schedulers who have
been given permission to manage more than one area.
View the Direct Conference Templates List
You can view a list of added direct conference templates.
To view the MCU Conference Template list:
1 Go to Conference > Direct Conference Templates.
The Direct Conference Templates list appears.
Polycom, Inc.
123
Direct Conference Templates
2 Select the template of interest from the list and click
.
You can expand the settings description in the right pane of the screen.
Add a Direct Conference Template
When you add a template to the RealPresence Resource Manager from an MCU, you can use it for
conferences you want to schedule. You can add conference templates from any MCU that is integrated with
the RealPresence Resource Manager system’s conferencing services.
To add a direct conference template:
1 Go to Conference > Direct Conference Templates.
2 On the Direct Conference Templates list, click
.
3 In the Select an MCU dialog, choose an MCU from which to add a template and click View Profile.
4 In the Select a Profile dialog, choose an MCU conference profile to add as a template.
 To link the template to its MCU profile, click Use Routing Name.
For more information, see Linked Templates
This option is not supported for MGC conference profiles.
 To create a standalone template, click Download Profile.
5 In the Add Direct Conference Template dialog, you can customize the profile summary.
Field
Description
General Settings
Template Name
Enter a unique and meaningful name for the template, which can be up to 50
characters long.
Description
Enter a meaningful description (ASCII only) of the conference settings template.
Audio-Only Template
Select this option to designate the template as an audio-only template. Selecting
this option disables many settings.
Supported MCUs
Specify the supported MCU type. Possible values include:
• RMX
• MGC
• RMX + MGC
Always Use MCU
When selected, an MCU is used for the scheduled conference, regardless of the
number of participants. When not selected, an MCU is used only when necessary.
Dial Options
These settings apply only to video conferences. The video dial options are:
• Dial-In Only (all participants dial into the conference)
• Dial-Out Only (all participants are called by the system)
• Dial-In + Dial-Out (The person setting up the conference can specify which
participants must dial into the conference and which participants are called by
the system.)
Polycom, Inc.
124
Direct Conference Templates
Field
Description
Assign Area
Select an area to which to assign this template.
This field is only visible when Areas are enabled.
A user can only view area-specific information for an area(s) that he has
permission to manage.
Template will be available to
users with the selected
roles...
Select the roles to which users must be assigned for them to see this template
when scheduling conferences.
Available Roles
The list of roles defined to the RealPresence Resource Manager system.
Selected Roles
The list of roles that can use the conference template being defined.
6 Click OK.
The new template appears in the Direct Conference Template list.
The RealPresence Resource Manager system does not validate the Conference Template settings.
When you create a new conference template, you must make certain that the settings match the
capabilities of the MCUs or endpoints.
Edit a Direct Conference Template
You can edit the profile of a direct conference template.
To edit a direct conference template:
1 Go to Conference > Direct Conference Templates.
2 On the Direct Conference Templates list, select the template of interest and click
.
3 Edit the Customized Profile Summary as needed.
4 Click OK.
Delete a Direct Conference Template
You can delete a direct conference template.
To delete a conference template:
1 Go to Conference > Direct Conference Templates.
2 On the Direct Conference Templates list, select a template and click
.
3 Click Yes to confirm the deletion.
Polycom, Inc.
125
Configuring Conference Settings
This section includes information about configuring MCU conference settings within the Polycom®
RealPresence® Resource Manager system. It includes these topics:
● Conference Settings
● Customizing Text to Email Notifications
Conference Settings
You can configure conference settings. Conference settings apply to conferences only. You can
disable/enable time warnings, set whether the conference requires a passcode, automatically include the
conference creator in conference, as well as enable overbooking of dial-in participants.
The settings you configure will be used for all conferences.
Conference settings apply to conferences scheduled using the RealPresence Resource Manager system.
These settings include:
Field
Description
Conference Time Warning
Specifies whether or not the Polycom RealPresence Resource Manager system
sends a message to video endpoints in a conference to warn the endpoint users
that their conference is scheduled to end soon. The system sends the message 17
minutes, 10 minutes and 5 minutes before the conference is scheduled to end.
To support this feature, the video endpoint system must be capable of receiving a
system Send Message action.
By default, Conference Time Warning is enabled.
Note
This feature is not related to the MCU-based End Time Alert Tone feature.
Pooled Conferences
This setting does not apply for Pooled Conferences.
Automatically Include
Conference Owner
(Scheduler) in New
Conferences
Select this option when you wish the system to always include the person
scheduling the conference as a conference participant. Do not select this option if
your organization has assistants or operators schedule conferences for others.
Allow overbooking of dial-in
participants
Select this option to allow schedulers to schedule dial-in participants to dial into
multiple conferences, but the system reserves resources for the participant for only
the first scheduled conference.
Polycom, Inc.
126
Configuring Conference Settings
Field
Description
Conference and chairperson
passcode length
Designate the required length of the system-generated conference and
chairperson passcodes. The acceptable length for both of these passcodes is 4 to
16 characters. By default, the required length for both of these passcodes is set to
15 characters.
Notes
• Depending on the system settings, the scheduler may be allowed to change the
conference or chairperson passcode. However, the passcode length
requirement still applies.
• If an administrator changes the passcode length here at the same time a
scheduler edits the passcode settings for a scheduled conference, the
scheduling operation may use either the old or the new length, depending on the
exact timing.
Include the Web Suite URL
in the notification email
Include the URL of the RealPresence Web Suite Experience Portal in the email
notification for the meeting.
Applicable for pooled and anytime conferences when the RealPresence DMA
system is integrated with a RealPresence Web Suite.
Web Suite Server Address
The server address of the RealPresence Web Suite Experience Portal.
This section includes the following topics:
● Specify Conference Settings
● Disable Conference Time Warning
● Automatically Include Conference Creator in Conference
● Overbook Dial-in Participants
● Set the Conference and Chairperson Passcode Length
Specify Conference Settings
Navigate to the conference settings page to configure conference settings.
To specify conference settings:
1 Go to Conference > Conference Settings.
2 On the Conference Settings page, make the required selections.
3 Click Update.
Disable Conference Time Warning
You can disable the warning that alerts users that their conference is ending.
To disable the conference time warning:
1 Go to Conference > Conference Settings.
Polycom, Inc.
127
Configuring Conference Settings
2 In the Conference Time Warning section of the Conference Settings page, clear the Enabled
check box.
3 Click Update.
Automatically Include Conference Creator in
Conference
Select this option when you wish the system to always include the person scheduling the conference as a conference
participant. Do not select this option if your organization has assistants or operators schedule conferences for others.
To automatically include the conference creator in the conference:
1 Go to Conference > Conference Settings.
2 Check the Automatically include conference creator (scheduler) in new conferences section of
the Conference Settings check box.
3 Click Update.
Overbook Dial-in Participants
A user with the administrator role can configure the system to allow scheduler’s to overbook dial-in
participants. In this case, dial-in participants can be scheduled to dial into multiple conferences, but the
system reserves resources for the participant for only the first scheduled conference. Dial-out participants
cannot be scheduled into multiple conferences.
This setting does not apply to guest participants. Guest participants can always be overbooked.
To allow schedulers to overbook dial-in participants:
1 Go to Conference > Conference Settings.
2 In the Allow overbooking of dial-in participants section of the Conference Settings page, check
the Enabled check box.
3 Click Update.
Set the Conference and Chairperson Passcode Length
You can designate the required length of the system-generated conference and chairperson passcodes.
The acceptable length for both of these passcodes is 6 to 16 characters. By default, the required length for
both of these passcodes is set to 15 characters.
Depending on the system settings, the scheduler may be allowed to change the conference or chairperson
passcode. However, the passcode length requirement still applies.
If an administrator changes the passcode length here at the same time a scheduler edits the passcode
settings for a scheduled conference, the scheduling operation may use either the old or the new length,
depending on the exact timing.
Polycom, Inc.
128
Configuring Conference Settings
To set the passcode length:
1 Go to Conference > Conference Settings.
2 Mark the Conference and chairperson passcode length check box.
3 Click Update.
Customizing Text to Email Notifications
You can configure the system to send conference notification emails. The same text will be used for all
conference notification email notifications. Within these emails, you can include customized text.
You can add, edit, or delete the customized text for your conference email notifications.
● Add Customized Text to Conference Email Notifications
● Edit Customized Text in Email Notifications
Add Customized Text to Conference Email
Notifications
You can customize the text for your conference email notifications. This text field is limited to 650 characters.
The text you type here will appear in plain text just as you typed it.
To add customized text to all conference E-mail notifications:
1 Go to Admin > Server Settings > E-mail.
2 In the The text entered below will be included with scheduling reminder E-mails section of the
E-mail page, type in the introductory text you want to appear at the start of all conferencing email
notifications.
3 In the Text at the End of the Reminder E-mail section of the E-mail page, type in the closing text
you want to appear at the end of all conferencing email notifications.
4 Click Update.
Edit Customized Text in Email Notifications
You can edit the customized text included in your conference notification emails.
To edit the customized text in all conferencing E-mail notifications:
1 Go to Admin > Server Settings > E-mail.
2 To change the introductory text, replace the text in the The text entered below will be included
with scheduling reminder E-mails section of the E-mail page with the new text you want to
appear at the start of all conferencing email notifications.
This text field is limited to 650 characters. The text you type here will appear in plain text just as you
typed it.
Polycom, Inc.
129
Configuring Conference Settings
3 To change the closing text, replace the text in the Text at the End of the Reminder Email section of
the E-mail page with the new text you want to appear at the end of all conferencing email
notifications.
This text field is limited to 650 characters. The text you type here will appear in plain text just as you
typed it.
4 Click Update.
Polycom, Inc.
130
Conference Scheduling
This section provides an introduction to the Polycom® RealPresence Resource Manager system video
conference scheduling functionality and operations. It includes:
● Conference Scheduling Overview
● Conference Scheduling
● Managing Conferences and Participants
● Managing the Guest Book and Favorites Lists
● Conference and Participant Details Reference
Polycom, Inc.
131
Conference Scheduling Overview
This section provides an introduction to the Polycom® RealPresence® Resource Manager system video
conference scheduling functionality and operations. It includes the following topics:
● Log into the system web interfac
● Conference Scheduler Roles
● Scheduling Participants
● Scheduling Bridges and DMA Pool Orders
● Recurring Conferences
● Anytime Conferences
Log into the system web interfac
To log into the RealPresence Resource Manager system web interface, you need the IP address or host
name of the RealPresence Resource Manager system server and your username, password, and domain.
Generally, you get three opportunities to enter the correct password. After three failed attempts, the system
returns an error message.
To log into the system:
1 Open a browser window and in the Address field enter the RealPresence Resource Manager
system IP address or host name.
2 When the RealPresence Resource Manager system Log In screen appears, enter your Username
and Password.
3 If necessary, select a different Language.
4 Click Login.
Conference Scheduler Roles
Users assigned a conference scheduling role can schedule conferences in a manner similar to other
calendar applications.
In the Scheduler role, you can schedule conferences and view information about your ongoing, past, and
future scheduled conferences. You can also add guests to and delete guests from the system Guest Book.
You cannot view information for conferences that you did not schedule.
Users assigned the Advanced Scheduler role can also select bridges and templates and edit some
conference settings.
Polycom, Inc.
132
Conference Scheduling Overview
Role
Supported Actions
View-Only Scheduler
View conferences that other users created
Scheduler
Add a new conference
Copy a conference you created
View details of a conference you created
Delete a conference you created
Advanced Scheduler
Add a new conference
Specify bridges and select templates for new conferences
Copy a conference you created
View details of a conference you created
Edit some conference settings
Delete a conference you created
Area Scheduler
Add a new conference
Edit a future conference you created
Copy a conference you created
View details of a conference you created
Delete a conference you created
Operator
Add a new conference
Specify bridges and select templates for new conferences
Copy any conference
Edit any future conference
Delete any future conference
View any conference
Manage any ongoing conference
Terminate any ongoing conference
Area Operator
All area scheduler functions
All advanced scheduler functions
Manage any ongoing conference
Terminate an ongoing conference
Polycom, Inc.
133
Conference Scheduling Overview
Scheduling Participants
When you schedule conferences, you select the participants you wish to join the conference from your user
directory. Depending on your system configuration, your user directory may be the enterprise directory, the
Global Address Book, or one or more local address books. It may also include Guest Book entries.
For participants that have multiple endpoints registered with the RealPresence Resource Manager system,
the system selects the participant’s default endpoint. You can change to another endpoint by selecting it
from the Call Info list or by editing the participant.
You can schedule participants without endpoints into conferences. You cannot schedule endpoints without
owners into conferences. The RealPresence Resource Manager system can be configured to allow you to
overbook dial-in participants. In this case, dial-in participants can be scheduled to dial into multiple
conferences during the same time period, but the system reserves resources for the participant for only the
first scheduled conference. Dial-out participants cannot be scheduled into multiple conferences at one time.
Scheduling Bridges and DMA Pool Orders
When you schedule a conference, you can select a single bridge or a RealPresence DMA pool order to host
the conference, depending on the permissions that you have been given by the administrator.
Conference Templates
Users with Advanced Scheduler or Operator permissions can also specify a conference template to use.
Two conferences scheduled with the same template may have different settings and behavior if they
are hosted on different types of MCUs. Minimize or eliminate such differences by ensuring that all
MCUs are similarly configured.
When using conference templates, keep in mind:
● Conference templates provide default conference settings. When you select a different template, you
are selecting the default conference settings for your conference.
● The Default Template and Default Audio Template are available to all users who can schedule
conferences. Other templates may also be available if they have been assigned to users with your
role.
● The Default Template and Default Audio Template are stored in the system database and their
names are not localized.
Conference templates for MCUs are stored in the RealPresence Resource Manager system, while
conference templates for Pooled Conferences are defined in the RealPresence DMA system.
MCU Selection
Users with the Advanced Scheduler or Operator role can select a MCU to host their conference by selecting
the Single Bridge option. When they select this option, the system presents a list of bridges that have the
capabilities and resources required to host their conference.
Polycom, Inc.
134
Conference Scheduling Overview
Because this bridge list depends on the template selection, users should make their template selection
before selecting a bridge. Otherwise, they may select a bridge that cannot meet their conferencing
requirements. In this case, the conference will fail to schedule.
Bridge Scheduling and Reassignment
When you schedule a conference, the system automatically assigns the conference to a bridge unless a
user with the default Advanced Scheduler or Operator role intercedes. If that bridge is down at the time the
system starts the conference, the RealPresence Resource Manager system attempts to dynamically
reassign the conference to another bridge with sufficient capabilities and resources.
● If the system can successfully reassign the conference to another bridge, the conference starts on
the newly selected bridge, and the system sends an updated conference email message to all
scheduled participants. This updated email includes a new dial-in number that dial-in participants
must use to join the conference.
● The system will chain bridge reassignments. This means that if the next bridge to which the system
assigns a conference is down at the time the system tries to start the conference, the system will try
to reassign the conference again.
● If the RealPresence Resource Manager system cannot find another bridge with the features and
capacity needed to support a conference, the conference fails to start. The system does not attempt
to modify the conference settings in any way. Instead, the system sends an email to notify the
conference organizer of the failure.
DMA Pool Orders
Instead of selecting a bridge for your conference, you can select a RealPresence DMA pool order to
manage your conference calls. This means that you do not need to track bridge availability or status of the
conference resources manually. When you select a DMA pool order for your conference, your scheduled
conference is hosted by the RealPresence DMA system. Using RealPresence DMA system defined
priorities, the RealPresence DMA system can manage resource allocation between RealPresence
Resource Manager system scheduled conferences and the RealPresence DMA-initiated ad hoc calls in
real-time.
Room ID Numbers
When you schedule your conference on a DMA Pool Order, you can also create a room ID and dial-in
number for participants to use. If you don’t specify a room ID, the RealPresence DMA system will create
one and the RealPresence Resource Manager associates it with the scheduled conference.
You can also use an existing VMR number that has been created on the RealPresence DMA system, as
long as the VMR is not already scheduled for the time you need it. When you use an existing RealPresence
DMA VMR, you can view the VMR settings on the RealPresence DMA VMR as “scheduled” (including the
time), but until the conference is started other settings will not display such as dial-out participants or
additional settings. These settings only get sent to the RealPresence DMA when the conference starts.
Polycom, Inc.
135
Conference Scheduling Overview
Limitations When Scheduling a Conference on a DMA Pool
Order
When scheduling your conference on a DMA pool order, you are limited by the following:
● You must use a modified dialing number when scheduling an ISDN dial-out participant. Use the Use
Modified Dial Number check box when scheduling an ISDN dial-out participant.
Recurring Conferences
When you schedule recurring conferences, the VMR associated with that recurring conference remains
associated with that conference. You can use the VMR during its free time. For example, the VMR
associated with a recurring conference scheduled at 9 a.m. to 10. a.m. on Mondays.You can still use this
VMR from the 10 .a.m. today to 9 a.m. tomorrow.
Anytime Conferences
Anytime conferences are scheduled RealPresence DMA conferences that do not have designated start and
end times. These conferences are not recurring. To be able to add Anytime conferences, the RealPresence
Resource Manager system must be connected to a Polycom RealPresence Distributed Media Application™
(DMA) system.
Anytime conferences do not have designated start and end times. Once an Anytime conference is
configured, conferences can be started at any time by authorized participants. The following events occur
when a new Anytime conference is added:
● A participant with scheduling permissions creates a new Anytime conference and the conference is
assigned a virtual meeting room (VMR) number.
● The Owner passcode is automatically generated and required to launch an Anytime conference.
● All Anytime conference participants receive an email indicating the VMR number. The owner will also
receive the owner passcode needed to launch the conference. Optionally, you can also include a
conference passcode that participants are required to enter.
● When a participant dials the VMR number and enters the owner passcode, all dial-out participants
are automatically called. If a participant dials into the VMR, they are not allowed into the conference
or placed on hold until someone dials in and enters the owner passcode.
● The conference continues until all participants hang up the call.
● You can terminate an anytime conference from the RealPresence Resource Manager UI. There is no
impact on the VMR.
Polycom, Inc.
136
Conference Scheduling
This section describes the Polycom® RealPresence® Resource Manager system conference scheduling
operations. It includes these topics:
● Schedule a Conference
● Schedule an Anytime Conference
● Copy an Existing Conference
● Edit a Future Conference
● Edit a Participant’s Settings
● View Scheduling Information for a Conference
Since Area Schedulers can perform both basic and advanced tasks, any references in this section to
the Scheduler role also applies to the Area Scheduler role.
Schedule a Conference
Users with the following default user roles are allowed to schedule conferences: scheduler, operator, area
operator and area scheduler.
When you schedule a conference, you specify the time, location and the list of participants. Optionally, you
can also assign conference roles to participants such as lecturer or conference chairperson. Users with
advanced scheduler or operator permission can also select a specific bridge and configure conference
settings.
When scheduling conferences, be aware that the time displayed in the lower left corner of the
RealPresence Resource Manager system is associated with the time clock of the local PC. See Edit
System Time Settings for how to view system time settings. You must have the administrator role to
view it.
Using NTP server is mandatory to schedule a conference.
To schedule a conference:
1 Go to Conference > Monitor View and click
.
2 Click Participant to add participants to the conference. You can add individual participants,
conference rooms or guests to the conference.
Polycom, Inc.
137
Conference Scheduling
•
•
•
For participants who are associated with endpoints, the RealPresence Resource Manager
system schedules their availability according to the endpoint’s availability.
For participants with multiple endpoints, check the availability for each endpoint. Click Call
Info to change the participant’s endpoint.
Dial-in participants can be scheduled to dial into multiple conferences during the same time
period; dial-out participants cannot.
3 To add a participant:
a Select Add Participant.
b Click
and type all or part of the participant (with wildcards) in either of the fields provided.
c Click Search.
d Select the participant you want from the search results.
4 Select Add Guest, select a guest from the list.
You can also click
to filter the list by entering the last or the first name of the guest you want.
If you want to add a new guest to the guest book, click Add Guest button. After you have added the
new guest to the guest book, you can add that guest to the conference from the list. You must be an
Advanced Scheduler or an Operator to add a new guest to the guest book.
5 To add a room:
a Select Add Room.
b Select a site from the Search for Rooms at a Site drop-down list.
c Select a room from the list of rooms associated with the site you selected.
6 When finished adding participants, rooms or guests, click Close.
7 Enter a new Conference Name or accept the system-generated name.
8 Use the Bridge Selection drop-down list to select a bridge or RealPresence DMA pool order for the
conference.
Only users with the Advanced Scheduler or Operator role can select a bridge. RealPresence DMA
pool orders are only available when your system is integrated with a RealPresence DMA system.
9 Select Start Time, Duration, and End Time for the conference for the conference.
10 If you want to make the conference recurring:
a Click Recurrence and in the Appointment Recurrence dialog, set:
 Recurrence frequency (Daily, Weekly, or Monthly)
 Recurrence day (Sunday through Saturday)
 Recurrence range (Start date and End After occurrences or End by date)
The maximum number of recurrences is 365.
b Click OK.
11 Assign roles to participants. If the conference type and template support conference roles, you can
associate conference roles with participants.
a Expand the Role Settings area.
b Use the drop-down lists to select Lecturer, Video Chairperson, or Owner. You must first add
participants before assigning them a role.
Polycom, Inc.
138
Conference Scheduling
Role
Description
Owner
Required for an Anytime conference. The owner is the participant who dials into
the conference and enters a passcode to start the conference.
Video Chairperson
Video Chairperson: You can select a video chairperson to control the conference
from his or her video endpoint system. The video chairperson must have a video
endpoint system and Chairperson conferences require an MCU.
Chairperson Passcode
If you enable Enable Chairperson passcode, the system assigns a
Chairperson Passcode and provides this password to the video chairperson in a
separate email.
When enabled for a conference, the chairperson must enter this password at his
or the video endpoint to assume control of the conference.
The length of the password is specified in the Conference and chairperson
passcode length drop down list on the Conference Settings page.
Lecturer
Designates the participant as the main participant in the conference. If you
designate a lecturer for a conference, that participant will not be muted if the
video operator mutes all.
12 To modify conference settings, expand the Conference Settings area.
Only users with the Advanced Scheduler or Operator role can modify conference settings.
Available for MCU or
RealPresence DMA
Pool Order
Conference?
Setting
Description
Conference Type
Select Video or Audio Only.
Video conferences can include audio participants. If you
choose an audio-only conference, video participants can only
participate on audio channels only and no video will be
displayed.
MCU conferences only
Conference ID
By default, the system assigns a Conference ID. You can
change this ID to permit integration with third-party scheduling
tools. This identifier must be 8 or less numeric digits.
Note that the RealPresence Resource Manager system
compares the Conference ID to it’s database to verify that it is
unique. If it is not unique, you will be prompted to enter a new
Conference ID.
Not available for Pooled Conferences.
MCU conferences only.
Room ID
By default, the RealPresence DMA will assign VMR as a
Room ID. You can leave this field empty.
RealPresence DMA
Pool Order
conferences only
Conference
Passcode
By default, the system assigns an 15-digit Conference
Passcode and provides this passcode to participants within
the content of the conference notification email.
You can change this passcode to another 4-digit through
16-digit number.
MCU conferences and
RealPresence DMA
Pool Order
conferences.
Polycom, Inc.
139
Conference Scheduling
Available for MCU or
RealPresence DMA
Pool Order
Conference?
Setting
Description
Conference Template
The available conference templates are automatically filtered
according to the Conference Mode you select and listed in
alphabetical/numerical order. When choosing a template for a
RealPresence DMA pool order conference, the template list is
ordered by the priority that was defined for the template in the
RealPresence DMA system.
MCU conferences and
RealPresence DMA
Pool Order
conferences.
Billing Code
Billing code is listed if areas are enabled and billing codes
have been assigned to the area. If areas are enabled and a
billing code is not assigned, the call detail report will list the
billing code as None.
MCU conferences and
RealPresence DMA
Pool Order
conferences.
Conference Mode
All: Supports all conferences.
Video Switching (VSW):
Enables a special conferencing mode that provides HD
video while using MCU resources more efficiently. All
participants see the current speaker full screen (the
current speaker sees the previous speaker).
If video switching mode is enabled:
 The minimum line rate available is 768 kbps (except for
SD resolution, available only on v7 and newer Polycom
MCUs with MPM+ or MPMx cards). • All endpoints must
connect at the same line rate, and those that don’t
support the specified line rate are connected in
voice-only mode.
 The video clarity, layout, and skins settings are not
available.
 LPR is automatically turned off, but can be turned back
on.
Continuous Presence (CP):
The MCU selects the best video protocol, resolution, and
frame rate for each endpoint according to its capabilities.
Select this mode if scheduling only AVC endpoints.
This is the only mode that supports the use of Polycom
MCU profiles, third-party and legacy endpoints, and legacy
RealPresence Collaboration Server (RMX) MCUs.
SVC conferencing is only possible with Polycom MCUs and
endpoints that support H.264 SVC.
CP and SVC:
The MCU selects the best video protocol, resolution, and
frame rate for each endpoint according to its capabilities.
Select this CP and SVC if scheduling both AVC and SVC
endpoints.
MCU Conferences
only.
13 Click Schedule Conference.
14 Optionally, send a notification e-mail to participants.
Polycom, Inc.
140
Conference Scheduling
a To exit without sending an updated email message to your participants, click Skip E-mail.
b To send an updated email to your participants, copy additional people on the notification and/or
add notes about the conference.
Note that the To, CC, and BCC fields are ASCII only.
c Click Send.
Configure Advanced Settings
You can use the settings in the Advanced Settings section when you schedule a conference directly on an
MCU instead of using a RealPresence DMA Pool order. In particular, advanced settings include parameters
related to dialing options and configuration of a Polycom MGC system which include content options, as
well specific bit rates or modes to use.
To configure advanced settings:
1 Expand the Advance Settings area.
2 Complete the following settings if you scheduled the conference on a Polycom MGC system.
Dial Options
You have three options:
• To create a conference for which the same dial-in information and a PIN code
are assigned to all conference participants, use the Dial-In setting. This setting
enables participants to dial in from an audio or video endpoint and connect to the
same conference on the MCU.
• To dial out to all participants in the conference, use the Dial-Out setting.
• To allow participants both options, select Dial-In+Dial-Out.
Note
When you change a conference from Dial-In to Dial In+Dial Out, the selected
resources remain set to Dial-In. You must change them manually.
Not available for Pooled Conferences.
Always Use MCU
Forces the conference to an MCU and prevents video endpoints from connecting to
each other directly. This setting is automatically selected and cannot be changed
when Audio Only is the conference type or when Enable Chairperson is selected.
Video Mode
Determines the initial layout on a video endpoint's monitor for a multipoint
conference that requires an MCU. The options are:
• Switching. Indicates that the display changes each time the speaker changes,
and everyone sees the current speaker.
• Select a Frame Count, then select the specific layout for the frames.
Available layouts are Continuous Presence settings.
Polycom, Inc.
141
Conference Scheduling
Bit Rate
Specifies the maximum connection speed for endpoints in the conference.
Individual endpoints that specify a lower connection speed connect at that lower
speed. Endpoints that specify a higher connection speed connect at the speed
identified in the conference template.
If you select a higher speed than an endpoint can support, the system reduces the
speed that endpoint; however, the conference uses the default connection speed
for endpoints that can match it. If you place the calls through an endpoint with an
embedded MCU, the behavior depends on the capabilities of that endpoint.
When the dial speed is higher than the number of channels defined in the H.320
service for the endpoint, you receive a warning. To continue, lower the dial speed to
less than or equal to the ISDN capability of the endpoint.
Higher speed is important for high-quality video in a conference. Because higher
speeds use greater bandwidth, scheduling a high-bandwidth conference may limit
the number of conferences that you can reserve at one time.
T.120 Mode
For MGC-hosted conferences only, selects the protocols and specifications for
multipoint data communication.
In the T.120 menu, select the speed for the T.120 connection. See your IT
department to determine the best combinations for your conferences. To disable
the T.120 mode, select None.
If you select T.120, these options may be available, according to the participant’s
endpoint and software:
• Application Sharing. Enables two or more participants to work on the same
document or application, even when only one participant has the application. In
application sharing, one participant launches the application, and it runs
simultaneously on all other computers.
• File Transfer. Enables participants to send files to each other.
• Chat or Whiteboard. Enables participants to communicate with each other by
writing.
In all of these modes, participants can view and hear each other.
Not available for Pooled Conferences.
Schedule an Anytime Conference
Users with the following default user roles are allowed to schedule Anytime conferences: Scheduler,
Advanced Scheduler, Operator, Area Operator and Area Scheduler.
if your RealPresence Resource Manager system is not integrated with a RealPresence DMA system, you
cannot create an Anytime conference.
To schedule an Anytime conference:
1 Go to Conference > Monitor View and click
.
2 Mark the Anytime check box which is to the right of the Bridge Selection drop-down list.
3 Click Participants to add participants to the conference.
a Select one of the following: Add Participants, or Add Rooms or Add Guest.
Polycom, Inc.
142
Conference Scheduling
b Click
and type all or part of the participant or room name (with wildcards) in either of the fields
provided. If searching for a room, use the Last Name or Room Name field.
c Click Search.
d Select the participant or room you want from the search results.
e To add a guest, select Add Guest, select a guest from the list and click Add Guest.
You can also filter the list by clicking
want.
f
and entering the last or the first name of the guest you
Repeat these steps to add all required participants, rooms and guests and then click Close.
4 Enter a new Conference Name or accept the name that the system generated.
5 Use the Bridge Selection drop-down list to select a RealPresence DMA pool order for the
conference.
6 Assign roles to participants. If the conference type and template support conference roles, you can
associate conference roles with participants.
a Expand the Roles Settings area.
b Use the drop-down lists to select an Owner for the conference. You must first add participants
before assigning them a role.
Role
Description
Owner
Required for an Anytime conference. The owner is the participant who dials into
the conference and enters a passcode to start the conference.
Video Chairperson
Video Chairperson: You can select a video chairperson to control the conference
from his or her video endpoint system. The video chairperson must have a video
endpoint system and Chairperson conferences require an MCU.
Chairperson Passcode
A chairperson passcode is required for an Anytime conference.
If you use a Chairperson passcode, the system assigns an 15-digit
Chairperson Passcode and provides this password to the video chairperson in a
separate email.
When enabled for a conference, the chairperson must enter this 15-digit
password at his or her video endpoint to assume control of the conference.
You can change this password to another 4- through 16-digit number.
Lecturer
Designates the participant as the main participant in the conference. If you
designate a lecturer for a conference, that participant will not be muted if the
video operator mutes all.
7 Configure conference settings.
a Expand Conference Settings.
b Enter a conference passcode.
8 (Optional) Enter a Room ID to use. If this field is empty, RealPresence DMA will assign a VMR
number.
9 To save the conference details, click Save.
Polycom, Inc.
143
Conference Scheduling
Copy an Existing Conference
You can copy an existing conference to be used as a template for a new conference.
Users can only copy conferences that appear in their All Conferences list. By default, schedulers see only
their conferences in the All Conferences list, while operators see all the conferences on the system, unless
areas are defined. In which case operators see all the conferences for the areas to which they belong. By
default, users assigned other roles cannot view conferences.
To copy a conference:
1 Go to Conference > Monitor View.
2 Select the conference of interest and click
.
3 If you used a template other than the default when you created the conference, re-select the
template.
4 Make the required changes to the conference date, participants, rooms, or other settings.
5 When finished, click Schedule Conference.
The system verifies that it has a bridge with the capabilities and resources required for your
conference. If it does, the conference notification email appears with a message indicating
Conference Successfully Scheduled.
6 To exit without sending an updated email message to your participants, click Skip E-mail.
Edit a Future Conference
You can modify future conferences.
Users can only edit the conferences that appear in their Conference list. By default, schedulers see only
conferences in the All Conferences list, while operators see all the conferences on the system, unless
areas are defined. In which case operators see all the conferences for the areas to which they belong. By
default, users assigned other roles cannot view conferences.
To edit a conference:
1 Go to Conference > Monitor View.
2 Click
to display future conferences.
3 Select the conference of interest and click
.
4 If you select a recurring conference, a dialog appears asking if you want to edit all conferences in
the series or just the selected one. Make the appropriate choice and click Edit.
The conference scheduling page appears.
5 Make the required changes to the conference date, participants, or other settings. For information
on performing these tasks, see Schedule a Conference.
6 When finished, click Schedule.
The system verifies that it has a bridge with the capabilities and resources required for your
conference. If it does, the conference notification email appears with a message indicating
Conference Successfully Scheduled.
7 To exit without sending an updated email message to your participants, click Skip Email.
Polycom, Inc.
144
Conference Scheduling
8 To send an updated email to your participants, copy additional people on the notification and/or add
notes about the conference.
Note that the To, CC, and BCC fields are ASCII only.
9 Click Send.
The system sends the updated conference notification email message. The Conference > Monitor
View appears. Your conference appears in the conference list.
Edit a Participant’s Settings
You can edit conference participant settings after you have added them to a scheduled conference. If the
conference is ongoing or already taken place, you can no longer edit the settings.
When you edit a participant’s settings, those settings are valid only for the current conference that you are
scheduling.
To edit a participant’s settings:
1 Go to Conference > Monitor View.
2 Select a future conference of interest and click
.
3 If you select a recurring conference, a dialog appears asking if you want to edit all conferences in
the series or just the selected one. Make the appropriate choice and click Edit.
4 In the conference scheduling page, click
Settings dialog.
beside a participant to open the Edit Participant
5 In the Edit Participant Settings dialog, you can edit the participant settings as required:
Field
Description
Endpoints
Select an endpoint from the list.
How will this
participant/room/guest join the
conference?
Select In Person, Audio Only or Use Video.
Bit Rate
Select the Bit Rate at which the participant will join the conference.
If you select Automatic, the participants bit rate will match the bit rate setting
configured for the conference when it was scheduled.
Dial Options
Select either Dial-In or Dial-Out.
Dial Type
Select either H.323, SIP (SIP URI) or H.320.
If no dial type is selected, it defaults to E.164.
If H.323 is selected for Dial
Type:
Polycom, Inc.
Number:
• Completed automatically and is read-only when the user is not a guest.
• Modify the number type if necessary (IP address, E.164, H.323, Annex-0)
• Add an extension if needed.
145
Conference Scheduling
Field
Description
If SIP is selected for Dial
Type:
•
SIP URI: Completed automatically and is read-only when the user is not a
guest.
Note
When scheduling a SIP dial-out participant, you cannot schedule the
participant as audio-only, encrypted, or use and extension.
If ISDN is selected for Dial
Type:
Enter the country code, area code, and phone number as necessary.
Use a modified dial number if you need to dial a prefix or an outside line first.
Note
You must use a modified dialing number if you are adding a dialout ISDN
participant.
Encryption
Indicate if this participant will join the conference under encryption.
Remember that the MCU that hosts the conference must be configured to
support encryption for this setting to take effect.
MCU Service:
Choose from the list of MCU services defined on the MCUs with which the
RealPresence Resource Manager system is registered. Leave this at Any
Available Service unless you have specific knowledge of MCU services.
6 When finished, click OK.
View Scheduling Information for a Conference
Users can only view scheduling information for the conferences that appear in their All Conference list.
By default, schedulers see only their conferences in the All Conference list, while operators see all the
conferences on the system, unless areas are defined. When areas are defined, operators see all the
conferences for the areas to which they belong. By default, users assigned other roles cannot view
conferences.
To view the scheduling information for a scheduled conference:
1 Go to Conference > Monitor View
2 From the
list, select the conference type of interest.
3 Select the conference to view from the list. Under Conference Actions, click
.
The detailed information of this conference is displayed on the right.
For details on the type of information that is provided, refer to Conference and Participant Details
Reference.
Polycom, Inc.
146
Managing Conferences and Participants
This section describes how the Polycom RealPresence Resource Manager system manages conferences
and conference participants. It includes these topics:
● Working with Conferences
● Managing Active Conferences
● Managing Participants within an Active Conference
Working with Conferences
You can view ongoing, past, and future conferences. You can view them in a list view or calendar view.
What you see depends on your user permissions. For example, if you have the view-only scheduler role,
you cannot see the details of any conferences. Those with the operation role can view all conferences,
including details.
For more information about roles, see Conference Scheduler Roles.
This section includes the following topics:
● View All Conferences
● Filter the Conference List
● Delete a Conference
● Export a List of Conferences
View All Conferences
You can view both scheduled and ongoing conferences in the conference monitor view. You can toggle
between a calendar and list view of all conferences.
When you view a conference, you can also view its status and any applicable alerts.
State
Description
Future Conference
Scheduled conference that has not yet started.
Completed Conference
A scheduled conference that occurred in the past.
Conference
A conference that is still /ongoing.
Polycom, Inc.
147
Managing Conferences and Participants
State
Description
Alerts Conference
The bridge on which the /ongoing conference is being hosted has sent an alert.
Examples of events that will trigger a bridge alert are:
• A participant is connected in secondary mode (audio only).
• A conference is not yet full (for example, not all scheduled participants have
joined the conference).
Note
This state does not apply to conferences scheduled on a RealPresence DMA Pool
Order.
Conference End Warning
The conference is ending. For example, the conference is in its last five minutes
unless someone extends it.
To view all conferences:
1 Go to Conference > Monitor View.
The All Conferences list displays a list of all conferences.
2 To view the list in calendar view, click
.
The All Conferences page displays the conferences in a calendar view. Click Day, Week, or Month
to change the calendar view.
3 To view the list in list view, click
again.
Filter the Conference List
You can filter the conference list to identify specific conferences you want to view. You must be in list view
to filter the conference list. Filtering is not available in calendar view.
You can filter by a number of criteria including date, bridge, conference name and so on.
To filter the conference list:
1 Go to Conference > Monitor View.
The All Conferences list displays a list of all conferences.
2 Click
to filter the All Conference list.
The Filter dialog allows you to filter on the various criteria.
3 To filter by date:
a Click Today to filter on conferences happening today.
Optionally, you can change the date to filter on conferences for a specific day.
b Click From and To to filter on conferences within a range of dates. Select From and/or To and fill
in the dates in the following format: YYYY-MM-DD or use the calendar tool to select a date.
4 To filter by Anytime conferences:
a Mark the Anytime check box to see all Anytime conferences.
b Optionally, use the date filtering options in combination with the check box.
Polycom, Inc.
148
Managing Conferences and Participants
5 To filter by status:
a Click Status.
b Click the text box and select a status from the context menu. Available statuses include: All,
Future, History, and Ongoing.
c Optionally, use the date filtering options in combination with the check box.
6 To filter by bridge:
a Click Bridge and fill in a bridge name in the text box.
b Optionally, use the date filtering options in combination with the check box.
7 To filter by dial in number:
a Click Dial in Number and enter a dial in number in the text box.
8 To filter by creator:
a Click Creator and enter first name or last name in the text box.
9 To filter by conference owner:
a Click Owner and fill in the owner’s name in the text box.
b Optionally, use the date filtering options in combination with the check box.
10 To filter by conference name:
a Click Conference Name and fill in the conference name in the text box.
b Optionally, use the date filtering options in combination with the check box.
11 To filter by endpoint name:
a Click Endpoint Name and fill in the conference name in the text box.
b Optionally, use the date filtering options in combination with the check box.
12 To filter by area:
a Click Area and fill in the area name in the text box.
b Optionally, use the date filtering options in combination with the check box.
13 When finished selecting criteria, click Search.
Only 1000 results can be returned when there are over 1000 results.
Delete a Conference
You can delete future or past conferences. You cannot delete active conferences.
To delete a conference:
1 Go to Conference > Monitor View.
2 If necessary, filter the All Conferences list to include the conference you want to delete.
3 Select the conference of interest and click
.
4 If you select a recurring conference, a dialog appears asking you if you want to delete just the
conference you selected or all conferences in the series. Make the appropriate choice. You cannot
deleted active conferences in the series.
Polycom, Inc.
149
Managing Conferences and Participants
5 Click OK to confirm the deletion.
The conference is deleted. For future conferences, the system emails the change to the conference
owner and participants and releases the participant and room resources.
Export a List of Conferences
Users with the Operator or Admin role can export a list of future conferences to a CSV file.
This option is only available when the list of conferences is filtered by Future.
To export a list of future conferences to a CSV file:
1 Go to Conference > Monitor View.
2 In the All Conferences list, be sure you filter the conference list to include only conferences that are
scheduled in the future. You cannot export ongoing or past conferences.
3 Click
.
Managing Active Conferences
Depending on your permissions, you can manage active conferences. For example, you can change the
layout that participants see or add new participants.
You can also manage participants within an active conference, see Managing Participants within an Active
Conference.
RealPresence Immersive Studio systems display as expandable folders containing an icon for each of
the codecs associated with the endpoint. You can only perform actions on the master codec. The
master codec is indicated by name of the codec that ends with “_1”.
Manage an Active Conference
You can manage an active conference. Users with the operator or advanced scheduler role can make
changes to the conference, such as add new participants, terminate the conference and so on.
To manage an active conference:
1 Go to Conference > Monitor View.
2 From the list of All Conferences, select the conference of interest and click
.
The conference page appears in a new tab displaying the Participants list. The Participants list
displays these settings:
Polycom, Inc.
150
Managing Conferences and Participants
Section
Description
Status
The state of the participant’s connection as identified by an icon. Hover over the icon to
determine the status.
Type
The type of conference as identified by an icon. Hover over the icon to determine the
type.
Name
The participant’s name.
Endpoint
The name assigned to the participant’s endpoint when it registered or was added to the
system.
Access
The endpoint’s network interface type. Possible values include:
• H323_E164
• H323_ID
• H323_ANNEX_O
• ISDN
• SIP
Address
The IP address, E614 number,H323 alias, or ISDN number of the participant’s endpoint
(if a dial-out), or SIP URI.
Bit Rate
The sum of the audio and video data transfer rate (in kbps) of the participant’s endpoint.
Dial Mode
How the participant joined the call. Possible values include:
• Audio or Video Dial-In
• Audio or Video Dial-Out
Bridge
The MCU or RealPresence DMA pool order on which the participants call resides.
3 Use these actions under the Conference Actions drop-down list as needed:
Action
Use this action to...
Extend Duration
Extend the duration of an active conference.
Change Layout
For applicable endpoints.
Change the default video layout for the conference display.
• Switching. Indicates that the display changes each time the speaker changes, and
everyone sees the current speaker.
• Select a Frame Count, then select the specific layout for the frames.
The available layouts are Continuous Presence settings.
Add Favorites
Add participants from one of your Favorites lists to the selected conference.
4 Use these under the Participant Actions drop-down list as needed. See Manage a Participant’s
Endpoint During a Conference for details.
Write Conference Notes During a Conference
You can write conference notes when managing an ongoing conference.
Polycom, Inc.
151
Managing Conferences and Participants
To create a conference note:
1 Go to Conference > Monitor View.
2 Click
to filter the All Conference list to include the conference of interest.
3 From the list of All Conferences, select the conference of interest and click
.
4 Expand the Conference Notes pane on the far right of the screen.
5 Click inside the text box to type a note.
If you type a note and then decide to undo your changes, click Escape to return to the original note.
6 Click Save.
The note becomes visible on any RealPresence Resource Manager browser session where other
users are monitoring the same conference.
Add Additional Participants to an Active Conference
Users with the Operator role can add additional participants to an active conference.
To add participants from the local directory or enterprise directory:
1 Go to Conference > Monitor View.
2 Click
to filter the All Conference list to include the conference of interest.
3 From the list of All Conferences, select the conference of interest and click
.
4 Go to Conference Actions > Add Participant.
5 If necessary, edit the new participants’ settings.
6 To initiate the system dial out to new participants, select the participants of interest from the New
Conference Participants list and click Connect New Participants.
The system dials out to the participants and adds them to the conference.
Add Guests to an Active Conference
Users with the Operator role can add guests to an active conference.
If guests with the same dialing string and different extensions are added into a RealPresence DMA
ongoing meeting, and then disconnected to the meeting. The guests may not reconnect to the
meeting successfully. You need to remove the guests and add them back to the meeting manually.
To add participants from the Guest Book:
1 Go to Conference > Monitor View.
2 Click
to filter the All Conference list to include the conference of interest.
3 From the list of All Conferences, select the conference of interest and click
.
4 Go to Conference Actions > Add Participant.
5 Click Add Guest.
Polycom, Inc.
152
Managing Conferences and Participants
6 From the Guest Book dialog, select the guest’s name from the list.
You can also click
to filter the list by entering the last or first name of the guest you want to add.
The guest’s name appears in the underlying New Conference Participants list.
7 Repeat step 6 to add all guest participants and then click Close.
8 To add new guest participants (participants not available from the local directory, enterprise
directory, or Guest Book), do the following:
a Click the Add Guest radio button.
b Fill in the necessary information in the Add Guest dialog.
c Click OK.
9 To initiate the system dial out to new participants, select the participants of interest from the New
Conference Participants list and click Connect New Participants.
The system dials out to the participants and adds them to the conference.
Add a Room to an Active Conference
You can add a room to an active conference.
To add a room to an active conference:
1 Go to Conference > Monitor View.
2 Click
to filter the All Conference list to include the conference you want to manage.
3 Select the conference of interest and click
.
4 From the Conference Actions list, click Add Room.
5 From the Add Room dialog, select the site location of the room.
The list of conference rooms at the site appears.
6 Select the conference room of interest.
The conference room name appears in the underlying New Conference Participants list.
7 Click Close.
8 To initiate the system dial out to the room, select the room from the New Conference Participants
list and click Connect New Participants.
The system dials out to the room endpoint system and adds the room to the conference.
View a Participant’s Video During a Conference
You can view a participant’s video during an ongoing conference. This is helpful to troubleshoot any video
issues during the conference.
To view the video of a participant in an active conference:
1 Go to Conference > Monitor View.
2 Click
to filter the All Conference list to include the conference you want to manage.
3 Select the conference of interest and click
Polycom, Inc.
.
153
Managing Conferences and Participants
4 Select a participant from the Participants list.
The selected participant’s video appears in the Conference Image section of the interface.
5 Click Shuffle to shuffle to the next participant’s video.
Join an Active Conference
By default, users assigned the Operator role can join an active conference to offer conference support.
To join an active conference:
1 Go to Conference > Monitor View.
2 Click
to filter the All Conference list to include the conference you want to manage.
3 Select the conference of interest and click
.
4 From the Conference Actions list, click Join Conference.
The Join Conference dialog appears.
5 If you have multiple endpoints, choose the endpoint to use to join the conference.
6 Click Join Conference.
Your endpoint is added to the conference with your video blocked but your audio not muted.
Add a Participant from a Favorites List to an Active
Conference
By default, users assigned the Operator role can work with favorites lists.
To add a participant from a favorites list to an active conference:
1 Go to Conference > Monitor View.
2 Click
to filter the All Conference list to include the conference you want to manage.
3 Select the conference of interest and click
.
4 From the Conference Actions list, click Add Favorites.
5 From the Favorites List, expand the list of interest.
The names of the participants in the list is displayed.
6 Select the participant of interest from the list.
The participant’s name appears in the underlying New Conference Participants list.
7 Repeat steps 5 and 6 to add all participants from Favorites List and then click Close.
8 To initiate the system dial out to new participants, select the participants of interest from the New
Conference Participants list and from the New Participants Action menu, click Connect New
Participants.
The system dials out to the participants and adds them to the conference.
Polycom, Inc.
154
Managing Conferences and Participants
Terminate an Active Conference
You can terminate an active conference.
To terminate an active conference:
1 Go to Conference > Monitor View.
2 Click
to filter the All Conferences list to include the conference you want to terminate.
3 Select the conference of interest and click
.
4 Click Terminate to confirm the termination.
Managing Participants within an Active Conference
When monitoring a conference, you can manage the participants within the conference. You can manage
their endpoints, and view the technical details of their connection.
Add or Save a Participant to a Favorites List
By default, users assigned the Operator role can work with favorites lists.
To add or save a conference participant to a favorites list:
1 Go to Conference > Ongoing.
2 Click
to filter the All Conference list to include the conference you want to manage.
3 Select the conference of interest and click
.
4 From the Participants list, select the participant of interest.
5 From the Participant Actions menu, click Save as Favorite.
The names of the participants in the list is displayed.
6 From the Save as Favorite Participant dialog, select the Favorite List to which to save the
participant and click OK.
Manage a Participant’s Endpoint During a Conference
You can manage a participant’s endpoint during a conference.
When using the commands on the manage page, these context-sensitive commands only appear
when the participant’s endpoint supports the action, and the commands work for rooms on the
participant list as well.
To manage a participant’s endpoint:
1 Go to Conference > Monitor View.
2 Click
Polycom, Inc.
to filter the All Conferences list to include the conference you want to manage.
155
Managing Conferences and Participants
3 Select the conference of interest and click
.
The Participants list appears.
4 Select a participant to manage.
5 From the Participants Actions list, select View.
The View Participants Details dialog displays
6 From the View Participants Details dialog, choose a manage option from the right section of the
dialog.
The following actions are available:
Action
Use this action to...
Mute or
Unmute Audio
Mute or unmute the selected participant’s audio line into the conference. This option
appears only when the conference is running on an external MCU. The Audio column in
the Participants list shows the current status of this setting.
Block or
Unblock Video
Block or unblock the selected participant’s video line into the conference. This option
appears only when the conference is running on an external MCU. The Video column in
the Participants list shows the current status of this setting.
Connect or
Disconnect
Disconnect or reconnect the selected participant to the conference. A disconnected
participant is still associated with the conference and cannot be scheduled for other
conferences.
Remove
Remove the selected participant from the Participants list at which time the participant
can be scheduled for another conference.
Send Message
Send a message to the selected participant’s registered Polycom endpoint. The
message appears briefly on the monitor for the selected video endpoint.
Acknowledge Help
Acknowledge a request for help and send a message to the requesting endpoint.
Manage Device
Open the web-based user interface for the selected participant’s endpoint in a new
browser window.
Note
Not available when managing a conference.
Save as Favorite
Function available when the selected participant has an associated endpoint to which
the system can dial out.
Save the selected participant to an existing Favorites List.
View a Participant’s Details During a Conference
You can view details for a participant’s endpoint while the participant is in conference.
RealPresence Immersive Studio systems display as expandable folders containing an icon for each of
the codecs associated with the endpoint. You can only perform actions on the master codec. The
master codec is indicated by name of the codec that ends with “_1”.
To view a participant’s endpoint details:
1 Go to Conference > Monitor View.
Polycom, Inc.
156
Managing Conferences and Participants
2 Click
to filter the All Conferences list to include the conference you want to manage.
3 Select the conference of interest and click
.
The Participants list appears.
4 To view participants endpoint details, click Participant Actions > View.
5 Double-click on the participant of interest.
The View Participant Details dialog appears with the Call Properties displayed. It includes the Near
End and Far End video, the Participant’s name, Status, Errors, Warnings, Endpoint Type,
Address, Access, and Bit Rate.
It also includes a list of Participant Actions. For more information about these actions, see Manage
a Participant’s Endpoint During a Conference.
6 To view additional participant details, change the selection in the Call Properties drop-down menu.
 If you select Device, you’ll see these participant details:
Setting
Description
Endpoint Type
Usually the endpoint model, such as Polycom HDX system.
IP Address
The IP address for the endpoint.
Site
The location of the endpoint as identified by its IP address and the subnet of
the site.
Gatekeeper
The gatekeeper with which the endpoint is registered.
GDS
The Global Directory Service for the endpoint. Usually the Polycom Global
Address Book.
Presence
Whether or not the endpoint is registered with a Presence service, so that its
availability can be reported.
Device Managed
Whether or not the endpoint is registered with a Provisioning service, so that
it can be configured automatically.
ISDN Line Status
The status of the ISDN line. Possible values include:
• Operational
• Non-operations
This field is blank for the following endpoint types: PVX, MGC, RMX,
GW/MCU, Other, and TANDBERG.
Alias Type
If the endpoint has an alias designation, the type of alias. Possible types
include E.164, H.323 ID, URL, Transport Address, email, Party Number, and
Unknown.
Alias Value
Value for the alias type shown.
 If you select Call Details, you’ll see these participant details:
Polycom, Inc.
157
Managing Conferences and Participants
Setting
Description
Video Protocol
The video connection protocol, both transmission (Tx) and reception (Rx),
the endpoint is using. Possible values include:
• H.261
H.261 is an ITU standard designed for two-way communication over
ISDN lines and supports data rates which are multiples of 64Kbit/s.
H.261 supports CIF and QCIF resolutions.
• H.263
H.263 is based on H.261 with enhancements that improve video
quality over modems. It supports CIF, QCIF, SQCIF, 4CIF and 16CIF
resolutions.
• H.264
Video Format
The video format, both transmission (Tx) and reception (Rx), the endpoint is
using.
Video Rate
The video bandwidth negotiated with the far site.
Video Rate Used
The actual video bandwidth used in the call to the far site.
Video Frame Rate
Specifies the frame rate to use.
Video FEC Errors
The number of Forward Error Correction (FEC) errors that have been
corrected in the current call.
Cause Code
The cause code showing how the call ended.
Audio Rate
The audio bandwidth negotiated with the far site
Audio Protocol
The audio connection protocol, both transmission (Tx) and reception (Rx),
the endpoint is using.
 If you select Call Quality of Service, you’ll see these standard service measurements: Total
Packet Loss, % Packet Loss, Audio Packet Loss, Video Packet Loss, Audio Jitter, and Video
Jitter.
Polycom, Inc.
158
Managing the Guest Book and Favorites
Lists
The RealPresence Resource Manager system provides two ways that you can customize and expand the
user directories. The system has a Guest Book and a Favorites List.
This section includes the following topics:
● Managing the Guest Book
● Managing Favorites
Managing the Guest Book
Users with the schedulers, operator, or administrator role have access to the Guest Book. The Guest Book
provides a way to store conference participants that aren’t managed by the RealPresence Resource
Manager system.
The Guest Book is a local system directory that includes guest participants who were either explicitly added
to the Guest Book or saved to the Guest Book while being added as conference participants.
Guest book entries are static and are not imported through the dynamically updated enterprise directory nor
included in the system Global Address Book. The Guest Book is limited to 500 entries.
Users with the schedulers, operator, or administrator role have access to the Guest Book. The Guest Book
provides a way to store conference participants that aren’t managed by the RealPresence Resource
Manager system.
This section includes these topics:
● View the Guest Book
● Add a Guest to the System Guest Book
● Edit a Guest in the System Guest Book
● Delete a Guest from the System Guest Book
View the Guest Book
By default, both system and area schedulers, operator, and administrators have access to the Guest Book.
When areas are enabled for your system, you can view only those guests who have been assigned to an
area that you manage. If you can manage more than one area, you can view users from all areas that you
manage.
To view the Guest Book:
1 Go to User > Guest Book.
2 Click
Polycom, Inc.
to filter the guest book by entering the first or the last name of the guest you want to find.
159
Managing the Guest Book and Favorites Lists
3 Click Search to get a filtered list. Or click Reset to clear your inputs.
The Guest Book pages includes a list of guest book entries that includes these fields.
Field
Description
Guest Name
The guest’s first and last name.
E-mail
The guest’s email address. The system validates the email structure only.
Location
The location of the guest’s endpoint system. This is a free-form entry field that the
system does not validate.
Number
(Optional) The ISDN phone number for the user. This number is constructed from
the Country code + Area/City code + phone number or entered as the modified dial
number.
Join Mode
Indicates whether the guest will use an audio endpoint or video endpoint to join
conferences.
Dial Options
Indicates whether the guest will dial into conferences or that the system should dial
out to the guest.
Dial Type
Indicates whether the guest has an H.323 (IP), SIP (IP), or H.320 (ISDN) endpoint.
Selected Area
This field is available when areas are enabled and the user can manage more than
one area.
Add a Guest to the System Guest Book
You can add a guest to the guest book.
You can add as many as 500 guests, but each guest must be unique. The RealPresence Resource
Manager validates each guest for a unique H.323 ID, E.164 number, IP address, and so on. The
RealPresence Resource Manager verifies that the guest does not already exist in the guest book or as a
user-associated endpoint.
To add a guest to the system Guest Book:
1 Go to User > Guest Book and click
.
2 Configure the Guest Information section of the Add New Guest dialog.
Field
Description
First Name
The guest’s first name.
Last Name
The guest’s last name.
Email
The guest’s email address. The system only validates the structure of the
email address.
Location
The location of the guest’s endpoint system. This is a free-form field that the
system does not validate.
Polycom, Inc.
160
Managing the Guest Book and Favorites Lists
Field
Description
Dial Type
Specify the protocol that the guest’s endpoint supports: H.323 (IP), SIP (IP),
or H.320 (ISDN).
This selection will determine what other sections of the Add New Guest
dialog you will need to complete.
Join Mode
Specify whether the guest’s endpoint is an audio or video endpoint.
Note
A guest may have multiple endpoints. Create a separate Guest Book entry
for each endpoint.
Dial Options
Specify whether the guest will dial into conferences, or require that the system
dial out to the guest.
Note
To support both options, create a separate Guest Book entry for each.
Assigned Area
This field is available when areas are enabled and the user can manage more
than one area.
3 If the guest has an H.323 (IP) endpoint, configure these settings:
Field
Description
Number and
Number Type
The specific dial string for the guest, and the format of the number that the
MCU must resolve to contact the guest. This may be an IP address, E.164
address, H.323, or Annex-O.
For Annex-O dialing, in the Number field enter the H.323.alias@IP, for
example:
• 1001@11.12.13.14
• 1001@domain.com
• username@domain.com
• username@11.12.13.14
Notes
• Polycom endpoints must register with a gatekeeper before they will attempt
an Annex-O call.
• You can enter a dial string for another MCU as a guest. If so, you may need
to specify the conference ID in the Extension field also.
Extension
Use this field to connect the conference to another conference on another
MCU. In this field, specify the conference ID or passcode for the conference
on the other MCU.
MCU Service
Choose from the list of MCU services defined on the MCUs with which the
RealPresence Resource Manager system is registered. Leave this at Any
Available Service unless you have specific knowledge of MCU services.
4 If the guest has a SIP (IP) endpoint, configure these settings:
Polycom, Inc.
161
Managing the Guest Book and Favorites Lists
Field
Description
Sip URI
The SPI URI the MCU must resolve to contact the guest.
MCU Service
Choose from the list of MCU services defined on the MCUs with which the
RealPresence Resource Manager system is registered. Leave this at Any
Available Service unless you have specific knowledge of MCU services.
5 If the guest has an H.320 (ISDN) endpoint, configure these settings:
Field
Description
Use Modified Dial Number
Select this option first (as needed) as it will determine the other fields you
must configure.
Country
(Not available when Use Modified Dial Number is selected.) The country to
which the system will dial out to the guest. Click Select to view a list of country
codes.
Area/City Code
(Not available when Use Modified Dial Number is selected.) The area code
to which the system will dial out to the guest.
Number
The participant’s phone number.
Extension
Cannot be configured.
MCU Service
Choose from the list of MCU services defined on the MCUs with which the
RealPresence Resource Manager system has registered. Leave this at Any
Available Service unless you have specific knowledge of MCU services.
6 Click OK.
Edit a Guest in the System Guest Book
You can edit information associated with a guest in the system guest book.
If you edit a guest that is already scheduled for a future conference or participating in an ongoing
conference, the changes you make will not be reflected in the conference.
To edit a guest in the system Guest Book:
1 Go to User > Guest Book and select the guest of interest.
2 Click
.
3 Change the Guest Information section and endpoint information sections of the Add New Guest
dialog, as needed. For more information about these fields, see Add a Guest to the System Guest
Book.
4 Click OK.
Delete a Guest from the System Guest Book
You can delete a guest from the Guest Book.
Polycom, Inc.
162
Managing the Guest Book and Favorites Lists
To delete a guest from the system Guest Book:
1 Go to User > Guest Book and select the guest of interest.
2 Click
. Click OK to confirm the deletion.
Managing Favorites
Users with the operator role or area operator role to create one or more Favorites list, which they can use
to quickly select participants to participate in conferences.
Users with the operator or area operator roles with Monitoring permissions can view, add, edit, delete, or
use Favorites lists and these Favorites lists cannot be shared with other operators.
This section includes the following tasks:
● Add a Favorites List
● Edit a Favorites List
● Delete a Favorites List
Add a Favorites List
You can create a new Favorites list.
To add a Favorites list:
1 Go to Conference > Favorites.
2 On the Favorites page, click
.
3 Enter a unique name for the Favorites List Name.
4 Enter a description.
f
5 Click
and enter all or part of the person’s last name or first name in the Search Available
Members field and click Search.
The system searches the Users list (local and domain) for users who are associated with endpoints
and who meet your search criteria. The results appear in the Search Results column.
•
•
Depending on the search domain, the search function may return different results. See Filter and
Search in a List.
The search results only include users associated with endpoints.
6 Select the user(s) of interest from the list and move them to the Favorite List Members column.
7 Repeat step 5 and 6 until you’ve added the users of interest to your Favorites list and then click OK.
The new list appears in the Favorites page.
Edit a Favorites List
You can edit a Favorites list. You can rename it or remove or add users to the list.
Polycom, Inc.
163
Managing the Guest Book and Favorites Lists
To edit a Favorites list:
1 Go to Conference> Favorites.
2 Select the Favorites list of interest and click
.
3 In the Edit Favorites List dialog, edit the Favorites List Name and Description fields as needed.
4 Remove or add users to the Favorite List Members column as needed and then click OK.
Delete a Favorites List
You can delete a Favorites list. When you delete a Favorites list, the users remain in the system but are not
associated with the deleted Favorites list.
To delete a Favorites list:
1 Go to Conference > Favorites.
2 Select the Favorites list of interest and click
.
3 Click OK to confirm the deletion.
The list is deleted from the system.
Polycom, Inc.
164
Conference and Participant Details
Reference
This section lists the conference and participant detail fields for reference. It includes the following topics:
● Conference Image
● Conference Details
● Conference Features
● Bridge (MCU) Features
● Participants
● Participant Details
Conference Image
The Conference Image section displays the selected participant’s video. Click Shuffle to shuffle to the next
participant’s video.
Conference Details
The Conference Details section has these fields.
Section
Description
Creator
Name of the person who created the conference.
Not applicable for ad hoc conferences.
Owner
Name of the owner of the conference, if an owner is selected.
Start Date/Time
For a scheduled conference, the start date and time of the conference and the time difference
between the local time and the standard time.
For an unscheduled conference, the date and time the conference started.
Duration
For a scheduled conference, how long the conference is scheduled to last.
For a completed conference, how long the conference actually lasted.
End Date/Time
The date and time the conference ended
Type
The type of conference. Possible values include:
• Audio
• Audio-Video
Polycom, Inc.
165
Conference and Participant Details Reference
Section
Description
Status
The state of the conference. Possible values include:
•
•
Alerts
Declined
•
•
Finished
Future
Recurring
Whether or not the conference was scheduled as a recurring conference.
Connection
Connection information about the conference. Possible values include:
• Multipoint
• Point To Point
• Gateway
• Embedded Multipoint
Bit Rate
The rate (in kbps) at which to transfer the conference audio or video data.
Conf Monitoring
ID
System-assigned ID used for troubleshooting.
Media Type
Describes the media type used for the conference.
Video Session
Type
Type of video session:
VSW (Video Switching)
CP (Continuous Presence)
SVC (Scalable Video Coding) only
CP and SVC
Video Layout
The video layout for the conference.
For more information about layouts, see your
MCU documentation.
Possible values are:
VIDEO_SWITCHING
CP_1X1
CP_1X2
CP_2X1
CP_2X2
CP_3X3
CP_1AND5
CP_1AND7
CP_1X2VER
CP_1X2HOR
CP_1AND2HOR
CP_1AND2VER
CP_1AND3HOR
CP_1AND3VER
CP_1AND4VER
CP_1AND4HOR
CP_1AND8CENTRAL
CP_1AND8UPPER
CP_1AND2HORUPPER
Polycom, Inc.
CP_1AND3HORUPPER
CP_1AND4HORUPPER
CP_1AND8LOWER
CP_4X4
CP_2AND8
CP_1AND12
CP_1X1QCIF
CP_1X2FLEX
CP_1AND2HORRFLEX
CP_1AND2HORLFLEX
CP_1AND2HORUPPERRFLEX
CP_1AND2HORUPPERLFLEX
CP_2X2UPPERRFLEX
CP_2X2UPPERLFLEX
CP_2X2DOWNRFLEX
CP_2X2DOWNLFLEX
CP_2X2RFLEX
CP_2X2LFLEX
CP_UNKNOWN
166
Conference and Participant Details Reference
Section
Description
Video Format
For a conference hosted on an MCU, the video format of the conference data stream. Possible
values include:
•
•
•
•
•
Video Protocol
•
•
•
•
VGA
SVGA
XGA
NTSC
For a conference hosted on an MCU, the video protocol of the conference data stream.
Possible values include:
•
•
Audio Algorithm
Automatic
CIF
QCIF
4CIF
16CIF
Auto
H.261
•
•
H.263
H.264
For a conference hosted on an MCU, the audio compression ratio of the conference data
stream. Possible values are:
•
•
AUTO
G.711
•
•
G.722
Siren 7 (16 kbps)
Conference Area
Area or areas assigned to the selected conference owner.
Participant Areas
List of areas to which participants belong.
Conference Features
The Conference Features section has these fields.
Section
Description
Conference Passcode
The conference passcode, which is assigned either by the system or the scheduler.
Chairperson Option
Indicates whether or not the conference requires a chairperson.
Note
The RealPresence Collaboration Server (RMX) 1000 system does not support the
Chairperson feature.
Chairperson Passcode
The passcode the chairperson must enter to take control of the conference. Not
applicable when no chairperson is designated.
Chairperson
The name of the chairperson. Not applicable when no chairperson is designated.
Dial-in #
The number that can be used by participant not explicitly invited to the scheduled
conference.
Polycom, Inc.
167
Conference and Participant Details Reference
Section
Description
Lecture Mode
The type of Lecture Mode, if any, that was selected when the conference was
created. Possible values are None, Lecture, and Presentation.
Note
The RealPresence Collaboration Server (RMX) 1000 system does not support
Lecture Mode.
Lecturer
The name of the lecturer. Not applicable when Lecture Mode is None.
Lecture View Switching
Indicates whether or not automatic switching between participants is enabled.
Dual Stream Mode
Possible values are:
• None
• People+Content
• Visual Concert PC
• Visual Concert FX
T120 Rate
Possible values are:
• None
• HMLP - Var
• HMLP - 384
• HMLP - 320
• HMLP - 256
• HMLP - 192
• HMLP - 128
• HMLP - 6.4
• HMLP - 62.4
• HMLP - 14.4
• MLP - Var
• MLP - 64.4
•
•
Duo Video
Unknown
•
•
•
•
•
•
•
•
•
•
•
•
MLP - 62.4
MLP - 46.4
MLP - 40
MLP - 38.4
MLP - 32
MLP - 30.4
MLP - 24
MLP - 22.4
MLP - 16
MLP - 14.4
MLP - 6.4
MLP - 4
End Time Alert
Whether or not the system alerts participants to the end of the conference by playing
an end tone.
Entry Tone
Whether or not an entry tone is played to all connected participants when a
participant joins the conference.
Exit Tone
Whether or not an exit tone is played to all connected participants when a participant
disconnects from the conference.
Bridge (MCU) Features
The Bridge (MCU) Features section, which applies only for conferences that use an MCU, has these fields.
Polycom, Inc.
168
Conference and Participant Details Reference
Section
Description
MCU Name
If the conference is hosted on an MCU, shows the MCU device name hosting the
conference.
Not applicable when the conference is not being hosted on an MCU.
Numeric ID
The unique conference identifier assigned by the MCU.
Entry Queue Access
Whether or not the conference has an entry queue enabled.
Note
The RealPresence Resource Manager system enables entry queues on a per MGC
basis and all conferences on an entry queue enabled MGC will be scheduled with
entry queue access.
Meet Me per Conf
Whether or not the a conference is a Meet Me conference, for which a dial-in
number is assigned, so that undefined participants can connect to the conference.
Conference on Port
(MGC only) Indicates whether or not the MGC is set to Conference on Port, which
conserves bandwidth and ports. In this case, all participants are on a single video
port and use the same connection speed and video format.
Message Service Type
Displays the type of messages participants joining the conference hear. Possible
values are:
• None
• Welcome (No wait)
• Attended (Wait)
• IVR
Message Service Name
Name on the MCU of the Message Service. So, for example, a service name IVR70
which provides the IVR service.
Participants
When you view a particular conference, the list of participants identifies users, rooms, and guests invited to
participate. When viewing a conference, the list of participants identifies participants on a call.
Section
Description
Name
The participant’s name.
Call Info
How the participant joined the call. Possible values include:
• Video Dial-Out@<Address>
• Audio Dial-In
• Video Dial-In
• In Person
• Room Only
Participant Details
The Participant Details section has these fields.
Polycom, Inc.
169
Conference and Participant Details Reference
Section
Description
Name
The participant’s name.
Type
The type of conference connection. Possible values include:
• Audio Only
• Audio-Video
• Other (for In Person and Room Only participants)
Endpoint Name
The name assigned to the participant’s endpoint when added to the system.
Connection Status
The state of the participant’s endpoint connection. Possible values include:
• Connected
• Connecting
• Declined
• Disconnected
• Disconnecting
• Error
• Unknown
Interface Type
Possible values are:
• H323
• ISDN
• SIP
• H323_E164
• H323_ANNEX_O
• H323_ID
Address
Used to reach endpoints, such as IP address or E164 number.
Number
The IP address or phone number of the participant’s endpoint (if a dial-out) or the
participant’s port address on the MCU (if a dial-in).
Bit Rate
The audio or video data transfer rate (in kbps) of the participant’s endpoint.
Encryption
Encryption is either enabled (True) or disabled (False).
Area
Area or areas assigned to the participant.
Polycom, Inc.
170
Endpoint Management
This section provides an introduction to the RealPresence Resource Manager system endpoint
management functionality and operations. It includes:
● Managing Endpoints and Peripherals
● Supported Endpoints and Peripherals
● Polycom Software Endpoints
Polycom, Inc.
171
Managing Endpoints and Peripherals
This section provides an overview of the Polycom® RealPresence® Resource Manager system’s endpoint
operations. It includes these topics:
● Endpoint Management
● Managing Endpoints
● Working with Endpoint Groups
● Monitoring and Managing Peripherals
● Download an Endpoint Inventory Report
Endpoint Management
Endpoint management eliminates the need to configure each endpoint individually through the hand-held
remote or the endpoint’s web interface. It also helps you easily enforce network, group, and system policies
for each device.
Endpoint management consists of two aspects of remotely configuring endpoints: updating software and
provisioning settings.
The RealPresence Resource Manager system enables you to manage endpoints in following ways:
● Scheduled Management of Video Endpoints (Polycom and Third-Party)
● Dynamic Management of Video Endpoints (Polycom Only)
● Dynamic Management of Phones
● Management of H.323 Endpoints Synchronized from a RealPresence DMA System
● Calendar Connector
Scheduled Management of Video Endpoints (Polycom
and Third-Party)
Scheduled management enables you to push software updates and provisioning profiles to endpoints at
intervals that you define.
Scheduled management uses server-to-client communication over HTTP. This management technique is
more appropriate for corporate networks where both the RealPresence Resource Manager and all
endpoints are behind the same firewall.
Polycom, Inc.
172
Managing Endpoints and Peripherals
Password Requirements for Scheduled Management
A RealPresence Resource Manager system can manage Polycom endpoints only when the password in
the device record matches the password in the endpoint. Matching passwords are required to:
● Schedule provisioning of an endpoint through a RealPresence Resource Manager system.
● Use the Scheduled Software Update feature.
● Monitor the endpoint from the Endpoint > Monitor View.
You can update the password for certain endpoint systems through scheduled provisioning only after you
have entered the matching password in the RealPresence Resource Manager system. In this case, you
must instruct end-users not to change the password.
Some companies select an administrative password that is used for all endpoints and regularly
updated through provisioning.
For third-party endpoints, passwords may be required to access the endpoint management software.
For information about restrictions in changing passwords for a specific endpoint, see the documentation for
the endpoint.
Dynamic Management of Video Endpoints (Polycom
Only)
Dynamic management enables the endpoint to poll the RealPresence Resource Manager automatically to
get provisioning updates (configuration settings) and software updates based on policies you define.
The administrator can use a rule-based system to apply dynamic provisioning profiles. An administrator can
create multiple rules and associate a profile with more than one rule at a time. A provisioning rule consists
of one or more conditions that must be met before the dynamic provisioning profile can be applied.
Dynamic management is client-to-server over HTTPS which makes it more secure and firewall-friendly.
Dynamic management is available:
● Only for Polycom endpoints.
● When Polycom endpoints are able to automatically discover the RealPresence Resource Manager.
This means you must add the DNS service record (SRV record) for the RealPresence Resource
Manager system.
In dynamic management mode, when an endpoint starts up and at designated intervals thereafter, it
automatically polls the RealPresence Resource Manager system for a newer software update package or
provisioning profile. If either is found, the package is sent in XML format over a secure HTTPS connection.
Endpoints do not poll the system if they are in a call. They restart polling after the call ends.
Presence Service for Dynamically-Managed Endpoints
The RealPresence Resource Manager system also provides a presence service to dynamically-managed
endpoints. The presence service maintains online status information for the users of dynamically-managed
endpoints. The presence service enables users to access information about the online status of other users.
Polycom, Inc.
173
Managing Endpoints and Peripherals
This is important, because when you make a video call or start a chat, that action only takes you to an
endpoint. It doesn’t ensure that you will reach the person you want to reach. The presence service provides
information about the user’s availability, which improves your chances of reaching the user.
The RealPresence Resource Manager supports presence services for all dynamically-managed
Polycom endpoints with the exception of RealPresence Mobile. RealPresence Desktop clients
managed by the RealPresence Resource Manager can receive offline messages.
For more information about dynamic management methods, see Understanding Dynamic Endpoint
Management.
Dynamic Management of Phones
The RealPresence Resource Manager system can be used as a central provisioning server for supported
conference phones when your deployment uses a Cisco Unified Communication Manager as the voice call
manager.
This allows you to use phone provisioning profiles to apply a single set of parameters and settings to all of
the phones in your deployment. The use of phone provisioning profiles can reduce the time it takes to deploy
new phones and configuration changes to existing phones.
You can also automatically send software updates.
For complete information about managing audio endpoints, see Managing Audio Phones.
Management of H.323 Endpoints Synchronized from a
RealPresence DMA System
H.323 endpoints that register with the RealPresence DMA system’s gatekeeper automatically display in a
RealPresence Resource Manager system that has been configured with a RealPresence DMA system. This
allows you to track the endpoints registered to the RealPresence DMA system. Once they are synchronized
to the RealPresence Resource Manager, you can associate users with them if you want to manage the
H.323 endpoints (provision or update) or schedule them into conferences.
Each synchronized DMA-registered endpoint consumes a device license in the RealPresence Resource
Manager system.
For complete information about how to manage H.323 endpoints that are synchronized from a
RealPresence DMA system, see Working with Endpoints Synchronized from a RealPresence DMA System.
Calendar Connector
The following Polycom endpoints can display a meeting calendar when associated with a Microsoft
Exchange user: RealPresence Group Series systems, Polycom HDX systems, RealPresence Desktop
video collaboration softwares, and RealPresence Mobile applications.
This means that in general, users of these systems can join meetings by clicking in the calendar display
instead of manually dialing into the conference.
Polycom, Inc.
174
Managing Endpoints and Peripherals
For an endpoint user to be able to use the feature, you must configure the RealPresence Resource Manager
system to be a connector for the Microsoft Exchange Server. When you do this, the Calendar Connector
service ensures that the right meeting information is routed to the endpoint’s calendar.
The Calendar Connector interprets the meeting invitations sent to the user via Microsoft Exchange and
ensures that the endpoint can correctly dial a meeting directly from its calendar interface. It modifies the dial
string within the invitation to ensure it is valid.
As an administrator, you must do the following:
● Configure the RealPresence Resource Manager to be a Calendar Connector
This enables the RealPresence Resource Manager to act as a proxy service for your Exchange
Server.
● Set up connector rules that scan emails for call information to insert into a user-associated Polycom
endpoint’s calendar.
● Provision the user-associated endpoint to use the RealPresence Resource Manager system as its
Exchange Server IP address.
OR
● Manually configure the endpoint to use the RealPresence Resource Manager system’s IP address
for its Microsoft Exchange server.
Configure the Calendar Connector
If you manage a supported Polycom endpoint (RealPresence Group Series, HDX, RealPresence Desktop
or RealPresence Mobile), you can use the Calendar Connector feature to ensure that those endpoint users
can click to join meetings directly from the endpoint’s calendar interface.
The Calendar Connector allows you to use the RealPresence Resource Manager system as a connector
for your Microsoft Exchange Server. It interprets the meeting invitations sent to the user’s endpoint via
Microsoft Exchange and ensures that the endpoint can correctly dial a meeting directly from its calendar
interface. It modifies the dial string within the invitation to ensure it is valid.
You must have Admin permissions to configure the Calendar Connector.
To configure the Calendar Connector:
1 Go to Endpoint > Calendar Connector.
2 Click
.
3 In the Add a Connector dialog, select the General section to enter a server type and server
information.
Field
Usage
Type
Only Exchange is supported for this release.
Yahoo, Google, Office365, and Office365(China) are not officially supported in
this release.
Server
Enter the server details for the calendar server type you selected:
Options
Configure the max concurrent sessions allowed.
Polycom, Inc.
175
Managing Endpoints and Peripherals
4 You need to add at least one Connector Rule before you click OK. For more information about
Connector Rule, see Add a Connector Rule.
Add a Connector Rule
You can create rules to help the connector find dial string information the meeting invitation to ensure it is
in the user’s calendar.
Connector rules are regular expressions that interpret meeting invite fields to retrieve VMR information for
the calendar. For connector rules to work effectively, your users must schedule meetings with consistent
conference room identifiers that can be read by the rules you create.
For example, when scheduling a meeting with Microsoft Outlook, a user can specify the meeting location
as below:
Location: Conference Room Marconi; VMR: 734567
or
Location: Conference Room Marconi; Bridge: 734567
In this case, the following match string would extract the VMR number 735467 from the meeting invite
contents:
?:^|Bridge\:|VMR\:|vmr\:)\s*(\d+)$
To create a connector rule:
1 Go to Endpoints > Calendar Connector.
2 Select a connector to edit and click
.
3 In the Edit a Connector dialog, select Rules to view the rule information.
4 Click
.
5 In the Add a Rule dialog, enter the rule parameters you want to use.
Parameter
Usage
Match For
Choose either Lync Meeting Invitation or Standard Meeting Invitation.
Invitation Field
Choose the meeting invitation field where you expect the VMR information to be.
If you selected Lync Meeting Invitation, this field is grayed out.
Match String of Domain (Lync
Invitation only)
Enter the Lync or Skype for Business domain name. For example,
pctc-rprmqa\.com
Match String of VMR Number
(Standard Meeting Invitation
only)
Enter a regular expression to use to detect the VMR number.
Prefix
Enter a prefix to append to the beginning of the VMR number.
Suffix
Enter a suffix to append to the end of the VMR number.
Routing Method
Use the default setting (tel).
6 Click OK.
Polycom, Inc.
176
Managing Endpoints and Peripherals
Add a Filter for Unaccepted Meetings
You can add a filter to the endpoint calendar so that meetings that are not accepted are not displayed.
To add a filter:
1 Go to Endpoint > Calendar Connector.
2 Select a connector to edit and click
.
3 In the Edit a Connector dialog, select Filters to view the filter information.
4 Enter (Busy) in the Match field. This will create a filter that displays only meetings that are accepted
(or busy).
5 Click Save.
Dynamically Provision Calendar Connector Information
If you have configured a Calendar Connector, you can dynamically provision Group and HDX systems with
this information by dynamically provisioning the endpoints with the RealPresence Resource Manager
FQDN instead of the Exchange Server address in a Network Config profile.
The Calendar Connector feature is only for supported Polycom endpoints: RealPresence Group, HDX
systems, RealPresence Desktop, and RealPresence Mobile systems.
Managing Endpoints
The follow topics describe the available actions for managing endpoints:
● View the Endpoint List
● Customize the Endpoint List
● View Endpoint Details
● Add an Endpoint
● Edit an Endpoint
● Delete an Endpoint
● Change an Endpoint Group Association
● Manage an Endpoint Owner
● Manage an Endpoint
● View an Endpoint’s Video Feed
● Clear an Endpoint Help Request
● Send a Message to an Endpoint
● Reboot an Endpoint
● Associate a User with an Endpoint
● Search for Endpoints in a Range of IP Addresses
Polycom, Inc.
177
Managing Endpoints and Peripherals
View the Endpoint List
You can view all the provisioned endpoints listed in the Monitor View screen.
To view endpoints:
» Navigate to Endpoint > Monitor View.
The following information is displayed:
Field
Description
Status
The state of the endpoint. Possible values include:
• Online
• Offline
• Licensed
• In a call
• Gatekeeper/SIP registered
• Signaling unregistered
• (Audio Phone Only) Registration Status Unknown
• Endpoints behind firewall
• Error
• Warning
• All paired peripherals are connected without alerts
• One or more paired peripherals are turned off or no longer connected
• One or more paired peripherals has an error
Mode
The management mode for the endpoint. Possible values include:
• Non-dynamically Managed Endpoints
• Dynamically Managed endpoints
• Synced RealPresence DMA Endpoints
• Synced CUCM Phones
• Auto-added Phones
• Manually Added Phones
Name
The assigned name of the endpoint.
Model
The type of endpoint. For valid endpoint types, see Supported Endpoints and Peripherals.
IP Address
The IP address assigned to the endpoint.
Area
(Available only when Areas are enabled.) The area with which the endpoint is associated.
Users can only view area information for the areas to which they belong or have been
assigned to manage.
Dial String
The dial string for the endpoint. If the endpoint has more than one dial string, it displays one
based on this order:
• SIP
• H.323
• ISDN
Polycom, Inc.
178
Managing Endpoints and Peripherals
Field
Description
Owner
The user associated with the endpoint.
Endpoint Groups
The endpoint group to which the endpoint belongs.
Customize the Endpoint List
You can filter the endpoint list and customize the columns that appear on the screen.
To customize the endpoint list:
1 Navigate to Endpoint > Monitor View.
2 Click
to filter the following list of endpoints:
Field
Description
Type
Filters the list by type.
Model
Filters the list by model name entered.
Mode
Filters the list by one of the following management modes:
• Dynamically Managed Endpoints
• Non-dynamically Managed Endpoints
• Synced RealPresence DMA Endpoints
• Synced CUCM Phones
• Manually Added Phones
• Auto-added Phones
Endpoint Group
Filters the list by endpoint group name.
Alerts
Filters the list by alert type: Help, Error, or Warning.
Connection Status
Filters the list by connection status: In a Call, Online, or Offline.
Name
Filters the list by system name entered.
IP Address
Filters the list by IP address entered.
Dial String
The IP address of the gatekeeper to which the device is registered.
Site
Filters the list by site location entered.
Area not the same
as Site’s Area
Available only when Areas are enabled. This filters endpoints that belong to a site which is
not associated with the area the endpoint belongs to. If the user does not manage the site’s
area, he cannot view the Site area information. The value for the area will display as
“Restricted”.
Area
Available only when Areas are enabled. Filters the list by the area with which the endpoint is
associated. This field is only visible when Areas are enabled. You can only view
area-specific information for area(s) that you have permission to manage.
MAC Address
Filters the list by MAC address entered.
Serial Number
Filters the list by serial number entered.
Polycom, Inc.
179
Managing Endpoints and Peripherals
Field
Description
VIP
Filters the list for VIP endpoints.
Ignore reclaimed
endpoint
Filters the list by endpoints with reclaimed certificates. When checked, endpoints with
reclaimed certificates will not be displayed.
3 Click
to customize the columns that appear on the screen.
4 To hide a column, cancel the check box next to the column that you wish to hide.
5 To display a column, mark the check box next to the column that you want displayed.\
View Endpoint Details
You can view more details about an endpoint listed in the Monitor View screen.
To view detailed information about a managed endpoint:
1 Go to Endpoint > Monitor View.
2 As needed, Click
to customize the endpoint list.
3 Select the endpoint of interest and click
.
Depending on the selected endpoint type, you may see different information.
Device Status, Device Alerts, Software Update Details, Provisioning Details, and Beacon ID are
only available for video endpoints.
Endpoint Files and Configuration Profile Association are only available for audio phones.
Field
Description
Device Summary
Name
The name of the endpoint.
• Endpoint names must be unique.
• The name must be in ASCII only and may have an unlimited number of
characters. Spaces, dashes, and underscores are valid.
• The system name might be different than the H.323 ID.
Type
The type of endpoint. For valid types, see Supported Endpoints and Peripherals.
ID
The system-generated ID for the device.
Owner
The person to whom the endpoint is assigned.
IP Address
The assigned IP address of the endpoint.
VLAN ID
(Audio Phone Only) Virtual Bridged LAN ID
Polycom, Inc.
180
Managing Endpoints and Peripherals
Field
Description
Site
The network site for the endpoint. By default, endpoints are added to the Primary
Site.
Note
When areas are enabled on your system, this field shows a value of Restricted if
you do not have permission to manage the area to which the site is assigned.
Software Version
The version of the software installed on the endpoint (ASCII only). The endpoint
provides the version number if it registered successfully or is managed.
Serial Number
The serial number (ASCII only) of the endpoint.The endpoint provides the serial
number if it registered successfully or is managed.
MAC Address
(Audio Phone Only) The MAC address of the endpoint.
SIP URI
A SIP URI is the address used to call another person via SIP. In effect it’s a user’s
SIP phone number. The SIP URI will be of the following format:
<username>@host(domain or IP):Port
Area
The area to which the endpoint is assigned.
This field is only visible when Areas are enabled.
A user can only view area-specific information for an area(s) that he has permission
to manage.
ISDN Video Number
(Video Endpoint Only) For ISDN endpoints only, the country code + city/area code +
phone number for the endpoint.
When you add an endpoint without native ISDN, the ISDN gateway, country code,
and area code are not captured. Only native ISDN is supported.
Available to Schedule
(Video Endpoint Only) It shows if this endpoint is available for conference
scheduling.
Monitoring Level
(Video Endpoint Only) The monitoring level for the device. Possible values include:
• Standard. This device is monitored.
• VIP. This device is monitored closely. The VIP identifier and filters are available
to operators to monitor and manage conferences.
Supported Protocols
(Video Endpoint Only) The communications protocols that the endpoint can
support. Possible values include:
• IP (H.323) - A standard that defines the protocols used for multimedia
communications on packet-based H.323 networks.
• IP (SIP) - A standard that defines the protocols used for multimedia
communications on SIP networks.
• ISDN (H.320) - A standard that defines the protocols used for multimedia
communications on switched networks, such as ISDN.
For endpoints with the type Unknown, select H.323.
The endpoint automatically provides the protocols if it registered successfully or is
managed.
Polycom, Inc.
181
Managing Endpoints and Peripherals
Field
Description
Capabilities Enabled
(Video Endpoint Only) Capabilities enabled on this endpoint. Options are:
• MCU - The endpoint can act as a control unit for multipoint conferences.
• Gateway - The endpoint can act as a gateway for call management.
The MCU provides the capability if it registered successfully or is managed.
Aliases
(Video Endpoint Only) The aliases that allow you to connect to the endpoint. The
RealPresence Resource Manager system converts the aliases to the IP address
associated with the endpoint.
• Alias Type. Possible types include E.164, H.323 ID, URL, Transport Address,
email, Party Number, and Unknown.
• Alias Value. Value for the alias type shown.
• The endpoint name is the system name, which might be different from the H323
ID.
• The value of the E.164 alias is the extension dialed to reach this endpoint.
Note
• The following Alias Values are ASCII only: H323 ID, URL, Transport Address,
and Unknown.
User
(Audio Phone Only) The user ID mapped to the phone's SIP URI.
Uptime
(Audio Phone Only) The time of the endpoint has been working and available.
Last Restart Time
(Audio Phone Only) Endpoint’s last reboot or restart time.
Last Touch Time
(Audio Phone Only) The last time that the endpoint connects to the RealPresence
Resource Manager system.
Last Provisioning Time
(Audio Phone Only) The last time that the RealPresence Resource Manager
system sends provisioning configurations to the endpoint.
Device Status (Video Endpoint Only)
Gatekeeper Registration
The status of the device’s registration with the gatekeeper service. Possible values
include:
• Registered
• Unregistered
Directory Registration
The status of the device’s registration with the Global Directory Service. Possible
values include:
• Registered
• Unregistered
Presence Registration
The status of the device’s registration with the presence service. Possible values
include:
• Registered
• Unregistered
Exchange Registration
The status of the device’s registration with the Microsoft Exchange service.
SIP Registration
The status of the device’s registration with the SIP service.
Polycom, Inc.
182
Managing Endpoints and Peripherals
Field
Description
Device Managed
Indicates whether or not the RealPresence Resource Manager system is
dynamically managing the device.
Gatekeeper Address
The IP address of the gatekeeper to which the device is registered.
SIP Server Address
The IP address of the SIP server.
Device Local Time
The local time as set within the device in a default format of hh:mm:ss AM | PM.
This field is blank for the following device types: RMX, GW/MCU, Other, and
TANDBERG.
ISDN Line Status
The status of the ISDN line. Possible values include:
• Operational
• Non-operations
This field is blank for the following device types: RMX, GW/MCU, Other, and
TANDBERG.
ISDN Assignment Type
How the ISDN type was assigned to the device. Possible values include:
• Administrator, when the ISDN type was assigned manually by an administrator
• Endpoint, when the ISDN type was natively assigned in the endpoint
• Auto-Assigned, when the ISDN type was automatically assigned by the
RealPresence Resource Manager system based on the site configuration
• From Network, when the ISDN type was derived from the gateway and
extension
• Undefined, when the RealPresence Resource Manager system cannot identify
the source for the ISDN type assignment
This field is blank for the following device types: RMX, GW/MCU, Other, and
TANDBERG.
Device ISDN Type
The ISDN network interface type installed in the device. Possible values include:
• ISDN_QUAD_BRI
• ISDN_PRI_T1
• ISDN_BRI
• ISDN_UNKNOWN
This field is blank for the following device types: RMX, GW/MCU, Other, and
TANDBERG.
Call Info
Call Type
(Video Endpoint Only) Type of call, such as H.323, SIP, ISDN, or POTS.
Video Protocol
(Video Endpoint Only) The video connection protocol, both transmission (Tx) and
reception (Rx), the endpoint is using. Possible values include:
• H.261
H.261 is an ITU standard designed for two-way communication over ISDN
lines and supports data rates which are multiples of 64Kbit/s. H.261
supports CIF and QCIF resolutions.
• H.263
H.263 is based on H.261 with enhancements that improve video quality over
modems. It supports CIF, QCIF, SQCIF, 4CIF and 16CIF resolutions.
• H.264
Polycom, Inc.
183
Managing Endpoints and Peripherals
Field
Description
Video Format
(Video Endpoint Only) The video format, both transmission (Tx) and reception (Rx),
the endpoint is using.
Audio Protocol
(Video Endpoint Only) The audio connection protocol, both transmission (Tx) and
reception (Rx), the endpoint is using. Possible values include:
• G.711
• G.722
• G.728
Far Site Name
The H.323 ID of the far site endpoint to which the selected endpoint is connected.
When multiple endpoints are connected through the endpoint's embedded MCU,
this field displays a concatenation of each endpoint's H.323ID separated by ' | ', for
example 'ISDN-CO1-7-1 | Vsfx-9-1'.
Far Site Number
The address of the far site endpoint to which the selected endpoint is connected.
The address value for the calling endpoint appears to be the dialed address. The
address value for the called endpoint appears to be the IP Address.
Cause Code
(Video Endpoint Only) The cause code showing how the call ended.
Encryption
(Video Endpoint Only) The type of encryption the far site uses.
Precedence Level
(Video Endpoint Only) Applicable only on AS-SIP calls. AS-SIP servers support a
“precedence level” that defines a call’s priority in terms of the order in which it is
given access to network resources.
Device Alerts (Video Endpoint Only)
Errors
Endpoint error message, for example, GK Registration error.
Warnings
Endpoint warning message, for example, Low Battery.
Provisioning Details (Video Endpoint Only)
Last Provisioning Type
The last provisioning type that was used for this endpoint.
Last Provisioning Rule
Applied
The name of the last provisioning rule that was applied to this endpoint.
Last Profile Applied
The name of the last provisioning profile that was or was not successfully applied to
the device. The Provisioning Status will be either Success or Failed.
Last Bundled Profile Applied
The name of the last bundled profile that was applied to this endpoint.
Provisioning Status
The device’s current provisioning status. Possible values include:
• Clear. No provisioning has been done.
• Pending. Provisioning is scheduled for this device.
• In Progress. The device is currently being provisioned.
• Success. Provisioning has been completed successfully on this device.
• Failed. Provisioning was not completed on this device.
Some endpoint systems expect all configuration fields to be provisioned. If any of
the fields are not provisioned, the status will indicate failed. However, the endpoint
will often function successfully.
Polycom, Inc.
184
Managing Endpoints and Peripherals
Field
Description
Pending Profile
The name of the provisioning profile that is scheduled to be applied to the device. In
this case, the Provisioning Status will be either Pending or In Progress.
This field is blank if the device is not scheduled for provisioning.
Scheduled
The date and time, in the default format of yyyy-mm-dd hh:mm, when the device
is schedule to be provisioned.
This field is blank if the device is not scheduled for provisioning.
Last Attempt Date/Time
The date and time, in the default format of yyyy-mm-dd hh:mm:ss, of the last
provisioning message exchanged with the device.
Failure Reason
A text description of the reason the provisioning failed. Causes for failure include:
• The provisioning profile does not exist
• The provisioning profile does not include provisioning information
• The RealPresence Resource Manager system no longer manages the device
• A password for the device is set in the video endpoint system, and you must
enter it in the RealPresence Resource Manager system
• The device is busy
• A network error occurred
• An incomplete transfer of provisioning information occurred
• Provisioning has timed out
• An internal error occurred on the device, and you must reboot it
• An unknown error occurred. Reboot the device.
Log Message
A read-only text box that contains messages related to the device provisioning
status
Software Update Details (Video Endpoint Only)
Software Update Status
The device’s software update status. Possible values include:
• Clear. A software update has not been done.
• Pending. A software update has been scheduled and is pending. The device may
be offline or in a call.
• In Progress. The software update is in progress.
• Success. A software update has completed successfully.
• Failed. A software update could not be performed.
Scheduled
The date and time, in the default format of yyyy-mm-dd hh:mm, when the device
software is scheduled to be updated.
This field is blank if the device is not scheduled for provisioning.
Last Attempt Date/Time
The date and time, in the default format of yyyy-mm-dd hh:mm:ss, of the last
software update message exchanged with the device.
Polycom, Inc.
185
Managing Endpoints and Peripherals
Field
Description
Failure Reason
A text description of the reason the software update failed. Causes for failure may
include:
• The software update file location does not exist.
• A password for the device is set in the video endpoint system, and you must
enter it in RealPresence Resource Manager.
• A network error has occurred.
• The update has timed out.
• An internal error occurred on the device, and you must reboot it.
• A profile has not been configured.
• An endpoint is offline.
• An incorrect activation key is in the key file.
• An unknown error has occurred. Reboot the device
Log Message
A read-only text box that contains the log message text recorded during the
execution of the software update.
Note that there are no log messages displayed for dynamically-managed endpoints.
Endpoint Files (Audio Phone Only)
Provisioning Profiles
This file contains all the attributes applied to the selected phone.
Phone Files
This file contains the configuration data that set from the selected phone.
Web Files
This file contains the configuration date that set from the selected phone’s web GUI.
APP Logs
This file contains the APP information received by the selected phone.
Boot Logs
This file contains the phone’s boot information.
Crash Dump
This file contains the logs for crash dump.
Others
Other files such as a file containing phone’s address book.
Endpoint Group
Association
This table lists the endpoint groups associated with the selected endpoint
Configuration Profile
Association
(Audio Phone Only) This table lists the configuration profiles associated with the
selected endpoint.
Beacon ID (Video Endpoint Only)
Proximity
This is the UUID the same for each endpoint and needs to be the same for each
beacon within your deployment.
Major
This ID is automatically generated and is unique to the endpoint. Enter this
number as the major ID for the respective beacon associated with the room
where the endpoint resides.
Minor
This ID is automatically generated and is unique to the endpoint. Enter this
number as the minor ID for the respective beacon associated with the room
where the endpoint resides.
Polycom, Inc.
186
Managing Endpoints and Peripherals
Download Endpoint Files
You can download the endpoint files to your local machine. LOG files are cumulative, and content is
appended with time stamps. The system creates a ZIP file if the log file is over 1024 KB by default. See
Configure Your Phone Management Settings on how to set the size.
XML and CFG files are not cumulative. New files will replace old files.
You can download the endpoint files only from the RealPresence Resource Manager GUI. Polycom
does not support downloading files in other ways.
To download endpoint files:
1 Go to Endpoint > Monitor View.
2 If needed, Click
to customize the endpoint list.
3 Select the audio phone and click
.
4 Go to the Endpoint Files panel.
Endpoint Files only show for audio phones.
5 Click
to download the ZIP file to your local PC.
Add an Endpoint
You can manually add video endpoints or audio phones. The configurations are different.
Add a Video Endpoint or Find an Endpoint on the Network
This topic describes how to manually add video endpoints and how to find endpoints on the same network
as the system.
For details about how to add audio phones, see Managing Audio Phones.
This action is not supported for RealPresence Mobile, RealPresence Desktop, RealPresence Group
systems, and RealPresence Immersive Studio systems.
For most endpoints, you enter basic information. The system then locates the endpoint and retrieves its
information.
When a SIP-only endpoint registers with the Polycom DMA system and does not register with the
RealPresence Resource Manager system’s provisioning service to become dynamically managed,
you must manually add it to the RealPresence Resource Manager system in order to manage that
endpoint.
To add an endpoint to the system or find an endpoint on the network:
1 Go to Endpoint > Monitor View and click
.
2 In the Add New Endpoint dialog, select a video endpoint as the Endpoint Type. For valid types,
see Supported Endpoints and Peripherals. For endpoints not specified in the list, select Other.
3 Enter the IP Address of the endpoint.
Polycom, Inc.
187
Managing Endpoints and Peripherals
4 Click Find Endpoint.
 If the RealPresence Resource Manager system can find the endpoint on the network, the Add
New Endpoint dialog is populated with information retrieved from the endpoint. Review any
information retrieved from the endpoint.
 If the RealPresence Resource Manager system cannot find the endpoint on the network, an error
message of Endpoint Not Found appears.
If you enter an invalid Admin ID or Password for an endpoint that requires that information, the
RealPresence Resource Manager system may still find the endpoint. It depends upon the endpoint
type.
• Polycom HDX systems doesn’t allow the RealPresence Resource Manager system to detect the
endpoint type and complete the registration. You can manually add the endpoint, but the
RealPresence Resource Manager system cannot communicate with it until you enter a valid Admin
ID or Password for the endpoint. In this case, the RealPresence Resource Manager system
records an error message in an error log.
• The Find Endpoint function only works for endpoints with a specified Endpoint Type. If you
selected a Endpoint Type of Other, the RealPresence Resource Manager system reports an error.
5 Assign the endpoint a System Name.
Endpoint names must be unique, must be in ASCII only, and may have an unlimited number of
characters. Spaces, dashes, and underscores are valid.
6 If necessary, enter the Admin ID and Password for the endpoint. Some endpoints may not require
this information. Other endpoints may require only a password.
7 Complete the Identification, Addresses, and Capabilities sections of the Add New Endpoint
dialog.
Pay particular attention to the Capabilities options, because these settings determine how the
endpoint is used throughout the RealPresence Resource Manager system. For example, you can
select it as a VIP endpoint and determine whether it will be Available to Schedule through the
scheduling interface.
Note that many fields in this dialog are ASCII only. Depending on the selected type, some of these
fields may not be displayed or may not be editable.
Field
Description
Identification
Description
A free-form text field (extended ASCII only) in which information about the endpoint
can be added.
GAB Display Name
Enter a name for the endpoint as it will appear in the Global Address Book.
Site
The network site for the endpoint.The system determines the site based upon IP
address.
Note
When areas are enabled on your system, this field shows a value of Restricted if
you do not have permission to manage the area to which the site is assigned.
Serial Number
Polycom, Inc.
The serial number (ASCII only) of the endpoint.The endpoint provides the serial
number if it registered successfully or is managed.
188
Managing Endpoints and Peripherals
Field
Description
Software Version
The version of the software installed on the endpoint (ASCII only). The endpoint
provides the version number if it registered successfully or is managed.
HTTP URL
The management URL for the endpoint, if available (ASCII only). This URL enables
the RealPresence Resource Manager system to start the endpoint’s management
system using the Manage function.
All Polycom endpoints allow management through a browser. For these endpoints,
this field is completed when the endpoint registers with the RealPresence Resource
Manager system.
For Cisco endpoints, you must manually enter the URL if you want to use the
Manage function.
HTTP Port
The HTTP port number for the endpoint. The endpoint provides the port number if it
registered successfully and is managed.
Area
Assign this endpoint to an area.
This field is only visible when Areas are enabled.
A user can only view area-specific information for an area(s) that he has permission
to manage.
If the user manages only one area, the endpoint will automatically be assigned to
that area.
Addresses
DNS Name
SIP URI
The name for the endpoint as entered on the domain name server.
The address used to call the endpoint via SIP.
<username>@host(domain or IP):Port
Aliases
The aliases that allow you to connect to the endpoint. The RealPresence Resource
Manager system converts the aliases to the IP address associated with the
endpoint.
• Alias Type. Possible types include E.164, H.323 ID, URL, Transport Address,
email, Party Number, and Unknown.
• Alias Value. Value for the alias type shown.
Notes
• The following Alias Values are ASCII only: H323 ID, URL, Transport Address,
and Unknown.
• In other cases, the endpoint name is the system name, which might be different
from the H323 ID.
• The value of the E.164 alias is the extension dialed to reach this endpoint.
ISDN Video Number
Polycom, Inc.
For ISDN endpoints only, the country code + city/area code + local phone number
for the endpoint.
When you add an endpoint without native ISDN, the ISDN gateway, country code,
and area code are not captured. The RealPresence Resource Manager system
only supports native ISDN.
189
Managing Endpoints and Peripherals
Field
Description
Capabilities
Supported Protocols
The communication protocols that the endpoint can support. Possible values
include:
• IP (H.323) - A standard that defines the protocols used for multimedia
communications on packet-based H.323 networks.
• IP (SIP) - A standard that defines the protocols used for multimedia
communications on SIP networks.
• ISDN (H.320) - A standard that defines the protocols used for multimedia
communications on switched networks, such as ISDN.
For endpoints with the type Unknown, select H.323.
The endpoint automatically provides the protocols if it registered successfully or is
managed.
Required MCU Service
The MCU service selected for the endpoint to use.
Capabilities Enabled
Capabilities enabled on this endpoint. Options are:
• MCU - The endpoint can act as a control unit for multipoint conferences
• Gateway - The endpoint can act as a gateway for call management
The MCU provides the capability if it registered successfully or is managed.
Monitoring Level
The monitoring level for the endpoint. Possible values include:
• Standard. This endpoint is monitored.
• VIP. This endpoint is monitored closely. The VIP identifier and filters are available
to operators to monitor and manage conferences.
Available to Schedule
Identifies if the endpoint is available when users are scheduling conferences.
8 (Optional) Click Endpoint Group Association and select the endpoint group to associate with. See
Working with Endpoint Groups for details about endpoint groups.
9 Click OK.
The endpoint appears in the Endpoint list. By default, the system may also:
 Add the endpoint to the applicable site.
 Set the HTTP Port to 80.
 Add an Alias for the endpoint.
 Make the endpoint Available to Schedule.
 Set the Monitoring Level to Standard.
For third-party endpoints, the HTTP URL, serial number, and DNS name are not captured during
endpoint registration.
Once you’ve added an endpoint, you can associate it with a user. See Edit a User.
Polycom, Inc.
190
Managing Endpoints and Peripherals
Edit an Endpoint
The system automatically detects IP address changes and updates its database with the new information
for Polycom and third-party endpoints that are registered with the RealPresence Resource Manager
system.
To edit an endpoint in the RealPresence Resource Manager system:
1 Go to Endpoint > Monitor View
2 In the Endpoint Name column, click the endpoint name that you want to edit.
As required, edit the Identification, Addresses, Capabilities, Endpoint Group Association, and
Configuration Profile Association (audio phone only) sections of the Edit Endpoint dialog. For
more information, see View Endpoint Details.
Note that many fields in this dialog are ASCII only.
3 Click Update.
The name of a dynamically-managed endpoint will be updated to the endpoint after the provisioning
interval. To update other information, you need to use provisioning or change the information at the
endpoint interface.
Delete an Endpoint
When you delete an endpoint, you remove the endpoint from the RealPresence Resource Manager system.
You also delete all the associations with the endpoint.
To delete an endpoint:
1 Go to Endpoint > Monitor View
2 Select an endpoint you want to delete.
3 Click
.
4 If the endpoint is dynamically-managed, choose one of the following options:
 Delete Endpoint Only: Deletes the endpoint
 Delete with dial string reservation: Deletes the endpoint and any dial string reservations
associated with the endpoint.
 Cancel: Cancels the action.
5 Click Delete for other endpoints types.
Change an Endpoint Group Association
When you edit an endpoint, you can associate it with an endpoint group, delete its association with an
endpoint group, or prioritize the associated endpoint groups in case of multiple ones.
To change the association from an endpoint to an endpoint group:
1 Go to Endpoint > Monitor View.
Polycom, Inc.
191
Managing Endpoints and Peripherals
2 Click the endpoint name that you want to edit from the Endpoint Name column.
3 In the Edit Device dialog box, click the Endpoint Group Association tab.
 To associate the endpoint to an endpoint group, select the name of the endpoint group from the
drop-down list and click Add.
 To delete the association, click
at the right end of each line of the endpoint group list.
 To prioritize an association, click the
the lowest or highest priority.
buttons to deprioritize or prioritize it, or give it
4 Click OK.
Manage an Endpoint Owner
The endpoint owner is the user associated with the endpoint. You can manage an endpoint owner that uses
scheduled management, but you cannot manage the owner of an endpoint that is dynamically-managed.
To manage an endpoint owner:
1 Go to Endpoint > Monitor View.
2 Select the endpoint of interest and click More > Manage Owner.
The Edit User dialog appears.
3 Edit any user properties you need.
4 Click OK.
Manage an Endpoint
You can navigate to the management interface of an endpoint from the RealPresence Resource Manager.
This function is not available for all endpoint types, including RealPresence Desktop, RealPresence Mobile,
and CMA Desktop.
To manage an endpoint from the RealPresence Resource Manager system:
1 Go to Endpoint > Monitor View
2 Select the endpoint of interest.
3 Click
.
A new browser instance opens and navigates to the web interface of the endpoint.
View Call Information
You can view an endpoint’s call information.
To view call information:
1 Go to Endpoint > Monitor View
2 Select the endpoint of interest.
Polycom, Inc.
192
Managing Endpoints and Peripherals
3 Click More > Call Info.
4 View the information listed in the table below.
Field
Description
Call Info > Site
Far Site Name
The H.323 ID of the far site endpoint to which the selected endpoint is connected.
When multiple endpoints are connected through the endpoint's embedded MCU,
this field displays a concatenation of each endpoint's H.323ID separated by ' | ', for
example 'ISDN-CO1-7-1 | Vsfx-9-1'.
Far Site Number
The address of the far site endpoint to which the selected endpoint is connected.
The address value for the calling endpoint appears to be the dialed address. The
address value for the called endpoint appears to be the IP Address.
Encryption
The type of encryption the far site uses.
Cause Code
The cause code showing how the call ended.
Error
Video FEC Errors
The number of Forward Error Correction (FEC) errors that have been corrected in
the current call.
Sync
Call Type
Type of call, such as, H.323, SIP, ISDN, or POTS.
Call Info > Call Details
Video Protocol
The video connection protocol, both transmission (Tx) and reception (Rx), the
endpoint is using. Possible values include:
• H.261
H.261 is an ITU standard designed for two-way communication over ISDN
lines and supports data rates which are multiples of 64Kbit/s. H.261
supports CIF and QCIF resolutions.
• H.263
H.263 is based on H.261 with enhancements that improve video quality over
modems. It supports CIF, QCIF, SQCIF, 4CIF and 16CIF resolutions.
• H.264
Video Format
The video format, both transmission (Tx) and reception (Rx), the endpoint is using.
Video Rate
The video bandwidth negotiated with the far site.
Video Rate Used
The actual video bandwidth used in the call to the far site.
Video Frame Rate
Specifies the frame rate the endpoint is using.
Audio Protocol
The audio connection protocol, both transmission (Tx) and reception (Rx), the
endpoint is using. Possible values include:
• G.711
• G.722
• G.728
Audio Rate
The audio bandwidth negotiated with the far site
Polycom, Inc.
193
Managing Endpoints and Peripherals
Field
Description
Call Info > Quality of Service (Not reported by all endpoint types)
Total Packet Loss
Specifies the total packet loss for the currently active call that is, the total
percentage of packet loss for all currently active calls divided by the number of
active calls.
% Packet Loss
Specifies the average percentage of packet loss for the currently active call that is,
the total percentage of packet loss for all currently active calls divided by the
number of active calls.
Audio Packet Loss
Specifies the audio packet loss for the currently active call.
Video Packet Loss
Specifies the video packet loss for the currently active call.
Audio Jitter
Specifies the audio jitter for the currently active call.
Video Jitter
Specifies the video jitter for the currently active call.
Call Info > Video Feed
Near Site
The video feed from the endpoint.
Far Site
The video feed from the endpoint to which the endpoint is connected.
Description
A free-form text field (extended ASCII only) in which information about the endpoint
can be added.
GAB Display Name
Enter a name for the endpoint as it will appear in the Global Address Book.
Site
The network site for the endpoint.The system determines the site based upon IP
address.
Note
When areas are enabled on your system, this field shows a value of Restricted if
you do not have permission to manage the area to which the site is assigned.
Serial Number
The serial number (ASCII only) of the endpoint.The endpoint provides the serial
number if it registered successfully or is managed.
Software Version
The version of the software installed on the endpoint (ASCII only). The endpoint
provides the version number if it registered successfully or is managed.
HTTP URL
The management URL for the endpoint, if available (ASCII only). This URL enables
the RealPresence Resource Manager system to start the endpoint’s management
system using the Manage function.
All Polycom endpoints allow management through a browser. For these endpoints,
this field is completed when the endpoint registers with the RealPresence Resource
Manager system.
For Cisco endpoints, you must manually enter the URL if you want to use the
Manage function.
HTTP Port
The HTTP port number for the endpoint. The endpoint provides the port number if it
registered successfully and is managed.
Polycom, Inc.
194
Managing Endpoints and Peripherals
Field
Description
Area
Assign this endpoint to an area.
This field is only visible when Areas are enabled.
A user can only view area-specific information for an area(s) that he has permission
to manage.
If the user manages only one area, the endpoint will automatically be assigned to
that area.
Addresses
DNS Name
The name for the endpoint as entered on the domain name server.
SIP URI
The address used to call the endpoint via SIP.
<username>@host(domain or IP):Port
Aliases
The aliases that allow you to connect to the endpoint. The RealPresence Resource
Manager system converts the aliases to the IP address associated with the
endpoint.
• Alias Type. Possible types include E.164, H.323 ID, URL, Transport Address,
email, Party Number, and Unknown.
• Alias Value. Value for the alias type shown.
Notes
• The following Alias Values are ASCII only: H323 ID, URL, Transport Address,
and Unknown.
• In other cases, the endpoint name is the system name, which might be different
from the H323 ID.
• The value of the E.164 alias is the extension dialed to reach this endpoint.
ISDN Video Number
For ISDN endpoints only, the country code + city/area code + local phone number
for the endpoint.
When you add an endpoint without native ISDN, the ISDN gateway, country code,
and area code are not captured. The RealPresence Resource Manager system
only supports native ISDN.
Capabilities
Supported Protocols
The communication protocols that the endpoint can support. Possible values
include:
• IP (H.323) - A standard that defines the protocols used for multimedia
communications on packet-based H.323 networks.
• IP (SIP) - A standard that defines the protocols used for multimedia
communications on SIP networks.
• ISDN (H.320) - A standard that defines the protocols used for multimedia
communications on switched networks, such as ISDN.
For endpoints with the type Unknown, select H.323.
The endpoint automatically provides the protocols if it registered successfully or is
managed.
Required MCU Service
The MCU service selected for the endpoint to use.
Polycom, Inc.
195
Managing Endpoints and Peripherals
Field
Description
Capabilities Enabled
Capabilities enabled on this endpoint. Options are:
• MCU - The endpoint can act as a control unit for multipoint conferences
• Gateway - The endpoint can act as a gateway for call management
The MCU provides the capability if it registered successfully or is managed.
Monitoring Level
The monitoring level for the endpoint. Possible values include:
• Standard. This endpoint is monitored.
• VIP. This endpoint is monitored closely. The VIP identifier and filters are available
to operators to monitor and manage conferences.
Available to Schedule
Identifies if the endpoint is available when users are scheduling conferences.
 Sites
View an Endpoint’s Video Feed
You can only view the video feed from the following endpoints:
● Polycom HDX system
● Polycom RealPresence Group Series system
● TANDBERG
● VSX-Series
To view the video feed for an endpoint (near site or far site):
1 Go to Endpoint > Monitor View.
2 Select the endpoint of interest.
3 Click More > Call Info.
4 Click the Video Feed tab to see the video feed from the near and far site.
Clear an Endpoint Help Request
This action is only applicable for an HDX system.
To clear an endpoint help request from the RealPresence Resource Manager system:
1 Go to Endpoint > Monitor View
2 As needed, use the Filter to customize the Endpoint list.
3 Select the endpoint of interest and click More > Clear Help.
The Confirm Endpoint Help Clear dialog appears.
4 To send a message to the endpoint as well as clear the help request, check Also send message to
endpoint.
5 Click Clear.
Polycom, Inc.
196
Managing Endpoints and Peripherals
6 If you selected the Also send message to endpoint check box, enter the text message to send the
endpoint in the Send Message to Endpoint dialog and click Send.
The Endpoint list is updated and alerts for the endpoint are cleared.
If the reason for the original alert still exists on the endpoint, the alert will likely reappear in the
Endpoint list.
Send a Message to an Endpoint
In some situations, such as in response to a help request, you can send a message to some types of
endpoints.
This action is not applicable for RealPresence Mobile, RealPresence Desktop or CMA Desktop systems.
To send a message to an endpoint from the RealPresence Resource Manager system:
1 Go to Endpoint > Monitor View
2 Select the endpoint of interest.
If the endpoint can receive text messages, a Send Message option appears in the More menu.
3 Click More > Send Message.
4 In the Send Message to Endpoint dialog, enter a text message and click OK.
The message is sent to the endpoint.
Reboot an Endpoint
An endpoint must be online to get rebooted from the RealPresence Resource Manager system.
To reboot an endpoint from the RealPresence Resource Manager system:
1 Go to Endpoint > Monitor View
2 Click
to enable multiple select.
3 Select the one or more endpoint(s) of interest.
4 Click More > Reboot Device.
5 To confirm the request, click OK.
Associate a User with an Endpoint
This action is available for endpoints that are not dynamically managed such as RealPresence DMA
system-synchronized endpoints. For example, if you associate a user with a RealPresence DMA
system-synchronized endpoint, you can manage that endpoint. Endpoints that are associated with user (or
room) can be scheduled into conferences.
Polycom, Inc.
197
Managing Endpoints and Peripherals
To associate an endpoint to a user:
1 Go to Endpoint > Monitor View
2 Select the endpoint of interest.
3 Click More > Associate User.
4 In the Last Name or Room Name field or the First Name field, enter all or part of the user’s last
name or first name and click Search.
The system displays the list of user or rooms that meet your search criteria.
5 Select the user of interest.
Search for Endpoints in a Range of IP Addresses
You can search for endpoints within a range of IP addresses. This search will only include endpoints that
are not dynamically managed, which are not displayed in the current endpoints list. The purpose of this
function is to provide a quick approach to find out those non-dynamically managed endpoints, so that
RealPresence Resource Manager can add the endpoints in a batch.
To search for a set of endpoints within a range of IP addresses:
1 Go to Endpoint > Monitor View and click More > Search Endpoints.
2 In the Search Endpoints dialog, enter the starting IP address and ending IP address for the search
range and click Search.
The system begins searching for endpoints. A progress bar displays the status of the search and a
results message displays the number of endpoints searched and the number of endpoints found
within the IP range.
Working with Endpoint Groups
Endpoint groups are logical collections of endpoints and are mainly used for audio phones’ provisioning.
Users with the Endpoint Admin or System Setup permission can manage endpoint groups.
The section includes:
● Add an Endpoint Group
● Edit an Endpoint Group
● Copy an Endpoint Group
● Refresh an Endpoint Group
● View Endpoint Group Details
● Delete an Endpoint Group
● Set an Endpoint Group to Top Priority
Add an Endpoint Group
You can define a new endpoint group by selecting a list of existing endpoints in the RealPresence Resource
Manager system.
Polycom, Inc.
198
Managing Endpoints and Peripherals
To add an endpoint group:
1 Go to Endpoint > Endpoint Groups.
2 Click
.
3 Enter a name and description for this endpoint group.
4 In the Endpoint Association tab, select the endpoints you want to include in the group from the
Available table and click the down arrow to move them to the Selected table.
5 In the Phone Configuration Profile Association tab, select a profile from the Configuration
Profile Association drop-down list.
6 Click the Apply button to associate this profile to the endpoint group.
7 Repeat step 5 and step 6 to associate more profiles.
The associated configuration profiles only apply to the audio phones in the endpoint group.
8 Do one of the followings to save the changes:
 Click Apply to apply the phone configuration profiles to the on-line phones in this endpoint group
immediately. This operation may reboot the phones.
 Click OK to only save the change. The RealPresence Resource Manager system will not apply
the changes until the next polling interval.
Edit an Endpoint Group
You can edit an endpoint group and change its associated endpoints and phone configuration profiles at
anytime.
To edit an endpoint group:
1 Go to Endpoint > Endpoint Groups.
2 Do one of the followings to open the Edit Endpoint Group dialog:
 Click the endpoint group hyperlink.
 Select the endpoint group and click
.
3 Make changes as needed.
4 Click OK or Apply to save or apply the changes.
Copy an Endpoint Group
You can create a new endpoint group by cloning an existing endpoint group and making necessary
changes.
To create an endpoint group based on a cloned endpoint group:
1 Go to Endpoint > Endpoint Groups.
2 Select an endpoint group and click
.
3 In the Copy Endpoint Group dialog, enter a name and description for the new endpoint group.
4 Edit the associations as needed.
Polycom, Inc.
199
Managing Endpoints and Peripherals
5 Click OK or Apply to save or apply the changes.
Reboot Phones in an Endpoint Group
You can reboot all the phones belonging to an endpoint group.
To reboot phones:
1 Go to Endpoint > Endpoint Groups.
2 Select an endpoint group.
3 Select More > Reboot Phones.
4 Click OK to confirm the reboot.
Refresh an Endpoint Group
Refresh the Endpoint Group page to see the endpoint group changes make by other users.
To refresh the endpoint group page:
1 Go to Endpoint > Endpoint Groups.
2 Click
.
View Endpoint Group Details
The detail information containing name, description, and its associations are display on the right.
To view details of a profile:
1 Go to Endpoint > Endpoint Groups.
2 Select an endpoint group and click
.
Delete an Endpoint Group
If you delete an endpoint group with endpoints that are associated with phone configuration profiles, all the
associations will be removed.
To delete an endpoint group:
1 Go to Endpoint > Endpoint Groups.
2 Select an endpoint group and click
.
3 Click OK to confirm the deletion.
Set an Endpoint Group to Top Priority
This operation sets the selected endpoint group to the highest priority group in its all associated phones.
Polycom, Inc.
200
Managing Endpoints and Peripherals
For each associated phone, the configuration profiles belonging to the selected endpoint group will have the
highest priority comparing to other endpoint group associated configuration profiles for this phone.
To set an endpoint group to top priority:
1 Go to Endpoint > Endpoint Groups.
2 Select an endpoint group.
3 Select More > Set Top Priority.
4 Click OK.
The endpoint group becomes the group with the highest priority in all its associated endpoints.
Monitoring and Managing Peripherals
If an endpoint is provisioned by the RealPresence Resource Manager system and this endpoint has one or
more peripherals connected, the peripherals can be added and provisioned and you can view information
about the peripherals.
This section includes the following topics:
● Monitor Peripherals
● Link to the Management Web Interface of a Peripheral
● Deleting a Peripheral
● Display Applications
● Peripheral Software Update
● Endpoint Inventory Report
Monitor Peripherals
Use the Peripherals View to monitor peripherals connected to dynamically managed endpoints.
» Go to Endpoint > Peripherals View to view peripherals.
Use Filter
You can use filter to customize the peripherals that you want to display.
To use the filter:
1 Click
.
2 Use the filter choices to display other views of the Endpoint list, which include:
 Endpoint Type
Filters the list by type.
 Paired Endpoint
 IP Address
Filters the list by IP address entered.
 Hardware Version
 Software Version
Polycom, Inc.
Filters the list by the endpoint to which the peripherals are connected.
Filters the list by hardware version entered.
Filters the list by software version entered.
201
Managing Endpoints and Peripherals
3 Click Search.
Peripherals List in the Peripherals View
By default the Peripherals list displays a list of all peripherals that are connected or have been connected
to endpoints managed by the RealPresence Resource Manager system.
The Peripherals list in this view has these fields.
Field
Description
Status
The state of the peripheral. Possible values include:
• Connected
- Peripheral is connected to the endpoint.
• Disconnected
- Peripheral is turned off or no longer connected to the
endpoint.
• Error
- Endpoint reports an error with the peripheral.
• Blank - Endpoint is not reporting that the peripheral is connected.
Paired Endpoint
Name of the endpoint to which the peripheral is connected or Not Paired. The Not
Paired designation means the peripheral was connected to an endpoint, but it is not
connected to one now.
Type
The type of peripheral.
Serial Number
The serial number of the peripheral.
IP Address
The IP address assigned to the peripheral, if applicable.
Hardware Version
The hardware version of the peripheral.
Software Version
The software version of the peripheral.
Link to the Management Web Interface of a Peripheral
You can navigate to the management interface of a peripheral from the RealPresence Resource Manager.
Link to the Management Web Interface of a Peripheral:
1 Go to Endpoint > Peripherals View
2 Select the peripheral of interest.
3 Click More > Manage.
A new browser instance opens and navigates to the web interface of the endpoint.
Deleting a Peripheral
When an endpoint is deleted, the peripherals connected with this endpoint are removed automatically.
When a peripheral is no longer connected to an endpoint, this peripheral is not in the Peripherals View list.
You cannot delete peripherals manually.
Polycom, Inc.
202
Managing Endpoints and Peripherals
Display Applications
For peripherals on which you can install multiple applications, you can display a list of installed applications
and their version.
To display applications:
1 Go to Endpoint > Peripherals View and select a peripheral.
2 Click More > Display Applications.
The Applications Installed on dialog for the selected peripheral appears.
Field
Description
Application Name
Name of the peripheral application.
Version
Version of the peripheral application.
3 Click OK.
Peripheral Software Update
The following peripherals can be updated separately via the RealPresence Resource Manager system:
● HDX Touch Control
● RealPresence Group Series Touch Control
● RealPresence Touch
Other peripherals can be updated with their connected endpoints.
To update a peripheral:
1 Go to Endpoint > Dynamic Management > Upload Software Updates.
2 Select one of the Touch Control peripherals from the Endpoint Type drop down list.
3 Click
to upload the software update file.
See for Creating Dynamic Software Updates for Endpoints details on how to update a software.
Download an Endpoint Inventory Report
You can download an inventory report of endpoints if you have the Admin role.
To download an endpoint inventory report:
1 Navigate to Endpoint > Monitor View.
2 Click
Polycom, Inc.
. The file is saved to the default download folder of your browser.
203
Managing Endpoints and Peripherals
Endpoint Inventory Report
This report is in *.CSV format and includes the following information about each endpoint.
Endpoint Attribute
Value
Endpoint Name
The name of the device.
Endpoint Type
The type of device.
Model
The model number of the device
Manage Mode
Describes if the device is dynamically managed:
●
●
NON_DYNAMIC means it is not dynamically managed.
DYNAMIC means the endpoint is dynamically managed.
Owner Name
The user associated with the device.
IP Address
The assigned IP address of the device.
ISDN Video Number
For ISDN devices only, the country code + city/area code + phone number for the
device.
When you add an endpoint without native ISDN, the ISDN gateway, country code,
and area code are not captured. The RealPresence Resource Manager system
only supports native ISDN.
E.164 Number
The value for the E.164 number associated with this device.
H323 Alias
The value for the H.323 ID is the device name if the device registered with the
gatekeeper and it is a third-party system. In other cases, the device name is the
system name, which might be different then the H323 ID.
SIP URI
The SIP URI address for the device.
Software Version
The version of the software installed on the device (ASCII only). The device
provides the version number if it registered successfully or is managed.
Serial Number
The serial number (ASCII only) of the device.The device provides the serial
number if it registered successfully or is managed.
Sites
The network site for the device. By default, devices are added to the Primary Site.
Note
When areas are enabled on your system, this field shows a value of Restricted if
you do not have permission to manage the area to which the site is assigned.
GK IP
The IP address of the gatekeeper to which the device is registered.
SIP server IP
The IP address of the SIP server to which the device is registered.
Polycom, Inc.
204
Supported Endpoints and Peripherals
The Polycom® RealPresence® Resource Manager system supports managing and monitoring both
Polycom and third-party endpoints.
This section includes the following topics:
● Supported Polycom Endpoints and Peripherals
● Supported Third-Party Endpoints
● Considerations for Third-Party Endpoints
Supported Polycom Endpoints and Peripherals
The following tables describe the RealPresence Resource Manager system support for endpoints based on
endpoint type and category of support. See Polycom RealPresence Resource Manager Release Notes for
more information on tested and supported endpoint versions.
Can be Managed Behind a Firewalli
Reports for ISDN Callse
Reports for IP Callsh
Command and Controlg
Monitoring (Standard)f
Scheduling (Dial in and Dial out)b
Scheduling (Dial In only)e
Scheduled Managementa
Polycom Endpoint Types
Dynamic Managementd
Global Address Book Access
The Polycom Telepresence M100 systems register as endpoint type of Other. As such, the
RealPresence Resource Manager can schedule and perform limited monitoring of these systems.
RealPresence Desktop
N
Y
N
N
Y
Y
N
Y
N
Y
RealPresence Mobile
N
Y
N
N
Y
Y
N
Y
N
Y
CMA Desktop
N
Y
N
N
Y
Y
N
Y
N
Y
Polycom CX5100
N
Y
N
N
N
Y
N
N
N
Y
Polycom, Inc.
205
Can be Managed Behind a Firewalli
Reports for ISDN Callse
Reports for IP Callsh
Command and Controlg
Monitoring (Standard)f
Scheduling (Dial in and Dial out)b
Scheduling (Dial In only)e
Scheduled Managementa
Polycom Endpoint Types
Dynamic Managementd
Global Address Book Access
Supported Endpoints and Peripherals
RealPresence Group Series (must be
dynamically managed)a
N
Y
N
N
Y
Y
Y
Y
N
Y
RealPresence Immersive Studio
system (must be dynamically
managed)
N
Y
N
N
Y
Y
Y
Y
N
N
RealPresence Debut
N
Y
N
N
Y
Y
N
Y
N
Y
RealPresence Centro
N
Y
N
N
Y
Y
Y
Y
N
Y
HDX Series (dynamic management
mode)
N
Y
N
N
Y
Y
Y
Y
Y
Y
HDX Series (scheduled management
mode)
Y
N
Y
N
Y
Y
Y
Y
Y
N
VVX 1500 Series (dynamic
management mode)b
N
Y
N
Y
N
Y
N
Y
N
N
VSX Series
Y
N
Y
N
Y
Y
Y
Y
Y
N
QDX Series
Y
N
Y
N
Y
Y
Y
N
N
N
Polycom Touch Control
N/A
N/A
N/A
N/A
N/A
Y
N
N/A
N/A
N/A
RealPresence Touch Control
N/A
N/A
N/A
N/A
N/A
Y
N
N/A
N/A
N/A
EagleEye Producerc
N/A
N/A
N/A
N/A
N/A
Y
N
N/A
N/A
N/A
EagleEye Director
N/A
N/A
N/A
N/A
N/A
Y
N
N/A
N/A
N/A
EagleEye Director II
N/A
N/A
N/A
N/A
N/A
Y
N
N/A
N/A
N/A
Polycom Peripheral Types
a. Polycom RealPresence Group Series systems must be dynamically managed. If a RealPresence Group
Series system is not dynamically managed, it can still connect to the Global Address Book.
b. The Polycom VVX 1500 cannot be dynamically provisioned when it is behind a Polycom VBP-ST firewall.
c. People count information available from a Polycom EagleEye Producer or EagleEye Director II camera is
available in the Call Detail Report.
d. Dynamic Management and Scheduled Management are mutually exclusive functionality.
Polycom, Inc.
206
Supported Endpoints and Peripherals
e. Scheduling (Dial In Only) and Scheduling (Dial In and Dial Out) are presented as mutually exclusive
functionality. Some endpoints, such as Polycom VVX systems do not have interfaces that can be asked to
perform dialing. Some endpoints, such as CMA Desktop clients and VVX systems require external MCU
resources for dial-in conferences.
f. Standard RealPresence Resource Manager monitoring does not involve using SNMP. It includes endpoint
monitoring (online/offline status) and alerts.
g. Command and Control means the RealPresence Resource Manager system can send a command like
Send Message and Reboot, and the endpoint can receive and act on the command.
h. Reports for IP Calls are generated as part of standard gatekeeper functionality. Reports for ISDN Calls are
additional system functionality. Endpoints that aren't registered with the gatekeeper or ISDN calls send an
alert to the device management function to record CDR information. Some legacy endpoints do not send
this alert so the CDRs are not written.
i. Supported behind a Polycom VBP, Polycom RealPresence Access Director or Acme SBC device with
Access Proxy enabled.
Reports for ISDN Callse
Reports for IP Callsf
Command and Controle
Monitoring (Standard)d
Scheduling (Dial in and Dial out)b
Scheduling (Dial In only)c
Scheduled Managementa
Endpoint Type
Dynamic Managementb
Global Address Book Access
Supported Third-Party Endpoints
Cisco T150 MXP
Y
N
Y
N
Y
Y
Y
Y
N
Cisco 95 MXP
Y
N
Y
N
Y
Y
Y
Y
Y
Cisco C Series
Y
N
Y
N
Y
Y
Y
Y
N
Cisco TelePresence MX
Y
N
Y
N
Y
Y
Y
Y
N
Cisco EX Series
Y
N
Y
N
Y
Y
Y
Y
N
Cisco SX Series
Y
N
Y
N
Y
Y
Y
Y
N
LifeSize Team and Expressa
Y
N
Y
N
Y
Y
Y
Y
Y
Other LifeSize Models
N
N
N
Y
N
N
N
Y
N
Other third-party endpoints:
• Sony PCS
• Aertha Maia Starr
• VCON
(Galaxy and Vigo)
• VTEL
N
N
N
Y
N
N
N
Y
N
a. Scheduled software updates are not supported on LifeSize Team or Express systems.
Polycom, Inc.
207
Supported Endpoints and Peripherals
b. Dynamic Management and Scheduled Management are mutually exclusive functionality. Third-party
endpoints cannot be dynamically managed.
c. Scheduling (Dial In Only) and Scheduling (Dial In and Dial Out) are presented as mutually exclusive
functionality.
d. Standard RealPresence Resource Manager monitoring does not involve using SNMP. It includes endpoint
monitoring (online/offline status) and alerts.
e. Command and Control means the RealPresence Resource Manager system can send a Reboot
command, and the endpoint can receive and act on the command.
f. Reports for IP Calls are generated as part of standard gatekeeper functionality. Reports for ISDN Calls are
additional system functionality. Endpoints that aren't registered with the gatekeeper or ISDN calls send an
alert to the device management function to record CDR information. Some legacy endpoints do not send
this alert so the CDRs are not written.
Considerations for Third-Party Endpoints
The RealPresence Resource Manager system includes additional command and control for select
TANDBERG C Series, Cisco SX series, Cisco EX series, TANDBERG Edge, and LifeSize Team and
Express endpoints. The RealPresence Resource Manager system can send a Reboot command to these
endpoints, and the endpoints can receive and act on the command. In addition, the RealPresence Resource
Manager system can:
● Discover these endpoints by searching for them within a range of IP addresses.
● Complete the initial provisioning of these endpoints.
● Schedule and launch point-to-point conferences on these endpoints.
● Launch the management interface for these endpoints.
In the following sections, some additional considerations for supporting third-party endpoints are discussed,
including:
● Reporting and Monitoring for Third-Party Endpoints
● Considerations for Cisco Endpoints
● Considerations for LifeSize Endpoints
Reporting and Monitoring for Third-Party Endpoints
● The RealPresence Resource Manager system includes standard reporting for select Cisco C Series,
Cisco SX Series, Cisco EX Series, and LifeSize Team and Express endpoints.
● The RealPresence Resource Manager system can monitor select Cisco C Series, Cisco SX Series,
Cisco EX Series, and LifeSize Team and Express endpoints, so when properly configured, the
RealPresence Resource Manager system can provide online/offline status and alerts, display call
status, and provide image support including near and far end images for these endpoints.
Considerations for Cisco Endpoints
Polycom supports managing Cisco endpoints. This section discusses the following topics:
● Enable Cisco Endpoints Global Address Book Access
● Considerations for Cisco Address Books
● Scheduled Provisioning of Selected Cisco Endpoints
Polycom, Inc.
208
Supported Endpoints and Peripherals
● Management of Cisco Endpoints with HTTPS
Polycom, Inc.
209
Supported Endpoints and Peripherals
Enable Cisco Endpoints Global Address Book Access
With the RealPresence Resource Manager system, users of the Cisco150, 990, 880, 770 MXP, Cisco C
Series, Cisco EX Series, Cisco SX Series, and endpoint types can access the Polycom Global Address
Book, so they can see the endpoints in the Global Address Book.
The timing of the endpoint’s connection with the Global Address Book can affect the success of its
connection. We recommend the following process.
To access the Polycom Global Address Book access:
1 At the endpoint, enter the information required for directory set up including the Polycom Global
Address Book/RealPresence Resource Manager system IP address and the path.
For example,
http://<RPRM_IP_ADDRESS>/TMS/Public/external/phonebook/PhoneBookService.asmx
To do this on Cisco endpoints, go to System Configuration> Phone Book Server.
2 Wait for the connections to take effect.
3 At the RealPresence Resource Manager system, go to Endpoint > Monitor View and verify the
endpoint’s Global Address Book connection status is green.
Some notes about the Cisco connection to the RealPresence Resource Manager system’s Global Address
Book:
● Even if the Global Address Book is password protected, Cisco endpoints are not required to provide
a password. They have unrestricted access to the Global Address Book.
● When a Cisco endpoint is connected to the Global Address Book, the Directory Registration status
will display as green.
Considerations for Cisco Address Books
When your Cisco endpoints are registered to a Cisco address book, the endpoint’s directory status will
display as unregistered in the Endpoint > Monitor View screen.
Scheduled Provisioning of Selected Cisco Endpoints
You can set up scheduled provisioning profiles for third-party endpoints. See the appropriate product
documentation for more information about these endpoint configuration fields and their acceptable values.
See Scheduled Endpoint Provisioning for information on implementing scheduled provisioning of endpoints.
For information about restrictions in changing passwords for a specific endpoint, see the documentation for
the endpoint.
Management of Cisco Endpoints with HTTPS
RealPresence Resource Manager system supports using HTTPS when managing a Cisco endpoint.
The following Cisco endpoints are supported with HTTPS (and HTTP): Cisco C series, Cisco SX series and
EX series, as well as Cisco MXP series. The Cisco T-150 series is not supported with HTTPS. By default,
the RealPresence Resource Manager system will try both HTTP and HTTPS when accessing a Cisco
endpoint. For better performance, you can enable the system to try your preferred protocol first.
Polycom, Inc.
210
Supported Endpoints and Peripherals
When HTTPS is used, the Cisco endpoint cannot accept a software update.
To configure the system to use HTTPS when managing Cisco endpoints:
1 Navigate to Endpoint > Scheduled Management > Endpoint Management Settings.
2 Under Cisco Endpoint Management, select the Use HTTPs check box.
 When this check box is selected, the RealPresence Resource Manager system will first use
HTTPS when managing a Cisco endpoint.
 If this check box is not selected, the RealPresence Resource Manager system will first use HTTP
when managing a Cisco endpoint.
Considerations for LifeSize Endpoints
Consider the following when you must support LifeSize endpoints:
● Enable Management of a LifeSize Endpoints
● Provisioning of LifeSize Passwords
● Scheduled Provisioning of LifeSize Endpoints
Enable Management of a LifeSize Endpoints
To facilitate management of a LifeSize endpoints, you must enable the Default Passwords for LifeSize
Endpoint Management option and enter the SSH and web UI passwords for the LifeSize endpoints.
Please see the LifeSize documentation for password parameters.
To enable LifeSize endpoint management:
1 On the RealPresence Resource Manager system, go to Endpoint > Scheduled Management >
Endpoint Management Settings.
2 In the Default Passwords for LifeSize Endpoint Management section of the Endpoint
Management Settings page, enable Use Default Passwords.
3 Enter the Password for User and confirm the password. Refer to the LifeSize system
documentation for information on using SSH to connect to the endpoint, then enter the same SSH
password here.
4 Enter the Password for Web UI User and confirm the password. Refer to the LifeSize system
documentation for information on using a web browser to connect to the endpoint, then enter the
same web UI password here.
5 Click Update.
Provisioning of LifeSize Passwords
Take note of the following when provisioning passwords to LifeSize endpoints:
● The Auto password must be provisioned to meet the LifeSize and SSH/telnet rules for passwords.
Polycom, Inc.
211
Supported Endpoints and Peripherals
● You cannot provision the Auto password to be blank. If you attempt to provision a blank value, the
existing value of the password will not be overwritten. It will remain valid.
● The Web UI or User password can be provisioned to include the numbers 0-9 and/or the symbols *
and #. The system will silently truncate these passwords to a maximum of 16 characters.
● You can provision the Web UI or User password to be blank.
Refer to the LifeSize documentation for more information about the requirements for these password.
Scheduled Provisioning of LifeSize Endpoints
The RealPresence Resource Manager system can provision many fields for LifeSize Team and Express
endpoints. See the appropriate product documentation for more information about these endpoint
configuration fields and their acceptable values.
See the Scheduled Endpoint Provisioning for information on implementing scheduled provisioning of
endpoints.
Polycom, Inc.
212
Polycom Software Endpoints
The RealPresence Resource Manager system enables you to download several Polycom applications for
use in specific environments.
This section includes the following topics:
● Add a Polycom CMA Desktop Custom Logo
● Distribute Polycom RealPresence Desktop for Windows Systems
● Distribute Polycom RealPresence Desktop for MAC OS Systems
Add a Polycom CMA Desktop Custom Logo
You can add your company logo to the Polycom CMA Desktop user interface. This logo will be displayed
on the application user interface before the user logs in. The following illustration shows the default Polycom
CMA Desktop user interface and a customized Polycom CMA Desktop user interface.
Default Polycom CMA Desktop
Branded Polycom CMA Desktop
To avoid distortion, use a logo in GIF or JPG format with a size of approximately 260x215 pixels.
To add a custom logo to the CMA Desktop user interface:
1 Go to Admin > Server Settings > System Logos.
Polycom, Inc.
213
Polycom Software Endpoints
2 In the CMA Desktop Logo section of the System Logos page, click Choose File to browse to a
logo file to use.
3 In the Open dialog, browse to the logo image and select the file.
4 Click Open.
5 Click Upload.
Once a user logs in, is provisioned, and then logs out, the logo will be displayed on the Polycom CMA
Desktop user interface.
Remove a custom logo from the CMA Desktop
You can remove a custom logo from the CMA Desktop systems.
Once a user logs in, is provisioned, and then logs out, the default logo will be displayed on the CMA Desktop
user interface.
To remove a custom logo from the CMA Desktop user interface:
1 Go to Admin > Server Settings > System Logos.
2 In the CMA Desktop Logo section of the System Logos page, click Restore Default.
Distribute Polycom RealPresence Desktop for
Windows Systems
On a Windows XP system, the user installing the Polycom RealPresence Desktop must sign in with
administrative privileges. On a Windows Vista system, the user installing the Polycom must sign into the
Administrator account.
The following procedures assume you have implemented DNS lookup and Windows authentication for
single sign-on.
To deploy the RealPresence Desktop client to users, you have the following distribution options:
● Distribute the client via an email link
● Distribute the client via the management system
● Distribute the client via a desktop management or group policy object
● Distribute the client via a .zip file
● Have users download the client from the Polycom support page
Distribute the client via an email link
You can copy the link for the client from the RealPresence Resource Manager system Downloads page
into an email that you can send to users.
To do this, copy and paste the link (for example,
https://10.47.9.170/SoftUpdate/vvl/CMADesktop_5_2_3_19935/CMADesktop.exe) from the
Downloads page into an email to be sent to users. Include the IP address of the RealPresence Resource
Manager system and usernames and passwords (as required) in the email to users.
Polycom, Inc.
214
Polycom Software Endpoints
Distribute the client via the management system
You can provide users access to the RealPresence Resource Manager system, from which they can
download the client.
To do this, copy and paste the IP address of the RealPresence Resource Manager system into an email to
be sent to users. Include usernames and passwords (as required) in the email to users and instruct them to
access the Downloads link.
Distribute the client via a desktop management or group policy object
Distribute the .exe installation file as a desktop management or group policy object to a location on client
systems and provide directions to users on how to run the executable.
To do this, build a desktop management or group policy object that writes the .exe installation file to a
directory (for example, C:\temp) on the user’s local system. Include the command for executing the file in
an email to be sent to users. For example:
C:\temp\CMA Desktop.exe”/s /v"/qn SBSERVERTYPE=2 SBSERVERADDRESS=nnn.nnn.nnn.nnn
Include the IP address of the RealPresence Resource Manager system and usernames and passwords (as
required) in the email to users.
Distribute the client via a .zip file
Zip the .exe installation file and send it in an email to users. Include the IP address of the RealPresence
Resource Manager system and usernames and passwords (as required) in the email to users. For
endpoints on the public network that will be accessing the system through a firewall, include the IP address
of the firewall system rather than the RealPresence Resource Manager system. The firewall system should
then direct traffic to the RealPresence Resource Managersystem.
Have users download the client from the Polycom support page
You can tell users to download the client from the Polycom support page
(http://support.polycom.com/PolycomService/support/us/support/video/index.html)
User can select a Polycom RealPresence Desktop to download.
With this option, you also need to email users the IP address of the RealPresence Resource Manager and
the requires username and password.
Distribute Polycom RealPresence Desktop for MAC OS
Systems
On a MAC system, the user installing the client must sign in with administrative privileges and an
Administrator account.
The following procedures assumes you have implemented DNS lookup and MAC authentication for single
sign-on.
To deploy the client for MAC OS clients to users, you have the following distribution options:
● Have users download the client from the Polycom support page
● Distribute the Client for MAC OS client via an email link
Polycom, Inc.
215
Polycom Software Endpoints
● Distribute the Mac client via the management system
● Distribute the Mac client via a .dmg file
Have users download the client from the Polycom support page
You can tell users to download the client from the Polycom support page
(http://support.polycom.com/PolycomService/support/us/support/video/index.html)
User can select a Polycom RealPresence Desktop to download.
With this option, you also need to email users the IP address of the RealPresence Resource Manager and
the requires username and password.
Distribute the Client for MAC OS client via an email link
You can copy the link for the client for MAC OS clients from the RealPresence Resource Manager system
Downloads page into an email that you can send to users. To do this, copy and paste the client for MAC
OS link (e.g., http://10.47.9.136/SoftUpdate/vvl/CMADesktopMac_5_2_3/CMADesktop.dmg) from the
Downloads page into an email to be sent to users. Include the IP address of the RealPresence Resource
Manager system and usernames and passwords (as required) in the email to users.
Distribute the Mac client via the management system
You can provide users access to the RealPresence Resource Manager system, from which they can
download the client. To do this, copy and paste the IP address of the client system into an email to be sent
to users. Include usernames and passwords (as required) in the email to users and instruct them to access
the Downloads link.
Distribute the Mac client via a .dmg file
Send the .dmg file in an email to users. Include the IP address of the RealPresence Resource Manager
system and usernames and passwords (as required) in the email to users. For endpoints on the public
network that will be accessing the system through a firewall, include the IP address of the firewall system
rather than the RealPresence Resource Manager system. The firewall system should then direct traffic to
the RealPresence Resource Manager system.
Polycom, Inc.
216
Scheduled Endpoint
Management
Scheduled management enables you to push software updates and provisioning profiles to endpoints at
intervals that you define. You can use scheduled management features to manage Polycom as well as
third-party endpoints.
Scheduled management uses server-to-client communication over HTTP. This management technique is
more appropriate for corporate networks where both the RealPresence Resource Manager and all
endpoints are behind the same firewall.
This section provides an introduction to the Polycom® RealPresence® RealPresence Resource Manager
system endpoint management functionality and operations. It includes the following topics:
● Scheduled Endpoint Provisioning
● Scheduling Endpoint Software Updates
Polycom, Inc.
217
Scheduled Endpoint Provisioning
You can schedule endpoint provisioning for an individual endpoint or group of endpoints. You can have
provisioning scheduled to occur immediately or for a date and time in the future. The provisioning data is
sent in XML format over a secure HTTP connection.
You can schedule provisioning for an unlimited number of endpoints, but the system may limit the number
of active provisioning processes. Some provisioning operations may reboot the endpoint.
You must have Device Administrator or Area Administrator role to use scheduled provisioning features.
This section describes RealPresence Resource Manager system endpoint provisioning operations. It
includes these topics:
This section includes the following topics:
● Supported Endpoints for Scheduled Management
● Scheduled Endpoint Management Settings
● Creating Scheduled Provisioning Profiles
● Scheduling Endpoints for Provisioning
● Endpoint Fields for Scheduled Provisioning Profiles
Supported Endpoints for Scheduled Management
In order to be provisioned, an endpoint’s system name cannot exceed 36 characters or the provisioning will
fail.
Scheduled provisioning is available for these endpoint types:
● Polycom VSX Series endpoints
● Polycom HDX Series--Polycom HDX systems that are not dynamically managed (are not configured
to use a provisioning server)
● Polycom QDX Series endpoints
● Selected Cisco endpoints—Cisco 95, Cisco 150 MXP, Cisco C series, Cisco EX series, and Cisco SX
endpoints
● LifeSize
For detailed information about all supported endpoints, see Supported Endpoints and Peripherals.
Scheduled Endpoint Management Settings
When you use scheduled management for endpoints, you can configure several options that make
management easier.
Polycom, Inc.
218
Automatic Registration Synchronization
You can configure the RealPresence Resource Manager system to send registration server address
information for the global directory server (GDS) when the endpoint is registered to the RealPresence
Resource Manager system.
For the RealPresence Resource Manager system, the GDS is the same as the global address book.
This automatic registration synchronization service only works for endpoints that register with the GDS or
are manually added to the RealPresence Resource Manager system after the Automatic Registration
Synchronization setting is enabled.
So if the Automatic Registration Synchronization setting is enabled and an endpoint registers with the
GDS, the GDS address information is sent to the endpoint. If the Automatic Registration Synchronization
setting is enabled and an endpoint is added manually to the RealPresence Resource Manager system, the
GDS address information is sent to the endpoint.
If automatic discovery and configuration is not successful, you can manually add endpoints.
•
•
Automatic Registration Synchronization works only for endpoints that register with the Global
Directory Server after the setting is enabled; it does not automatically register pre-existing
endpoints.
The RealPresence Resource Manager system only supports Automatic Registration
Synchronization for Polycom and selected third-party endpoints operating that are not dynamically
managed. For supported endpoint types, including third-party endpoint types, see Supported
Endpoints and Peripherals.
To enable Automatic Registration Synchronization of endpoints:
1 Go to Endpoint > Scheduled Management > Endpoint Management Settings.
2 In the Automatic Registration Synchronization section, select Synchronize endpoint
registration and click Update.
After you have changed this setting, all endpoints you added are automatically provisioned.
Support HTTPs for Cisco Endpoint Management
You can choose to have the RealPresence Resource Manager check for an HTTPs connection first when
managing Cisco endpoints.
When this check box is selected, the RealPresence Resource Manager system will check for an HTTPs
connection first when managing Cisco endpoints. If it is not selected, the system checks for an HTTP
connection first.
To set HTTPs as a preference for Cisco endpoints:
1 Navigate to Endpoints > Scheduled Management > Endpoint Management Settings.
Polycom, Inc.
219
2 In the Cisco Endpoint Management section, select the Use HTTPs check box.
When this check box is selected, the RealPresence Resource Manager system will check for an
HTTPs connection first when managing Cisco endpoints.
Set Common Passwords for Endpoints
The Common Password feature enables you to manage endpoints with scheduled management
(provisioning and software updates) that have the same global administrative password. However, it cannot
reset the administrative password on endpoints.
If you use the Common Password feature, access to password-protected data within endpoints is granted
if the specified common password matches the endpoints’ Administrator Password.
To set common passwords for endpoints:
1 Go to Endpoint > Scheduled Management > Endpoint Management Settings.
2 In the Common Password section, select Use a Common Password.
3 Enter the common User Name and the common password in the Password and Verify Password
fields and click Update.
Disable Common Password for Endpoints
You can disable common passwords for endpoints.
To disable common passwords for endpoints:
1 Go to Endpoint > Scheduled Management > Endpoint Management Settings.
2 In the Common Password section, clear Use a Common Password and click Update.
The common password feature is disabled. However, the values for the common password feature
are retained in the database, so you can easily re-enable it.
Creating Scheduled Provisioning Profiles
The first step in scheduled provisioning is to create provisioning profiles for the endpoint types you want to
provision.
The provisioning profile is grouped by pages. You can select which pages to use within the profile. When
the page is selected, the system provisions all the values on that page. When the page is not selected, the
system does not provision any of the values on that page. At least one page must be selected, or the system
returns an error stating “No data to save in profile. Either press Cancel or add pages.”
For information about the endpoint fields that you can provision, see Endpoint Fields for Scheduled
Provisioning Profiles. You may find more implementation details about these fields in the endpoint system
documentation.
The RealPresence Resource Manager system does not include a default profile for scheduled provisioning.
You must create a profile before you can schedule a endpoint for provisioning. Create a different profile for
each endpoint type and group of users.
Polycom, Inc.
220
Some examples of when to use scheduled provisioning profiles:
● To apply a standard set of options to each new endpoint
By creating templates of standard settings for different types of endpoints, or for the needs of different
users, you can have the RealPresence Resource Manager system apply all the settings at once. After
the endpoint is connected and registered with the RealPresence Resource Manager system, you can
use a provisioning profile that defines a range of other options.
● To update the password for all endpoints of a particular type
For security purpose, you can create a provisioning profile to update the password for endpoints on
a regular basis and reuse the same profile quarterly. You might have several profiles, one for each
type of endpoint to update.
Profile settings differ depending on the endpoint type selected.
This section includes the following topics:
● Add a Scheduled Provisioning Profile
● Edit a Scheduled Provisioning Profile
● Clone a Scheduled Provisioning Profile
● Delete a Scheduled Provisioning Profile
Add a Scheduled Provisioning Profile
The first step in scheduled provisioning is to create a profile for the endpoint type you want to provision.
Each page in the scheduled Provisioning Fields dialog has a Provision This Page option. When this
option is selected, the system provisions all of the values on that page. When this option is not selected, the
system does not provision any of the values on that page. At least one page must be selected, or the system
returns an error stating, “No data to save in profile. Either press Cancel or add pages.”
You must have the device administrator role to modify provisioning profiles. Users with the role of area
administrator cannot modify provisioning profiles.
For information about the endpoint fields that you can provision, see Endpoint Fields for Scheduled
Provisioning Profiles. You may find more implementation details about these fields in the endpoint system
documentation.
To add a scheduled provisioning profile:
1 Go to Endpoint > Scheduled Management > Provisioning Profiles.
2 In the Provisioning Profiles page, click
.
3 In the Add Profile dialog, select the Endpoint Type for the provisioning profile, enter a name for the
profile, and click OK. The Edit Scheduling Provisioning Profile dialog appears.
4 As needed, select Provision This Page and complete the General Settings, Video Network,
Monitors, Cameras, Audio Settings, LAN Properties, and Global Services sections of the
Provisioning Fields dialog.
The sections may differ depending on the endpoint type selected.
5 Click OK.
The provisioning profile appears in the updated Provisioning Profiles list.
Polycom, Inc.
221
Edit a Scheduled Provisioning Profile
You can edit an existing provisioning profile. You cannot rename an existing profile. If you want to change
the name of a provisioning profile, you must use the Clone action.
You must have the device administrator role to modify provisioning profiles. Users with the role of area
administrator cannot modify provisioning profiles.
For a detailed description of the endpoint fields you can configure when adding a new scheduled
provisioning profile, see Endpoint Fields for Scheduled Provisioning Profiles.
To edit a scheduled provisioning profile:
1 Go to Endpoint > Scheduled Management > Provisioning Profiles.
2 In the Provisioning Profiles list, select the profile of interest and click
.
3 As needed, select Provision This Page and complete the General Settings, Video Network,
Monitors, Cameras, Audio Settings, LAN Properties, and Global Services sections of the
Provisioning Fields dialog.
You may find more implementation details about these fields in the endpoint system documentation.
The sections may differ depending on the endpoint type selected.
4 Click OK.
The provisioning profile is updated.
Clone a Scheduled Provisioning Profile
If you want to rename an existing provisioning profile or create a new profile based on an existing profile,
you can use the Clone action.
You must have the device administrator role to modify provisioning profiles. Users with the role of area
administrator cannot modify provisioning profiles.
To clone a scheduled provisioning profile:
1 Go to Endpoint > Scheduled Management > Provisioning Profiles.
2 Select a profile and click
.
3 In the Clone Profile dialog, enter a name for the new profile and click OK.
The provisioning profile appears first in the updated Provisioning Profiles list.
4 Edit the this profile as needed.
5 Click OK to save the changes.
Delete a Scheduled Provisioning Profile
You can delete a provisioning profile at any time. Deleted profiles will no longer be sent during scheduled
provisioning updates.
You must have the device administrator role to modify provisioning profiles. Users with the role of area
administrator cannot modify provisioning profiles.
Polycom, Inc.
222
To delete a scheduled provisioning profile:
1 Go to Endpoint > Scheduled Management > Provisioning Profiles.
2 In the Provisioning Profiles page, select a profile and click
.
3 Click OK to confirm the deletion.
The profile is deleted from the RealPresence Resource Manager system.
Scheduling Endpoints for Provisioning
You can schedule provisioning for an unlimited number of endpoints, but the system may limit the number
of active provisioning processes. Keep in mind that provisioning may reboot the endpoint.
● Until the RealPresence Resource Manager system successfully provisions an endpoint scheduled for
provisioning, provisioning remains in the Pending state and the system attempts to provision the
endpoint until it succeeds or until the provisioning is canceled.
● If an endpoint scheduled for provisioning is In a Call, the system waits until the call ends before
provisioning the endpoint. The system checks the endpoint at 15 minute intervals.
● If an endpoint scheduled for provisioning is Offline, the system attempts to connect to it at 60 minute
intervals until the endpoint is Online.
This section describes the scheduled provisioning tasks a user assigned the Device Administrator or Area
Administrator can perform.
● View a List of Eligible Endpoints
● Schedule an Endpoint for Provisioning
● Check the Status of a Scheduled Provisioning Update
● Clear the Status of Scheduled Provisioning
● Cancel a Scheduled Provisioning
View a List of Eligible Endpoints
You can view a list of endpoints registered to the RealPresence Resource Manager system that are eligible
for scheduled provisioning.
You must have Device Administrator or Area Administrator role to use scheduled provisioning features.
You must have already created a provisioning profile to use before you can schedule a provisioning update
for an endpoint.
To view a list of eligible endpoints:
1 Go to Endpoint > Scheduled Management > Provisioning.
2 As needed, click
to filter the Endpoint list.
The filter choice for endpoint types that can be scheduled for provisioning. Possible values include:
 HDX Series—Displays the Polycom HDX systems operating in scheduled management
mode.
 Cisco®
 LifeSize®
Polycom, Inc.
223
 QDX Series
 V and VSX Series
The Endpoint list in this view has the following information.
Field
Description
Status
The status of the endpoint’s last provisioning process. Possible values
include:
•
•
•
•
Success
Pending
Failed
Clear
Endpoint Name
The system name of the endpoint.
Type
The type of endpoint. Scheduled provisioning is only available for the
endpoints types listed in this table as Filter selections.
IP Address
The IP address assigned to the endpoint.
Last
The date and time of the endpoint’s last provisioning, unless its status has
been cleared.
Pending
When the endpoint is scheduled for provisioning, this field shows the
provisioning profile to be used for the scheduled provisioning process.
Scheduled
When the endpoint is scheduled for provisioning, this field shows the date and
time for the next scheduled provisioning process.
Schedule an Endpoint for Provisioning
You can schedule provisioning profiles to be sent to endpoints at times you specify.
You must have Device Administrator or Area Administrator role to use scheduled provisioning features.
To schedule an endpoint for provisioning:
1 Go to Endpoint > Scheduled Management > Provisioning.
2 As needed, click
to filter the endpoint list.
3 Select the endpoints that you want to schedule provisioning updates.
4 Click More > Provision.
5 In the Scheduled Provisioning Profiles dialog, select the appropriate provisioning profile.
6 In the Schedule field, select Now or Later.
7 If you select Later, enter a Date and Time for the provisioning.
8 Select either Use Server Date/Time or Use Endpoint Date/Time as these may differ.
9 Click Schedule.
The Scheduled Provisioning View reappears.
Polycom, Inc.
224
10 Click Refresh and check the Pending column for the provisioning status.
For each endpoint you selected, the name of the profile appears in the Pending column, and the date
and time you entered appears in the Scheduled column.
Check the Status of a Scheduled Provisioning Update
You can monitor the status of scheduled provisioning updates. Until the RealPresence Resource Manager
system successfully provisions an endpoint scheduled for provisioning, provisioning remains in the
Pending state and the system attempts to provision the endpoint until it succeeds or until the provisioning
is canceled.
Profile statuses include: Pending, Failed, Success, and Clear.
You must have Device Administrator or Area Administrator role to use scheduled provisioning features.
To check the status of a scheduled provisioning:
1 Go to Endpoint > Scheduled Management > Provisioning.
2 As needed, click
to filter the endpoint list.
3 Select the endpoint of interest.
4 Click
to open the Device Details section.
5 Expand the Provisioning Details tab.
6 View the Status field to see the current status of the update.
Clear the Status of Scheduled Provisioning
You can reset the provisioning status so you can better monitor succeeding provisioning updates. For
example, you can clear all profile Success statuses.
To clear the status of a scheduled provisioning:
1 Go to Endpoint > Scheduled Management > Provisioning.
2 As needed, click
to filter t the endpoint list.
3 Select the endpoint of which you want to clear the status.
4 Click More > Clear Status.
The endpoint provisioning status returns to Clear.
Cancel a Scheduled Provisioning
You can only cancel provisioning of a Pending process. You cannot cancel the provisioning of an endpoint
while it is In Progress.
To cancel a pending scheduled provisioning:
1 Go to Endpoint > Scheduled Management > Provisioning.
Polycom, Inc.
225
2 As needed, click
to filter the endpoint list.
3 Select the endpoints of interest.
4 Click More > Cancel Provision.
The provisioning operation is canceled and the provisioning status returns to Clear.
Endpoint Fields for Scheduled Provisioning Profiles
The following table shows the fields you can configure when adding a new scheduled provisioning profile
for a Polycom endpoint. You may find more implementation details about these fields in the endpoint system
documentation.
For information about third-party endpoint fields, consult the respective documentation.
HDX Series
VSX Series
QDX Series
.
Maximum Time in Call
(minutes)
Specifies the maximum number of minutes allowed for a call. Enter
0 to remove any limit.
Y
Y
Y
Allow Mixed IP and ISDN
calls
Specifies whether users can make multipoint calls that include both
IP and H.320 sites.
Y
Y
—
Auto Answer Point-to-Point
Calls
Specifies whether to set the endpoint system to answer incoming
point-to-point calls automatically.
Y
Y
Y
Auto Answer Multipoint
Calls
Specifies whether to set the endpoint system to answer incoming
multipoint calls automatically.
Y
Y
—
Allow Directory Changes
Specifies whether users can save changes to the directory or
contacts/favorites list.
Y
Y
Y
Confirm Directory Additions
Upon Call Disconnect
Specifies whether users are prompted to confirm deletions of
directory entries.
Y
Y
Y
Confirm Directory Deletions
Specifies whether users are prompted to confirm new directory
entries when saving the information for the last site called.
Y
Y
Y
Allow Access to User Setup
Specifies whether the User Settings screen is accessible to users
via the System screen.
Select this option to allow users to change limited environmental
settings.
Y
Y
Y
Field
For the endpoint systems being provisioned...
General Settings > System Settings > System Settings 1
General Settings > System Settings > System Settings 2
Far Site Name Display
Specifies how long the far site name to appear on the screen when
the call is first connected.
Y
Y
Y
Display Time in Call
Displays time that the current call has been connected
Y
Y
Y
Polycom, Inc.
226
Field
For the endpoint systems being provisioned...
HDX Series
VSX Series
QDX Series
Keypad Audio Confirmation
Allows the user to hear a voice confirmation of the numbers
selected with the remote control.
Y
Y
Y
Call Detail Report
Collects call data.
Y
Y
Y
Recent Calls
Provides navigational tool for call history.
Y
Y
Y
Color Scheme
Enables the customization of the look of the system with five
different color schemes.
Y
Screen Saver Wait Time
The time the system will delay before going into standby mode
after nonuse.
Y
Y
General Settings > Home Screen Settings > Home Screen Settings 1
Home screen settings cannot be provisioned for Polycom QDX endpoints.
Dialing Display
Dialing entry field - Includes the dialing entry field on the Home
screen.
Display Marquee - Allows the addition of text to the dialing entry
field of the Home screen.
Y
Y
Y
Enter Marquee Text
Enter the Marquee text that will appear in the “Dialing entry field”
when Display Marquee is selected.
Y
Y
Y
Call Quality
Allow users to select the speed/bandwidth of the call.
Y
Y
Y
Display H.323 Extension
Displays the IP dialing extension on the main call screen
Y
Y
Y
Directory
Includes the Directory button on the Home screen.
Y
Y
Y
System
Includes the System button on the Home screen.
Y
Y
Y
Multipoint
Includes the Multipoint navigational item on the Home screen.
Y
Y
General Settings > Home Screen Settings > Home Screen Settings 2
System Name
Enable when the system name is to be displayed on the Home
Screen.
Y
Y
IP or ISDN Information
•
Y
Y
•
•
•
Both – Displays both number types on the system’s Home
screen.
IP only – Display the system IP number on the Home screen.
ISDN only – Displays the system ISDN number on the Home
screen.
None – The system will not display contact numbers on the
Home screen.
Y
Local Date and Time
Displays the local time on the Home screen.
Y
Y
Y
Enable Availability Control
Displays availability icons on the Home screen.
Y
Y
Y
Polycom, Inc.
227
Field
For the endpoint systems being provisioned...
HDX Series
VSX Series
QDX Series
Sites
Displays icons created for frequently called sites on the Home
screen.
Y
Y
Y
Last Number Dialed
Displays the last number dialed on the Home screen.
Y
Y
Y
Remote Access Password
Specifies the password for administrator access when logging in to
the system remotely.
When the remote access password is set, users must enter it to
manage the system from a computer. The remote access
password must not contain spaces.
Y
Y
Y
Meeting Password
Specifies the password users must supply to join multipoint calls
on this system if the call uses the internal multipoint option, rather
than a bridge.
The meeting password must not contain spaces.
Do not set a meeting password if multipoint calls will include
audio-only endpoints. Audio-only endpoints cannot participate in
password-protected calls.
You cannot provision this setting for Polycom VSX systems.
Y
Y
Enable Web Access
Specifies that the endpoint system can be accessed via it’s web
interface.
Y
Y
Y
Y
Y
Y
General Settings > Security
Note
The system restarts if you change the remote access settings. This
setting does not deactivate the associated port, only the
application. Use Web Access Port to disable the port.
Enable Telnet Access
Specifies that the endpoint system can be accessed via a telnet
session.
Note
The system restarts if you change the remote access settings. This
setting does not deactivate the associated port, only the
application. Use Web Access Port to disable the port.
Polycom, Inc.
228
HDX Series
VSX Series
QDX Series
Y
Y
Y
Y
Y
Y
Y
Y
Y
Month
Y
Y
Y
Day
Y
Y
Y
Year
Y
Y
Y
Hour
Y
Y
Y
Minute
Y
Y
Y
AM/PM
Y
Y
Y
Field
For the endpoint systems being provisioned...
AES Encryption
Specifies how to encrypt calls with other sites that support AES
encryption.
• Off—AES Encryption is disabled.
• When Available—AES Encryption is used with any endpoint that
supports it, even if the other endpoints in the call don’t support it.
• Required for Video Calls Only—AES Encryption is used for all
video endpoints in the call. Analog phone and voice over ISDN
connections are allowed. Video endpoints must support AES
Encryption to participate in the call.
• Required for All Calls—AES Encryption is used for all video
endpoints in the call. Analog phone and voice over ISDN
connections are not allowed. All endpoints must support AES
Encryption to participate in the call.
Enable SNMP Access
Specifies that the endpoint system can be accessed via an SNMP
monitoring system.
Note
The system restarts if you change the remote access settings. This
setting does not deactivate the associated port, only the
application. Use Web Access Port to disable the port.
General Settings > Date and Time 1
Date Format
Time Format
Specifies the preferred format preference for the date and time
display and lets you enter your local date and time.
Auto Adjust for Daylight
Saving Time
Specifies the daylight savings time setting. When this setting is
enabled, the system clock automatically changes for daylight
saving time.
Y
Y
Y
Time Difference from GMT
Specifies the time difference between GMT (Greenwich Mean
Time) and the endpoint system’s location.
Y
Y
Y
Time Server
Specifies connection to a time server for automatic system time
settings.
Y
Y
Y
Polycom, Inc.
229
Specifies the address of the time server to use when Time Server
is set to Manual.
QDX Series
Primary Time Server
Address
VSX Series
For the endpoint systems being provisioned...
HDX Series
Field
Y
Y
Y
Video Network > IP Network > Call Preferences
Enable IP H.323
Enables the system to make IP calls
Y
Y
Y
Enable H.239
Specifies standards-based People+Content data collaboration.
Enable this option if you know that H.239 is supported by the far
sites you will call. If callers experience issues when sharing
content with other Polycom systems, disable this setting.
Y
Y
Y
Enable Transcoding
Specifies whether the system enables each far-site system to
connect at the best possible call rate and audio/video algorithm. If
transcoding is disabled, the Polycom HDX system down-speeds all
connections to the same call rate.
Y
Y
ISDN Gateway
Enables users to place IP-to-ISDN calls through a gateway.
Y
Y
IP Gateway
Enables users to place ISDN-to-IP or IP-to-IP calls through a
gateway.
Y
—
Y
Video Network > IP Network > Gatekeeper
Use Gatekeeper
Specifies whether to use a gatekeeper. Gateways and gatekeepers
are required for calls between IP and ISDN.
• Off — Calls do not use a gatekeeper.
• Auto — System attempts to automatically find an available
gatekeeper.
• Specify — Calls use the specified gatekeeper. Enter the
gatekeeper’s IP address or name (for example,
gatekeeper.companyname.usa.com, or 10.11.12.13).
Y
Y
Y
Gatekeeper IP Address
If you chose to use an automatically selected gatekeeper, this area
displays the gatekeeper’s IP address.
If you chose to specify a gatekeeper, enter the IP address.
Y
Y
Y
Use Gatekeeper for
Multipoint Calls
Specify whether multipoint calls use the system’s internal
multipoint capability or the Conference on Demand feature.
Y
Y
Video Network > IP Network > Gateway Number
Country Code
Specifies the country code for the system’s location
Y
Y
Area Code
Specifies the area or city code for the system’s location
Y
Y
Gateway Number
Specifies the gateway’s number
Y
Y
Polycom, Inc.
230
Specifies the number type users enter to call this system:
• Direct Inward Dial — Users enter an internal extension to call
this system directly.
Y
Y
QDX Series
Gateway Number Type
VSX Series
For the endpoint systems being provisioned...
HDX Series
Field
Note
If you choose this setting, you must also register the number with
the gatekeeper as an E.164 alias.
• Number + Extension — Users enter the gateway number and
the system’s extension to call this system.
Number of digits in DID
Number
Specifies the number of digits in the DID number.
The national or regional dialing plan for your location determines
the standard number of digits. For instance, the US standard is 7
digits.
Y
Y
Number of digits in
Extension
Specifies the number of digits in the extension used when Direct
Inward Dial is selected.
Your organization’s dial plan determines this number.
Y
Y
Video Network > IP Network > Quality of Service Settings
Type of Service Field
Specifies the service type and the priority of IP packets sent to the
system for video, audio, and far-end camera control:
• IP Precedence — Represents the priority of IP packets sent
to the system. The value can be between 0 and 7.
• DiffServ — Represents a priority level between 0 and 63. If this
setting is selected, enter the value in the Type of Service Value
field.
Y
Y
Y
Video Type of Service
Value
Specifies the IP Precedence or Diffserv value for video packets.
This value does not apply to the CMA Desktop system. It’s value is
set by the client’s operating system.
Y
Y
Y
Audio Type of Service
Value
Specifies the IP Precedence or Diffserv value for audio packets.
Y
Y
Y
FECC Type of Service
Value
Specifies the IP Precedence or Diffserv value for Far End Camera
Control packets.
Y
Y
Y
Enable Dynamic Bandwidth
Specifies whether to let the system automatically find the optimum
line speed for a call
Y
Y
Enable PVEC
Enables the system to use PVEC (Polycom Video
ErrorConcealment) if packet loss occurs.
Y
Y
Polycom, Inc.
Y
231
VSX Series
QDX Series
For the endpoint systems being provisioned...
HDX Series
Field
Y
Y
Y
Y
Y
Y
Video Network > IP Network > Firewall Settings
Use Fixed Ports
Specifies whether to define the TCP and UDP ports.
• If the firewall is H.323 compatible or the endpoint systems are
not behind a firewall, disable this setting.
• If the firewall is not H.323 compatible, enable this setting. The
endpoint systems will assign a range of ports starting with the
TCP and UDP ports you specify. The endpoint system defaults
to a range beginning with port 3230 for both TCP and UDP.
Note
You must open the corresponding ports in the firewall. You must
also open the firewall’s TCP port 1720 to allow H.323 traffic.
Start TCP Port
Allows you to specify the beginning value for the range of TCP
ports used by the endpoint systems. The endpoint systems will
automatically assign a range of ports starting with the port you
specify.
Note
You must also open the firewall’s TCP port 1720 to allow H.323
traffic.
Start UDP Port
Allows you to specify the beginning value for the range of TCP
ports used by the endpoint systems. The endpoint systems will
automatically assign a range of ports starting with the port you
specify.
Y
Y
Y
NAT Configuration
Specifies whether the endpoint systems should determine the NAT
Public WAN Address automatically.
• If the endpoint systems are behind a NAT that allows HTTP
traffic, select Auto.
• If the endpoint systems are behind a NAT that does not allow
HTTP traffic, select Manual. Then specify a NAT Public
(WAN) Address.
• If the endpoint systems are not behind a NAT or are connected
to the IP network through a virtual private network (VPN), select
Off.
Y
Y
Y
NAT Public (WAN) Address
When NAT Configuration is set to Manual, specifies the
address that callers from outside the LAN should use to call the
endpoint systems.
Y
Y
Y
NAT is H.323 Compatible
Specifies that the endpoint systems are behind a NAT that is
capable of translating H.323 traffic.
Y
Y
Y
Address Displayed in
Global Directory
Specifies whether or not to include the endpoint system’s
information in the global directory
Y
Y
Y
Polycom, Inc.
232
VSX Series
QDX Series
HDX Series
Enable ISDN H.320
Enables this system to make H.320 (ISDN) calls.
Y
Y
Number of ISDN Channels
to Dial in Parallel
Specifies how many channels to dial at one time. You can specify
up to eight channels. If you experience network problems,
decrease the number.
Set this value to 1 for serial dialing. Serial dialing is not
recommended unless you have trouble connecting calls using
parallel dialing.
Y
Y
ISDN Switch Protocols
Specifies the protocol used by your network’s switch.
Y
Y
Outside Line Dialing Prefix
Specifies the ISDN dialing prefix used to call outside the network.
Y
Y
Determines the speeds that will be used for IP, ISDN, or
International ISDN calls from this endpoint system when:
• The Call Quality selection is either unavailable or set to Auto
on the Place a Call screen
• The call is placed from the directory
If the far-site endpoint system does not support the selected
speed, the endpoint system automatically negotiates a lower
speed.
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Restricts the bandwidth used when receiving IP or ISDN calls.
If the far site attempts to call the system at a higher speed than
selected here, the call is re-negotiated at the speed specified in
this field.
Y
Y
Y
Y
Y
Y
Y
Y
Field
For the endpoint systems being provisioned...
Video Network > ISDN BRI Protocol
Video Network > Preferred Speeds
Preferred Speed for
Placing Calls (Kbps)
IP Calls
ISDN Video Call (H.320)
International ISDN calls
Maximum Speed for
Receiving Calls (Kbps)
IP Calls
ISDN Video Call (H.320)
Monitors > Monitors 1
Number of Monitors
The number of monitors of QDX.
Y
Specifies the monitor’s aspect ratio.
• 4:3 — Select if you are using a regular TV monitor.
Y
Monitor 1 Options
Monitor 1
Polycom, Inc.
233
For the endpoint systems being provisioned...
HDX Series
VSX Series
QDX Series
Field
Video Format
Specifies the monitor’s format:
• DVI — Select if the monitor is connected to the DVI connector
using a DVI or HDMI cable.
• VGA — Select if the monitor is connected to the DVI connector
using a VGA cable.
• Component YPbPr — Select if the monitor is connected to the
DVI connector using component cables. Polycom HDX 8000
series and Polycom HDX 7000 series systems do not support
720p Component format for 50 Hz monitors.
• S-Video (Polycom HDX 9000 series only) — Select if the
monitor is connected to the BNC connectors using an S-Video
cable.
• Composite (Polycom HDX 9000 series only) — Select if the
monitor is connected to the BNC connectors using a composite
video cable.
Y
Y
Display Icons in Call
Specifies whether to display all on-screen graphics, including icons
and help text, during calls.
Y
Y
Snapshot Timeout
Lets you choose whether to have slides and snapshots time out
after a period of four minutes.
—
Y
Dual Monitor Emulation
Specifies whether the system can show multiple views on a single
display.
Y
Y
Output Upon Screen Saver
Activation
Specifies whether black video or no signal is sent to the monitor
when the system goes to sleep and the screen saver activates.
• Select Black to display black video. This is the recommended
setting to prevent burn-in for TV monitors.
• Select No Signal to have the display react as if it is not
connected when the system goes to sleep. This is the
recommended setting for VGA monitors and projectors.
Y
VGA Resolution
VGA Resolution of VSX.
—
Y
Monitor 2 Options
Applies to:
Y
—
Y
Monitor 2
Specifies the second monitor’s aspect ratio:
• Off — Select if you do not have a second monitor.
• 4:3 — Select if you are using a regular TV monitor as the second
monitor.
Y
—
Y
Polycom, Inc.
Y
Y
234
Field
For the endpoint systems being provisioned...
HDX Series
VSX Series
QDX Series
Video Format
Specifies the monitor’s format:
• DVI — Select if the monitor is connected to the DVI connector
using a DVI or HDMI cable.
• VGA — Select if the monitor is connected to the DVI connector
using a VGA cable.
• Component YPbPr — Select if the monitor is connected to the
DVI connector using component cables. Polycom HDX 8000
series and Polycom HDX 7000 series systems do not support
720p Component format for 50 Hz monitors.
• S-Video (Polycom HDX 9000 series only) — Select if the
monitor is connected to the BNC connectors using an S-Video
cable.
• Composite (Polycom HDX 9000 series only) — Select if the
monitor is connected to the BNC connectors using a composite
video cable.
Y
—
Y
Output Upon Screen Saver
Activation
Specifies whether black video or no signal is sent to the monitor
when the system goes to sleep and the screen saver activates.
• Select Black to display black video. This is the recommended
setting to prevent burn-in for TV monitors.
• Select No Signal to have the display react as if it is not
connected when the system goes to sleep. This is the
recommended setting for VGA monitors and projectors.
Y
—
Y
People Display Mode
Y
Content Display Mode
Y
Color System
Y
Monitor 3 Options
Monitor 3
Specifies the aspect ratio for recording.
• Off — Select if you do not have a VCR or DVD player connected
to record video conferences.
• 4:3 — Select to record for playback on a standard monitor.
• 16:9—Select to record for playback on a wide-screen monitor, if
your recording device has this capability.
See the endpoint product documentation for more information
about these selections.
Y
—
Video Format
Specifies the VCR or DVD player’s format:
• S-Video — Select if the VCR or DVD player is connected to a
Polycom HDX system using an S-Video cable.
• Composite — Select if the VCR or DVD player is connected to
a Polycom HDX system using a composite video cable and
S-Video to RCA adapter.
Y
—
Polycom, Inc.
235
For the endpoint systems being provisioned...
HDX Series
VSX Series
QDX Series
Field
Output Upon Screen Saver
Activation
Specifies whether black video or no signal is sent to the VCR or
DVD player when the system goes to sleep and the screen saver
activates.
• Select Black to send black video.
• Select No Signal to have the VCR or DVD player react as if it
is not connected when the system goes to sleep.
Y
—
VCR/DVD Record Source
Specifies the video source to be recorded to videotape or DVD.
• If Far is enabled, the recorded video will switch to the current
far site speaker.
• If both Near and Far are enabled, the recorded video will
switch between near and far sites depending on the current
speaker.
• If Content is enabled, any content sent during the call is
recorded.
Y
—
Y
—
Y
—
Y
—
The time the system will delay before going into standby mode
after nonuse
Y
Far Control of Near
Camera
Specifies whether the far site can pan, tilt, or zoom the near-site
camera. When this option is selected, a user at the far site can
control the framing and angle of the camera for the best view of the
near site.
Y
Y
Y
Backlight Compensation
Specifies whether the camera should automatically adjust for a
bright background. Backlight compensation is best used in
situations where the subject appears darker than the background.
Y
Y
Y
Primary Camera
Specifies which camera is the main camera.
Y
Y
Y
Camera Direction
Specifies the direction the camera moves when using the arrow
buttons on the remote control.
Y
Y
Y
Camera 1 Name
Specifies a name for camera 1.
Y
Y
Y
Camera 1 Icon
Specifies an icon for camera 1.
Y
Y
Y
Camera 2 Name
Specifies a name for camera 2.
Y
Y
Y
Camera 2 Icon
Specifies an icon for camera 2.
Y
Y
Y
Camera 3 Name
Specifies a name for camera 3.
Y
Y
Y
Camera 3 Icon
Specifies an icon for camera 3.
Y
Y
Y
Near
Far
Content
Screen Saver Wait Time
Cameras > Cameras 1
Cameras > Camera Settings
Cameras > Video Quality
Polycom, Inc.
236
Specifies Motion or Sharpness for the video input. The default is
Sharpness.
• Motion — This setting is for showing people or other video with
motion.
• Sharpness — The picture will be sharp and clear, but
moderate to heavy motion at low call rates can cause some
frames to be dropped. Sharpness is available in point-to-point
H.263 and H.264 calls only. It is recommended for HD calls
between 1 Mbps and 2 Mbps.
Camera 2
Camera 3
QDX Series
Camera 1
VSX Series
For the endpoint systems being provisioned...
HDX Series
Field
Y
Y
Y
Y
Y
Y
Y
Y
Y
Audio Settings > Audio Settings 1
Sound Effects Volume
Sets the volume level of the ring tone and user alert
tones.
Y
Y
Y
Incoming Video Call
Specifies the ring tone used for incoming calls.
Y
Y
Y
User Alert Tones
Specifies the tone used for user alerts.
Y
Y
Y
Mute Auto Answer Calls
Specifies whether to mute incoming calls.
Incoming calls are muted by default until you press the
mute on the microphone or on the remote control.
Y
Y
Y
Line Input
Specifies the type of equipment that is connected to audio input 1.
Y
Y
Input Type Level
Sets the volume level for audio input 1.
Y
Y
Line Input Level
Sets the volume level for audio input 2.
Y
Y
Line Outputs
Specifies how the audio output behaves. The default selection,
Monitor - Far Site Audio, supplies audio to the Monitor 1 audio
outputs only when the system is receiving audio from the far site.
If you have connected a VCR to record the conference, select
Monitor - Far and Near Audio to supply audio from both the
far site and the system’s microphones.
Y
Y
Line Output Level
Sets the volume level for audio output
Y
Y
Audio Settings > Audio Settings 2
Master Audio Volume
Sets the volume level for audio from the far site.
Y
Y
Midrange Speakers
Specifies whether to use the system’s built-in midrange speaker.
You may prefer to turn off the midrange speaker if you connect the
audio output to Monitor 1 or if you connect an external speaker
system.
—
Y
Bass
Sets the volume level for the low frequencies without changing the
master audio volume.
Y
Y
Polycom, Inc.
Y
237
Sets the volume level for the high frequencies without changing the
master audio volume.
Y
Y
QDX Series
Treble
VSX Series
For the endpoint systems being provisioned...
HDX Series
Field
LAN Properties > LAN Properties 1
Connect to My LAN
Enables connection to the local area network
Y
Y
IP Address
Specifies how the system obtains an IP address.
• Obtain IP Address Automatically — Select if the system
gets an IP address from the DHCP server on the LAN.
• Enter IP Address Manually — Select if the IP address will
not be assigned automatically.
Y
Y
Y
Use the Following IP
Address
If you selected Enter IP Address Manually, enter the IP
address here.
Y
Y
Y
LAN Properties > LAN Properties 2
DNS Servers
Displays the DNS servers currently assigned to the system.
If the system does not automatically obtain a DNS server address,
enter up to four DNS servers here.
Changing this setting causes the system to restart.
Y
Y
Y
Default Gateway
Displays the gateway currently assigned to the system.
If the system does not automatically obtain a gateway IP address,
enter one here.
Changing this setting causes the system to restart.
Y
Y
Y
Subnet Mask
Displays the subnet mask currently assigned to the system.
If the system does not automatically obtain a subnet mask, enter
one here.
Changing this setting causes the system to restart.
Y
Y
Y
WINS Server
Displays the server running the Windows Internet Name Service
—
Y
WINS Resolution
Enables connection to the WINS Server for URL resolution
—
Y
LAN Speed
Specify the LAN speed to use. Note that the setting you choose
must be supported by the switch.
Choose Auto to have the network switch negotiate the speed
automatically. In this case, the switch must also be set to Auto.
Choosing Auto automatically sets Duplex Mode to Auto.
If you choose 10 Mbps, 100 Mbps, or 1000 Mbps you must set
Duplex Mode to Half or Full.
Changing this setting causes the system to restart.
Y
Y
Y
Note
Mismatches with the network switch settings may lead to
unexpected behaviors.
Polycom, Inc.
238
Specify the duplex mode to use. Note that the Duplex mode you
choose must be supported by the switch.
Choose Auto to have the network switch negotiate the Duplex
mode automatically. In this case, the switch must also be set to
Auto. Choosing Auto automatically sets LAN Speed to Auto.
Changing this setting causes the system to restart.
QDX Series
Duplex Mode
VSX Series
For the endpoint systems being provisioned...
HDX Series
Field
Y
Y
Y
Global Services > Directory Servers
Global Directory (GDS)
Specifies the IP address or DNS address of the Global Directory
Server.
Y
Y
Y
Password
Lets you enter the global directory password, if there is one.
Y
Y
Y
Display Name in Global
Directory
Specifies whether to display the system’s name in the global
directories of other registered systems. Global Address
Y
Y
Y
Display Global Addresses
Displays other registered systems in the global directory.
Y
Y
Y
Register
Registers this system with the Global Directory Server.
Y
Y
Y
Save Global Directory to
System
Copies the global directory to this local system. When this setting
is disabled, the system can display no more than 1,000 global
directory entries. When this setting is enabled, the system can
display up to 4,000 global directory entries.
Y
Y
Y
—
—
—
—
—
—
—
—
—
—
—
—
LAN/H.323 > Global Directory (GDS) > Preferences
Show Addresses in
Address Book
Preferred Speed for Placing
Calls (Kbps)
ISDN Video Call (H.320)
International ISDN calls
IP Calls
Determines the speeds that will be used for IP, ISDN, or
International ISDN calls from this endpoint system when:
• The Call Quality selection is either unavailable or set to Auto
on the Place a Call screen
• The call is placed from the directory
If the far-site endpoint system does not support the selected
speed, the endpoint system automatically negotiates a lower
speed.
LAN/H.323 > Global Directory (GDS) > Preferred Alias
Preferred Alias
Possible values include:
• Gateway Number
• ISDN Number
• Called Party Line Identifier
• Extension
Global Services > Account Validation
Polycom, Inc.
239
For the endpoint systems being provisioned...
HDX Series
VSX Series
QDX Series
Field
Require Account Number
to Dial
Specify whether to require an account number for placing calls and
whether that number should be validated by the system.
Y
Y
Validate Account Number
Specify whether to require an account number for placing calls and
whether that number should be validated by the system.
Y
Y
Contact Person
Specifies the name of the person responsible for this system
Y
Y
Y
Contact Number
Specifies the phone number of the person responsible for this
system
Y
Y
Y
Contact Email
Specifies the email address of the person responsible for this
system
Y
Y
Y
Contact Fax
Specifies the Fax number of the person responsible for this system
Y
Y
Y
Tech Support
Specifies the contact information for Technical Support for this
system
Y
Y
Y
City
Specifies the location of the person responsible for this system
Y
Y
Y
State/Province
Y
Y
Y
Country
Y
Y
Y
Global Services > My Info
Polycom, Inc.
240
Scheduling Endpoint Software Updates
The Polycom RealPresence Resource Manager system’s software update feature, which requires a
software update profile for the endpoint type and model, allows an administrator to upgrade the software on
one or more endpoints with a standard software package. This eliminates the need to upgrade each
endpoint individually.
The RealPresence Resource Manager system supports two exclusive software update processes: dynamic
and scheduled. Dynamic and scheduled software update are exclusive endpoint management scenarios.
Endpoints enabled for dynamic software update should not be scheduled for software updates through the
system.
Polycom recommends that all endpoints in a region (that is, a gatekeeper zone) be managed by a
single management system.
This section describes how to use Polycom RealPresence Resource Manager system to schedule software
updates for endpoints. It includes these topics:
● Software Update Considerations for Multi-Tenancy
● Creating Scheduled Software Updates for Endpoints
● Using Scheduled Software Updates
Software Update Considerations for Multi-Tenancy
Within a multi-tenancy environment, area administrators are not allowed to create software updates or set
up maintenance windows for dynamic software updates. However, they are allowed to schedule software
updates that have already been uploaded by a user with the administrator role.
Software update images are also not area-aware, which means that users with area administrator roles see
all software updates on the system, not just those for their area. As a best practice, the system administrator
should either name the software update appropriately or add information to the description field of the
update so that area administrators know which updates to use for their area.
Creating Scheduled Software Updates for Endpoints
To implement scheduled software updates, you must first create respective software updates for your
endpoints.
Only users with the administrator role can create software updates.
1 List the Serial Numbers for the Endpoints to be Updated.
2 Download the Required Software Package.
Polycom, Inc.
241
Scheduling Endpoint Software Updates
3 Request Update Activation Keys.
4 Upload the Software Update for Scheduled Software Updates.
List the Serial Numbers for the Endpoints to be
Updated
You need to create a text file that contain the list of endpoints to be updated.
To list the serial numbers for the endpoints to be updated:
1 Go to Endpoint > Scheduled Management > Upload Software Updates.
2 Select the endpoint type for which to get serial numbers.
a If getting serial numbers for a scheduled update, select the appropriate Endpoint Type and
Endpoint Model combination for the endpoint to update. You can select more than one Endpoint.
b If getting serial numbers for a dynamic software update, click the appropriate tab for the endpoint.
3 Click Get Serial Numbers from the More menu.
The Endpoint Serial Number List appears listing the endpoints of the selected type and model that
are eligible for software updates.
Field
Description
Name
The name assigned to the endpoint system
IP Address
The IP address assigned to the endpoint.
Version
The current software version installed on the endpoint.
Site
The site to which the endpoint belongs.
Note
When areas are enabled on your system, this field shows a value of
Restricted if you do not have permission to manage the area to which
the site is assigned.
Area
(Available only when Areas are enabled.) The area with which the
endpoint is associated.
Users can only view area information for the areas to which they belong
or have been assigned to manage.
4 As needed, use the Filter to customize the endpoint list.
5 Select the specific endpoints to be updated.
6 Click Get Serial Numbers from the More menu.
The serial number(s) appear in the text box on the page.
7 Create a .txt file containing the serial number(s).
a Copy and paste the serial numbers from the endpoint serial number list to a .txt file that you can
submit to the Polycom Product Activation site. Put one serial number per line as shown in the
following example.
Polycom, Inc.
242
Scheduling Endpoint Software Updates
82071007E1DACD
82070407E010CD
820418048078B2
82040903E00FB0
b Save the .txt file.
c Return to the endpoint serial number list and click Close.
The Software Updates list reappears.
8 Repeat from step 2 to step 7 for the each endpoint or set of endpoints to be updated. You may
include all of the serial numbers for all of the different endpoint types in the same .txt file.
9 Click Close.
The Software Updates list reappears.
Download the Required Software Package
You need to download the required software packages to update the software.
To download the software package required to update the endpoints:
1 On your local system, create a directory to which to save the software package (if one does not
already exist).
2 For Polycom endpoints:
a Open a web browser and go to http://support.polycom.com.
b In the Downloads section, select the Product and Category for the required software package.
c Select the software package and save it to the directory created in step 1.
d Repeat steps a through c for each endpoint type to be updated. Note that the software package
may contain the software for different models of the same endpoint type.
3 For third-party endpoints, follow the company’s recommended procedure for downloading a
software package. Save it to the directory created in step 1.
Request Update Activation Keys
You need to request upgrade activation keys from Polycom’s technical support site.
To request upgrade activation keys:
1 For Polycom products
a Go to http://support.polycom.com.
b Log in or Register for An Account.
c Select Product Activation.
d In the Software Upgrade Key Code section, click Retrieve Software KeyCode.
e When upgrading a single endpoint:
 Enter the serial number of the endpoint to be updated into the Serial Number field of the
Single Upgrade Key Code section.
Polycom, Inc.
243
Scheduling Endpoint Software Updates
 Enter the version number to which you are upgrading and click Retrieve.
 The key code is returned on the screen.
 Record the key code and create a .txt file with the Serial Number - Key Code combination
to be updated.
 Close the Product Activation screens.
f
When updating multiple endpoints from a prepared .txt file (step a):
 In the Multiple Upgrade KeyCode section, click Add Attachment.
 Browse to the location of the .txt file you created in step a and click Upload.
 A file containing the Serial Number - Key Code combinations will be emailed to the specified
email account.
 When you receive the .txt file, save it to your local system.
 Close the Product Activation screens.
2 For third-party endpoints, follow the company’s recommended procedure for requesting an upgrade
activation key.
Upload the Software Update for Scheduled Software
Updates
Polycom recommends you to do software updates using the split packages available on Polycom’s support
website to reduce system resource consuming.
To upload the software package and create a software update profile:
1 Go to Endpoints > Scheduled Management > Upload Software Updates.
2 Select an endpoint type to update.
3 Click
.
4 In the Upload Software Update dialog, verify the endpoint type and model.
5 If an activation key code is required to activate the software update, click Update Requires Key and
in the Software Update Key File field browse to the .txt key file (received in Request Update
Activation Keys).
The key is generated from the endpoint serial number and version number, and Polycom sends it as a
text (.txt) file to the customer when new software is available. Customers can review their key
history at http://support.polycom.com.
6 In the Software Update File field, browse to the software update file you downloaded.
7 Enter a meaningful description that will help other users to understand the purpose of the software
update.
8 Click OK.
A software update profile for the endpoint type and model type is created.
Polycom, Inc.
244
Scheduling Endpoint Software Updates
Using Scheduled Software Updates
The scheduled software update feature is enabled at the RealPresence Resource Manager system. An
administrator with System Setup permissions can schedule software updates for one endpoint or a group
of endpoints to occur immediately or for a date and time in the future.
Some notes about scheduled software updates:
● Until the RealPresence Resource Manager system successfully updates an endpoint scheduled for
updating, the update remains in the Pending or In Progress state and the RealPresence Resource
Manager system attempts to update the endpoint until it succeeds or until the update is canceled.
● If an endpoint scheduled for update is In a Call, the RealPresence Resource Manager system waits
until the call ends before updating the endpoint. The system checks the endpoint at 15 minute
intervals.
● If an endpoint scheduled for update is Offline, the RealPresence Resource Manager system
attempts to connect to the endpoint every hour until the endpoint is Online.
● A software update may reboot the endpoint.
This section includes these topics:
● Supported Endpoints for Scheduled Software Updates
● Schedule the Software Update for Endpoints
● Scheduled Software Update View
● View Scheduled Software Update Information
● View List of Software Update Packages
● Cancel Software Updates
Supported Endpoints for Scheduled Software Updates
Scheduled software updates are available for these endpoint types.
● HDX Series--when operating in scheduled management mode (not using a provisioning server)
● LifeSize
● Cisco T150
● Cisco C-Series
● Cisco SX-Series
● Cisco EX-Series
● Cisco MXP series
Schedule the Software Update for Endpoints
Only users with the administrator role can schedule software updates. Users with the area administrator role
cannot schedule software updates.
To schedule one or more endpoints for software update:
1 Go to Endpoint > Scheduled Management > Schedule Software Updates.
Polycom, Inc.
245
Scheduling Endpoint Software Updates
2 As needed, click
to filter the endpoint list.
3 Select the endpoints of interest and click Software Update from the More menu.
4 In the Schedule Software Update dialog, specify when the update should occur.
a In the Schedule field, select Now or Later.
b If you select Later, enter a Date and Time for the update.
c Select either Use Server Date/Time or Use Endpoint Date/Time as these may differ.
5 Select from these options.
Fields
Description
Remove address book entries
Select this check box to have all local address book entries removed after the
update.
Remove system files
Select this check box to have all endpoint settings removed after the update.
You must then reconfigure the endpoint.
Allow endpoint to be a DHCP
server
Caution: You may apply a single software update request to multiple endpoint models. If the request
includes one or more scheduling options that are not valid for a selected endpoint model, the system
applies only the options that are valid.
6 Click Schedule.
For each endpoint selected, the status changes to Pending and the date and time for the software
update appears in the Scheduled column.
Scheduled Software Update View
Use Scheduled Software Update, available from the Endpoint menu, to:
● View the list of endpoints that are eligible for a scheduled software update
● Schedule one or more endpoints for a software update
● Cancel a scheduled software update.
Endpoint List in the Scheduled Software Update View
By default the Endpoint list in Scheduled Software Update displays all endpoints eligible for scheduled
software update.
The Endpoint list in Scheduled Software Update has the following information.
Polycom, Inc.
246
Scheduling Endpoint Software Updates
Field
Description
Filter
Filter choices for this view include:
• Endpoint Type—Filters the list by endpoint type.
• Endpoint Name—Searches the list by the endpoint’s system name.
• IP Address—Searches the list by endpoint’s IP address.
• ISDN Video Number—Searches the list by endpoint’s ISDN video number.
• Alias—Searches the list by endpoint’s alias.
• Site—Searches the list by site location.
• Area—Filters the endpoint list by area. This filter is only available when
areas are enabled and when the user manages more than one area.
Status
The status of the endpoint’s last scheduled software update. Possible values
include:
• Success
• Failed
• Clear
Name
The system name of the endpoint.
Model
The type of endpoint. Scheduled software update is only available for these
endpoint types:
• HDX Series--when operating in scheduled management mode (not using a
provisioning server)
• QDX Series
• LifeSize
• Cisco T150
• Cisco C-Series
• Cisco SX-Series
• Cisco EX-Series
• Cisco MXP series
IP Address
The IP address assigned to the endpoint.
Current Version
The version of software installed during the last successful software update
procedure.
Scheduled
When the endpoint is scheduled for software update, this field shows the date
and time for the scheduled software update process.
Scheduled Software Update Actions
Besides providing access to the endpoint views, you can perform the following actions:
Action
Use this action to...
Software
Update
Schedule software update for the selected endpoints.
Polycom, Inc.
247
Scheduling Endpoint Software Updates
Action
Use this action to...
Cancel Update
Cancel a scheduled or in progress software update operation.
Clear Status
Change the status column for an endpoint to the Clear state.
For information about these endpoint actions, see Scheduling Endpoint Software Updates.
View Scheduled Software Update Information
You can view software update information for endpoints that are scheduled eligible for scheduled software
updates.
To view information about scheduled software updates:
1 Go to Endpoint > Scheduled Management > Schedule Software Update.
2 As needed, click
to filter the endpoint list. Filter choices include Endpoint Type, Endpoint
Name, IP Address, ISDN Video Number, Dial String, and Site.
3 Select the endpoint of interest.
4 Click
to open the Endpoint Summary pane, expand the Software Update Details tab. For
more information, see View Software Update Details.
View List of Software Update Packages
You can view a list of endpoints eligible for software updates.
To view the list of scheduled software update packages:
» Go to Endpoint> Scheduled Management > Upload Software Updates.
The Upload Software Updates page appears listing all of the endpoint types and models for which
the RealPresence Resource Manager system can perform a scheduled software update. It includes
this information. If a software update package has been uploaded to the system, the Description and
Uploaded fields are populated for the endpoint.
Cancel Software Updates
You can cancel scheduled software updates for an endpoint.
To cancel scheduled software updates:
1 Go to Endpoint > Scheduled Management > Schedule Software Updates.
2 As needed, click
to customize the endpoint list.
3 Select the endpoint or endpoints of interest and click Cancel Update from the More menu.
A confirmation dialog appears. The dialog may indicate that one or more of the selected endpoints
had a software update in progress.
Polycom, Inc.
248
Scheduling Endpoint Software Updates
4 Click OK to cancel in progress and future software updates for the selected endpoints and clear
their status.
You can cancel software update operations that are in progress, but you may wish to check the
endpoint afterward to verify it was left in a operational state.
Polycom, Inc.
249
Dynamic Management
This section provides an introduction to the RealPresence Resource Manager system dynamic endpoint
management functionality and operations. It includes:
● Understanding Dynamic Endpoint Management
● Dynamically Updating Endpoint and Peripheral Software
● Using Dynamic Provisioning Profiles
● Creating Dynamic Provisioning Rules
● Dynamically Managing Endpoint Naming Schemes
● Using Bundled Provisioning Profiles
● Using Access Control Lists
● Dynamic Provisioning of Endpoints for SIP Server Integration
● Using Zero-Touch Provisioning
● Enable Polycom® Concierge
● Dynamically Managing a RealPresence Access Director System
Polycom, Inc.
250
Understanding Dynamic Endpoint
Management
When you dynamically manage an endpoint, you can remotely control the configuration settings and
software version of an endpoint, according to policies you define.
Administrators use the flexibility of a rule-based system to apply dynamic provisioning profiles. An
administrator can create multiple rules and associate a profile with more than one rule at a time. A
provisioning rule consists of one or more conditions that must be met before the dynamic provisioning profile
can be applied.
Dynamic management enables a Polycom endpoint to poll the Polycom® RealPresence® Resource
Manager system automatically to get provisioning updates (configuration settings) and software updates on
a regular basis.
Dynamic management is client-to-server over HTTPS which makes it more secure and firewall-friendly.
Dynamic management is available:
● Only for Polycom endpoints.
● When Polycom endpoints are able to automatically discover the RealPresence Resource Manager
system. This means you must add the DNS service record (SRV record) for the RealPresence
Resource Manager system to your DNS server.
In dynamic management mode, when a endpoint starts up and at designated intervals thereafter, it
automatically polls the RealPresence Resource Manager system for a newer software update package or
provisioning profile. If a either is found, the package URL is sent in XML format over a secure HTTPS
connection.
Endpoints do not poll the system if they are in a call. They restart polling after the call ends.
This section provides an overview on dynamic management. It includes the following topics:
● Supported Polycom Endpoints and Peripherals
● Overview of Dynamic Management Setup
● Selective Provisioning of Dynamically Managed RealPresence Group Series Systems
● Dynamically Manage RealPresence Immersive Studio Systems
● Stop Dynamic Management of an Endpoint
Supported Polycom Endpoints and Peripherals
You can only dynamically manage some Polycom endpoints. The following Polycom endpoints and
peripherals can be dynamically managed:
● RealPresence Group Series systems (must be dynamically managed)
● RealPresence Immersive Studio systems (must be dynamically managed)
● RealPresence Group Touch Control
Polycom, Inc.
251
Understanding Dynamic Endpoint Management
● RealPresence Mobile (must be dynamically managed)
● RealPresence Desktop (must be dynamically managed)
● Polycom VVX systems
● Polycom HDX systems
● HDX Touch Control
● CMA Desktop (must be dynamically managed)
You should use either scheduled or dynamic provisioning for an endpoint, never both.
Overview of Dynamic Management Setup
Setting up dynamic management of Polycom endpoints is a multi-step process. You’ll need to have your
DNS server configured, the endpoint needs to be configured to use the RealPresence Resource Manager
system as its provisioning server, and you need to set up provisioning profiles and software updates.
You need to dynamically provision a Polycom endpoint BEFORE you integrate with the RealPresence
DMA system. If you manually register the system with the RealPresence DMA system before you
dynamically provision the endpoint, the RealPresence Resource Manager system will show two
endpoints in the Monitoring screen instead of one.
The following topics provide an overview of each step:
● Configure your DNS Server
● Configure Endpoints to use a Provisioning Service
● Define Endpoint Naming Schemes
● Create Video Endpoint Provisioning Profiles
● Create Provisioning Rules
● Create Access Control Lists
● Create Software Updates
Configure your DNS Server
Configure the DNS server, if you wish it to resolve queries for the RealPresence Resource Manager by the
RealPresence Resource Manager’s host name or IP address.
To dynamically manage endpoints (which includes dynamic provisioning, dynamic software update, and
presence), they must be able to automatically discover the RealPresence Resource Manager. This means
you must add the DNS service record (SRV record) for the RealPresence Resource Manager.
Polycom, Inc.
252
Understanding Dynamic Endpoint Management
Configure Endpoints to use a Provisioning Service
At the physical endpoint, configure the endpoint to use the RealPresence Resource Manager system as its
provisioning service.
You do this via the endpoint’s web interface or soft endpoint’s utility. You can do this on initial setup or at
any time when you need to switch to dynamic management.
Some Polycom endpoints must be dynamically managed, such as RealPresence Desktop, RealPresence
Mobile, RealPresence Group Series systems, and RealPresence Immersive Studio systems.
If you want to dynamically manage RealPresence Debut systems, you must use zero-touch provisioning.
See Using Zero-Touch Provisioning.
Define Endpoint Naming Schemes
The RealPresence Resource Manager allows administrators to configure their E.164 alias, system naming
schemes and SIP URIs for endpoints that are dynamically managed.
If you choose to provision H.323 settings through a network provisioning profile, you can also define the
E.164 number and system naming scheme used for endpoints. You can also auto-generate SIP URIs for
dynamically managed endpoints.
For more information, see Dynamically Managing Endpoint Naming Schemes.
Create Video Endpoint Provisioning Profiles
Dynamic provisioning enables endpoints to poll the RealPresence Resource Manager automatically to get
provisioning updates (configuration settings) on a dynamic basis. The provisioning profiles the endpoint
receives are based provisioning rules you define.
When you dynamically manage endpoints (have the endpoint use the RealPresence Resource Manager as
its provisioning server), you can automatically configure them by using provisioning profiles.
You need to modify and create three types of video endpoint provisioning profiles:
● Network Provisioning profiles define Network settings such as security, quality of service, and
gatekeeper address, SIP server address, and so on, see Network Provisioning Profiles.
● Admin Config Provisioning profiles define endpoint administrative settings such as maximum and
preferred call speeds for H.323 settings, calendaring settings, Microsoft Lync settings, and so on, see
Admin Config Provisioning Profiles.
● Bundled Provisioning profiles allow you to control system settings that affect user experience, see
Using Bundled Provisioning Profiles.
Create Provisioning Rules
You can create rules that include conditions that need to be met before the RealPresence Resource
Manage system sends a provisioning profile to an endpoint. You can also prioritize these rules so that
certain provisioning profiles get applied first.
For more information about provisioning rules, see Creating Dynamic Provisioning Rules.
Polycom, Inc.
253
Understanding Dynamic Endpoint Management
Create Access Control Lists
Access Control Lists provide an additional level of endpoint provisioning security when you dynamically
manage endpoints. These lists allow you to group endpoints into “white lists” that can be dynamically
provisioned. This is particular useful when controlling Polycom’s soft endpoints such as CMA Desktop and
RealPresence Mobile which use the provisioning credentials to authenticate with your video network. With
Polycom RealPresence Mobile clients, you can also control access according to model (for example,
RealPresence Mobile for the iPad).
See Using Access Control Lists.
Create Software Updates
You need to create software updates to automatically send to endpoints. See Dynamically Updating
Endpoint and Peripheral Software for more information.
Selective Provisioning of Dynamically Managed
RealPresence Group Series Systems
By default, each setting within the provisioning profile that you use is provisioned to the endpoint. The
settings within the profile overwrite any settings that were set locally for the endpoint. In addition, some
settings become read-only on the endpoint.
However, when you dynamically manage a RealPresence Group Series system, you can choose to
selectively provision fields within the provisioning profile. This means you can unmark fields within the profile
that you do not want to set with the dynamic provisioning profile. For example, you may want the endpoint
administrator to locally configure the language or time zone of the endpoint.
When you define a provisioning profile, you can choose to selectively apply fields within the profile when it
is used for a RealPresence Group Series system. Choosing this option does not affect other dynamically
managed endpoints that may use the same profile.
Dynamically Manage RealPresence Immersive Studio
Systems
A RealPresence Immersive Studio system contains multiple endpoints (codecs). When the RealPresence
Resource Manager system dynamically manages (required) these devices, they display as a group of three
codecs that following a specific numbered naming convention that helps specify the total number of codecs
included in the system. This is in addition to any system name you have configured. For example, the three
RealPresence Group Series in an RealPresence Immersive Studio system named
wangle1PCTCDMAQAITP could display in the RealPresence Resource Manager system screens and
reports with the following names:
wangle1PCTCDMAQAITP_3_1
wangle1PCTCDMAQAITP_3_2
wangle1PCTCDMAQAITP_3_3
In the Endpoint > Monitor View screen, dynamically managed RealPresence Immersive Studio systems
display as expandable icons.
Polycom, Inc.
254
Understanding Dynamic Endpoint Management
The RealPresence Resource Manager system also provisions settings as applying to a single system. You
can only provision the primary codec (the device designated as 1); the RealPresence Resource Manager
system automatically propagates any changes to the other devices in the ITP system.
Stop Dynamic Management of an Endpoint
If you want to stop dynamically managing an endpoint, you must first disable the provisioning service
settings on the endpoint.
You can stop dynamic management of the following Polycom endpoints: RealPresence Group Series and
RealPresence Immersive Studio systems.
To stop dynamic management for a Polycom HDX system, please see the Polycom HDX documentation.
To stop dynamically managing an endpoint:
1 From the endpoint’s web interface, navigate to the Provisioning Service settings and cancel the
Enable Provisioning check box.
2 From the RealPresence Resource Manager system, navigate to Endpoint > Monitor View,
highlight the endpoint and click
.
Polycom, Inc.
255
Dynamically Updating Endpoint and
Peripheral Software
The Polycom RealPresence Resource Manager system’s software update feature, which requires a
software update profile for the endpoint type and model, allows an administrator to upgrade the software on
one or more endpoints with a standard software package. This eliminates the need to upgrade each
endpoint individually.
The RealPresence Resource Manager system supports two exclusive software update processes: dynamic
and scheduled. Dynamic and scheduled software update are exclusive endpoint management scenarios.
Endpoints enabled for dynamic software update should not be scheduled for software updates through the
system.
Polycom recommends that all endpoints in a region (that is, a gatekeeper zone) be managed by a
single management system.
This section describes how to use RealPresence Resource Manager system to dynamically update the
software on Polycom endpoints when a new software package is available using a policy you define. It
includes the following topics:
● Software Update Considerations for Multi-Tenancy
● Software Update Considerations for RealPresence Desktop
● Creating Dynamic Software Updates for Endpoints
● Using Dynamic Software Updates
● Set up a Trial Dynamic Software Update
● Populate Domain Name for Software Endpoints
● Enable Software Endpoints to Save Password
● Dynamic Software Updates for Peripherals
Software Update Considerations for Multi-Tenancy
Within a multi-tenancy environment, area administrators are not allowed to create software updates or set
up maintenance windows for dynamic software updates. However, they are allowed to schedule software
updates that have already been uploaded by a user with the administrator role.
Software update images are also not area-aware, which means that users with area administrator roles see
all software updates on the system, not just those for their area. As a best practice, the system administrator
should either name the software update appropriately or add information to the description field of the
update so that area administrators know which updates to use for their area.
Polycom, Inc.
256
Dynamically Updating Endpoint and Peripheral Software
Software Update Considerations for RealPresence
Desktop
When you upgrade RealPresence Desktop clients, Polycom recommends that you temporarily configure the
RealPresence Resource Manager system to reclaim soft endpoint licenses in a very short time (one day).
As soon as the client’s license is reclaimed and re-distributed, the RealPresence Resource Manager system
can accurately track the upgraded endpoints.
When you upgrade the RealPresence Desktop and RealPresence Mobile clients, you may see erroneous
endpoint reports in the RealPresence Resource Manager system that show duplicate RealPresence
Desktop endpoints. In addition, these erroneous duplicate endpoints will each consume a RealPresence
Desktop license.
After upgrading your RealPresence Desktop and RealPresence Mobile clients, you can reconfigure the
license reclamation to the value you need. The default is 30 days.
Creating Dynamic Software Updates for Endpoints
To implement a dynamic software update, you must first create respective software updates for your
endpoints.
Only users with the administrator role can create dynamic software updates. To create software updates for
endpoints:
1 List the Serial Numbers for the Endpoints to be Updated.
2 Download the Required Software Package.
3 Request Upgrade Activation Keys.
4 Upload the Software Update for Dynamic Software Updates.
For more information on software update profiles, see View Software Update Details for an Endpoint
on page 264.
The dynamic software update feature is only available for these endpoint types:
• Polycom HDX system endpoints deployed in dynamic management mode
• Polycom RealPresence Group Series deployed in dynamic management mode
• Polycom RealPresence Immersive Studio systems
• Polycom CMA Desktop systems (Windows and Mac)
• RealPresence Desktop systems (Windows and Mac)
• Polycom VVX systems
• Polycom Touch Controls for both HDX and Group Series when dynamically managed
• Polycom RealPresence Debut
• Polycom RealPresence Centro™
• Polycom RealPresence OTX® Studio
Polycom provides default dynamic software update profiles for both CMA Desktop and RealPresence
Desktop clients. Default software update profiles are not available for other endpoint systems.
Polycom, Inc.
257
Dynamically Updating Endpoint and Peripheral Software
List the Serial Numbers for the Endpoints to be
Updated
You need to create a .txt file containing a list of the endpoint serial numbers to be updated.
To list the serial numbers for the endpoints to be updated:
1 Go to Endpoint > Dynamic Management > Upload Software Updates.
2 Select the endpoint type for which to get serial numbers.
3 Click Get Serial Numbers from the More menu.
The Endpoint Serial Number List appears listing the endpoints of the selected type and model that
are eligible for software updates.
Field
Description
Name
The name assigned to the endpoint system
IP Address
The IP address assigned to the endpoint.
Version
The current software version installed on the endpoint.
Site
The site to which the endpoint belongs.
Note
When areas are enabled on your system, this field shows a value of
Restricted if you do not have permission to manage the area to which
the site is assigned.
Area
4 As needed, click
(Available only when Areas are enabled.) The area with which the
endpoint is associated.
Users can only view area information for the areas to which they belong
or have been assigned to manage.
to customize the endpoint list.
5 Select the specific endpoints to be updated.
6 Click Get Serial Numbers from the More menu.
The serial number(s) appear in the text box on the page.
7 Create a .txt file containing the serial number(s).
a Copy and paste the serial numbers from the endpoint serial number list to a .txt file that you can
submit to the Polycom Product Activation site. Put one serial number per line as shown in the
following example.
82071007E1DACD
82070407E010CD
820418048078B2
82040903E00FB0
b Save the .txt file.
Polycom, Inc.
258
Dynamically Updating Endpoint and Peripheral Software
c Return to the endpoint serial number list and click Close.
The Software Updates list reappears.
8 Repeat steps 2 through 7 for the each endpoint or set of endpoints to be updated. You may include
all of the serial numbers for all of the different endpoint types in the same .txt file.
9 Click Close.
The Software Updates list reappears.
Download the Required Software Package
You need to download the required software update.
To download the software package required to update the endpoints:
1 On your local system, create a directory to which to save the software package (if one does not
already exist).
2 For Polycom endpoints:
a Open a web browser and go to http://support.polycom.com.
b In the Downloads section, select the Product and Category for the required software package.
c Select the software package and save it to the directory created in step 1.
d Repeat steps a through c for each endpoint type to be updated. Note that the software package
may contain the software for different models of the same endpoint type.
3 For third-party endpoints, follow the company’s recommended procedure for downloading a
software package. Save it to the directory created in step 1.
Request Upgrade Activation Keys
You need to request software upgrade activation keys. And you can review your key history at
http://support.polycom.com.
To request upgrade activation keys:
1 Go to http://support.polycom.com.
2 Log in or Register for An Account.
3 Select Product Activation.
4 In the Software Upgrade Key Code section, click Retrieve Software KeyCode.
5 When upgrading a single endpoint:
a Enter the serial number of the endpoint to be updated into the Serial Number field of the Single
Upgrade Key Code section.
b Enter the version number to which you are upgrading and click Retrieve.
c The key code is returned on the screen.
d Record the key code and create a .txt file with the Serial Number - Key Code combination to be
updated.
e Close the Product Activation screens.
Polycom, Inc.
259
Dynamically Updating Endpoint and Peripheral Software
6 When updating multiple endpoints from a prepared .txt file (step a):
a In the Multiple Upgrade KeyCode section, click Add Attachment.
b Browse to the location of the .txt file you created and click Upload.
c A file containing the Serial Number - Key Code combinations will be emailed to the specified email
account.
d When you receive the .txt file, save it to your local system.
Do not modify or rename the file that Polycom sends.
7 Close the Product Activation screens.
Upload the Software Update for Dynamic Software
Updates
Polycom recommends you to do software updates using the split packages available on Polycom’s support
website to reduce system resource consuming.
To upload the software package and create an software update:
1 Go to Endpoint > Dynamic Management > Upload Software Updates.
2 Select an endpoint type to update.
3 Click
.
4 In the Upload Software Update dialog, select an endpoint type:
 HDX Series
 Group Series
 CMA Desktop (PC)
 CMA Desktop (Mac OS)
 VVX
 HDX Touch Control
 Group Series Touch Control
 ITP
 RealPresence Desktop (PC)
 RealPresence Desktop (Mac OS)
 RealPresence Touch
 RealPresence Centro
 CX
5 If an activation key code is required to activate the software update, in the Software Update Key
File field, browse to the .txt key file (received in Request Upgrade Activation Keys).
Polycom, Inc.
260
Dynamically Updating Endpoint and Peripheral Software
The key is generated from the endpoint serial number and version number, and Polycom sends it as a
text (.txt) file to the customer when new software is available.
6 In the Software Update File field, browse to the software update file you downloaded.
7 Enter a meaningful description that will help other users to understand the purpose of the software
update.
8 Click OK.
A software update profile for the endpoint type and model type is created.
Using Dynamic Software Updates
Dynamic software updates, which controls the endpoint’s software version level, is tied to the endpoint type
and the policy you define. Currently, the dynamic software update feature is only available for these endpoint
types.
● Polycom HDX system endpoints that are dynamically managed
● Polycom RealPresence Group Series endpoints that are dynamically managed
● Polycom RealPresence Immersive Studio systems that are dynamically managed
● Polycom CMA Desktop systems (both Windows and Mac)
● RealPresence Desktop systems (both Windows and Mac)
● Polycom VVX systems
● Polycom Touch Controls that are dynamically managed
● Polycom RealPresence Group Series Touch Controls
● Polycom RealPresence Debut
● Polycom RealPresence Centro
● Polycom RealPresence OTX Studio
In dynamic management mode, when an endpoint starts up at designated intervals thereafter, it
automatically polls the RealPresence Resource Manager system for a newer software update package. If
a software update is necessary, the package is sent in XML format over a secure HTTPS connection.
Endpoints do not poll for software update packages if they are in a call. They restart polling after the call
ends.
This section describes how to use the RealPresence Resource Manager system to dynamically update the
software on Polycom endpoints when a new software package is available. It includes the following topics:
● Set a Dynamic Software Update Policy
● View Dynamic Software Update Status
● View Software Update Details for an Endpoint
● View Dynamic Software Update Packages
● Set Maintenance Window for Dynamic Software Updates
Polycom, Inc.
261
Dynamically Updating Endpoint and Peripheral Software
Set a Dynamic Software Update Policy
After creating a dynamic software update, you can use the Version to use and Allow this version or
newer selections to manage the roll out of a software update package. These selections also allow you to
manage the release of multiple software packages for the same endpoint type.
Here’s how it works: All endpoints have a current version of software. To automatically overwrite that current
software with a different software version on all dynamically managed endpoint systems:
1 Create a new dynamic software update.
2 Activate the roll out, you change the Version to use selection from the current value to the new
version number and Update the page.
The next time a dynamically managed endpoint polls the RealPresence Resource Manager system, it will
detect that it has a different software version than the Version to use selection, so it will automatically
download and install the identified software update package. Use this method to force users to use a specific
software version.
Until the Version to use selection is enabled, the dynamic software update is not activated.
If you also enable the Allow this version or newer selection, anytime you upload a newer version of
software into a dynamic software update that update will be automatically installed on all dynamically
managed endpoint systems.
Some important things to note about software versions:
● Newer software is identified by the version number. If the Allow this version or newer selection is
enabled, when a dynamically managed endpoint polls the RealPresence Resource Manager system,
the system will compare the current software version number with the packaged software version
numbers. The system will send the software package with the highest version number to the
endpoint.
● You can also use the Version to use selection to roll endpoints back to older software versions. If
you change the Version to use selection to an older software version and clear the Allow this
version or newer selection, the RealPresence Resource Manager system will send the specifically
identified software package to the endpoint even if it is an older version.
To roll back a Polycom CMA Desktop or RealPresence Desktop client to an older version, you must
first remove the existing Polycom CMA Desktop client via the Windows Add or Remove Software
selection. Then you can install the older software package.
To set a dynamic software update policy for an endpoint type:
1 Go to Endpoint > Dynamic Management > Upload Software Update.
2 Select the tab for the endpoint type of interest.
3 Choose one of these policies:
 To specify an area to which to apply the update, use the Select Area drop-down to select the area
to apply the policy.
This feature is only available when areas are enabled and you manage more than one area.
Polycom, Inc.
262
Dynamically Updating Endpoint and Peripheral Software
 To specify a minimum version of dynamic software update package, make that version the
Version to use and select Allow this version or newer.
 To require a specific version of dynamic software update package, make that version the Version
to use and clear Allow this version or newer.
 To turn off dynamic software update for an endpoint type, change the Version to use value to
(none).
4 Click Update.
View Dynamic Software Update Status
You can view the list of endpoints that have registered to the system for dynamic software updates.
To view the list of endpoints registered to the system for dynamic updates:
1 Navigate to Endpoint > Dynamic Management > Software Update Status menu to view the list of
endpoints that have registered to the system for dynamic software updates.
2 Click
to use for the list. Filter choices for this view include:
 Endpoint Type—Filters the list by endpoint type.
 Endpoint Name—Searches the list by the endpoint’s system name.
 IP Address—Searches the endpoint list by IP address.
 ISDN Video Number—Searches the endpoint list by ISDN video number.
 Dial String— Searches the endpoint list by dial string (SIP, H.323, or ISDN).
 Site—Searches the endpoint list by site location.
 Area—Filters the endpoint list by area. This filter is only available when areas are enabled and
when the user manages more than one area.
3 Use the Items per page drop-down to customize the number of endpoints included per page.
The endpoint list includes the following information:
Field
Description
Status
The status of the endpoint’s last software update. Possible values include:
• Success
• Failed
• Clear
• Timed Out
• Skipped (only applied to CMA Desktop and RealPresence Desktop clients)
Endpoint Name
The system name of the endpoint.
Polycom, Inc.
263
Dynamically Updating Endpoint and Peripheral Software
Field
Description
Type
The type of endpoint. Dynamic software update is only available for these
endpoint types:
• HDX systems (when dynamically managed)
• RealPresence Group Series (when dynamically managed)
• RealPresence Immersive Studio systems (when dynamically managed)
• CMA Desktop
• RealPresence Desktop
• Polycom VVX
IP Address
The IP address assigned to the endpoint.
Current Version
The current software version that the endpoint is using.
Area
(Available only when Areas are enabled.) The area with which the endpoint is
associated.
You can only view area information for the areas you have been assigned to
manage. If you do not manage more than one area, this column is not
displayed.
View Software Update Details for an Endpoint
Users with the Device Administrator, Administrator or the Area Administrator role can view details about
dynamic software updates made to endpoints.
To view detailed information for endpoints that are eligible for dynamic software updates:
1 Go to Endpoint > Dynamic Management > Software Update Status.
The Software Update Status page appears.
2 As needed, click
to customize the endpoint list. Filter choices include Endpoint Type,
Endpoint Name, IP Address, ISDN Video Number, Dial String, Site and Area.
3 Select the endpoint of interest.
4 Click
and expand the Software Update Details section.
The endpoint list in the Dynamic Software Details pane has the following information.
Polycom, Inc.
264
Dynamically Updating Endpoint and Peripheral Software
Field
Description
Software Update
Status
The device’s software update status. Possible values include:
• Clear. A software update has not been done.
• Pending. A software update has been scheduled and is pending. The device may be offline
or in a call.
• In Progress. The software update is in progress.
• Success. A software update has completed successfully.
• Failed. A software update could not be performed.
Last Attempt
Date/Time
The date and time, in the default format of yyyy-mm-dd hh:mm:ss, of the last software
update message exchanged with the device.
Note
Polycom CMA Desktop systems and RealPresence Desktop clients are updated at the start of
each session.
Field
Description
Scheduled
For dynamic updates, this value is N/A.
For scheduled updates, the date and time, in the default format of yyyy-mm-dd
hh:mm, when the device software is schedule to be updated.
This field is blank if the device is not scheduled for provisioning.
Failure Reason
A text description of the reason the software update failed. Causes for failure may
include:
• The software update file location does not exist.
• A password for the device is set in the video endpoint system, and you must enter
it in RealPresence Resource Manager system.
• A network error has occurred.
• The update has timed out.
• An internal error occurred on the device, and you must reboot it.
• A profile has not been configured.
• An endpoint is offline.
• An incorrect activation key is in the key file.
• An unknown error has occurred. Reboot the device
Log Message
A read-only text box that contains the log message text recorded during the
execution of the software update.
Note that there are no log messages displayed for dynamically managed endpoints.
For more information, see View Software Update Details.
View Dynamic Software Update Packages
You can view a list of software updates available to dynamically managed endpoints and the update policies.
Polycom, Inc.
265
Dynamically Updating Endpoint and Peripheral Software
To view the list of dynamic software update packages:
1 Go to Endpoint > Dynamic Management > Upload Software Update.
The Dynamic Software Policies page appears and the uploaded software update packages are
displayed. The Dynamic Software Updates page includes this information.
Field
Description
Select Area
Enables you to specify an area to which to apply the update.
This option is only available when areas are enabled and for areas that
the user is allowed to manage.
Endpoint Type
The type of endpoint system. You can use dynamic software updates
for the following Polycom endpoints and peripherals:
• HDX Series
• RealPresence Group Series
• RealPresence Centro
• RealPresence Debut
• RealPresence Immersive Studio systems
• CMA Desktop (PC and Mac OS)
• RealPresence Desktop (PC and Mac OS)
• VVX
• Polycom HDX Touch Control
• Polycom Touch Control
• RealPresence Touch Control
Version to use
Displays the default dynamic software update profile to be used for the
endpoint type and model.
Allow this version or newer
When checked, indicates that when a newer dynamic software update
package for the endpoint type and model is added, that package should
be used as the default package.
Version
The version of the software package associated with the dynamic
software update package.
Description
The meaningful name given to the dynamic software update package
when it was created.
Uploaded
The date and time when the dynamic software update package was
created.
Trial Group
The trial group assigned to the software update package, if applicable.
2 To view the dynamic software update packages for other endpoints and peripherals, select the
appropriate item from the Device Type drop-down list: HDX, Group Series, CMA Desktop (PC or
Mac OS), VVX or HDX Touch Control, Group Series Touch Control, and RealPresence Desktop
(PC or Mac OS).
Polycom, Inc.
266
Dynamically Updating Endpoint and Peripheral Software
Set Maintenance Window for Dynamic Software
Updates
You can restrict dynamic software updates of dynamically managed endpoint systems to a scheduled
maintenance window.
Typically, dynamic software updates occur as specified by the Software Update Polling Interval that is
provisioned with the network provisioning profile for the endpoint.
Enabling the maintenance window feature in the RealPresence Resource Manager system overrides the
Software Update Polling Interval. The RealPresence Resource Manager system provisions the
maintenance window to the endpoints, and the endpoints hold their dynamic software update requests until
the maintenance window starts.
Some notes about this feature:
● It applies to dynamically managed HDX and RealPresence Group Series only.
● To avoid dynamically updating the software on all HDX or RealPresence Group Series at the start of
the maintenance window, the systems randomize their dynamic software update requests.
To restrict dynamic software updates to a scheduled maintenance window:
1 Go to Endpoint Management > Dynamic Management > Upload Software Update.
2 Select the appropriate device type: HDX or Group Series.
3 Click Maintenance Window from the More menu.
4 In the Maintenance Window dialog, click Enable Maintenance Window and set a maintenance
window Start Time and either an End Time or Duration.
Set the maintenance window start time to the endpoint’s system local time, not the RealPresence
Resource Manager system local time. For example, if you set the maintenance window start time to
3am, the maintenance window for each HDX system will start at 3am local time. Therefore, the
maintenance window for HDX systems in Buffalo, NY will start at 3am EST; the maintenance window
for HDX systems in Denver, CO will start at 3am MST; and the maintenance window for HDX systems
in San Francisco, CA will start at 3am PST.
5 Click OK.
Set up a Trial Dynamic Software Update
Setting up a trial of a software update requires the user to create a software update. Only users with the
administrator role can do this.
To trial a software update package:
1 Get the things you need to create the package. You must have the administrator role to complete
the tasks in this step:
a List the Serial Numbers for the Endpoints to be Updated.
b Download the Required Software Package.
c Request Upgrade Activation Keys.
2 Set up testing. Complete these tasks:
Polycom, Inc.
267
Dynamically Updating Endpoint and Peripheral Software
a Create a Local Trial Group.
b Upload the Software Update for Dynamic Software Updates. For more information on software
update packages, see View Software Update Details for an Endpoint.
c Create a Trial Software Update Package.
3 Once your testing of the trial software package is complete, do one of these tasks:
 Promote the Trial Software Update Package to Production
 Delete the Trial Software Update Package.
Create a Local Trial Group
To trial a software update with a specific group of local and/or enterprise users, create a local group that
includes these users, as described in Add a Local Group on page 398. The people in this group will receive
the trial software update package when their endpoint goes through its normal, automated software update
process.
•
•
You can use an existing enterprise group as a trial group, but you will not be allowed to change the
enterprise group in any way.
If the trial software group is a parent group with children, all of its children will inherit trial
permissions.
Create a Trial Software Update Package
You need to upload the software packages before you create a trial software update package.
To create a trial dynamic software update package:
1 To trial the software with the group created previously, select Trial Software and from the Select
Trial Group menu, select the trial group created in Create a Local Trial Group on page 268.
2 Click OK.
A trial dynamic software update package for the endpoint type and model type appears in the
Dynamic Software Update list. You can tell it is a trial package, because the Trial Group column
includes your entry.
The next time members of the trial group log into the system, their systems will be upgraded with the
trial software package.
Promote the Trial Software Update Package to
Production
If you determine that the trial software update package is acceptable for production, you can then promote
it to production.
To promote a trial software update package to production:
1 Go to Endpoint> Dynamic Management > Upload Software Updates.
2 Select theendpoint type to update.
Polycom, Inc.
268
Dynamically Updating Endpoint and Peripheral Software
3 If areas are enabled, use the Select Area drop-down list to choose the area to which to promote the
update.
This drop-down list is only available if you manage more than one area.
4 Select the software update package of interest and click Promote to Production.
5 Click Yes to confirm the promotion.
The package becomes a production dynamic software update package.
Delete the Trial Software Update Package
If you determine that the trial software update package is unacceptable for production, you can delete it.
To delete a trial software update package:
1 Go to Endpoint > Dynamic Management > Upload Software Updates.
2 Select the endpoint type to update.
3 Select the software update package you want to delete and click
.
4 Click Yes to confirm the deletion.
The package is removed from the Dynamic Software Updates list.
5 To return your trial group to the last production version of software, clear the Allow this version or
newer option and click Update.
6 When all endpoints are back to the last production version of software, reset your dynamic software
update policy. See Set a Dynamic Software Update Policy.
Populate Domain Name for Software Endpoints
If you use only one domain, you can set the domain name in the RealPresence Resource Manager, which
will automatically populate the domain name for your software endpoints. Currently only RealPresence
Mobile endpoints are supported.
To set the domain name:
1 Go to Endpoint > Dynamic Management > Endpoint Management Settings > Default Domain
Name Setting.
2 Select the check box of Set the default domain name for Enterprise user login from software
endpoint.
3 In the Default Domain Name box, specify the domain name.
4 Click Update.
Enable Software Endpoints to Save Password
You can make the software endpoints save the passwords with the help of a provisioning attribute. Both
RealPresence Mobile endpoints and RealPresence Desktop endpoints support the setting.
By default, the setting is disabled.
Polycom, Inc.
269
Dynamically Updating Endpoint and Peripheral Software
To save the password:
1 Go to Endpoint > Dynamic Management > Endpoint Management Settings > Remember
Password Options.
2 Select the check box of Enable “Remember Password” for the software endpoints.
3 Click Update.
Dynamic Software Updates for Peripherals
You can update the platform (operating system) and applications (if applicable) for peripherals connected
to endpoints. Peripheral software updates can be in any of the following states:
● Production - The software update is configured for one or more groups that are using the software
in production.
● Trial - The software update is configured for one or more groups that are trialing the software.
● Both - The software update is configured for one or more groups that are trialing the software and for
one or groups are using the software in production.
For peripherals that permit software updates from the RealPresence Resource Manager system, you can
download the updates from http://support.polycom.com and make them available from the
RealPresence Resource Manager system web server. You also configure which updates are for trial or
production use. The following topics describe software updates for peripherals:
● View Software Updates for Polycom Touch Controls
● Upload Peripheral Software Updates to the RealPresence Resource Manager System
● Configure Peripheral Updates for Production
● Configure Peripheral Updates for Trial
View Software Updates for Polycom Touch Controls
You can view a list of the software updates available for Polycom Touch Controls. This includes status
information, the software version, and so on.
To view software updates for peripherals:
1 Go to Endpoint > Dynamic Management > Upload Software Updates.
2 Select the HDX Touch Control or Group Series Touch Control tab.
The tab includes this information.
Field
Description
Select Area
Enables you to specify an area to which to apply the update.
Production URL
URL where the peripheral can access software updates configured for
production use. The URL consists of the IP dress of the RealPresence
Resource Manager system plus /repo.
Polycom, Inc.
270
Dynamically Updating Endpoint and Peripheral Software
Field
Description
Trial URL
URL where the peripheral can access software updates configured for
trial use. The URL consists of the IP dress of the RealPresence
Resource Manager system plus /repotrial.
Package Name
Displays the name of the software update package. Updates listed as
platform are updates to the peripheral’s operating system. Other
updates are for specific applications.
Description
The meaningful name given to the software update package when it
was created
Version
The version of the software package
Status
The status of the software update. Possible values are:
• None - The software update has not been configured for production
or trial.
• Production - The software update is configured for production. It is
available only from the Production URL.
• Trial - The software update is configured for trial. It is available only
from the Trial URL.
• Both - The software update is configured for both production and
trial. It is available from both the Production URL and the Trial URL.
Uploaded
The date and time when the software update package was uploaded
Upload Peripheral Software Updates to the
RealPresence Resource Manager System
After you download the software updates from http://support.polycom.com and save them on your hard
drive, you can upload them to the RealPresence Resource Manager system web server.
To upload software updates to the RealPresence Resource Manager system:
1 Go to Endpoint > Dynamic Management > Upload Software Updates.
2 Select the endpoint type for the peripheral.
3 Click
.
4 In the Select File to Upload dialog box, navigate to and select the software update that you saved
to your hard drive.
5 Click Open.
The update is added to the list on the peripheral tab.
If this is the first update for the platform or an application, the update is automatically configured for
production.
Polycom, Inc.
271
Dynamically Updating Endpoint and Peripheral Software
Configure Peripheral Updates for Production
You need to configure software updates for peripherals to be used in production.
To configure software updates for production:
1 Go to Endpoint > Dynamic Management > Upload Software Updates.
2 Select the RealPresence Touch, HDX Touch Control, or Group Series Touch Control as the
peripheral endpoint type.
3 Click More > Configure Production.
The Configure Production dialog box includes the following information.
Field
Description
Configure Platform
Platform Description
The meaningful name given to the platform software update package
when it was created
Status
The current status of the platform software update. Possible values are:
• None - The software update has not been configured as production
or trial.
• Production - The software update is configured as production. It is
available only from the Production URL.
• Trial - The software update is configured as trial. It is available only
from the Trial URL.
• Both - The software update is configured as both production and trial.
It is available from both the Production URL and the Trial URL.
Configure Application
Application Description
The meaningful name given to the application software update package
when it was created
Platform Compatible
Column title shows the version of the currently selected platform. Use
the drop-down list to select available application versions that match the
platform version.
Status
The current status of the application software update. Possible values
are:
• None - The software update has not been configured as production
or trial.
• Production - The software update is configured as production. It is
available only from the Production URL.
• Trial - The software update is configured as trial. It is available only
from the Trial URL.
• Both - The software update is configured as both production and trial.
It is available from both the Production URL and the Trial URL.
4 From the Configure Platform section, select the platform version to configure for production.
You can select only one platform version for production.
Polycom, Inc.
272
Dynamically Updating Endpoint and Peripheral Software
5 Click Configure Application.
6 For each application, select the version to configure for production from the Platform Compatible
drop-down list.
The version selected must be compatible with the platform version listed in the column heading. If the
application is not selected (no check mark), the application will not be configured for production.
7 Click OK.
From the peripheral itself, the configured software updates are now available using the Production
URL.
Configure Peripheral Updates for Trial
You need to configure the software updates to be used for the trial.
To configure software updates for trial:
1 Go to Endpoint > Dynamic Management > Upload Software Updates.
2 Select the endpoint type for the peripheral.
3 Click More > Configure Trial.
The Configure Trial dialog box includes the following information.
Field
Description
Configure Platform
Platform Description
The meaningful name given to the platform software update package
when it was created
Status
The current status of the platform software update. Possible values are:
• None - The software update has not been configured as production
or trial.
• Production - The software update is configured as production. It is
available only from the Production URL.
• Trial - The software update is configured as trial. It is available only
from the Trial URL.
• Both - The software update is configured as both production and
trial. It is available from both the Production URL and the Trial URL.
Configure Application
Application Description
Polycom, Inc.
The meaningful name given to the application software update package
when it was created
273
Dynamically Updating Endpoint and Peripheral Software
Field
Description
Platform Compatible
Column title shows the version of the currently selected platform. Use
the drop-down list to select available application versions that match
the platform version.
Status
The current status of the application software update. Possible values
are:
• None - The software update has not been configured as production
or trial.
• Production - The software update is configured as production. It is
available only from the Production URL.
• Trial - The software update is configured as trial. It is available only
from the Trial URL.
• Both - The software update is configured as both production and
trial. It is available from both the Production URL and the Trial URL.
4 From the Configure Platform section, select the platform version to configure for trial.
You can select only one platform version for trial.
5 Click Configure Application.
6 For each application, select the version to configure for trial from the Platform Compatible
drop-down list.
The version selected must be compatible with the platform version listed in the column heading. If the
application is not selected (no check mark), the application will not be configured for trial.
7 Click OK.
From the peripheral itself, the configured software updates are now available using the Trial URL.
Polycom, Inc.
274
Using Dynamic Provisioning Profiles
The Polycom RealPresence Resource Manager system enables you to use provisioning profiles and
provisioning rules as a way to dynamically manage endpoint settings.
If your deployment includes a RealPresence Access Director system that you want to dynamically
manage, you must create a RealPresence Access Director Server Provisioning Profile. For more
information, see Dynamically Managing a RealPresence Access Director System.
This section describes how to set up video endpoint provisioning profiles within the RealPresence Resource
Manager system. It includes these topics:
● Set up Dynamic Provisioning Profiles
● Selective Provisioning of Dynamically Managed RealPresence Group Systems
● Working with Provisioning Profiles
● Network Provisioning Profiles
● Admin Config Provisioning Profiles
Set up Dynamic Provisioning Profiles
When you dynamically manage endpoints (have the endpoint use the RealPresence Resource Manager as
its provisioning server), you can automatically configure them by using provisioning profiles.
Dynamic provisioning profiles are applied through a rule-based paradigm. This change makes provisioning
profiles more flexible and provides the administrator more control over when they are applied.
Dynamic provisioning now consists of following steps:
1 Create a dynamic provisioning profile.
2 Create one or more provisioning rules.
3 Associate a provisioning profile with a rule.
Types of Dynamic Endpoint Provisioning Profiles
The RealPresence Resource Manager provides three types of provisioning profiles for use when you
dynamically manage endpoints.
● Network provisioning profiles define network settings such as security, quality of service, and
gatekeeper address, SIP server address, and so on.
● Admin Config provisioning profiles define endpoint administrative settings such as maximum and
preferred call speeds for H.323 settings, calendaring settings, Microsoft Lync settings, and so on
Polycom, Inc.
275
Using Dynamic Provisioning Profiles
● Bundled provisioning profiles allow you to configure endpoint system settings according to
endpoint model and software version.
Dynamic
Provisioning Profile
Summary of Provisioned Settings:
How applied:
Network provisioning profile
Network settings such as security,
quality of service, and gatekeeper
address, SIP server address, and so on.
Applied according to the provisioning
rules you define.
Admin Config provisioning
profile
Maximum and preferred call speeds for
H.323 settings, calendaring settings,
Microsoft Lync settings, and so on.
Applied according to the provisioning
rules you define.
Bundled provisioning profile
Home screen settings related to user
experience, monitor display and camera
settings, password format settings and
so on.
Applied according to model and
software version of the particular
endpoint.
Selective Provisioning of Dynamically Managed
RealPresence Group Systems
By default, each setting within the provisioning profile that you use is provisioned to the endpoint. The
settings within the profile overwrite any settings that were set locally for the endpoint. In addition, some
settings become read-only on the endpoint.
However, when you dynamically manage a RealPresence Group Series system, you can choose to
selectively provision fields within the provisioning profile. This means you can unmark fields within the profile
that you do not want to set with the dynamic provisioning profile. For example, you may want the endpoint
administrator to locally configure the language or time zone of the endpoint.
When you define a provisioning profile, you can choose to selectively apply fields within the profile when it
is used for a RealPresence Group Series system. Choosing this option does not affect other dynamically
managed endpoints that may use the same profile.
Working with Provisioning Profiles
Navigate to Endpoint > Dynamic Management > Provisioning Profiles to work with both Network and
Admin Config provisioning profiles.
See Using Bundled Provisioning Profiles for details about working with bundled provisioning profiles.
This section describes the following tasks:
● Create a New Provisioning Profile
● Edit a Provisioning Profile
● Reset a Default Provisioning Profile
● Edit a Default Provisioning Profile
● Reset a Provisioning Profile
● Clone a Provisioning Profile
Polycom, Inc.
276
Using Dynamic Provisioning Profiles
● Delete a Provisioning Profile
For information on how to associate a profile with a provisioning rule, see Creating Dynamic Provisioning
Rules.
Create a New Provisioning Profile
As soon as an endpoint is configured to use the RealPresence Resource Manager for its provisioning
server, it starts polling for provisioning profile updates. So to ensure out-of-box usability, the RealPresence
RealPresence Resource Manager system comes with a default provisioning profiles. These default profiles
cannot be customized with any rule but apply to all video endpoints by default.
You need to create new provisioning profiles to customize endpoint settings in your environment. New
provisioning profiles are based on the default profiles. Any changes you make to the default profiles are not
applied to pre-existing profiles.
Not all of the provisioning parameters apply to all endpoint systems being provisioned. If an endpoint system
does not have a corresponding parameter, it ignores the parameter.
To create a provisioning profile:
1 Go to Endpoint > Dynamic Management > Provisioning Profiles.
2 Click
.
3 In the General Info section of the Add New Profile section, enter a name for the new provisioning
profile.
4 Select a provisioning profile type from the drop-down list.
5 If the profile will be used for RealPresence Group systems, mark the Selectable Provisioning for
Group Series check box.
When this check box is marked, the RealPresence Group systems that use this profile will only be
provisioned with the settings you select. You can select settings by marking the respective check box
next to the setting.
6 As needed, edit the provisioning details.
7 Click OK.
For information about network profiles, see Available Settings for a Network Provisioning Profile.
For information about Admin Config profiles, see Available Settings for Admin Config Provisioning Profiles.
Edit a Provisioning Profile
You can edit a provisioning profile.
To edit a provisioning profile:
1 Go to Endpoint > Dynamic Management > Provisioning Profiles.
2 In the Provisioning Profiles page, select a profile and click
Polycom, Inc.
.
277
Using Dynamic Provisioning Profiles
3 If the profile will be used for RealPresence Group systems, mark the Selectable Provisioning for
Group Series check box.
When this check box is marked, the RealPresence Group systems that use this profile will only be
provisioned with the settings you select. You can select settings by marking the respective check box
next to the setting.
4 As needed, edit the provisioning details.
5 Click OK.
The provisioning profile is updated.
For information about network profiles, see Available Settings for a Network Provisioning Profile.
For information about Admin Config profiles, see Available Settings for Admin Config Provisioning Profiles.
Reset a Default Provisioning Profile
To reset a phone provisioning profile:
1 Navigate to Endpoint > Dynamic Management > Provisioning Profiles.
2 In the Provisioning Profiles page, select a profile and click
.
You cannot change the name of a default provisioning profile.
3 Click OK.
The default provisioning profile is updated.
For details about network profiles, see Available Settings for a Network Provisioning Profile.
For details about Admin Config profiles, see Available Settings for Admin Config Provisioning Profiles.
Edit a Default Provisioning Profile
You can edit a default provisioning profile.
To edit a default provisioning profile:
1 Go to Endpoint > Dynamic Management > Provisioning Profiles.
2 In the Provisioning Profiles page, select a default profile and click Edit.
You may find more implementation details about these fields in the respective system documentation.
3 If the profile will be used for RealPresence Group systems, mark the Selectable Provisioning for
Group Series check box.
When this check box is marked, the RealPresence Group systems that use this profile will only be
provisioned with the settings you select. You can select settings by marking the respective check box
next to the setting.
4 Click OK.
The provisioning profile is updated.
Polycom, Inc.
278
Using Dynamic Provisioning Profiles
For details about network profiles, see Available Settings for a Network Provisioning Profile.
For details about Admin Config profiles, see Available Settings for Admin Config Provisioning Profiles.
For details about RealPresence Access Director profiles, see Available Settings for RealPresence Access
Director Server Provisioning Profile.
Reset a Provisioning Profile
You can reset a provisioning profile you created. When you reset a provisioning profile, its values revert to
the values derived from the default template of the same type.
To reset a provisioning profile:
1 Go to Endpoint > Dynamic Management > Provisioning Profiles.
2 In the Provisioning Profiles page, select a default profile and click Reset.
You may find more implementation details about these fields in the endpoint system documentation.
You cannot change the name of a default provisioning profile.
3 Click OK.
The default provisioning profile is updated.
For details about network profiles, see Available Settings for a Network Provisioning Profile.
For details about Admin Config profiles, see Available Settings for Admin Config Provisioning Profiles.
Clone a Provisioning Profile
You can clone a provisioning profile. This enables you to re-name an existing profile.
To clone a provisioning profile:
1 Go to Endpoint > Dynamic Management > Provisioning Profiles.
2 In the Provisioning Profiles page, select the profile of interest and click Clone.
3 In the Clone Profile dialog, enter a name for the new profile and click Save.
The provisioning profile appears last in the Provisioning Profiles list.
4 As needed, edit the profile.
See Edit a Provisioning Profile.
For information about network profiles, see Available Settings for a Network Provisioning Profile.
For information about Admin Config profiles, see Available Settings for Admin Config Provisioning Profiles.
Delete a Provisioning Profile
You can delete a provisioning profile.
Polycom, Inc.
279
Using Dynamic Provisioning Profiles
To delete a provisioning profile:
1 Go to Endpoint > Dynamic Management > Provisioning Profiles.
2 In the Provisioning Profiles page, select the profile of interest and click Delete.
3 Click Yes to confirm the deletion.
The profile is deleted from the system.
For information about network profiles, see Available Settings for a Network Provisioning Profile.
For information about Admin Config profiles, see Available Settings for Admin Config Provisioning Profiles.
Network Provisioning Profiles
With network provisioning profiles, you can ensure that all dynamically managed endpoints have the optimal
and correct settings respective to their network location. For more information about dynamic endpoint
management, see Understanding Dynamic Endpoint Management.
Network provisioning profiles allow you to provision endpoints with network settings such as security, quality
of service, gatekeeper address, SIP server address, and so on.
As soon as an endpoint is configured to use the RealPresence Resource Manager for its provisioning
server, it starts polling for provisioning profile updates. To ensure out-of-box usability, the RealPresence
Resource Manager system comes with a default Network provisioning Profile. This default profile cannot be
associated with any rule.
You need to create new network provisioning profiles to have rule-based network settings in your video
environment.
For information about how to add a network provisioning profile, see Create a New Provisioning Profile.
Available Settings for a Network Provisioning Profile
Field
For the endpoint systems being provisioned...
General Info
Profile Name
Specify a unique name for the profile
Provisioning Profile
Type
Choose the profile type from the drop-down list.
Selectable
Provisioning for Group
Series
When you mark this check box, you can manually select which settings within the
provisioning profile are sent to a RealPresence Group Series system. Only the selected
settings will be provisioned to RealPresence Group Series systems.
Within the provisioning profile, only the settings that you select are set to the
RealPresence Group Series system. For example, if a provisioning setting is blank but
still checked, the blank value is still be provisioned to the system.
By default, all settings are checked. If you don’t want to provision the setting to the
RealPresence Group Series system, you must uncheck the individual settings.
Date and Time Settings
Country
Polycom, Inc.
Specify the country code for their location.
280
Using Dynamic Provisioning Profiles
Field
For the endpoint systems being provisioned...
Date Format
Specify the date display format.
Auto Adjust for
Daylight Saving Time
Specify whether or not to adjust the endpoint’s system clock for daylight savings time.
Time Format
Specify the time display format.
Time Server
Specify whether to connect to a time server for automatic system time settings.
Select Auto to require that the video endpoint system synchronize with an external time
server that is identified by a network domain controller. Because it is identified by a
network domain controller, you do not need to enter the IP address of the time server.
Select Manual to require that the video endpoint system synchronize with an external
time server that may not be identified by a network domain controller. In this case, you
must also enter the IP address of the time server in the Time Server Address field.
If Time Server is set to Off, or if the Time Server is set to Manual or Auto but the
endpoint system cannot connect to the time server, the date and time must be manually
reset at the endpoint.
Primary Time Server
Address
Specify the address of the primary time server when Time Server is set to Manual.
Secondary Time
Server Address
Specify the address of the secondary time server when Time Server is set to Manual.
Timezone
Specify the time difference between GMT (Greenwich Mean Time) and the endpoint
system’s location.
Firewall Settings
Use Fixed Ports
Specify whether to define the TCP and UDP ports.
• If the firewall is H.323 compatible or the endpoint systems are not behind a firewall,
disable this setting.
• If the firewall is not H.323 compatible, enable this setting. The endpoint systems will
assign a range of ports starting with the TCP and UDP ports you specify. The endpoint
system defaults to a range beginning with port 3230 for both TCP and UDP.
Note
You must open the corresponding ports in the firewall. You must also open the firewall’s
TCP port 1720 to allow H.323 traffic.
Start TCP Port
Lets you specify the beginning value for the range of TCP ports used by the endpoint
systems. The endpoint systems will automatically assign a range of ports starting with the
port you specify.
Note
You must also open the firewall’s TCP port 1720 to allow H.323 traffic.
Start UDP Port
Lets you specify the beginning value for the range of TCP ports used by the endpoint
systems. The endpoint systems will automatically assign a range of ports starting with the
port you specify.
Enable H.460 Firewall
Traversal
Enables the endpoint system to use H.460-based firewall traversal. For more
information, see the Administrator’s Guide for Polycom HDX Systems.
Polycom, Inc.
281
Using Dynamic Provisioning Profiles
Field
For the endpoint systems being provisioned...
NAT Configuration
Specify whether the endpoint systems should determine the NAT Public WAN Address
automatically.
• If the endpoint systems are behind a NAT that allows HTTP traffic, select Auto.
• If the endpoint systems are behind a NAT that does not allow HTTP traffic, select
Manual. Then specify a NAT Public (WAN) Address.
• If the endpoint systems are not behind a NAT or are connected to the IP network
through a virtual private network (VPN), select Off.
NAT Public (WAN)
Address
When NAT Configuration is set to Manual, specify the address that callers from outside
the LAN should use to call the endpoint systems.
NAT is H.323
Compatible
Specify that the endpoint systems are behind a NAT that is capable of translating H.323
traffic.
Address Displayed in
Global Directory
Specify whether to include the endpoint system’s information in the global directory
• Select Private to exclude the endpoint from the global directory
• Select Public to include the endpoint in the global directory
Enable SIP Keep
Alives
When checked, SIP Keep Alive messages are enabled.
H323 Settings
Enable IP H.323
Specify whether to enable IP H.323 calls.
Use Gatekeeper
Select one of the following items:
• Off: Do not use a gatekeeper.
• Auto: The RealPresence Resource Manager system finds an available gatekeeper
automatically.
• Specify: Specify the gatekeeper IP address in the Gatekeeper Address field.
Gatekeeper Address
When Use Gatekeeper is set to Specify, enter the gatekeeper address.
Notes for endpoints that will use a RealPresence Access Director system or
Polycom VBP
If this network provisioning profile is used for endpoints within a site that includes a
RealPresence Access Director system or Polycom VBP system, the gatekeeper IP
address should be the external or subscriber IP address of the RealPresence Access
Director or Polycom VBP system.
Use Gatekeeper for
Multipoint Calls
Specify whether multipoint calls use the endpoint system’s internal multipoint capability or
the Polycom MCU’s Conference on Demand feature. This feature is available only if the
system is registered with a PathNavigator.
SIP Settings
Enable SIP
Specify whether to enable SIP calls and enable the provisioning of SIP settings.
Automatically Discover
SIP Servers
The RealPresence Resource Manager system sends provisioning info telling endpoints
to auto discover SIP servers. The endpoint then performs a DNS query to locate the SIP
server.
Polycom, Inc.
282
Using Dynamic Provisioning Profiles
Field
For the endpoint systems being provisioned...
Proxy Server
Specify the IP address or FQDN of the SIP proxy server for the network. If you leave this
field blank, the registrar server is used.
Notes for endpoints that will use a RealPresence Access Director system
If this network provisioning profile is used for endpoints within a site that includes a
RealPresence Access Director system, the Proxy Server IP address should be the
external or subscriber IP address of the RealPresence Access Director.
Registrar Server
Specify the IP address or FQDN of the SIP registrar server for the network.
• In an Microsoft Office Communications Server 2007 or Microsoft Lync Server 2010
environment, specify the IP address or FQDN of the Office Communications Server or
Lync Server server.
• If registering a remote HDX system with an Office Communications Server Edge
Server or Lync Server Edge Server, use the fully qualified domain name of the access
edge server role.
Notes for endpoints that will use a RealPresence Access Director system
If this network provisioning profile is used for endpoints within a site that includes a
RealPresence Access Director system, the Registrar Server address should be the
external or subscriber IP address of the RealPresence Access Director.
Backup Proxy Server
Specify the IP address or FQDN of a backup SIP proxy server for the network.
Notes for endpoints that will use a RealPresence Access Director system
If this network provisioning profile is used for a endpoints within that includes a
RealPresence Access Director system, the Backup Proxy Server IP address should be
the IP address of the RealPresence Access Director.
Backup Registrar
Server
Specify the IP address or FQDN of a backup SIP registrar server for the network.
Notes for endpoints that will use a RealPresence Access Director system
If this network provisioning profile is used for a site that includes a RealPresence Access
Director system, the Backup Registrar Server IP address should be the IP address of the
RealPresence Access Director.
Transport Protocol
Polycom, Inc.
Indicates the protocol the system uses for SIP signaling. The SIP network infrastructure
determines which protocol is required.
• Auto enables an automatic negotiation of protocols in the following order: TLS, TCP,
UDP. This is the recommended setting for most environments.
• TCP provides reliable transport via TCP for SIP signaling.
• UDP provides best-effort transport via UDP 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.
283
Using Dynamic Provisioning Profiles
Field
For the endpoint systems being provisioned...
Server Type
Specify the type of the SIP registrar server.
You can provision the following SIP registrar servers:
• Standard (Polycom DMA system)
• Polycom
• BroadSoft (BroadWorks)
• Cisco (Cisco Unified Communications Manager)
• Avaya (Avaya Communications Manager)
• Siemens (OpenScape UC Server)
• Microsoft (Lync of Office Communications Server)
Verify Certificate
Enable this option when the endpoint system’s certificate should be verified by the
certificate authority.
Use Endpoint
Provisioning
Credentials
Enable this option when the endpoint system should use the credentials the user entered
at the endpoint for authenticating when registering with a SIP registrar server.
Use Enterprise URI
Enable this option with the endpoint should use the SIP URI of the enterprise user
(domain user).
Common SIP User
Name
Specify the name to use for authentication when registering with a SIP registrar server,
for example, msmith@company.com. If the SIP proxy requires authentication, this field
and the password cannot be blank.
Common SIP credentials (username and password) can be used when the SIP server
does not require unique user credentials.
Common SIP
Password
Specify the password that authenticates the system to the registrar server.
Common SIP credentials (username and password) can be used when the SIP server
does not require unique user credentials.
Provisioning Settings
Provisioning Polling
Interval (minutes)
Specify the frequency at which the endpoint systems poll the RealPresence Resource
Manager system for new provisioning information.
By default, this interval is 60 minutes. For performance reasons, the minimum positive
value for this interval is 5 minutes. There is no maximum value enforced.
Software Update
Polling Interval
(minutes)
Specify the frequency at which the endpoint systems poll the RealPresence Resource
Manager system for a new software update package.
By default, this interval is 60 minutes. For performance reasons, the minimum positive
value for this interval is 5 minutes.
Quality of Service Settings
Video Type of Service
Value
Specify the IP Precedence or Diffserv value for video packets.
Audio Type of Service
Value
Specify the IP Precedence or Diffserv value for audio packets.
FECC Type of Service
Value
Specify the IP Precedence or Diffserv value for Far End Camera Control packets.
Polycom, Inc.
284
Using Dynamic Provisioning Profiles
Field
For the endpoint systems being provisioned...
Type of Service Field
Specify the service type and the priority of IP packets sent to the system for video, audio,
and far-end camera control:
• IP Precedence — Represents the priority of IP packets sent to the system. The value
can be between 0 and 5.
• DiffServ — Represents a priority level between 0 and 63. If this setting is selected,
enter the value in the Type of Service Value field.
Maximum
Transmission Unit Size
(bytes)
Specify the Maximum Transmission Unit (MTU) size used in IP calls. If the video
becomes blocky or network errors occur, packets may be too large; decrease the MTU. If
the network is burdened with unnecessary overhead, packets may be too small; increase
the MTU.
Enable PVEC
Enables the endpoint system to use PVEC (Polycom Video Error Concealment) if packet
loss occurs. PVEC delivers smooth, clear video over IP networks by concealing the
deteriorating effects of packet loss
Enable RSVP
Enables the endpoint system to use Resource Reservation Setup Protocol (RSVP) to
request that routers reserve bandwidth along an IP connection path. Both the near site
and far site must support RSVP in order for reservation requests to be made to routers
on the connection path.
Enable Dynamic
Bandwidth
Specify whether to let the endpoint system automatically find the optimum line speed for
a call.
Maximum Transmit
Bandwidth (Kbps)
Specify the maximum transmission line speed.
Maximum Receive
Bandwidth (Kbps)
Specify the maximum reception line speed.
Operation and
Management Type
Specifies the IP Precedence or Diffserv value for traffic not related to video, audio, or
FECC.
Security Settings
Security Profile
Read-only field. Displays the security level of the endpoint.
Enable Dynamic
Provisioning for
ID/Passwords
This check box must be marked if you want to provision IDs or passwords.
Use Room Password
for Remote Access
Specify whether the local endpoint system password and remote access password are
the same.
Room Password
Enter or change the local endpoint system password here.
When the local password is set, you must enter it to configure the system Admin Settings
using the remote control. The local password must not contain spaces.
Administrator ID
Enter the administrative account that should be used to access the endpoint system
remotely.
Remote Access
Password
For endpoint systems, enter or change the remote access password here.
When the remote access password is set, you must enter it to upgrade the software or
manage the endpoint systems from a computer. The remote access password cannot
include spaces.
Polycom, Inc.
285
Using Dynamic Provisioning Profiles
Field
For the endpoint systems being provisioned...
Meeting Password
Specify the password users must supply to join multipoint calls on this endpoint system if
the call uses the internal multipoint option, rather than a bridge.
This field can also be used to store a password required by another endpoint system that
this system calls. If a password is stored in this field, you do not need to enter it at the
time of the call; the endpoint system supplies it to the system that requires it. The
meeting password cannot include spaces.
Enable Secure Mode
Specify whether to operate in secure mode (also known as security mode), which uses
TLS, HTTPS, AES, digital signatures, and other security protocols, algorithms, and
mechanisms. These protocols encrypt management communication over IP, preventing
access by unauthorized users.
When devices at a site are provisioned to operate in secure mode, the RealPresence
Resource Manager system can only perform the dynamic management operations of
automatic provisioning, automatic software update, and directory and presence services
for the devices. The RealPresence Resource Manager system cannot perform
monitoring or control operations for the devices.
For more information, see the Administrator’s Guide for Polycom HDX Systems.
AES Encryption
Specify how to encrypt calls with other sites that support AES encryption.
• Off—No encryption is used.
• When Available—AES Encryption is used with any endpoint that supports it, even if
the other endpoints in the call don’t support it.
• Required for Video Calls Only—AES Encryption is used for all video endpoints in the
call. Analog phone and voice over ISDN connections are allowed. Video endpoints
must support AES Encryption to participate in the call.
• Required for All Calls—AES Encryption is used for all video endpoints in the call.
Analog phone and voice over ISDN connections are not allowed. All endpoints must.
support AES Encryption to participate in the call.
Enable Web Access
Specify whether to allow remote access to the endpoint system by the web.
Note
The endpoint systems will restart if the remote access settings are changed. This setting
does not deactivate the associated port, only the application. Use the Web Access Port
setting to disable the port.
Enable HTTPS only
Select this check box to allow the endpoint to connect only using HTTPS.
Enable Telnet Access
Specify whether to allow remote access to the system by Telnet.
Note
The endpoint systems will restart if the remote access settings are changed. This setting
does not deactivate the associated port, only the application. Use the Web Access Port
setting to disable the port.
Polycom, Inc.
286
Using Dynamic Provisioning Profiles
Field
For the endpoint systems being provisioned...
Web Access Port
Specify the port to use when accessing the endpoint system’s web interface.
If you change this from the default (port 80), specify a port number of 1025 or higher, and
make sure the port is not already in use. You will need to include the port number with the
IP address when you use the Polycom HDX web interface to access the system. This
makes unauthorized access more difficult.
Note
The system restarts if you change the web access port.
Allow Video Display On
Web
Specify whether to allow viewing of the room where the endpoint system is located, or
video of calls in which the endpoint system participates, using the endpoint system’s web
interface.
Note
This feature activates both near site and far site video displays in Web Director.
NTLM Version
Specify the NTLM version the endpoint system should use to authenticate.
Security Settings 2
Idle Session Timeout in
Minutes
When sessions are enabled, Specify the number of minutes your system can be idle
before the session times out.
Lock Port after Failed
Logins
Specify the number of failed login attempts allowed before the system locks the account.
If set to Off, the system will not lock the user account due to failed login attempts.
This selection controls local and web interface login attempts. For example, if you select
3 here, a user who fails to log in properly twice on the web interface and twice on the
local interface is locked out on the fourth attempt.
Failed Login Window in
Hours
Specify the amount of time that the account remains locked due to failed login attempts.
Port Lock Duration in
Minutes
Specify the amount of time that the port remains locked due to failed login attempts.
Maximum Peer
Certificate Chain Depth
Specify how many links a certificate chain can have. The term peer certificate refers to
any certificate sent by the far-end host to the HDX system when a network connection is
being established between the two systems.
Verify Certificates for
all Web Access
Specify whether the endpoint requires certificate validation to access the endpoint.
Enable NIDS
Enable Network Intrusion Detection messages.
FIPS 140 Mode
Support FIPS 140.
Enable Security
Classification
Helps RealPresence Group system call participants remain conscious of the security
classification when in a BroadWorks managed call.
Whitelist
Enable Whitelist of IPs
Polycom, Inc.
When a white list is enabled, enables access to an endpoint’s web interface only by those
systems with an IP address that matches a pattern using regular expression notation.
287
Using Dynamic Provisioning Profiles
Field
For the endpoint systems being provisioned...
Enter all IPs allowed to
Connect via the web
Specify (by IP addresses using regular expression notation) which systems can access
an endpoint’s web interface. Addresses are matched by pattern, which means that you
could allow IP address that you did not mean to allow. For example, if you entered an IP
address of 15.1.2.111, all of the following results would match:
• 15.1.2.111
• 15.182.1.11
• 15.1.252.111
If you want to allow a range of IP addresses, use the * wildcard instead. For example,
enter 10.11.*.* to allow all IP addresses that begin with 10.11.
General Settings
Heartbeat Posting
Interval (minutes)
Specify the frequency at which the endpoint systems poll the RealPresence Resource
Manager system for a heartbeat.
In Call Stats Posting
Interval (minutes)
Specify the frequency at which the endpoint systems poll the RealPresence Resource
Manager system for in call statistics.
Calendaring Settings
Automatically Discover
Exchange Server
Specify that the RealPresence Resource Manager system should discover the Microsoft
Exchange server for the site by searching DNS records.
If you have configured a Calendar Connector, you should use the Specify Exchange
Server field instead.
Specify Exchange
Server
Specify that the RealPresence Resource Manager system should use the Microsoft
Exchange server specified in the Exchange Server Address field.
Exchange Server
Address
Specify the IP address or FQDN of the Microsoft Exchange server for the site.
If you have configured a Calendar Connector, put the RealPresence Resource Manager
system FQDN in this field.
See Calendar Connector for additional information.
Enterprise Directory Settings
Group Display Name
Specify whether the RealPresence Resource Manager system should identify groups by
their common name (cn) or their DisplayName. These names are extracted from the
Active Directory.
User Display Name
Specify whether the RealPresence Resource Manager system should identify users by
their common name (cn) or their DisplayName. These names are extracted from the
Active Directory.
Enterprise Directory
Admin Group
Specify the Active Directory group whose members should have access to the Admin
settings on the HDX system. This name must exactly match the name in the Active
Directory server for authentication to succeed.
Enterprise Directory
User Group
Specify the Active Directory group whose members should have access to the User
settings on the HDX system. This name must exactly match the name in the Active
Directory server for authentication to succeed.
Polycom, Inc.
288
Using Dynamic Provisioning Profiles
Field
For the endpoint systems being provisioned...
Use Default
Authentication Server
This check box is only available if you have marked the Enterprise Directory Admin
Group or the Enterprise Directory User Group.
When checked, endpoints will use the RealPresence Resource Manager system’s IP
address as the IP for the authentication server.
If you have marked the Enterprise Directory Admin Group or the Enterprise Directory
User Group and leave this check box unchecked, you must indicate an authentication
server for provisioned endpoints.
Authentication Server
This check box is only available if you have marked the Enterprise Directory Admin
Group or the Enterprise Directory User Group.
If you have marked the Enterprise Directory Admin Group or the Enterprise Directory
User Group and have NOT marked the Use Default Authentication Server check box,
you must indicate an authentication server for provisioned endpoints.
Directory Settings
Provision directory
service for hardware
endpoints
Specifies that directory services will be enabled for all endpoints, including hardware
endpoints.
If unchecked, directory services are only provisioned to software endpoints.
Use Default Directory
Server
Use the RealPresence Resource Manager system to provide the directory service.
Directory Server
When the Use Default Directory Server radio button is unchecked, you can use the
Directory Server field enter the IP address of the directory server you wish to use.
Verify Certificate
Enable this option when the endpoint system’s certificate should be verified by the
certificate authority.
Presence Settings
Use Default Presence
Server
Use the RealPresence Resource Manager system to provide the presence service.
Presence Server
When the Use Default Presence Server button is unchecked, you can use the Presence
Server field enter the IP address of the presence server you wish to use.
Verify Certificate
Enable this option when the endpoint system’s certificate should be verified by the
certificate authority.
SNMP Settings
Enable SNMP Access
Specify whether to allow remote access to the system by SNMP.
Note
The endpoint will restart if the remote access settings are changed. This setting does not
deactivate the associated port, only the application.
SNMP Version1
Select to enable SNMP Version1.
SNMP Version2C
Select to enable SNMP Version2C.
SNMP Version3
Select to enable SNMP Version3.
Transport Protocol
Select TCP or UDP.
Polycom, Inc.
289
Using Dynamic Provisioning Profiles
Field
For the endpoint systems being provisioned...
Listening Port
The default port is 161.
Read-only community
For SNMPv2c, specifies the context for the information, which is the SNMP
group to which the devices and management stations running SNMP belong.
The RealPresence RealPresence Resource Manager system has only one
valid context—by default, public—which is identified by this Community
name. The RealPresence RealPresence Resource Manager system will not
respond to requests
Contact Name
Specifies the name of the per son responsible for remote management of this system
Location Name
Specifies the location of the system.
User Name
Specifies the SNMPv3 User Security Model (USM) account name that will be used for
SNMPv3 message transactions. The maximum length is 64 characters
Auth Algorithm
Specifies the type of SNMPv3 authentication algorithm used:
• SHA
• MD5
Auth Password
Specifies the SNMPv3 authentication password. The maximum length is 48 character
Privacy Algorithm
Specifies the type of SNMPv3 cryptography privacy algorithm used.
• CFB-AES128
• CBC-DES
Privacy Password
Specifies the SNMPv3 privacy (encryption) password. The maximum length is 48
characters.
Notification Receiver 1
Enter the following information:
Server Address
SNMP Version
Listening Port
Trap/Inform
Notification Receiver 2
Enter the following information:
Server Address
SNMP Version
Listening Port
Trap/Inform
Notification Receiver 3
Enter the following information:
Server Address
SNMP Version
Listening Port
Trap/Inform
Concierge Settings
Enable Concierge
Service
Polycom, Inc.
Mark the Enable Concierge Service check box to enable Polycom Concierge.
290
Using Dynamic Provisioning Profiles
Admin Config Provisioning Profiles
Admin Config provisioning profiles, allow you to create provisioning profiles that include maximum and
preferred call speeds for H.323 settings, calendaring settings, Microsoft Lync settings, and so on.
You can use Admin Config provisioning profiles to provision the following Polycom endpoints:
● Polycom VVX systems deployed in dynamic management mode
● Polycom HDX systems deployed in dynamic management mode
● Polycom RealPresence Group Series endpoints (required)
● Polycom RealPresence Immersive Studio systems (required)
● Polycom CMA Desktop clients
● RealPresence Mobile clients
● RealPresence Desktop clients
Polycom CMA Desktop provisioning occurs on a session by session basis.
As soon as an endpoint is configured to use the RealPresence Resource Manager for its provisioning
server, it starts polling for provisioning profile updates. To ensure out-of-box usability, the RealPresence
Resource Manager system comes with a default Admin Config provisioning Profile. This default profile
cannot be customized with any rule. You need to create new Admin Config provisioning profiles to customize
endpoint configuration settings in your video environment.
•
•
If an Admin Config provisioning profile provisions a setting that the endpoint is not capable of
fulfilling, the endpoint will ignore those settings.
The name of the Default Provisioning Profile is stored in the system database and is not localized
into other languages. You cannot change the name.
For information about how to add an Admin Config provisioning profile, see Create a New Provisioning
Profile.
Available Settings for Admin Config Provisioning
Profiles
The following table shows the fields you can configure when adding a new Admin Config provisioning profile
to the RealPresence Resource Manager system. You may find more implementation details about these
fields in the endpoint system documentation.
To view these fields, go to Endpoint > Dynamic Management > Provisioning Profiles. Then choose Add
and choose Admin Config Provisioning Profile.
Field
For the endpoint systems being provisioned...
General Info
Name
Polycom, Inc.
Specify a unique name for the profile
291
Using Dynamic Provisioning Profiles
Field
For the endpoint systems being provisioned...
Provisioning Profile Type
Choose the profile type from the drop-down list.
Selectable Provisioning for Group
Series
When you mark this check box, you can manually select which settings within
the provisioning profile are sent to a RealPresence Group system. Only the
selected settings will be provisioned to RealPresence Group systems.
Within the provisioning profile, only the settings that you select are set to the
RealPresence Group system. For example, if a provisioning setting is blank
but still checked, the blank value is still be provisioned to the system.
By default, all settings are checked. If you don’t want to provision the setting to
the RealPresence Group system, you must uncheck the individual settings.
System Settings
Enable Language Settings
Specifies the language for the video endpoint system’s user interface.
Possible values include: Arabic, Simplified Chinese, Traditional Chinese,
English_US, English_UK, French, German, Hungarian, Italian, Japanese,
Korean, Norwegian, Polish, Portuguese, Russian, and Spanish.
If you clear this check box, the language settings can be manually configured
on the endpoint.
Allow Access to User Setup
Specifies whether the User Settings screen is accessible to users via the
System screen. Select this option to allow endpoint system users to change
limited environmental settings.
Allow Directory Changes
Specifies whether endpoint system users can save changes they make to the
directory on contacts/favorites list.
Auto-answer Point to Point Calls
Specifies whether endpoint answers point to point calls automatically.
Auto-answer Multipoint calls
Specifies whether endpoint answers multipoint calls automatically.
Call Detail Report
Specifies whether to collect call data for the Call Detail Report and Recent
Calls list. When selected, information about calls can be viewed through the
endpoint system’s web interface and downloaded as a .csv file.
Note
If this setting is disabled, applications will not be able to retrieve Call Detail
Report (CDR) records.
Maximum Time in Call (minutes)
Specifies the maximum number of minutes allowed for a call. Enter 0 to
remove any limit.
Recent Calls
Specifies whether to display the Recent Calls button on the home screen. The
Recent Calls screen lists the site number or name, the date and time, and
whether the call was incoming or outgoing.
Note
If the Call Detail Report option is not selected, the Recent Calls option is not
available.
Polycom, Inc.
292
Using Dynamic Provisioning Profiles
Field
For the endpoint systems being provisioned...
Screen Saver Wait Time
Specifies how long the system remains awake during periods of inactivity. The
default is 3 minutes. If the system requires users to log in, the screen saver
timeout also logs out the current user.
Setting this option to Off prevents the system from going to sleep. To prevent
image burn-in, specify 15 minutes or less.
Directory Search Mode
Specifies how endpoint directory searches are initiated by the endpoint user.
Possible values are:
• Auto—The search is executed after the user stops entering characters.
• Manual—The search is executed only when the user explicitly clicks the
Search button.
Maximum Number of Active Web
Sessions
Specifies the number of active web sessions that are allowed. The default is
25.
Home Screen Settings
Display H.323 Extension
Lets users placing a gateway call enter the H.323 extension separately from
the gateway ID.
If you do not select this setting, endpoint system users make gateway calls by
entering the call information in this format:
gateway ID + ## + extension
Enable Availability Control
When enabled, lets users set their availability in the endpoint system’s local
user interface.
Address Bar (Left Element)
Allows you to select which element you want displayed on the left side of the
address bar on the local interface.
Address Bar (Right Element)
Allows you to select which element you want displayed on the right side of the
address bar on the local interface.
Call Settings
Maximum Speed for Receiving
Calls (kbps)
Restricts the bandwidth used when receiving calls.
If the far site attempts to call the endpoint system at a higher speed than
selected here, the call is re-negotiated at the speed specified in this field.
The default is 384 kbps.
Preferred Speed for Placing Calls
(kbps)
Determines the speeds that will be used for calls from this endpoint system
when:
• The Call Quality selection is either unavailable or set to Auto on the Place
a Call screen
• The call is placed from the directory
If the far-site endpoint system does not support the selected speed, the
endpoint system automatically negotiates a lower speed.
The default is 384 kbps.
Preferred Dialing Method
Specifies the preferred method for dialing various call types.
• If set to Auto (default), calls use the configured dialing order.
• If set to Manual, the endpoint systems will prompt the user to select the call
type from a list when placing a call.
Polycom, Inc.
293
Using Dynamic Provisioning Profiles
Field
For the endpoint systems being provisioned...
Audio Settings
Mute Auto Answer Calls
Specifies whether or not to automatically mute incoming calls.
The default setting is to not automatically mute incoming calls.
CMA Desktop Settings
Allow IM/Chat
When enabled, specifies that the Polycom CMA Desktop client can initiate
instant messaging.
This is enabled by default.
Software Endpoint Settings
Enable IM/Chat
For RealPresence Desktop clients, this option must be provisioned to support
both presence and chat functions.
For CMA Desktop, this option must be provisioned to support chat functions.
Enable Screen Saver When in
Call
Specifies whether or not to enable screen saver during a call.
Auto Accept Invitation
Enables the client to auto-accept chat invitations.
Applicable to RealPresence Desktop clients only.
Allow IM Storage
Enables the client to store chat history on its local drive.
Applicable to RealPresence Desktop clients only.
Note
If you disable this option after enabling it, all chat history is cleared for the
client.
Provision Check that the CMA
Desktop is the default program
for:
• Opening Call To links
• Opening H323 links
• Opening SIP links
Selecting this setting provisions the CMA Desktop to be the default program
for opening the above links.
Provision Enable Sending 720p
(HD) Video
Select this check box to enable sending HD video.
This is enabled by default.
Allow 720p frame rates up to:
Enabled when Provision Enable Sending 720p (HD) people video is also
selected.
You can choose 15 Frames per second or 30 Frames per second.
Calendaring Settings
Enable Calendaring
When enabled, this provisions the Microsoft Exchange server and calendaring
settings for the endpoint system.
Alert Tone
When enabled, specifies that an endpoint system provisioned for Polycom
Conferencing for Outlook will play a sound along with the meeting reminder. In
this case, the endpoint will only play a sound when the system is not in a call.
Display Private Meeting
When enabled, specifies that an endpoint system provisioned for Polycom
Conferencing for Outlook will display details about meetings marked private.
Polycom, Inc.
294
Using Dynamic Provisioning Profiles
Field
For the endpoint systems being provisioned...
Meeting Reminder Time
Specifies the number of minutes before the meeting an endpoint system
provisioned for Polycom Conferencing for Outlook will display a reminder.
Check for New Messages Interval
Specifies the interval to check calender invitation messages.
Use Endpoint Provisioning
Credentials
If checked, the endpoint provisioning credentials will be used to connect the
calender server.
If canceled, you need to go to the endpoint UI to specify the credential used to
connect the calender server.
Microsoft Lync Settings
Group Name
Specifies the group name for which the endpoint system should be
provisioned.
VVX Settings
Configuration Server URL
Specifies the IP address for the system that will provide provisioning service.
All addresses can be followed by an optional directory and optional filename.
Logging Server URL
Specifies the directory to use for log files, if required.
A URL can also be specified. This field is blank by default.
Configuration Data
Enter XML data for a custom configuration. Enables the RealPresence
Resource Manager system administrator's to provision settings that the
RealPresence Resource Manager system does not normally provide.
Polycom, Inc.
295
Creating Dynamic Provisioning Rules
You apply dynamic provisioning profiles by using provisioning rules. A provisioning rule consists of one or
more conditions that must be met before the dynamic provisioning profile can be applied. You can create
multiple rules and associate a profile with more than one rule at a time.
For example, you can use provisioning rules to provision different endpoints within the same site with
different network settings.
If a dynamically managed endpoint does not meet any conditions of any rule, it is provisioned with the
default profiles.
This section describes provisioning rules operations. It includes these topics:
● Activating Provisioning Rules
● Prioritizing Provisioning Rules
● Using Rule Conditions
● Working with Provisioning Rules
Activating Provisioning Rules
Provisioning rules must be activated in order to be used in dynamic provisioning.
When you create a rule, it is activated by default and will be used the next time a polling endpoint or server
meets the conditions of the rule.
If you want to stop using a provisioning rule, you need deactivate it. If you want to change a rule, you must
deactivate it before you can edit it. In addition, you cannot delete an activated provisioning rule.
Prioritizing Provisioning Rules
After you have added more than one provisioning rule, you can change the priority of the list of provisioning
rules you created. When you add rules, they are automatically prioritized according to the order in which
they were added to the system.
Rules with a higher priority will be applied first. The Rule Priority determines which provisioning rule takes
priority.
Consider the following example:
Create two rules, one for the Support user group and one for the Toronto user group. Jason Smith is part
of the Support group and also part of the Toronto group.
● The Support Rule is assigned an Admin Config provisioning profile named Low-Bandwidth, which
enables a maximum speed for receiving calls of 128kbps. The Support Rule is assigned a priority of
1.
Polycom, Inc.
296
Creating Dynamic Provisioning Rules
● The Toronto Rule is assigned an Admin Config provisioning profile called High-Bandwidth, which
enables a maximum speed for receiving calls of 1920kbps. The Toronto Rule is assigned a priority
of 2.
In this example, Jason’s endpoint is provisioned with the Low-Bandwidth provisioning profile, because it has
the higher priority.
When you add provisioning rules, you may want to assign provisioning rules with more robust privileges a
higher priority than those providing fewer privileges.
Using Rule Conditions
A provisioning rule is comprised of one or more conditions that you define. You are allowed to add multiple
conditions of multiple condition types to a single rule.
For example, you can create a rule that applies a provisioning profile according to the user group (condition)
and device type (condition).
Rule conditions can be complex and include OR or AND relationships, as well as NOT relationship.
If a dynamically managed endpoint does not meet any conditions of any rule, it is provisioned with the
default profiles.
For example, you can create a rule that applies a network provisioning profile for all device types within a
site except for VVX endpoints.
Provisioning rules support the following condition types:
Condition Type
Attributes
Site
The site name.
User Group
The name of a user group.
User
You can choose from one of the following user attributes when defining a
user condition for a rule:
• Title
• Department
• User ID
Device
You can choose from the following attributes when defining a device
condition for a rule:
• Device Type
• Serial Number
Condition Operators
When you build conditions you can use three operators: CONTAINS, IN, and =.
The IN operator allows you to add multiple values to the same condition. For example, if you want to create
a provisioning rule that applies to both RealPresence Desktop devices and RealPresence Mobile devices,
you should use the IN operator and add both devices to the condition.
The IN operator is equivalent to OR but the IN performance is much higher than the OR when building the
rule. It is highly recommended to use IN if you want to use >= 5 ORs to connect conditions
Polycom, Inc.
297
Creating Dynamic Provisioning Rules
The = operator allows you to add only one value to the condition.
The CONTAINS operator is available for user group rules.
Working with Provisioning Rules
When you create a provisioning rule, you can associate multiple profile types with the same provisioning
rule. For example, when you provision a RealPresence Access Director for your environment, it is typical to
associate a Network provisioning profile, an Admin Config provisioning profile, and a RealPresence Access
Director server provisioning profile with the same rule.
If a dynamically managed endpoint does not meet any conditions of any rule, it is provisioned with the
default profiles.
This topic describes the provisioning rule operations a user assigned the Administrator role can perform.
These are:
● Add a Provisioning Rule
● View Details of a Provisioning Rule
● Edit the Priority of a Provisioning Rule
● Clone a Provisioning Rule
● Deactivate a Provisioning Rule
● Edit a Provisioning Rule
● Delete a Provisioning Rule
Add a Provisioning Rule
This topic describes how to add provisioning rules. Only users with the administrator role can add
provisioning rules.
Add new provisioning rules in the middle of the work day, not first thing in the morning.
When you add a new provisioning rule or change its priority, the RealPresence Resource Manager system
immediately rolls it out. If it rolls it out first thing in the morning, people who need to attend a “start the day”
conference will have to first wait for their endpoint to be provisioned. Polycom recommends implementing
profiles in the middle of a work day and then let the provisioning occur at the designated polling interval.
When you add a provisioning rule, use the Add New Rule dialog box to complete the following steps:
1 Name the Provisioning Rule.
2 Activate the Rule.
3 Add a Condition to a Provisioning Rule.
4 Associate Provisioning Profiles with a Provisioning Rule.
The following steps incorporate an example of creating a rule that applies provisioning profile to all devices
of a certain type within a specific site. You can create rules of varying complexity or simplicity. See Using
Rule Conditions for other examples.
Polycom, Inc.
298
Creating Dynamic Provisioning Rules
Name the Provisioning Rule
Each provisioning rule you create must have a unique name as well as a description.
To create and name a provisioning rule:
1 Navigate to Endpoint > Dynamic Management > Provisioning Rules.
2 Click
.
The Add New Rule dialog box displays.
3 In the General Info area, enter a name for the new rule.
In this example, we are creating a rule for all HDX systems in the Austin, TX, area.
Next you will ensure that the provisioning rule is active, if needed. Do not close the dialog box.
Activate the Rule
By default, a rule is marked as active when you create it. Active rules are automatically sent the next time
a dynamically managed device polls the RealPresence Resource Manager system for provisioning updates.
If you do not want the rule to be active, cancel the Active check box.
The next step is to add one or more conditions to your rule. Do not close the dialog box.
Add a Condition to a Provisioning Rule
You can add a condition to a provisioning rule when you first create it or you can add a new condition or
change a condition of an inactive rule.
To add a condition to a provisioning rule:
1 In the Add New Rule dialog box, click
Polycom, Inc.
on the top.
299
Creating Dynamic Provisioning Rules
The Add New Condition dialog box displays.
2 Use the Add New Condition dialog to create the conditions that you need.
a Select a condition.
In this example, we are creating a condition for the Austin site, so we chose Site in the Type drop
down list, and selected the Austin site for the Value.
b Click OK to save the condition.
This example defines a condition for the rule to include all HDX systems.
c To add another condition, first select the condition you just created and then click
.
To add a new condition to a rule, you must select a condition in the list from which to build on.
When creating conditions, you can use the following condition operators: contains, in, or =. The
contains operator is only applicable to group condition type.
After you create the Site condition, click
to add more conditions to your rule.
d Select a value from the Relation column. You can relate multiple conditions with an And
statement or an Or statement.
In our example, we want this rule to apply to both the site and the device type, so we chose And.
This screenshot shows a Device condition type that defines a condition that includes all HDX
device types.
e Click OK to save the condition.
Polycom, Inc.
300
Creating Dynamic Provisioning Rules
f
To view all conditions in your rule, expand the folder.
In our example, we expanded the And folder to view each condition. Notice that the condition is
also displayed in the field below the condition table.
The next step in the Add New Rule dialog is to associate provisioning profiles with the rule. Do not close
the Add New Rule dialog box.
Associate Provisioning Profiles with a Provisioning Rule
After you have created your condition(s), you need to select which provisioning profiles to associate with
this rule. You must have already created the provisioning profiles you need.
A provisioning rule must have at least one profile associated with the rule.
See Using Dynamic Provisioning Profiles.
To associate provisioning profiles with a provisioning rule:
1 To associate an endpoint provisioning profile such as a Network Provisioning profile or Admin
Config profile, navigate to the Endpoint Provisioning Profile page in the Add New Rule dialog
box.
You can associate one or more profile to the rule. For example, one Network Provisioning Profile, one
Admin Config Profile, and one Server Provisioning profile.
2 Select the Available Profiles you want to associate with the rule you created and click the down
arrow to move them to the Selected Profiles section.
In this example, you can select the HDX system profile, which is an Admin Config provisioning
profile.
3 You have now finished creating a provisioning rule. Click OK to save the rule.
These steps used an example rule that applied the associated profile to all HDX systems within a
example Austin site.
View Details of a Provisioning Rule
You can view the details of a provisioning rule. Use this option when you want to view the provisioning rule
without editing it.
To view details of a provisioning rule:
1 Go to Endpoint > Dynamic Management > Provisioning Rule.
2 Optionally, click
to filter the rules that display. Choose from the following filters: Rule Name,
Status, and Condition (Device Type, Site, User Group).
3 In the Provisioning Rules page, select the rule you want to view,
4 Click
.
5 Click OK.
Edit the Priority of a Provisioning Rule
By default, provisioning rules are assigned a priority level according to order in which they are added to the
system. You can change the priority of a provisioning rule.
Polycom, Inc.
301
Creating Dynamic Provisioning Rules
Provisioning rules with higher priority get applied first.
To edit the priority of a provisioning rule:
1 Go to Endpoint > Dynamic Management> Provisioning Rules.
2 Optionally, click
to filter the rules that display. Choose from the following filters: Rule Name,
Status, and Condition (Device Type, Site, User Group).
3 In the Provisioning Rules page, select the rule of which you want to change the priority.
4 Click Edit Priority from the More drop-down list.
The Edit Priority dialog appears.
5 Enter a new priority number in the Rule Priority field.
6 Click OK.
The system changes the priority of the selected provisioning rule.
Clone a Provisioning Rule
You can clone a provisioning rule when you want to re-use most of its conditions in a new rule or just change
the name of an existing rule.
To clone a provisioning rule:
1 Go to Endpoint > Dynamic Management > Provisioning Rules.
2 Optionally, click
to filter the rules that display. Choose from the following filters: Rule Name,
Status, and Condition (Device Type, Site, User Group).
3 In the Provisioning Rules page, select the rule you want to clone and click
.
4 In the Clone Rule dialog box, enter a name for the new rule and click Save.
The provisioning rule appears last in the Provisioning Rules list.
5 As needed, edit the rule.
Deactivate a Provisioning Rule
You can deactivate a provisioning rule if you want to stop using it as a provisioning rule or edit it. Deactivated
provisioning rules are not used.
You must activate a provisioning rule for it to be used.
To deactivate a provisioning rule:
1 Navigate to Endpoint > Dynamic Management > Provisioning Rule.
2 Optionally, click
to filter the rules that display. Choose from the following filters: Rule Name,
Status, and Condition (Device Type, Site, User Group).
3 In the Provisioning Rule page, select the rule and select More > Deactivate.
4 Click Yes to confirm the deactivation.
Polycom, Inc.
302
Creating Dynamic Provisioning Rules
Edit a Provisioning Rule
When you choose to edit a provisioning rule, it automatically becomes deactivated. If you want to view the
details of a provisioning rule without de-activating it, use the View Details option.
If you choose not to save your changes, the rule will not be deactivated.
To edit a provisioning rule:
1 Go to Endpoint > Dynamic Management > Provisioning Rule.
2 Optionally, click
to filter the rules that display. Choose from the following filters: Rule Name,
Status, and Condition (Device Type, Site, User Group).
3 Select the rule and click
.
You are prompted to deactivate the rule.
4 Click OK to confirm the deactivation.
5 In the Edit Rule dialog box, make your changes.
For a detailed description of how to create a rule, see Add a Provisioning Rule on page 298.
6 Click OK.
The provisioning rule is updated.
Delete a Provisioning Rule
You cannot delete an active provisioning rule. You must first deactivate it before you can delete it.
To delete an provisioning rule:
1 Go to Endpoint > Dynamic Management> Provisioning Rules.
2 Optionally, click
to filter the rules that display. Choose from the following filters: Rule Name,
Status, and Condition (Device Type, Site, User Group).
3 Select the rule and click
.
4 Click Yes to confirm the deletion.
The rule is deleted from the system.
Polycom, Inc.
303
Dynamically Managing Endpoint Naming
Schemes
The RealPresence Resource Manager system allows administrators to configure their E.164 alias, endpoint
naming schemes and SIP URIs for endpoints that are dynamically managed.
If you choose to provision H.323 settings through a network provisioning profile, you can also define the
E.164 number and endpoint naming scheme used for endpoints. You can also auto-generate SIP URIs for
dynamically managed endpoints.
This section discusses these topics:
● Using Custom Active Directory Attributes
● Define an E.164 Address Scheme
● Define an Endpoint Naming Scheme and H.323 Alias
● Auto-Generate SIP URIs for Dynamically Managed Endpoints
Using Custom Active Directory Attributes
When your system is integrated with Active Directory, it only incorporates and displays attributes from the
Active Directory record that are part of the Active Directory Global Catalog. When you define E.164 numbers
and SIP URIs, you can use Active Directory attributes that are not displayed in the RealPresence Resource
Manager system user record.
For example, the following diagram displays some telephone numbers that can be configured in Active
Directory. By default, when you integrate your RealPresence Resource Manager system with Active
Directory only the default phone number field is used within the E.164 Numbering scheme.
If you wanted use the IP Phone attribute instead of the default phone number, you need to enter that specific
attribute name that in RealPresence Resource Manager system when you create a naming scheme.
\
Polycom, Inc.
304
Dynamically Managing Endpoint Naming Schemes
The following screen shot displays the IP Phone attribute being entered when you create an E.164 naming
scheme:
Find the Attribute Name to Use
You must use the correct name of the attribute. You can use the Active Directory management console to
find the attribute name you want to use.
To use Active Directory to find an attribute name:
1 Select View > Advanced Features to ensure advanced features are enabled in the console.
2 Navigate to an Active Directory user.
3 Right-click the user and select Properties.
4 In the Properties dialog, click the Attribute Editor tab.
5 Find the attribute to be used and record the attribute name.
6 Use the Attribute name as the value in Mapping to Active Directory Name field.
Polycom, Inc.
305
Dynamically Managing Endpoint Naming Schemes
Active Directory Global Service
To take advantage of custom Active Directory attributes in RealPresence Resource Manager, your Active
Directory administrator must ensure that the attributes you want to use have been added to the Active
Directory Global Catalog service.
You must work with your Active Directory administrator to decide how to manipulate the Active Directory
schema to ensure that the attributes you want to use in naming schemes are available to the RealPresence
Resource Manager system.
The Active Directory global catalog is a distributed data repository that contains a search-able, partial
representation of every object in every domain in a multi-domain Active Directory Domain Services (AD DS)
forest. The global catalog is stored on domain controllers that have been designated as global catalog
servers and is distributed through multi-master replication. Searches that are directed to the global catalog
are faster because they do not involve referrals to different domain controllers.
However, to minimize replication traffic and keep the global catalog's database small, only selected
attributes of each object are replicated. This is called the partial attribute set (PAS). The PAS can be
modified by modifying the schema and marking attributes for replication to the global catalog.
The Active Directory administrator can do this by ensuring that the corresponding attributes are included in
the Partial Attribute Set. See http://support.microsoft.com/kb/248717 for information about “How to Modify
Attributes That Replicate to the Global Catalog.”
Define an E.164 Address Scheme
You can define an E.164 address scheme that will be used when provisioning E.164 addresses to all
dynamically managed endpoints.
You can choose to use to define a number range, use the default phone number or use a different Active
Directory attributes. See Using Custom Active Directory Attributes.
To define an E.164 address scheme for dynamically managed endpoints:
1 Navigate to Endpoint > Dynamic Management > E.164 Numbering.
2 Define your numbering scheme according to the options provided.
The administrator has the following options when implementing an E.164 numbering scheme:
Polycom, Inc.
306
Dynamically Managing Endpoint Naming Schemes
Option
Usage
Select Area
When areas are enabled, you can select an area to which you want to apply this E.164
numbering scheme.
This field is only available to users who manage more than one area. The drop-down list
lists only those areas that the user has permission to manage.
Users with the administrator role can always select an area when areas are enabled.
Prefix
•
•
•
Base Field
You can define a specific number range or indicate that a phone number be used for the
Base Field:
No Prefix—The system will not append a prefix to create the E.164 assignment.
A Number —The system appends the prefix specified to create the E.164 assignment.
Based on Endpoint Type—The system appends an Endpoint Type prefix to create
the E.164 assignment.
You can use the suggested prefix or click the Device Number field to edit the
prefix for the device type.
This options is not available if you choose to use a suffix based on the endpoint
type.
To specify a Number Range:
1 In the Base Field, select Specify Number Range.
2 Use the To and From fields to define the number range.
To use a Phone Number:
1 In the Base Field, select Use Phone Number.
2 If you want to use the main phone number field from Active Directory, leave the
Mapping to Active Directory Name field blank.
3 If you want to use a number other than the one indicated in the Phone Number field in
Active Directory, you can indicate another Active Directory attribute to use.
 For example, if your Active Directory also includes mobile number information in an
Active Directory Attribute called mobilenum, you should select Use Phone Number
and then enter the name mobilenum in the Mapping to Active Directory Name
field.
For more information on which Active Directory attributes can be used, see To
auto-generate SIP URIs for dynamically managed endpoints:.
4 Enter the Maximum number of digits to use from the user’s phone number (between
3 and 10 digits). The digits from the phone number are selected from right to left.
5 Enter Number range to use if phone number is empty (reverts to Specify Number
Range)—The system will revert to using a number range if the user’s phone number
is empty.
Suffix
Polycom, Inc.
•
•
•
No Suffix—The system will not append a suffix to create the E.164 assignment.
A Number —The system appends the suffix specified to create the E.164 assignment.
Based on Endpoint Type—The system appends a pre-defined Endpoint Type suffix
to create the E.164 assignment.
You can use the suggested suffix or click the Device Number field to edit the suffix
for the device type.
This option is not available if you used a prefix based on the endpoint type.
307
Dynamically Managing Endpoint Naming Schemes
The total number of digits specified for an E.164 number must be 15 or less. If the user’s phone
number is used as the base field, the system reserves one digit to differentiate between the user’s
multiple devices. In this case the total number of digits configured cannot exceed 14 digits.
3 When finished defining your numbering scheme, click Update.
Settings are applied the next time the endpoint polls for a dynamic provisioning update.
Define an Endpoint Naming Scheme and H.323 Alias
You can define an endpoint naming scheme that will be provisioned to all dynamically managed endpoints.
When you define the endpoint name, you can choose to have the endpoint name also serve as the H.323
alias for the endpoint. This is the default.
Alternatively, you can use a different name for the H.323 alias and the endpoint name and define a naming
scheme for both.
System names cannot exceed 36 characters or provisioning will fail.
To define an endpoint naming scheme for dynamically managed endpoints:
1 Navigate to Endpoint > Dynamic Management > Endpoint Naming.
2 Build your endpoint naming scheme.
System names can be a combination of up to four naming fields and three separators. For example,
the following endpoint name is defined by selecting UserID, City and Endpoint Type fields and by
using two “.” separators: UserID.City.HDX.
The administrator has the following options when implementing an endpoint naming scheme:
Polycom, Inc.
308
Dynamically Managing Endpoint Naming Schemes
Option
Usage
Select Area
When areas are enabled, you can select an area to which you want to apply this endpoint
naming scheme.
This field is only available to users who manage more than one area. The drop-down list
lists only those areas that the user has permission to manage.
Naming Field
The following fields are available to use as a naming field. Be sure that the field you
choose is populated for all users in your system. You cannot use the same naming field
twice in the same scheme.
• Last Name
• First Name
• User ID
• City
• Department
• Endpoint Type
• Domain
• Title
• Area (only available when areas are enabled)
You cannot use the same naming field more than once within the same naming scheme.
Separator
You can use a separator between each naming field. If you do not want to use a
separator, you must select (none).
Choose from the following separators:
• (none)
• (space)
• ,
• • _
You can use the same separator multiple times.
3 To use the endpoint name as the hostname for hardware endpoints (such as RealPresence Group
Series, HDX, or RealPresence Immersive Studio systems), select the Use the Generated
Endpoint Name as the Hardware Endpoint’s Hostname check box.
4 To use same naming scheme for the H.323 alias, ensure that the Use Endpoint Naming for H323
ID check box is selected.
5 To use a different naming scheme for the H.323 alias:
a Clear the Use Endpoint Naming for H323 ID check box.
b Build your H.323 ID scheme according to the same options as the System Name.
The administrator has the following options for an H.323 ID scheme:
Polycom, Inc.
309
Dynamically Managing Endpoint Naming Schemes
Option
Usage
Select Area
When areas are enabled, you can select an area to which you want to apply this endpoint
naming scheme.
This field is only available to users who manage more than one area. The drop-down list
lists only those areas that the user has permission to manage.
Naming Field
The following fields are available to use as a naming field. Be sure that the field you
choose is populated for all users in your system. You cannot use the same naming field
twice in the same scheme.
• Last Name
• First Name
• User ID
• City
• Department
• Endpoint Type
• Endpoint Model
• Domain
• Title
• Area (only available when areas are enabled)
You cannot use the same naming field more than once within the same naming scheme.
Separator
You can use a separator between each naming field. If you do not want to use a
separator, you must select (none).
Choose from the following separators:
• (none)
• • _
You can use the same separator multiple times.
6 When finished, click Update.
Settings are applied the next time the endpoint polls for a dynamic provisioning update.
Polycom, Inc.
310
Dynamically Managing Endpoint Naming Schemes
Auto-Generate SIP URIs for Dynamically Managed
Endpoints
You can automatically generate a SIP URI for each dynamically managed endpoint according to a naming
scheme you define.
You can choose to use the user email address as the SIP URI or define a custom URI from Active Directory
attributes. See Using Custom Active Directory Attributes.
When you define a custom SIP URI from Active Directory fields, you can choose one of the default fields or
an different Active Directory attribute.
To auto-generate SIP URIs for dynamically managed endpoints:
1 Navigate to Endpoint > Dynamic Management > SIP URI.
2 If areas are enabled, select an area from the Select Area drop-down list.
The Select Area drop-down list is available to users with the administrator or area administrator role.
The areas included in the list are restricted to those areas that the user is allowed to manage.
3 Select the Auto-generate SIP URIs for all users check box.
You can either use the user’s email address as the SIP URI or define the SIP URI yourself.
4 To use the user’s email address as their SIP URI. Check the Use the user’s email address as
their SIP URI if you want this option.
If you choose this option, you cannot further define the fields used for the SIP URI.
5 To define a SIP URI, complete the naming fields and separators.
SIP URIs can be a combination of up to four naming fields, three separators and domain name suffix.
For example, the following SIP URI is defined by selecting UserID, City and Endpoint Type fields, by
using two “.” separators and domain name "abc.com": UserID.City.HDX@abc.com.
You can use a pre-defined naming field from the drop-down list or type a specific Active Directory
attribute.
a To use a pre-defined field, select it from the drop-down list. Pre-defined fields include: Last Name,
First Name, User ID, City, Department, Endpoint Type, Endpoint Model, Domain, and Title.
b To use an Active Directory attribute, select AD Attribute from the drop-down list and enter the
name of the attribute in the Attribute Name field. The attribute you enter must exactly match an
existing Active Directory attribute. Talk to your Active Directory administrator if you have
questions about which Active Directory attributes are available for use.
As a best practice, include be sure to include a valid SIP Domain information in the SIP URI
definition.
Polycom, Inc.
311
Dynamically Managing Endpoint Naming Schemes
Option
Usage
Naming Field
The following fields are available to use as a naming field. Be sure that the field you
choose is populated for all users in your system. You cannot use the same naming field
twice in the same scheme.
• Last Name
• First Name
• User ID
• City
• Department
• Endpoint Type
• Endpoint Model
• Domain
• Title
• AD Attribute.
 When you select AD attribute, you must also enter an name in the Attribute Name
field. The name must match an available Active Directory attribute.
You cannot use the same naming field more than once within the same naming scheme.
Separator
You can use a separator between each naming field. If you do not want to use a
separator, you must select (none).
Choose from the following separators:
• (none)
• .
• • _
• @
•
You cannot use the @ separator more than once and it cannot be used before the _
separator.
Domain name suffix
Adds the domain suffix to the naming field you choose.
You can either choose None or select “A String (specify) to enter the domain suffix as a
string value.
For example, LastName.FirstName@domainsuffix.com can be defined by selecting
LastName and FirstName as naming fields with a “.” separator. The Domain suffix in this
example was entered as a string.
Caution: Be sure to verify that the string you enter here is a valid SIP domain or the SIP
URI will not be valid.
6 Select the Keep URIs Unique check box if you want unique SIP URIs for each endpoint regardless
of user.
If you leave this check box cleared, the user’s SIP URI can be used for each endpoint associated with
that user.
7 Click Update.
Polycom, Inc.
312
Using Bundled Provisioning Profiles
The Polycom RealPresence Resource Manager system supports Bundled Provisioning Profiles for
dynamically managed Polycom RealPresence Group Series systems, Polycom RealPresence Immersive
Studio systems, RealPresence Centro, and Polycom HDX (v3.0.3 and higher) systems. With Bundled
Provisioning Profiles, a RealPresence Resource Manager user with the administrator role can download
a bundled provisioning profile from any already configured HDX or RealPresence Group Series that is
dynamically managed by the RealPresence Resource Manager.
You can then indicate which dynamically managed Polycom HDX or RealPresence Group Series of the
same model and software version will receive the bundled provisioning profile when it next polls the
RealPresence Resource Manager system for new provisioning information.
Bundled provisioning profiles are one of three types of provisioning profiles that you can use when
dynamically managing an endpoint.
Bundled provisioning profiles provides businesses with an efficient and effective way to provision
RealPresence Group Series, RealPresence Immersive Studio systems, and Polycom HDX systems
consistently across each model. Endpoint users with administrative rights can still change the settings on
an HDX system after the bundled provisioning profile is applied. However, if another profile is sent by the
RealPresence Resource Manager system, it will overwrite the user’s changes.
This section describes how to work with bundled provisioning profiles. It includes the following topics:
● How Bundled Provisioning Works
● Download a Bundled Provisioning Profile
● View the List of Bundled Provisioning Profiles
● Edit a Bundled Provisioning Profile
● Delete a Bundled Provisioning Profile
● Re-associate Devices with a Different Profile
● Settings included in a Bundled Provisioning Profile for an HDX
● Settings included in a Bundled Provisioning Profile for a RealPresence Group System and
RealPresence Immersive Studio System
How Bundled Provisioning Works
In dynamic management mode, when an Polycom endpoint starts up and at designated intervals thereafter,
it automatically polls for new provisioning information from the RealPresence Resource Manager system. If
a bundled provisioning profile exists on the RealPresence Resource Manager system that has been
associated with the endpoint, the bundled profile is sent over a secure HTTPS connection.
Polycom, Inc.
313
Using Bundled Provisioning Profiles
In this release, the RealPresence Group Series, RealPresence Immersive Studio systems, and HDX
system (v3.0.3 and higher) parameters that may be included in a bundled provisioned profile are limited to
the following types:
● Camera configuration settings
● Monitor configuration settings
● Microphone configuration settings
● Security settings (such as password length)
● Home screen settings
Considerations for Bundled Provisioning Profiles
Consider the following items when using bundled provisioning profiles.
● You can store a maximum of 1000 bundled provisioning profiles on your RealPresence Resource
Manager system.
● You cannot update software with a bundled profile.
● The software version of the endpoint must match the software version of the endpoint from which the
bundled provisioning profile was made. A bundled profile is only compatible with endpoints of the
same software version. If the endpoint’s software version is updated, you must create a new bundled
profile.
● When using bundled provisioning profiles to provision HDX systems, you can use them with v3.0.3
or higher. Previous versions do not supported bundled provisioning profiles.
● Security and home screen settings are not included in bundled profiles for RealPresence Group
Series.
● You must have the Administrator role to create bundled provisioning profiles. Users with the Device
Administrator role can apply and re-assign bundled provisioning profiles.
● Be sure to give each provisioning profile a unique name.
Download a Bundled Provisioning Profile
You can download a bundled provisioning profile from any RealPresence Group Series, RealPresence
Immersive Studio system, or HDX system that is registered with the RealPresence Resource Manager
system. After you download a provisioning profile for a specific endpoint, all dynamically-managed HDX
endpoints that you associate with this profile will receive the provisioning profile when the HDX system next
polls the RealPresence Resource Manager system for new provisioning information.
For more information about bundled provisioning profiles, see How Bundled Provisioning Works.
To download a bundled provisioning profile:
1 Go to Endpoint > Dynamic Management > Bundled Provisioning Profiles.
2 Click
.
The Download Bundled Provisioning Profile From an Endpoint dialog lists all of the HDX
systems and Group Series registered with the system, up to 500 endpoints.
3 As needed, click
to customize the endpoint list.
4 Select the endpoint that is configured the way you want for the bundled provisioning profile.
Polycom, Inc.
314
Using Bundled Provisioning Profiles
5 Complete the Bundled Provisioning Profile Name and Description fields.
6 Click Download.
The system confirms that the profile downloaded successfully.
7 Click OK.
After downloading a bundled profile, you should associate it with selected endpoints, see Edit a Bundled
Provisioning Profile.
View the List of Bundled Provisioning Profiles
Use the Bundled Provisioning View to see the list of bundled provisioning profiles available to dynamically
managed RealPresence Group Series, RealPresence Immersive Studio systems and HDX systems.
To view a list of bundled provisioning profiles:
1 Go to Endpoint > Dynamic Management > Bundled Provisioning Profiles.
By default the Bundled Provisioning Profile View displays the list of bundled provisioning profiles
available for use by dynamically managed HDX systems and RealPresence Group Series.
2 As needed, click
to customize the endpoint list. The filter provides the following options:
 Profile Name
 Model
Filters by the name of the bundled provisioning profile.
Filters by the endpoint model.
 Software Version
Filters by the software version of the endpoint.
 Creation Date Filters by the date the bundled provisioning profile was downloaded and created
on the system.
 Description
Filters by the description of the bundled provisioning profile.
The profile list in the Bundled Provisioning Profile View has the following information.
Field
Description
Profile Name
The name assigned to the bundled provisioning profile when it was downloaded and created
on the system.
Model
The exact model of endpoint to which the bundled provisioning profile applies as defined
when it was downloaded and created on the system.
Software Version
Displays the software version of the endpoint from which the bundled provisioning profile was
downloaded.
Creation Date
The date the bundled provisioning profile was downloaded and created on the system.
Description
The description assigned to the bundled provisioning profile when it was downloaded and
created on the system.
Device Count
The number of devices that are associated with the bundled provisioning profile.
Polycom, Inc.
315
Using Bundled Provisioning Profiles
Edit a Bundled Provisioning Profile
Users with the administrator role are allowed to edit bundled provisioning profiles. When you edit a bundled
provisioning profile you can rename the profile or change which devices are associated with the profile.
To edit a bundled provisioning profile:
1 Go to Endpoint > Dynamic Management > Bundled Provisioning Profiles.
2 As needed, click
to customize the list of profiles.
3 Select the profile that you want to edit.
4 Click
to view the Edit Bundled Provisioning Profile dialog box.
5 Use the Edit Bundled Provisioning Profile dialog to edit the profile and click OK.
Field
Description
General Settings
Name
Enter a name for the profile.
Description
Enter a description for the profile.
Associate Devices
Filter
This list of available devices automatically lists all dynamically-managed
devices of the same model and software version used for the bundled profile.
The Filter enables you to filter the list of available devices.
Available filters include:
Name: Type the first few letters of the system name and press Enter.
IP Address: Type the first numbers of the IP address of the device(s)
and press Enter.
Site: Type the first letters of the site name of which whose devices you
want to view and press Enter.
Available Devices
Lists the available devices to associate with this profile. Only devices that are
dynamically managed appear in the list.
Use the arrows to move a device or devices to the Selected Devices list.
Selected Devices
Lists the devices that have been selected to receive this profile.
Use the arrows to move a device or devices back to the Available Devices list.
Delete a Bundled Provisioning Profile
When you no longer need a bundled provisioning profile, you can delete it.
1 Go to Endpoint > Dynamic Management > Bundled Provisioning Profiles.
2 As needed, click
to customize the list of bundled provisioning profiles.
3 Select the profile you want to delete.
4 Click
.
5 Click Yes to confirm the deletion.
Polycom, Inc.
316
Using Bundled Provisioning Profiles
The system confirms that the profile was deleted.
Re-associate Devices with a Different Profile
Users with the administrator role can re-associate devices with a different bundled provisioning profile or no
bundled profile. For example, you could use this feature if you previously associated all RealPresence
Group 300 systems with a specific profile, but then downloaded an updated bundled provisioning profile that
you would like to use instead.
To re-associate devices with a different bundled provisioning profile:
1 Go to Endpoint > Dynamic Management > Bundled Provisioning Profiles.
2 Select the profile from which you want to remove the associated devices.
3 Click More > Re-associate Devices to view the Move Associated Devices dialog.
4 Choose a profile (or None) from the list to move the associated devices.
5 Click OK.
Settings included in a Bundled Provisioning Profile for
an HDX
The following tables lists the settings contained in a bundled provisioning profile for an HDX system.
Field
Home Screen Settings
System Name (Display)
Local Date and Time (Display)
System (Display)
Availability Control (Display)
My SIP (Display)
My IP (Display)
My ISDN (Display)
My Extension (Display)
Home Button (1-6)
Speed Dial (all)
Place a call
Last Number Displayed
Call Quality
Password Settings
Polycom, Inc.
317
Using Bundled Provisioning Profiles
Field
Admin Room
Minimum Length
Require Lower Case
Require Upper Case
Require Numbers
Require Special Characters
Reject Previous Passwords
Minimum Password Age in Days
Maximum Password Age in Days
Password Expiration Warning in Days
Minimum Changed Characters
Maximum Consecutive Repeated Characters
Can contain ID or its Reverse Form
Admin Remote
Minimum Length
Require Lower Case
Require Upper Case
Require Numbers
Require Special Characters
Reject Previous Passwords
Minimum Password Age in Days
Maximum Password Age in Days
Password Expiration Warning in Days
Minimum Changed Characters
Maximum Consecutive Repeated Characters
Can contain ID or its Reverse Form
User Room
Minimum Length
Require Lower Case
Require Upper Case
Require Numbers
Require Special Characters
Reject Previous Passwords
Minimum Password Age in Days
Maximum Password Age in Days
Password Expiration Warning in Days
Minimum Changed Characters
Maximum Consecutive Repeated Characters
Can contain ID or its Reverse Form
Polycom, Inc.
318
Using Bundled Provisioning Profiles
Field
User Remote
Minimum Length
Require Lower Case
Require Upper Case
Require Numbers
Require Special Characters
Reject Previous Passwords
Minimum Password Age in Days
Maximum Password Age in Days
Password Expiration Warning in Days
Minimum Changed Characters
Maximum Consecutive Repeated Characters
Can contain ID or its Reverse Form
Meeting
Minimum Length
Require Lower Case
Require Upper Case
Require Numbers
Require Special Characters
Reject Previous Passwords
Minimum Password Age in Days
Maximum Password Age in Days
Password Expiration Warning in Days
Minimum Changed Characters
Maximum Consecutive Repeated Characters
Can contain ID or its Reverse Form
Require Numbers: User Room
LDAP Settings
Enable LDAP Global Directory
Specify whether to allow endpoint systems to connect to the Polycom
RealPresence Resource Manager system LDAP directory, which includes both
local and enterprise users and groups.
If this check box is unchecked then the provisioned endpoint will not search the
Polycom RealPresence Resource Manager system LDAP directory. The
endpoint system will display groups and users local to endpoint.
LDAP Default Group
Specify a default contact group for the endpoints systems. Set to All or to a
specific local or enterprise group.
Account Management
Lock Account After Failed Logins: Admin
Account Lock Duration in Minutes: Admin
Lock Account After Failed Logins: User
Account Lock Duration in Minutes: User
Log Management
Polycom, Inc.
319
Using Bundled Provisioning Profiles
Field
Percent Filled Threshold
Log File Name
Folder Name
Transfer Frequency
Monitors
Monitor 1
Aspect Ratio
Video Format
Resolution
Output Upon Screen Saver Activation
Display Near Video
Display Far Video
Display Content
Monitor 2
Aspect Ratio
Video Format
Resolution
Output Upon Screen Saver Activation
Display Near Video
Display Far Video
Display Content
Monitor 3
Aspect Ratio
Video Format
Resolution
Output Upon Screen Saver Activation
Display Near Video
Display Far Video
Display Content
Display Copy of Monitor 1/2
Monitor 4
Aspect Ratio
Video Format
Resolution
Output Upon Screen Saver Activation
Loop Selected Camera to Monitor 4
People Video Adjustment
Content Video Adjustment
Dual Monitor Emulation
Display Icons in a Call
Screen Saver Wait Time
Polycom, Inc.
320
Using Bundled Provisioning Profiles
Field
PIP Timer
Multipoint Setup
Auto Answer Multipoint Video
Multipoint Mode
Cameras
Camera 1
Name
Aspect Ratio
Video Quality (Motion/Sharpness setting)
Source (People/Content setting)
Camera 2
Name
Aspect Ratio
Video Quality (Motion/Sharpness setting)
Source (People/Content setting)
Camera 3
Name
Aspect Ratio
Video Quality (Motion/Sharpness setting)
Source (People/Content setting)
Camera 4
Name
Aspect Ratio
Video Quality (Motion/Sharpness setting)
Source (People/Content setting)
Camera 5
Name
Aspect Ratio
Video Quality (Motion/Sharpness setting)
Source (People/Content setting)
Far Control of Near Camera
Backlight Compensation
Primary Camera
Camera Pan Direction
Quality Preference
Dynamic People/Content
Bandwidth
Power Frequency
SIP Settings
Enable SIP
Polycom, Inc.
Specify whether to enable SIP calls.
321
Using Bundled Provisioning Profiles
Field
Proxy Server
Specify the DNS name or IP address of the SIP Proxy Server. If you leave this
field blank, no proxy server is used.
By default, the SIP signaling is sent to port 5060 on the proxy server. To specify
a different port, add it to the address as shown here:
10.11.12.13:5070
Transport Protocol
Indicates the protocol the endpoint system uses for SIP signaling. The SIP
network infrastructure determines which protocol is required.
• Auto enables an automatic negotiation of protocols in the following order:
TLS, TCP, UDP. This is the recommended setting for most environments.
• TLS provides secure communication of the SIP signaling. TLS is available
only when the system is registered with a SIP server that supports TLS.
• TCP provides reliable transport via TCP for SIP signaling.
• UDP provides best-effort transport via UDP for SIP signaling.
Maximum Time in Call (minutes)
Enter the maximum number of minutes allowed for calls on the endpoint
systems.
When this time has expired, endpoint system users see a message asking
them if they want to hang up or stay in the call. If they do not answer within one
minute, the call automatically disconnects. If they choose to stay in the call at
this time, they will not be prompted again.
Set this value to 0 to remove any limit.
Recent Calls
Specify whether to display the Recent Calls button on the endpoint system’s
home screen. The Recent Calls page lists the site number or name, the date
and time, and whether the call was incoming or outgoing.
Note
If the Call Detail Report option is not selected, the Recent Calls option is not
available.
Screen Saver Wait Time
Specify how long the endpoint systems should remain awake during periods of
inactivity. The default is 3 minutes. Setting this option to Off prevents the
system from going to sleep.
Address Displayed in Global
Directory
Specify whether to display the endpoint systems’ public or private address in
the Global Address Book.
Send Content When PC
Connects
Camera Icon Category
People On Content
Foreground Source
Background Source
Polycom, Inc.
322
Using Bundled Provisioning Profiles
Field
Audio Settings
Sound Effects Volume
Sound Effects Volume
Incoming Video Call Tone
User Alert Tone
Mute Auto Answer Calls
Enable Live Music Mode
Mute Auto Answer Calls
Enable Live Music Mode
Enable Keyboard Noise Reduction
Enable Polycom Microphones
Enable Hawkeye Microphones
Audio Input
Content Input Level
Line Input Level
Line Input Type (Line, Mic)
Line Input Canceler Enable
Enable Phantom Power (for Mic Input mode)
Audio Output
Line Output Mode
Line Output Level
VCR/DVD Output Level
VCR/DVD Output On
Master Audio Volume
Bass
Treble
Stereo Settings
Enable Polycom StereoSurround
Stereo Auto Rotation (per Mic)
Mic Mode (Left, Left+Right, Right)
Polycom, Inc.
323
Using Bundled Provisioning Profiles
Settings included in a Bundled Provisioning Profile for
a RealPresence Group System and RealPresence
Immersive Studio System
The following tables lists the settings contained in a bundled provisioning profile for a RealPresence Group
system as well as RealPresence Immersive Studio systems.
Field
Monitors
Monitor 1
Enable
Video Format
Resolution
Monitor 2
Enable
Video Format
Resolution
Monitors
Monitor 1
Enable
Video Format
Resolution
Monitor 2
Enable
Video Format
Resolution
Sleep
Sleep
Display
Time before system goes to sleep
Video Inputs
General Camera
Settings
Allow other participants in a call to control your camera
Power Frequency
Make this camera your main camera
Input1: Main
Model
Name
Display As
Input Format
Optimized for
White Balance
Brightness
Color Saturation
Polycom, Inc.
324
Using Bundled Provisioning Profiles
Field
Input2: Main
Name
Display As
Input Format
Optimized for
Backlight compensation
White Balance
Brightness
Color Saturation
Audio
General Audio Settings
Polycom Stereo Sound
Sound Effects volume
Ringtone
User Alert Tones
Mute Auto Answer Calls
Enable Music Mode
Enable Keyboard Noise Reduction
Enable Polycom Microphones
Audio Input
Use 3.5 mm Input for Microphone
HDMI Input (left/right)
3.5 mm (left/right)
Audio Output
Line Output Mode
Levels
Master Audio Volume
Bass
Treble
Security > Local Accounts
Account Lockout
•
Lock User Account After Failed Logins
Login Credentials
•
•
•
Admin Room Password
User Remote Access Password
Require User Login for System Access
Password
Requirements
All password requirements for the following passwords:
• Admin Room
• User Room
• Meeting
• Remote Access
General Setting > Pairing > Polycom Touch Control
Enable Polycom Touch
Control
Polycom, Inc.
325
Using Access Control Lists
The Polycom® RealPresence® Resource Manager system enables you to create Access Control Lists for
dynamically managed endpoints.
This section describes RealPresence Resource Manager system Access Control List operations. It includes
these topics:
● Understanding Access Control Lists
● Using Access Control Lists in a Multi-Tenancy Environment
● Working with Access Control Lists
Understanding Access Control Lists
Users with the administrator, device administrator or area administrator role can create Access Control
Lists.
An access control list is a whitelist of users/groups whose endpoint(s) of a particular type are allowed to
authenticate with the RealPresence Resource Manager system for provisioning and video network services.
Access Control Lists can be used only with endpoints that are dynamically managed.
This is particularly useful when controlling Polycom’s soft endpoints such as RealPresence Desktop and
RealPresence Mobile which use provisioning credentials to authenticate with your video network.
You can use Access Control Lists to control access to the RealPresence Resource Manager system for the
following endpoint types:
● Polycom HDX systems
● Polycom RealPresence Group Series
● Polycom RealPresence Immersive Studio systems
● Polycom CMA Desktop
● RealPresence Desktop
● RealPresence Mobile (multiple device models)
● Polycom VVX systems
Implementing Access Control Lists
Once you create an Access Control List for an endpoint type, all users of that endpoint type must be included
on an Access Control List in order to access the RealPresence Resource Manager system for provisioning
and authentication.
In other words, if you create an Access Control List for an endpoint type and associate it with a user group,
only those members of that user group can access the RealPresence Resource Manager system for
provisioning and authentication.
Polycom, Inc.
326
Using Access Control Lists
If you do not create Access Control List for an endpoint type, then all users with that endpoint type are
allowed to access the RealPresence Resource Manager for provisioning and authentication.
For example, if you create an Access Control List that includes RealPresence Mobile systems, all users
of RealPresence Mobile endpoints must now be included on that Access Control List in order for their
endpoints to be provisioned and authenticate with your video network.
However, if you have not created an Access Control List for HDX systems, all users with HDX systems
managed by the RealPresence Resource Manager system can have their endpoints be dynamically
managed.
Plan Implementation of Access Control List
It’s important to plan your implementation of Access Control Lists. Use the following steps:
1 Determine an endpoint type of which you want to limit RealPresence Resource Manager system
access.
2 Determine which user groups you want to include in the Access Control List.
Using Access Control Lists in a Multi-Tenancy
Environment
You can associate an Access Control List with a specific area.
If you associate the Access Control List with a user group that is not in the same area as the assigned area
of the Access Control List, you will be prompted to allow the RealPresence Resource Manager system to
change the area of the group to match the area of the list.
If you move re-assign an Access Control List to a different area, you are prompted to allow the
RealPresence Resource Manager system to change the are of the group(s) to match the area of the list.
User groups associated with an Access Area List must reside in the same area as the list.
Working with Access Control Lists
This section describes how to work with Access Control Lists and includes the following topics:
● Add a New Access Control List
● Edit an Access Control List
● Delete an Access Control List
Polycom, Inc.
327
Using Access Control Lists
Add a New Access Control List
You can create an Access Control List that includes all endpoints of a particular device type(s) within a user
group. For example, you can create an Access Control List that enables all RealPresence Mobile users that
belong to a particular group to access the RealPresence Resource Manager for provisioning.
To add a new Access Control List:
1 Go to Endpoint > Dynamic Management > Access Control Lists.
The Access Control Lists page appears.
2 Click
.
3 In the Add Access Control List dialog box, complete the following fields in the General Info tab.
Field
Description
Access Control List Name
Enter a unique name for the Access Control List.
Description
Enter a description for the Access Control List.
Assign Area
If areas are enabled, and you have permission to manage more than
one area, use the Assign Area drop-down list to assign the Access
Control List to an area.
The drop-down list does not appear if areas are not enabled or the
user does not have permission to assign an area.
4 Click Associate Endpoint Types.
5 In the Associated Endpoint Types section, select and move the desired Available Endpoint
Types endpoint types(s) to Selected Endpoint Types list.
6 When you include a RealPresence Mobile endpoint, you need to also choose the endpoint model to
include in the Access Control List.
 In the Select the RealPresence Mobile device model section, select and move the desired
endpoint models to the Selected Endpoint Model list.
All endpoint models are included by default.
7 Click Associated User Groups.
8 Use the Search Group field to find the group(s) you want to associate with this Access Control List.
9 In the Search Results section, select and move the desired group(s) to Selected Groups list.
10 Click OK.
Edit an Access Control List
You can edit an Access Control List at any time. You can add or delete IP addresses or the groups
associated with the list. When you alter an access control list, the changes take place immediately.
To edit an Access Control List:
1 Go to Endpoint > Dynamic Management > Access Control Lists.
The Access Control Lists page appears.
Polycom, Inc.
328
Using Access Control Lists
2 Select an access control list.
3 Click
.
4 Modify any of the fields and click OK.
If you change the area of the access control list, you are asked to confirm that all groups associated
with the list will also be changed to the new area.
Delete an Access Control List
You can delete an access control list. Deleting an access control list may deny user groups associated with
the list access to RealPresence Resource Manager conferencing services. Remember to reassign any user
groups to a new access control list if you need them to continue to be able to authenticate.
To delete an access control list:
1 Go to Endpoint > Dynamic Management >Access Control Lists.
The Access Control Lists page appears.
2 Select an access control list.
3 Click
.
4 Click OK to confirm the deletion.
Polycom, Inc.
329
Dynamic Provisioning of Endpoints for
SIP Server Integration
The RealPresence Resource Manager system enables you to dynamically provision some Polycom
endpoints with the SIP server integration information by them with the SIP credentials and SIP settings they
need.
SIP settings can only be provisioned when you use dynamic management. You can provision SIP by using
both a Network provisioning profile and an Admin Config provisioning profile. You cannot use scheduled or
bundled provisioning to provision SIP settings.
For more information about network provisioning profiles, see Network Provisioning Profiles.
You can configure the RealPresence Resource Manager system to dynamically provision SIP settings for
the following SIP servers:
● Standard (a SIP server that meets SIP standards)
● Microsoft Lync
● BroadSoft BroadWorks
● Polycom RealPresence DMA system
● Siemens OpenScape
● Avaya Aura Session Manager
● Cisco Unified Communications Manager
You need to consider the following items when using SIP provisioning:
● SIP settings are configured using network provisioning profiles.
● If the SIP server uses a different authentication directory than your RealPresence Resource Manager
system and requires unique authentication for each endpoint, you need to ensure that users have
existing SIP URIs before provisioning SIP settings.
● Provisioning Microsoft SIP requires additional steps, see Provision Group for Microsoft Lync or
Microsoft Office Communications Server Integration.
This section includes the following topics:
● SIP Server Authentication Requirements
● Provisioning Endpoints with SIP Server Settings
SIP Server Authentication Requirements
You must understand your SIP server’s authentication requirements when you provision SIP settings for
endpoints managed by the RealPresence Resource Manager system.
SIP server authentication requirements differ according to your environment.
● If your SIP server does not require credentials, you do not need to indicate any credentials to use
when provisioning.
Polycom, Inc.
330
Dynamic Provisioning of Endpoints for SIP Server Integration
● If your SIP server requires a common username and password for all endpoints registering to the SIP
server, you need to explicitly provision that username and password to applicable endpoints.
● If your SIP server uses the same authentication database (i.e., Microsoft Active Directory) as the
RealPresence Resource Manager system, you need to use the RealPresence Resource Manager
system provisioning credentials.
● If your SIP server does NOT use the same authentication database as the RealPresence Resource
Manager system and requires unique usernames and passwords for each endpoint, you need ensure
that each user has an existing SIP URI before you can use Network provisioning profiles to provision
SIP settings.
Provisioning Endpoints with SIP Server Settings
The RealPresence Resource Manager system supports the integration with various SIP servers by
provisioning endpoints SIP settings they need.
After you provision endpoints with SIP settings, all endpoints receive directory information from one of those
servers. You are no longer using the enterprise directory or the other directory functions in the
RealPresence Resource Manager system.
The RealPresence Resource Manager system supports SIP to establish conference connections. If you
want to use SIP, you must enable it and configure SIP settings. You must also ensure that users have SIP
URIs.
To provision endpoints with the information required to integrate with these SIP servers, you must complete
the following tasks:
● Create Authentication Information for SIP Endpoints
● Import SIP URI Data
● Provision SIP Settings for SIP Server Integration
Create Authentication Information for SIP Endpoints
To have the RealPresence Resource Manager system dynamically provision a Polycom endpoint for SIP
integration, the endpoint must use the same credentials (username and password) to access both the SIP
server and the RealPresence Resource Manager system. Only then can the RealPresence Resource
Manager system provision SIP settings.
If the SIP server uses a third-party database for authentication that the RealPresence Resource Manager
system is not aware of, you need to import both the user information and SIP URI information from the SIP
server.
1 Create a RealPresence Resource Manager system local user account for the endpoint that matches
the username and password. To save time, you can import the users that you need, see Import
Local Users.
2 Import SIP URI data for those users, see Import SIP URI Data.
Import SIP URI Data
After you enable and configure SIP, you must import your endpoint SIP URI information from your SIP
server. The SIP URI is used as the endpoint’s address.
Polycom, Inc.
331
Dynamic Provisioning of Endpoints for SIP Server Integration
If you are using Microsoft as your SIP server, you do not need to import SIP URI
data. The RealPresence Resource Manager system can retrieve the SIP URI from
the enterprise directory.
To import SIP URI data:
1 Create a CSV file in the format described here. The import requires a CSV file in the following
format:
domain,username,deviceType,SIPURI,devicename
where:
 domain—Specifies the domain the user uses to log in to the RealPresence Resource Manager
system.
 username—Specifies the RealPresenceRealPresence Resource Manager system user name.
 deviceType—Specifies the device type (valid values are HDX, VVX, CMADesktop, RPMobile,
RPDesktop, GroupSeries or All_Types).
 SIP URI—Specifies the SIP URI for this user.
For example, this import reserves the SIP URI johndoe@example.com for all device types for the
John Doe user:
local,johndoe,All_Types,johndoe@example.com
2 From the RealPresence Resource Manager system, go to User > Users.
a Go to More > Import User Aliases.
b Navigate to the CSV file, select it, and click Open.
Whenever you add new users or rooms or need change a SIP URI, you must provide SIP URI data.
For the methods available for editing the SIP URI, see Editing SIP URI Data.
Editing SIP URI Data
You can edit SIP URI data in the following ways:
● Upload a CSV file that has changes or new data. Data in the CSV file is added to any existing data.
For information about the CSV file format and the upload process, see Import SIP URI Data.
● Edit individual users or rooms. For each RealPresence Resource Manager system user or room, you
can add or edit the SIP URI in the Dial String Reservations section of the Edit User or Edit Room
dialog.
Provision SIP Settings for SIP Server Integration
SIP settings are dynamically provisioned with a network provisioning profile. This procedure describes how
to change existing network provisioning settings so that they provision integration with a SIP server.
Be sure to enable SIP and configure the servers, protocol, and credentials needed for your SIP sever.
To provision SIP for integration with a SIP server:
1 Go to Endpoint > Dynamic Management > Provisioning Profiles.
2 Select the Network Provisioning Profile you want to edit and click
Polycom, Inc.
.
332
Dynamic Provisioning of Endpoints for SIP Server Integration
3 In the Edit Profile dialog, click SIP Settings and select these options.
Fields
Description
Enable SIP
Specify whether to enable SIP calls.
Automatically Discover SIP
Servers
The RealPresence Resource Manager system will issue a DNS query to locate
the SIP server and provision that information to endpoints.
Proxy Server
Specify the IP address or DNS name of the SIP proxy server for the network.
Backup Proxy Server
Specify the IP address or DNS name of a backup proxy server for the network.
Registrar Server
Specify the IP address or DNS name of the SIP registrar server for the network.
• In an Microsoft Office Communications Server 2007 or Microsoft Lync
Server 2010 environment, specify the IP address or DNS name of the Office
Communications Server or Lync Server server.
• If registering a remote HDX system with an Office Communications Server
Edge Server or Lync Server Edge Server, use the fully qualified domain
name of the access edge server role.
Backup Registrar Server
Specify the IP address or DNS name of a backup SIP registrar server for the
network.
Transport Protocol
Indicates the protocol the system uses for SIP signaling. The SIP network
infrastructure determines which protocol is required.
• Auto enables an automatic negotiation of protocols in the following order:
TLS, TCP, UDP. This is the recommended setting for most environments.
• TCP provides reliable transport via TCP for SIP signaling.
• UDP provides best-effort transport via UDP 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.
Server Type
Specify the SIP server type.
• Standard:
• Polycom:
• Avaya:
• BroadSoft:
• Cisco:
• Microsoft: If you are integrating with a Microsoft Server, you must also
provision a group for the endpoint, see Provision Group for Microsoft Lync
or Microsoft Office Communications Server Integration on page 334.
• Siemens:
Verify Certificate
Enable this option when the endpoint system’s certificate should be verified by
the certificate authority.
Use Endpoint Provisioning
Credentials
Enable this option when the endpoint system should use the credentials the
user entered at the endpoint to use for authenticate when registering with a SIP
registrar server.
Polycom, Inc.
333
Dynamic Provisioning of Endpoints for SIP Server Integration
Fields
Description
Common SIP User Name
Specify the name to use for authentication when registering with a SIP registrar
server, for example, msmith@company.com. If the SIP proxy requires
authentication, this field and the password cannot be blank.
Use Enterprise URI
Enable this option with the endpoint should use the SIP URI of the enterprise
user (domain user).
Common SIP Password
Specify the password that authenticates the system to the registrar server.
4 Click OK.
5 You need to ensure that you have created a provisioning rule that applies this network provisioning
profile to the intended site and endpoints.
Provision Group for Microsoft Lync or Microsoft Office
Communications Server Integration
You must set up the Microsoft Lync or Office Communications Server group that needs to be provisioned to
endpoints in each Admin Config provisioning profile. This controls the directory that endpoints can see.
You cannot provision integration with a Microsoft Lync or Office Communications Server via
scheduled provisioning. If the endpoint being provisioned is not capable of integration with a Microsoft
Lync or Office Communications Server, the endpoint will ignore this setting. The group setting here
applies to both Microsoft Lync and Office Communication Server.
To provision integration with Microsoft Lync or Office Communications Server:
1 Go to Endpoint > Dynamic Management > Provisioning Profiles.
2 In the Provisioning Profiles page, select the Admin Config profile of interest and click
.
3 In the Provisioning Fields dialog, click Microsoft Lync Settings and enter a Group Name.
The Group Name is the group set in the Microsoft Lync Server or Office Communication Server.
4 Click OK.
Microsoft Directory Considerations
When Polycom endpoints are registered with a Microsoft Lync Server or Office Communications Sever, the
SIP server replaces the RealPresence Resource Manager system as the presence and directory service
provider. However, the system continues to act as manager for these endpoint systems.
If you want your directories to include endpoints such as CMA Desktop that are not registered to the
Microsoft SIP server, you need to select Standard as your SIP server when provisioning settings.
You still need to use the RealPresence Resource Manager system provisioning credentials when
provisioning the SIP settings to the endpoint.
Polycom, Inc.
334
Using Zero-Touch Provisioning
The RealPresence Debut can connect to the network via DHCP and if it can find the RealPresence
Resource Manager system, it will dynamically be provisioned according to any dynamic provisioning rules
and profiles you have created.
Because dynamic provisioning rules are used to apply provisioning profiles, you must ensure that endpoints
are associated with room or user accounts before provisioning can take place. You can do this automatically
by configuring your settings or by manually associating an endpoint with a room or user account.
This section includes the following topics:
● Configure your DHCP Server
● Configure Zero Touch Provisioning Settings
● Manually Associate an Endpoint’s Serial Number with a Room or User
Configure your DHCP Server
Configure your DHCP server to be aware of the RealPresence Resource Manager system’s IP address, if
you wish it to resolve queries for the RealPresence Resource Manager by the RealPresence Resource
Manager’s host name or IP address.
You can use the default available option of “066 Boot Server Host Name” or add a custom option.
If you choose to use a custom option, you need to update the provisioning page of the RealPresence Debut
system. See the RealPresence Debut System Administrator’s Guide for more information.
To configure your DHCP server:
1 Login to the DHCP server and navigate to the Server Options page.
2 Find the default Available Option 066 Boot Server Host Name and add the string value of the
RealPresence Resource Manager system’s IP address. The default format is
https://<user>:<password>@ip_address.
Configure Zero Touch Provisioning Settings
In order to be provisioned by zero-touch provisioning, an endpoint must be associated with a room or user
account. You can configure your system to automatically create this account when the endpoint
auto-discovers the RealPresence Resource Manager system via DNS.
The automatic association you configure cannot create accounts in an enterprise directory. If you want to
associate provisioned endpoints with enterprise room or user accounts, you need to make the association
manually.
Polycom, Inc.
335
Using Zero-Touch Provisioning
To configure Zero Touch Provisioning Settings:
1 Go to Endpoints > Dynamic Management > Zero Touch Provisioning Bindings.
2 Click
.
3 In the Settings dialog, mark the autoGenerate check box.
4 In the Default Language drop-down list, select a language to use.
5 Click OK.
Manually Associate an Endpoint’s Serial Number with
a Room or User
To take advantage of zero touch provisioning, you must ensure that each endpoint is associated with a room
or user account. You can also manually associate the endpoint with an existing account if you did not
configure your system to automatically create this account when the endpoint auto-discovers the
RealPresence Resource Manager system via DHCP.
Alternatively, you can set up the RealPresence Resource Manager system to automatically add a room
account (and the associated machine account) when an endpoint discovers the RealPresence Resource
Manager system via DHCP.
To associate an endpoint with a room or user:
1 Go to Endpoints > Dynamic Management > Zero Touch Provisioning Bindings.
2 Click
.
3 Enter the serial number of the RealPresence Debut system you want to provision.
4 Select a room or user to associate with the endpoint.
a Click Select.
b Click
.
c In the Search Users and Rooms field, enter the name of the user of interest.
Searches for a user are case-insensitive, prefix searches of the Username, First Name, and Last
Name fields. You must be logged into the system as an enterprise user in order to search for
enterprise users.
d Select the user to associated and click OK.
5 In the Add dialog, click OK.
6 If there is not a machine account already associated with the user you selected, you are prompted to
create one.
See Adding Machine Accounts for more information.
Enable Calendaring Service
In order for the RealPresence Debut to use the calendaring feature, it must use an Active Directory
credentials to communicate with the RealPresence Resource Manager system.
After the initial zero-touch provisioning, you must log in to the RealPresence Debut system’s administrator
interface to change the account used for provisioning to an Active Directory account.
Polycom, Inc.
336
Using Zero-Touch Provisioning
See the RealPresence Debut System Administrator Guide for more details.
Polycom, Inc.
337
Enable Polycom® Concierge
You can dynamically provision RealPresence Desktop, RealPresence Mobile, and RealPresence Group
Series with Polycom® Concierge features. When provisioned with Polycom Concierge features,
RealPresence Desktop and RealPresence Mobile clients offer additional functionality to allow users to pair
with room system and join and control multi-party video conferences.
Polycom Concierge features are available only if your video conferencing environment also includes a
Polycom RealPresence Web Suite instance that has been licensed for Enhanced Content. RealPresence
Web Suite provides the foundation for the application services layer that supports real-time collaboration
services that include meeting controls and enhanced content sharing.
Polycom Concierge allows RealPresence Mobile and RealPresence Desktop users to pair with a
RealPresence Group Series and use “click to dial” on the room system from their personal calendar, carry
out basic endpoint control operations, and view a list of meeting participants and controls. Additionally
RealPresence Desktop clients allow users to send and receive content when in a meeting.
To enable this feature, your video conference environment must also include the following Polycom
systems:
● A Polycom RealPresence Web Suite instance that is licensed for Enhanced Content.
● A Polycom RealPresence DMA system integrated with your RealPresence Resource Manager
system and RealPresence Web Suite.
Polycom Concierge is only available for conference participants for conferences that are scheduled
on the RealPresence DMA system.
To enable the Polycom Concierge solution in your environment, you must do the following in the
RealPresence Resource Manager system:
1 Integrating with Active Directory.
2 Configuring the Calendar Connector.
3 Configure your system with RealPresence Web Suite.
4 Dynamically Provisioning Polycom Concierge Features.
5 SmartPairing for RealPresence Mobile and RealPresence Desktop Systems.
Integrating with Active Directory
Polycom Concierge relies on the RealPresence Resource Manager system to be integrated with Active
Directory so that room accounts and user accounts are connected with Microsoft Exchange for calendaring.
For details on how to integrate your system with Active Directory, see Integrating with an Enterprise
Directory
Polycom, Inc.
338
Enable Polycom® Concierge
Configuring the Calendar Connector
You can enable the RealPresence Resource Manager system to deliver accurate calendar information to
endpoints by configuring the Calendar Connector.
For details on how to configure the Calendar Connector, see Calendar Connector.
Configure your system with RealPresence Web Suite
RealPresence Web Suite Pro with Enhanced Content is used to assist endpoints with Polycom Concierge
content sharing and call control. You must configure your RealPresence Resource Manager system with
the network location of your RealPresence Web Suite server.
To configure the location of RealPresence Web Suite:
1 Go to Endpoint > Dynamic Management > Web Suite Server & Beacon.
2 In the Web Suite Server Address field, enter the server address of the RealPresence Web Suite
server.
3 Click OK.
Dynamically Provisioning Polycom Concierge
Features
You need to create provisioning profiles and rules for the endpoints that you want to configure to use
Polycom Concierge.
Endpoints need to be configured for calendaring, which is specified with an Admin Config profile.
Within the Network Config file, you need to enable calendaring and Polycom Concierge.
Configuring dynamic provisioning includes the following tasks:
● Enable Dynamic Provisioning of Polycom Concierge
● Enable Calendaring for Dynamically Provisioned Endpoints
● Enable Dynamic Provisioning of the Calendar Connector
Enable Dynamic Provisioning of Polycom Concierge
For endpoints to use Polycom Concierge, you must enable dynamic provisioning of Polycom Concierge.
You do this in the Network Config profile for the endpoints.
To dynamically provision Polycom Concierge features:
1 Go to Endpoint > Dynamic Management > Provisioning Profiles.
2 Select the Network profile you want to use or create a new one.
3 Click
.
4 In the Edit Profile dialog box, select the Concierge Settings section.
5 Mark the Enable Concierge Service check box.
Polycom, Inc.
339
Enable Polycom® Concierge
6 Click OK to save the profile.
Enable Calendaring for Dynamically Provisioned Endpoints
You need to include the calendaring feature in any Admin Config profiles used for endpoints that you want
to enable with Polycom Concierge.
For more information about creating dynamic provisioning profiles and rules, see Overview of Dynamic
Management Setup.
To enable calendaring:
1 Go to Endpoint > Dynamic Management > Provisioning Profiles.
2 Select the Admin Config profile you want to use or create a new one.
3 Click
.
4 In the Edit Profile dialog box, select Calendar Settings.
5 Mark the Enable Calendaring check box.
6 Click OK to save the profile.
Enable Dynamic Provisioning of the Calendar Connector
In order to use the Calendar Connector, endpoints must be configured to use the RealPresence Resource
Manager system as a proxy for their connection to Microsoft Exchange.
You should dynamically provision this setting in the appropriate network provisioning profile.
To provision the Calendar Connector:
1 Go to Endpoint > Dynamic Management > Provisioning Profiles.
2 Select the Network profile you want to use and Click
.or create a new one.
3 In the Edit Profile dialog box, select Calendaring Settings.
4 In the Calendaring Settings section, do the following:
a Mark the Specify Exchange Server check box.
b In the Exchange Server field, enter the FQDN of the RealPresence Resource Manager system.
5 Click OK to save the profile.
SmartPairing for RealPresence Mobile and
RealPresence Desktop Systems
You will need to ensure that RealPresence Mobile or RealPresence Desktop users will have the information
they need to pair with a RealPresence Group Series system when they enter the room. You can do this by
programming a beacon for the room and ensuring the pairing code and QR code is in the conference room
where the RealPresence Group Series system resides.
Before you can ensure pairing, you must have dynamically provisioned the RealPresence Group Series
system or HDX system with Polycom Concierge.
Polycom, Inc.
340
Enable Polycom® Concierge
This section includes the following sections:
● Program the Beacon
● Generate SmartPairing Information for RealPresence Group Series Systems
● Change the Beacon UUID
Program the Beacon
You can install a Bluetooth beacon in conference room where the endpoint resides. Typically, this can be a
USB beacon placed in one of the USB ports of the room system. You’ll need to configure the beacon with
the appropriate identifying information of the endpoint.
How you enter the beacon configuration information varies according to the type of beacon you are using.
However the information is the same for all beacons. You will need a UUID, a major ID and a minor ID.
You need to use the RealPresence Resource Manager system to look up associated beacon ID
components (UUID, Major ID and Minor ID) for an endpoint before programming your beacon with that
information. The major and minor IDs are automatically generated for the endpoint when it is managed by
the RealPresence Resource Manager system.
To look up the major and minor IDs:
1 Go to Endpoint > Monitor View and navigate to the endpoint that associated with the room where
the beacon will reside.
2 After selecting the desired endpoint, click
and expand the Beacon ID pane on the right side of
the screen to view the Beacon ID information.
The Beacon ID information includes the following:
Filed
Description
Proximity ID
This is the UUID the same for each endpoint and needs to be the same for each
beacon within your deployment.
Major ID
This ID is automatically generated and is unique to the endpoint. Enter this
number as the major ID for the respective beacon associated with the room
where the endpoint resides.
Minor ID
This ID is automatically generated and is unique to the endpoint. Enter this
number as the minor ID for the respective beacon associated with the room
where the endpoint resides.
3 Write down the respective ID information so you can use it to program your beacon. Consult your
beacon documentation for information about how to configure your beacon with the ID information.
Generate SmartPairing Information for RealPresence Group Series
Systems
You can generate and print pairing document to display in the conference rooms that are enabled for
Polycom Concierge. The generated document can should be saved to your network for safekeeping before
printed and placed in the room where the endpoint resides.
Polycom, Inc.
341
Enable Polycom® Concierge
The document includes information for three different ways for users to pair with the room.
QR Code
Graphical code that can be scanned by mobile applications to pair the
device with the room system.
Used by RealPresence Mobile users.
Pairing Code
Pairing code that users can manual enter to pair their client with the room
system.
Used by RealPresence Desktop users or RealPresence Mobile users.
Polycom Concierge Service URL
If you do not have RealPresence Mobile or RealPresence Desktop, you
can instead visit this URL in a browser to join a conference and share
content from your device:
Before you can generate a QR code, you must have dynamically provisioned the RealPresence Group
Series or HDX system with Polycom Concierge.
To set up and generate a QR code to pair a device with a Polycom endpoint:
1 Go to Endpoint > Monitor View.
2 As needed, click
to filter the Endpoint list.
3 Select the endpoint of interest and click More > Generate QR Code.
The QR Code sheet appears in a new browser window.
4 Use your browser tools to print the QR code sheet.
5 Optionally, use your browser tools to save a copy of the sheet to an archive location.
6 Ensure that the document is placed prominently in the associated room.
Change the Beacon UUID
In some cases, you may want to change the default UUID generated by the RealPresence Resource
Manager system. If you change this ID, you must ensure that each of your deployed beacons are configured
with the new ID.
The UUID on the beacon used for the Polycom room system (RealPresence Group Series system or HDX)
must match the UUID in the RealPresence Resource Manager system.
To change the beacon proximity ID:
1 Use a UUID-generating tool to generate a new UUID for your beacon. Consult your beacon
documentation for details on how to do this. It varies according to the type of beacon you are using.
2 Within theRealPresence Resource Manager, go to Endpoint > Dynamic Management > Web
Suite Server & Beacon.
3 In the Beacon field, enter the new ID. The ID format should be in the standard UUID format.
4 Click Update.
Polycom, Inc.
342
Dynamically Managing a RealPresence
Access Director System
The Polycom® RealPresence® Resource Manager system enables you to dynamically manage a
RealPresence Access Director system.
You can use a RealPresence Access Director server provisioning profile to dynamically manage the
RealPresence Access Director system and configure it with the right network information to allow for firewall
traversal in your video infrastructure environment.
This section describes RealPresence RealPresence Resource Manager system RealPresence Access
Director system provisioning operations. It includes these topics:
● Creating a Site for the RealPresence Access Director System
● Create a RealPresence Access Director Server Provisioning Profile
● Creating a Network Provisioning Profile for Endpoints
● Creating a Provisioning Rule and Associate it with All Related Profiles
● Creating a User Account for the RealPresence Access Director System
● Available Settings for RealPresence Access Director Server Provisioning Profile
Creating a Site for the RealPresence Access Director
System
You should create a site that includes the subnet on which the RealPresence Access Director resides. You’ll
need to add the RealPresence Access Director system’s internal IP to the subnet of the site.
See Add a Site for more information about adding a site.
You cannot use the same site for more than one RealPresence Access Director system. You must
create a unique site for each RealPresence Access Director system that you use.
Create a RealPresence Access Director Server
Provisioning Profile
You can dynamically provision a RealPresence Access Director system with the RealPresence Access
Director server provisioning profile.
A RealPresence Access Director server provisioning profile includes all applicable settings for a
RealPresence Access Director system.
The RealPresence Access Director system should be configured with the IP addresses of the Polycom
RealPresence DMA system as the gatekeeper and the SIP server within your environment.
Polycom, Inc.
343
Dynamically Managing a RealPresence Access Director System
With RealPresence Access Director server provisioning profiles, you can ensure that an RealPresence
Access Director system has the optimal and correct firewall traversal settings to support endpoints that will
depend on it for firewall traversal.
As soon as an RealPresence Access Director system is configured to use the RealPresence Resource
Manager for its provisioning server, it starts polling for provisioning profile updates. To ensure out-of-box
usability, the RealPresence RealPresence Resource Manager system comes with a default RealPresence
Access Director Server provisioning profile.
The default RealPresence Access Director server provisioning profile cannot be associated with any
provisioning rules. You must add a new RealPresence Access Director server provisioning profile in order
to customize the settings of your RealPresence Access Director system.
To create a RealPresence Access Director provisioning profile:
1 Go to Endpoint > Dynamic Management > RPAD Server Provisioning Profiles.
2 Click
.
3 In the General Info section of the Add New Profile section,
 Enter a name for the new RealPresence Access Director server provisioning profile.
 Select Server Provisioning Profile from the drop-down list.
4 As needed, edit the server provisioning details and click Apply.
5 Click OK.
See Available Settings for RealPresence Access Director Server Provisioning Profile.
Creating a Network Provisioning Profile for Endpoints
You need to create a network provisioning profile to apply to all dynamically managed endpoints within the
same site as a RealPresence Access Director system. These endpoints need to be provisioned to use the
RealPresence Access Director system external IP address for all of their network settings.
Ensure that all network settings (gatekeeper, presence server, SIP server, and directory) are set to the
external IP address of the RealPresence Access Director system.
For example, instead of the IP address of the RealPresence DMA system’s gatekeeper, provision endpoints
to use the external IP address of the RealPresence Access Director system as the gatekeeper IP.
For more information about creating a network provisioning profile, see Network Provisioning Profiles.
Creating an Admin Config Provisioning Profile
If you want to provision the endpoints that use the RealPresence Access Director system with specific
admin configuration settings, you can create an Admin Config profile to use.
For information about creating Admin Config provisioning profiles, see Admin Config Provisioning Profiles.
Polycom, Inc.
344
Dynamically Managing a RealPresence Access Director System
Creating a Provisioning Rule and Associate it with All
Related Profiles
You need to create a provisioning rule that includes a condition that defines the rule to be applied to the site
that includes the RealPresence Access Director system.
For example,(Site.Site = RealPresence Access Director Site)
At a minimum, the provisioning rule must contain this site condition.
Associate both the RealPresence Access Director Server Provisioning profile and the Network
Provisioning profile (for endpoints) with the rule. You can also include an Admin Config profile if needed.
This ensures that all endpoints within the subnet of the site created for the RealPresence Access Director
are provisioned with the correct settings. It also provisions the RealPresence Access Director system.
For detailed instructions on how to create a provisioning rule, see Creating Dynamic Provisioning Rules.
Creating a User Account for the RealPresence Access Director System
You need to create a user account for RealPresence Access Director system in order to authenticate with
the RealPresence Resource Manager system’s provisioning service.
For more information about creating user accounts, see Managing Users.
Use this account to register the RealPresence Access Director system with the RealPresence Resource
Manager system’s provisioning service.
See the Polycom RealPresence Access Director System Administrator’s Guide for more information about
provisioning the RealPresence Access Director system.
Available Settings for RealPresence Access Director
Server Provisioning Profile
Field
For the RealPresence Access Director system being provisioned...
RPAD Settings
Time Server
Specify whether to connect to a time server for automatic system time settings.
Currently, the RealPresence Access Director system can be provisioned only with a
Manual setting. If you use the Auto setting, the RealPresence Access Director system
will behave as if the Time Server is set to Off.
Select Manual to require that the RealPresence Access Director system synchronize
with an external time server that may not be identified by a network domain controller. In
this case, you must also enter the IP address of the time server in the Time Server
Address field.
If Time Server is set to Off, or if the Time Server is set to Manual but the endpoint
system cannot connect to the time server, the date and time must be manually reset at
the endpoint.
Primary Time Server
Address
Specify the address of the primary time server when Time Server is set to Manual.
Polycom, Inc.
345
Dynamically Managing a RealPresence Access Director System
Field
For the RealPresence Access Director system being provisioned...
Secondary Time
Server Address
Specify the address of the secondary time server when Time Server is set to Manual.
Provisioning Polling
Interval
Specify the frequency at which the RealPresence Access Director system polls the
RealPresence RealPresence Resource Manager system for new provisioning
information.
By default, this interval is 60 minutes. For performance reasons, the minimum positive
value for this interval is 5 minutes. There is no maximum value enforced.
Heartbeat Posting
Interval
Specify the frequency at which the RealPresence Access Director system poll the
RealPresence Resource Manager system for a heartbeat.
Server Status Posting
Interval
RPAD Settings 2
Enable IP H.323
Configure the system to enable or disable H.323 signal forwarding.
Gatekeeper IP
Address
When Use Gatekeeper is set to Specify, enter the gatekeeper IP address in this field.
The IP address of the internal gatekeeper that the system forwards to when endpoints
behind the system send gatekeeper registration or H.323 call requests.
Enable SIP
Specify whether to enable SIP calls and enable the provisioning of SIP settings.
Configures the system to enable or disable SIP signal forwarding.
Proxy Server
Specify the IP address or DNS name of the internal SIP proxy server that the system
forwards to when endpoints behind the system send SIP call requests.
Enter the RealPresence DMA signaling IP address in this field.
Registrar Server
Specify the IP address or DNS name of the internal SIP registrar server that the system
forwards to when endpoints behind the system send SIP registration requests.
Enter the RealPresence DMA signaling IP address in this field.
Use Default Directory
Server
Not provisionable in RealPresence Resource Manager system v8.2.
Directory Server
Not provisionable in RealPresence Resource Manager system v8.2.
Use Default Presence
Directory Server
Not provisionable in RealPresence Resource Manager system v8.2.
Presence Server
Not provisionable in RealPresence Resource Manager system v8.2.
Verify Certificate
Enable this option when the RealPresence Access Director system’s certificate should
be verified by the certificate authority.
Polycom, Inc.
346
Phone Management
This section provides an introduction to the Polycom® RealPresence® Resource Manager system audio
endpoint management functionality and operations. It includes:
Managing Audio Phones
Polycom, Inc.
347
Managing Audio Phones
The RealPresence Resource Manager system can be used as a central provisioning server for supported
phones. When a phone is provisioned, it polls the RealPresence Resource Manager system for
configuration profile settings and software updates at intervals that you define. You can remotely control the
configuration settings and software version of the phone, according to the conditions that you define. The
RealPresence Resource Manager system communicates with audio phones via HTTP or HTTPS.
Polycom recommends you to use the HTTPS protocol, especially when manging over 400 phones to
enhance the performance.
This section includes the following topics:
● Overview of Phone Management Setup
● Supported Phones and Call Servers
● Managing Audio Phones
● Working with Phone Configuration Profiles
● Audio Phone Configuration Profile Deployment
● Register Phones to a SIP server
● Monitor Phones Behind Firewall
● Working with Resource Files
● Working with Phone Software Updates
● Working with CUCM
● Configure Your Phone Management Settings
Overview of Phone Management Setup
Setting up phone management is a multistep process that may include the following tasks:
● Adding phones to the RealPresence Resource Manager system.
● Setting up configuration profiles.
● Deploying configuration profiles to phones per conditions.
● Setting up software updates.
● Registering phones to a SIP server.
● Setting up phone management settings.
Polycom, Inc.
348
Managing Audio Phones
Supported Phones and Call Servers
RealPresence Resource Manager supports standard SIP servers and the following Polycom audio phones:
RealPresence Resource Manager can only integrate with Cisco Unified Communications Manager
Supported Phones Types and Models
Audio Phone Type
Audio Phone Model
VVX
VVX 101
VVX 201
VVX 300
VVX 301
VVX 310
VVX 311
VVX 400
VVX 401
VVX 410
VVX 411
VVX 500
VVX 501
VVX 600
VVX 601
VVX 1500
SoundStation
SoundStation IP 5000
SoundStation IP 6000
SoundStation IP 7000
SoundStation Duo
SoundPoint
SoundPoint IP 321
SoundPoint IP 331
SoundPoint IP 335
SoundPoint IP 450
SoundPoint IP 550
SoundPoint IP 560
SoundPoint IP 650
SoundPoint IP 670
SoundStructure VoIP Interface
SoundStructure VoIP Interface
RealPresence Trio
RealPresence Trio 8800
RealPresence Trio Visual+
Polycom, Inc.
349
Managing Audio Phones
Managing Audio Phones
Phones can be added to the RealPresence Resource Manager system via the following ways:
● Adding phones automatically, see Automatically Added Phones.
● Adding phones manually, see Add a Phone Manually.
● Adding phones by importing a CSV file, see Import the CSV File and View the Import Details.
● Adding phones by syncing with a CUCM server, see Working with CUCM.
All the added phones can be monitored and managed from the Endpoint > Monitor View page. From this
page, you can:
● View phone’s information, see View the Endpoint List.
● View phone’s detail information, see View Endpoint Details.
● Edit phones, see Edit an Audio Phone.
● Delete phones, see Delete an Audio Phone.
● Reboot phones, see Reboot an Endpoint.
● Go to phone’s Web GUI, see Manage an Endpoint.
● Set Active Directory Password
● Control Call Remotely
● Monitor Phones Behind Firewall
Automatically Added Phones
Phones connected via Intranet can be added to the RealPresence Resource Manager system automatically
via the HTTP/HTTPS protocol.
Phones behind a firewall, Polycom recommends you to use HTTPS to connect to a RealPresence Resource
Manager system.
When a phone is online and connects to the RealPresence Resource Manager system, the phone is
provisioned by the system.
You can find automatically added phones by viewing the Mode
View page.
information on the Endpoint > Monitor
When a phone is automatically added to the RealPresence Resource Manager system and then the
same phone (with the same MAC address) is synced from CUCM, the phone becomes a synced
CUCM phone. If this phone is removed from CUCM, it is also removed from the RealPresence
Resource Manager system.
Configure Automatically Added Audio Phones for
Provisioning
To use the RealPresence Resource Manager system as phones’ provisioning service, you usually need to
configure some settings via the phone’s web interface.
Polycom, Inc.
350
Managing Audio Phones
To configure automatically added audio phones for provisioning:
● Select HTTP or HTTPS as the transport protocol for phones using the Intranet. Select HTTPS as the
transport protocol for phones behind firewall.
● When selecting HTTPS, you need a public certificate installed on theRealPresence Resource
Manager system for HTTPS to work without loading the private CA, or you can disable the Common
Name Validation on the phone as the self-signed certificate is trusted by the phones.
● Specify the RealPresence Resource Manager system address in the following format:
RPRM_Address/phoneservice/configfiles
For example, your RealPresence Resource Manager system address is 172.21.125.243. You need
to use “172.21.125.243/phoneservice/configfiles” as the server address.
● Specify the provisioning account and password configured on the Endpoint > Phone Management
> Phone Management Setting page. See Configure Your Phone Management Settings for details.
The way to configure RealPresence Trio Visual+ is different from other phones. Please refer to the
Polycom RealPresence Trio User Guide for more information.
Editing Automatically Added Phones
After a phone is discovered and added to the RealPresence Resource Manager system, a user with the
device administrator role can edit its settings. After manually editing an auto-added phone, the mode of this
phone will become Manually Added Phones.
For information on editing automatically added phones, see Edit an Audio Phone for details. You also can
export all the auto-added phones to a CSV file, edit phones information in a batch, and then import the CSV
into the RealPresence Resource Manager system. See Export and Edit Phones on how to edit phones in a
CSV file.
Add a Phone Manually
Phones can be added one by one on the Endpoint > Monitor View page.
To add an audio phone to the system:
1 Go to Endpoint > Monitor View and click
.
2 In the Add New Endpoint dialog, select phone type that you want to add in the Endpoint Type
drop-down list.
3 Specify the MAC address and the system name of the phone.
4 In the Line Address tab, click
to add line information by specifying SIP URI, Display Name,
Digest Account, and Digest Password if needed in the Lines Information dialog.
5 (Optional) On the Endpoint Group Association tab, select the endpoint group to associate with
and click Apply.
Click the arrow icon to adjust the priority of endpoint groups. The arrow icons appear when the cursor
stays on an endpoint group.
See Working with Endpoint Groups for details about endpoint group.
Polycom, Inc.
351
Managing Audio Phones
6 (Optional) On the Configuration Profile Association tab, select the configuration profile to
associate with and click Apply.
Click the arrow icon to adjust the priority of configuration profiles. The configuration profiles set on
device level always has higher priority.
See Working with Phone Configuration Profiles for details on configuration profile.
7 Click OK.
Edit an Audio Phone
You can edit manually added, automatically added, or imported phones.
Polycom does not recommend that you change the line information of CUCM synced phones from the
RealPresence Resource Manager system since the changes will be overwritten at the next CUCM sync
interval.
To edit an audio phone:
1 Go to Endpoint > Monitor View.
2 Click
, select Mode, and select one of the following modes to filter phones that you want to edit:
 Auto-added Phones
 Manually Added Phones
3 Select a phone and click
.
4 Edit the phone and line information as needed.
All the line information is listed in the Line Address tab.
Provisioning Line indicates how this line is created. If the line is created from phones, Provisioning
Line is False. If the line is created by RealPresence Resource Manager admin, Provisioning Line
is True.
If you change the line information of an auto-added phone, the Provisioning Line value will change
from False to True.
5 Do one of the following:
 Click Apply to apply the changes including the line information and configuration profiles changes
to the online phone now. This operation may reboot the phone.
If the phone is offline or the phone is behind firewall, Apply is not displayed.
 Click OK to wait for the updates to take effect at the next polling interval.
Change Endpoint Group Association
When you edit an audio phone, you can associate it with an endpoint group, delete its association with an
endpoint group, or prioritize multiple associated endpoint groups.
To change the association from an audio phone to an endpoint group:
1 Go to Endpoint > Monitor View.
2 Click the endpoint name that you want to edit from the Endpoint Name column.
Polycom, Inc.
352
Managing Audio Phones
3 In the Edit Device dialog box, click the Endpoint Group Association tab.
 To associate the endpoint to an endpoint group, select the name of the endpoint group from the
drop-down list and click Add.
 To delete the association, click
at the right end of each line of the endpoint group list.
 To prioritize an association, click the
the lowest or highest priority.
buttons to deprioritize or prioritize it, or give it
4 Click Apply or OK.
Change Configuration Profile Association of Audio
Phones
When you edit an audio phone, you can associate it with a configuration profile, delete its association with
a configuration profile, or prioritize multiple associated configuration profiles.
To change the association between audio phone and configuration profile:
1 Go to Endpoint > Monitor View.
2 Click the audio phone’s name that you want to edit from the Endpoint Name column.
3 In the Edit Endpoint dialog box, click the Configuration Profile Association tab.
 To associate the audio phone to a configuration profile, select the profile’s name from the
drop-down list and click Apply.
 To delete the association, click
at the right end of each line of the configuration profiles list.
 To prioritize an association, click the
the lowest or highest priority.
buttons to deprioritize or prioritize it, or give it
4 Do one of the following:
 Click Apply to apply the configuration profiles changes to the online phone now. This operation
may reboot the phone.
If the phone is offline or the phone is behind firewall, Apply is not displayed.
 Click OK to wait for the updates to take effect at the next polling interval.
Delete an Audio Phone
You can only delete manually added or imported phones. Phones synced from the Cisco Unified
Communications Manager system cannot be deleted manually.
To delete an audio phone:
1 Go to Endpoint > Monitor View.
2 Select a manually added phone.
3 Click
.
4 Click Delete to confirm the deletion.
Polycom, Inc.
353
Managing Audio Phones
Set Active Directory Password
You can set an AD (Active Directory) password to the phones that are provisioned by the RealPresence
Resource Manager system.
You can only set an AD password for Polycom audio phones that support REST API, such as RealPresence
Trio and Polycom VVX phones.
To set AD password:
1 Go to Endpoint > Monitor View.
2 Click
to select one or more phones to set an unified AD password.
3 Click More > Change Phone AD Password.
4 Enter a new password.
5 Click OK.
Control Call Remotely
You can control a provisioned phone to make a call in the RealPresence Resource Manager system.
This feature is supported by Polycom RealPresence Trio and Polycom VVX phones that support REST API.
To control call remotely:
1 Go to Endpoint > Monitor View.
2 Select a supported phone.
3 Click More > Remote Call Control.
4 Enter the destination SIP URI or phone number in the Remote Call dialog.
5 Click OK.
Import Audio Phones Using CSV Files
You can import audio phones into your RealPresence Resource Manager system via CSV files.
To import audio phones using CSV file:
1 Create a CSV File Containing the Audio Phone Information You Need.
2 Import the CSV File and View the Import Details
Create a CSV File Containing the Audio Phone Information
You Need
You must create a CSV (comma separated values) file that contains the audio information that you need.
You can create this file with any plain text editor or use Microsoft Excel.
The format should be the following:
Polycom, Inc.
354
Managing Audio Phones
MAC Address,Endpoint Name,Endpoint Type,Endpoint Model,Owner,Endpoint Group(s),Line
Index,SIP URI,Display Name,Digest Account,Digest Password
Guidelines
Use the following guidelines:
● MAC Address is a mandatory field.
● If an imported phone record contains line information, the Line Index and SIP URI field must have a
value. A phone record without line information is also allowed.
● Commas (,) are used as field separators and cannot be embedded in a field.
● The values of the Endpoint Type and Endpoint Model fields must strictly follow the type and model
names defined in the Supported Phones Types and Models table.
The RealPresence Resource Manager system can get the Endpoint Type and Endpoint Model
when it starts to provision this phone if the values of these two fields are blank.
If the value of Endpoint Type or Endpoint Model is incorrect, this record is imported into the
RealPresence Resource Manager system with Endpoint Type as Polycom Phone. When the phone
connects to the RealPresence Resource Manager system, the connected Endpoint Type will be
corrected automatically.
● The format of the Owner field is domain/userid or any owner display name if the owner does not
match to local user or Enterprise user.
● A phone may associate with one or more endpoint groups. Use a pipe(|) to separate multiple group
names.
● Asterisk (*) is reserved for the Digest Account and Digest Password fields. The value of the Digest
Account or Digest Password field can be hidden with an asterisk (*), which means “keep the
existing value” when importing a CSV file.
● SIP URI can be an ASCII encoded string containing digits or a valid SIP URI string. For example,
6416 and 6416@polycom.com are all valid values.
● The allowed values of the Line Index field are from 1 to 5 for the each phone.
● Phone information including MAC Address, Endpoint Name, Endpoint Type, Endpoint Model,
Owner, and Endpoint Group(s) needs to be repeated for phones with multiple lines. If the phone
data is different for the same phone (same MAC Address) with multiple lines, the RealPresence
Resource Manager system will use the phone date of the first line.
Examples
For example, your SoundPoint phone has two lines. The line indexes are 1 and 2, then use the following
format to add this phone:
0004F23EA4E1,SoundPoint-EA4E1,SoundPoint,SoundPoint IP
550,ASIAPAC/Jsmith,EP_Gourp1|EP_Group2,1,1000,Jon Smith,1000,1000
0004F23EA4E1,SoundPoint-EA4E1,SoundPoint,SoundPoint IP
550,ASIAPAC/Jsmith,EP_Gourp1|EP_Group2,2,1001,Jon Smith1,1001,1001
The following example only contains the required fields specified. In this case, the RealPresence Resource
Manager system can get the Endpoint Type and Endpoint Model when it starts to provision this phone.
0004F24FD08E,,,,,1,1001,,,
The following example only contains MAC address without line information.
Polycom, Inc.
355
Managing Audio Phones
0004F24FD08E,,,,,,,,,
Import the CSV File and View the Import Details
You must have either the administrator or area administrator role to import users.
To import audio phones and view the import details:
1 Go to Endpoint > Monitor View.
2 Select More > Import/Export Audio Phones.
3 Click the Choose File button on the Import Audio Phones tab.
4 Browse to the CSV file and select this file.
5 Click the Import button. A Task Progress dialog will show the file uploading and importing
progress.
6 View the import details on the Import Phones Result dialog.
7 Download the import log by clicking the Download Import Log button if needed.
8 Click Close to dismiss the Import Phones Result dialog.
Export and Edit Phones
This operation will export all the audio phones to a CSV file. You can edit the phones’ information and then
import the updated CSV file to the system again.
To export manually added audio phones:
1 Go to Endpoint > Monitor View.
2 Select More > Import/Export Audio Phones.
3 Click the Export & Download button on the Export Audio Phones tab. The CSV file is
downloaded.
4 Open the CSV file and edit the phones’ information if needed.
The Digest Account and Digest Password fields are hidden with asterisks (*) for security reasons.
You can change the values of the two fields. A asterisk (*) means keeping the previous value when
importing the CSV file.
For automatically added phones, the Line Index, SIP URI, Display Name, Digest Account, and
Digest Password fields are always displayed as blank even the fields have values. You can enter
new values to change the line information.
For automatically added phones, after the line information is changed, the phones become manually
added phones. The mode changes from
to
.
Polycom does not recommend that you change the line information of CUCM synced phones since
the changes are overwritten at next CUCM sync interval.
Working with Phone Configuration Profiles
When you manage phones, you can configure them by using configuration profiles. As soon as a phone is
configured to use the RealPresence Resource Manager system for its provisioning server, it starts polling
Polycom, Inc.
356
Managing Audio Phones
for configuration profile updates. The default polling interval is 3:00 am to 5:00 am every day. After a phone
is provisioned, the RealPresence Resource Manager will enable its REST API and change its Admin
password to “789”.
To ensure out-of-box usability, the RealPresence Resource Manager system comes with a large number of
Polycom standard (pre-defined) configuration profiles which are read-only. All provisioning parameters
defined in provision profiles will be sent to endpoints according to the profiles deployment. If an endpoint
system does not have a corresponding parameter, it ignores the parameter.
Please see the Polycom UC Software Administration Guide for complete documentation on the features of
your Polycom phones.
This section includes the following topics:
● Create a Phone Configuration Profile
● Edit a Phone Configuration Profile
● Copy a Configuration Profile
● View a Configuration Profile Detail
● Delete a Phone Configuration Profile
● Export Configuration Profiles
Create a Phone Configuration Profile
You can create new profiles to customize endpoint settings in your environment. You can either create a
new one or copy a pre-defined profile and make necessary changes
Users with the Provision Profiles permission can edit profiles.
To create a configuration profile:
1 Go to Endpoint > Phone Management > Configuration Profiles.
2 Click
.
3 In the General Information tab of the Add New Configuration Profile dialog, enter a name and
description for the new provisioning profile. File name cannot contain / \ : * ? "< > |.
4 Click the Configuration Attributes tab.
5 (Optional) From the Software drop-down list, select a software image.
 The selected version is used to update the phones under certain condition. See Set a Software
Update Policy for details.
 When a software image is selected, the system will use the attributes defined in its XSD file
instead of the default XSD file.
6 Add phone’s provisioning attribute in one of the following ways. When there is an overlap of the
attributes, the latest edit will take effect.
 Standard Fields
Enter text (two or more characters) to search attributes in a XSD file.
 If you selected a software image with XSD file in the previous step, the system will search
attributes in the XSD file packed in the software image.
Polycom, Inc.
357
Managing Audio Phones
 If you have uploaded a customized XSD file from the Endpoint > Phone Management >
Phone Management Settings page. The system will search attributes in the uploaded XSD
file.
 The system also comes a default XSD file that contains phone configuration elements that you
can use. By default, the system searches attributes in the default XSD file.
 Custom Fields
You can enter an attribute that is not included in the XSD file and click Apply to add this attribute.
XSD validation will not apply to the customized attributes.
 Import from File
Browse to select a CFG or XML file containing the attributes. The file can contain customized
attributes that are not included in the specified XSD file.
 Paste Configuration XML
Paste a piece of XML containing the attributes and click Apply. You can paste customized
attributes that are not included in the specified XSD file.
7 Click OK to save the changes.
For information about uploading XSD file, see Configure Your Phone Management Settings.
Edit a Phone Configuration Profile
You can only edit user defined configuration profiles that you created.
To edit an customized profile:
1 Go to Endpoint > Phone Management > Configuration Profiles.
2 Use one of the following ways to open the Edit Configuration Profile dialog.
 Select a user defined profile and click
.
 Click a user defined profile hyper link. All editable customized profiles are shown as hyper links
in blue.
3 As needed, edit the provisioning details.
4 Do one of the following for configuration profiles in use:
 Click Apply to apply the updates to the associated on-line phones now. This operation may reboot
the phones. If the associated phones are off-line, the phones will receive the changes when the
phones connect to the RealPresence Resource Manager system.
If the profile has not been applied to any phones before, Apply will not be displayed.
 Click OK to wait for the updates taking effect automatically at the next polling interval.
If this profile has not been applied to any phones before, click OK to save the changes.
For associated phones behind firewall, you can only click OK to wait for the updates taking effect
automatically at the next polling interval.
Polycom, Inc.
358
Managing Audio Phones
Copy a Configuration Profile
You can copy a Polycom standard profile or an user defined profile and create your own profiles based on
cloned profiles.
To create an customized profile based on a cloned profile:
1 Go to Endpoint > Phone Management > Configuration Profiles.
2 Select a profile and click
.
3 In the Copy Configuration Profile dialog, enter a name and description for the new provisioning
profile.
4 Edit the attribute as needed.
5 Click OK.
View a Configuration Profile Detail
You can view the details for both Polycom standard and user defined profiles.
To view details of a profile:
1 Go to Endpoint > Phone Management > Configuration Profiles.
2 Select a profile and click
.
The detail information displays on the right.
Delete a Phone Configuration Profile
You can only delete user defined configuration profiles that you created.
To delete an provisioning profile:
1 Go to Endpoint > Phone Management > Provisioning Profiles.
2 Select an user defined profile and click
.
3 Do one of the following to confirm the deletion:
 Click Apply to delete the profile and remove its phones’ association right now.
This operation may reboot the phones. If the associated phones are offline, the profile association
will be removed when the phones connect to the RealPresence Resource Manager system.
If the profile has not been applied to any phones before, Apply is not displayed.
 Click OK to remove the phones’ profile association automatically at the next polling interval.
4 If this profile has not been applied to any phones before, click OK to delete the profile.
For associated phones behind firewall, you can only click OK to wait for removing the phones profile
association automatically at the next polling interval.
Polycom, Inc.
359
Managing Audio Phones
Export Configuration Profiles
This operation export one user defined profile or all user defined profiles to a ZIP file.
To export configuration profile(s):
1 Go to Endpoint > Phone Management> Configuration Profiles.
2 Do one of the following:
 Select a user defined profile and click
to export this profile.
 Click More > Export User Defined Profile to export all user defined profiles.
Audio Phone Configuration Profile Deployment
The RealPresence Resource Manager system allows the endpoint admin to use the pre-defined conditions
to deploy the configuration profiles for provisioning audio phones. The following list is ordered by priority of
the conditions from the lowest to the highest.
For example, you have a call.autoAnswer.SIP parameter enabled in configuration profile A and disabled
in configuration profile B. Profile A applies to specific Sites. Profile B applies to Global. The
call.autoAnswer.SIP parameter is also enabled for all Global phones since Sites has higher priority.
● Global: All audio phones are part of Global regardless of model, site or endpoint group.
Configuration profiles association in this container apply to all endpoints.
● Endpoint Groups: Configuration profiles association in this container apply to the audio phones
belonging to this Endpoint Group.
● Endpoint Models: Configuration profiles association in this container apply to the audio phones in a
specific endpoint model. For example, apply a customized configuration profile to all Polycom VVX
500 phones.
● Sites: Configuration profiles association in this container apply to the audio phones in a specific site.
Geographical locations is the typical use case for site.
● Endpoints: Configuration profiles association in this container apply to the audio phones that you
specified. For example, you know specific phones need a specific configuration or call server. You
can select these phones to receive the required configuration profiles.
Associate Configuration Profiles with Pre-defined
Conditions
You can associate one or more configuration profiles with a pre-defined condition.
To associate profiles to conditions:
1 Go to Endpoint > Phone Management > Profiles Deployment.
2 Associate configuration profiles with one of the following pre-defined conditions:
 Global: Click
to open the Edit Configuration Profile Association for Global dialog.
 Endpoint Groups/Endpoints: Select a group or endpoint, click
Configuration Profile Association tab.
Polycom, Inc.
, and click the
360
Managing Audio Phones
 Endpoint Models/Sites: Select a device model or site and click
.
3 Select a configuration profile from the Configuration Profile Association drop-down list.
4 Click Apply.
5 Repeat step 3 and step 4 to add more configuration profiles.
6 Adjust the priority of the configuration profiles by clicking the
configuration profile up and down or to top or to bottom.
buttons to move the
7 Do one of the following:
 Click Apply to apply the updates to the associated on-line phones now. This operation may reboot
the phones. If the phones are offline, the phones receive the changes when the phones connect
to the RealPresence Resource Manager system.
 Click OK to wait for the updates to take effect automatically at the next polling interval.
For associated phones behind firewall, you can only click OK to wait for updates taking effect
automatically at the next polling interval.
Reboot Phones
You can reboot phones for each pre-defined condition.
To reboot phones:
1 Go to Endpoint > Phone Management > Profiles Deployment.
2 Reboot phones for one of the following conditions:
 Global: Select More > Reboot All Phones.
 Endpoint Groups/Endpoint Models/Sites: Select a group, device model, or site, select More >
Reboot Phones.
3 Click OK to confirm the reboot.
Register Phones to a SIP server
After registering to a SIP call server, you can make calls using the phones.
To register to a SIP sever:
1 Go to Endpoint > Phone Management > Configuration Profiles.
2 Create a profile containing the call server fields.
For example, create a profile named SIP_server containing the following fields:
voIpProt.server.1.address="server_IPaddress"
voIpProt.server.1.port="Port"
voIpProt.server.1.transport="TCPpreferred"
3 Go to Endpoint > Phone Management > Profiles Deployment.
4 Apply the profile to certain phones based on conditions.
See Create a Phone Configuration Profile on how to create profiles.
Polycom, Inc.
361
Managing Audio Phones
See Associate Configuration Profiles with Pre-defined Conditions on how to deploy profiles based on
conditions.
Monitor Phones Behind Firewall
The RealPresence Resource Manager system comes with a pre-defined configuration profile,
NotificationServerURL-External. This profile contains the parameters that you need to specify to
monitor the SIP register status and call status of phones behind firewall. You can view the status from the
Endpoint > Monitor View page.
To monitor phones behind firewall:
1 Go to Endpoint > Phone Management > Configuration Profiles.
2 Click
and select Profile Name.
3 Enter NotificationServerURL-External.
4 Click Search.
5 Select NotificationServerURL-External.
6 Click
.
7 In the Configuration Attributes tab, replace ProxyServerAddress with your proxy server address in
the following parameters. For example, the RealPresence Access Director address.
 apps.statePolling.URL="https://ProxyServerAddress/PlcmRmWeb/device/PhoneStatus
 apps.telNotification.URL="https://ProxyServerAddress/PlcmRmWeb/device/PhoneStatu
s
8 Click OK.
9 Go to Endpoint > Phone Management > Profiles Deployment.
10 Apply this profile to the phones behind firewall per the conditions.
See View the Endpoint List on details for the status shown on the Endpoint > Monitor View page.
See Create a Phone Configuration Profile on how to create profiles.
See Associate Configuration Profiles with Pre-defined Conditions on how to deploy profiles based on
conditions.
Working with Resource Files
Resource files can be any type of file used for configuring phones. For example, you can upload image files
and configure the system to use the files as phone icons in your configuration profile.
Upload Resource File
Uploading resource files under 50 MB is recommended.
To upload resource file:
1 Go to Endpoint > Phone Management > Resource Files.
Polycom, Inc.
362
Managing Audio Phones
2 Click
to open the Upload Resource Files dialog.
3 Browse to the file to be uploaded.
4 Enter a description.
5 Click OK to upload the file.
Download Resource File
You can download the resource files and check the content.
To download resource file:
1 Go to Endpoint > Phone Management > Resource Files.
2 Select a resource file to download. You can download a single file each time.
3 Click
to download the selected file.
Delete Resource Files
You can delete one or more resource files.
To delete resource files:
1 Go to Endpoint > Phone Management > Resource Files.
2 Select a resource file or click
3 Click
to select multiple resource files.
.
4 Click OK to confirm the deletion.
Refresh Resource Files
Refresh the Resource Files page to see the resource files changes made by other users.
To Refresh resource files:
1 Go to Endpoint > Phone Management > Resource Files.
2 Click
.
Working with Phone Software Updates
You can update the software on your provisioned phones automatically with the RealPresence Resource
Manager system.
Setting up software updates includes the following tasks:
● Upload the Software Update for Phone Software Updates
● Set a Software Update Policy
Polycom, Inc.
363
Managing Audio Phones
Upload the Software Update for Phone Software
Updates
Polycom recommends you to do software updates using the split packages available on Polycom’s support
website to reduce system resource consuming.
When a large number of audio phones applies for updates at the same time, the updates may not be
completed at one time.
To upload a software update:
1 Go to Endpoint > Phone Management > Upload Software Updates.
2 Click
to open the Upload Software Update dialog.
3 In the Software Update File field, browse to the software update file you downloaded.
4 Enter a meaningful description that will help other users to understand the purpose of the software
update.
5 Click OK.
A software update profile is created.
Set a Software Update Policy
After uploading software updates, you can set the update versions to manage the roll out of a software
update package. You can set update versions in configuration profiles and apply the profiles to different
phones under certain conditions.
To set software update versions:
1 Go to Endpoint > Phone Management > Configuration Profile.
2 Select a specific profile that you want to use to do phone updates.
3 In Configuration Attributes, select a software version to use.
4 Go to Endpoint > Phone Management > Profile Deployment.
5 Deploy this the configuration profile to a condition that you want.
6 Do one of the following:
 Click Apply to upgrade the associated on-line phones now.
 Click OK to save the changes.The next time the phones under this condition poll the
RealPresence Resource Manager system, the phones will detect the new software version, so
the phones will automatically download and install the identified software update package. Use
this method to force users to use a specific software version.
Working with CUCM
When you integrate a Cisco Unified Communications Manager system with your RealPresence Resource
Manager system, the RealPresence Resource Manager system becomes aware of all of the supported
Polycom, Inc.
364
Managing Audio Phones
Polycom phones registered to the Cisco Unified Communications Manager. Supported phones are
displayed in the Endpoint > Monitor View page, and the RealPresence Resource Manager system can
use information about these phones to deliver provisioning information.
•
•
Polycom highly recommends you to re-integrate CUCM after upgrading to 10.1.
After upgrading to 10.1, you must manually update the phones’ provisioning protocol to HTTP or
HTTPS and specify the RealPresence Resource Manager system IP address. See Configure
Automatically Added Audio Phones for Provisioning for details.
Setting up a CUCM server to work with the RealPresence Resource Manager system includes the following
tasks:
● Configuring Cisco Unified Communications Manager
● Enabling Auto Discovery of RealPresence Resource Manager through DHCP
● Creating Phone Configuration Profiles
● Customizing Digest User Password
● Integrating with a Cisco Unified Communications Manager
Configuring Cisco Unified Communications Manager
The RealPresence Resource Manager system uses Cisco AXL SOAP API to enable integration with the
Cisco Unified Communications Manager. This web service is disabled by default. You’ll need to enable it,
and create a user with the appropriate privileges to use with the RealPresence Resource Manager system.
This section includes the following topics that pertain to setting up your Cisco Unified Communications
Manager system:
● Start the Cisco AXL Web Service
● Creating a User for the RealPresence Resource Manager Integration
Start the Cisco AXL Web Service
In your Cisco Unified Communications Manager system, you’ll need to activate the Cisco AXL Web Service
before you create a new user.
To activate the service:
1 From the Unified CM Administration window, go to Navigation > Unified CM Serviceability.
2 Choose Tools > Service Activation.
3 From the Server box, choose the server and click Go.
4 From the Database and Admin Services section, select Cisco AXL Web Service and save the
changes.
Polycom, Inc.
365
Managing Audio Phones
Creating a User for the RealPresence Resource Manager
Integration
In your Cisco Unified Communications Manager, you need to create an Access Control Group with the
correct role and then add your newly-created user to that group.
● Create the Access Control Group
● Assign AXL role to the Group
● Create the User
By default, the administrator has the correct privileges for integration. Although not recommended,
you can use this user for an initial test or quick set up.
Create the Access Control Group
In the Cisco Unified Communications Manager system, Access Control Groups are used to organize users
and their roles.
To create an Access Control Group with AXL API role:
1 In the Cisco Unified Communications Manager system, ensure that the Standard AXL API Access
role exists. Choose User Management > User Settings > Role.
2 Choose User Management > User Settings > Access Control Group.
3 Click Add New.
4 In the Access Control Group Information dialog box, name your access control group. For
example, Polycom RPRM Integration.
5 Click Save to save the name.
Assign AXL role to the Group
In the Cisco Unified Communications Manager system, you’ll need to assign the Standard AXL API Access
role to the new group.
To assign the role:
1 Choose User Management > User Settings > Access Control Group.
2 Click Find to list all the groups.
3 Select the group you created and click Assign Role to Group, and select Standard AXL API
Access to assign it to the new group.
4 Click Save.
Create the User
In the Cisco Unified Communications Manager, you should create a new user to use for integration with the
RealPresence Resource Manager system.
Polycom, Inc.
366
Managing Audio Phones
To create a new user:
1 Choose User Management > Application User > Add New.
2 In the Add New User dialog, enter a name for your new user. For example, rprmint.
3 Click Add to Access Control Group to add the access control group you created.
4 Click Save to save the user information.
After completing each of these sections, your Cisco Unified Communications Manager is ready to be
integrated with the RealPresence Resource Manager system.
Enabling Auto Discovery of RealPresence Resource
Manager through DHCP
The phones will use the DHCP option 66 to discover the RealPresence Resource Manager system. See
Polycom UC Software Administrators’ Guide for detailed information.
Creating Phone Configuration Profiles
You should create your phone provisioning profiles before integrating your system with a Cisco Unified
Communications Manager. Phones registered with the Cisco Unified Communications Manager begin
polling for provisioning updates via HTTP or HTTPS after you integrate your Cisco Unified Communications
Manager with your RealPresence Resource Manager system. After initial provisioning, provisioning updates
are sent according to the provisioning poll you configure.
Configuring the CUCM as a SIP server (Optional)
If you want to use the CUCM server, you need to configure the SIP registration server to the CUCM in a
profile.
See Register Phones to a SIP server for details.
Customizing Digest User Password
Optionally, you can customize the digest user password for the phones you provision. When you integrate
with a Cisco Unified Communications Manager system, each phone’s password is reset to the factory
default. By default, a system-generated password is used. You can change this password at any time.
See Configure Your Phone Management Settings for details.
Integrating with a Cisco Unified Communications
Manager
Integrating with a CUCM server includes the following tasks:
● Add a Cisco Unified Communications Manager
● Synchronize with the Cisco Unified Communication Manager
Polycom, Inc.
367
Managing Audio Phones
Add a Cisco Unified Communications Manager
You can add a Cisco Unified Communications Manager system to your RealPresence Resource Manager
system. The RealPresence Resource Manager begins provisioning phones as soon as you add the Cisco
Communications Manager system to your RealPresence Resource Manager system.
To add a Cisco Unified Communications Manager for provisioning:
1 Go to Network Device > Instances.
2 Click
.
3 In the Add Instance dialog box, select Cisco Unified Communications Manager from the Device
Type drop-down list. Complete the following fields:
Field
Description
Device Type
Add By
You can only add a Cisco Unified Communications Manager system by IP or
FQDN address.
Device Name
The name of the Cisco Unified Communications Manager system.
Management Address
The IP address of the Cisco Unified Communications Manager.
Admin User
Enter the user name used to connect with the Cisco Unified Communications
Manager.
This user must have the AXL API Access Role.
See Working with Phone Configuration Profiles.
Admin Password
Enter the user name password.
Service Integration
CUCM is Integrated with
same AD as Resource
Manager
Select the check box if the Cisco Unified Communications Manager is
integrated with the same Active Directory as the RealPresence Resource
Manager system.
LDAP Attribute for CUCM
User ID
If you marked the CUCM is Integrated with the same AD as Resource
Manager check box, please enter the user ID that the Cisco Unified
Communications Manager system used to integrate with the Active Directory.
Synchronized Time with
CUCM (in days)
Configure how often you want the RealPresence Resource Manager to
synchronize with the Cisco Unified Communications Manager to retrieve the
list of registered Polycom phones.
If you are using Cisco Unified Communications Manager v10 or higher,
Polycom recommends synchronizing every five to seven days.
4 Click OK.
The system integrates with the Cisco Unified Communications Manager and begins provisioning
phones.
Polycom, Inc.
368
Managing Audio Phones
Synchronize with the Cisco Unified Communication Manager
When you synchronize your system with the Cisco Unified Communications Manager, the RealPresence
Resource Manager system retrieves information about any added phones since the last time you
synchronized. Synchronization happens automatically when you first integrate with a Cisco Unified
Communications Manager.
If you are using Cisco Unified Communications Manager 10 or higher, all added Polycom phones are
automatically synchronized to the RealPresence Resource Manager every 10 minutes.
You can choose to synchronize with the Cisco Unified Communications Manager at any time.
To synchronize with a Cisco Unified Communications Manager:
1 Go to Network Device > Instances.
2 Select the Cisco Unified Communications Manager you want to synchronize.
3 Click More > Sync Data. A progress dialog displays.
4 Click Close after the synchronization is done.
Configure Your Phone Management Settings
You can configure the following phone settings from the Endpoint > Phone Management > Phone
Management Settings page:
● Digest Password for CUCM Synced Phones: After you integrate with a Cisco Unified
Communications Manager, the digest password for the phones is reset to the factory default unless
you change this password. You can also customize the digest user passwords for the phones.
● Provisioning Account Configuration: The HTTP or HTTPS service is used for the provisioning
connection between the RealPresence Resource Manager system and the phones. By default, a
system-generated user name and password are used by the phones during the process to get
provisioning profiles and software updates from the RealPresence Resource Manager. Each phone
uses the same HTTP or HTTPS service password. The default user name and password are both
PlcmSpIp.
You can change this password at any time. After you change the password, you need to configure
the phones to use the same HTTP or HTTPS password. Otherwise, the phones will not be able to
connect to the RealPresence Resource Manager system to receive provisioning profiles and
software updates.
.
If phone communicates with RealPresence Resource Manager via HTTPS, you should ensure that
the phone(s) can validate the RealPresence Resource Manager system’s security certificate. For
more information about certificates RealPresence Resource Manager system certificates, see
Security Certificates.
For information about certificates for Polycom phones, see the respective UC Software Administrator
Guide.
Polycom, Inc.
369
Managing Audio Phones
● Phone Files Rotation Settings: You can control the disk space that the uploaded configuration and
log files occupy in the RealPresence Resource Manager system. The default values rotate the log
files every 1024 KB and keep up to five files for 15 days.
The logs are saved in the /var disk. When the /var disk 90% occupied, the system will clean the
logs automatically. For example, if the Days to Retain Phone Files value is 15 days, when the /var
disk 90% occupied, the system will clean the logs saved on the first day. If the /var disk still 80%
occupied, the system will keep cleaning the logs saved on the second day.
● Upload Default XSD: The RealPresence Resource Manager system comes with a default XSD
(Polycom RealPresence Trio 5.4.4.7609) file that contains phone configuration elements that you can
use. You also can make your own XSD file to include more customized phone settings and upload
the XSD file to the system to overwrite the default file.
To configure phone management settings:
1 Go to Endpoint > Phone Management > Phone Management Settings.
2 To change the digest password for phones synced from Cisco Unified Communications Manager:
a In the Digest Password for CUCM Synced Phones section, clear the Use System Auto
Generated Password check box.
b Complete Password and Confirm Password fields.
3 In the Phone Files Rotation Settings section, change the settings as needed and click Update.
4 To configure the provisioning account, in the Provisioning Account Configuration section, edit
the User Name or the Password.
5 To upload a XSD file, in the Upload Default XSD section, browse to the XSD file and click the
Upload button.
6 Click Update.
Polycom, Inc.
370
User Management
This section provides an introduction to the Polycom® RealPresence Resource Manager system video user
management options functionality and operations. It includes:
● Understanding Users, Groups, and Roles
● Managing Users
● Managing Meeting Rooms
Polycom, Inc.
371
Understanding Users, Groups, and Roles
The Polycom® RealPresence® Resource Manager system supports two types of users.
● Users that come directly from the enterprise directory. These users are referred to as enterprise
users.
● Users that are local to the management system. These users are added manually to the system or
imported.
Both user types can be assigned management roles, associated with endpoints, and organized in groups.
By default all users can be scheduled into conferences, and call into conferences. However, the system
cannot call out to them until they are associated with endpoints.
This section provides an overview of the RealPresence Resource Manager system users and groups
management structure. It includes the following topics:
● Working with Users
● Working with Groups
● Working with Management Roles and Permissions
Working with Users
The RealPresence Resource Manager system supports two types of users.
● Users that come directly from the enterprise directory. These users are referred to as enterprise
users.
● Users that are local to the management system. These users are added manually to the system or
imported from a file.
Local Users
When you manually add local users (or import them), the RealPresence Resource Manager system
manages all user information and associations.
At a minimum, when you manually add users, you must enter a user’s First Name or Last Name, User ID,
Email Address, and Password. When you enter the minimum information, the RealPresence Resource
Manager system automatically assigns local users the basic Scheduler role or Area Scheduler role (when
areas are enabled), unless you remove that assignment. You can unassign that role if the user does not
need any management permissions.
By default all users can be scheduled into conferences, and can dial into conferences. However, the system
cannot dial out to them until they are associated with endpoints.
You can associate local users with one or more roles and associate them with one or more endpoints.
Alternatively, you can associate local users with local groups and then assign roles to an entire group.
Polycom, Inc.
372
Understanding Users, Groups, and Roles
See Local Groups for more information.
If your company has implemented multi-tenancy, you can also assign local users to an area or areas that
you manage. For more information about areas, see Configuring Multi-Tenancy or Managing Areas.
Enterprise Users
When the RealPresence Resource Manager system is integrated with an enterprise directory, the system
manages only the following pieces of an enterprise users’ information:
● Endpoints associated with the user
● Roles assigned to the user
● Area to which the user belongs
● Alert profiles for the user
The remaining information is pulled from the enterprise directory, including email address, system password
and so on.
The RealPresence Resource Manager system supports only a Microsoft Active
Directory integration. Other LDAP systems are not supported.
The RealPresence Resource Manager system displays a user’s City, Title, and
Department to help distinguish between users with the same name.
Users imported into the system through the enterprise directory are added to the system without a role. This
default set up enables users to log into the RealPresence Resource Manager system with their enterprise
user IDs and passwords. They can then be scheduled into conferences and call into conferences. However,
the system cannot call out to them until they are associated with endpoints.
Provisioning for hardware endpoint associated with a username that includes a
special character will not work. As a best practice, do not use special characters in
usernames.
Assigning Roles to Enterprise Users
Users with management roles can perform tasks on the RealPresence Resource Manager system, such as
device management or conference scheduling. Management roles can be system-wide or area-restricted.
A user must be assigned a management role in order to access the management system interface.
Conference participant users can be scheduled into conferences and do not need to be assigned a
management role, unless that particular user also needs to perform system management tasks.
If your company has implemented the Areas feature, you can also associate enterprise users with areas for
which you are an administrator. For more information about areas, see Managing Areas or Configuring
Multi-Tenancy.
If you want the RealPresence Resource Manager system to, by default, automatically assign enterprise
users the basic Scheduler role, you must change the appropriate system Security Settings. See Enabling
and Editing Log In Banners.
Polycom, Inc.
373
Understanding Users, Groups, and Roles
Working with Groups
Groups provide a more efficient and consistent use of the RealPresence Resource Manager system,
because they allow you to assign roles and provisioning profiles to sets of users rather than to individual
users.
This section includes the following topics:
● Local Groups
● Enterprise Groups
Local Groups
The RealPresence Resource Manager system enables you to add local groups (that is, groups added
manually to the system) and associate them with provisioning profiles, roles and address books.
For local groups, the RealPresence Resource Manager system manages all group information and
associations.
Enterprise Groups
When the RealPresence Resource Manager system is integrated with an enterprise directory, groups
defined to the enterprise directory are not automatically added to the RealPresence Resource Manager
system, but you can import them into the system.
When the RealPresence Resource Manager system is integrated with an enterprise directory, the system
manages only three pieces of group information: the provisioning profile assigned to the group, the roles
assigned to the group, and whether or not the group is Directory Viewable (that is, displayed in endpoint
directories) or included in an address book. The remaining group information is pulled from the enterprise
directory.
Preparing to Use Active Directory
To take full advantage of the RealPresence Resource Manager system, the enterprise Microsoft Active
Directory must:
● Have the Global Catalog turned ON. The Global Catalog enables searching for Active Directory
objects in any domain without the need for subordinate referrals, and users can find objects of interest
quickly without having to know what domain holds the object.
● Use universal groups. The Global Catalog stores the member attributes of universal groups only. It
does not store local or global group attributes.
● Have a login account that has read access to all domains in the Active Directory that the
RealPresence Resource Manager system can use. Polycom recommends an account with a
administrative username and a non-expiring password.
● Have the Active Directory Domain Name Service correctly configured. For more information about
Active Directory design and deployment, see the Microsoft best practices guides at
http://technet.microsoft.com.
For system and endpoint directory performance purposes, two best practices in regards to enterprise
groups are as follows:
● Do not import more than 500 enterprise groups into a RealPresence Resource Manager system.
● Do not mark more than 200 enterprise groups as Directory Viewable.
Polycom, Inc.
374
Understanding Users, Groups, and Roles
Working with Management Roles and Permissions
You must decide which users will have management roles. Users with management roles can perform tasks
on the RealPresence Resource Manager system, such as device management or conference scheduling.
Management roles can be system-wide or area-restricted. A user must be assigned a management role in
order to access the management system interface.
Participant users who can be scheduled into conferences do not need to be assigned a management role,
unless that particular user also needs to perform system management tasks.
For more information about area roles, see User Roles within a Multi-Tenancy Environment.
This section includes the following topics:
● Understanding User Roles
● Default System Roles and Permissions
● Customized Roles and Responsibilities
Understanding User Roles
The RealPresence Resource Manager system is a role and permissions based system.
● Users can be assigned one or more user roles either directly or through their group associations.
● User roles are assigned a set of permissions. The system comes with default roles for both
system-wide and area management tasks.
● Users see only the pages and functions available to their roles and associated permissions.
Permissions are cumulative, so users see all of the pages and functions assigned to all of their roles
and associated permissions.
Users inherit roles from their parent groups—local or enterprise. They cannot inherit
roles from groups more distantly removed—for example, from their grandparent
groups. The default role names are stored in the system database and are not
localized into other languages. If you wish to localized their names into your
language, edit the roles and enter new names for them.
● If you have implemented the Areas feature, users are restricted to the manage resources in the areas
they are assigned to manage, according to the role they are given.
While the RealPresence Resource Manager system provides almost unlimited flexibility in defining roles,
for simplicity and clarity, Polycom recommends keeping the default roles with their default permissions and
responsibilities. Because users can be assigned multiple roles, and permissions are cumulative, you can
combine roles as needed to reflect the workload of managing and using the system.
An administrator has several options when implementing user roles.
1 Implement only the default user roles and keep the standard permissions assigned to these roles.
2 Implement only the default user roles but change the permissions assigned to these roles.
To ensure system access and stability, the default administrator role cannot be
deleted or edited.
Polycom, Inc.
375
Understanding Users, Groups, and Roles
3 Implement either option 1 or 2, but also create additional unique, workflow-driven user roles and
determine which permissions to assign to those user roles.
Some important notes about user roles and permissions:
● Users (local and enterprise) may be assigned more than one role. In this case, the permissions
associated with those roles are cumulative; a user has all of the permissions assigned to all of his
roles.
● Users (local and enterprise) may be assigned roles as an individual and as part of a group. Again,
the permissions associated with those roles are cumulative; a user has all of the permissions
assigned to all roles no matter how that role is assigned.
● Users assigned a role with any one of the Administrator Permissions are generally referred to as
administrators. Users assigned a role with any one of the Operator Permissions and none of the
Administrator Permissions are referred to as operators. Users assigned a user role with
Scheduler Permissions and none of the Administrator or Operator Permissions are referred to
as schedulers.
Default System Roles and Permissions
The RealPresence Resource Manager system includes a default set of management roles. Roles are
associated with a set of permissions that allow the user to perform certain management tasks. Users see
only the menus, pages, and functions associated with their roles.
While the RealPresence Resource Manager system provides administrators almost unlimited flexibility in
defining roles, for simplicity and clarity, Polycom recommends keeping the default roles with their default
permissions and responsibilities. Because users can be assigned multiple roles, and permissions are
cumulative, you can combine roles as needed to reflect the workload your people undertake to manage and
use the system.
The following table identifies the default system roles. Each of these roles is discussed in more detail in the
following sections:
● Scheduler Roles, Responsibilities, and Menus
● Operator Role, Responsibilities, and Menus
● Device Administrator Role, Responsibilities, and Menus
● Auditor Role, Responsibilities, and Menus
● Administrator Role, Responsibilities, and Menus
For information about area roles, see User Roles within a Multi-Tenancy Environment.
Polycom, Inc.
376
Understanding Users, Groups, and Roles
Role
Permissions
Scheduler
Schedule Conferences
Scheduling Level = Basic
When areas are enabled:
View and/or modify all areas.
Can perform role tasks in all areas.
Advanced Scheduler
Schedule Conferences
Scheduling Level = Advanced
When areas are enabled:
View and/or modify all areas.
Can perform role tasks in all areas.
View-Only Scheduler
Schedule Conferences
Scheduling Level = View-Only
When areas are enabled:
View and/or modify all areas.
Can perform role tasks in all areas.
Operator
Conference Operator
Report Operator
Troubleshooting
Schedule Conferences
Scheduling Level = Advanced
When areas are enabled:
View and/or modify all areas.
Can perform role tasks in all areas.
Device Administrator
Add endpoints and network devices.
Network Device Admin
Assign Provisioning Profiles through scheduled management
Schedule software updates for endpoints
When areas are enabled:
View and/or modify all areas.
Place devices and endpoints in Areas
Polycom, Inc.
377
Understanding Users, Groups, and Roles
Role
Permissions
Administrator
Directory Setup
Topology Setup
Conferencing Setup
System Setup
Network Device Monitor
System Maintenance/Troubleshooting and Trace troubleshooting
Create Provisioning Profiles
Create Software Updates
Network device admin
Create configuration profiles for audio phones
Create software updates for audio phones
When areas are enabled:
Assign RealPresence Resource Manager users to manage areas
Create areas
Place Entities in areas
View and/or modify all areas
Note
This role cannot be deleted or edited.
Auditor
Endpoint Usage Report
Network Usage Report
Alert Level Settings
Server Software Upgrade
System Log Files
Audio Log Files
Log Settings
Scheduler Roles, Responsibilities, and Menus
The RealPresence Resource Manager system offers three different default Scheduler roles.
,
Role
Responsibilities
Scheduler
For the areas to which they belong (areas are optional), users assigned the
Scheduler (sometimes called basic scheduler) role can schedule
conferences. They do so using the conference templates defined for them.
But basic schedulers cannot change any of the conference settings defined
in the templates they choose when scheduling their conferences.
Advanced Scheduler
For the areas to which they belong (areas are optional), users assigned the
Advanced Scheduler role can also schedule conferences. And again they
do so using the conference templates defined for them. But advanced
schedulers can change selected conference settings defined in the template
they use when scheduling their conferences.
View-Only Scheduler
For the areas to which they belong (areas are optional), users assigned the
View-only Scheduler role cannot schedule conferences; they can only see
conferences that have been scheduled.
When basic or advanced schedulers log into the RealPresence Resource Manager system, the system
displays the conference page and they have access to the Guest Book.
Polycom, Inc.
378
Understanding Users, Groups, and Roles
When view-only schedulers log into the RealPresence Resource Manager system, the system displays the
conference page and it is the only menu item to which they have access.
Operator Role, Responsibilities, and Menus
The Operator role enables businesses to offer high-touch customer service for video conferencing. User
assigned the Operator role can:
● Schedule conferences.
● Monitor and manage ongoing conferences.
● Monitor endpoints.
● Monitor network devices such as MCUs.
● Add, edit, and delete entries in the system Guest Book.
● Create favorites.
● View some system reports.
Device Administrator Role, Responsibilities, and Menus
The Device Administrator role is for those users who administrate endpoints, bridges, and other network
devices. For the areas to which they belong, users assigned the Device Administrator role can:
● Monitor endpoints, peripherals, and network devices.
● Add, edit, and delete endpoints and network devices.
● Provision endpoints using scheduled management.
● Update endpoints using scheduled management.
When device administrators log into the RealPresence Resource Manager system, the system displays the
system Dashboard.
Auditor Role, Responsibilities, and Menus
The Auditor role enables security-conscious companies to separate system administration functions from
system auditing functions. This provides an added level of system checks and balances. This role must be
explicitly assigned by an administrator.
For the areas to which they belong, users assigned the Auditor role can:
● View audit logs.
● Backup and delete audit logs.
● Change the audit log file alert level.
● View and download system log files.
● Respond to audit log alerts.
Administrator Role, Responsibilities, and Menus
The Administrator role is for those users who administrate the RealPresence Resource Manager system
itself. Users assigned the Administrator role can generally do almost all system functions, however they
cannot schedule conferences, monitor conferences, or manage endpoints or other network devices.
When administrators log into the RealPresence Resource Manager system, the system displays the system
Dashboard.
Polycom, Inc.
379
Understanding Users, Groups, and Roles
Customized Roles and Responsibilities
The RealPresence Resource Manager system provides you almost unlimited flexibility in defining and
redefining roles, but for simplicity and clarity, we recommend keeping the default roles with their default
permissions and responsibilities.
Users can be assigned multiple roles and permissions are cumulative, so your business can combine roles
as needed to reflect the workload your people undertake to manage and use the system.
Permission Set
Permitted Tasks
Administrators Permissions
Directory Setup
Create users
Create user groups
Create a guest book
Create a room
Create a machine account
Create address books
Site Topology Setup
Site Topology
Sites
Site-Links
Network Clouds
Territories
Reports> Site Statistics
Reports > Site-Link Statistics
Conferencing Setup
Direct Conference Templates
Conference Settings
Favorites
System Setup
System configuration under Admin
Endpoint Monitor
Endpoint Image Management
System
Maintenance/Troubleshooting
Dashboard and troubleshooting utilities -- without wireshark trace.
System Maintenance
Troubleshooting - Trace
Dashboard and troubleshooting utilities -- with wireshark trace
Assign User to managed Area
Edit user or user group for assigned area.
Place entities in Areas
Edit MCU for assigned area.
Provision Profiles
Endpoint provisioning profile management and ACL control.
Network Device Monitor
Network device monitor function.
Operator Permissions
Endpoint Admin
Polycom, Inc.
Endpoint management
Control provisioning and software update for scheduled Endpoints.
380
Understanding Users, Groups, and Roles
Permission Set
Permitted Tasks
Network Device Admin
Network Device management.
Schedulable resource monitor
Monitor MCU and RealPresence DMA pool status.
Conference operator
View, manage, and control all conferences in system.
Have no permission for scheduling conferences.
Report Operator
Manage the reports in system (view and export reports).
MCU/EP Monitor
Monitor MCU and Endpoint status.
View and edit all areas
View and edit the areas.
Scheduler Permissions
Schedule conferences
(view-only)
View all scheduled conference in system.
Have no permission for scheduling conferences.
Schedule conferences (basic)
View and schedule new conference of the user account, but can't select bridge
or change the conference settings in the template.
Schedule conferences
(advanced)
View and schedule new conference of the user account and change
conference settings for scheduled conferences.
Auditor Permissions
Getting system logs
Polycom, Inc.
381
Managing Users
This section includes information on managing users and groups within the Polycom® Real Presence®
Resource Manager system. It includes these topics:
● Managing Users
● Adding Machine Accounts
● Manage Dial String Reservations for Users
● Managing Groups
● Managing User Roles
Managing Users
In the RealPresence Resource Manager system, only users assigned the Administrator role can manage
users. Some of these tasks include:
● Search for a User
● Add a Local User
● Edit a User
● Assign Users to Manage an Area(s)
● Delete a Local User
● Clear Orphan Active Directory Users/Rooms
● Enable/Disable Users
● Import Local Users
● Updating Users by Import
● Adding Machine Accounts
Search for a User
You can search for a user. Searches for a user are case-insensitive, prefix searches of the User ID, First
Name, and Last Name fields.
You must be logged in as an enterprise user in order to search for enterprise users.
To search for a user:
1 Go to User > Users.
2 In the Search Users field, enter the following keywords to search the users of interest.
Polycom, Inc.
382
Managing Users
 First Name
The first name of the user of interest.
 Last Name
The last name of the user of interest.
 User ID
The user ID of the user of interest.
 Domain
users.
Enter Local to search for local users. Enter a domain name to search for enterprise
3 Press Enter.
The first 500 users in the database that match your search criteria are displayed in the Users list.
If the list is too large to scan, further refine your search string.
View User Information
You can view information about a user, local or enterprise.
For more information about user roles, see Working with Management Roles and Permissions.
To view a user information:
1 Go to User > Users.
2 Select the user you want.
3 Click
.
Column
Description
General Info
First Name
The user’s first name.
Last Name
The user’s last name.
User ID
The user’s unique login name. This user ID must be unique across all rooms
and users and across all domains.
Email Address
The user’s email address. (The Email address is an ASCII-only field.)
Title
The user’s professional title.
Department
The user’s department within the enterprise.
City
The city in which the user’s office is located.
Contact Number
The contact phone number for the user.
Assign Area
If your RealPresence Resource Manager system has areas enabled, you can
choose to assign this user to an area that you manage.
Belongs to Area
This field is only available if Areas have been enabled.
Manages Area
This field is only available if Areas have been enabled.
Create Password
Click the Create Password button to generate a password by the system.
Associated Roles
Polycom, Inc.
383
Managing Users
Column
Description
Assigned Roles
The roles assigned to the user.
Groups
Type
The type of group to which the user belongs. Possible values are local and
enterprise.
Name
The name of the group to which the user belongs.
Inherited Group Info
Address Book
The Address Book(s) the user sees based upon the groups to which the user
is assigned.
Add a Local User
You can add local users.
To add a local user:
1 Go to User > Users and click
.
The Add New User dialog appears. The User Enabled option is selected by default.
2 Enter the following user information.
Column
Description
First Name
The user’s first name
Last Name
The user’s last name
User ID
The user’s unique login name. This user ID must be unique across all rooms
and users and across all domains.
For Multi-Tenancy:
Create user names using the email address format. This will ensure that all
user names are unique. Otherwise two people named Bob Smith belonging to
different tenants may end up with the same user name. By following an email
address format, Bob Smith in TenantA could have bsmith@tenantA.com as a
user name and Bob Smith in TenantB could have bsmith@tenantB.com.
Password
The user’s assigned password. This password must be a minimum of eight
characters in length.
Email Address
The user’s Email address. (The Email address is an ASCII-only field.)
Title
The user’s professional title.
Department
The user’s department within the enterprise.
City
The city in which the user’s office is located.
Polycom, Inc.
384
Managing Users
Column
Description
Phone Number
The contact phone number for the user.
Assign Area
If your RealPresence Resource Manager system has areas enabled, you can
choose to assign this user to an area that you manage.
3 If needed, click the Create Password button to generate a random password by the system.
4 Click Save.
5 In the Associated Endpoints section, select and move the required endpoints(s) to Selected
Endpoints list. Move the unwanted endpoints(s) to the Available Endpoints list. Press Shift-click
or Ctrl-click to select multiple items in the list.
If the user has multiple endpoints, list the endpoints in order of priority, with the primary endpoint first.
When scheduling a user in a conference, the RealPresence Resource Manager system will, by
default, schedule the user’s primary endpoint. The scheduler can choose to change the request to
schedule one of the user’s other endpoints.
6 In the Associated Roles section, select and move the required role(s) to Selected Roles list. Move
the unwanted role(s) to the Available Roles list. Press Shift-click or Ctrl-click to select multiple
items in the list.
7 If Areas are enabled, click the Managed Areas section.
You must have either the administrator role or have the area administrator role and be allowed to
manage more than one area in order to perform this action.
 If the user has not been assigned a role, select the None radio button and continue to the
Associated Alert Profile section.
 If the user has been assigned an role, select the Specific Areas radio button.
8 In the Available Areas section, select and move the required area(s) to Selected Areas list. Move
the unwanted role(s) to the Available Areas list. Press Shift-click or Ctrl-click to select multiple
items in the list.
The user will be assigned to manage the areas in the Selected Areas section.
9 In the Associated Alert Profile section, select a Remote Alert Notification Profile as appropriate.
10 In the SIP Dial String Reservations section, select the user’s Endpoint Type and enter the
appropriate dial string for SIP URI, then click Apply.
The dial strings appear in the list below.
By default, the same SIP URI is used for all endpoints that belong to the same user. If the user has
multiple endpoints and you want a different SIP URI for each endpoint type, enter the dial strings for
one endpoint type at a time and click Apply each time.
11 In the H323 Dial String Reservations section, select the user’s Endpoint Type and enter the
appropriate dial string for E164 and H323 ID, then click Apply.
The dial strings appear in the list below.
If the user has multiple endpoints, enter the dial strings for one endpoint type at a time and click Apply
each time.
12 Click Update.
If the Phone Number you entered is exactly the same as an existing user or endpoint, the Phone
Number Conflict dialog appears and lists the names of the other users or endpoints with the same
number.
Polycom, Inc.
385
Managing Users
 To keep the duplicate number, click Continue.
 To change the phone number, click Cancel.
Edit a User
For local users added manually to the RealPresence Resource Manager system, you can edit all user
information. If you change the user ID, the user must log into the associated endpoints with the new ID.
For users added through the enterprise directory, you can edit their roles (unless the role is inherited from
a group) and associate them to endpoints, but you cannot change user names, user IDs, or passwords.
To edit a user:
1 Go to User > Users.
2 Search for the user you want to edit.
3 Select the user you want to edit and click
.
4 As required, edit the General Info, Associated Endpoints, Associated Roles, Managed Areas,
Associated Alert Profile, and Dial String Reservations sections of the Edit User dialog.
If the user has multiple associated endpoints, list the endpoints in order of priority, with the primary
endpoint first.
When scheduling a user in a conference, the RealPresence Resource Manager system will, by
default, schedule the user’s primary endpoint. The scheduler can choose to change the request to
schedule one of the user’s other endpoints.
5 Click Update.
Assign Users to Manage an Area(s)
This task is only available if areas have been enabled (multi-tenancy).
In order to perform RealPresence Resource Manager system tasks within an area, the user must be allowed
to manage that area. Allowing a user to manage an area means allowing them to perform the duties
associated with their role in the areas that they are allowed to manage.
A user can be allowed to manage:
● Zero areas. This means that user cannot perform any tasks in any area.
● One Area. This means that the user can perform role-based tasks for the area he manages. You
must indicate which area you want the user to manage.
● Multiple areas. This means the user can perform role-based tasks in each area that he manages.
You must indicate which areas you want the user to manage.
● All areas. A user can manage all areas if he is assigned a system role or if his role includes the View
and/or Modify All areas permission. If the user has this role, you do not need to explicitly allow him to
manage an area or areas.
For example, a user with the area scheduler role can belong to the yellow area and allowed to schedule
conferences in both the yellow and blue areas if he has permission to manage the blue area as well as the
yellow area.
Polycom, Inc.
386
Managing Users
In order to enable a user to manage an area, you must have the administrator role or the area administrator
role and manage the area to which you want to allow a user to manage. In short, you need to have
permission to manage the area to which you want to allow a user to manage.
To assign a user to manage an area(s):
1 Go to User > Users.
2 Search for the user you want to assign to an area.
3 Select the user and click
.
4 In the Edit User dialog, click Managed Areas.
You must have either the administrator role or have the area administrator role and be allowed to
manage more than one area in order to perform this action.
5 In the Available Areas section, select the area(s) you want the user to manage and click the arrow
icon to move the list to the Selected Areas section.
Conversely, you can select area(s) in the Selected Areas section and click the corresponding arrow
to move the selected area(s) to the Available Areas section.
The user will be assigned to manage the areas in the Selected Areas section.
6 Click Update.
Delete a Local User
You can only delete local users from the RealPresence Resource Manager system. You cannot delete
users added through integration with an enterprise directory.
To delete a user:
1 Go to User > Users.
2 Search the user you want to delete.
3 Select the user and click
.
To delete multiple users, hold the Shift key down while you make your selections.
4 Click OK to confirm the deletion.
The user is deleted from the system.
Clear Orphan Active Directory Users/Rooms
When a user or room has been deleted from your Active Directory system, it is not automatically deleted
from your RealPresence Resource Manager system. You may want to periodically update your user list
when you are integrated with an Active Directory system.
Use the Clear Orphan Active Directory Users/Rooms option to delete enterprise users that are listed in your
system, but no longer exist in Active Directory.
Be sure your Active Directory Connection is Available.
If you perform an orphan clean up when your system is not connected to Active Directory, you will
delete ALL users in the system.
Polycom, Inc.
387
Managing Users
To delete orphaned Active Directory users:
1 Go to User > Users.
2 Select Clear Orphan AD User/Rooms from the More drop-down list.
3 Click OK.
All enterprise users that no longer exist in your enterprise directory are deleted from your
RealPresence Resource Manager system.
Enable/Disable Users
Be default, a user is enabled to use the system when you create the user. However, after some period of
inactivity users may become disabled.
You can enable or disable multiple users at once.
To enable or disable multiple users:
1 Go to User > Users
2 Select the user you want to enable or disable and click
.
3 Check or clear User Enabled.
The users are enabled or disabled.
Unlock a User Account
When a local user reaches the Failed login threshold, the system will not allow the user to log in until an
administrator unlocks the user’s account. When a user’s account is locked, the system will display an error
message.
To unlock a user account:
1 Go to User > Users and search for the user you want to unlock.
2 Select the user whose account you want to unlock and click
.
3 Clear the User Locked check box.
4 Click Update.
The system should allow the user to log in.
Import Local Users
You can import local users into your RealPresence Resource Manager system. You may choose to do this
if your RealPresence Resource Manager deployment does not include an integration with an LDAP server
and you need the convenience of importing users in bulk instead of creating them one at a time.
You can only import users to one area at a time and must have either the administrator role or area
administrator role in order to import users.
Polycom, Inc.
388
Managing Users
To import users to your system:
1 Create a CSV File Containing the User Information You Need.
2 Import the CSV File.
3 Review the Import Details File.
Create a CSV File Containing the User Information You Need
You must create a CSV (comma separated values) file that contains the users you need. You can create
this file with any plain text editor or use Microsoft Excel.
Only UTF-8 encoding is supported in the CSV file.
The format should be the following:
Username, First Name, Last Name, Email, Title, Dept, City, Phone Number, Role(s),
Password
Use the following guidelines:
● Use a file with a *.csv extension.
● All fields for a single user must be on a single line and end with a new line or end of file character.
The line after a new line is assumed to be for another user.
● Commas (‘,’) are used as field separators and cannot be embedded in a field. All commas must be
included, even before fields that are optional. Each field’s leading and trailing white space (blanks
and tabs) is ignored (does not become part of the field value).
● Unicode characters are allowed in the file as long as they are valid for the field type.
● Blank lines are allowed and are ignored.
● A header line is not allowed in the CSV file. All lines must either represent a user or be blank.
● The following fields are required: Username, First Name or Last Name, and Email.
● Other fields can be left blank, but not skipped.
Field
Usage Notes
Username
The username must be unique across the entire RealPresence Resource Manager
system. (The recommended naming convention to ensure uniqueness is specified in
section
If a specified username already exists in the selected area (or in the system, if Areas is
disabled), then the system assumes you wish to update the existing user’s information.
If a specified username already exists in a different area, then the user is neither added
nor updated and an error is issued.
Role(s)
Role names are case sensitive.
To specify multiple roles for a user, separate the roles with a pipe (‘|’).
If the Role(s) field contains only area-specific roles, then the user will automatically be
set to manage the selected area.
Polycom, Inc.
389
Managing Users
Field
Usage Notes
Password
If any of the users have no password specified, then a single default password is
generated and assigned to all those without a password specified. The administrator will
be shown what password was assigned to all and is responsible for writing it down and
communicating it to all the users.
For users assigned default passwords, the first time they log in, they will be required to
change their password.
Email
Be sure to includes a valid email address.
Examples
This first example shows all fields specified:
js@co.com, John, Smith, js@co.com, Tech I, IT, Boulder, 303-333-4444, Role 1|Role 2, JSpw
This example shows only the required fields specified. In this case, the user will be given a blank first name,
title, department, city and phone number, no role and a generated password.
jdoe, , Doe, doe@co.com, ,
,
,scheduler,
,
Import the CSV File
You need to have either the administrator or area administrator role to import users.
To import local users:
1 Choose User > Users and click Import Local Users from the More drop-down list.
2 In the File Location (CSV) field, browse to the location of the CSV file you created.
3 If areas are enabled and you manage more than one area, select an area from the Assign Area
drop-down list.
If Areas are not enabled on your RealPresence Resource Manager system or you only manage one
area, the Areas drop-down is not available.
If Areas are enabled and the you manage more than one area, you must select an area to which all
the users will be added. You can also select None to add the users to no area.
4 Click Import.
A status window appears. Click OK when it is complete.
The results of the import are summarized on the Import Summary screen.
5 If a default password is shown in the summary, write the password down and inform those users of
the password.
6 Click Download Import Details to view the import details file. Save it as a text file for your records.
7 Close the Import Users dialog.
Handle the User Accounts with Password lost
If you fail to record or remember the password shown on the Import Summary screen, there will be no other
way to determine the password and the users will be unable to login. If this happens, you can either:
Polycom, Inc.
390
Managing Users
● Edit each affected user one-by-one via the RealPresence Resource Manager system’s User Edit
screen and manually change the password field or have system generate a password.
● Delete all affected users one-by-one via the RealPresence Resource Manager user interface and
re-import them.
Review the Import Details File
You should review the Import Details file for any information about errors that may need to be corrected.
If there are errors, you can either:
● Create another CSV file with the users that need to be corrected and import only those users.
● Edit the same CSV file to correct the users with errors and import the file again. Users that were
previously added successfully will be updated, see Updating Users by Import on page 391.
Specifically, existing user updates will fail if a password is specified, so either remove those user’s
passwords or ignore password errors that are issued for those users who were previously added.
In either case, realize that a different default password will be assigned in subsequent imports than was
assigned to users in a previous import.
To view the Import Details file:
» Navigate to the location where you downloaded the Import Details file and open it in a text editor.
Updating Users by Import
You can also use the Import Local Users action to update existing users.
The CSV format for updating an existing user is the same as that used for adding a user except that the
password field must be blank. For each existing username whose attributes are to be updated, the CSV
format is:
Username, First Name, Last Name, Email, Title, Dept, City, Phone Number, Role(s),
Note that the comma after the Role(s) field is still required.
Importing a CSV file that has existing usernames will overwrite existing data. Make sure the CSV data
is at least as current as what is in RealPresence Resource Manager system. Determining existing
user data can be done one-by-one and manually via the RealPresence Resource Manager system
user interface (currently there is no way to export local user data in bulk).
A single CSV file may contain both users to be added and users to be updated. The system will
automatically determine whether you are intending to add or update a user by whether the username
already exists in the system or not:
The following fields cannot be changed using the Import Local Users action.
● An existing user’s username
● An existing user’s password
● Any of the attributes not specified in the Import CSV format
The following rules apply when updating existing users.
Polycom, Inc.
391
Managing Users
● The Username must already exist in the selected area.
You can only change an existing user’s username by using the RealPresence Resource Manager
system user interface.
● The Password must be blank. If a password is specified, the update for that user will fail such that
none of the fields will be updated.
You cannot change a user’s password with an import. You must use the system’s web interface.
● Fields that are left blank will replace any existing data that the RealPresence Resource Manager
system has for that user with a blank.
● There is no way to indicate that any of the user’s data should be left as is.
● All other user attributes not included in the CSV format, such as which areas a user manages, will
not be modified by an Import.
Adding Machine Accounts
For dynamically managed endpoints associated with a room, a user assigned the Administrator role must
associate each room in the RealPresence Resource Manager system with a machine account. In addition,
dynamically managed HDX systems and RealPresence Group Series require machine accounts.
The machine account enables the endpoint to connect and authenticate with the RealPresence Resource
Manager system for directory and dynamic management purposes without using the endpoint user’s
account. You should use a unique machine account for each room or endpoint you need to provision.
You can set up the room and machine account the following ways:
● You can set up a machine account and create a new room at the same time, then edit the room to
complete the room information.
● You can create a new room, then create the machine account and associate the machine account
with the existing room. For more information, see Add a Local Room.
● If your system is integrated with Active Directory and you want to associate a machine account with
an Active Directory account, you must first create that account in Active Directory.
This section includes the following topics:
● Add a Machine Account
● Edit a Machine Account
Add a Machine Account
When you add a machine account, you must associate it with a user or a room. You can choose to use an
existing user or room or create one when you add the machine account.
Once you have created this machine account on the RealPresence RealPresence Resource Manager
system, provide this information to the appropriate endpoint administrator. They should enter this User ID
and Password as the User Name and Password on the Provisioning Service page.
Note that the machine account password expires after one year. After the expiration, the endpoint login will
fail. After three failed login attempts, the system locks the machine account. You can reset the password
and unlock the machine account by editing it and assigning a new password.
Polycom, Inc.
392
Managing Users
To add a machine account:
1 Go to User > Machine Accounts.
2 Click
.
3 In the Add Machine Account dialog, complete the fields.
The dialog includes the following information.
Field
Description
Enable Machine
Account
Select or clear this option to enable and disable (respectively) the machine account you
create for the endpoint.
Unlock Machine
Account
Select this option to unlock machine accounts that become locked when they exceed
the Failed login threshold. This will only happen when the password expires.
User ID
Enter a unique name for the machine account.
As a best practice, name the machine account in a way that associates it with the
corresponding device. For example, if your company names endpoint systems for the
system user or room (for example, bsmith_HDX or Evergreen_Room), then give the
machine account an associated User ID (bsmith_HDX_machine or
evergreen_room_machine).
Password/
Confirm Password
Enter a password for the machine account user ID.
This password must meet the Local Password Requirements. This password
expires in 365 days.
Description
Enter a meaningful description for the endpoint.
Associate with an
existing user or room
Select this option to associate the endpoint system with a specific user or room. This
may be a local or enterprise user or room.
Associate with a new
room (created
automatically)
Select this option to associate the endpoint system with a system-generated room. The
name of the new room is the same as the machine account User Name and can be
edited when you edit the room.
This option can only create a local room account. If you want to associate a machine
account with an Active Directory account, you must first add the account through Active
Directory.
Assign Area
When areas are enabled, you can assign the newly-created room to an area.
Only users who manage more than one area can assign areas.
4 Click OK.
Edit a Machine Account
You can edit a machine account. Once you have created this machine account on the RealPresence
RealPresence Resource Manager system, provide this information to the appropriate endpoint
administrator. They should enter this User ID and Password as the User Name and Password on the
Provisioning Service page.
Note that the machine account password expires after one year. After the expiration, the endpoint login will
fail. After three failed login attempts, the system locks the machine account. You can reset the password
and unlock the machine account by editing it and assigning a new password.
Polycom, Inc.
393
Managing Users
To edit a machine account:
1 Go to User > Machine Accounts.
2 Select a machine account and click
.
3 In the Edit Machine Account dialog, edit the fields as needed.
4 Click OK.
Manage Dial String Reservations for Users
If you need to make multiple dial string reservations for multiple users, you can use the Import User Alias
function. If you need to make a report of which dial strings (H.323 or SIP URIs) have been reserved for each
user, you can use the Export User Alias function.
Both the Import User Alias and Export User Alias features allow you to manage the dial string
reservations for all users at once. If you need to only add or modify a dial string for a single user, it is more
efficient to edit that user’s dial strings directly, see Edit a User.
Dial string reservations take first priority when they are associated with a user and will overwrite any
provisioned H.323 alias or SIP URI for that user.
Specifically, SIP URI dial string reservations are assigned in the following three ways, listed by priority:
1 Dial string reservation associated with user record.
2 Domain user or third-party server (for example, Microsoft Lync)
3 Auto-generated SIP URI through the RealPresence Resource Manager system
Export User Aliases
You can export a report of users with reserved SIP URI aliases, either SIP or H.323. Keep in mind that this
CSV file will contain displays reserved aliases and dynamically provisioned aliases if the provisioning
information has already been sent.
Users with the area administrator role can only export aliases from one area at a time or from only the
areas they manage. Users with the administrator role can export alias information from all areas.
To export a list of user aliases:
1 Navigate to User > Users.
2 Click Export User Aliases from the More drop-down list.
3 In the Export User Aliases dialog, select the SIP radio button and click Export.
You cannot export both H.323 and SIP aliases in the same report. You must export them separately.
4 Save the report.
Importing User Aliases
You can import a list of user aliases that will add to or overwrite any existing reserved dial string aliases that
have been associated with users.
Polycom, Inc.
394
Managing Users
You will need to create a CSV (comma separated values) file that lists the user information and user alias
reservations you wish to add or update. You may use any text editor or Microsoft Excel to create the CSV
file.
Use the following guidelines:
● Use a file with a *.csv extension.
● All fields for a single user must be on a single line and end with a new line or end of file character.
The line after a new line is assumed to be for another user.
● Commas (‘,’) are used as field separators and cannot be embedded in a field. All commas must be
included, even before fields that are optional. Each field’s leading and trailing white space (blanks
and tabs) is ignored (does not become part of the field value).
● Unicode characters are allowed in the file as long as they are valid for the field type.
● Blank lines are allowed and are ignored.
● A header line is not allowed in the CSV file. All lines must either represent a user or be blank.
SIP Format:
Domain, username, endpoint type, SIP URI, Endpoint Name
Where:
Commas (‘,’) are used as field separators and cannot be embedded in a field. The endpoint name should
be used if you need to differentiate between two endpoint names (HDX1 and HDX1) of the same endpoint
type for the same user. The endpoint name is required in order to associate the SIP URI with a device. You
do not need to include a SIP URI for all users in the file, but at least one user must have a value for the SIP
URI field.
The following fields are required: Domain, Username, Endpoint Type, and SIP URI.
Other fields can be left blank, but not skipped.
Field
Usage Notes
Domain
Specifies the domain of the user.
Username
The username must already exist in the RealPresence Resource Manager system.
This can be the user ID of a user or a machine account, or the name of a room.
Polycom, Inc.
395
Managing Users
Field
Usage Notes
Endpoint Type
The following are valid endpoint types:
HDX
VVX
CMADesktop
RPMobile
GroupSeries
RPDesktop
ITP
RPDebut
RPCentro
CX
All_Types
URI
The SIP URI for this user. The SIP URI supports alphanumeric characters and the
following special characters: '.', '-', '_', '@', ':'.
Endpoint Name
The endpoint name should be included if you need to differentiate between two endpoint
names (jsmithHDX1 and jsmithHDX2) for the same endpoint type for the same user.
Examples
● This first example reserves the SIP URI to all endpoint types for this user:
local,johndoe,All_Types,johndoe@example.com
● This example reserves the SIP URI to the HDX for this user.
local,johndoe,HDX,johndoeHDX@example.com
● This example reserves the SIP URI to the HDX that is named johndoeHDX2.
local,johndoe,HDX,johndoeHDX2@example.com,johndoeHDX2
H323 Format
Domain, Username, Endpoint Type, H.323 ID, E.164 Number, Endpoint Name
Where:
Commas (‘,’) are used as field separators and cannot be embedded in a field. The endpoint name should
be used if you need to differentiate between two endpoint types (HDX1 and HDX1) of the same type for the
same user. You can supply an H.323 ID, an E.164 number or both. You do not need to enter a dial string
for each user in the file.
The following fields are required: Domain, Username, Endpoint Type, H323 ID and E.164.
Other fields can be left blank, but not skipped.
Polycom, Inc.
396
Managing Users
Field
Usage Notes
Domain
Specifies the domain of the user.
Username
The username must already exist in the RealPresence Resource Manager system.
This can be the user ID of a user or a machine account, or the name of a room.
Endpoint Type
The following are valid endpoint types:
HDX
VVX
CMADesktop
RPMobile
GroupSeries
RPDesktop
ITP
RPDebut
RPCentro
CX
All_Types
H.323 ID
The H.323 ID for this user. The H.323 ID supports alphanumeric characters and the
following special characters: '.', '-', '_', '@', ':'.
E.164 Number
The E.164 number for this user. The E.164 number must consist of only numeric
characters.
Endpoint Name
The endpoint name should be included if you need to differentiate between two endpoint
names (jsmithHDX1 and jsmithHDX2) for the same endpoint type for the same user.
The endpoint name is required if you want to associate the SIP URI with a particular
endpoint name that has been assigned to a user.
Examples
● This first example reserves the H.323 ID and E.164 number for this user’s HDX system.
local,johndoe,HDX,johndoeHDX,771000
● This example updates the H.323 ID and E.164 number for this user’s “johndoeHDX2”.
local,johndoe,HDX,johndoeHDX2,771001
Importing User Aliases
You can import user aliases.
To import a list of user aliases:
1 Create a valid CSV file to use. It may be helpful to use an exported User Alias CSV file on which to
base your changes.
2 Navigate to User > Users.
3 Select Import User Aliases from the More drop-down list.
Polycom, Inc.
397
Managing Users
4 In the Import User Aliases dialog, select SIP aliases or H323 aliases radio button and click Export.
You cannot import both H.323 and SIP aliases in the same report. You must export them separately.
5 Click Update.
An error message will display if your CSV file contained any mistakes. If you get an error message,
you will need to correct the rows that were not loaded and import them again.
Managing Groups
In the RealPresence Resource Manager system, only users assigned the Administrator role can manage
groups.
This section includes the following topics:
● Add a Local Group
● Import Enterprise Groups
● Edit a Group
● Delete a Group
Add a Local Group
You can create local groups.
You must have the Administrator role to manage groups.
To add a local group:
1 Go to User > User Groups.
2 In the User Groups page, click
.
3 Complete the General Info section of the Add Group dialog.
Column
Description
General Info
User Group Name
A meaningful and unique group name assigned when creating the group.
Description
A more complete description of the group’s purpose
Enterprise Directory Viewable
Indicates if the group is displayed in the endpoint directory
Assigned Area
If your RealPresence Resource Manager system has areas enabled, you can
choose to assign this user to an area that you manage.
Associated Roles
Available Roles
The list of roles defined to the RealPresence Resource Manager system.
Selected Roles
The list of roles that you assign users when adding them to the system. Users
have all of the permissions associated with all of the roles assigned to them
(that is, permissions are cumulative).
Polycom, Inc.
398
Managing Users
Column
Description
Address Book
Address Book
See Assign Address Books to User Groups.
Group Members (Local Users Only)
Filter
Search for finding users
Search Results
The users and groups identified to the system that you can add to the local
group. This list can include both local and enterprise users and groups.
Group Members
The users and groups selected as part of the group
4 Click
to search for the users and groups to add to this local group.
5 In the Search Results section, select and move the users and groups of interest to the Group
Members list. To select all users and groups listed, click the check box in the column header.
6 Click Update.
The group appears in the User Groups list. It is identified as a LOCAL group.
Import Enterprise Groups
When you import an enterprise group, you can edit the group, user roles, and specify whether or not the
group directory is viewable. You can also search for enterprise users.
You must have the Administrator role to manage groups.
To import one or more enterprise groups:
1 Go to User > User Groups.
2 Go to More > Import Enterprise Group.
3 Click
and type all or part of the group name (with wildcards) in the Search Available Groups
field, and press Search.
Searches for a group are case-insensitive, exact-match searches of the Group Name field. Use
wildcard characters to perform substring searches.
4 In the Search Results list, select the enterprise groups to add. To select all enterprise groups, click
the check box in the column header.
5 Click the right arrow to add the enterprise groups to the Groups to Import list.
6 Click OK.
The enterprise group appears in the Groups list.
Edit a Group
You can edit both local or enterprise groups. If you remove a user from a group or a role from a group, the
user no longer has the roles associated with the group.
You must have the Administrator role to manage groups.
Polycom, Inc.
399
Managing Users
The Group Members section is only available for Local groups.
To edit a local or enterprise group:
1 Go to User > User Groups.
2 In the User Groups page, select the group you want to edit and click
.
3 As required, edit the General Info, Associated Roles, and Group Members sections of the Edit
Local Groups dialog.
4 Click Update.
Delete a Group
You can delete a local or enterprise group. An enterprise group is only deleted from the system, not the
enterprise directory. You can re-import an enterprise group if necessary.
You must have the Administrator role to manage groups.
To delete a local or enterprise group:
1 Go to User > User Groups.
2 In the User Groups page, select the group you want to delete and click
.
3 Click OK to confirm the deletion.
The group is deleted from the system.
For information about enterprise groups, see Managing Directories.
Managing User Roles
You can assign roles to both local and enterprise users.
You must decide which users will have management roles. Users with management roles can perform tasks
on the RealPresence Resource Manager system, such as device management or conference scheduling.
Management roles can be system-wide or area-restricted. A user must be assigned a management role in
order to access the management system interface.
Participant users who can be scheduled into conferences do not need to be assigned a management role,
unless that particular user also needs to perform system management tasks.
Only users assigned the Administrator role can manage user roles.
This section includes the following topics:
● View the List of User Roles
● Add a User Role
● Edit Permissions for a User Role
● Delete a User Role
● View the Groups and Users Associated with a User Role
Polycom, Inc.
400
Managing Users
View the List of User Roles
You can view a list of the user roles for your system.
To view the list of user roles:
» Go to User > User Roles.
The User Roles list appears. It can be filtered by Name and Description.
Column
Description
Name
The unique name of the user role
Description
An optional description of the role
Add a User Role
When you add a user role, you also specify permissions for the role.
To add a new user role:
1 Go to User > User Roles.
2 On the User Roles page, click
.
3 Complete the Name and Description fields of the Add Role dialog and assign permissions to the
new role.
The following table describes the fields of the Add Role dialog.
Field
Description
Name
The unique name (ASCII only) of the user role
Description
(Optional) A useful description (ASCII only) of the user role
Administrator
Permissions
Identifies which RealPresence Resource Manager system administrator pages and
functions are available to the user role.
Operator Permissions
Identifies which RealPresence Resource Manager system operator pages and functions
are available to the user role.
Scheduler Permissions
Identifies which RealPresence Resource Manager system scheduling pages and
functions are available to the user role.
Scheduling Level. This setting determines the level of scheduling available through
this role. Possible values are:
• Basic. Users can schedule conferences using the conference templates defined for
them. They cannot access or edit the advanced Conference Settings.
• Advanced. Users can schedule conferences using the conference templates defined
for them. They can also access and edit the advanced Conference Settings.
4 Click Update.
The new user role appears in the RealPresence Resource Manager system.
Polycom, Inc.
401
Managing Users
Edit Permissions for a User Role
You can change permissions for the default roles, as well as for other user roles that were created manually.
You cannot change permissions for the default Administrator role.
Do not edit pre-defined roles for system that needs high security.
To edit the permissions for a user role:
1 Go to User > User Roles.
2 As needed, click
to customize the User Roles list.
3 In the User Roles list, select the role you want to edit and click
.
4 Edit the Description field of the Edit Role dialog and edit permissions for the role.
5 Click Update.
Delete a User Role
You can delete a user role from the RealPresence Resource Manager system, provided no users are
currently assigned to it.
To delete a user role:
1 Go to User > User Roles.
2 As needed, use
to customize the User Roles list.
3 In the User Roles list, select the role you want to delete and click
.
4 Click Yes to confirm the deletion.
The user role is deleted from the RealPresence Resource Manager system.
View the Groups and Users Associated with a User
Role
You can view the users and groups that have been associated with a role.
To view which groups and users are associated with a specific user role:
1 Go to User > User Roles.
2 As needed, use
to customize the User Roles list.
3 In the User Roles list, select the role you want to view and click View Associated Groups and
Users from the More drop-down list.
The View Associated Groups and Users dialog appears.
Polycom, Inc.
402
Managing Meeting Rooms
This section describes how to set up rooms in the Polycom® RealPresence® Resource Manager system. It
includes these topics:
● Local and Enterprise Meeting Rooms
● View the Rooms List
● Search for a Room
● Add a Local Room
● Add an Enterprise Room
● Edit a Room
● Delete a Room
Local and Enterprise Meeting Rooms
The RealPresence Resource Manager system enables a user assigned the default Administrator role or
the Area Administrator role to manage local and enterprise meeting rooms and the endpoints associated
with those meeting rooms.
Most often a system is integrated with an enterprise directory to which rooms have been added. However,
the system also enables you to add local rooms (that is, rooms added manually to the system) and associate
them with endpoints.
If you want to dynamically manage the endpoint associated with a local room, you must also associate each
room in the system with a machine account. The machine account enables the local room’s endpoint to
connect and authenticate with the system for directory and dynamic management purposes without using
the endpoint user’s account. After you add a local room, you can create the machine account and associate
the room with the machine account.
See Adding Machine Accounts for detailed information about using machine accounts.
View the Rooms List
You can view a list of rooms. To edit or view additional details about a room, you can select it and choose
an action.
To view the rooms list:
» Go to User > Rooms.
The Rooms list appears. It can be filtered by Site.
Polycom, Inc.
403
Managing Meeting Rooms
Search for a Room
You can search the list of rooms. When searching for a room that is in the enterprise directory, you must
use the search field with which the room was created. For example, if the enterprise directory room was
created using the Last Name field in the enterprise directory, you must use that field within theRealPresence
Resource Manager system. In such an example, if you use the First Name field, the search will not return
the correct result.
To search for a room:
1 Go to User > Rooms.
2 On the Rooms list, click
.
The Add New Room dialog box appears.
3 To find a room in the enterprise directory:
a Click the Find Room in Enterprise Directory button.
b In the Room Name field, type in the first few characters of the room name.
The system does a prefix search of the appropriate fields.
c Click Search.
A list of the enterprise users and rooms that meet the search criteria appears. If the search found
more than 500 matching entries, only the first 500 are displayed.
Add a Local Room
When you add a local room to your system, you specify room settings and associate one or more endpoints
with the room.
If you want to dynamically manage the endpoint associated with a room, you must also associate the room
with a machine account. The machine account enables the room’s endpoint to connect and authenticate
with the system for directory and dynamic management purposes without using the endpoint user’s
account.
After you add a room, you can create the machine account and associate the room with the machine
account.
For instructions on adding machine accounts to rooms, see Add a Machine Account.
To add a local room:
1 Go to User > Rooms.
2 On the Rooms page, click
.
The Add New Room dialog box appears.
3 Complete the General Info and Associated Endpoints sections of the Add New Room dialog box.
The following table shows the room information in the RealPresence Resource Manager system
records.
Polycom, Inc.
404
Managing Meeting Rooms
Field
Description
General Info
Room Name
The name of the room, which appears in the address book for associated endpoints.
Description
(Optional) A useful description (ASCII only) of the room.
Site
The site in which the room is located.
Note:
• Rooms and the endpoint associated with them must be assigned to the same site.
• When areas are enabled on your system, this field shows a value of Restricted if
you do not have permission to manage the area to which the site is assigned.
Email
(Optional) The email address of the room administrator.
Assign Area
Select an area to which to assign this room.
This field is visible only when Areas are enabled.
A user can view area-specific information only for an area that he has permission to
manage.
Associated Endpoints
Available Endpoints
The list of unassigned endpoints that are managed by the RealPresence Resource
Manager system.
Selected Endpoints
The list of endpoints assigned to the room. The endpoint at the top of the list is the
primary endpoint.
4 In the SIP Dial String Reservations section, click
to add SIP dial string reservations.
5 On the SIP Dial String Reservations dialog, select the user’s Endpoint Type and enter the
appropriate dial string for SIP URI, then click OK.
The dial strings appear in the list below.
By default, the same SIP URI is used for all endpoints that belong to the same user. If the user has
multiple endpoints and you want a different SIP URI for each device type, enter the dial strings for
one endpoint type at a time and click OK each time on the SIP Dial String Reservations dialog.
6 In the H323 Dial String Reservations section, click
to add H323 dial string reservations.
7 On the H323 Dial String Reservations dialog, select the user’s Endpoint Type and enter the
appropriate dial string for E164 and H323 ID, then click OK.
The dial strings appear in the list below.
If the user has multiple endpoints, enter the dial strings for one endpoint type at a time and click OK
each time on the H323 Dial String Reservations dialog.
8 Click Update.
The room is added to the system. Note that the system does not distinguish between enterprise
rooms and local rooms once they’ve been added to the system.
Polycom, Inc.
405
Managing Meeting Rooms
Add an Enterprise Room
If your system is integrated with an enterprise directory, you can add a room from the enterprise directory
to the system.
If you want to dynamically manage the endpoint associated with a room, you must also associate the room
with a machine account. The machine account enables the room’s endpoint to connect and authenticate
with the system for directory and dynamic management purposes without using the endpoint user’s
account.
After you add a room, you can create the machine account and associate the room with the machine
account.
For instructions on adding machine accounts to rooms, see Add a Machine Account.
To add an enterprise room:
1 Go to User > Rooms.
2 On the Rooms list, click
.
The Add New Room dialog box appears.
3 To find a room in the enterprise directory:
a Click the Find Room in Enterprise Directory button.
b Click click
.
c In the Room Name field, type in the first few characters of the room name.
The system does a prefix search of the appropriate fields.
d Click Search.
A list of the enterprise users and rooms that meet the search criteria appears. If the search found
more than 500 matching entries, only the first 500 are displayed.
e Select the room of interest and click Define Details.
4 Complete the General Info, Associated Endpoints, SIP Dial String Reservations, and H323 Dial
String Reservations sections of the Add New Room dialog box. For information on these fields,
see Add a Local Room on page 404.
5 Click Update.
The room is added to the system. Note that the system does not distinguish between enterprise
rooms and local rooms once they’ve been added to the system.
Edit a Room
You can edit a room, including its name, dial string reservations, and so on.
If you want to dynamically manage the endpoint associated with a room, you must also associate the room
with a machine account. The machine account enables the room’s endpoint to connect and authenticate
with the system for directory and dynamic management purposes without using the endpoint user’s
account.
After you add a room, you can create the machine account and associate the room with the machine
account.
Polycom, Inc.
406
Managing Meeting Rooms
For instructions on adding machine accounts to rooms, see Add a Machine Account.
To edit a room:
1 Go to User > Rooms.
2 In the Rooms list, select the room you want to edit and click
.
3 Edit the General Info, Associated Devices, SIP Dial String Reservations, and H323 Dial String
Reservations sections of the Edit Room dialog box. For information on these fields, see Add a
Local Room on page 404.
4 Click Update.
Delete a Room
You can delete a room. When you delete a room, you are also asked if you want to delete the dial strings
(aliases) associated with the room.
To delete a room:
1 Go to User > Rooms.
2 In the Rooms list, select the room you want to delete and click
.
3 In the Delete Room dialog, click OK.
The room is deleted from the RealPresence Resource Manager system.
Polycom, Inc.
407
System Configuration
This section provides an introduction to the RealPresence Resource Manager system configuration. It
includes:
● Network Settings
● Understanding System Administration
● Securing the System
● Security Certificates
● Integrating with an Enterprise Directory
● Configuring Multi-Tenancy
● Managing Areas
● System Redundancy
● Local System Redundancy
● Geographic System Redundancy
Polycom, Inc.
408
Network Settings
This section describes how to update the Polycom® RealPresence® Resource Manager system
configuration, many of which were entered during First Time Setup. It includes these topics:
● Edit Network Settings
● Virtualization Settings
● Time Settings
● System Licensing
● Customizing System Logos
● Edit the System Email Account
Edit Network Settings
You can edit the network settings to change the basic network information for the RealPresence Resource
Manager system. Some networks setting changes require a restart, such as updating the IP address or
changing the subnet mask.
Some network changes also require you to install a new security certificate or certificate chain. When you
use certificates, you must request and install a new certificate or certificate chain if you change the system
name, DNS domain name or switch from supporting single to multiple IP protocols or vice versa.
To edit network settings:
1 Go to Admin > Server Settings > Network.
2 Configure these settings on the Service Interface tab, as necessary.
Field
Description
Supported Network Types
Choose the type of network on which the RealPresence Resource Manager
resides:
• IPv4 only
• IPv4 and IPv6
• IPv6 only
If you are using security certificates, you must request a new certificate if you
change these settings.
System Name
The NetBIOS name (ASCII only) of the RealPresence Resource Manager
system server. Must be between 6 and 16 characters long; dashes and
underscores are valid characters.
If you are using security certificates, you must request a new certificate if you
change these settings.
Polycom, Inc.
409
Network Settings
Field
Description
DSCP Marker
Enables the administrator to configure the Quality of Service level of the
RealPresence Resource Manager.
Set the level between 0 - 63. The higher the number the higher the Qualify of
Service level.
IPv6 Address
IPv6 global address
IPv6 Prefix length
Within IPv6 networks, the prefix length is the equivalent of the subnet mask in
IPv4 networks. Should be 1-128.
IPv6 Default Gateway
The IPv6 address of the gateway server/router. For IPv6 networks only.
IPv6 Link Local Address
Read-only field. The RealPresence Resource Managersystem generates a
value for this field when IPv6 is enabled.
IPv4 Address
The static IPv4 address for the RealPresence Resource Manager system.
IPv4 Subnet Mask
The network subnet mask for the RealPresence Resource Manager system
IPv4 address.
IPv4 Default Gateway
The static IP address of the RealPresence Resource Manager system IPv4
default gateway.
DNS Search Domain
The DNS domain name suffix for the network in which the domain name
server and RealPresence Resource Manager system server reside. For
example polycom.com, not the fully qualified path of hostname.polycom.com.
If you are using security certificates, you must request a new certificate if you
change these settings.
Note
If instead of entering a single domain controller, you enter an FQDN that maps
to multiple servers, be sure that all of the mapped servers are directory
domain controllers with global catalogs.
Preferred DNS Server
The IP address of the preferred domain name server for the network.
Alternate DNS Server
The IP address of the alternate domain name server for the network.
3 Click Save Settings.
If you change the IP address, the system prompts you to restart the RealPresence Resource
Manager system. We also recommend that you restart the system if you change the subnet mask.
4 As required, restart the system.
Be sure that RealPresence Resource Manager is connected to the network before you restart
system.
Virtualization Settings
If you are running a RealPresence Resource Manager system, Virtual Edition, you must configure your
RealPresence Resource Manager system to match the capacity of your virtual environment.
For additional system capability information, see the release notes.
Polycom, Inc.
410
Network Settings
Edit Virtualization Settings
For maximum performance, set the system capability of your virtual edition to match the supported number
of endpoints. See the RealPresence Resource Manager Release Notes for the supported number of
endpints.
To configure your Virtualization settings in the RealPresence Resource Manager system
1 Navigate to Admin > Server Settings > Virtualization Settings.
2 In the System Capability field, enter the number of endpoints that matches your hardware
configuration.
3 Click Update.
Time Settings
You can configure your system to time manual or set it up to synchronize with an external NTP server. If
you use an NTP server, be sure to use the same NTP server that is used by your other video conference
systems. This will ensure continuity, accurate scheduling and accurate reports for all systems.
Edit System Time Settings
You can update the your time settings manually or point your system to an external NTP server.
Make sure the current system time is correct before synchronizing with an NTP server. If you set the system
to use an external NTP server when the current date and time are incorrect, the system time may be wrong
for the amount of time specified in the Minutes between synchronization attempts.
To edit the system time settings:
1 Go to Admin > Server Settings > System Time.
2 Configure these settings, as necessary.
Field
Description
System Time Zone
The time zone in which the RealPresence Resource Manager system server
resides.
Use Current Time
Select this option to input the current date and time.
Use External NTP Server Time
Synchronization
Select this option to synchronize the RealPresence Resource Manager
system date and time with an external NTP server.
IP address or DNS resolved name
The IP address or fully qualified domain name (ASCII only) of the NTP server.
If needed, enter multiple servers separated by a space.
3 Click Update.
Polycom, Inc.
411
Network Settings
System Licensing
The device management capacity for a RealPresence Resource Manager system with the scales from 100
to 50,000 devices. The minimum capacity of a RealPresence Resource Manager system is of 100 client
access licenses. Additional licensing is offered in 100, 500, and 1000 license pack sizes.
When applied to the system, an expansion license pack augments the device license count.
Device licenses are consumed based on a 1:1 basis for any managed device (endpoints, MCU, GW—
including personal endpoints, and more) that can be added to the system by any means, including the user
interface, registration for management services, or registration for Global Address Book services. This
includes the following device types:
● Endpoints synchronized from an integrated RealPresence DMA system
● Any managed video endpoint, both dynamic and scheduled (RealPresence Immersive Studio
systems and other Polycom ITP systems consume three device licenses, one for each codec.)
● Any managed audio endpoint
● A RealPresence Access Director system
● A RealPresence DMA system
● A RealPresence Collaboration Server
● A Cisco Unified Communications Manager
Device licenses are consumed by managed devices, not by users. You may add any number of local
or enterprise users to the RealPresence Resource Manager system.
The RealPresence Resource Manager system has the following feature licenses:
Field
Description
Multi-Tenancy
Enables you to use the areas feature to partition collections of resources.
Management of Endpoints and
Services
Determines the number of devices you can manage.
If you are a RealPresence One customer, this license is disabled and
governed by your RealPresence One subscription.
Service Provider API
Enables you to access RealPresence Resource Manager functionality via the
API
Redundant system licenses
(primary and redundant licenses)
Enables you to set up redundant systems.
Media Encryption
Enables encryption for chat and presence (XMPP) service.
Licensing for RealPresence software clients is included with the RealPresence Resource Manager system.
RealPresence software clients include Polycom CMA Desktop, RealPresence Desktop and RealPresence
Mobile clients.
When a software client is provisioned by the RealPresence Resource Manager system, it automatically
consumes a license. That license is then reserved for that client. However, you can configure the system to
automatically release a RealPresence client license after a set time (days) of inactivity.
Polycom, Inc.
412
Network Settings
See Reclaim Software Client Licenses.
Dynamically managed Polycom endpoints (both hardware and software endpoints) are automatically
deleted from the system after six months of inactivity, which is independent of the license reclamation for
Polycom software endpoints.
Endpoints that are not dynamically managed are never automatically released. To release a license from a
registered endpoint, an administrator must manually delete the device from the system.
Trial Licenses for Appliance Editions
Appliance editions come with a trial license file that is valid for 60 days after activating your system. The trial
license also enables the optional Polycom RealPresence DMA system integration, multi-tenancy, and
Service Provider API capabilities for 60 days.
With your system order for an appliance edition, you will receive one or more License Certificates. You must
activate the License Certificate to receive a license file, which you then upload to the RealPresence
Resource Manager system. When you update this license file, it overwrites the trial license file.
Licenses for Virtual Editions
RealPresence Resource Manager is now available as part of Polycom RealPresence Clariti, a Polycom
collaboration infrastructure offer that features simplified concurrent user licensing and add-on options. If you
are a RealPresence Clariti customer, you must use the RealPresence Resource Manager system to license
your products.
See Managing RealPresence Platform Product Licenses for details about license management.
View Current Licensing
You can view the current licensing status and information.
To view current system licensing for an Virtual Edition:
1 Go to Admin > Server Settings > Licenses.
The Licenses page displays the following license related information when you have a virtual edition.
 System licensing is handled by the license server. Please check the license server for license
details.
 License Server Address
 License Server Port
 Last time connecting to the license server successfully
 Last time attempting to connect to license server
 End User License Agreement
 Status

Automatically send usage data
 Reclaim Inactive RealPresence Software Client Licenses
Polycom, Inc.
413
Network Settings
The Licenses page displays the following information when you have an appliance edition.
 Software Version
 Serial Number
 Supported Versions
 Server Type
 Licenses Status
 Site Duration
 End User License Agreement
 Status

Automatically send usage data
 Reclaim Inactive RealPresence Software Client Licenses
Add System Licenses for an Appliance Edition
If you are not a RealPresence Clariti customer, adding licenses to your RealPresence Resource Manager
system, Appliance Edition is a two step process:
● Request a Software License File
● Update the License File
These processes are described in the following topics.
Request a Software License File
If you are not a RealPresence Clariti customer and have an appliance edition, you need to request a license
file from the Polycom technical support website.
To request a software license file:
1 In a separate browser page or tab, log into the RealPresence Resource Manager system server as
an administrator.
2 Go to Admin > Server Settings > Licenses and record the RealPresence Resource Manager
system server serial number.
3 Go to http://support.polycom.com.
4 In the Licensing & Product Registration section, select Activation/Upgrade.
5 Log in or Register for an Account.
6 Select Site & Single Activation/Upgrade.
7 In the Site & Single Activation page, enter the serial number you recorded in step 2.
8 Click Next.
9 Accept the EXPORT RESTRICTION agreement.
Polycom, Inc.
414
Network Settings
10 In the new Site & Single Activation page, enter the serial number listed on your License Certificate
and enter the license number (shipped with the product) and click Activate.
If retrieving licenses for a redundant system, repeat this step for each server in your configuration.
You will need to load both license files onto your primary server, see System Redundancy.
11 In the Key Code field, click click here to download to retrieve and save your license files.
Update the License File
You can update the license file for your appliance edition system at any time. For example, if you purchase
more device licenses or add features. After you update a license file, you must logout and re-login to the
system to see newly licensed features.
To update the license file:
1 Go to Admin > Server Settings > Licenses.
2 Click Update License to view the Update License dialog box.
3 Click Choose File to navigate to the license file you received from Polycom.
4 Click Preview to preview the license features.
5 On the Update License dialog, click Update.
6 You must log out of the system and log back in to view any new licensed features such as
multi-tenancy or RealPresence DMA integration features.
Sending Usage Data
To continually improve the product, it is important to gain understanding of how the RealPresence Resource
Manager system is used by customers. By collecting this data, Polycom can identify both the system level
utilization and the combination and usage of RealPresence Resource Manager features. This usage data
will inform Polycom which features are important and are actually used on your system. Polycom will use
this information to help guide future development and testing to concentrate on the areas of RealPresence
Resource Manager that are most heavily used. If you choose not to send this information, Polycom is less
aware of which features are important to you and that are used by you, which may influence future
development to go in directions that are less beneficial to you.
Your decision to enable or not enable the sending of this data does not affect the availability of any
documented system feature in any way.
The system sends the data once per hour over a secure TLS connection (port 8443) to a Polycom collection
point (customerusagedatacollection.polycom.com). There is no access by any customer or others to view
the data received at the collection point. The raw data will be viewable only by Polycom. To avoid any impact
to starting and ending calls and conferences, data is never sent between 5 minutes before the hour and 5
minutes after the hour.
The following types of data are reported:
● License information
● Hardware configuration
● System resource usage: CPU, RAM, disk, database
● System configuration: number of servers, clusters
Polycom, Inc.
415
Network Settings
● Feature usage: Enterprise Directory integration, conference, endpoints, network topology, user
management, alert management, and license management.
● Number of users, endpoints, sites, and MCUs.
● Security settings
When this information is reported, a customer’s user and environment identifying information (such as
internal IP addresses, and FQDNs, names of users, devices, and external systems) is made anonymous
before being sent from the system. System serial numbers and license information are sent without
anonymization and may be used to help improve customer experiences. In total, less than 100KB of data
per hour is collected and sent.
Enable or Disable User Data Collection
You can enable or disable this feature at any time.
To enable or disable user data collection:
1 Go to Admin > Server Settings > Licenses.
2 Select or clear the Automatically send usage data check box.
See the Collected Usage Data
The system records data that has been sent and collected in the system logs.
To see the collected data:
1 Log in to the RealPresence Resource Manager system as an Administrator.
2 Download the system logs.
3 On the PC where the logs have been downloaded, use an archiving or zipping tool to extract the file
analytics.json.
Analytics.json is a text file containing the hourly data reported most recently before the time when the
system logs were created.
4 View the analytics.json file with Notepad or another common text editing tool.
See System Log Overview.
Reclaim Software Client Licenses
Polycom RealPresence Desktop, RealPresence Mobile and CMA Desktop clients do not release licenses
automatically when they are not in use. You can reclaim software client licenses by setting a reclaim
threshold.
To reclaim licenses more quickly, lower the threshold. Set the threshold to zero to stop reclaiming licenses.
The threshold time limit is measured in days.
However, unlicensed software endpoints are kept in the system until the total number of soft endpoints
(licensed and unlicensed) exceeds 90 percent of four times the number of allowed licenses. This allows
software endpoints to remain in the RealPresence Resource Manager system, retain their dial string
reservations, and to be scheduled into conferences.
Polycom, Inc.
416
Network Settings
For example, if you have purchased a license for 500 endpoints, you can keep up to 90 percent of four times
500, or 1800 total endpoints (software and hardware) in the system at one time. While only 500 of those
endpoints will be licensed, unlicensed software endpoints will remain associated with user dial strings so
that the user can still be scheduled into conferences and remains in the system if the user wants to use the
software endpoint at any time.
The RealPresence Resource Manager system automatically deletes unlicensed software endpoints when
the 90 percent of four times the number of allowed licenses is reached. It started deleting software endpoints
based on number of days of inactivity, starting with the most number of days.
To set the threshold for reclaiming inactive software client licenses:
1 Go to Admin > Server Settings > Licenses.
2 Change the Threshold value in the Reclaim Inactive RealPresence Software Client (Mobile and
Desktop) Licenses section of the Licenses page. The threshold time limit is measured in days.
To reclaim licenses more quickly, lower the threshold. Set the threshold to zero days, to stop
reclaiming licenses.
3 Click Update.
Customizing System Logos
You can add your company logo to the RealPresence Resource Manager system interface as well as to the
CMA Desktop system interface.
Add a System Logo
You can add your company’s logo to the RealPresence Resource Manager system user interface. To avoid
distortion, we recommend adding a logo in GIF, JPG, or PNG format with a size of 300 x 44 pixels.
The system logo added with these steps is viewed only by users with system roles that have permission to
view all areas and do not belong to an area. If you want to customize a logo for an area, you must use have
Area admin permissions and use the Admin > Area Logos option.
See Customizing the Area Logos (system and CMA Desktop) for the Area for more information about
customizing area logos.
To add a custom logo to the RealPresence Resource Manager system user interface:
1 Go to Admin > Server Settings > System Logos.
2 In the Resource Manager System Logo section, click the Browse button to select a system logo
file to be used.
3 Click Upload.
Remove a System Logo
You can remove a custom logo at any time.
Polycom, Inc.
417
Network Settings
To remove a system logo from the RealPresence Resource Manager system user interface:
1 Go to Admin > Server Settings > System Logos.
2 In the Resource Manager System Logo section, click Remove.
Edit the System Email Account
The system email account is used for conference notifications as well as system alert emails.
To edit the RealPresence Resource Manager system email account:
1 Go to Admin > Server Settings > E-mail.
2 On the E-mail page, edit the email account (ASCII only) from which the RealPresence Resource
Manager system will send conference notification emails or edit the IP address of the mail server
from which the RealPresence Resource Manager system will send conference notification emails.
Many email servers will block or discard emails without a qualified From: address. To avoid this issue,
make sure each person with Scheduler permissions has a valid email address. Many email servers
will block or discard emails from un-trusted domains, in which case you may need to change the
default RealPresence Resource Manager system email address to one in a trusted domain.
3 Click Update.
Polycom, Inc.
418
Understanding System Administration
This section describes the Polycom® RealPresence® Resource Manager system Dashboard.
System Dashboard
When you log into the RealPresence Resource Manager system with Administrator role and permissions,
the system first displays the system Dashboard. Use the system Dashboard to view information about
system health and activity levels.
The system Dashboard displays data in an array of charts, forms, data grids, and other graphical displays.
You can modify your system Dashboard layout by moving, closing, and restoring panes. Also note that your
changes to the system Dashboard are persistent not just for a session but between logouts and logins.
Dashboard Panes
Within the Dashboard, you can customize the panes you see by selecting the following panes under the
Add Panes drop-down list.
● Today’s Scheduled Conferences
● Endpoint Number
● CPU/Memory/Disk
● Users
● Today’s Adhoc Conferences
● Hardware Usage
● Endpoint Type
● Site Map
● Service Groups
● Today’s Conferences Statistics
● System Info
● Endpoints (multiple, configurable panes)
● Pre-call Status
● MCU Status (multiple, configurable panes)
● Users Logged In
● Redundancy Status
● Resource Manager Licenses
● CUCM
Polycom, Inc.
419
Understanding System Administration
● DMA
Today’s Scheduled Conferences
The Today’s Scheduled Conferences pane displays information about the scheduled conferences
managed by the RealPresence Resource Manager system. For the current day (starting at 0:00 and ending
at 24:00), it displays:
● The number of scheduled conferences that were Completed that day
● The number of scheduled conferences that are Active at the current time
● The number of scheduled conferences that are yet to occur (Future)
Endpoint Number
The Endpoint Number pane displays the number of endpoints registered with the RealPresence Resource
Manager system.
CPU/Memory/Disk
This pane displays general information about the current CPU, memory, and disk usage of the system.
When the CPU and memory usage is under 75%, the color is green. When the usage is between 75% and
90%, the color is yellow. When the usage is over 90%, the color is red.
Users
This pane displays the total number of local users (with endpoints associated), enterprise users, rooms, and
guests.
Today’s Adhoc Conferences
The Today’s Adhoc Conferences pane displays information about the ad hoc conferences started by
video endpoints registered to the RealPresence Resource Manager system. For the current day (starting at
0:00 and ending at 24:00), it displays:
● The number of ad hoc conferences that were Completed for the current day.
● The number of ad hoc conferences that are Active at the current time.
Ad hoc conferences that take place on MCUs that are managed by the RealPresence DMA system
cannot be accurately monitored by theRealPresence Resource Manager. Monitoring information will
be incorrect and inconsistent.
Hardware Usage
This pane displays the temperature, battery, and cooling fan status. You can only see this pane on the
appliance edition.
Polycom, Inc.
420
Understanding System Administration
● Temperature—Temperature status information provided by the Polycom-branded Dell server agent
through its MIB.
● Battery Status—Battery status information provided by the Polycom-branded Dell server agent
thought its MIB.
● Cooling Fan—Fan status information provided by the Polycom-branded Dell server agent thought
its MIB.
Endpoint Type
The system enables you to add multiple Endpoint Type panes. When you add an Endpoint Type pane,
you can give the pane a meaningful name and select to display the endpoints by type, by site, or by endpoint
group. You can save the pane and create others as needed. You can also reconfigure an Endpoint Type
pane using the configuration tool.
When your mouse stays on a specific type of endpoint on the meter, the endpoint name and number will be
shown.
Site Map
This pane displays the site topology. See Setting Up Site Topology for details.
Service Groups
This pane displays the service groups. See Managing Service Groups for details.
Today’s Conferences Statistics
Select Scheduled Conference, Adhoc conference, or Both form the Type drop-down list to display the
information about:
● Scheduled conferences managed by the RealPresence Resource Manager system. For the current
day (starting at 0:00 and ending at 24:00), it displays a bar chart that displays time on the linear axis
plotted against the number of scheduled conferences on the horizontal axis
● Ad hoc conferences started by video endpoints registered to the RealPresence Resource Manager
system. For the current day (starting at 0:00 and ending at 24:00), it displays a bar chart that displays
the number of ad hoc conferences (vertical axis) plotted against time of day (horizontal axis)
System Info
This pane displays general information about the system, including:
Field
Description
Server Time
Displays the current time of the RealPresence Resource Manager system.
Last JServer Start
Time
The last time when JServer started.
Polycom, Inc.
421
Understanding System Administration
Field
Description
Server Address
The IP address of the RealPresence Resource Manager system.
Software Version
The RealPresence Resource Manager system version number.
Hardware Version
The Dell hardware version of the system.
• Rev D, R620
• Rev E, R220
• Rev F, R630
• Rev G, R230
Remote Access
Displays whether or not Remote Desktop Connection is enabled
Provisioning in
Progress
Displays the number of scheduled endpoint provisioning processes that are currently
underway.
Software Updates in
Progress
Displays the number of scheduled endpoint software update processes that are currently
underway.
Failed Logins (last 24
hours)
The total number of Failed Logins for Active Directory users in the last 24 hour period.
Endpoints
The system enables you to add multiple Endpoints panes so you can create your own scheme for grouping
and monitoring endpoints. When you add an Endpoints pane, you can give the pane a meaningful name
and select which endpoints to monitor. You can save the pane, create others as needed. You can also
reconfigure an Endpoints pane using the configuration tool.
Each Endpoints pane can list up to 500 endpoints.
Endpoints panes display the following information:
● The number of endpoints being monitored
● The number of monitored endpoints that are In a Call
● The number of monitored endpoints that are Online
● The number of monitored endpoints that are Offline
Pre-call Status
The Pre-call Status pane displays information about the next conference or conferences that are
scheduled to launch including:
Field
Description
Time to Conference
Displays the system-defined pre-call status reporting time of 10 minutes. In other words,
the Pre-call Status pane always reports on conferences that are scheduled to start in the
next 10 minutes.
Scheduled to Launch
Displays the number of conferences scheduled to start in the next 10 minutes.
Polycom, Inc.
422
Understanding System Administration
Field
Description
Ready to Launch
Displays the subset of conferences that are scheduled to start in the next 10 minutes and
that have passed the resource tests that the system executes before launching a
conference.
Ready to Launch with
Device in Call
Displays the subset of conferences that are scheduled to start in the next 10 minutes and
that have passed the resource tests but that still have one or more devices in another call.
NOT Ready to
Launch
Displays the subset of conferences that are scheduled to start in the next 10 minutes but
that have not yet passed the resource tests.
Also displays the conferences that are not ready to launch.
MCU Status
The system enables you to add multiple MCU Status panes so you can create a pane for all or individual
MCUs registered with the RealPresence Resource Manager system. When you add an MCU Status pane,
you can give the pane a meaningful name and either select an MCU to monitor or select All MCUs. You can
save the pane, create others as needed. You can also reconfigure an MCU Status pane using the
configuration tool.
The MCU Status pane for All MCUs displays the following information:
If your system has areas enabled, you will be able to view only the MCUs that belong to areas that you
have been assigned to manage.
:
Field
Description
Errors
Displays the cumulative number of alarms for all of the registered MCUs.
Warnings
Displays the cumulative number of warnings for all of the registered MCUs.
Active Conferences
Displays the total number of active conferences being hosted by all of the registered
MCUs.
The MCU Status pane for an individual MCU displays the following information:
Field
Description
Errors
Displays the number of alarms on the MCU.
Warnings
Displays the number of conferences that are active on the MCU at the current time.
Active Conferences
Displays the number of active conferences currently being hosted by the MCU.
Number of Audio
Ports
Displays the number of dedicated audio ports configured on the MCU.
Audio Ports
Utilization
Displays two views of the MCU audio port usage:
• A sparkline that presents the audio port usage over time
• A percentage indicator that shows the current usage
Polycom, Inc.
423
Understanding System Administration
Field
Description
Number of Video
Ports
Displays the number of video ports configured on the MCU.
Video Ports
Utilization
Displays two views of the MCU video port usage:
• A sparkline that presents the video port usage over time
• A percentage indicator that shows the current usage
Expected Port
Utilization
A timeline that shows how many ports are scheduled for conferences within the next 45
minutes.
This status information is sent by the MCU to the RealPresence Resource Manager system.
In addition, the MCU Status pane identifies when the monitored MCU is experiencing alert conditions.
Users Logged In
The Users Logged In pane displays the type and number of users that are currently logged into the system.
A sparkline presents the number of logins over time (30 minutes total; updated every 5 minutes so there are
6 data points on the sparkline) for each user type.
The system identifies three user types by their permissions: Administrators, Operators, and Schedulers.
Note that these three user types are not necessarily the same as user roles. For example, users assigned
the default Administrator and default Device Administrator roles appear in this pane as Administrators.
And users assign the default View Only Scheduler, default Scheduler, and default Advanced Scheduler
roles appear in this pane as Schedulers.
For more information, see Working with Management Roles and Permissions.
Redundancy Status
The Redundancy Status pane displays information about the RealPresence Resource Manager system
redundancy configuration, including:
● Whether or not the system is configured for redundancy. Possible values for Status are Configured
or Not Configured.
● The Virtual IP Address for the redundant system. If it is not configured for redundancy, the value will
be No.
● The IP address of the Active Server.
● The IP address of the Backup Server.
Resource Manager Licenses
The Resource Manager Licenses pane displays information about how the system is licensed, including:
● The Total Number of Licenses available on the system
● The Licenses in Use.
Polycom, Inc.
424
Understanding System Administration
CUCM
The CUCM pane displays the information about the integrated Cisco Unified Communication Manager
information.
DMA
The DMA pane displays the information about the integrated RealPresence DMA information.
Polycom, Inc.
425
Securing the System
This section describes the Polycom® RealPresence® Resource Manager system management and security
tasks. It includes these topics:
● System Security
● Managing Security Baselines
● Configure Secure Communication
● Configure TLS Settings
● Configure System Hardening
● Session Security and User Access
System Security
You can configure various security features of your system. You can determine how you want to work with
security certificates, you can make the system’s operating system more secure as well as configure session
management and password settings.
Security settings work in tandem with the security certificates you have installed. For example, if you enable
strict TLS settings, you will need to add the required certificates to your system and systems that need to
communicate with the RealPresence Resource Manager system, such as endpoints the system manages
or network devices.
Managing Security Baselines
Security baselines are a snapshot of the system’s security settings that you can save in order to apply or
audit at a later time.
The system comes with two baselines ready for use:
● Standard Security Baseline Settings
● High Security Baseline Settings
Unless you require a maximum level of security, you should use the Standard Security Baseline Settings.
You can audit your security settings against a saved baseline to easily view any security settings you have
changed since that baseline was created.
You can also apply an existing baseline to your RealPresence Manager system. However, if you try to apply
a security baseline that will disallow a configured function, the application will fail to update security settings
that are in conflict with configured system functions.
How you use security settings is dependent on how you have configured certificates for your system.
Polycom, Inc.
426
Securing the System
Standard Security Baseline Settings
The Standard Security Baseline is applied by default. You can customize any security settings when the
Standard Security Baseline is applied.
Secure Communication Settings
Field
Enabled?
HTTP: Enforce Secured http
No
Inbound: false
Outbound: false
LDAP: Enforce Secured
LDAP
No
Inbound: false
Outbound: false
FTP: Enforce Secured FTP
No
Outbound: false
SMTP: Enforce Secured
SMTP
No
SNMP: Enforce Secured
SNMP v3
No
Disable GDS (Global
Directory Service)
No
Disable Outbound Telnet
No
TLS Settings
Field
Enabled?
Cipher Mode
Standard Ciphers
Enabled Protocols
TLS1.2 : true
TLS1.1 : true
TLS1.0 : true
SSLv3 : false
Validate Certificates for Connections from Clients
No
Validate Certificates for Connections to Servers
No
Verify Hostname
No
Enable FIPS -140
No
Check Revocation Status
No
Polycom, Inc.
427
Securing the System
System Hardening Settings
Field
Enabled?
Enable NIDS
Yes.
Ignore Redirect Flag
Yes.
Allow ICMP (ping) responses
Yes.
Respond to ICMP (ping) requests with Destination Unreachable message
No.
Allow traces for troubleshooting
Yes.
Allow Linux console access
Yes.
Disable Root User Login
No.
SSH Access
Disable
Lock Bios
No.
Session Management Settings
Field
Enabled?
Resource Manager user interface timeout (minutes)
No.
Maximum number of sessions per user
No.
Maximum number of sessions per system
No.
Enable Banner
No.
User Account Configuration
Field
Enabled?
Account Lockout
Failed login threshold
Yes. Threshold is set to 3 failed attempts.
Failed login window (hours)
Yes. Time span is set to1 hour.
Customized user account lockout duration (minutes)
No.
Account Inactivity
Customize account inactivity threshold (days)
Polycom, Inc.
No.
428
Securing the System
Password Requirements
Field
Enabled?
Password Management
Minimum length (characters)
Yes. Minimum length is 8 characters.
Minimum changed characters
Yes. Minimum number of changed character is 1.
Minimum password age (days)
No.
Maximum password age (days)
No.
Password warning interval (days)
Yes. Password warning interval is set to 7 days.
Reject previous passwords
No.
Password Complexity
Lowercase letters
No. Lowercase letters are not required
Uppercase letters
No. Uppercase letters are not required.
Numbers
No. Digits are not required.
Special characters
No. Special characters are not required.
Maximum consecutive repeated characters
No. Repeated character are not restricted.
OS Account Password Policy
Apply rules to the OS account
No.
Conference PIN Code
Minimum length
4
Maximum length
16
Maximum consecutive repeated characters
2
Sensitive Information Disclosure
Sensitive information disclosure settings determine whether software version information is displayed to the
user.
Field
Enabled?
Generalized Message
No. When disabled, users see system-specific error messages.
Show Software Build Number
Yes.
Polycom, Inc.
429
Securing the System
High Security Baseline Settings
You should use the high security baseline settings only when you require maximum levels of security. When
you select the high security baseline, the SSH Access is set to Disabled Permanently. This setting
becomes read-only and you cannot change it back.
Secure Communication Settings
Field
Enabled?
HTTP: Enforce Secured http
Yes
Inbound: true
Outbound: true
LDAP: Enforce Secured
LDAP
Yes
Inbound: true
Outbound: true
FTP: Enforce Secured FTP
Yes
Outbound: true
SMTP: Enforce Secured
SMTP
Yes
SNMP: Enforce Secured
SNMP v3
Yes
Disable GDS (Global
Directory Service)
Yes
Disable Outbound Telnet
Yes
TLS Settings
Field
Enabled
Cipher Mode
Strong Ciphers
Enabled Protocols
TLS1.2: false
TLS1.1: true
TLS1.0: true
SSLv3: false
Validate Certificates for Connections from Clients
Yes
Validate Certificates for Connections to Servers
Yes
Verify Hostname
Yes
Enable FIPS -140
Yes
Check Revocation Status
Yes
Polycom, Inc.
430
Securing the System
System Hardening Settings
Field
Enabled?
Enable NIDS
Yes
Ignore Redirect Flag
Yes
Allow ICMP (ping) responses
No
Respond to ICMP (ping) requests with Destination Unreachable message
No
Allow traces for troubleshooting
No
Allow Linux console access
No
Disable Root User Login
Yes
SSH Access
Disabled Permanently
Lock Bios
Yes
Session Management Settings
Field
Enabled?
RealPresence Resource Manager user interface timeout (minutes)
Yes
User interface timeout is
set for 10 minutes.
Maximum number of sessions per user
Yes
Maximum number of
sessions per users is set
to 5 sessions.
Maximum number of sessions per system
Yes
Maximum number of
sessions is set to 50
sessions.
Enable Banner
Yes
User Account Configuration
Field
Enabled?
Account Lockout
Failed login threshold
Yes. Threshold is set to 3 failed attempts.
Failed login window (hours)
Yes. Time span is set to 1 hour.
Customized user account lockout duration (minutes)
No
Polycom, Inc.
431
Securing the System
Field
Enabled?
Account Inactivity
Customize account inactivity threshold (days)
Yes. Threshold is set to 30 days.
Password Requirements
Field
Enabled?
Password Management
Minimum length (characters)
Yes. Minimum length is 15 characters.
Minimum changed characters
Yes. Minimum number of changed character is 4.
Minimum password age (days)
Yes. Password can be changed only once per day.
Maximum password age (days)
Yes. Password expires after 60 days.
Minimum system password age (days)
Yes. Password expires after 360 days
Password warning interval (days)
Yes. Password warning interval is set to 7 days.
Reject previous passwords
Yes. Previous 10 passwords will be rejected.
Password Complexity
Lowercase letters
Yes. Two lowercase letters are required
Uppercase letters
Yes. Two uppercase letters are required.
Numbers
Yes. Two digits are required.
Special characters
Yes. Two special characters are required.
Maximum consecutive repeated characters
Yes. Only two repeated character are allowed.
OS Account Password Policy
Apply rules to the OS account
No
Conference PIN Code
Minimum length
Yes. Minimum length is 9 characters.
Maximum length
Yes. Maximum length is 16 characters.
Maximum consecutive repeated characters
Yes. Only two consecutive repeated characters are allowed.
Sensitive Information Disclosure
Sensitive information disclosure settings determine whether software version information is displayed to the
user.
Polycom, Inc.
432
Securing the System
Field
Enabled?
Generalized Message
Yes. When enabled, only generalized error messages are displayed to the user.
Show Software Build Number
No
Create a Security Baseline
When you add a security baseline, you are saving a list of the currently configured system security settings
for the system. Creating a security baseline allows you to easily audit your system against the baseline to
see what changes were made since the baseline was created.
To create a new security baseline:
1 Go to Admin > Management And Security > Security Baseline.
2 Click
.
3 In the Add Baseline dialog, enter a Name and Description for your baseline.
4 Click OK.
The new Security Baseline is listed in the Security Baseline list. It includes the date and time it was
created as well as the user who created it.
View a Security Baseline
You can view the configuration of an existing security baseline.
To view a security baseline:
1 Go to Admin > Management And Security > Security Baseline.
2 Select a baseline.
3 Click
.
The configuration information will appear on the right.
4 Expand each item to view the settings.
Edit a Security Baseline
You can edit the security baselines that you created. The High Security Baseline Settings and Standard
Security Baseline Settings cannot be edited.
To delete a security baseline:
1 Go to Admin > Management And Security > Security Baseline.
2 Select a baseline.
3 Click
.
4 Modify the Name and Description if needed.
Polycom, Inc.
433
Securing the System
5 Click OK to save the changes.
Delete a Security Baseline
You can delete the security baselines that you created. The High Security Baseline Settings and
Standard Security Baseline Settings cannot be deleted.
To delete a security baseline:
1 Go to Admin > Management And Security > Security Baseline.
2 Select a baseline.
3 Click
.
4 Click OK to confirm the deletion.
Apply Security Baseline
After you apply an existing security baseline to your system, the security options of the existing baseline will
take effect. You do not need to configure the settings one by one. After applying an existing security
baseline, you can customize security options; for example, TLS and system hardening.
When you apply a system baseline, the system will reboot.
To view a security baseline:
1 Go to Admin > Management And Security > Security Baseline.
2 Select an existing baseline.
3 Select More > Apply Baseline.
The system will reboot.
Audit Your System Against a Security Baseline
You can audit your security settings at any time. Auditing your system against a saved security baseline
allows you to easily see how your settings differ from the settings within that security baseline.
To audit your security settings using a security baseline:
1 Go to Admin > Management And Security > Security Baseline.
2 Select a security baseline from the list.
3 Click More > Audit Baseline.
The Audit Baseline Results dialog lists the security settings that differ from the selected Security
Baseline and includes the following information.
Polycom, Inc.
434
Securing the System
Field
Description
Option
Lists the current security setting that differs from the selected security baseline.
Baseline Value
Lists the value of the security setting that is stored in the selected security
baseline.
Current Setting Value
Lists the current value of the listed security setting.
4 Click Close.
Configure Secure Communication
You can configure secured communications for the following protocols: HTTP, LDAP, FTP, SMTP, SNMP,
Global Directory Services (GDS) and Outbound Telnet.
To configure secure communication:
1 Go to Admin > Management And Security > Secure Communication.
2 Enable secured communication settings for the following protocols:
Field
Description
HTTP: Enforce Secured http
Enabling this option may impact services using HTTP, such as scheduled
endpoint management, remote endpoint reboot, and MCU management using
HTTP.
LDAP: Enforce Secured
LDAP
After enabling secured LDAP, you must select either .LDAPS or StratTLS as
Security Level when configuring Enterprise Directory integration. See Enable
Integration with the Enterprise Directory Server on how to configure Security
Level.
FTP: Enforce Secured FTP
Enabling this option may impact services using FTP, such as backing up the
system using FTP.
SMTP: Enforce Secured
SMTP
Enabling this option may impact services using SMTP.
SNMP: Enforce Secured
SNMP v3
Enabling this option may impact services using SNMP v3. SNMP v2 will be
disabled if you enable this option.
Disable GDS (Global
Directory Service)
After GDS is disabled, Polycom Global Address Book cannot be used.
Disable Outbound Telnet
After outbound telnet is disabled, the server controlled endpoint dialing out and
hanging up functions will be impacted.
Configure TLS Settings
You can configure how the RealPresence Resource Manager deals with security certificates. How you set
up your TLS settings determines the level of security you have for your system.
Polycom, Inc.
435
Securing the System
If you choose to use the High Security Baseline Settings, most of these settings cannot be changed.
For example, you can require all clients attempting to access the system to present a certificate.
After you install a full PKI chain, you should delete the self-signed certificates of any system on which
the self-signed certificate has been replaced with a CA signed certificate.
Self-signed certificates are not allowed when the system is in maximum security mode.
To configure TLS settings:
1 Go to Admin > Management and Security > TLS Settings.
2 For TLS Settings, use the following table as guidance:
Field
Description
Cipher Mode
You can choose from the following cipher modes:
• Standard Ciphers When you choose Standard Ciphers, all the supported Ciphers
can be used. See for all the supported Ciphers.
• Weak Ciphers The supported Ciphers with key size less than 128 bits.
• Strong Ciphers The supported Ciphers with key size equal to or more than 128 bits.
When you use the High Security Baseline Settings, Cipher mode is set to Strong
Ciphers and cannot be changed.
See Appendix B: Supported Ciphers for the list of supported Ciphers.
Validate Certificates
for Connections from
Clients
This setting requires all clients (endpoints, peripherals, and users accessing the
RealPresence Resource Manager system web interface over an encrypted protocol such
as SSL or TLS) to send identity certificates in order to access the system.
You must have at least one CA certificate installed if you want to validate external
certificates.
If you are using the UC-APL security settings, this setting is enabled by default, but can
be configured. During First Time Setup you should uncheck this setting; it will be checked
later after completing First Time Setup (this can help avoid connection problems from
occurring during initial configuration).
Validate Certificates
for Connections to
Servers
This setting requires all servers (other Polycom systems such as the RealPresence DMA
system or the RealPresence Collaboration server as well as third-party integrations),
accessing the RealPresence Resource Manager system web interface over an encrypted
protocol such as SSL or TLS) to send identity certificates in order to access the system.
You must have at least one CA certificate installed if you want to validate external
certificates.
Mark the Verify Hostname setting if you want to verify the host name (IP address) of the
server. With Verify Hostname enabled, IP address will be used to validate the CA
certificate of RealPresence Resource Manager. Therefore the SAN must contain the IP
address of the server (RealPresence Resource Manager), otherwise, verifying host name
will fail.
See Security Certificates for details.
Polycom, Inc.
436
Securing the System
Field
Description
Enable FIPS -140
When you enable FIPS-140, Strong Ciphers and Validate Certificates for
Connections to Servers are automatically checked and cannot be disabled.
You cannot use TLSv1.2 for Microsoft Active Directory connections if you enable
FIPS-140.
Check Revocation
Status
This option is available only when you check the Validate Certificates for Connections
from Clients or Validate Certificates for Connections to Servers check boxes. When
enabled, RealPresence Resource Manager will check if the CA is revoked or not.
3 Click Update.
Configure System Hardening
Operating system hardening is the process of securely configuring the system against the unauthorized
access, intruders, hackers and other security vulnerabilities. System hardening makes the computer system
more reliable, secure, efficient and gives the optimized performance.
System hardening may also disable features that you may want to use. Select these options carefully.
To configure System Hardening:
1 Go to Admin > Management and Security > System Hardening.
2 For System Hardening, use the following table as guidance:
Field
Description
Enable NIDS
Allows the Network Instruction Detector System to run.
Ignore Redirect Flag
Redirect flags will be ignored.
Allow ICMP (ping)
responses
You can choose to disallow the RealPresence Resource Manager to respond to ping
messages.
Respond to ICMP
(ping) requests with
Destination
Unreachable message
If you choose to allow the server to respond to ping requests, you can configure a
Destination Unreachable message.
Allow traces for
troubleshooting
Troubleshooting traces are not encrypted, you can disable these.
Allow Linux console
access
You can disable Linux console access to the RealPresence Resource Managerserver.
This setting disables console access for all users.
Disable Root User
Login
Root user login is disabled.
SSH Access
Allow users to use SSH to access RealPresence Resource Manager system.
Note: The Disable Permanently option is irrevocable.
Lock Bios
(Appliance Only) Bios access is protected by complicated password after enable Lock
Bios.
Polycom, Inc.
437
Securing the System
Session Security and User Access
You can control various aspects of user sessions with the RealPresence Resource Manager system’s web
interface.
This section includes the following topics:
● Change the System User Interface Timeout and Number of Sessions
● Control Remote Connections to the System
● Enabling and Editing Log In Banners
● Set Local Account Lockout and Timeout
● Set Password Requirements
● Setting Management Access Settings
● Set Sensitive Information Disclosure
● Reset System Passwords
Change the System User Interface Timeout and
Number of Sessions
You can modify the length of the user interface time out as well as set up parameters for how many active
sessions are allowed.
To change the system user interface timeout and number of sessions:
1 Go to Admin > Management and Security > Session Management.
2 On the Session Management page, configure these settings as needed.
Field
Description
RealPresence Resource
Manager user interface
timeout (minutes)
By default, the RealPresence Resource Manager system user interface times out
after 10 minutes of inactivity. Use this procedure to change the timeout value for
the user interface inactivity timer. Possible value is 5 to 60 minutes.
Maximum number of
sessions
The number of simultaneous login sessions by all users. By default, the maximum
number of sessions by all users is 50. Possible value is 2 to 50 sessions.
This setting is available only when RealPresence Resource Manager is in
maximum security mode.
Note
If this limit is reached, but none of the logged-in users is an Administrator, the first
Administrator user to arrive is granted access, and the system terminates the
non-Administrator session that’s been idle the longest.
Maximum number of
sessions per user
The number of simultaneous login sessions per user ID. By default, the maximum
number of sessions per user ID is 5. Possible value is 1 to 10 sessions.
3 Click Update.
Polycom, Inc.
438
Securing the System
Control Remote Connections to the System
By default, users can access the RealPresence Resource Manager system through the Linux console. You
can disable this ability.
To disallow Linux console access:
1 Go to Admin > Management and Security > System Hardening.
2 Clear the Allow Linux console access option.
3 Click Update.
Enabling and Editing Log In Banners
A log in banner is the message that appears when users attempt to access the system. Users must
acknowledge the message before they can log in. By default, the long banner field on the Banner
Configuration page displays the required Standard Mandatory Notice and Consent Provision for systems
operating in a maximum security environment. The short banner field displays a shortened version of this
same notice.
The long banner is used for the RealPresence Resource Manager system log in banner.
The RealPresence Resource Manager system provides several sample long banners. You can use these
banners as is or edit them to create a custom long banner. The RealPresence Resource Manager system
provides a single short banner, which you can also customize. If you customize the banners, remember that
the long banner message may contain up to 5000 characters. The short banner message may contain up
to 1315 characters.
Enable Banner
You must enable banner to show the message when you log into the system.
To enable banner:
1 Go to Admin > Management and Security > Session Management.
2 Check the Enable Banner check box.
3 Click Update.
Edit Banner
The Banner Configuration page allows users assigned the Administrator role to customize the long and
short login banners.
To edit the login banners:
1 Go to Admin > Management and Security > Banner Configuration.
2 To use one of the existing sample long banners:
a From the Message drop-down menu, select the sample banner that most suits your needs.
Polycom, Inc.
439
Securing the System
b Edit the banner as needed. If you edit one of the existing banners, the Message menu selection
changes to Custom.
3 Click Update.
Set Local Account Lockout and Timeout
You can configure failed login thresholds as well as how long a local user account can be locked out after
a failed login.
To set local account lockout and timeout:
1 Go to Admin > Management and Security > User Account Configuration.
2 On the User Account Configuration page, configure these settings as needed.
Field
Description
Account Lockout
Failed login threshold
Specify how many consecutive login failures cause the system to lock an account.
Possible value is 2 to 10.
Failed login window (hours)
Specify the time span within which the consecutive failures must occur in order to
lock the account. Possible value is 1 to 24.
Customized user account
lockout duration (minutes)
Specify how long the user’s account remains locked. Possible value is 1 to 480.
Account Inactivity
Customize account inactivity
threshold (days)
Specify the inactivity threshold that triggers disabling of inactive accounts.
Possible value is 30 to 180.
3 Click Update.
Set Password Requirements
If you have been assigned the Administrator role, you can configure password requirements for local users.
You can change, but not disable password, security requirements by specifying password age, length, and
complexity.
To set local password requirements:
1 Go to Admin > Management and Security > Password Requirements.
2 On the Password Requirements page, configure these settings as needed..
Field
Description
Password Management
Minimum length (characters)
Polycom, Inc.
Specify the number of characters a password must contain. Possible value is
8 to 15.
440
Securing the System
Field
Description
Minimum changed characters
Specify the number of characters that must be different from the previous
password. Possible value is 1 to 4.
Minimum password age (days)
Specify how frequently a password can be changed. Possible value is 1 to 30.
Maximum password age (days)
Specify at what age a password expires. Possible value is 30 to 180.
Password warning interval (days)
Specify when users start to see a warning about their password expiration.
Possible value is 1 to 7.
Reject previous passwords
Specify how many of the user’s previous passwords the system remembers
and won’t permit to be reused. Possible value is 8 to 16.
Password Complexity
Lowercase letters
Specify the number of lowercase letters (a-z) that a password must contain.
Possible value is 1 or 2.
Uppercase letters
Specify the number of uppercase letters (A-Z) that a password must contain.
Possible value is 1 or 2.
Numbers
Specify the number of digit characters (0-9) that a password must contain.
Possible value is 1 or 2.
Special characters
Specify the number of non-alphanumeric keyboard characters that a
password must contain. Possible value is 1 or 2.
Maximum consecutive repeated
characters
Specify how many sequential characters may be the same. Possible value is
1 to 4.
OS Account Password Policy
Apply the above rules to the OS
account
When enabled, all the password rule configuration is applied to OS password.
Conference PIN Code
Minimum length
Specify the number of characters a PIN code must contain. Possible value is
4 to 9
Maximum length
Specify the maximum number of a PIN code. Possible value is 9 to 16.
Maximum consecutive repeated
characters
Specify how many sequential characters may be the same. Possible value is
1 to 2.
Setting Management Access Settings
You can configure a list of IP addresses that will be allowed will be allowed to access the RealPresence
Resource Manager system’s web interface or SNMP information. Once you enable this list, only IP
addresses on the list will be allowed to access the web interface or SNMP information.
This section includes the following topics:
● Configure Management Access
● Disable Management Access
Polycom, Inc.
441
Securing the System
Configure Management Access
You can configure a list of IP addresses that are allowed to access the RealPresence Resource Manager
system’s web interface or SNMP information.
To configure a list of IP addresses:
1 Navigate to Admin > Management and Security > Management Access Settings.
2 In the Whitelist screen, select the Enable Management Access Settings check box.
3 Click
.
4 In the Add Whitelist dialog, specify the IP address(s) to be included.
You can specify IP addresses individually or as a range. If IPv6 is enabled, you can enter either an
IPv4 address or range or an IPv6 address or range.
5 Click Update to save the IP address to the whitelist.
Repeat these steps to continue adding IP addresses or ranges of IP addresses until finished.
6 Click Update on the main page to save your whitelist.
Disable Management Access
After you disable Management Access, all IP addresses will be allowed to access the RealPresence
Resource Manager system’s web interface or SNMP information.
To disable a list of IP addresses:
1 Go to Admin > Management and Security > Management Access Settings.
2 In the Whitelist screen, de-select the Management Access Settings check box.
3 Click Update to save your changes.
Set Sensitive Information Disclosure
You can choose not to display some detailed error messages and build number by configuring Information
Disclosure.
To configure the settings for information disclosure:
1 Go to Admin > Management and Security > Information Disclosure.
2 Check Generalize Error Message to hide detailed error information or uncheck Build Number
Display to hide build numbers on the GUI.
Reset System Passwords
You can configure random passwords for the RealPresence Resource Manager internal system processes
(Including database and other internal 3rd party software services, not including OS accounts and
RealPresence Resource Manager application users). Use these options only when you require maximum
security.
Polycom, Inc.
442
Securing the System
After resetting passwords, you need to re-integrate RealPresence Resource Manager and the
RealPresence DMA systems for network topology synchronization. You may need to re-setup Polycom
RealAccess data collection features.
To reset system passwords:
1 Go to Admin > Management and Security > Reset System Passwords.
2 Click the Reset System Passwords button.
3 Click OK.
Polycom, Inc.
443
Security Certificates
Certificates are used between systems within your video conferencing environment (such as servers and
endpoints) to build a trust/authentication and to support encryption. Certificates confirm that the servers
within your infrastructure can communicate and have the option to encrypt the data. Each digital certificate
is identified by its public key. The collection of all public keys used in an enterprise to determine trust is
known as a Public Key Infrastructure (PKI).
The CA, or certificate authority, is a single, centralized authority such as an enterprise’s IT department or a
commercial certificate authority that each computer on the network is configured to trust. Each server on
the network has a public certificate that identifies it. When a client connects to a server, the server shows
its signed public certificate to the client. The certificate authority signs the public certificates of those servers
that clients should trust. Trust is established because the certificate has been signed by the certificate
authority (CA), and the client has been configured to trust the CA.
This section describes the Polycom® RealPresence® Resource Manager system certificate management
tasks. It includes these topics:
● How Certificates are Used
● Accepted Certificates
● Certificate Signing Requests
● Installing Certificates
● Removing Certificates
● OCSP Settings
How Certificates are Used
Before installing any certificates or configuring an Online Certificate Status Protocol (OCSP) responder
settings, you must configure how the RealPresence Resource Manager system will use certificates. This is
done by configuring your TLS settings.
TLS settings also specify if client systems (endpoints and systems who access the RealPresence Resource
Manager system user interface) are required to present certificates for authentication. Determine the degree
in which you want to use certificates within your deployment and configure the settings appropriately.
See Configure TLS Settings.
Accepted Certificates
To support encrypted communications and establish a minimum level of trust, the RealPresence Resource
Manager system presents a self-signed digital certificate to its clients. This default certificate will typically
not be trusted by clients. Web browsers that connect to the RealPresence Resource Manager system user
interface will display a warning regarding the certificate.
Polycom, Inc.
444
Security Certificates
Participation in a Public Key Infrastructure requires a RealPresence Resource Manager system to have
been configured with at least one root CA certificate, and a digital certificate signed by that CA that identifies
the RealPresence Resource Manager system.
However, you will often need additional CA certificates to allow the system to properly validate a received
certificate. Work with your network administrator to gather all required certificates needed for use in the
environment. Here is a simple checklist:
● RealPresence Resource Manager Identify Certificate - created by the system via the Certificate
Signing Request (CSR) (see Certificate Signing Requests) and signed by a CA within your network
infrastructure.
● CA certificate for the CA that signs the RealPresence Resource Manager Identity Certificate
● A root CA certificate - this is the certificate for the root of the CA hierarchy.
● The CA certificates for all intermediate CAs between the root CA and the CA that signs the
RealPresence Resource Manager identity certificate.
● The certificate used to validate responses from the OCSP responder.
Certificates come in several forms (encoding and protocol). The following table shows the forms that can be
installed in the RealPresence Resource Manager system.
Encoding
PEM (Base64-encoded ASCII
text)
Polycom, Inc.
Standard/
FileType
Description and Installation Method
PKCS #7
standard
P7B file
Certificate chain containing:
• A signed certificate for the system.
• The CA’s public certificate.
• Sometimes intermediate CA certificates.
Upload file or paste into text box.
CER
(single
certificate)
PEM (Base64-encoded ASCII text)
Upload file or paste into text box.
Certificate
text (can
be
PKCS#7(
P7B) or a
single
certificate)
Encoded certificate text copied from CA’s email or secure web
page.
Paste into text box.
445
Security Certificates
Encoding
Standard/
FileType
DER
(binary format using ASN.1
Abstract Syntax Notation)
PKCS #12
standard
PFX file
Certificate chain containing:
• A signed certificate for the system.
• A private key for the system.
• The CA’s public certificate.
• Sometimes intermediate CA certificates.
Upload file.
Note
This format does not require a Certificate Signing Request to have
been generated by the RealPresence Resource Manager system.
PKCS #12 is not supported when the RealPresence Resource
Managersystem is in maximum security mode or when Strong
Ciphers (FIPS) mode is being used.
PKCS #7
standard
P7B file
Certificate chain containing:
• A signed certificate for the system.
• The CA’s public certificate.
• Sometimes intermediate certificates.
Upload file.
CER
(single
certificate)
file
Digital certificate that uniquely identifies the system within the PKI.
Upload file.
Note
The certificate must be issued by a CA using the most recent
Certificate Signing Request generated by the RealPresence
Resource Manager system.
Description and Installation Method
Certificate Signing Requests
The initial RealPresence Resource Manager system configuration permits using the default, self-signed
certificate.
Normal operation in a secure mode requires that you install a digital certificate signed by a trusted certificate
authority that uniquely identifies the RealPresence Resource Manager system within your public key
infrastructure. This can be done by creating a certificate signing request for the RealPresence Resource
Manager system and submitting it to a certificate authority to be signed.
Although it is common for a system to be identified by any number of digital certificates, each signed
by a different CA, the RealPresence Resource Manager system currently only supports a single
identity certificate.
This section includes the following topics:
● Requirements for Certificate Signing Request
● Create a Certificate Signing Request
Polycom, Inc.
446
Security Certificates
Requirements for Certificate Signing Request
When you choose to use security certificates with your video infrastructure environment, you need to
generate a CSR (Certificate Signing Request) for the Certificate Authority (CA) you are using.
Since the RealPresence Resource Manager system uses this single certificate for both TLS client and TLS
server connections, it is important that the certificate template used on the CA enable both "clientAuth" and
"serverAuth" use in the "Extended Key Usage" (EKU) field of the certificate. Related bits in the "Key Usage"
extension should be set accordingly per RFC 5280 guidance. Work with the administrator of the CA to
assure this.
When you create a certificate signing request (CSR) from RealPresence Resource Manager system, the
system not only populates the CSR with the data that you enter in the Certificate Information dialog, but it
also populates some of the CSR’s subject alternative name (SAN) fields. This information is not visible in
the Certificate Information dialog.
The RealPresence Resource Manager system generates a CSR containing all of the information shown in
the following table for your configuration. You cannot edit or remove any of the fields, including those listed
in the Optional fields column. If your CA cannot accept a CSR that includes all of this information, you must
generate the CSR and certificate manually using at least the data in the Required fields column for your
configuration. If you include the fields listed in the Optional fields column, users can access the system using
an abbreviated name without authentication errors.
Polycom, Inc.
447
Security Certificates
The RealPresence Resource Manager system only uses the DNS format for SAN values, even though
some values are IP addresses.
Required and Optional CSR SAN Fields
Configuration
Required Fields
Optional Fields
Single-server
system
•
•
•
•
•
•
•
SAN-DNS – FQDN
SAN-DNS – System IP address (Ipv4)
Country Name (two-letter code)
State or Province Name (full name)
Organizational Name(s) (one per line)
Email address
Key Size
•
•
Local Redundant
System
•
Common Name – Fully qualified domain name
(FQDN) of Virtual IP Address
SAN-DNS – FQDN of Virtual IP address
Country Name (two-letter code)
State or Province Name (full name)
Organizational Name(s) (one per line)
Email address
Key Size
SAN-DNS – Virtual host short name
•
•
•
•
•
•
Geo-Redundant
System
Server 1:
• Common Name – Fully qualified domain name
(FQDN) of server 1 IP
• SAN-DNS – FQDN of Virtual IP
• SAN-DNS – System IP address of server 1
• SAN-DNS – System IP address of server 2
• Country Name (two-letter code)
• State or Province Name (full name)
• Organizational Name(s) (one per line)
• Email address
• Key Size
SAN-DNS – Host short name
SAN-DNS – Ipv6 address, if used
SAN-DNS – Server 1 short name
SAN-DNS – Server 2 short name
Server 2:
• Common Name – Fully qualified domain name
(FQDN) of server 2 IP
• SAN-DNS – FQDN of Virtual IP
• SAN-DNS – System IP address of server 1
• SAN-DNS – System IP address of server 2
Country Name (two-letter code)
• State or Province Name (full name)
• Organizational Name(s) (one per line)
• Email address
• Key Size
Polycom, Inc.
448
Security Certificates
Create a Certificate Signing Request
This procedure describes how to create a certificate signing request (CSR) to submit to a certificate
authority.
You should create a certificate signing request after you have completed the network configuration of your
system.
To create a certificate signing request:
1 Go to Admin > Management and Security > Certificate Management.
The Certificate Management page displays the list of currently available certificates. By default, the
system will have one server certificate identified as the Resource Manager self-signed certificate and
one or more root certificates or certificate chains.
2 Click Create Certificate Signing Request.
If you see the warning “This action will overwrite any previously generated or uploaded private key.
Do you want to continue?,” do one of the following:
 If you are waiting for a previous request to be signed, click No. Because the RealPresence
Resource Manager system currently supports only one identity certificate, only the most recent
private key is retained. The digital certificate resulting from the most recent CSR is the only
certificate that will match the retained private key and is therefore the only identity certificate that
can be installed.
 If this is a new certificate signing request, click Yes to continue.
3 In the Certificate Request Data dialog, enter the identifying information for your RealPresence
Resource Managerr system and click OK.
Field
Description
Signature Algorithm
You can select either SHA256 or SHA1.
Country Name
Two-letter (ASCII only) ISO 3166 country code in which the server is located.
State and Province Name
Full state or province name (ASCII only) in which the server is located.
Locality Name
City name (ASCII only) in which the server is located.
Organization Name
Enterprise name (ASCII only) at which the server is located.
Organizational Unit Name
Optional: Subdivision (ASCII only) of the enterprise at which the server is located.
Multiple values are permitted, one per line.
Common Name
The FQDN (fully-qualified domain name) of the system (read-only), as defined in
the network settings.
E-mail Address
Email address (ASCII only) for a contact at the enterprise.
Subject Alternative Name
Your CA must support at least six SAN fields.
A File Download dialog appears.
4 In the File Download dialog, click Save.
5 In the Save As dialog, enter a unique name for the file, browse to the location to which to save the
file, and click Save.
Polycom, Inc.
449
Security Certificates
6 Submit the file (or text within the file) as required by your certificate authority.
When your certificate authority has processed your request, it sends you a signed digital certificate
for your RealPresence Resource Manager system. Some certificate authorities send only the signed
digital certificate while others send all of the certificates that form the chain of trust (including
intermediate and/or root CA certificates). These certificates may arrive as email text, email
attachments, or be available on a secure web page.
Installing Certificates
Install certificates after you have configured your network settings. If you update your network settings (for
example, if you change FQDN or change the network protocol IPv4 to IPv6), you must reconfigure
certificates for your system.
This section includes the following topics:
● Install a Certificate
● View Certificates and Certificate Details
Install a Certificate
Before installing a certificate or certificate chain provided by the certificate authority, be sure that you
received the certificate or certificate chain in one of the following forms:
● A PFX, P7B, or single certificate file that you’ve saved on your computer.
● PEM-format encoded text that you received in an e-mail or on a secure web page.
Installing or removing certificates requires a system restart. When you install a certificate, the change is
made to the certificate store immediately, but the system will not recognize or use the new certificate until it
restarts and reads the changed certificate store.
To install a signed certificate that identifies the RealPresence Resource Manager system:
1 Go to Admin > Management and Security > Certificate Management.
2 Click Install Certificates.
A warning appears stating that changes made to the certificates will require a system restart to take
effect.
3 In the Install Certificates dialog, do one of the following:
 If you have a PKCS#12, PFX, P7B, or single certificate file, click Upload Certificate, enter the
password (if any) for the file, and browse to the file or enter the path and file name.
PKCS #12 is not supported when the RealPresence Resource Manager system is in maximum
security mode or when Strong Ciphers (FIPS) mode is being used.
 If you have PEM-format text, copy the certificate text, click Paste Certificate, and paste it into the
text box at the bottom of the dialog. You can paste multiple PEM certificates one after the other.
4 Click OK.
If you are uploading a signed identity certificate for the first time, it will replace the RealPresence
Resource Manager system self-signed certificate.
5 Verify that the new signed certificate has replaced the default self-signed certificate:
Polycom, Inc.
450
Security Certificates
a In the list of certificates, select the RealPresence Resource Manager certificate and click View
Certificate Details.
b In the Certificate Details dialog, verify that the information in the Issued To sections matches
the FQDN of the RealPresence Resource Manager and the certificate from the certificate
authority and that the information in the Issued By section matches the expected name of the
certificate authority.
c Click Close to close the dialog.
Use the same procedure to install other certificates as needed (intermediate CA certificates, root CA
certificates, certificate used to validate OCSP responses). You need to have all CA certificates installed that
are part of the chain of trust for any client or server identity certificate that the system may be presented and
be required to validate on any of its external connections. Work with your network administrator to determine
this list.
View Certificates and Certificate Details
You can view currently installed certificates and certificate details, including expiration dates.
To view the list of installed certificates:
1 Go to Admin > Management and Security > Certificate Management.
2 The Certificate Management page displays the list of currently installed certificates. By default, the
system will display only one certificate. It will be identified as the RealPresence Resource Manager
self-signed certificate. When other certificates are installed, they will display along with the server
identity certificate.
The Certificate Management page has this information.
Field
Description
Status
The status of the certificate. Possible values include:
• Certificate is valid
• Certificate is invalid
Alias
The certificate name as assigned by the CA
Common Name
This is most often the fully qualified domain name of the server to which the
certificate has been issued. If the certificate identifies a client (trusted peer) it
might contain the name of a user or the name of an endpoint.
Purpose
The type of certificate. Possible values are:
• RealPresence Resource Manager self-signed—the system identity certificate.
• Trusted root certificate—the root certificate for a CA.
• Intermediate certificate—certificate from an intermediate CA.
• Trusted peer—certificate from any server or computer that is not a CA but
whose identity is trusted.
Expiration
The expiration date of the certificate.
Polycom, Inc.
451
Security Certificates
3 To view more information about a certificate, select the certificate and click View Certificate Details
from the More drop-down list.
The Certificate Details dialog appears with this information.
Section
Description
Certificate Info
Purpose and alias of the certificate.
Issued To
Information about the entity to which the certificate was issued and the certificate
serial number.
Issued By
Information about the issuer.
Validity
Issue and expiration dates.
Fingerprints
SHA1 and MD5 fingerprints (checksums) for confirming certificate.
Public key
The certificate’s public key, which in the public key infrastructure is
distributed widely, and is not kept secure.
4 Use the arrows to reveal or hide information. Click Close when you are done.
Removing Certificates
You can delete certificates from the system, but the RealPresence Resource Manager system prevents you
from deleting any certificate that breaks the identity certificate’s chain of trust. To delete these certificates,
you must first install new CA certificates and the identity certificate must be replaced.
There are two kinds of certificate removal:
● Removing the certificate of a Trusted Root CA so that the system no longer trusts certificates signed
by that certificate authority.
● Removing the signed certificate currently in use as the certificate so that the system reverts to using
the default self-signed certificate.
Removing a signed certificate also removes the certificate of the Trusted Root CA that signed it, along
with any intermediate certificates provided by that certificate authority.
Installing or removing certificates requires a system restart and terminates all active conferences. When you
install or remove a certificate, the change is made to the certificate store immediately, but the system can’t
implement the change until it restarts and reads the changed certificate store.
For your convenience, you’re not required to restart and apply a change immediately. This permits you to
perform multiple installs or removals before restarting and applying the changes. But when you’re finished
making changes, you must select Restart to Apply Saved Changes to restart the system and finish your
update. Before you begin, make sure there are no active conferences and you’re prepared to restart the
system when you’re finished.
This section includes the following topics:
● Remove a Trusted Root CA’s Certificate
● Remove a Signed Certificate and Revert to Default Self-Signed Certificate
● Regenerate a Default Self-Signed Certificate
● Revert to a Legacy VVX Certificate
Polycom, Inc.
452
Security Certificates
Remove a Trusted Root CA’s Certificate
You can remove a trusted root CA certificate so that the system no longer trusts certificates signed by that
certificate authority.
To remove a Trusted Root CA’s certificate:
1 Go to Admin > Management and Security > Certificate Management.
2 In the certificates list, select the certificate you want to delete.
3 Click Delete Certificate.
4 When asked to confirm, click OK.
A dialog informs you that the certificate has been deleted.
5 Click Restart to Apply Saved Changes, and when asked to confirm that you want to restart the
system so that certificate changes can take effect, click OK.
Remove a Signed Certificate and Revert to Default
Self-Signed Certificate
Removing the signed certificate currently in use as the certificate so that the system reverts to using the
default self-signed certificate.
Removing a signed certificate also removes the certificate of the Trusted Root CA that signed it, along with
any intermediate certificates provided by that certificate authority.
To remove a signed certificate and revert to the default self-signed certificate:
1 Go to Admin > Management and Security > Certificate Management.
2 In the certificates list, select the certificate to which you want to revert.
3 Select Revert to Legacy VVX Certificate from the More drop-down list.
4 When asked to confirm, click OK.
A dialog informs you that the system has reverted to a self-signed certificate.
5 Click Restart to Apply Saved Changes, and when asked to confirm that you want to restart the
system so that certificate changes can take effect, click OK.
6 After the system restarts, log back in, return to Management and Security > Certificates
Management, and verify that the system has reverted to the default self-signed certificate:
a In the list of certificates, select the default certificate.
b Click View Certificate Details from the More drop-down list.
The Certificate Details dialog appears.
c Confirm from the information under Issued To and Issued By that the default self-signed
certificate has replaced the CA-signed certificate.
d Click Close to close the dialog.
Polycom, Inc.
453
Security Certificates
Regenerate a Default Self-Signed Certificate
You need to update your certificate(s) whenever you make network configuration changes such as
changing the host name or IP of your RealPresence Resource Manager system.
After you generate a default certificate, you will need to restart your system.
To regenerate a self-signed certificate:
1 Go to Admin > Management and Security > Certificate Management.
2 Click Regenerate Resource Manager Certificate from the More drop-down list.
A new default certificate is generated.
3 Click Restart to Apply Saved Changes, and when asked to confirm that you want to restart the
system so that certificate changes can take effect, click OK.
4 After the system restarts, log back in, return to Management and Security > Certificates
Management, and verify that the system has reverted to the default self-signed certificate by
confirming the information under Issued To and Issued By that the default self-signed certificate
has replaced the CA-signed certificate.
Revert to a Legacy VVX Certificate
Some versions of the Polycom VVX rely on the self-signed certificate that comes installed with the
RealPresence Resource Manager system.
The legacy self-signed certificate is deleted automatically when you import a CA certificate chain. However,
if you need to revert to a self-signed certificate scenario for your systems, you will need to revert back to the
Legacy VVX Certificate.
The Legacy VVX certificate supports only 1024-bit key RSA.
To revert to the Legacy VVX certificate:
1 Go to Admin > Management and Security > Certificate Management.
2 Select Revert to Legacy VVX Certificate from the More drop-down list.
OCSP Settings
The RealPresence Resource Manager system supports using OCSP to verify the status of a certificate. This
is an alternative to manually uploading CRLs (Certificate Revocation Lists). If your network does not include
an OCSP responder, the RealPresence Resource Manager system parses individual certificates for a CRL
Distribution Point URL. There is no need to upload a CRL to complete your certificate validation.
When configuring the RealPresence Resource Manager system to use an OCSP responder, you can either
use the default OCSP information that is included in the certificates you receive or explicitly define the
OCSP responder location. You should only define an explicit OCSP responder location if your deployment
relies on a global OCSP responder.
After you configure OSCP settings, you will need to restart your system.
Polycom, Inc.
454
Security Certificates
To configure OSCP settings for your certificate(s):
1 Go to Admin > Management and Security > Certificate Management.
2 Select the Enable Online Certificate Status Protocol (OCSP) check box if your organization’s PKI
includes OCSP responders for revocation checking.
This check box is automatically enabled when your system is in maximum security mode.
3 Use the OCSP Certificate drop-down list to select one of the installed certificates to use to verify
OCSP responses. Which certificate to use depends on your OSCP server configuration. Consult
with your security administrator.
4 Depending on your security configuration, you can enter the URL of an OCSP Responder location to
use.
During first-time setup, it is recommended that you leave this field blank. This can ensure that you
don’t have connection problems during initial configuration.
a If OCSP is enabled and NO responder URL has been specified:
 If the certificate contains an OCSP URL it will be used to check revocation. The OCSP URL
is found in the certificate’s AIA field.
 If the certificate doesn't contain the OCSP URL then if the certificate contains a CDP it will be
used to check revocation.
 If the certificate doesn't contain a CDP revocation check fails and certificate isn't trusted.
b If OCSP is enabled and a global responder URL has been specified the global responder is used
to check revocation.
 If the global responder cannot be contacted then if the certificate contains a CDP it will be used
to check revocation.
 If the certificate doesn't contain a CDP revocation check fails and the certificate isn't trusted.
5 Click Verify OCSP Configuration.
The system verifies that the OSCP configuration is correct. If the OSCP URL as well as the OSCP
certificate, the configuration will also be verified as correct.
6 Click Save OCSP Configuration.
The system saves this configuration.
7 After making any changes, you must reboot the system.
Polycom, Inc.
455
Integrating with an Enterprise Directory
In a large organization, integrating your RealPresence Resource Manager system with Microsoft Active
Directory greatly simplifies the task of managing conference system security. Directory management
provides the following features.
● Single sign-on capability. Users get the benefits of pass-through authentication, allowing them to
leverage their Active Directory user name and password to login to the RealPresence Desktop
system, RealPresence Mobile or CMA Desktop system. This happens without the user having to
enter their credentials, creating seamless integration for logins.
● Single management environment. After the initial setup of the RealPresence Resource Manager
system, adding groups into RealPresence Resource Manager system is no more complex than
adding a group to a file share or database. Continue to manage your group memberships through
Active Directory, then grant those groups rights within the RealPresence Resource Manager system.
● Enables you to continue leveraging the existing role-based security model that you have in place,
though the RealPresence Resource Manager system only uses Universal groups.
This section describes the Polycom RealPresence RealPresence Resource Manager system enterprise
directory integration and operations. It includes these topics:
● Enterprise Directory Supported Configurations
● Using the Base DN to Manage Enterprise Directory Searches
● RealPresence Resource Manager System and Windows Authentication
● Managing Directories
● Endpoint Directory and Directory Settings
Enterprise Directory Supported Configurations
There are many possible configurations available within Microsoft Active Directory, some of which are not
fully supported by the RealPresence Resource Manager system. These topics describes the implications of
different Microsoft Active Directory configurations for integrating with the RealPresence Resource Manager
system.
This section includes information on the following topics:
● Single Forest Support
● Multiple Domains within a Single Forest
● Universal Group Support
● Read-only Enterprise Directory Users
● How Global Catalog Searches Work
Polycom, Inc.
456
Integrating with an Enterprise Directory
Single Forest Support
Microsoft Active Directory may be set up in either a single-forest or multi-forest configuration. However, the
RealPresence Resource Manager system requires that user accounts reside in a single forest.
Multiple Domains within a Single Forest
Microsoft Active Directory forests may contain one or more domains. In either configuration, the directory
must have a Global Catalog service. The RealPresence Resource Manager system can integrate to either
single or multiple domains, so long as they reside in the same forest structure.
Microsoft Active Directory domains are organized into trees, each tree being a group of domains which
share a consistent DNS namespace (e.g.: polycom.com and na.polycom.com would be in the same tree,
while polycom.com and resouceManagerDevelopment.net would be separate trees, if they were in the
same forest). The RealPresence Resource Manager system will integrate to all domains in a multi-tree
forest.
Viable options:
1 Integrate to all domains of a multi-domain forest configuration.
2 Restrict to a single domain tree in a multi-domain forest through the use of LDAP Search base DN
criteria.
Universal Group Support
Microsoft Active Directory provides three group scopes: Universal, Global, and Domain Local. Both Global
groups and Universal Groups are held on all Global Catalog servers in the forest. The RealPresence
Resource Manager system supports only the Universal groups.
Microsoft Active Directory provides two group types: Security and Distribution. The RealPresence Resource
Manager system supports either of these group types.
An Active Directory forest with a functional level of Windows 2000 Mixed mode only supports
Universal Distribution groups. Windows 2000 Native mode, Windows 2003 Mixed, and Windows 2003
forest functional levels support Universal Security and Distribution groups.
In addition to leveraging Active Directory Universal groups, the RealPresence Resource Manager system
also has Local groups, which you can use to grant a standard set of rights to multiple users or groups. These
RealPresence Resource Manager system Local groups can have as members, RealPresence Resource
Manager system Local users, Active Directory users or Active Directory Universal groups. In this fashion,
you can nest a variety of users and groups into a RealPresence Resource Manager system Local group
and assign those users rights through their RealPresence Resource Manager system Local group
membership, simplifying management of rights on the RealPresence Resource Manager system.
Read-only Enterprise Directory Users
The RealPresence Resource Manager system supports both local and enterprise user accounts. Local user
accounts exist entirely on the RealPresence Resource Manager system. They can be created and managed
whether or not the system is integrated to an enterprise directory. Enterprise user accounts exist in your
Polycom, Inc.
457
Integrating with an Enterprise Directory
enterprise Active Directory. The RealPresence Resource Manager system cannot create or manage Active
Directory accounts, except to modify their privileges on the RealPresence Resource Manager system itself.
If simultaneously using local and enterprise accounts, it is important to avoid duplication of account data.
For example, if your Active Directory has a user named John Doe with a username of jdoe, a local account
for this user must possess a unique name, such as localjdoe or johndoetest. If duplicate user accounts exist
in the same domain or across domains, the user associated with these accounts will not be able to log into
a dynamically managed endpoint.
The RealPresence Resource Manager system accesses the enterprise directory in a read-only mode. It
does not create, modify, or delete Active Directory users or groups in any way.
Once you integrate with an enterprise directory, it is best to minimize your dependency on local users. A
single local administrative user account must exist, and it should be used only when there is a problem
connecting to the enterprise directory.
This configuration provides flexibility and varying security levels as follows:
● Restricted access: For security reasons, local user accounts do not have access to any data in Active
Directory, though they can see the Active Directory users and groups as defined in the RealPresence
Resource Manager system's security.
● Administration: Active Directory users and their Active Directory group memberships are managed
through your Active Directory. RealPresence Resource Manager system local users are managed
through the RealPresence Resource Manager system's web interface.
● Security: Local accounts have their own passwords, which are stored on the RealPresence Resource
Manager system. Active Directory user accounts maintain the same users' Active Directory
credentials and password complexity policies, which are validated by the domain controllers.
How Global Catalog Searches Work
When you integrate the RealPresence Resource Manager system with Active Directory, you can configure
it to integrate in one of two ways:
● It can access a specific global catalog server by host name or IP address (not recommended, due to
a lack of redundancy).
If you select this option, the domain name that you specify for the RealPresence Resource Manager
system must match the DNS name suffix of the Global Catalog server (example: dc1.polycom.com
configured as the Global Catalog, then you must enter polycom.com as the domain name of the
RealPresence Resource Manager system server).
● It can auto-discover the server by querying the DNS for the closest Global Catalog server (strongly
recommended).
If you select this option, you can specify any domain in the Active Directory forest in the Domain
Name criteria for the RealPresence Resource Manager system server. The DNS server must contain
Active Directory-specific entries.
It is recommended that you enter the forest root DNS domain name.
When configured to auto-discover the server, every time the RealPresence Resource Manager system
needs to bind to a Global Catalog server for LDAP queries, the RealPresence Resource Manager system
performs the following.
● Uses Microsoft's LDAP Ping mechanism to determine the site in which the system is located.
● Uses a DNS SRV record query to find a Global Catalog server within the same site.
Polycom, Inc.
458
Integrating with an Enterprise Directory
● Connects to the Global Catalog on the domain controller and queries for the object in question and
any relevant information (such as GUID, userID, name, phone number).
You can secure the connection between the RealPresence Resource Manager system and the Active
Directory server's Global Catalog using LDAP-S (via outbound TCP/UDP port 3269) or Start TLS (via
outbound 3268 TCP/UDP). To implement the secure connection, the appropriate ports must be open on any
network equipment between the Global Catalog and the RealPresence Resource Manager system.
Using the Base DN to Manage Enterprise Directory
Searches
When the RealPresence Resource Manager system is integrated with an enterprise directory, the system
uses the base DN to determine domains and manage directory searches. The Base DN is the starting point
in the Active Directory hierarchy at which your search will begin.
The Base DN field is where you specify the distinguished name (DN) of a subset of the Active Directory
hierarchy (a domain, subset of domains, or organizational unit) to which you want to restrict the
RealPresence Resource Manager system search. It acts like a filter.
By default, the Base DN field is empty. The first time you tell the system to connect to the enterprise
directory server, leave the Base DN field empty. Once you have established a working connection with your
Active Directory, then you enter a Base DN.
For complete documentation on using Base DNs, see the documentation for Microsoft Active Directory.
This section includes examples of Base DN filters.
● Examples of Base DN Filter Expressions
● Examples of Base DN Exclusion Filters
● Examples of Advanced Base DN Exclusion Filters
Examples of Base DN Filter Expressions
The following table illustrates some basic examples of Base DN filter expressions.
Search base DN expression
Description
ou=ResourceManagerGroups,dc=example,dc=com
Include only groups and users which reside within the
ResourceManagerGroups OU in the example.com
domain
dc=example,dc=com
Include only groups and users which reside within the
example.com domain or domain tree.
Expressions in the Base DN and exclusion filter fields must be formatted according to RFC-4514, section
2.4.
Some special characters are allowed in the Base DN field. They include:
Polycom, Inc.
459
Integrating with an Enterprise Directory
Character
Character Name
“%”
Percent
“ ”
Space
“"”
Double quote
“?”
Question mark
“{”
Open brace
“}”
Close brace
“^”
Caret
“~”
Tilde
“[”
Open bracket
“]”
Close bracket
“‘”
Single quote
“&”
Ampersand
“|”
Pipe or bar
The special characters that are not allowed in the Base DN field without the special escape character
(backslash, \) are:
Character
Character Name
“\”
Backslash
“=”
Equal
“,”
Comma
“#”
Pound
“+”
Plus
“;”
Semicolon
“<”
Less than
“>”
Greater than
Therefore, to use these character as part of a name, they must be preceded in the Base DN field by a
backslash. For example, the base DN of an ou named "tom,ann,bob" in the "myteam.example.com"
domain must be entered as:
ou=tom\,ann\,bob\ dc=my team,dc=example,dc=com
Or the base DN of an ou named "#+,=<>\ " in the "mydomain.example.com" domain must be entered as
ou=\#\+\,\=\<\>\\\ ,dc=mydomain,dc=example,dc=com
Polycom, Inc.
460
Integrating with an Enterprise Directory
Note that this applies only to attribute values, not the ou= or dc= structure.
Examples of Base DN Exclusion Filters
Using LDAP exclusion filters, you can exclude objects in your directory based on a wide variety of criteria
within your Active Directory environment. Any LDAP filters that you create must follow the LDAP standard
and reference the LDAP display name of the attributes against which you are filtering.
The following table illustrates some basic examples of exclusion filter expressions.
Search base DN expression
Description
Memberof=cn=Restricted Group,OU=users,dc=example,dc=com
Excludes all users who are members of
“Restricted Group” within the Users OU in the
example.com domain.
!(Memberof=cn=Video Users,OU=Users,dc=example,dc=com)
Includes only groups and users within the
Video Users group in the Users OU in the
example.com domain.
Creating exclusion filters can impact the performance of your LDAP queries. As a best practice, use indexed
attributes and do not use medial searches when implementing exclusion filters. For more information, see
Creating More Efficient Microsoft Active Directory-Enabled Applications.
Examples of Advanced Base DN Exclusion Filters
The following table illustrates some more advanced examples of exclusion filter expressions.
Search base DN expression
Description
!(| (memberof=CN=Sales,DC=europe,DC=example,DC=com)
(memberof=CN=IT,DC=europe,DC=example,DC=com))
Includes only users that are members of the
‘Sales’ or ‘IT’ Groups in the domain
europe.example.com.
Notes:
• The expression should be in continuous line
with no carriage returns or extra spaces (not
possible in this document’s format).
• By excluding an entity, we implicitly mean to
include all other entities. Conversely, by
including an entity, we are implicitly
excluding all other entities. Hence, this
exclusion filter will suffice for a case where,
for example, the administrator wants to
include Sales and IT but exclude Human
Resources, Engineering, etc., within the
specified domain.
&(objectCategory=person)(objectClass=user)(userAccountContr
ol:1.2.840.113556.1.4.803:=2)
Polycom, Inc.
Excludes all users who are disabled. Note this
is using a different but valid notation.
461
Integrating with an Enterprise Directory
RealPresence Resource Manager System and
Windows Authentication
When the RealPresence Resource Manager system must be integrated with an Active Directory server and
trusted by Active Directory, users with dynamically managed endpoints can securely log into their endpoint
without typing in their network credentials
When the RealPresence Resource Manager system starts up, it performs the following actions.
● Uses Microsoft's LDAP ping mechanism to determine the site in which the system is located.
● Uses a DNS SRV record query to find a domain controller within the same site.
When an Active Directory user attempts to log into the RealPresence Resource Manager system, it
authenticates the user by connecting to the domain controller that it is connected to and passes the user's
credentials using NTLMv2. The credentials are seamlessly passed to the RealPresence Resource Manager
system utilizing a secure channel connection from the user's workstation, using the credentials with which
they logged into the workstation.
Because the RealPresence Resource Manager system uses NTLMv2, the password is not stored
within and the RealPresence Resource Manager system never receives the user's password.
Some important notes about the RealPresence Resource Manager system Active Directory integration:
● The RealPresence Resource Manager system is not joined to the domain. Other computers on the
network cannot browse its file system and it cannot be managed remotely by existing IT mechanisms
such as SMS.
● The RealPresence Resource Manager system does not modify the Active Directory in any way.
● The RealPresence Resource Manager system can auto-discover the closest logical domain
controller and Active Directory servers, but to do this the network DNS server must have a DNS SRV
record for these servers. Once the domain controller’s hostname and IP address have a record on
the DNS, the RealPresence Resource Manager system can auto-discover the IP address of the
domain controller. If your Active Directory does not publish the domain controller’s hostname and IP
address to the network DNS, you must edit the file to include it.
● The RealPresence Resource Manager system requires that you enable Digitally sign
communications on the Active Directory server.
Managing Directories
This section describe the enterprise directory management operations. It includes these topics:
● Integrating with Enterprise Directory Server
● Allow Delegated Authentication to Enterprise Directory Server
● Give Enterprise Users Default Scheduler Role
● Change the Message for Enterprise Users without a Role
Polycom, Inc.
462
Integrating with an Enterprise Directory
Integrating with Enterprise Directory Server
The process of integrating with an enterprise directory server, involves these steps:
● Create the RealPresence Resource Manager System Service Account
● Create the RealPresence Resource Manager System Computer Account
● Enable Integration with the Enterprise Directory Server
Enabling the Integrate with Enterprise Directory Server option enables RealPresence Resource
Manager system users who are included in the Active Directory to log into the RealPresence Resource
Manager system interface using their network credentials.
Enabling the Integrate with Enterprise Directory Server option also enables endpoint users to select
conference participants and rooms from the enterprise directory. Because endpoint connections to LDAP
use the endpoint user’s credentials, the Active Directory access control lists identify which endpoint users
and rooms each user can see.
The RealPresence Resource Manager system supports only the Microsoft Active Directory for its
enterprise directory.
In addition, administrative users can:
● View some enterprise user and group information
● Import enterprise groups into the RealPresence Resource Manager system
● Assign roles to users in different enterprise groups
● Identify enterprise resources, such as rooms, so that they can be treated as resources in the
RealPresence Resource Manager system
To allow endpoint users to use NTLM Single Sign On technology to connect to the RealPresence
Resource Manager system, see Allow Delegated Authentication to Enterprise Directory Server.
For more information about Active Directory and LDAP, see MS Strategy for Lightweight Directory Access
Protocol (LDAP).
Create the RealPresence Resource Manager System Service
Account
Before integrating the RealPresence Resource Manager system with an Active Directory forest, you must
create a service account for it in Active Directory. This service account is a read-only user account that the
RealPresence Resource Manager system uses to perform LDAP queries against your Active Directory
Global Catalog.
You need to create a service account in Active Directory for the RealPresence Resource Manager system
to use.
Polycom, Inc.
463
Integrating with an Enterprise Directory
To create the RealPresence Resource Manager system service account:
1 On the Active Directory server, open the Active Directory Users and Computers module (Start >
Programs > Administrative Tools > Active Directory Users and Computers).
2 Click the node for your domain and then right-click the OU folder in which you want to add a user
account and select New > User.
3 At a minimum, in the First name, Full name, and User logon name fields, type
resoucemanagerservice or an appropriate name for your environment and click Next.
4 In the Password and Confirm Password fields, type a password for the service account to use
during initial integration. This is the password you must enter on the RealPresence Resource
Manager system Enterprise Server page.
5 Select the Password never expires option, unselect the User cannot change password option,
click Next and then Finish.
You can reset the password for this account manually, but to do so you must change it in Active
Directory first and then update the RealPresence Resource Manager system LDAP Server page. The
service account requires the rights to read all properties on all users and groups that will be used in
the RealPresence Resource Manager system. Without these permissions, it may not function
properly.
Create the RealPresence Resource Manager System
Computer Account
The RealPresence Resource Manager system requires a computer account to enable secure channel
communications with the Active Directory forest that is being leveraged for authentication. This account
must be pre-created and the password set by an administrator from a Domain Controller.
When setting up a redundant RealPresence Resource Manager system, the redundant servers use
the same computer account to create their secure channel connection. The computer account name
does not have to match the host name of your RealPresence Resource Manager system server.
You need to create a computer account in Active Directory for the RealPresence Resource Manager
system.
To create the RealPresence Resource Manager System computer account:
1 On the Microsoft Active Directory system, open the Active Directory Users and Computers
module (Start > Programs > Administrative Tools > Active Directory Users and Computers.
2 Select the node for your domain, right-click the OU folder in which to add the computer account and
then select New > Computer.
3 In the Computer name field, type PolycomResourceManager or an appropriate name for your
environment and then click Next and Finish (or simply click OK depending on your version of Active
Directory).
4 Ensure that the Active Directory Users and Computers console will show all available computer
options necessary for the remaining steps by enabling View > Advanced Features.
5 Right-click the computer account, select Properties, and then select the Security tab.
6 In the Group or user names section of the Security tab, select the SELF object.
Polycom, Inc.
464
Integrating with an Enterprise Directory
7 In the Permissions for SELF section, select Change password, and then click OK.
8 Login to the domain controller where the computer account was created and set the password using
the following command:
net user <computername>$ <password>
For example: net user polycomrm$ p@ssw0rd
Performing the net user command on any machine other than a domain controller will not assign the
computer account password for the RealPresence Resource Manager system computer account. At
initial integration, the RealPresence Resource Manager system will change its Computer Account
password to a random 120 character string including special characters. This password will also be
changed, to a new randomly generated password, every time the RealPresence Resource Manager
system is rebooted, or every week if no reboots are performed. Because this is a Computer account,
resetting the password to a known value requires use of net user commands on an Active Directory
Domain Controller.
Enable Integration with the Enterprise Directory Server
Enabling the Integrate with Enterprise Directory Server option enables RealPresence Resource
Manager system users who are included in the Active Directory to log into the RealPresence Resource
Manager system interface using their network credentials.
Enabling the Integrate with Enterprise Directory Server option also enables endpoint users to select
conference participants and rooms from the enterprise directory. Because endpoint connections to LDAP
use the endpoint user’s credentials, the Active Directory access control lists identify which endpoint users
and rooms each user can see.
To integrate the RealPresence Resource Manager system to an enterprise directory server:
1 Go to Admin > Directories > Enterprise Directory.
2 On the Enterprise Directory page, select Integrate with Enterprise Directory Server.
3 To have the system auto-discover the server by querying DNS, enable Auto-discover in the
Enterprise Directory Server DNS Name section; otherwise, enter the DNS Name for the
enterprise directory server.
4 As needed, configure these settings.
Setting
Description
Domain\Enterprise Directory User
ID
Domain and Enterprise Directory User ID for an account that the
RealPresence Resource Manager system can use to access the enterprise
directory server and retrieve group, user, and room information. This is the
account created Create the RealPresence Resource Manager System
Service Account.
This User ID must have read permissions so it can search the entire forest on
the enterprise directory server.
This User ID is automatically associated with the RealPresence Resource
Manager system administrator role - by default it is the ONLY enterprise
directory User ID with this role.
Enterprise Directory User
Password
The password for the enterprise directory user account
Polycom, Inc.
465
Integrating with an Enterprise Directory
Setting
Description
Security Level
The level of security on the connection between the RealPresence Resource
Manager system and the enterprise directory server. Possible values include:
• Plain—No security on the connection
• LDAPS—The connection is secured over outbound port 3269 using
LDAPS in a manner similar to https.
If the “Domain Controller: LDAP Server signing requirements” setting
on the Active Directory server is set to “Require Signing”, then you
must use LDAPS to secure the connection.
• StartTLS—The connection is secured over outbound port 3268 (the same
port as Plain), but it then negotiates security once the socket is opened.
Some LDAP servers reject any unsecured transactions, so the first
command is the StartTLS negotiation command.
Use LDAP Filter
Specifies which user accounts to include (an underlying, non-editable filter
excludes all non-user objects in the directory). The default expression
includes all users that don’t have a status of disabled in the directory.
Enterprise Directory Search Base
DN
If necessary and you understand the filter syntax, specify the top level of the
enterprise directory tree (referred to as the base DN) to search. Don’t edit
these expressions unless you understand the filter syntax.
For more information, see Using the Base DN to Manage Enterprise Directory
Searches.
5 If you also wish to implement single sign-on, see the following section Allow Delegated
Authentication to Enterprise Directory Server. Otherwise, click Update.
Allow Delegated Authentication to Enterprise Directory
Server
The RealPresence Resource Manager system Use Single Sign on (Integrated Windows Authentication)
option, enables endpoint users who are included in the enterprise directory to securely log into their
dynamically managed endpoint without typing in credentials.
To allow RealPresence Resource Manager system users who enter their network usernames and
passwords to log into the RealPresence Resource Manager system and select conference
participants from your company’s active directory, see Integrating with Enterprise Directory Server.
To delegate authentication to the enterprise directory server:
1 Go to Admin > Directories > Enterprise Directory.
2 On the Enterprise Directory page, select Allow delegated authentication to enterprise
directory server.
3 To have the system auto-discover the closest logical domain controller and enterprise directory
servers, in the Domain controller name section enable Auto-discover; otherwise, enter the fully
qualified hostname of the domain controller (for example, dc1.mydomain.com).
Polycom, Inc.
466
Integrating with an Enterprise Directory
To auto discover the domain controller and enterprise directory server, the network DNS server must
have a DNS SRV record for these servers.
4 Enter the Username (domain\<computer name>) and Password and click Update.
Give Enterprise Users Default Scheduler Role
By default when local users are added to the RealPresence Resource Manager system, they are assigned
the Scheduler role. By default, when you integrate a RealPresence Resource Manager system to an Active
Directory, enterprise users are not assigned a role. In this case, you must either assign each enterprise user
a role, or you can use this procedure to give enterprise users the Scheduler role by default.
To give enterprise users default Scheduler role:
1 Go to Admin > Directories > Enterprise Directory.
2 Select the Associate Enterprise users with basic scheduler role by default check box.
3 Click Update.
Change the Message for Enterprise Users without a
Role
You can customize the message enterprise users see when they attempt to log in but do not have a user
role assigned.
To change the message enterprise users without a role see when they try to log in:
1 Go to Admin > Directories > Enterprise Directory.
2 Edit the Message to be displayed to unauthorized users.
For example, enter a message such as “Your username and password are valid, but you have no
permissions on this system. Contact your IT department for more information.”
3 Click Update.
Endpoint Directory and Directory Settings
When an endpoint registers with the RealPresence Resource Manager system, its information is
automatically entered into the Global Address Book. When information changes at the endpoint, the Global
Address Book is automatically updated as well. If an endpoint is configured to Allow Directory Changes,
additions and deletions to the Global Address Book are pushed to the endpoint.
Endpoints that get their global directory from the RealPresence Resource Manager system will either get
the Global Address Book or the enterprise LDAP directory. You can use the Directory Setup options to
affect which devices and users appear in the endpoint directory.
Polycom, Inc.
467
Integrating with an Enterprise Directory
Typically, endpoints that do not use the RealPresence Resource Manager as register for the Polycom GDS
and are listed in the RealPresence Resource Manager system Global Address Book. The Global Address
Book enables standard endpoint users to call other standard endpoint users by selecting them by name. In
this case, the Global Address Book is limited to 2000 entries, which is the limit that standard endpoint
systems can manage.
Global Address Book Tips
● The RealPresence Resource Manager system Global Address Book lists endpoints. Endpoints may
or may not have users or rooms associated with them. On an endpoint, the Global Address Book
does not list users unless they have endpoints associated with them.
● If your company has more than 100 endpoints, don’t limit the Global Address Book on the endpoint
side or the endpoint user won’t have access to all Global Address Book entries.
● The RealPresence Resource Manager system Global Address Book does not support unicode data.
● Non-dynamically managed endpoints are listed in the Global Address book regardless of if they are
associated with an owner.
● For Desktop 3.2 endpoints, the device model is also shown in the directory listing.
Removing or Include Dynamically Managed Endpoints
in the Global Address Book
By default the RealPresence Resource Manager system includes all dynamically managed endpoints in the
Global Address Book.
The Include dynamically managed devices in the Global Address Book option changes the Global
Address Book so that it also includes all dynamically managed endpoints. In this case, the Global Address
Book limit is increased to 5000 entries. (Dynamically managed endpoints are always included in the
enterprise LDAP directory.)
Remove Enterprise Users
You can remove enterprise users from the RealPresence Resource Manager system Global Address Book.
To remove enterprise users from the RealPresence Resource Manager system Global
Address Book:
1 Go to Admin > Directories > Directory Setup.
2 In the Directory page, clear Include dynamically managed devices in the Global Address
Book.
3 Click Update.
Include Enterprise Users
You can include enterprise users in the RealPresence Resource Manager system Global Address Book.
Polycom, Inc.
468
Integrating with an Enterprise Directory
To include enterprise users in the RealPresence Resource Manager system Global
Address Book:
1 Go to Admin > Directories > Directory Setup.
2 In the Directory page, select Include dynamically managed devices in the Global Address
Book.
3 Click Update.
Remove or Include Guest Book Entries in the Directory
By default the RealPresence Resource Manager system includes Guest Book entries in the endpoint
directory, regardless of whether the endpoint directory is the Global Address Book or the enterprise
directory. The Show Guest Book entries in the Directory option is also selected by default.
Remove Guest Book
You can remove Guest Book entries from the endpoint directory.
To remove Guest Book entries from the endpoint directory:
1 Go to Admin > Directories > Directory Setup.
2 In the Directory Setup page, clear Show Guest Book entries in the Directory.
3 Click Update.
Include Guest Book
You can include Guest Book entries in the endpoint directory.
To include Guest Book entries in the endpoint directory:
1 Go to Admin > Directories > Directory Setup.
2 In the Directory Setup page, select Show Guest Book entries in the Directory.
3 Click Update.
Allow Local Users to View Enterprise Directory Entries
You can allow local users to access Enterprise Directory entries when the RealPresence Resource
Manager is integrated with an enterprise directory.
To allow local users to view Enterprise Directory Entries:
1 Go to Admin > Directories > Directory Setup.
2 In the Directory Setup page, select the Allow endpoint directories for local users to include
enterprise directory user information check box.
3 Click Update.
Polycom, Inc.
469
Integrating with an Enterprise Directory
Supporting LifeSize Endpoints in Directories
You can include LifeSize endpoints in the endpoint directory by configuring your directory setup. When you
do this, you also need to ensure that your LifeSize endpoint is configured to use the correct LDAP settings.
Complete the following steps:
● Modify Directory Listings
● Configure LDAP Settings
For more information about LifeSize endpoints, see Considerations for LifeSize Endpoints.
Modify Directory Listings
You need to allow your directory listings to include support for LifeSize endpoints.
To modify directory listings for LifeSize endpoint support:
1 Go to Admin > Directories > Directory Setup.
2 In the Directory Setup page, select the Modify directory listings for LifeSize endpoint support
check box.
3 Click Update.
Configure LDAP Settings
In addition to configuring directory listing support in the directory set up, you need to also ensure that the
LifeSize endpoint is configured to use the RealPresence Resource Manager system’s LDAP settings. You
can provision these through a scheduled provisioning profile or configure them manually on the endpoint.
To add LDAP settings to a scheduled provisioning profile:
1 Go to Admin > Scheduled Management > Provisioning Profiles.
2 Click
.
3 In the Add Profile dialog, select LifeSize in the Endpoint Type drop-down list, enter a name for the
profile, and click OK.
4 As needed, complete the various settings that you would like to provision for your LifeSize endpoint.
For more information about these fields, see Endpoint Fields for Scheduled Provisioning Profiles.
5 For Directory support, select the Directory > LDAP.
6 On the Directory > LDAP page:
a Select the Provision This Page check box.
b In the LDAP field, select Enabled from the drop-down list.
 In the LDAP Username field, enter uid=ldapgab,ou=system
 In the LDAP Password field, enter the password for the Polycom Global Address Book if you
have one. If not, leave this field blank.
 In the LDAP Base field, enter DC=Polycom,dc=com.
7 Click OK.
Polycom, Inc.
470
Integrating with an Enterprise Directory
If you manually enter the LDAP settings on the LifeSize endpoint, the value for the LDAP Base field
needs to be the following: OU=Endpoints,DC=Polycom,dc=com.
Allow Mid-String Searches for Local Users
By default, you can only search for local users by the initial letter(s) or number(s) of the user ID. If you enable
mid-string searches for local users, you can search by any character in the user ID.
For example, if you type “oo”, you’ll see the following results:
TeslaRoom
TurinRoom
EinsteinRoom
To allow for mid-string searches for local users:
1 Go to Admin > Directories > Directory Setup.
2 Select the Allow mid-string search for local user/room/guest and legacy endpoint check box.
3 Click Update.
Polycom, Inc.
471
Configuring Multi-Tenancy
The Polycom® RealPresence® Resource Manager system supports multi-tenancy with its areas feature.
Multi-tenancy enables you to use the system to service multiple customers, internal or external. Each area
serves a system tenant by partitioning off a collection of resources including users, associated endpoints,
network devices, etc.
Administration and conferencing duties for areas can then be delegated to users within that area or by a set
of super users who are allowed to view and manage all areas. You can set up flexible scenarios by having
an area scheduler or area operator for each respective tenant or area. Otherwise, you can limit area
administration tasks to users specifically allowed to manage that area.
For example, in an enterprise deployment, the RealPresence Resource Manager system administrator can
divide up users and resources according to department and then delegate video conferencing duties to
users within that area. This allows the system administration duties to remain with a specialized video IT
department, while video conference scheduling can be delegated to users within specific areas. Areas also
allow the administrator to run area-specific reports on how specific departments within the enterprise are
utilizing video conferencing.
The Areas feature of the RealPresence Resource Manager system is a licensed feature. Contact your
sales representative for more details.
Planning For Multi-Tenancy
You should plan your multi-tenancy environment so that you can ensure scalability and efficient use of
resources. Setting up the RealPresence Resource Manager system for multi-tenancy should use the
following best practices:
● RealPresence Resource Manager system does not support integration with more than one Active
Directory or multi-forest Active Directory integrations. If you need to support users that reside in
different Active Directories or different Active Directory forests, you cannot use the Resource
Manager system’s integration with Active Directory feature. You will need to use only local
RealPresence Resource Manager system users. To save time, you can import users into your
RealPresence Resource Manager system.
● Software updates cannot be assigned to an area.
● You must use dynamic provisioning when areas are enabled. Other methods of endpoint provisioning
are not supported. See Admin Config Provisioning Profiles
● RealPresence DMA systems, Polycom VBP systems, RealPresence Access Director systems, and
SBCs (Acme Packet Net-Net Enterprise Session Director) are not area-aware, which means they
cannot be assigned to an area.
● Resources can belong to only one area, with the exception of RealPresence DMA Pool Orders. If you
want to share network devices between areas, you can leave them in no area.
Polycom, Inc.
472
Configuring Multi-Tenancy
● You can assign an area user an area role according to the tasks the user needs to perform in the
RealPresence Resource Manager system. Area roles restrict user tasks to the area or areas in which
they are allowed to manage.
● Some system-wide administration tasks cannot be delegated to users with only area-specific roles.
These include site topology and conference templates. System maintenance and set up must also
be done by a user with a system role.
Working within a Multi-Tenancy Environment
When using the RealPresence Resource Manager system’s area feature, most aspects of the system
become “area-aware” which means that management of the system and conferencing tasks may become
different according to the role of the user.
The following aspects of the area feature are discussed in this topic:
● User Roles within a Multi-Tenancy Environment
● Area Address Books
● Area User Groups
● Area Users, Rooms, and Associated Endpoints
● Area Conference Guests
● Using the Common Pool in a Multi-Tenancy Environment
● Area Conference Templates
User Roles within a Multi-Tenancy Environment
When you have enabled areas for your RealPresence Resource Manager system, you have access to
additional user roles to help you delegate responsibilities to users within specific areas.
System Roles
System roles are used for users who are required to perform RealPresence Resource Manager tasks for all
areas. RealPresence Resource Manager users that have a system role will be able to view and modify
resources from all areas because their role includes the View and/or Modify All Areas permission.
System roles include: Administrator, Advanced Scheduler, Auditor, Device Administrator, Operator,
Scheduler, and View-Only Scheduler.
For detailed information about system roles, see Working with Management Roles and Permissions.
Area Roles
An area role delegates RealPresence Resource Manager responsibilities to a user that needs to manage
the resources in one or more areas, but not all areas. A user must be assigned a RealPresence Resource
Manager area role in order to perform his role-related tasks. In addition to being assigned a role, you must
enable that user to manage the area(s) in which he needs to perform his responsibilities.
You can also allow a user to manage areas to which he does not belong. For example, you can allow an
area scheduler to schedule users from two areas into conferences. For this, you would need to configure
this user to manage both areas.
Polycom, Inc.
473
Configuring Multi-Tenancy
Area roles include: area administrator, area operator, and area scheduler.
Role
Permissions
Area Scheduler
Schedule Conferences
Scheduling Level = Basic
Area Operator
Conference operator
Reports
Troubleshooting
Schedule conferences, both basic and advanced.
Schedule-able resource monitor. The area operator can monitor MCUs and RealPresence
DMA Pool orders that are in the areas he manages or in the common pool (no area).
Area Administrator
Add endpoints
Manage users and groups
Monitor conferences
Monitor network devices
View-only scheduler
Directory setup
Can provision devices using existing profiles (cannot create provisioning profiles)
Can update software on devices using existing software updates (cannot create software
updates)
Can add and edit users, groups, rooms, and other resources
Can view Reports for the area(s) they manage. No system-wide reports will be available.
Can monitor the system via the Admin Dashboard. System-wide pods will not be
available. Each sub-pod will have its source information filtered by area.
Area Conference Participants
Although conferences are area-specific, an area scheduler can add users from any area that he manages.
For example, if a area scheduler for the blue area was also granted permission to manage the yellow area,
he can add conference participants from both the blue and yellow areas.
A system scheduler is able to schedule conferences in all areas and invite users from all areas.
Note that if a conference has participants, rooms, and/or guests from multiple areas, then RealPresence
Resource Manager users will be able to see the area names of only the areas that they belong to or can
manage. Participants, rooms and guests that belong to other areas are presented as a “Guest of” the
conference’s area.
Area Address Books
An address book must belong to only one area or to no area, but can contain users, endpoints, rooms and
guests from multiple areas.
An address book is accessible to only users who are also assigned to the area that the address book
belongs to. That is, if a user has a system role, they will see all address books, but if a user has only an area
roles, they will see only address books that belong to the areas that they belong to or to areas in which they
manage.
Polycom, Inc.
474
Configuring Multi-Tenancy
When a user views the contents of an address book that has members from multiple areas, they will be able
to view only those members that belong to areas the user has access to. That is, if a user has a
non-area-specific role, they will be able to see address book members from all areas, but if a user has only
area-specific roles, they will see only members that belong to the areas they manage.
From an endpoint, an address book is accessible only if the logged in user and address book belong to the
same area or if the logged in user manages the area the address book belongs to. When an endpoint user
views the contents of a cross-area address book, the address book members they can see include:
● Members that belong to the same area as the user who is logged in to the endpoint
● Members that belong to other areas that the logged in user manages
Also note that changing the area that an address book is assigned to does not affect the areas of its
members.
Area User Groups
User groups can be assigned to one area or no area. Although it can contain users from multiple areas.
Users with the system role of administrator or the role of area administrator are allowed to create and edit
user groups. If the area administrator manages more than one area, he can add users from any area that
he manages to the user group. Remember that system administrators are automatically have permission to
view/manage all areas, and can therefore add any user to a user group.
However, even if a group has users from multiple areas, area administrators can only view users within the
group that belong to the areas they manage.
Changing the area of the group does not affect the area of the users in the group.
Area Users, Rooms, and Associated Endpoints
Endpoints and rooms follow strict rules of staying in the same area of the user they are associated with. The
RealPresence Resource Manager system ensures that a user and their associated endpoint(s) belong to
the same area. If one moves to another area or no area, the others move with it. The same is true for rooms
and their associated endpoints. More specifically:
● If a user or room is put into an area or moved to a different area, all of their associated endpoints will
be automatically updated to the same new area.
● If one of the associated endpoints of a user or room is moved to a different area, the change will
propagate to the associated user or room and any other endpoints owned by the user or room.
The logged-in user is warned that this will happen so that they can cancel the operation if this is not what
they intended. The only way to move an endpoint without also moving the owner and the owner’s other
endpoints is to disassociate the endpoint from the user or room before changing the area of the endpoint.
Area Conference Guests
When a new guest is added to a conference and saved to the guest book, the guest is configured to belong
to the area that the conference belongs to. This area information of the guest is persisted in the guest book.
If the conference’s area changes after this point, the guest’s area will not change. Users who can manage
more than one area can change the guest’s area by using the editing the guest book entry.
Polycom, Inc.
475
Configuring Multi-Tenancy
Using the Common Pool in a Multi-Tenancy
Environment
If a network device or RealPresence DMA pool order does not belong to an area, it is said to be in the
“common pool” and therefore is available for the system to use for any area. Any user who manages an
area and has permission to perform tasks within that area can view resources that are in the common pool.
For example, an area operator can schedule a conference on an RealPresence Collaboration Server (RMX)
system that is explicitly assigned to the area to which the operator belongs or the scheduler can use a
RealPresence Collaboration Server (RMX) system that belongs to the common pool.
Area Conference Templates
A user must have a system administrator role in order to create new conference templates. As a best
practice, the same user responsible for system set up should be responsible for creating conference
templates.
Conference templates can be assigned to an specific area and also associated with users with a specific
role.
As a best practice, when you create a conference template, give it an area-specific name. This is especially
helpful if you allow an area scheduler to scheduler conferences for more than one area.
When a scheduler (area or system) schedules a conference, he is required to use a conference template
from the same area as the conference area or a template that is assigned to no area (common pool).
Configure Areas
You must configure your system for areas. Most of the configuration tasks can be completed by a user with
the administrator role or area administrator role. However, network devices must be added by a user with
the device administrator role.
You need to enable your system for areas and then add an area for each tenant that will use your system.
1 Enable the areas feature.
2 Add the areas that you want to use.
3 Customize the logos for each area, if desired.
4 Add network devices to areas. This task must be done by a user who has the device administrator
role.
5 Import users into each area.
This step is necessary if you need to support users who do not reside in your single LDAP directory.
RealPresence Resource Manager system does not support integration with multiple LDAP
directories.
6 Assign roles to area users. By default, area users all have the area scheduler role. You need to
determine which, if any, of the area users will be given the area administrator or area operator roles.
7 Designate which users will manage each area.
Users must be allowed to manage an area in order to perform the tasks associated with their area
role. You can allow users to manage one area, no area, multiple areas (including areas to which they
do not belong).
Polycom, Inc.
476
Configuring Multi-Tenancy
8 Add resources to areas. This task can be done by the RealPresence Resource Manager system
administrator, or a user with the area administrator who is also allowed to manage the area to which
he is adding endpoints/rooms.
9 Add conference templates to areas. This task needs to be done by a user with the administrator
role.
10 Configure site topology.
11 Add billing codes, if preferred.
Enable Areas
In order to enable areas for the RealPresence Resource Manager system, login to the system with a user
who has the administrator role.
Users will need to log out and log back in to the RealPresence Resource Manager system in order for them
to view any changes.
To enable areas:
1 Go to Admin > Areas.
2 From the list of Actions, select Configure Areas.
3 In the Configure Areas dialog, ensure that the Enable Areas functions in Resource Manager
box is checked.
4 Optionally, choose a name in which to refer to areas. For example, you can rename Area and Areas
to Tenant and Tenants.
5 Click Save Configuration.
Create Areas for Tenants
You can create a new area for each new tenant.
To create areas:
1 Create a new area for the new tenant.
2 Give the area a name that appropriately identifies the tenant.
3 Create a user that will manage this area. You can do either of the following (or both).
 Add at least one user to the tenant area who has the Area Administrator role and is set up to
manage the area. That person can then manage their area themselves, including adding other
users to manage the area and its resources.
 You can also allow a user that belongs to no area or another area to manage the area and perform
tasks, Assign Users to Manage an Area(s).
Setting up Area Management
The RealPresence Resource Manager provides you flexibility when setting up how to manage an area.
Polycom, Inc.
477
Configuring Multi-Tenancy
Managing the Area with System Roles
You can either have a set of users with system roles who manage the administrative and conference
scheduling tasks for an area or you can set up area users with these roles and responsibilities.
In order for a user to perform tasks within ALL areas, a user must be given a system role that includes the
View and/Or Modify all Areas permission. All system roles have this permission by default.
Managing the Area with Area Roles
In order for a user to perform tasks within a a single area, a user must be given the following:
● An area role
● Be configured to manage the area to which they need to perform their tasks.
When associating a user with an area role, you must also explicit configure that user to manage the
area. If the user is not allowed to manage the area, he cannot perform the tasks associated with his
role. Area users can be configured to manage more than one area, see Assign Users to Manage an
Area(s).
Assigning Resources to an Area
You need to assign resources to an area. Resources that belong exclusively to an area must be assigned
to the area. Most resources can be created and assigned to an area by an Administrator or an Area
Administrator.
Network devices must be assigned to an area by someone with the Device Administrator role.
The Administrator role is the only pre-defined role that can add or edit conference templates.
Resources Belong to One or No Area
The following resources need to be assigned to one area or no area.
● Users
● Rooms
● Guests
● Groups
● Address Books
● Endpoints
● Network Devices
● Conferences
● Conference Templates
● Machine Accounts
● Peripherals
Polycom, Inc.
478
Configuring Multi-Tenancy
Resources Belong to One or More Areas (or no Area)
Resources that can be associated with one or more areas or no areas are:
● RealPresence DMA Pool Orders
Adding Users to An Area
When you add users, create user names using the email address format. This will ensure that all user
names are unique. Otherwise two people named Bob Smith belonging to different tenants may end up with
the same user name. By following an email address format, Bob Smith in TenantA could have
bsmith@tenantA.com as a user name and Bob Smith in TenantB could have bsmith@tenantB.com.
Configuring Site Topology
You can use site topology to limit the bandwidth used by each tenant. This can be accomplished with a
combination of a carefully organized site topology and the Site Statistics tool.
You can assign a site to a particular area. A site cannot be shared between areas.
Use the following guidelines:
● As a best practice, use a naming convention that identifies the area in the site name. For example,
all sites in the blue area should be named blue_<sitename>.
● Site names should be unique across the system. That is, two areas should not use the same site
name.
● At a minimum, each site in an area should have a site link to the service provider or the internet cloud.
It is best practice that the purpose of each link be obvious from the site link name. Any site link being
used to measure bandwidth for a specific tenant should be named in such a way as to make this
purpose clear.
Endpoints and devices should be associated with the same area to which their site belongs or they may not
be visible to area constrained users when searching by site.
Polycom, Inc.
479
Configuring Multi-Tenancy
Site Topology for Multiple Tenants
Associating Billing Codes with Conferences
The RealPresence Resource Manager system supports associating a billing code with a conference. This
feature is only available when areas are enabled.
You can define billing codes within an area that can then be assigned to conferences. When an area
scheduler creates a conference within an area that includes billing codes, the scheduler can associate a
billing code with that conference.
Billing codes are included in CDRs. This enables you to track how much each department (billing code)
within an area is using video resources. Service providers can use this information to create billing
breakdowns for their tenants.
Users with the Administrator role can create new billing codes for an area. Users with the area scheduler or
area operator role are allowed to associate a billing code with a conference when the schedule the
conference.
Add a New Billing Code
Billing codes are supported when areas are enabled. You can add a billing code(s) to an area when you
create an area or when you edit an existing area.
To add or edit a new billing code:
1 Navigate to Admin > Areas.
Polycom, Inc.
480
Configuring Multi-Tenancy
2 Click Add to add a new area or select an area in the list and click Edit
3 In the Edit an Area dialog, click Billing Code.
4 On the Billing Code page, do the following:
a In the Billing Code field, enter the billing code you want to use.
b Enter a description for the billing code.
c Click Apply.
5 Click OK.
Delete a Billing Code
Users with the administrator role can delete billing codes.
To delete a billing code:
1 Navigate to Admin > Areas.
2 Select an area in the list and click Edit.
3 In the Edit an Area dialog, click Billing Code.
4 On the Billing Code page, do the following:
a Select a billing code.
b Click Delete.
5 Click OK.
Note: To clear the billing code fields after an existing billing code in the list has been selected, click Apply.
Associating a Billing Code with a Conference
When creating a new conference, you can select a billing code after you select conference participants.
Viewing Billing Code Information
The Conference Usage Report now includes billing code information for each conference. Billing code
information is also include in conference information sent to the Polycom RealPresence DMA system and
the Polycom RealPresence Collaboration Server (RMX) systems.
When monitoring conferences, you can also filter conferences by billing code.
Polycom, Inc.
481
Managing Areas
This section describes how to manage areas in the Polycom® RealPresence® Resource Manager system.
It includes these topics:
● Enable Areas
● Add an Area
● Edit an Area
● Viewing All Areas
● View Information for a Specific Area
● Remove an Area
● Customizing the Area Logos (system and CMA Desktop) for the Area
Enable Areas
Before you can manage area and use area related features, you need to first enable areas.
To enable areas:
1 Go to Admin > Areas.
2 Select More > Configure Areas.
3 In the Configure Areas dialog, mark the Enable Areas Functions in Resource Manager check
box.
4 Click OK and log in again.
Add an Area
You can add an area. Before adding an area, review the Create Areas for Tenants topic.
To add an area:
1 Go to Admin > Areas > Areas.
2 Click
to add a new area.
3 Click Set Resource Manager System Logo.
4 In the Set Resource Manager System Logo dialog box, browse to a file to upload and click
Upload.
5 When the upload is complete, click OK.
6 Click Set CMA Desktop Logo.
Polycom, Inc.
482
Managing Areas
7 In the Set CMA Desktop Logo dialog box, browse to a file to upload and click Upload.
8 When the upload is complete, click OK.
9 Click Billing Code.
10 On the Billing Code page, do the following:
a Click
to add a new billing code.
b In the Billing Code field, enter the billing code you want to use.
c Enter a description for the billing code.
d Click OK.
11 Click OK.
Edit an Area
You can edit an area.
To add an area:
1 Navigate to Admin > Areas.
2 Select an area to edit and click
.
3 Click Set Resource Manager System Logo.
4 In the Set Resource Manager System Logo dialog box, browse to a file to upload and click
Upload.
5 When the upload is complete, click OK.
6 Click Set CMA Desktop Logo.
7 In the Set CMA Desktop Logo dialog box, browse to a file to upload and click Upload.
8 When the upload is complete, click OK.
9 Click Billing Code and do the following:
a In the Billing Code field, enter the billing code you want to use.
b Enter a description for the billing code.
c Click Apply.
10 Click OK.
Viewing All Areas
You can view the list of existing areas from Admin > Areas if you have the Administrator role. The following
information is available.
Field
Description
Area Name
Name for the area.
Description
Description of the area.
Area Resource Manager Users
Number of users that can manage the selected area.
Polycom, Inc.
483
Managing Areas
Field
Description
Endpoints
Number of endpoints that belong to the selected area
Rooms
Number of rooms that belong to the selected area.
Members
Number of users that belong to the selected area.
View Information for a Specific Area
You can view all information for a specific area including resources and users.
You must be assigned the Administrator role to do this task.
To view information for a specific area:
1 Go to Admin > Areas.
2 Click an area in the list.
3 Select the area information from the More drop-down list.
4 The following View actions are available. The details you can view from each action is dependent
on the type of resource it is. The following resources are available:
 View Area Rooms. For more information, see View the Rooms List.
 View Area Resource Manager Users. This action displays a list of all users who are allowed to
managed the selected area. For more information, see View User Information.
 View Area Endpoints. For more information, see View Endpoint Details.
 View Area Guests. For more information, see Managing the Guest Book and Favorites Lists.
 View Area Members. This action provides a list of all users that belong to the selected area. For
more information, see View User Information.
 View Guests. For more information, see Managing the Guest Book and Favorites Lists.
 View Area Groups. For more information, see Managing Groups.
 View Area Address Books. For more information, see Using Multiple Address Books.
 View Area Conference. For more information, see Managing Conferences and Participants.
 View Direct Conference Templates. For more information, see Direct Conference Templates
Overview.
Remove an Area
When you no longer need an area, you can either move the area’s contents to another area or delete the
area and all its contents. A user must have the Administrator role in order to move or delete an area.
Consider which of these approaches is right for the area:
To delete an area and all of its resources:
1 Backup your data.
2 Click
Polycom, Inc.
to delete the area and its resources.
484
Managing Areas
To delete the area, but keep all of its resources in the system:
1 Use the Move Contents action to move all of the area’s resources to another area or to no area.
Move Contents will also delete the area from which contents are moved.
If you wish to keep some of the area’s resources, but delete the rest, then:
2 Edit the resources you would like to keep and reassign them to other areas or to no area.
3 Backup your data.
4 Click
to delete the area and its remaining resources.
Move the Contents of an Area
If you wish to delete the area, but keep all of its resources in the RealPresence Resource Manager system,
then you can move the contents of the area.
When you move the contents of an area:
● All resources will now belong to the specified destination (an area or no area).
● The area and any custom logos are deleted.
● Any users who managed the moved area will not be automatically allowed to manage the new area.
If you want the moved users to manage the destination area, you will need to explicitly edit the user
to do so.
To move an area’s resources to another area:
1 Go to Admin > Areas.
2 Select the area.
3 Click More > Move Contents.
4 Select the available area from the Move the objects associated with the area being deleted to
area drop down list.
5 Click OK.
Deleting an Area and its Resources
If you no long need an area and its resources, you can delete them from the RealPresence Resource
Manager system.
Before deleting an area, you must manually un-assign any network devices and sites from the area. You
should also verify that there are no ongoing conferences or area users involved in a conference belonging
to another area.
When you delete an area, the following actions take place:
● All future conferences are canceled.
● All past conferences are associated with no area (None).
● All pool orders are disassociated from the area.
Users, rooms and endpoints from this area