Garmin 7000 Polycom RealPresence DMA System Operations Guide User Manual To The 156a113a E3cd 4b93 B579 00256a680052

User Manual: Garmin 7000 to the manual

Open the PDF directly: View PDF .
Page Count: 437

Download
Open PDF In Browser	View PDF

Operations Guide

6.2 | December 2014 | 3725-76302-001P

Polycom® RealPresence® DMA®
7000 System

The Polycom RealPresence DMA 7000 System is also known and certified as the DMA System.

Copyright© 2014, 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

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.

Java is a registered trademark of Oracle America, Inc., and/or its affiliates.

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

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.

Contents

Polycom® RealPresence DMA® 7000 System Overview . . . . . . . . . . . . . . . . . . . 13
Introduction to the Polycom RealPresence DMA System . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
The Polycom RealPresence DMA System’s Primary Functions . . . . . . . . . . . . . . . . . . . . 13
The Polycom RealPresence DMA System’s Three Configurations . . . . . . . . . . . . . . . . . 16
System Capabilities and Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
System Port Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Polycom Solution Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Working in the Polycom RealPresence DMA System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Accessing the Polycom RealPresence DMA System . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Field Input Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Settings Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Polycom RealPresence DMA System User Roles and Their Access Privileges . . . . . . . . 22
Open Source Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
License Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Polycom RealPresence DMA System Initial Configuration Summary . . . . . . . . 27
Add Required DNS Records for the Polycom RealPresence DMA System . . . . . . . . . . . . . . 28
Additional DNS Records for SIP Proxy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Additional DNS Records for the H.323 Gatekeeper . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Additional DNS Records for the Optional Embedded DNS Feature . . . . . . . . . . . . . . . . . 29
Verify That DNS Is Working for All Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
License the Polycom RealPresence DMA System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
License the RealPresence DMA System, Appliance Edition . . . . . . . . . . . . . . . . . . . . . . 30
License the RealPresence DMA System, Virtual Edition . . . . . . . . . . . . . . . . . . . . . . . . . 31
Set Up Signaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Configure the Call Server and Optionally Create a Supercluster . . . . . . . . . . . . . . . . . . . . . . 32
Set Up Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Set Up MCUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Connect to Microsoft Active Directory® . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Set Up Conference Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Test the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Polycom, Inc.

Contents

System Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Security Certificates Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
How Certificates Work . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Forms of Certificates Accepted by the Polycom RealPresence DMA System . . . . . . . . . 37
How Certificates Are Used by the Polycom RealPresence DMA System . . . . . . . . . . . . . 38
Frequently Asked Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Certificate Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Certificate Information Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Certificate Signing Request Dialog

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Add Certificates Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Certificate Details Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Certificate Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Install a Certificate Authority’s Certificate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Create a Certificate Signing Request in the RealPresence DMA System . . . . . . . . . . . . 45
Install a Certificate in the RealPresence DMA System

. . . . . . . . . . . . . . . . . . . . . . . . . . 46

Remove a Certificate from the RealPresence DMA System . . . . . . . . . . . . . . . . . . . . . . 47
Security Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
The Consequences of Enabling Maximum Security Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Enabling File Uploads in Maximum Security with Mozilla Firefox . . . . . . . . . . . . . . . . . . . 55
Login Policy Settings

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Local Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Session

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Local User Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Banner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Access Policy Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Reset System Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Local Cluster Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Network Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Routing Configuration Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Time Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Licenses for the Appliance Edition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Licenses for the Virtual Edition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Signaling Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
H.323 and SIP Signaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Add Guest Port Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Edit Guest Port Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Add Guest Prefix Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Edit Guest Prefix Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Polycom, Inc.

Contents

Logging Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Alerting Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Local Cluster Configuration Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Add Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Configure Signaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Configure Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Automatically Send Usage Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Enable or Disable Automatic Data Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
See the Collected Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Device Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Active Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Call Details Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Endpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Names/Aliases in a Mixed H.323 and SIP Environment . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Naming ITP Systems Properly for Recognition by the Polycom RealPresence DMA System
93
Add Endpoint Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Edit Device Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Edit Devices Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Add Alias Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Edit Alias Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Associate User Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Site Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Site Link Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
External Gatekeeper . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Add External Gatekeeper Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Edit External Gatekeeper Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
External SIP Peer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Multiple External SIP Peers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Add External SIP Peer Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Edit External SIP Peer Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
SIP Peer Postliminary Output Format Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Add Authentication Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Edit Authentication Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Add Outbound Registration Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Edit Outbound Registration Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
External H.323 SBC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Add External H.323 SBC Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Edit External H.323 SBC Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

Polycom, Inc.

Contents

MCU Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
MCUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Considerations when using MCUs with the RealPresence DMA system . . . . . . . . . . . . 127
Add MCU Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Edit MCU Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Add Session Profile Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Edit Session Profile Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
ISDN Gateway Selection Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
MCU Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
MCU Pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Add MCU Pool Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
Edit MCU Pool Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
MCU Pool Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
MCU Pool Orders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
Add MCU Pool Order Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Edit MCU Pool Order Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
MCU Selection Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
MCU Availability and Reliability Tracking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
MCU Pool Order Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

Integrations with Other Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Microsoft Active Directory® Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Microsoft Active Directory Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
Active Directory Integration Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
Understanding Base DN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Adding Passcodes for Enterprise Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
About the System’s Directory Queries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
Microsoft® Lync® 2013 Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
Lync 2010 vs. Lync 2013 Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
Scheduled Conferences with Polycom RealConnect™ . . . . . . . . . . . . . . . . . . . . . . . . . 168
Automatic Contact Creation and Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
Active Directory Service Account Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
Lync and non-Lync Endpoint Collaboration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
Considerations and Requirements for Lync 2013 Integration . . . . . . . . . . . . . . . . . . . . . 170
Lync 2010 and 2013 Client / Server Feature Support . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Integrate RealPresence DMA and Lync 2013 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Diagnose Presence Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
Microsoft Exchange Server Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
Polycom Solution and Integration Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
Differences between Calendaring and Scheduling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

Polycom, Inc.

Contents

Microsoft Exchange Server Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
Exchange Server Integration Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
RealPresence Resource Manager Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
RealPresence Resource Manager Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
Join RealPresence Resource Manager Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
RealPresence Resource Manager Integration Procedures . . . . . . . . . . . . . . . . . . . . . . . 179
Juniper Networks SRC Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
Juniper Networks SRC Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
Juniper Networks SRC Integration Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182

Conference Manager Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Conference Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Class of Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
Default Polycom Conference Contacts Presence Settings . . . . . . . . . . . . . . . . . . . . . . . 186
Remove Contacts from Active Directory Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
Conference Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
Two Types of Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
Template Priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
About Conference IVR Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
About Cascading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
Conference Templates List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
Add Conference Template Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
Edit Conference Template Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
Select Layout Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
Conference Templates Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
IVR Prompt Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
Shared Number Dialing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
Add Virtual Entry Queue Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
Add Direct Dial Virtual Entry Queue Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
Edit Virtual Entry Queue Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
Edit Direct Dial Virtual Entry Queue Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
Script Debugging Dialog for VEQ Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
Sample Virtual Entry Queue Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225

Superclustering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
About Superclustering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
DMAs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
Join Supercluster Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230
Supercluster Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231

Polycom, Inc.

Contents

Call Server Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
About the Call Server Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
Call Server Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
Domains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
Dial Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
Test Dial Rules Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
The Default Dial Plan and Suggestions for Modifications . . . . . . . . . . . . . . . . . . . . . . . . 243
Add Dial Rule Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
Edit Dial Rule Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
Preliminary/Postliminary Scripting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
Predefined Preliminary/Postliminary Scripting Variables . . . . . . . . . . . . . . . . . . . . . . . . 254
Preliminary/Postliminary Scripting Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255
How Dial Rule Actions Affect SIP Headers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257
Script Debugging Dialog for Preliminaries/Postliminaries . . . . . . . . . . . . . . . . . . . . . . . . 258
Sample Preliminary and Postliminary Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259
Hunt Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
Add Hunt Group Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
Edit Hunt Group Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
Add Alias Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
Edit Alias Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
Device Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
Add Device Authentication Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
Edit Device Authentication Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268
Registration Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268
Registration Policy Scripting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270
Script Debugging Dialog for Registration Policy Scripts . . . . . . . . . . . . . . . . . . . . . . . . . 272
Sample Registration Policy Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273
Prefix Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275
Add Simplified ISDN Gateway Dialing Prefix Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276
Edit Simplified ISDN Gateway Dialing Prefix Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277
Edit Vertical Service Code Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278
Embedded DNS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278
History Retention Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280

Site Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282
About Site Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282
Bandwidth Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283
Sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284
Site Information Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
Add Site Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286

Polycom, Inc.

Contents

Edit Site Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290
Add Subnet Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294
Edit Subnet Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295
Site Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296
Add Site Link Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
Edit Site Link Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
Site-to-Site Exclusions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298
Add Site-to-Site Exclusion Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298
Territories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299
Add Territory Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300
Edit Territory Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301
Network Clouds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302
Add Network Cloud Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302
Edit Network Cloud Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303
Site Topology Configuration Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304

Users and Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306
User Roles Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306
Adding Users Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307
Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308
Add User Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310
Edit User Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312
Authentication Required Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315
Select Associated Endpoints Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315
Conference Rooms Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315
Add Conference Room Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317
Edit Conference Room Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322
Add Dial-out Participant Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326
Edit Dial-out Participant Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326
Users Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326
Conference Rooms Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328
Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329
Import Enterprise Groups Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331
Edit Group Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331
Enterprise Groups Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334
Login Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335
Change Password Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336

System Management and Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337
Management and Maintenance Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337

Polycom, Inc.

Contents

Administrator Responsibilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337
Administrative Best Practices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338
Auditor Responsibilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338
Auditor Best Practices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338
Provisioner Responsibilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339
Recommended Regular Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339
Regular archive of backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339
General system health and capacity checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339
Microsoft Active Directory health . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340
Security configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341
Certificates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341
Network usage data export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341
CDR export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341
Dashboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341
Active Directory Integration Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342
Call Server Active Calls Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342
Call Server Registrations Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343
Cluster Info Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343
Conference History – Max Participants Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343
Conference Manager MCUs Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344
Conference Manager Usage Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344
Exchange Server Integration Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345
Juniper Networks SRC Integration Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345
License Status Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346
RealPresence Resource Manager Integration Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346
Signaling Settings Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346
Supercluster Status Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346
Territory Status Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347
User Login History Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347
Alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348
Supercluster Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349
Territory Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350
Asynchronous Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352
RealPresence Resource Manager System Integration . . . . . . . . . . . . . . . . . . . . . . . . . . 352
Active Directory Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353
Exchange Server Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355
Database Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356
Lync Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357
Signaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358
Certificate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359

Polycom, Inc.

Contents

Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361
Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362
Server Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364
Data Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366
System Health and Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367
MCUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368
Endpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372
Conference Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374
Conference Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374
Lync Presence Publishing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375
Call Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378
Call Bandwidth Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379
System Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379
System Logs Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380
Troubleshooting Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382
Ping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382
Traceroute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382
Top . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382
I/O Stats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382
SAR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383
NTP Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383
Check Configuration Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383
Diagnostics for your Polycom Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384
Backing Up and Restoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384
Confirm Restore Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386
Backup and Restore Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386
Upgrading the Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391
Basic Upgrade Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392
Incompatible Software Version Supercluster Upgrades . . . . . . . . . . . . . . . . . . . . . . . . . 396
Factors to Consider for an Incremental Supercluster Upgrade . . . . . . . . . . . . . . . . . . . . 397
Simplified Supercluster Upgrade (Complete Service Outage) . . . . . . . . . . . . . . . . . . . . 398
Complex Supercluster Upgrade (Some Service Maintained) . . . . . . . . . . . . . . . . . . . . . 401
RealPresence DMA System, Virtual Edition System Upgrade . . . . . . . . . . . . . . . . . . . . 401
Adding a Second Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401
Expanding an Unpatched System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402
Expanding a Patched System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403
Replacing a Failed Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404
Shutting Down and Restarting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404

Polycom, Inc.

Contents

System Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406
Alert History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406
Call History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406
Export History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 408
Conference History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 408
Export History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409
Associated Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409
Conference Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410
Property Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410
Call Detail Records (CDRs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411
Exporting CDR Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411
Call Record Layouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411
Conference Record Layouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416
Registration History Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 418
Registration History Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419
Active Directory Integration Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420
Orphaned Groups and Users Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 422
Orphaned Groups and Users Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 422
Conference Room Errors Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423
Exporting Conference Room Errors Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424
Enterprise Passcode Errors Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425
Exporting Enterprise Passcode Errors Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 426
Network Usage Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 426
Exporting Network Usage Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427

Polycom RealPresence DMA System SNMP Support . . . . . . . . . . . . . . . . . . . . 430
SNMP Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 430
SNMP Framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 430
SNMP Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431
SNMP Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431
Configure SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432
Enable the SNMP Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432
Add an SNMP Notification User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433
Edit Notification User Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434
Add an SNMP Notification Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434
Edit Notification Agent Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 435
Download MIBs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 436
Available SNMP MIBs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 436

Polycom, Inc.

Polycom® RealPresence DMA® 7000
System Overview
This section provides an overview of the Polycom® Distributed Media Application™ (RealPresence DMA®)
7000 system. It includes these topics:
● Introduction to the Polycom RealPresence DMA System
● Polycom Solution Support
● Working in the Polycom RealPresence DMA System
● Open Source Software

Introduction to the Polycom RealPresence DMA
System
The Polycom RealPresence DMA system is a highly reliable and scalable video collaboration infrastructure
solution based on the Polycom® Proxias™ application server. The following topics introduce you to the
system:
● The Polycom RealPresence DMA System’s Primary Functions
● The Polycom RealPresence DMA System’s Three Configurations
● System Capabilities and Constraints
● System Port Usage

The Polycom RealPresence DMA System’s Primary Functions
The primary functions of the Polycom RealPresence DMA system are described briefly below.

Conference Manager
The Polycom RealPresence DMA system’s Conference Manager facilitates multipoint video conferencing.
A multipoint video conference is one in which multiple endpoints are connected, with all participants able to
see and hear each other. The endpoints connect to a media server (Multipoint Control Unit, or MCU), which
processes the audio and video from each and sends the conference audio and video streams back to them.
Traditionally, such multipoint conferences had to be scheduled in advance, reserving ports on a specific
MCU, in order to ensure the availability of resources. Conference Manager makes this unnecessary.
Conference Manager uses advanced routing policies to distribute voice and video calls among multiple
MCUs, creating a single virtual resource pool. This greatly simplifies multipoint video conferencing resource
management and uses MCU resources more efficiently.
The Polycom RealPresence DMA system integrates with your Microsoft® Active Directory®, automating the
task of provisioning users with virtual meeting rooms (VMRs), which are available for use at any time for
Polycom, Inc.

Polycom® RealPresence DMA® 7000 System Overview

multipoint video conferencing. Combined with its advanced resource management, this makes
reservationless (ad hoc) video conferencing on a large scale feasible and efficient, reducing or eliminating
the need for conference scheduling.
The Polycom RealPresence DMA system’s ability to handle multiple MCUs as a single resource pool makes
multipoint conferencing services highly scalable. You can add MCUs on the fly without impacting end users
and without requiring re-provisioning. The RealPresence DMA system can span a conference across two
or more MCUs (called cascading), enabling the conference to contain more participants than any single
MCU can accommodate.
The Conference Manager continually monitors the resources used and available on each MCU and
intelligently distributes conferences among them. If an MCU fails, loses its connection to the system, or is
taken out of service, the Polycom RealPresence DMA system distributes new conferences to the remaining
MCUs. Every conference on the failed MCU is restarted on another MCU (provided there is space
available). The consequences for existing calls in those conferences depend on whether they’re H.323 or
SIP:
● H.323 participants are not automatically reconnected to the conference. In order to rejoin the
conference, dial-in participants simply need to redial the same number they used for their initial
dial-in. Dial-out participants will need to be dialed out to again; the RealPresence DMA system
doesn’t automatically redial out to them.
● SIP participants are automatically reconnected to the conference on the new MCU. This includes
both dial-in and dial-out SIP participants. No new dial-out is needed because the RealPresence DMA
system maintains the SIP call leg to the participant and only has to re-establish the SIP call leg from
the RealPresence DMA system to the MCU.

Call Server
The Polycom RealPresence DMA system’s Call Server provides the following functionality:
● H.323 gatekeeper
● SIP registrar and proxy server
● H.323 <—> SIP transition gateway
● Dial plan and prefix services
● Device authentication
● Bandwidth management
The Call Server can also be integrated with a Juniper Networks Service Resource Controller (SRC) to
provide bandwidth and QoS assurance services.

RealPresence® Platform API
The Polycom RealPresence DMA system optionally allows an API client application, developed by you or a
third party, to access the Polycom RealPresence® Platform Application Programming Interface (API). This
API access is licensed separately. It provides programmatic access to the Polycom RealPresence DMA
system for the following:
● Provisioning
● Conference control and monitoring
● Call control and dial-out
● Billing and usage data retrieval
● Resource availability queries
Polycom, Inc.

Polycom® RealPresence DMA® 7000 System Overview

The API uses XML encoding over HTTPS transport and adheres to a Representational State Transfer
(REST) architecture.
To browse the RealPresence Platform API reference documentation, go to Help > RealPresence Platform
API Documentation in the system’s web interface.
Note: Asynchronous API communication
The API communicates asynchronously. Clients subscribing to event notifications via the API must be
prepared to receive notifications out of order.

A Polycom RealPresence Resource Manager system can integrate with the RealPresence DMA system via
the API. No separate license is needed in order for the RealPresence Resource Manager system to use the
API. It provides the full programmatic access to the RealPresence DMA system described above and
enables users of the RealPresence Resource Manager scheduling interface to:
● Schedule conferences using the RealPresence DMA system’s MCU resources.
● Set up Anytime conferences. Anytime conferences are referred to as preset dial-out conferences in
the RealPresence DMA system (see Edit Conference Room Dialog).
Note: Integration with a RealPresence Resource Manager system
Integrating the Polycom RealPresence Resource Manager system with the RealPresence DMA
system via the API is separate and distinct from integrating the RealPresence DMA system with a
RealPresence Resource Manager system.
• The former enables RealPresence Resource Manager users to obtain information from and use
functionality of the RealPresence DMA system that would otherwise be accessible only in the
RealPresence DMA system’s management interface.
• The latter enables the RealPresence DMA system to retrieve site topology and user-to-device
associations from the RealPresence Resource Manager system.
For convenience, however, when you integrate your RealPresence Resource Manager system to the
RealPresence DMA system, the RealPresence DMA system automatically integrates itself back to the
RealPresence Resource Manager system so that the RealPresence DMA system will have the site
topology and user-to-device information that the RealPresence Resource Manager system expects it
to have.

SVC Conferencing Support
This version of the Polycom RealPresence DMA system supports the Annex G extension of the H.264
standard, known as H.264 Scalable Video Coding (SVC), for both point-to-point and multipoint (VMR) calls.
SVC is sometimes referred to as layered media because the video streams consist of a base layer that
encodes the lowest available quality representation plus one or more enhancement layers that each provide
an additional quality improvement. SVC supports three dimensions of scalability: temporal (frames per
second), spatial (resolution and aspect ratio), and quality (signal-to-noise ratio).
The video stream to a device can be tailored to fit the bandwidth available and device capabilities by
adjusting the number of enhancement layers sent to the device.
For multipoint conferencing, the MCU doesn't have to do processing-intensive mixing and transcoding to
optimize the experience for each device. Instead, it simply passes the video stream from each device to
each device, including the enhancement layers that provide the best quality the device can support.
Polycom’s SVC solution focuses on the temporal and spatial dimensions. It offers a number of advantages
over standard AVC conferencing, including:
Polycom, Inc.

Polycom® RealPresence DMA® 7000 System Overview

● Improved video quality at lower bandwidths
● Improved audio and video error resiliency (good audio quality with more than 50% packet loss, good
video quality with more than 25% packet loss)
● Lower end-to-end latency (typically less than half that of AVC)
● More efficient use of bandwidth
● Lower infrastructure cost and operational expenses
● Easier to provision, control, and monitor
● Better security (end-to-end encryption)
Polycom’s SVC solution is supported by the Polycom RealPresence Platform and Environments, including
the latest generation of Polycom MCUs and RealPresence room, personal, desktop, and mobile endpoints.
Existing RMX MCUs with MPMx cards can be made SVC-capable with a software upgrade, and doing so
triples their HD multipoint conferencing capacity.
RealPresence Collaboration Server 800s MCUs support mixed-mode (SVC+AVC) conferences. Both SVC
and AVC endpoints can join the conference, and each gets the appropriate experience: SVC endpoints get
SVC mode and get a video stream for each AVC participant; AVC endpoints get a single Continuous
Presence (CP) video stream of the participants (both AVC and SVC) supplied by the MCU.
When the Polycom RealPresence DMA system selects an MCU that doesn’t support SVC for a conference
configured for mixed mode, it starts the conference as an AVC-only conference (all SVC-capable endpoints
also support AVC). But if the MCU supports SVC but not mixed mode (RMX 7.8), the conference fails to
start.
Refer to your RealPresence Collaboration Server or RMX documentation for important information about
the MCU’s implementation of SVC conferencing and its configuration, limitations, and constraints.
See also:
Introduction to the Polycom RealPresence DMA System

The Polycom RealPresence DMA System’s Three Configurations
Depending on your organization’s needs, you can deploy the Polycom RealPresence DMA system in one
of the following three configurations.

Two-server Cluster Configuration
The Polycom RealPresence DMA system is designed to be deployed as a pair of co-located redundant
servers that share the same virtual IP address(es). The two-server cluster configuration of the Polycom
RealPresence DMA system has no single point of failure within the system that could cause the service to
become unavailable.
The two servers communicate over the private network connecting them. To determine which one should
host the public virtual IP address, each server uses three criteria:
● Ability to ping its own public physical address
● Ability to ping the other server’s public physical address
● Ability to ping the default gateway
In the event of a tie, the server already hosting the public virtual address wins.

Polycom, Inc.

Polycom® RealPresence DMA® 7000 System Overview

Failover to the backup server takes about five seconds in the event of a graceful shutdown and about 40
seconds in the event of a power loss or other failure. In the event of a single server failure, these things
happen:
● All calls that are being routed through the failed server are terminated (including SIP calls, VMR calls,
and routed mode H.323 calls). These users simply need to redial the same number, and they’re
placed back into conference or reconnected to the point-to-point call they were in. The standby server
takes over the virtual signaling address, so existing registrations and new calls are unaffected.
● Direct mode H.323 point-to-point calls are not dropped, but the bandwidth management system loses
track of them. This could result in overuse of the available network bandwidth.
● If the failed server is the active web host for the system management interface, the active user
interface sessions end, the web host address automatically migrates to the remaining server, and it
becomes the active web host. Administrative users can then log back into the system at the same
URL. The system can always be administered via the same address, regardless of which server is
the web host.
The internal databases within each Polycom RealPresence DMA system server are fully replicated to the
other server in the cluster. If a catastrophic failure of one of the database engines occurs, the system
automatically switches itself over to use the database on the other server.

Single-server Configuration
The Polycom RealPresence DMA system is also available in a single-server configuration. This
configuration offers all the advantages of the Polycom RealPresence DMA system except the redundancy
and fault tolerance at a lower price. It can be upgraded to a two-server cluster at any time.
This manual generally assumes a redundant two-server cluster. Where there are significant differences
between the two configurations, those are spelled out.

Superclustering
To provide geographic redundancy and better network traffic management, up to five geographically
distributed Polycom RealPresence DMA system clusters (two-server or single-server) can be integrated into
a supercluster. All five clusters can be Call Servers (function as gatekeeper, SIP proxy, SIP registrar, and
gateway). Up to three can be designated as Conference Managers (manage an MCU resource pool to host
conference rooms).
The superclustered Polycom RealPresence DMA systems can be centrally administered and share a
common data store. Each cluster maintains a local copy of the data store, and changes are replicated to all
the clusters. Most system configuration is supercluster-wide. The exceptions are cluster-specific or
server-specific items like network settings and time settings.

Polycom, Inc.

Polycom® RealPresence DMA® 7000 System Overview

Note: Clusters vs. superclusters
Technically, a standalone Polycom RealPresence DMA system (two-server or single-server) is a
supercluster that contains one cluster. All the system configuration and other data that’s shared
across a supercluster is kept in the same data store. At any time, another Polycom RealPresence
DMA system can be integrated with it to create a two-cluster supercluster that shares its data store.
It’s important to understand the difference between two co-located servers forming a single
RealPresence DMA system (cluster) and two geographically distributed RealPresence DMA clusters
(single-server or two-server) joined into a supercluster.
A single two-server RealPresence DMA system (cluster) has the following characteristics:
• A single shared virtual IP address and FQDN, which switches from one server to the other when
necessary to provide local redundancy and fault tolerance.
• A single management interface and set of local settings.
• Ability to manage a single territory, with no territory management backup.
• A single set of Call Server and Conference Manager responsibilities.
A supercluster consisting of two RealPresence DMA clusters (single-server or two-server) has the
following characteristics:
• Separate IP addresses and FQDNs for each cluster.
• Separate management interfaces and sets of local settings for each cluster.
• Ability for each cluster to manage its own territory, with another cluster able to serve as backup for
that territory.
Different Call Server and Conference Manager responsibilities for each territory and thus each cluster.

System Capabilities and Constraints
The following capabilities and constraints apply to the entire supercluster:
● Number of sites: 500
● Number of subnets: 5000
● Number of clusters in a supercluster: 5 (not counting an integrated Polycom RealPresence Resource
Manager system)
● Number of MCUs enabled for conference rooms: 64
● Number of territories enabled for conference rooms (Conference Manager enabled): 3
● Number of concurrent VMR calls: 1200 per cluster (Conference Manager), up to 3600 total
● Number of concurrent SIP<->H.323 gateway calls: 500
● Size of Active Directory supported: 1,000,000 users and 1,000,000 groups (up to 10,000 groups may
be imported)
The following capabilities and constraints apply to each cluster in the supercluster:
● Number of registrations: 15000
● Number of contacts registered to a Microsoft Lync 2013 server: 25,000
● Number of concurrent H.323 calls: 5000
● Number of concurrent SIP calls: 5000
● Total number of concurrent calls: 5000
● Number of network usage data points retained: 8,000,000

Polycom, Inc.

Polycom® RealPresence DMA® 7000 System Overview

● Number of IRQ messages sent per second: 100
● Number of history records retained per cluster:
 500,000 registration history
 2,000,000 registration signaling history
 500,000 call history
 12,500,000 call signaling history
 200,000 conference history
 10,000 CDR export history

System Port Usage
The following table lists the inbound ports that may be open on the Polycom RealPresence DMA system,
depending on signaling and security settings, integrations, and system configuration.
Port

Protocol

Description

TCP

SSH. Only available if Linux console access is enabled (see Security
Settings).

TCP/UDP

DNS. Only available if the embedded DNS server is enabled (see
Embedded DNS).

TCP

HTTP. Redirects to 443 (HTTP access is not allowed). Disabled in
maximum security mode.

123

UDP

NTP. Only available if an NTP server is specified (see Time Settings).

161

UDP

SNMP. Default port; can be changed or disabled (see Configure SNMP).

443

TCP

HTTPS. Redirects to 8443.

1718

UDP

H.323 RAS. Default port; can be changed (see Signaling Settings).

1719

UDP

H.323 RAS. Default port; can be changed (see Signaling Settings).

1720

TCP

H.323 H.225 signaling. Default port; can be changed (see Signaling
Settings).

4449

TCP

LDAP. OpenDJ replication (superclustering).

5060

TCP/UDP

Unencrypted SIP. Default port; can be changed or disabled (see Signaling
Settings).

5061

TCP

SIP TLS. Default port; can be changed (see Signaling Settings).

8080

TCP

HTTP. Redirects to 443 (HTTP access is not allowed). Disabled in
maximum security mode.

8443

TCP

HTTPS. Management interface access.

8444

TCP

HTTPS. Supercluster communication.

8989

TCP

LDAP. OpenDJ replication (superclustering).

Polycom, Inc.

Polycom® RealPresence DMA® 7000 System Overview

Port

Protocol

Description

9090

TCP

HTTPS. Upgrade status monitoring (only while upgrade process is
running).

36000-61000

TCP

Ephemeral port range.

The following table lists the remote ports to which the Polycom RealPresence DMA system may connect,
depending on signaling and security settings, integrations, and system configuration.
Port

Protocol

Description

TCP

HTTP. MCUs, Exchange Web Services (calendaring). Only used if
unencrypted connections are enabled (see Security Settings).

162

TCP/UDP

SNMP notifications (Traps or Informs). Used if SNMP is enabled and
configured to send notifications (see Configure SNMP), or if system is
monitored with RealPresence Platform Director.

389

TCP

LDAP. Active Directory integration. RealPresence Platform Director
licensing and API communication.

443

TCP

HTTPS. MCUs, Exchange Web Services (calendaring), RealPresence
Platform Director licensing and API communication.

1718

UDP

H.323 RAS. Default port; can be changed (see Signaling Settings).

1719

UDP

H.323 RAS. Default port; can be changed (see Signaling Settings).

1720

TCP

H.323 H.225 signaling. Default port; can be changed (see Signaling
Settings).

3268

TCP

Global Catalog. Active Directory integration.

3269

TCP

Secure Global Catalog. Active Directory integration.

4449

TCP

OpenDJ replication (superclustering).

5060

TCP/UDP

Unencrypted SIP. Default port; can be changed or disabled (see Signaling
Settings).

5061

TCP

SIP TLS. Default port; can be changed (see Signaling Settings).

8443

TCP

HTTPS. RealPresence Platform Director API communication.

8443

TCP

HTTPS. Hourly transmission of system usage data to the address
customerusagedatacollection.polycom.com. This data is only sent if the
Automatically Send Usage Data feature is enabled (see Automatically
Send Usage Data).

8444

TCP

Supercluster communication.

8989

TCP

OpenDJ replication (superclustering).

36000-61000

TCP

Ephemeral port range.

Polycom, Inc.

Polycom® RealPresence DMA® 7000 System Overview

Polycom Solution Support
Polycom Implementation and Maintenance services provide support for Polycom solution components only.
Additional services for supported third-party Unified Communications (UC) environments integrated with
Polycom solutions are available from Polycom Global Services and its certified Partners. These additional
services will help customers successfully design, deploy, optimize, and manage Polycom visual
communications within their UC environments.
Professional Services for Microsoft Integration is mandatory for Polycom Conferencing for Microsoft Outlook
and Microsoft Office Communications Server or Lync Server 2010 integrations. For more information,
please visit www.polycom.com/services/professional_services/ or contact your local Polycom
representative.

Working in the Polycom RealPresence DMA System
This section includes some general information you should know when working in the Polycom
RealPresence DMA system.

Accessing the Polycom RealPresence DMA System
The Polycom RealPresence DMA system’s management interface is accessed by pointing a compatible
browser equipped with Adobe® Flash® Player to the system’s host name or IP address (a two-server cluster
or an IPv6-only single-server cluster has a virtual host name and IP address, and we strongly recommend
always using the virtual address). Minimum requirements:
● Microsoft Internet Explorer® 7 or newer, or Mozilla Firefox® 3 or newer, or Google Chrome 11 or
newer
● Adobe Flash Player 9.0.124 or newer
● 1280x1024 minimum display resolution (1680x1050 or greater recommended)
Note: Adobe Flash Player considerations
The Polycom RealPresence DMA system’s Flex-based management interface requires Adobe Flash
Player. For stability and security reasons, we recommend always using the latest version of Flash
Player.
Even so, be aware that your browser’s Flash plugin may hang or crash from time to time. Your
browser should alert you when this happens and enable you to reload the plugin. In some cases, you
may need to close and restart your browser.
In the Google Chrome browser, use the Adobe Flash plugin, not the built-in Flash support.

Field Input Requirements
While every effort was made to internationalize the Polycom RealPresence DMA system, not all system
fields accept Unicode entries. If you work in a language other than English, be aware that some fields accept
only ASCII characters.
For input fields that accept a SIP URI, the supported characters for the “userinfo” portion of the URI include:
● Alpha: a-z, A-Z

Polycom, Inc.

Polycom® RealPresence DMA® 7000 System Overview

● Numeric: 0-9
● Escaped: %XX where X=0-9,A-F,a-f
● Other: -_!~*’();:&=+$,
This character support adheres to the full SIP specification.
For input fields that accept an H.323 alias, the supported characters include:
● All ASCII characters in the ranges %x21-24,%x26-3F,%x41-7f
● % @ and values < %x21 can be escaped.
● Escaped: %XX
This character support adheres to the full H.323specification.

Settings Dialog
The Settings dialog opens when you click the
button to the right of the menus. It displays your user
name and the address of the RealPresence DMA server you’re logged in to.
The Settings dialog lets you change:
● The maximum number of columns in the Dashboard. Note that this is a maximum, not a fixed value.
The panes have a minimum width, and they arrange themselves to best fit your browser window.
Depending on the size of your browser window, there may be fewer columns than the maximum you
select. For instance, at the minimum supported display resolution of 1280x1024, only two columns
can be displayed.
● The text size used in the system interface. Note that larger text sizes will affect how much you can
see in a given window or screen size and may require frequent scrolling.

Polycom RealPresence DMA System User Roles and Their Access
Privileges
The Polycom RealPresence DMA system has three system user roles (see User Roles Overview) that
provide access to the management and operations interface and, if available, the separately licensed
RealPresence Platform Application Programming Interface (API). The functions you can perform and parts
of the interface you can access depend on your user role or roles, as shown in the following table.
For information on access privileges to API resources, go to Help > RealPresence Platform API
Documentation in the system’s web interface.
Menu/Icon

Admin

Provisioner

Auditor

•

Active Calls

•

Endpoints

•

DMAs 1

•

- Home. Returns to the Dashboard.
Network >

Polycom, Inc.

Polycom® RealPresence DMA® 7000 System Overview

Menu/Icon

Admin

Provisioner

Auditor

MCU > MCUs1

•

MCU > MCU Pools1

•

MCU > MCU Pool Orders1

•

Site Statistics1

•

Site Link Statistics1

•

Site Topology > Sites1

•

Site Topology > Site Links1

•

Site Topology > Site-to-Site Exclusions1

•

Site Topology > Network Clouds1

•

Site Topology > Territories1

•

External Gatekeeper1

•

External SIP Peer1

•

External H.323 SBC1

•

Users 2

•

Groups

•

Change Password

•

Alert History

•

Call History

•

Conference History

•

Registration History

•

Network Usage

•

Microsoft Active Directory Integration3

•

Enterprise Passcode Errors3

•

Orphaned Groups and Users

•

Conference Room Errors3

•

User >

Reports >

Polycom, Inc.

•

Polycom® RealPresence DMA® 7000 System Overview

Menu/Icon

Admin

Provisioner

Auditor

Maintenance
System Log Files4

•

Troubleshooting Utilities > Ping, Traceroute, Top, I/O
Stats, SAR, NTP Status, Check Configuration
Synchronization

•

Shutdown and Restart

•

Software Upgrade

•

Backup and Restore

•

Admin > Conference Manager >
Conference Settings

•

Conference Templates

•

IVR Prompt Sets

•

Shared Number Dialing

•

Admin > Call Server >
Call Server Settings

•

Domains

•

Dial Rules

•

Hunt Groups

•

Registration Policy

•

Device Authentication

•

Prefix Service1

•

Embedded DNS

•

History Retention Settings

•

Admin > Integrations >
Microsoft Active Directory

•

Microsoft Exchange Server

•

RealPresence Resource Manager

•

Juniper Networks SRC

•

Polycom, Inc.

Polycom® RealPresence DMA® 7000 System Overview

Menu/Icon

Admin

Provisioner

Auditor

Admin > Login Policy Settings >
Local Password

•

Session

•

Local User Account

•

Banner

•

Access Policy Settings

•

Admin > Local Cluster >
Network Settings

•

Signaling Settings

•

Time Settings

•

Licenses

•

Logging Settings

•

SNMP Settings

•

Security Settings

•

Certificates

•

About DMA 7000

•

Help Contents

•

- Log Out. Logs you out of the Polycom RealPresence DMA
system.

•

- Help. Opens the online help topic for the page you’re
viewing.

•

Help >

- Settings. Displays Settings dialog.

1. Provisioners have view-only access.
2. Must be an enterprise user to see enterprise users. Provisioners can’t add or remove roles or endpoints,
and can’t edit user accounts with explicitly assigned roles (Administrator, Provisioner, or Auditor), but can
manage their conference rooms.
3. Must be an enterprise user to view this report.
4. Administrators can’t delete log archives.

Polycom, Inc.

Polycom® RealPresence DMA® 7000 System Overview

Open Source Software
License Information
Refer to the Polycom RealPresence DMA 7000 System Offer of Open Source Software for a list of the open
source software packages used in the Polycom RealPresence DMA system, the applicable license for each,
and the internet address where you can find it. To obtain the source code for any of these packages, e-mail
your request to Open.Source@Polycom.com.

Modifying Open Source Code
The Polycom RealPresence DMA system software is not combined with or otherwise linked to any open
source libraries, but the CentOS software is. The LGPL v2.1 license allows you to modify the LGPL code
included with CentOS, recompile the modified code, and re-link it with the CentOS code. Note that although
you’re free to modify the included LGPL modules in any way you wish, we cannot be responsible if the
changes you make impair the system.

To replace an LGPL library with your modified version
1 Obtain the source code for the module you want to modify.
2 Modify the source code and compile it.
3 Go to Admin > Local Cluster > Security Settings, select Allow Linux console access, and click
Update.
4 Contact Polycom Global Services for the root password for the Polycom RealPresence DMA server.
5 Use ssh to log into the server as root.
6 Upload the modified software via wget or scp.
7 Find the module you’re replacing and install the new version to that location.
8 Reboot the system.

Polycom, Inc.

Polycom RealPresence DMA System
Initial Configuration Summary
This section describes the configuration tasks required to complete your implementation of a new Polycom®
RealPresence® Distributed Media Application™ (DMA®) 7000 system once installation and initial network
configuration are complete.
This section assumes you’ve completed the server configuration procedure in the Getting Started Guide
(available at support.polycom.com), logged in to the Polycom RealPresence DMA system’s management
interface, and verified that the Supercluster Status pane of the Dashboard shows (for a two-server
configuration) two servers in the cluster, with healthy enterprise and private network status for both.
Initial configuration includes the following topics:

System configuration
● Add Required DNS Records for the Polycom RealPresence DMA System
● License the Polycom RealPresence DMA System
● Set Up Signaling
● Configure the Call Server and Optionally Create a Supercluster
● Set Up Security
● Set Up MCUs
● Connect to Microsoft Active Directory®
● Set Up Conference Templates

Confirming configuration
● Test the System
Each topic describes the task, provides background and overview information for it, and where appropriate,
links to specific step-by-step procedures to follow in order to complete the task.
Note: Optional configuration tasks
These topics outline the configuration tasks that are generally required. You may wish to complete
other optional configuration tasks, including:
• Enable cascading of conferences (see About Cascading).
• Configure calendaring service (see Microsoft Exchange Server Integration).
Integrate with a Juniper Networks SRC Series Session and Resource Control module to provide
bandwidth assurance services (see Juniper Networks SRC Integration).

Polycom, Inc.

Polycom RealPresence DMA System Initial Configuration Summary

Add Required DNS Records for the Polycom
RealPresence DMA System
Note: Consult an expert
If you’re not familiar with DNS administration, the creation of various kinds of DNS resource records
(A/AAAA,NAPTR, NS, and SRV), your enterprise’s DNS implementation, and tuning for load
balancing (if needed), please consult with someone who is.

Your Polycom RealPresence DMA system must be accessible by its host name(s), not just its IP
address(es), so you (or your DNS administrator) must create A and/or AAAA records for IPv4 and IPv6,
respectively, as well as the corresponding PTR records, on your DNS server(s).
A/AAAA records and PTR records that map each physical host name to the corresponding physical IP
address and each virtual host name to the corresponding virtual IP address are mandatory, as are the
corresponding PTR records that allow reverse DNS resolution of the system’s physical or virtual host
name(s).
Note: Fully qualified domain names
Depending on local DNS configuration, a host name could be the Polycom RealPresence DMA
system’s fully qualified domain name (FQDN) or a shorter name that DNS can resolve.
For some features, such as Microsoft Exchange Server integration, it’s imperative that the FQDN can
be resolved in DNS, especially by the Exchange server.

The DNS server(s) should also have entries for your Microsoft® Active Directory® server (if different from
the DNS server) and any external gatekeepers or SIP peers.
You may need to create additional DNS records as described below.

Additional DNS Records for SIP Proxy
To support the use of your Polycom RealPresence DMA system as a SIP proxy server and ease future
network administrative burdens, create the following DNS records (for each cluster in a supercluster, if
applicable):
● Optionally, NAPTR records that describe the transport protocols supported by the SIP proxies at a
domain and identify the preferred protocol. Configure these statically to match the system’s SIP
transport protocol configuration.

Polycom, Inc.

Polycom RealPresence DMA System Initial Configuration Summary

● SRV records for each transport protocol that identify the host names of the SIP proxies that service
a particular domain. Configure these statically to point to the host names of the Call Servers in the
domain. Here are example records for two clusters:

_sips._tcp.example.com.
_sips._tcp.example.com.
_sip._tcp.example.com.
_sip._tcp.example.com.
_sip._udp.example.com.
_sip._udp.example.com.

86400
86400
86400
86400
86400
86400

IN
IN
IN
IN
IN
IN

SRV
SRV
SRV
SRV
SRV
SRV

10
10
20
20
30
30

1001
1002
1001
1002
1001
1002

5061
5061
5060
5060
5060
5060

dma-asia.example.com.
dma-europe.example.com.
dma-asia.example.com.
dma-europe.example.com.
dma-asia.example.com.
dma-europe.example.com.

To enable access from the public internet, create corresponding SRV records, visible from outside the
firewall, for the public address of each SIP session border controller (SBC).
For more information about the use of DNS in SIP, refer to RFCs 3263 and 2782.

Additional DNS Records for the H.323 Gatekeeper
To support the use of your Polycom RealPresence DMA system as an H.323 gatekeeper and ease future
network administrative burdens, create SRV records that identify the host names of the gatekeepers that
service a particular domain. These records are necessary in order to enable the optional inbound URL
dialing feature. Configure them statically to point to the host names of the Call Servers in the domain. Here
are example records for two clusters:

_h323ls._udp.example.com.
_h323ls._udp.example.com.
_h323cs._tcp.example.com.
_h323cs._tcp.example.com.

86400
86400
86400
86400

IN
IN
IN
IN

SRV
SRV
SRV
SRV

0
0
0
0

1
1
1
1

1719
1719
1720
1720

dma-asia.example.com.
dma-europe.example.com.
dma-asia.example.com.
dma-europe.example.com.

To enable access from the public internet, create corresponding SRV records, visible from outside the
firewall, for the public address of each H.323 session border controller (SBC).
For more information about the use of DNS in H.323, refer to the H.323 specification, Annex O, and the
H.225.0 specification, Appendix IV.

Additional DNS Records for the Optional Embedded DNS Feature
To support DNS publishing by your Polycom RealPresence DMA system’s embedded DNS servers (see
Embedded DNS), a DNS NS record is needed for the physical host name of each server in each cluster in
the supercluster. These records identify the Polycom RealPresence DMA system’s embedded DNS servers
as authoritative for the specified logical host name. The logical host name you specify is the one in the Call
server sub-domain controlled by RealPresence DMA field on the Embedded DNS page. Here are
example records for two dual-server clusters:
callservers.example.com.
callservers.example.com.
callservers.example.com.
callservers.example.com.
Polycom, Inc.

86400
86400
86400
86400

IN
IN
IN
IN

NS
NS
NS
NS

dma-asia-server1.example.com.
dma-asia-server2.example.com.
dma-europe-server1.example.com.
dma-europe-server2.example.com.
29

Polycom RealPresence DMA System Initial Configuration Summary

Note: Virtual host names cannot have NS records
NS records for the virtual host names must not exist.

Your enterprise DNS must also have the zone callservers.example.com defined and be configured to
forward requests for names in that zone to any of the clusters in the supercluster. The way you do this
depends on the DNS server software being used.
Queries to the enterprise DNS for callservers.example.com are referred to the specified RealPresence DMA
clusters. Their embedded DNS servers create and manage A records for each site in the site topology.
When responsibility for a site moves from one cluster to another, the A records are updated so that the site’s
domain name is mapped to the new cluster.

Verify That DNS Is Working for All Addresses
To confirm that DNS can resolve all the host names and/or FQDNs, ping each of them, either from a
command prompt on the PC you’re using to access the system or from one of the clusters you’re setting up
(go to Troubleshooting Utilities > Ping).
If you have access to a Linux PC and are familiar with the dig command, you can use it to query the
enterprise DNS server to verify that all the records (A/AAAA, NS, and SRV) are present and look correct.

License the Polycom RealPresence DMA System
A Polycom RealPresence DMA system is licensed at the cluster level (single-server or two-server). A
cluster’s license specifies:
● The maximum number of concurrent calls that can touch the cluster. In a supercluster configuration,
note that:
 A single call may touch more than one cluster. It consumes a license on each cluster it touches.
 Each cluster may be licensed for a different number of calls.
 If your superclustering strategy (see About Superclustering) calls for a cluster to be primary for
one territory and backup for another, it must be licensed for the call volume expected when it has
to take over the territory for which it’s the backup.
● Whether access to the RealPresence® Platform Application Programming Interface (API) is enabled.
The API provides an API client application with programmatic access to the Polycom RealPresence
DMA system (see RealPresence® Platform API). In a supercluster, all clusters must have the same
API licensing status.
Note: API licenses
An API license isn’t required in order for a Polycom RealPresence Resource Manager system to
access the API. It’s only needed for a client application that you or a third party develop.

License the RealPresence DMA System, Appliance Edition

Polycom, Inc.

Polycom RealPresence DMA System Initial Configuration Summary

You should have received either one or two license numbers for each cluster, depending on whether you
ordered a single-server or two-server cluster. You must obtain an activation key code for each server from
the Polycom Resource Center (PRC):
1 Enter the server’s serial number and the license number that you were given for that server.
The PRC generates an activation key for that server.
2 For a two-server cluster, repeat the process using the other server’s serial number and its license
number.
3 On the Licenses page of the RealPresence DMA system, install the activation keys to activate the
licenses for your system (see Licenses).
Caution: Do not generate both activation keys from the same physical server
An activation key is linked to a specific server’s serial number. For a two-server cluster, you must
generate the activation key for each server using that server’s serial number. Licensing will fail if you
generate both activation keys from the same server serial number.

License the RealPresence DMA System, Virtual Edition
The RealPresence DMA Virtual Edition is deployed and licensed through Polycom RealPresence Platform
Director. You can view the licensing information for your system from the RealPresence DMA system user
interface on the Admin > Local Cluster > Licenses page.
See the RealPresence Platform Director System Administrator’s Guide for more information.
Note: Local cluster not supported with virtual edition
The RealPresence DMA Virtual Edition does not support a two-server local cluster configuration.
However, superclustering of individual RealPresence DMA Virtual Edition instances is fully supported
in a virtual environment.

Set Up Signaling
Signaling setup includes configuring the following options:
● Enable H.323 signaling so that the Polycom RealPresence DMA system’s Call Server operates as a
gatekeeper, which may include:
 Enable gatekeeper discovery via H.323 multicast.
 Enable and configure H.235 device authentication.
● Enable SIP signaling so that the Polycom RealPresence DMA system’s Call Server operates as a
SIP registrar and proxy server, which may include:
 Configure whether to support unencrypted SIP and whether to require mutual authentication
(validation of client certificates).
 Enable pass-through of ANAT signaling (RFC 4091 and RFC 4092).
 Enable and configure SIP digest authentication.
 Enable and configure special handling for untrusted (“unauthorized” or “guest”) calls from SIP
session border controllers (SBCs).
To set up signaling, follow the procedure in Configure Signaling.

Polycom, Inc.

Polycom RealPresence DMA System Initial Configuration Summary

Configure the Call Server and Optionally Create a
Supercluster
Configuring the Polycom RealPresence DMA system’s Call Server function consists of the following
high-level tasks:
1 Integrate with a Polycom RealPresence Resource Manager or CMA system (see RealPresence
Resource Manager Integration) or enter site topology information (see Site Topology).
2 If deploying a supercluster of multiple geographically distributed Polycom RealPresence DMA
clusters:
a Set the Security Configuration page security options before superclustering (see Security
Settings). But wait until after superclustering to do the rest of the security setup tasks.
b Depending on security settings, you may need to install certificates before superclustering (see
Certificate Procedures).
c Create a supercluster (see About Superclustering) and configure supercluster options.
3 Create territories and assign sites to them (if you integrated with a Polycom RealPresence
Resource Manager or CMA system, this must be done on that system). Assign the primary and
backup cluster responsible for each territory, and designate which territories can host conference
rooms (see Territories).
4 Add any external devices, such as a neighbor gatekeeper or SIP peer (see Call Server
Configuration).
5 Configure the dial plan (see Dial Rules).

Set Up Security
The first step in securing your Polycom RealPresence DMA system is to locate it in a secure data center
with controlled access, but that topic is beyond the scope of this document.
Secure setup of the Polycom RealPresence DMA system consists of the following high-level tasks (some
of which assume you’re integrating with Active Directory and some of which overlap with other initial setup
topics):
1 As the default local administrative user (admin), create a local user account for yourself with the
Administrator role, log in using that account, and delete the admin user account. See Adding Users
Overview and Users Procedures.
2 Create the Active Directory service account (read-only user account) that the Polycom
RealPresence DMA system will use to read and integrate with Active Directory. See Active Directory
Integration Procedure.
3 Assign the Administrator role to your named enterprise account, and remove the Polycom
RealPresence DMA system’s user roles (see User Roles Overview) from the service account used
to integrate with Active Directory. See Connect to Microsoft Active Directory® and Microsoft Active
Directory® Integration.
4 Log out and log back in using your enterprise user ID and password.
5 Verify that the expected enterprise users are available in the Polycom RealPresence DMA system
and that conference room IDs were successfully created for them. If necessary, adjust integration
settings and correct errors. See Microsoft Active Directory® Integration, Users Procedures, and
Conference Room Errors Report.

Polycom, Inc.

Polycom RealPresence DMA System Initial Configuration Summary

6 Obtain and install a security certificate from a trusted certificate authority. See Security Certificates
Overview and Certificate Procedures.
7 Configure as needed various login policy settings (see Login Policy Settings) and optionally, a
management access whitelist (see Access Policy Settings).
8 Document your current configuration for comparison in the future. We recommend saving screen
captures of all the configuration pages.
9 Manually create a backup, download it, and store it in a safe place. See Backing Up and Restoring.

Set Up MCUs
Note: MCUs and RealPresence DMA system interaction
The Polycom RealPresence DMA system can interact with MCUs, or media servers, in either or both
of the following two ways:
• MCUs may be made available to system’s Conference Manager to manage for multi-point
conferencing (hosting virtual meeting rooms, or VMRs).
• MCUs may be registered with the system’s Call Server as standalone MCUs and/or gateways.
This configuration summary assumes you want to do both.

Make sure your MCUs are configured to accept encrypted (HTTPS) management connections (required for
maximum or high security mode).
Make sure that each MCU is in a site belonging to a territory for which the Polycom RealPresence DMA
system is responsible. If you’re deploying a supercluster (see Configure the Call Server and Optionally
Create a Supercluster and About Superclustering), make sure that each territory has a primary and backup
cluster assigned to it. If the primary cluster becomes unavailable, the MCUs registered to it can re-register
to the backup.
If you’re deploying a supercluster, verify that you’ve enabled the hosting of conference rooms in the right
territories and assigned clusters to those territories. See Configure the Call Server and Optionally Create a
Supercluster.
Standalone MCUs can register themselves to the Polycom RealPresence DMA system’s Call Server. To
make an MCU available as a conferencing resource, either add it to the appropriate Polycom RealPresence
DMA cluster’s Conference Manager manually or, if it’s already registered with the Call Server, edit its entry
to enable it for conference rooms and provide the additional configuration information required. See MCU
Management.
You must organize MCUs configured as conferencing resources into one or more MCU pools (logical
groupings of media servers). Then, you can define one or more MCU pool orders that specify the order of
preference in which MCU pools are used.

Polycom, Inc.

Polycom RealPresence DMA System Initial Configuration Summary

Note: Resource management and MCU pools
If you have a Polycom RealPresence Resource Manager system that’s going to use the
RealPresence DMA system API to schedule conferences on the RealPresence DMA system’s
conferencing resources (MCU pools), you must create MCU pools and pool orders specifically for the
use of the RealPresence Resource Manager system. The pool orders should be named in such a way
that:
• They appear at the top of the pool order list presented in the RealPresence Resource Manager
system.
• Users of that system will understand that they should choose one of those pool orders.
If the RealPresence Resource Manager system is also going to be used to directly schedule
conferences on MCUs, those MCUs should not be part of the conferencing resources (MCU pools)
available to the RealPresence DMA system.

Every conference room (VMR) is associated with an MCU pool order. The pool(s) to which an MCU belongs,
and the pool order(s) to which a pool belongs, are used to determine which MCU is used to host a
conference. See MCU Pools and MCU Pool Orders for information about how to use pools and pool orders,
as well as the rules that the system uses to choose an MCU for a user.
The Polycom RealPresence DMA system uses conference templates to define the conferencing experience
associated with a conference room or enterprise group. You can create standalone templates
(recommended), setting the conferencing parameters directly in the Polycom RealPresence DMA system,
or link templates to RealPresence® Collaboration Server or RMX conference profiles (see Conference
Templates).
Both methods allow you to specify most conference parameters:
● General information such as line rate, encryption, auto termination, and H.239 settings
● Video settings such as mode (presentation or lecture) and layout
● IVR settings
● Conference recording settings
If you want to create RealPresence DMA system templates linked to conference profiles on the
RealPresence Collaboration Server or RMX MCUs, make sure the profiles used by the Polycom
RealPresence DMA system exist on all the MCUs and are defined the same on all of them.

Connect to Microsoft Active Directory®
Connecting to Microsoft® Active Directory® simplifies the task of deploying conferencing to a large
organization. All Polycom RealPresence DMA system access to the Active Directory server is read-only and
minimally impacts the directory performance. See Microsoft Active Directory® Integration.
Note: Consult an expert
If you’re not knowledgeable about enterprise directories in general and your specific implementation in
particular, please consult with someone who is. Active Directory integration is a non-trivial matter.

Before integrating with Active Directory, be sure that one or more DNS servers are specified (this should
have been done during installation and initial setup). See Network Settings.

Polycom, Inc.

Polycom RealPresence DMA System Initial Configuration Summary

If you’re deploying a supercluster of multiple geographically distributed Polycom RealPresence DMA
clusters, verify that you’ve assigned clusters to the territories in your site topology (see Configure the Call
Server and Optionally Create a Supercluster) and decide which cluster is to be responsible for Active
Directory integration.
Active Directory integration automatically makes the enterprise users (directory members) into
Conferencing Users in the Polycom RealPresence DMA system, and can assign each of them a conference
room (virtual meeting room, or VMR). The conference room IDs are typically generated from the enterprise
users’ phone numbers.
Note: Manually add conference rooms
Creating conference rooms for enterprise users is optional. If you want to integrate with Active
Directory to load user and group information into the Polycom RealPresence DMA system, but don’t
want to give all users the ability to host conferences, you can do so. You can manually add conference
rooms for selected users at any time. See Conference Rooms Procedures.

Once the Polycom RealPresence DMA system is integrated with Active Directory, it reads the directory
information nightly, so that user and group information is updated automatically as people join and leave the
organization. The system caches certain data from Active Directory. In a superclustered system, one cluster
is responsible for updating the cache, which is shared with all the clusters.
Between updates, clusters access the directory only to authenticate passwords (for instance, for
management interface login); all other user information (such as user search results) comes from the cache.
You can manually update the cache at any time.
Enterprise groups can have their own conference templates that provide a custom conferencing experience
(see Conference Templates). They can also have their own MCU pool order, which preferentially routes
conferences to certain MCUs (see MCU Pool Orders).
You can assign Polycom RealPresence DMA system roles to an enterprise group, applying the roles to all
members of the group and enabling them to log into the Polycom RealPresence DMA system’s
management interface with their standard network user names and passwords.
See User Roles Overview, Groups, and Enterprise Groups Procedures.
There are security concerns that need to be addressed regarding user accounts, whether local or
enterprise. See the high-level process described in Set Up Security.

Set Up Conference Templates
The Polycom RealPresence DMA system uses conference templates and global conference settings to
manage system and conference behavior, and it has a default conference template and default global
conference settings.
After you’ve added MCUs to the system, you may want to change the global conference settings or create
additional templates that specify different conference properties.
If you integrate with Active Directory, you can use templates to provide customized conferencing
experiences for various enterprise groups.
When you add a custom conference room to a user (either local or enterprise), you can choose which
template that conference room uses.

Polycom, Inc.

Polycom RealPresence DMA System Initial Configuration Summary

To add conference templates, see Conference Templates Procedures. To change conference settings, see
Conference Settings. To customize the conferencing experience for an enterprise group, see Enterprise
Groups Procedures.

Test the System
On the Signaling Settings page (see Signaling Settings), verify that:
● If you enabled H.323, the H.323 Signaling Status section indicates that the signaling status is Active
and the port assignments are correct.
● If you enabled SIP, the SIP Signaling Status section shows that the correct protocols and listening
ports are enabled.
Have some endpoints register with the Polycom RealPresence DMA Call Server and make point-to-point
calls to each other.
On the Dashboard (see Dashboard), verify that:
● The information in the Cluster Info pane looks correct, including the time, network settings, and
system resource information.
● The Supercluster Status pane shows the correct number of servers and clusters, and the network
interfaces that should be working (depending on your IP type and split network settings) are up (green
up arrow) and in full duplex mode, with the speed correct for your enterprise network.
● The Call Server Registrations pane shows that the endpoints that attempted to register did so
successfully.
● The Call Server Active Calls pane shows that the endpoints that made calls did so successfully, and
the call limits per cluster and total are correct for your licenses.
● The Conference Manager MCUs pane shows that the MCUs you added are connected and in
service.
● The information on the Active Directory Integration pane looks correct, including the status, cache
refresh data, and enterprise conference room count.
Set up some multipoint conferences by having endpoints dial into enterprise users’ conference rooms
(preferably including a custom conference room). Verify that conferencing works satisfactorily, that the
system status is good, and that the Conference Manager Usage pane accurately presents the status.
When you’re satisfied that the Polycom RealPresence DMA system is configured and working properly,
manually create a backup, download it, and store it in a safe place. See Backing Up and Restoring.

Polycom, Inc.

System Security

This section describes the following Polycom® RealPresence® Distributed Media Application™ (DMA®)
7000 system security topics:
● Security Certificates Overview
● Certificate Settings
● Certificate Procedures
● Security Settings
● The Consequences of Enabling Maximum Security Mode
● Login Policy Settings
● Reset System Passwords

Security Certificates Overview
How Certificates Work
X.509 certificates are a security technology that assists networked computers in determining whether to
trust each other.
● A single, centralized certificate authority (CA) is established. Typically, this is either an enterprise’s IT
department or a commercial certificate authority.
● Each computer on the network is configured to trust the central certificate authority.
● Each server on the network has a public certificate that identifies it.
● The certificate authority signs the public certificates of those servers that clients should trust.
● When a client connects to a server, the server shows its signed public certificate to the client. Trust
is established because the certificate has been signed by the certificate authority, and the client has
been configured to trust the certificate authority.

Forms of Certificates Accepted by the Polycom RealPresence DMA
System
X.509 certificates come in several forms (encoding and protocol). The following table shows the forms that
can be installed in the Polycom RealPresence DMA system.

Polycom, Inc.

System Security

Encoding

Protocol /
File Type

PEM (Base64-encoded
ASCII text)

PKCS #7 protocol
P7B file

Certificate chain containing:
• A signed certificate for the system, authenticating its
public key.
• The CA’s public certificate.
• Sometimes intermediate certificates.
Upload file or paste into text box.

CER (single certificate)
file

Signed certificate for the system, authenticating its
public key.
Upload file or paste into text box.

Certificate text

Encoded certificate text copied from CA’s email or
secure web page.
Paste into text box.

PKCS #12 protocol
PFX file

Certificate chain containing:
• A signed certificate for the system, authenticating its
public key.
• A private key for the system.
• The CA’s public certificate.
Upload file.

PKCS #7 protocol
P7B file

Certificate chain containing:
• A signed certificate for the system, authenticating its
public key.
• The CA’s public certificate.
• Sometimes intermediate certificates.
Upload file.

CER (single certificate)
file

Signed certificate for the system, authenticating its
public key.
Upload file.

DER
(binary format using ASN.1
Distinguished Encoding
Rules)

Description and Installation Method

How Certificates Are Used by the Polycom RealPresence DMA System
The Polycom RealPresence DMA system uses X.509 certificates in the following ways:
1 When a user logs into the Polycom RealPresence DMA system’s browser-based management
interface, the Polycom RealPresence DMA system (server) offers an X.509 certificate to identify
itself to the browser (client).
The Polycom RealPresence DMA system’s certificate must have been signed by a certificate
authority (see Certificate Procedures).
The browser must be configured to trust that certificate authority (beyond the scope of this
documentation).
If trust can’t be established, most browsers allow connection anyway, but display a dialog to the user,
requesting permission.

Polycom, Inc.

System Security

2 When the Polycom RealPresence DMA system connects to a Microsoft Active Directory server, it
may present a certificate to the server to identify itself.
If Active Directory is configured to require a client certificate (this is not the default), the Polycom
RealPresence DMA system offers the same SSL server certificate that it offers to browsers
connecting to the system management interface. Active Directory must be configured to trust the
certificate authority, or it rejects the certificate and the connection fails.
3 When the Polycom RealPresence DMA system connects to a Microsoft Exchange server (if the
calendaring service is enabled; see Microsoft Exchange Server Integration), it may present a certificate
to the server to identify itself.
Unless the Allow unencrypted calendar notifications from Exchange server security option is
enabled (see Security Settings), the Polycom RealPresence DMA system offers the same SSL server
certificate that it offers to browsers connecting to the system management interface. The Microsoft
Exchange server must be configured to trust the certificate authority. Otherwise, the Microsoft
Exchange Server integration status (see Dashboard) remains Subscription pending indefinitely, the
Polycom RealPresence DMA system does not receive calendar notifications, and incoming meeting
request messages are only processed approximately every 4 minutes.
4 When the Polycom RealPresence DMA system connects to a RealPresence Collaboration Server or
RMX MCU configured for secure communications (this is not the default), a certificate may be used
to identify the MCU (server) to the Polycom RealPresence DMA system (client).
5 When performing call signaling requiring TLS, the Polycom RealPresence DMA system presents its
certificate to the connecting client (one-way TLS). If the Require mutual authentication
(validation of client certificates) SIP Settings option is enabled (see Signaling Settings), the
system uses the installed CA certificates to authenticate the connecting client’s certificate as well
(mutual TLS).

Polycom, Inc.

System Security

Frequently Asked Questions
Q. Is it secure to send my certificate request through email?
A. Yes. The certificate request, signed certificate, intermediate certificates, and authority certificates
that are sent through email don’t contain any secret information. There is no security risk in letting
untrusted third parties see their contents.
As a precaution, you can verify the certificate fingerprints (which can be found in the Certificate
Details popup) with the certificate authority via telephone. This ensures that a malicious third party
didn’t substitute a fake email message with fake certificates.
Q. Why doesn’t the information on the Certificate Details popup match the information that I filled out
in the signing request form?
A. Commercial certificate authorities routinely replace the organizational information in the certificate
with their own slightly different description of your organization.
Q. I re-installed the Polycom RealPresence DMA system software. Why can’t I re-install my signed
public certificate?
A. X.509 certificates use public/private key pair technology. The public key is contained in your public
certificate and is provided to any web browser that asks for it. The private key never leaves the
Polycom RealPresence DMA system.
As part of software installation, the Polycom RealPresence DMA system generates a new
public/private key pair. The public key from your old key pair can’t be used with the new private key.
To re-use your signed public certificate, try restoring from backup. Both the public and private keys
are saved as part of a backup file. Alternatively, if the certificate you want to reinstall is a PKCS#12
certificate, it contains a private key and will replace both the public key and the private key generated
at installation time.
See also:
System Security
Certificate Settings
Certificate Procedures

Polycom, Inc.

System Security

Certificate Settings
The following table describes the fields on the Certificate Settings page.
Column

Description

Enable OCSP

Enables the use of Online Certificate Status Protocol as a means of obtaining the
revocation status of a certificate presented to the system.
If OCSP responder URL is not specified, the system checks the certificate’s
AuthorityInfoAccess (AIA) extension fields for the location of an OCSP responder:
• If there is none, the certificate fails validation.
• Otherwise, the system sends the OCSP request to the responder identified in the
certificate.
If OCSP responder URL is specified, the system sends the OCSP request to that
responder.
The responder returns a message indicating whether the certificate is good, revoked, or
unknown.
If OCSP certificate is specified, the response message must be signed by the specified
certificate’s private key.

OCSP responder URL

Identifies the responder to be used for all OCSP requests, overriding the AIA field
values.
If OCSP certificate is specified, the response message must be signed by the specified
certificate’s private key.

OCSP certificate

Select a certificate to require OCSP response messages to be signed by the specified
certificate’s private key.

Store OCSP
Configuration

Saves the OCSP configuration.

Identifier

Common name of the certificate.

Purpose

Kind of certificate:
• Server SSL is the RealPresence DMA system’s public certificate, which it presents to
identify itself. By default, this is a self-signed certificate, not trusted by other devices.
• Trusted Root CA is the root certificate of a certificate authority that the RealPresence
DMA system trusts.
• Intermediate CA is a CA certificate that trusted root CAs issue themselves to sign
certificate signing requests (reducing the likelihood of their root certificate being
compromised). If the RealPresence DMA system trusts the root CA, then the chain
consisting of it, its intermediate CA certificates, and the server certificate will all be
trusted.

Expiration

Expiration date of certificate.

Polycom, Inc.

System Security

See also:
Security Certificates Overview
Certificate Signing Request Dialog
Add Certificates Dialog
Certificate Details Dialog
Certificate Procedures

Certificate Information Dialog
The Certificate Information dialog appears when you click Create Certificate Signing Request in the
Actions list (if a signing request has already been issued, you’re first asked whether to use the existing one
or create a new one). The following table describes the fields in the dialog.
Field

Description

Common name (CN)

Defaults to the FQDN of the system’s management interface, as defined by the virtual
host name and domain specified on the Network page. Editable.

Signature algorithm

The cryptographic hash algorithm used to sign the CSR. Use SHA256 for maximum
security. Use SHA1 when necessary for interoperability.

Organizational unit (OU)

Subdivision of organization. Specify up to three OUs. Optional.

Organization (O)

Optional.

City or locality (L)

Optional.

State (ST)

Optional.

Country (C)

Two-character country code.

See also:
Security Certificates Overview
Certificate Settings
Certificate Procedures

Certificate Signing Request Dialog
The Certificate Signing Request dialog appears when you create a request in the Certificate Information
dialog.
The Summary section at the top displays the information the Certificate Information dialog.
The Encoded Request box below displays the encoded certificate request text, which you can select and
copy.
See also:
Security Certificates Overview
Certificate Settings
Certificate Procedures

Polycom, Inc.

System Security

Add Certificates Dialog
The Add Certificates dialog appears when you click Add Certificates in the Actions list. It lets you install
signed certificates or certificate chains. You can do so in two ways:
● Upload a PFX, PEM, or P7B certificate file.
● Paste PEM-format certificate text into the dialog.
The following table describes the fields in the dialog.
Field

Description

Upload certificate

If checked, the Password field and Upload file button enable you to upload a PFX,
PEM, or P7B certificate file.

Password

Enter the password, if any, assigned to the certificate file when it was created.

Upload file

Click the button to browse to the file you want to upload.

Paste certificate

If checked, the text field below enables you to paste in the text of PEM certificate files.

See also:
Security Certificates Overview
Certificate Settings
Certificate Procedures

Certificate Details Dialog
The Certificate Details dialog appears when you click Display Details in the Actions list. It displays
information about the certificate selected in the list, as outlined in the following table.
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.

Subject Alternative
Names

Additional identities bound to the subject of the certificate.
For the Polycom RealPresence DMA system, this should include the virtual and physical
FQDNs, short host names, and IP addresses of the system.

Extended Key Usage

Indicates the purposes for which the certificate can be used.
The Polycom RealPresence DMA system’s certificate is used for both server and client
connections, so this should always contain at least serverAuth and clientAuth.

Polycom, Inc.

System Security

See also:
Security Certificates Overview
Certificate Settings

Certificate Procedures
Certificate procedures include the following:
● Install your chosen certificate authority’s public certificate, if necessary, so that the Polycom
RealPresence DMA system trusts that certificate authority.
● Create a certificate signing request to submit to the certificate authority.
● Install a public certificate signed by your certificate authority that identifies the Polycom RealPresence
DMA system.
● Remove a signed certificate or a certificate authority’s certificate.
Note: Obtaining certificates for Microsoft environments
If you’re configuring the Polycom RealPresence DMA system to support Polycom’s solution for the
Microsoft OCS or Lync environment, you can use Microsoft’s Certificate Wizard to request and obtain
a PFX file (a password-protected PKCS12 file containing a private key and public key for the system,
and the CA’s certificate).
Once you have the PFX file, you’re ready to install it.
See Polycom’s solution deployment guide for information about using the Certificate Wizard and other
steps needed to implement the solution.

Install a Certificate Authority’s Certificate
This procedure is not necessary if you obtain a certificate chain that includes a signed certificate for the
Polycom RealPresence DMA system, your certificate authority’s public certificate, and any intermediate
certificates.
Use this procedure to add a trusted certificate authority, either an in-house or commercial CA.
Caution: Installing or removing certificates requires a restart
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.

To install a certificate for a trusted root CA
1 Go to Admin > Local Cluster > Certificates.
The installed certificates are listed. The Trusted Root CA entries, if any, represent the certificate
authorities whose public certificates are already installed on the RealPresence DMA system and are
thus trusted.
Polycom, Inc.

System Security

2 If you’re using a certificate authority that isn’t listed, obtain a copy of your certificate authority’s
public certificate.
The certificate must be either a single X.509 certificate or a PKCS#7 certificate chain. If it’s ASCII
text, it’s in PEM format, and starts with the text -----BEGIN CERTIFICATE-----. If it’s a file, it
can be either PEM or DER encoded.
3 In the Actions list, select Add Certificates.
4 In the Add Certificates dialog, do one of the following:
 If you have a file, click Upload certificate, enter the password (if any) for the file, and browse to
the file or enter the path and file name.
 If you have PEM-format text, copy the certificate text, click Paste certificate, and paste it into the
text box below.
5 Click OK.
6 Verify that the certificate appears in the list as a Trusted Root CA.
7 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.
See also:
Security Certificates Overview
Certificate Settings
Certificate Procedures

Create a Certificate Signing Request in the RealPresence DMA System
The procedure below creates a certificate signing request (CSR) that you can submit to your chosen
certificate authority. This method uses the private key generated at software installation time.

To create a certificate signing request
1 Go to Admin > Local Cluster > Certificates.
By default, the system is configured to use a self-signed certificate.
2 To see details of the public certificate currently being used to identify the system to other computers:
a In the list, select the Server SSL certificate.
b In the Actions list, select Display Details.
The Certificate Details dialog appears. If this is the default self-signed certificate, Organizational
Unit is Self Signed Certificate.
c To close the dialog, click OK.
3 In the Actions list, select Create Certificate Signing Request.
If you’ve created a signing request before, you’re asked if you want to use your existing certificate
request or generate a new one. Elect to generate a new one.
4 In the Certificate Information dialog, enter the identifying information for your Polycom
RealPresence DMA system (see Certificate Information Dialog) and click OK.
The Certificate Signing Request dialog displays the encoded request (see Certificate Signing
Request Dialog).

Polycom, Inc.

System Security

5 Copy the entire contents of the Encoded Request box (including the text -----BEGIN NEW
CERTIFICATE REQUEST----- and -----END NEW CERTIFICATE REQUEST-----) and
submit it to your certificate authority.
Depending on the certificate authority, your CSR may be submitted via email or by pasting into a web
page.
6 Click OK to close the dialog.
When your certificate authority has processed your request, it sends you a signed public certificate
for your Polycom RealPresence DMA system. Some certificate authorities also send intermediate
certificates and/or root certificates. Depending on the certificate authority, these certificates may
arrive as e-mail text, e-mail attachments, or be available on a secure web page.
The Polycom RealPresence DMA system accepts PKCS#7 or PKCS#12 certificate chains or single
certificates.
Caution: Some CSR fields should not be modified
When you submit the CSR to your CA, make sure that the CA doesn’t modify any of the predefined
SAN fields or the X.509v3 Key Usage or Extended Key Usage fields. Changes to these fields may
make your system unusable. Contact Polycom technical support if you have any questions about this.

See also:
Security Certificates Overview
Certificate Settings
Certificate Procedures

Install a Certificate in the RealPresence DMA System
The procedure below installs the certificate or certificate chain provided by the certificate authority. It
assumes that you’ve 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.
Caution: Installing or removing certificates requires a restart
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.

To install a signed certificate that identifies the Polycom RealPresence DMA system
1 When you receive your certificate(s), return to Admin > Local Cluster > Certificates.
2 In the Actions list, select Add Certificates.
3 In the Add Certificates dialog, do one of the following:

Polycom, Inc.

System Security

 If you have a 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.
 If you have PEM-format text, copy the certificate text, click Paste certificate, and paste it into the
text box below. You can paste multiple PEM certificates one after the other.
4 Click OK.
5 To verify that the new signed certificate has replaced the default self-signed certificate:
a In the list of certificates, once again select the Server SSL certificate.
b In the Actions list, select Display Details.
The Certificate Details dialog appears.
c Confirm from the information under Issued To and Issued By that the self-signed default
certificate has been replaced by your signed public certificate from the certificate authority.
d Click OK to close the dialog.
6 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.
See also:
Security Certificates Overview
Certificate Settings
Certificate Procedures

Remove a Certificate from the RealPresence DMA System
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 Server SSL certificate so that the system
reverts to using the default self-signed Server SSL 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.
Both procedures are described below.
Caution: Installing or removing certificates requires a restart
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.

To remove a Trusted Root CA’s certificate
1 Go to Admin > Local Cluster > Certificates.
2 In the certificates list, select the certificate you want to delete.

Polycom, Inc.

System Security

3 In the Actions list, select Display Details and confirm that you’ve selected the correct certificate.
Then click OK.
4 In the Actions list, select Delete Certificate.
5 When asked to confirm, click Yes.
A dialog informs you that the certificate has been deleted.
6 Click OK.
7 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.

To remove a signed certificate and revert to the default self-signed certificate
1 Go to Certificates.
2 In the Actions list, select Revert to Default Certificate.
3 When asked to confirm, click Yes.
A dialog informs you that the system has reverted to a self-signed certificate.
4 Click OK.
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 Admin > Local Cluster > Certificates, and verify
that the system has reverted to the default self-signed certificate:
a In the list of certificates, select the Server SSL certificate.
b In the Actions list, select Display Details.
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 OK to close the dialog.
See also:
Security Certificates Overview
Certificate Settings
Certificate Procedures

Security Settings
The Security Settings page lets you switch between high security mode and a custom security mode in
which one or more insecure capabilities are allowed. It also lets you switch to, but not from, a maximum
security mode.

Polycom, Inc.

System Security

Caution: High security setting recommended
We recommend always using the High security setting unless you have a specific and compelling
need to allow one of the insecure capabilities.
We recommend the Maximum security setting only for those environments where the most stringent
security protocols must be adhered to.
Enabling Maximum security is irreversible and has significant consequences (see The
Consequences of Enabling Maximum Security Mode). Don’t choose this setting unless you know what
you’re doing and are prepared for the consequences. Refer to the Polycom RealPresence DMA 7000
System Deployment Guide for Maximum Security Environments for additional important information
about enabling this setting.

Note: Security settings must match across superclusters
All clusters in a supercluster must have the same security settings. Before attempting to join a
supercluster, make sure the cluster’s security settings match those of the other members of the
supercluster. You can’t change a cluster’s security settings while it’s part of a supercluster.

Note: Maximum security mode unsupported in virtual edition
The RealPresence DMA system, Virtual Edition, does not support Maximum Security Mode.

The following table describes the options in the Security Settings page.
Field

Description

Maximum security

An extremely high security mode suitable for use where very strict security
requirements apply.
Once this mode is enabled, it’s no longer possible to reduce the security level.
See caution above.

High security

Recommended setting for normal operation.

Custom security

Lets you enable one or more of the unsecured methods of network access
listed below it.

Allow Linux console access

Enables the Linux user root to log into the system using SSH. This direct
Linux access isn’t needed for normal operation, routine maintenance, or even
troubleshooting, all of which can be done through the administrative GUI.
In extreme circumstances, this option might enable expert Polycom Global
Services personnel to more fully understand the state of a troubled system or
correct problems. Enable this option only when asked to do so by Polycom
Global Services.

Polycom, Inc.

System Security

Field

Description

Allow unencrypted connections to
the Active Directory

Normally, the Polycom RealPresence DMA system connects to Active
Directory using SSL or TLS encryption. But if the Active Directory server or
servers (including domain controllers if you import global groups) aren’t
configured to support encryption, the Polycom RealPresence DMA system
can only connect using an unencrypted protocol. This option allows such
connections if an encrypted connection can’t be established.
This configuration causes an extreme security flaw: the unencrypted
passwords of enterprise users are transmitted over the network, where they
can easily be intercepted.
Use this option only for diagnostic purposes. By toggling it, you can determine
whether encryption is the cause of a failure to connect to Active Directory or to
load group data. If so, the solution is to correctly configure the relevant
servers, not to allow ongoing use of unencrypted connections.

Allow unencrypted connections to
MCUs

Normally, the Polycom RealPresence DMA system uses only HTTPS for the
conference control connection to RealPresence Collaboration Server or RMX
MCUs, and therefore can’t control an MCU that accepts only HTTP (the
default). This option enables the system to fall back to HTTP for MCUs not
configured for HTTPS.
We recommend configuring your MCUs to accept encrypted connections
rather than enabling this option. When unencrypted connections are used, the
RealPresence Collaboration Server or RMX login name and password are
sent unencrypted over the network.

Allow unencrypted calendar
notifications from Exchange
server

Normally, if calendaring is enabled, the Polycom RealPresence DMA system
gives the Microsoft Exchange server an HTTPS URL to which the Exchange
server can deliver calendar notifications. In that case, the Polycom
RealPresence DMA system must have a certificate that the Exchange server
accepts in order for the HTTPS connection to work.
If this option is selected, the Polycom RealPresence DMA system does not
require HTTPS for calendar notifications.
We recommend installing a certificate trusted by the Exchange server and
using an HTTPS URL for notifications rather than enabling this option.

Allow basic authentication to
Exchange server

Normally, if calendaring is enabled, the Polycom RealPresence DMA system
authenticates itself with the Exchange server using NTLM authentication.
If this option is selected, the Polycom RealPresence DMA system still
attempts to use NTLM first. But if that fails or isn’t enabled on the Exchange
server, then the RealPresence DMA system falls back to HTTP Basic
authentication (user name and password).
We recommend using NTLM authentication rather than enabling this option.
In order for either NTLM or HTTP Basic authentication to work, they must be
enabled on the Exchange server.

Polycom, Inc.

System Security

Field

Description

Skip validation of certificates
received while making outbound
connections

Normally, when the Polycom RealPresence DMA system connects to a
server, it validates that server’s certificate.
This option configures the system to accept any certificate presented to it
without validating it.
We recommend using valid certificates for all servers that the system may
need to contact rather than enabling this option. Depending on system
configuration, this may include:
MCUs
Active Directory
Exchange
RealPresence Resource Manager system
Other RealPresence DMA systems
Endpoints
Note: Either the Common Name (CN) or Subject Alternate Name (SAN) field
of the server’s certificate must contain the address or host name specified for
the server in the Polycom RealPresence DMA system.
Polycom MCUs don't include their management IP address in the SAN field of
the CSR (Certificate Signing Request), so their certificates identify them only
by the CN. Therefore, in the Polycom RealPresence DMA system, a Polycom
MCU's management interface must be identified by the name specified in the
CN field (usually the FQDN), not by IP address.
Similarly, an Active Directory server certificate often specifies only the FQDN.
So in the Polycom RealPresence DMA system, identify the enterprise
directory by FQDN, not by IP address.

Unlock SIP Settings mutual
authentication option on the
Signaling Settings page

Normally, during encrypted call signaling (SIP over TLS), the Polycom
RealPresence DMA system requires the remote party (endpoint or MCU) to
present a valid certificate. This is known as mutual TLS.
When enabled, this check box unlocks the Require mutual authentication
(validation of client certificates) option for SIP signaling on the Signaling
Settings page, allowing you to disable the mutual TLS requirement for SIP
signaling.
Polycom recommends recommend installing valid certificates on your
endpoints and MCUs rather than enabling this option.

Allow non-conference participants
to receive conference events

The SIP SUBSCRIBE/NOTIFY conference notification service (as described
in RFCs 3265 and 4575), allows SIP devices to subscribe to a conference and
receive conference rosters and notifications of conference events. Normally,
the subscribing endpoints are conference participants.
This option configures the system to let devices subscribe to a conference
without being participants in the conference.
Note: A subscription to a conference by a non-participant consumes a call
license. Call history doesn’t include data for non-participant subscriptions.

Polycom, Inc.

System Security

Field

Description

The following settings may be configured in any security mode.
Skip validation of certificates for
inbound connections

This option may be configured in any security mode, and affects inbound
connections from entities like web browsers and API clients.
If this option is turned off, you can only connect to the Polycom RealPresence
DMA system if your browser presents a client certificate issued by a CA that
the system trusts (this is known as mutual TLS for administrative
connections).
Turn this option off only if:
• You’ve implemented a complete public key infrastructure (PKI) system,
including a CA server, client software (and optionally hardware, tokens, or
smartcards), and the appropriate operational procedures.
• The CA’s public certificate is installed in the Polycom RealPresence DMA
system so that it trusts the CA.
• All authorized users, including yourself, have a client certificate signed by
the CA that authenticates them to the Polycom RealPresence DMA
system.

Allow forwarding of IPv6 ICMP
destination unreachable
messages

This option may be configured in any security mode.
If this option is off, the Polycom RealPresence DMA system has an internal
firewall rule that blocks outbound destination unreachable messages.
If this option is on, that firewall rule is disabled.
Note: The Polycom RealPresence DMA system currently doesn’t send such
messages, regardless of this setting.

Allow IPv6 ICMP echo reply
messages to multicast addresses

This option may be configured in any security mode.
If this option is off, the Polycom RealPresence DMA system doesn't reply to
echo request messages sent to multicast addresses (multicast pings).
If this option is on, the system responds to multicast pings.

To change the security settings
1 Go to Admin > Local Cluster > Security Settings.
2 To switch from a custom setting back to the recommended security mode, click High security.
3 To switch from the recommended security mode to a custom setting:
a Click Custom security.
b Check the unsecured network access method(s) that you want to enable.
4 Click Update.
A dialog informs you that the configuration has been updated.
Note: Skip validation of certificates for inbound connections is automatically re-enabled
If you turn off Skip validation of certificates for inbound connections, the system notifies you that
if you don’t log back in within 5 minutes, the setting will be automatically turned back on. This is a
safety precaution to ensure that at least one user is still able to access the system.

5 Click OK.

Polycom, Inc.

System Security

See also:
System Security
Certificate Settings
Login Policy Settings
Reset System Passwords

The Consequences of Enabling Maximum Security
Mode
Enabling the Maximum security setting is irreversible and has the following significant consequences:
● All unencrypted protocols and unsecured access methods are disabled, and the enhanced support
feature is disabled.
● The boot order is changed so that the server(s) can’t be booted from the optical drive or a USB
device.
● A BIOS password is set.
● The port 443 redirect is removed, and the system can only be accessed by the full URL
(https://:8443/dma7000, where is one of the system's management IP addresses or a host
name that resolves to one of those IP addresses).
● For all server-to-server connections, the system requires the remote party to present a valid X.509
certificate. Either the Common Name (CN) or Subject Alternate Name (SAN) field of that certificate
must contain the address or host name specified for the server in the Polycom RealPresence DMA
system.
Polycom RMX MCUs don’t include their management IP address in the SAN field of the CSR
(Certificate Signing Request), so their certificates identify them only by the CN. Therefore, in the
Polycom RealPresence DMA system, an RMX MCU's management interface must be identified by
the host name or FQDN specified in the CN field, not by IP address.
Similarly, an Active Directory server certificate often specifies only the FQDN. Therefore, in the
Polycom RealPresence DMA system, the Active Directory must be identified by FQDN, not by IP
address.
● Superclustering is not supported.
● The Polycom RealPresence DMA system can’t be integrated with Microsoft Exchange Server and
doesn’t support virtual meeting rooms (VMRs) created by the Polycom Conferencing Add-in for
Microsoft Outlook.
● Integration with a Polycom RealPresence Resource Manager system is not supported.
● On the Banner page, Enable login banner is selected and can’t be disabled.
● On the Login Sessions page, the Terminate Session action is not available.
● On the Troubleshooting Utilities menu, Top is removed.
● In the Add User and Edit User dialogs, conference and chairperson passcodes are obscured.
● After Maximum security is enabled, management interface users must change their passwords.
● If the system is not integrated with Active Directory, each local user can have only one assigned role
(Administrator, Provisioner, or Auditor).
If some local users have multiple roles when you enable Maximum security, they retain only the
highest-ranking role (Administrator > Auditor > Provisioner).
Polycom, Inc.

System Security

● If the system is integrated with Microsoft Active Directory, only one local user can have the
Administrator role, and no local users can have the Provisioner or Auditor role.
If there are multiple local administrators when you enable Maximum security, the system prompts
you to choose one local user to retain the Administrator role. All other local users, if any, become
conferencing users only and can’t log into the management interface.
Each enterprise user can have only one assigned role (Administrator, Provisioner, or Auditor). If some
enterprise users have multiple roles (or inherit multiple roles from their group memberships), they
retain only the lowest-ranking role (Administrator > Auditor > Provisioner).
● Local user passwords have stricter limits and constraints (each is set to the noted default if below that
level when you enable Maximum security):
 Minimum length is 15-30 characters (default is 15).
 Must contain 1 or 2 (default is 2) of each character type: uppercase alpha, lowercase alpha,
numeric, and non-alphanumeric (special).
 Maximum number of consecutive repeated characters is 1-4 (default is 2).
 Number of previous passwords that a user may not re-use is 8-16 (default is 10).
 Minimum number of characters that must be changed from the previous password is 1-4 (default
is 4).
 Password may not contain the user name or its reverse.
 Maximum password age is 30-180 days (default is 60).
 Minimum password age is 1-30 days (default is 1).
● Other configuration settings have stricter limits and constraints (each is set to the noted default if
below that level when you enable Maximum security):
 Session configuration limits:
 Sessions per system is 4-80 (default is 40).
 Sessions per user is 1-10 (default is 5).
 Session timeout is 5-60 minutes (default is 10).
 Local account configuration limits:
 Local user account is locked after 2-10 failed logins (default is 3) due to invalid password
within 1-24 hours (default is 1).
 Locked account remains locked either until unlocked by an administrator (the default) or for a
duration of 1-480 minutes.
● Non-conference participants can’t be permitted to register for conference events.
● Software build information is not displayed anywhere in the interface.
● You can’t restore a backup made before Maximum security was enabled.
● The RealPresence DMA system, Virtual Edition, does not support Maximum Security Mode.
● If you’re using the Mozilla Firefox browser, you need to configure it to support TLS version 1.1 so that
it can function correctly with a RealPresence DMA system configured for Maximum Security Mode.
● File uploads may fail when using the Mozilla Firefox browser unless the proper steps have been
taken. See below.

Polycom, Inc.

System Security

Enabling File Uploads in Maximum Security with Mozilla Firefox
The Mozilla Firefox browser uses its own certificate database instead of the certificate database of the OS.
If you use only that browser to access the Polycom RealPresence DMA system, the certificate(s) needed
to securely connect to the system may be only in the Firefox certificate database and not in the Windows
certificate store. This causes a problem for file uploads.
File upload via the Polycom RealPresence DMA system’s Flash-based interface bypasses the browser and
creates the TLS/SSL connection itself. Because of that, it uses the Windows certificate store, not the Firefox
certificate database. If the certificate(s) establishing trust aren’t there, the file upload silently fails.
To avoid this problem, you must import the needed certificates into Internet Explorer (and thus into the
Windows certificate store). And, when accessing the system with Firefox, you must use its fully qualified
host name.
First, start Internet Explorer and point it to the Polycom RealPresence DMA system. If you don’t receive a
security warning, the needed certificates are already in the Windows certificate store.
If you receive a warning, import the needed certificates. The details for doing so depend on the version of
Internet Explorer and on your enterprise’s implementation of certificates. In Internet Explorer 7, elect to
continue to the site. Then click Certificate Error to the right of the address bar and click View Certificates
to open the Certificate dialog. From there, you can access the Certificate Import Wizard.
The entire trust chain must be imported (the system’s signed certificate, intermediate certificates, if any, and
the root CA’s certificate). When importing a certificate, let Internet Explorer automatically select a certificate
store.
See also:
System Security
Security Certificates Overview
Certificate Settings
Security Settings
Reset System Passwords

Login Policy Settings
The following pages, under Admin > Login Policy Settings, let you configure various aspects of user
access to the system:
● Local Password
● Session
● Local User Account
● Banner
● Access Policy Settings
See also:
System Security
Certificate Settings
Security Settings
Reset System Passwords
Polycom, Inc.

System Security

Local Password
The Local Password page lets you increase system security by specifying age, length, and complexity
requirements for the passwords of local administrator, auditor, and provisioner users. These rules don’t
apply to conferencing users’ conference and chairperson passcodes, or to Active Directory users.
The following table describes the fields on the Local Password page.
Field

Description

Password Management
Maximum password age (days)

Specify at what age a password expires (30-180 days).

Minimum password age (days)

Specify how frequently a password can be changed (1-30 days).

Minimum length

Specify the number of characters a password must contain (8-30).

Minimum changed characters

Specify the number of characters that must be different from the previous
password (1-4).

Reject previous passwords

Specify how many of the user’s previous passwords the system remembers
and won’t permit to be reused (8-30).

Password Complexity
Allow user name or its reverse
form

Turns off the protection against a password containing the user’s login name
or its reverse.

Lowercase letters

Specify the number of lowercase letters (a-z) that a password must contain.

Uppercase letters

Specify the number of uppercase letters (A-Z) that a password must contain.

Numbers

Specify the number of digit characters (0-9) that a password must contain.

Special characters

Specify the number of non-alphanumeric keyboard characters that a
password must contain.

Maximum consecutive repeated
characters

Specify how many sequential characters may be the same.

See also:
System Security
Login Policy Settings

Session
The Session page lets you increase system security by limiting the number and length of login sessions.
You can see the current login sessions and terminate sessions by going to User > Login Sessions. See
Login Sessions.
The following table describes the fields on the Session page.

Polycom, Inc.

System Security

Field

Description

Active system sessions

Specify the number of simultaneous login sessions by all users or select
Unlimited.
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.

Active sessions per user

Specify the number of simultaneous login sessions per user ID or select
Unlimited.

Session timeout (minutes)

Specify the length of time after which the system terminates a session for
inactivity or select Unlimited.

See also:
System Security
Login Policy Settings

Local User Account
The Local User Account page lets you increase system security by:
● Locking out users who have exceeded the specified number and frequency of login failures. The
system locks the account either indefinitely or for the length of time you specify.
● Disabling accounts that have been inactive a specified number of days.
The following table describes the fields on the Local User Account page.
Field

Description

Account Lockout
Enable account lockout

Turns on lockout feature and enables lockout configuration fields below.

Failed login threshold

Specify how many consecutive login failures cause the system to lock an
account.

Failed login window (hours)

Specify the time span within which the consecutive failures must occur in
order to lock the account.

Customize user account lockout
duration (minutes)

If selected, specify how long the user’s account remains locked.
If not selected, the lockout is indefinite, and a user with a locked account must
contact an Administrator to unlock it.

Account Inactivity
Customize account inactivity
threshold (days)

Turns on disabling of inactive accounts and lets you specify the inactivity
threshold that triggers disabling.

See also:
System Security
Login Policy Settings

Polycom, Inc.

System Security

Banner
A login banner is a message that appears when users attempt to access the system. They must
acknowledge the message before they can log in.
The Banner page lets you enable the banner and select or create the message it displays. The message
may contain up to 1500 characters. If the system is in Maximum Security mode, the login banner is enabled
and can’t be disabled.
The following table describes the fields on the Banner page.
Field

Description

Enable login banner

Enables the display of a login banner.
If this box is unchecked, the Message field is disabled. The existing contents,
if any, remain unchanged, but aren’t displayed to users.

Message

Select one of the messages from the list, or select Custom and type or paste
your own message into the field below.
If you select one of the built-in samples, it’s copied into the Message field, and
you can then edit the copy. When you do so, the system resets the list to
Custom.
Your edits don’t affect the stored sample. You can revert to the original version
of the sample by re-selecting it from the list.

See also:
System Security
Login Policy Settings

Access Policy Settings
The Access Policy Settings page lets you increase system security by restricting access to the
management and operations interface and APIs (port 8443) and to SNMP (by default, port 161) to a whitelist
of authorized IP addresses or address ranges.
If enabled, the whitelist restrictions take effect as soon as the update operation is completed. If you enable
the whitelist and click Update while logged in from an IP address that’s not included in the whitelist, the
system warns you that you won’t be able to access the system and asks you to confirm the update.
The whitelist settings apply to all clusters in a supercluster. When you join a cluster to a supercluster, the
cluster’s settings are replaced by those from the supercluster.
The following table describes the fields on the Access Policy Settings page.

Polycom, Inc.

System Security

Field

Description

Accept management connections
from these IP addresses and
address ranges on ports 8443
(GUI/API) and 161 (SNMP)

Enables the input field below and restricts management access to the IP
addresses or address ranges added to the list.
If this box is unchecked, the list and input field are disabled. The existing
contents of the list, if any, remain unchanged so that it can be re-enabled at
any time without having to re-enter the addresses.
Note: The label changes to reflect the currently configured SNMP port (see
Configure SNMP). Port 161 is the default.

(list)

Lists the IP addresses and address ranges authorized for management
access. Select an entry and click Delete to remove it from the list.

(input field)

Enter an IP address or address range and click Add. Enter a range as valid
starting and ending IP addresses separated by a dash. For example:
(IPv4) 10.33.33.0 - 10.33.34.255
(IPv6) ::1:fffe - ::2:1

See also:
System Security
Security Settings
The Consequences of Enabling Maximum Security Mode
Login Policy Settings
Reset System Passwords

Reset System Passwords
In an extremely high-security environment, security compliance policies may require that all passwords be
changed at certain intervals, including operating system passwords.
The Reset System Passwords page is available only if the system is in maximum security mode. It lets
you change these operating system passwords (such as the password for grub) to new,
randomly-generated values. These are passwords for logins that aren’t possible on a secure system.
Resetting these operating system passwords has no effect on authorized users of the management
interface (Administrators, Auditors, and Provisioners) or conferencing users.

To reset system passwords
1 Make sure there are no calls or conferences on the system.
2 Go to Admin > Local Cluster > Reset System Passwords.
3 Click Reset Passwords.
The system warns you that active calls and conferences will be terminated and the system will restart,
and asks you to confirm.
4 Click Yes.
The system informs you that the passwords have been reset and that you’re being logged out. Then
it restarts. This takes several minutes.

Polycom, Inc.

System Security

5 Wait a few minutes to log back in.
See also:
System Security
Security Settings
The Consequences of Enabling Maximum Security Mode
Login Policy Settings
Access Policy Settings

Polycom, Inc.

Local Cluster Configuration

This section describes the following Polycom® RealPresence® Distributed Media Application™ (DMA®)
7000 system configuration topics:
● Network Settings
● Time Settings
● Licenses
● Signaling Settings
● Alerting Settings
● Logging Settings
● Local Cluster Configuration Procedures
● Automatically Send Usage Data
These are cluster-specific settings that are not part of the data store shared across superclustered systems.
See Introduction to the Polycom RealPresence DMA System.
If you’re performing the initial configuration of your Polycom RealPresence DMA system, study Polycom
RealPresence DMA System Initial Configuration Summary before you continue.

Network Settings
The following table describes the fields on the Network Settings page. In the Appliance Edition, most of
these values are normally set in the USB Configuration Utility during system installation and rarely need to
be changed. In the Virtual Edition, some of these settings are provisioned automatically when the system is
deployed with RealPresence Platform Director. See the Getting Started Guide and the Getting Started
Guide for a Virtual Environment.

Polycom, Inc.

Local Cluster Configuration

Caution: Network settings changes require a restart
Changing some network settings (host names, IP addresses, or domains) requires a system restart
and terminates all active conferences.
If the system is using a CA-provided identity certificate, changing some network settings (host names
or IP addresses) also requires you to update the certificate. (If the system is using a self-signed
certificate, an updated one is automatically created.)
You can’t change these network settings while the system is part of a supercluster or integrated with a
Polycom RealPresence Resource Manager system. You must first leave the supercluster or terminate
the integration. If the cluster is responsible for any territories (as primary or backup), reassign those
territories. After the change, rejoin the supercluster or Polycom RealPresence Resource Manager
system. See Superclustering or RealPresence Resource Manager Integration.
Incorrect network information may make the system unusable and the management interface
unreachable.

Caution: Configuring the RealPresence DMA system in a secure environment
The 802.1x LAN security settings can’t be configured in the USB Configuration Utility. In a highly
secure network that requires 802.1x authentication, the Polycom RealPresence DMA system won’t be
accessible until those settings are properly configured. To do so, follow the procedure for configuring
the network settings using a laptop, as described in the Deployment Guide for Maximum Security
Environments.

Note: Virtual host name not needed for single-server systems
This version of the Polycom RealPresence DMA system eliminates the need for virtual host name(s)
and IP addresses in a single-server system or cluster. When a version 5.0 or earlier single-server
RealPresence DMA system is upgraded to version 5.1 or later, the previous version's virtual host
name(s) and IP addresses become the upgraded version's physical host name(s) and IP addresses,
so accessing the system doesn't change.
(Exception: If only IPv6 is enabled, the system must have two addresses, so a single-server system
must still have a virtual host name and IP address.)

Field

Description

System IP type

IP addressing supported (IPv4, IPv6, or both).

System server configuration

Number of servers (1 or 2) in this cluster.
Caution: Once this is set to 2 server configuration, it can’t be changed back
to 1 server configuration. To reconfigure a two-server system as two
separate single-server systems, you must use the USB Configuration Utility.
See the Polycom RealPresence DMA 7000 System Getting Started Guide.

Polycom, Inc.

Local Cluster Configuration

Field

Description

System split network setting

Specifies whether to combine or split the system’s management and signaling
interfaces. If the same network will be used for both management
(administrative access) and signaling, the signaling IP addresses and Shared
Signaling Network Settings section below are not used.
Caution: Choose split networking only if you need to restrict access to the
management interface and SNMP to users on an isolated “non-public”
network separate from the enterprise network. Typically, this is the case only
in high-security environments.
In most network environments, users accessing the management interface
are on the same network as endpoints and other devices communicating with
the RealPresence DMA system, and they use the same physical and virtual IP
addresses and the same network interface.
To split the network configuration, you must use different gateways and
subnets for management and signaling, and separate physical connections
for the management and signaling networks (eth0 for management, eth2 for
signaling). In a split network configuration, routing rules are necessary for
proper routing of network traffic. See Routing Configuration Dialog.
If management and signaling traffic are combined on the same network
(subnet), both use the same physical and virtual IP addresses and the same
network interface.
If you aren’t sure whether split networking is appropriate, possible, or
necessary for this installation, consult the appropriate IT staff or network
administrator for your organization.
In a split network configuration, routing rules are necessary for proper routing
of network traffic.

Server 1

Status, host name, and IP address(es) of the primary server. The IP type and
network setting determine which of the IP fields in this section are enabled.
The management IP address is disabled if IPv4 boot protocol is set to
DHCP.
Host names may contain only letters, numbers, and internal dashes
(hyphens), and may not include a domain. The reserved values appserv* and
dmamgk-* may not be used for host names.
The host name is combined with the domain name specified under General
System Network Settings to form the fully qualified domain name (FQDN).

Server 2

Status, host name and IP address(es) of the secondary server. The fields in
this section duplicate those in the Server 1 section and are enabled only in
two-server configuration.
The management IP address is disabled if IPv4 boot protocol is set to
DHCP.

Polycom, Inc.

Local Cluster Configuration

Field

Description

Shared Management Network
Settings

The settings in this section apply to the entire system (both servers in
two-server configuration), whether management and signaling are combined
or separate.

Virtual host name

Virtual host name and IP address(es) for the system’s management (or
combined) network interface.
For a one-server configuration, these fields are disabled. (Exception: If only
IPv6 is enabled, the system must have two addresses, so a single-server
system must still have a virtual host name and IP address.)
Host names may contain only letters, numbers, and internal dashes
(hyphens), and may not include a domain. The reserved values appserv* and
dmamgk-* may not be used for host names.
The host name is combined with the domain name specified under General
System Network Settings to form the fully qualified domain name (FQDN).
Note: Specify all IPv4 addresses in dotted-decimal form and all IPv6
addresses in colon-hex form.

IPv4
IPv6

Subnet mask

IPv4 network mask that defines the subnetwork of the system’s management
or combined interface.

IPv6 prefix length

IPv6 CIDR (Classless Inter-Domain Routing) prefix size value (the number of
leading 1 bits in the routing prefix mask) that defines the subnetwork of the
system’s management or combined interface.

IPv4 gateway

IP address of the gateway server used to route network traffic outside the
subnet.

Management Link
Name
Enable
Auto-negotiation
Speed

The name of the management network interface (eth0) is not editable, and it
can’t be disabled.
The eth0 interface corresponds with the GB1 jack on the server.
Turn on Auto-negotiation or set Speed and Duplex manually.
Note: Auto-negotiation is required if your network is 1000Base-T. Don’t select
10000 unless you’re certain your hardware platform supports it.

Duplex
Show Link Details
LAN Security Settings

Click to see details about link settings and information. This information may
be useful to Polycom Global Services when troubleshooting a network issue.
Caution: In a network that requires 802.1x authentication for servers (this is
rarely the case), incorrect settings in this section and, if applicable, lack of the
proper certificate(s) can make the system unreachable. Recovering from this
situation requires connecting a laptop to the system using a crossover cable
in order to access it.

Enable 802.1x

Enables the system to authenticate this network interface to the LAN.
Depending on the authentication method, the access credentials required
may be either a user name and password (specified below) or a security
certificate.

User name

The user name with which the system may authenticate this interface.

Polycom, Inc.

Local Cluster Configuration

Field

Description
Password
Confirm password

The password for the user name entered above.

EAP Method

The Extensible Authentication Protocol method used to establish trust with the
authentication server (this is also known as the outer authentication protocol).

Protocol

When a TLS tunnel is established with the authentication server, the protocol
used within the tunnel (this is also known as the inner authentication protocol).

Shared Signaling Network
Settings

The settings in this section are enabled only if management and signaling
traffic are on separate networks. If so, they apply to the entire system (both
servers in two-server configuration).
For a one-server configuration, the virtual host name and IP fields are
disabled. (Exception: If only IPv6 is enabled, the system must have two
addresses, so a single-server system must still have a virtual host name and
IP address.)
The settings are the same as those in Shared Management Network
Settings, except that under Signaling Link, the signaling network interface
(eth2) can be disabled. This capability exists for debugging purposes.
The eth2 interface corresponds with the GB3 jack on the server.
(The eth1 interface, which corresponds with the GB2 jack, is reserved for the
private network connection between the two servers in a two-server cluster.)

General System Network
Settings

The settings in this section apply to the entire system and aren’t specific to
management or signaling.

DNS search domains

One or more fully qualified domain names, separated by commas or spaces.
The system domain you enter below is added automatically, so you need not
enter it.

DNS 1

IP addresses of up to three domain name servers. At least one DNS server is
required.
Your Polycom RealPresence DMA system must be accessible by its host
name(s), not just its IP address(es), so you (or your DNS administrator) must
create A and/or AAAA records for IPv4 and IPv6, respectively, as well as the
corresponding PTR records, on your DNS server(s). A/AAAA records and
PTR records that map each physical host name to the corresponding physical
IP address and each virtual host name to the corresponding virtual IP address
are mandatory, as are the corresponding PTR records that allow reverse DNS
resolution of the system’s physical or virtual host name(s).

DNS 2
DNS 3

Domain

The domain for the system. This is combined with the host name to form the
fully qualified domain name (FQDN). For instance:
Host name: dma1
Domain: callservers.example.com
FQDN: dma1.callservers.example.com

Signaling DSCP

The Differentiated Services Code Point value (0 - 63) to put in the DS field of
IP packet headers on outbound packets associated with signaling traffic.
The DSCP value is used to classify packets for quality of service (QoS)
purposes. If you’re not sure what value to use, leave the default of 0.

Polycom, Inc.

Local Cluster Configuration

Field

Description

Management DSCP

The Differentiated Services Code Point value (0 - 63) to put in the DS field of
IP packet headers on outbound packets associated with management traffic
(including communications to other clusters.
The DSCP value is used to classify packets for quality of service (QoS)
purposes. If you’re not sure what value to use, leave the default of 0.

Default IPv6 gateway

The IPv6 gateway’s address and the interface used to access it, generally
eth0, specified as:
%eth0

Default IPv4 gateway

If management and signaling traffic are on separate networks, select which of
the two networks’ gateway servers is the default.
Your choice depends on your network configuration and routing. Typically,
unless all the endpoints, MCUs, and other devices that communicate with the
system are on the same subnet, you’d select the signaling network.

See also:
Local Cluster Configuration
Local Cluster Configuration Procedures

Routing Configuration Dialog
In the Network page’s action list, the Routing Configuration command opens the Routing Configuration
dialog, where you can add or delete network routing rules (IPv4, IPv6, or both, depending on the System
IP type setting on the Network page). The Show raw routing configuration button lets you view the
operating system’s underlying routing configuration.
In a split network configuration, routing rules are necessary for proper routing of network traffic. In a
combined network configuration, the operating system’s underlying routing configuration is likely sufficient
unless you need a special rule or rules for your particular network. If you aren’t sure, consult the appropriate
IT staff or network administrator for your organization.
Note: Route configuration applies to current network settings
You can only configure route settings that are valid for the currently applied settings in Admin > Local
Cluster > Network Settings. If you need to change the network settings and routing configuration,
make and apply the network settings changes first. Keep this in mind if you receive an error when
attempting to change the routing configuration.

The following table describes the fields in the Routing Configuration dialog. If System IP type is set to
IPv4 + IPv6, the dialog contains two essentially identical sections, one for each IP type. Each section
contains the input fields listed below, a table showing the defined routing rules, and buttons for adding and
deleting routes.

Polycom, Inc.

Local Cluster Configuration

Field

Description

Host/Network

The IP address of the destination network host or segment.

Prefix length

The CIDR (Classless Inter-Domain Routing) prefix size value (the number of
leading 1 bits in the routing prefix mask). This value, together with the
Host/Network address, defines the subnet for this route.
For IPv4, a prefix length of 24 is equivalent to specifying a dotted-quad subnet
mask of 255.255.255.0. A prefix length of 16 is equivalent to specifying a
subnet mask of 255.255.0.0.

Interface

In split network configuration, select the interface for this route.

Via

IP address of router for this route. Optional, and only needed for non-default
routers.

When you add a routing rule, it appears in the table below the input fields. Select a rule and click Delete
selected route to delete it. Click Show raw routing configuration to display the operating system’s
underlying routing configuration.
See also:
Network Settings

Time Settings
The following table describes the fields on the Time Settings page. These values are normally set in the
USB Configuration Utility during system installation and rarely need to be changed. See the Getting Started
Guide.
Caution: Time settings changes require a restart
Changing time settings requires a system restart and terminates all active conferences.
You can’t change the system’s time settings while it’s integrated with a Polycom RealPresence
Resource Manager system or part of a supercluster. The integration must first be terminated or the
cluster removed from the supercluster. See RealPresence Resource Manager Integration or
Superclustering.
We strongly recommend specifying NTP servers.

Field

Description

System time zone

Time zone in which the system is located. We strongly recommend selecting
the time zone of a specific geographic location (such as America/Denver), not
one of the generic GMT offsets (such as GMT+07 POSIX).
If you really want to use a generic GMT offset (for instance, to prevent
automatic daylight saving time adjustments), note that they use the
Linux/Posix convention of specifying how many hours ahead of or behind
local time GMT is. Thus, the generic equivalent of America/Denver
(UTC-07:00) is GMT+07, not GMT-07.

Polycom, Inc.

Local Cluster Configuration

Field

Description

Manually set system time

We don’t recommend setting time and date manually.

NTP Servers

Specify up to three time servers for maintaining system time (we recommend
three). Enter IP addresses or fully qualified domain names.

See also:
Local Cluster Configuration
Local Cluster Configuration Procedures

Licenses
The Polycom RealPresence DMA system is licensed for the number of concurrent calls it can handle and
optionally for API access. See License the Polycom RealPresence DMA System for more information about
licensing.

Licenses for the Appliance Edition
The following table describes the fields on the Licenses page when using the Appliance Edition of the
RealPresence DMA system.
Field

Description

Active License
Licensed calls

The maximum number of concurrent calls that the license enables.

Licensed capabilities

Currently, the only separately licensed capability is access to the
RealPresence Platform API.
Note: An API license isn't required in order for a Polycom RealPresence
Resource Manager system to access the API. It's only needed for a client
application you or a third party develop.

Licensed capabilities

The special features of the Polycom RealPresence DMA system that the
license enables.

Activation Keys
A two-server cluster has two sets of the fields below, one for each server in the cluster.
System serial number

The serial number of the specified server.

Activation key

The activation key you received from Polycom for this server. The key for
each server must be the correct one for that server’s serial number.

End User License Agreement
Status

The state of acceptance of the EULA; if not accepted, this system is unable to
make calls.

User

The user who accepted the EULA.

Polycom, Inc.

Local Cluster Configuration

Field

Description

Date accepted

The GMT date and time of EULA acceptance.

Automatically send usage data

Select to help improve this product by sending anonymous usage data to
Polycom.
See Automatically Send Usage Data for more information.

Licenses for the Virtual Edition
The following table describes the fields on the Licenses page when using the Virtual Edition of the
RealPresence DMA system.
Field

Description

Active License
Licensed calls

The maximum number of concurrent calls that the license enables.

Licensed capabilities

DMA Host
Host name

The host name of this VM instance, configurable on the Admin > Local
Cluster > Network Settings page.

Host ID

The VMware UUID of this VM instance.

License version

The version of the installed license.

Licensing Server
License server address

The read-only address of the primary licensing server.
Note: This field is automatically provisioned by RealPresence Platform
Director.

Backup server address

The read-only IP address or domain name of the secondary license server.
Note: This information is automatically provisioned by RealPresence Platform
Director.

Port

The port used for communication with the licensing server(s). The default port
is 3333.

Last successful connection

The licensing server that the system last communicated with, followed by the
time of the last communication.

End User License Agreement
Status

The state of acceptance of the EULA; if not accepted, this system is unable to
make calls.

User

The user who accepted the EULA.

Polycom, Inc.

Local Cluster Configuration

Field

Description

Date accepted

The GMT date and time of EULA acceptance.

Automatically send usage data

Select to help improve this product by sending anonymous usage data to
Polycom.
See Automatically Send Usage Data for more information.

See also:
Local Cluster Configuration
Local Cluster Configuration Procedures

Signaling Settings
On the Signaling Settings page, you can configure H.323 and SIP signaling.
Note: Supercluster-wide signaling settings
Although these are cluster-specific settings that are not part of the data store shared across
superclustered systems, we strongly recommend that all signaling settings be the same across all
clusters in a supercluster.
The settings for untrusted SIP call handling (“unauthorized” or “guest” calls) must be the same across
all clusters in a supercluster.

H.323 and SIP Signaling
If H.323 signaling is enabled, the Polycom RealPresence DMA system’s Call Server operates as a
gatekeeper, receiving registration requests and calls from H.323 devices. If SIP signaling is enabled, Call
Server operates as a SIP registrar and proxy server, receiving registration requests and calls from SIP
devices. If both are enabled, the system automatically serves as a SIP <–> H.323 gateway.
As a best practice, we recommend configuring your video conferencing network in such a way as to avoid
using the RealPresence DMA system as a SIP <--> H.323 gateway.
Either H.323, SIP, or both must be enabled in order for the RealPresence DMA system’s Conference
Manager to receive calls for multipoint conferences (virtual meeting rooms, or VMRs) and distribute them
among its pool of MCUs.
On this page, you can also:
● Turn on H.235 authentication for H.323 devices.
● Turn on SIP digest authentication for SIP devices.
● Click a Device authentication settings link to go to the Device Authentication page, where you
can configure SIP device authentication and maintain the inbound device authentication list for both
H.323 and SIP devices (see Device Authentication).
Note: Authentication for specific devices
You can turn authentication off and on for specific devices (assuming that it’s turned on here for that
device type). See Edit Device Dialog.

Polycom, Inc.

Local Cluster Configuration

● Configure specific ports or prefixes for untrusted (“unauthorized” or “guest”) SIP calls that can only
access specific resources (VMRs, VEQs, or a SIP peer).

H.323 Device Authentication
In an environment where H.235 authentication is used, H.323 devices include their credentials (name and
password) in registration and signaling (RAS) requests. The Polycom RealPresence DMA system
authenticates requests as follows:
● If it’s a signaling request (ARQ, BRQ, DRQ) from an unregistered endpoint, the Call Server doesn’t
authenticate the credentials.
● Otherwise, if the request is from an endpoint and the Polycom RealPresence DMA system is
integrated with a Polycom RealPresence Resource Manager system, the Call Server attempts to
authenticate the endpoint’s credentials with the RealPresence Resource Manager system.
● If it can’t authenticate with the RealPresence Resource Manager system, or if the request is from an
MCU or neighbor gatekeeper, the Call Server attempts to authenticate using its device authentication
list.
● If it’s a signaling request from a registered endpoint, or if the request is from an MCU or neighbor
gatekeeper, the Call Server attempts to authenticate using its device authentication list (see Device
Authentication).
If the credentials can’t be authenticated, the Call Server rejects the registration or signaling request. For call
signaling requests, it also rejects the request if the credentials differ from those with which the device
registered.

SIP Device Authentication
The SIP digest authentication mechanism is described in RFC 3261, starting in section 22, and in
RFC 2617, section 3. When a SIP endpoint registers with or calls the Polycom RealPresence DMA system,
if the request includes authentication information, that information is checked against the Call Server’s local
device authentication list (see Device Authentication).
SIP authentication can be enabled at the port/transport level or (for “unauthorized” access prefixes) the
prefix level.
If SIP authentication is enabled and an endpoint’s request doesn’t include authentication information, the
Call Server responds with an authentication challenge containing the required fields (see the RFCs). If the
endpoint responds with valid authentication information, the system accepts the registration or call.
Note: SIP device authentication
If inbound SIP authentication is turned on for a port or prefix, the Polycom RealPresence DMA system
challenges any SIP message coming to the system via that port or with that prefix. Any SIP peer and
other device that interacts with the system by those means must be configured to authenticate itself,
or you must turn off Device authentication for that specific device. See Edit Device Dialog.

Untrusted SIP Call Handling Configuration
You can configure special handling for SIP calls from devices outside the corporate firewall that aren’t
registered with the Polycom RealPresence DMA system and aren’t from a federated division or enterprise.
These calls come to the RealPresence DMA system via SIP session border controllers (SBCs) such as a
Polycom RealPresence Access Director or Acme Packet Session Border Controller device (which are
configured as SIP peers in the RealPresence DMA system; see External SIP Peer).

Polycom, Inc.

Local Cluster Configuration

You can route such untrusted (“unauthorized” or “guest”) calls by creating a separate set of “guest” dial rules
used only for these untrusted calls. See Dial Rules.
Depending on the SIP SBC and how it’s configured, such calls can be distinguished in one of two ways:
● By port: The SBC routes untrusted calls to a specific port.
● By prefix: The SBC adds a specific prefix in the Request-URI of the first INVITE message for the call.
The RealPresence Access Director SBC supports only the prefix method. The Acme Packet Session Border
Controller SBC can be configured for either.
In the SIP Settings section of the page, you can add one or more ports, prefixes, or both for untrusted calls.
For each entry, you can specify whether authentication is required. Calls to an untrusted call prefix follow
the authentication setting for that prefix, not for the port on which they’re received. For port entries, you can
also specify the transport, and if TLS, whether certificate validation is required (mutual TLS).
Note: Require certificate validations for TLS
If Unlock SIP Settings mutual authentication option on the Signaling Settings page is
unchecked on the Security Settings page, then Require mutual authentication (validation of
client certificates) is turned on for both authorized and unauthorized ports, and it can’t be turned off.
See Security Settings.

Signaling Settings Fields
The following table describes the fields on the Signaling Settings page.
Field

Description

H.323 Settings
Enable H.323 signaling

Enables the system to receive H.323 calls.
Caution: Disabling H.323 terminates any existing H.323 calls. When you click
Update, the system prompts you to confirm.

Status

Indicates whether the system’s H.323 gatekeeper functions are active.

H.225 port

Specifies the port number the system’s gatekeeper uses for call signaling.
We recommend using the default port number (1720), but you can use the
same value as the RAS port or any other value from 1024 to 65535 that’s not
already in use.

RAS port

Specifies the port number the system’s gatekeeper uses for RAS
(Registration, Admission and Status).
We recommend using the default port number (1719), but you can use the
same value as the H.225 port or any other value from 1024 to 65535 that’s not
already in use.

H.245 open firewall ports

Shows the port range used for H.245 so you can configure your firewall
accordingly. This is display only.

H.323 multicast

Enables the system to support gatekeeper discovery (GRQ messages from
endpoints) as described in the H.323 and H.225.0 specifications.

Polycom, Inc.

Local Cluster Configuration

Field

Description

Enable H.323 device
authentication

Check the box to turn on H.323 device authentication.
Click Device authentication settings to go to the Device Authentication
page and add authentication credentials (see Device Authentication).

SIP Settings
Enable SIP signaling

Enables the system to receive Session Initiation Protocol (SIP) calls.
Caution: Disabling SIP terminates any existing SIP calls. When you click
Update, the system prompts you to confirm.

Enable ANAT support

Configures the system to pass through Alternative Network Address Types
(ANAT) signaling (RFC 4091 and RFC 4092) in the Session Description
Protocol (SDP) for the purpose of negotiating IP version in a dual-stack (IPv4
+ IPv6) environment.

Authorized ports
Unencrypted SIP port

To permit unencrypted SIP connections, select either TCP or UDP/TCP from
the list. Select None to disallow unencrypted SIP connections.
We recommend using the default port number (5060), but you can use any
value from 1024 to 65535 that’s not already in use and is different from the
TLS port and from any “unauthorized” or “guest” ports that your SBC(s) may
be configured to use for calls to the system.

Enable authentication

Check the box to turn on SIP device authentication for unencrypted SIP.
Click the Device authentication settings link to go to the Device
Authentication page to configure SIP device authentication and add device
authentication credentials (see Device Authentication). The settings on that
page determine:
• The realm used for authentication.
• Whether the Call Server responds to unauthenticated requests with 401
(Unauthorized) or 407 (Proxy Authentication Required).

TLS port

Specifies the port number the system uses for TLS.
We recommend using the default port number (5061), but you can use any
value from 1024 to 65535 that’s not already in use and is different from the
UDP/TCP port and from any “unauthorized” or “guest” ports that your SBC(s)
may be configured to use for calls to the system.
If SIP signaling is enabled, TLS is automatically supported. Unless
unencrypted SIP connections are specifically permitted, TLS must be used.

Enable authentication

Check the box to turn on SIP device authentication for encrypted SIP.
Click the Device authentication settings link to go to the Device
Authentication page to configure SIP device authentication and add device
authentication credentials (see Device Authentication). The settings on that
page determine:
• The realm used for authentication.
• Whether the Call Server responds to unauthenticated requests with 401
(Unauthorized) or 407 (Proxy Authentication Required).

Polycom, Inc.

Local Cluster Configuration

Field

Description
Require mutual
authentication (validation
of client certificates)

Check the box to enable mutual TLS, requiring each caller to present a valid
certificate.
Note: This setting is enabled and locked if Unlock SIP Settings mutual
authentication option on the Signaling Settings page option is unchecked
on the Security Settings page. See Security Settings.

Unauthorized ports

Lists the ports used by your SBC(s) for untrusted calls, showing the transport
type for each and, for TLS, whether a certificate is required. The
Authentication column indicates whether calls to that port are passed without
challenge, challenged for authentication credentials, or blocked.
Click Add to add a port to the list (see Add Guest Port Dialog). Click Edit to
edit the selected entry (see Edit Guest Port Dialog) or Delete to delete it.

Unauthorized prefixes

Lists the prefixes used by your SBC(s) for untrusted calls. The Strip Prefix
column indicates whether the RealPresence DMA system should immediately
strip the prefix. The Authentication column indicates whether calls to that
port are passed without challenge, challenged for authentication credentials,
or blocked.
Click Add to add a prefix to the list (see Add Guest Prefix Dialog). Click Edit
to edit the selected entry (see Edit Guest Prefix Dialog) or Delete to delete it.

See also:
Local Cluster Configuration
Local Cluster Configuration Procedures

Add Guest Port Dialog
The Add Guest Port dialog appears when you click the Add button next to the Unauthorized ports list in
the SIP Settings section of the Signaling Settings page. It lets you add a port to the list of ports used for
“unauthorized” or “guest” calls.
The following table describes the fields in the Add Guest Port dialog.
Field

Description

Port

The SIP signaling port number for this entry.
This is the port number that an SBC is configured to use for untrusted calls to
the RealPresence DMA system via the transport specified below.

Transport

To use this guest port for unencrypted SIP connections, select either TCP or
UDP/TCP from the list. To use this port for encrypted SIP connections, select
TLS.

Polycom, Inc.

Local Cluster Configuration

Field

Description

Require mutual authentication
(validation of client certificates)

For TLS transport, check this box to enable mutual TLS, requiring callers to
present a valid certificate.
Note: This setting is enabled and locked if Unlock SIP Settings mutual
authentication option on the Signaling Settings page is unchecked on the
Security Settings page. See Security Settings.

Authentication

Select one of the following:
• None — The system doesn’t issue authentication challenges or check
authentication credentials for calls to this port.
• Authentication — The system issues authentication challenges and
checks authentication credentials for calls to this port.
The settings on the Device Authentication page (see Device
Authentication) determine the realm used for authentication and
whether the Call Server responds to unauthenticated requests with
401 (Unauthorized) or 407 (Proxy Authentication Required).
• Block — The system blocks calls to this port.

See also:
Signaling Settings
Local Cluster Configuration Procedures

Edit Guest Port Dialog
The Edit Guest Port dialog lets you edit an Unauthorized ports list entry in the SIP Settings section of
the Signaling Settings page.
The following table describes the fields in the Edit Guest Port dialog.
Field

Description

Port

The SIP signaling port number for this entry.
This is the port number that an SBC is configured to use for untrusted calls to
the RealPresence DMA system via the transport specified below.

Transport

To use this guest port for unencrypted SIP connections, select either TCP or
UDP/TCP from the list. To use this port for encrypted SIP connections, select
TLS.

Polycom, Inc.

Local Cluster Configuration

Field

Description

Require mutual authentication
(validation of client certificates)

Authentication

See also:
Signaling Settings
Local Cluster Configuration Procedures

Add Guest Prefix Dialog
The Add Guest Prefix dialog appears when you click the Add button next to the Unauthorized prefixes
list in the SIP Settings section of the Signaling Settings page. It lets you add a prefix to the list of prefixes
used for “unauthorized” or “guest” calls.
The following table describes the fields in the Add Guest Prefix dialog.
Field

Description

Prefix

The prefix number for this entry.
This is the number that an SBC is configured to add to the Request-URI of the
first INVITE message for untrusted calls to the RealPresence DMA system.

Strip prefix

Check this box to have the system immediately strip this prefix from the
INVITE message.

Authentication

Select one of the following:
• None — The system doesn’t issue authentication challenges or check
authentication credentials for calls with this prefix.
• Authentication — The system issues authentication challenges and
checks authentication credentials for calls with this prefix.
The settings on the Device Authentication page (see Device
Authentication) determine the realm used for authentication and
whether the Call Server responds to unauthenticated requests with
401 (Unauthorized) or 407 (Proxy Authentication Required).
• Block — The system blocks calls with this prefix.

Polycom, Inc.

Local Cluster Configuration

See also:
Signaling Settings
Local Cluster Configuration Procedures

Edit Guest Prefix Dialog
The Edit Guest Prefix dialog lets you edit an Unauthorized prefixes list entry in the SIP Settings section
of the Signaling Settings page.
The following table describes the fields in the Edit Guest Prefix dialog.
Field

Description

Prefix

The prefix number for this entry.
This is the number that an SBC is configured to add to the Request-URI of the
first INVITE message for untrusted calls to the RealPresence DMA system.

Strip prefix

Check this box to have the system immediately strip this prefix from the
INVITE message.

Authentication

See also:
Signaling Settings
Local Cluster Configuration Procedures

Logging Settings
The following table describes the fields on the Logging Settings page.
Field

Description

Logging level

Leave the default, Debug, unless advised to change it by Polycom support.
Production reduces system overhead and log file sizes, but omits information
that’s useful for troubleshooting. Verbose debug is not recommended for
production systems.

Rolling frequency

If rolling the logs daily (the default) produces logs that are too large, shorten
the interval.

Polycom, Inc.

Local Cluster Configuration

Field

Description

Retention period (days)

The number of days to keep log archives. For most systems, we recommend
setting this to 7.

Local log forwarding

Checking the Enable forwarding check box allows you to forward selected
log entries to a central log management server (such as Graylog2). The log
management server should be configured to accept log entries via UDP port
514.
Specify:
• The address of the destination server. It must be running some version of
syslog.
• The facility value. Default is Local0.
• The log or logs to forward. The source log file name is included in each of
the forwarded messages.
Note: The RealPresence DMA system’s server.log entries are mapped to
syslog-compliant severities (for example, a “warn” message from server.log
arrives at the destination server with the syslog-compliant “warn” level, and an
“info” message arrives with the “info” level). All other logs being forwarded are
assigned the syslog-compliant “notice” severity.
Each log message is forwarded with the RealPresence DMA system’s
timestamp intact. The receiving syslog adds its own timestamp, but preserving
the RealPresence DMA-applied timestamp makes it easier to accurately
troubleshoot time-sensitive events.

See also:
Licenses for the Appliance Edition

Alerting Settings
The Alerting Settings page allows you to configure thresholds for system alerts. Here, you can enable or
disable certain alerts, and control when they will be triggered.
Note: SNMP and system alerts configuration
Since the triggering of SNMP alerts coincides with system alerts, configuration on this page applies to
both system alerts and SNMP alerts.

The Threshold Value column on the right of the page lists the configurable value for each alert’s threshold.
Use the arrows next to each field or enter a new number to change the default value. Click the Update
button to save your changes, or the Select Defaults button to revert them (Select Defaults returns the
values in all fields on this page to their factory defaults).
See the following table for descriptions of each alert’s condition.

Polycom, Inc.

Local Cluster Configuration

Alert ID

Threshold Condition

Description

3103

Days until server certificate expires is less than

Alert when there are only this many
days until the system’s security
certificate expires.

3105

Days until CA certificate expires is less than

Alert when there are only this many
days until the server’s CA-signed
security certificate expires.

3401

Percentage available disk space is less than

Alert when the percentage of free disk
space available on the DMA system
falls below this value.

3404

Percentage log file usage is greater than

Alert when the percentage of the log
file storage area used by log data is
above this value.

3405

Percentage CPU utilization is greater than

Alert when system CPU utilization is
between this lower limit, and...

And percentage CPU utilization is less than or equal to

...this upper limit.

3406

Percentage CPU utilization is greater than

Alert when system CPU utilization is
above this value.

5002

Number of hyperactive, blacklisted endpoints is greater than

Alert when the number of registered
endpoints that are blacklisted for
sending too much H.323 traffic is
above this value.

Local Cluster Configuration Procedures
This section describes the following Polycom RealPresence DMA 7000 system configuration procedures:
● Add Licenses
● Configure Signaling
● Configure Logging
If you’re performing the initial configuration of your Polycom RealPresence DMA system, study Polycom
RealPresence DMA System Initial Configuration Summary before you continue. Other tasks are required
that are described elsewhere.

Add Licenses
You can add licenses to both Appliance Edition and Virtual Edition systems.

Add Licenses to the RealPresence DMA system, Appliance Edition
Adding licenses to your Polycom RealPresence DMA system, Appliance Edition, is a two-step process:
● Request a software activation key code for each server.
● Enter the activation key codes into the system.

Polycom, Inc.

Local Cluster Configuration

The procedures below describe the process.

To request a software activation key code for each server
1 Log into the Polycom RealPresence DMA system as an administrator and go to Admin > Local
Cluster > Licenses.
2 Record the serial number for each Polycom RealPresence DMA server:
Server A: ____________________________
Server B: ____________________________ (none for single-server system)
3 Go to http://www.polycom.com/activation.
4 If you don’t already have one, register for an account. Then log in.
5 Select Product Activation.
6 In the License Number field, enter the software license number listed on the first (or only) server’s
License Certificate (shipped with the product).
7 In the Serial Number field, enter the first (or only) server’s serial number (which you recorded in
step 2).
8 Click Generate.
9 When the activation key for the first (or only) server appears, record it:
Server A: __________-__________-_________-___________
10 If you have a single-server Polycom RealPresence DMA system, you’re finished with this procedure.
Continue to the next procedure.
11 If you have a two-server cluster, repeat steps 6–8, this time entering the second license number you
received and the second server’s serial number (also recorded in step 2).
Caution: Activation keys linked to the server serial number
An activation key is linked to a specific server’s serial number. For a two-server cluster, you must
generate the activation key for each server using that server’s serial number. Licensing will fail if you
generate both activation keys from the same server serial number.

12 When the activation key for the second server appears, record it:
Server B: __________-__________-_________-___________

To enter license activation key codes
1 Go to Admin > Local Cluster > Licenses.
2 In the Activation key field for the first (or only) server, enter the activation key code that was
generated for that server’s serial number.
Caution: Activation keys linked to the server serial number
An activation key is linked to a specific server’s serial number. Each Activation Key field is labeled
with a serial number. For a two-server cluster, make sure that the activation key code you enter for
each server is the correct one for that server’s serial number.

3 If you have a two-server cluster, in the Activation key field for the second server, enter the
activation key code that was generated for that server’s serial number.
Polycom, Inc.

Local Cluster Configuration

4 Click Update.
A dialog informs you that the licenses have been updated.
5 Click OK.

Add Licenses to the RealPresence DMA system, Virtual Edition
The RealPresence DMA system, Virtual Edition, is deployed and licensed through Polycom RealPresence
Platform Director. You can view the licensing information for your system from the RealPresence DMA
system user interface on the Admin > Local Cluster > Licenses page.
See the RealPresence Platform Director System Administrator’s Guide for more information.
Note: Local cluster not supported with virtual edition
The RealPresence DMA Virtual Edition does not support a two-server local cluster configuration.
However, superclustering of individual RealPresence DMA Virtual Edition instances is fully supported
in a virtual environment.

See also:
Shared Number Dialing

Add Direct Dial Virtual Entry Queue Dialog
Lets you add a direct dial virtual entry queue (VEQ) to the list of configured VEQs on the Shared Number
Dialing page. The following table describes the fields in the dialog.
Field

Description

A meaningful description for this VEQ and its IVR experience, such as Direct
Dial - English.

Response entry attempts

The number of times a caller can enter an invalid VMR number before the
system rejects the call.

RMX entry queue

See also:
Shared Number Dialing

Edit Virtual Entry Queue Dialog
Lets you edit the virtual entry queue (VEQ) selected on the Shared Number Dialing page. The following
table describes the fields in the dialog.
Field

Description

Virtual Entry Queue
Virtual entry queue number

The VEQ number.

Dial-in number

Number used to dial into the VEQ. Automatically set to the dialing prefix (see
Conference Settings) plus VEQ number.

Description

A meaningful description for this VEQ and its IVR experience, such as which
language is used.

Response entry attempts

The number of times a caller can enter an invalid VMR number before the
system rejects the call.

Polycom, Inc.

222

Conference Manager Configuration

Field

Description

RMX entry queue

DMA-based IVR Call Flow (only for “External IVR control” entry queues)
IVR prompt set

For a RealPresence DMA-controlled VEQ, the prompt set to be used. The list
includes all those installed on the RealPresence DMA system (see IVR
Prompt Sets).

Timeout for response entry
(sec)

The length of time that the RealPresence DMA system waits for a caller to
respond to a prompt (5-60 seconds).

DTMF terminator

The terminator used to mark the end of caller input.

Operator assistance URI

The SIP URI to which to route the call for operator (help desk) assistance.

Request operator transfer
DTMF

The DTMF command for requesting an operator.
Note: If this digit string matches a VMR number, that VMR becomes
unreachable.

Timeout to cancel operator
request (sec)

The length of time after requesting an operator that a caller is given to cancel
that request (1-10 seconds).
Note: An operator request can be canceled by entering any DTMF key.

Script

Scripts entered in this section have access to the DTMF digits entered by
callers. The system executes these scripts during VEQ processing, and can
change and reject the DTMF digits callers enter. You can use this functionality
to strip prefixes entered by a caller or to authorize participants dialing in to
VEQs. These scripts are written in the Javascript language.
The Sample Virtual Entry Queue Script section provides an example VEQ
script that you can modify for your own purposes.

Enabled

Enable or disable the script in the Script text box.

Script

Type (or paste) the VEQ script you want to apply. Then click Debug this
script to open the Script Debugging Dialog for VEQ Scripts and test the script
with various variables.

See also:
Shared Number Dialing

Edit Direct Dial Virtual Entry Queue Dialog
Lets you edit the direct dial virtual entry queue (VEQ). The following table describes the fields in the dialog.

Polycom, Inc.

223

Conference Manager Configuration

Field

Description

A meaningful description for this VEQ and its IVR experience, such as Direct
Dial - English.

Response entry attempts

The number of times a caller can enter an invalid VMR number before the
system rejects the call.

RMX entry queue

See also:
Shared Number Dialing

Script Debugging Dialog for VEQ Scripts
The Script Debugging dialog lets you test a Javascript executable script that you’ve associated with a
Virtual Entry Queue (VEQ). It lets you specify parameters of a call and the DTMF string entered by a caller,
observing the result of the script.
The following table describes the fields in the Script Debugging dialog.
Field

Description

Dial string

This is the DIAL_STRING variable in the script. Enter a dial string if script
execution depends on this variable. Alternatively, provide the entire SIP INVITE
message.
Note: For SIP, the script should always specify the schema prefix (sip or sips).
For instance:
DIAL_STRING = "sip:xxx@10.33.120.58"

DTMF digits

Enter the DTMF digits, corresponding to the script variable DTMF_STRING, that
should be evaluated or transformed by the script.

Caller site

Select a site in order to set the first four caller variables.

Caller variables

Lists variables that can be used in the script to represent caller alias values. Enter
an alias value to test for that variable.

Final result

Displays the outcome of running the script.
If the script rejected the DTMF string, a message tells you so. Otherwise, the
transformed DTMF string is displayed.

Script output

Displays any output produced by the script (e.g., println statements).

Output SIP headers

Displays any SIP headers produced by the script.

See also:
Sample Virtual Entry Queue Script

Polycom, Inc.

224

Conference Manager Configuration

Sample Virtual Entry Queue Script
Virtual Entry Queue (VEQ) scripts are scripts written in the Javascript language that have access to the
DTMF digits entered by callers. The system executes these scripts during VEQ processing, and can change
and reject the DTMF digits callers enter. You can use this functionality to strip prefixes entered by a caller
or to authorize participants dialing in to VEQs.
VEQ scripts have access to the DTMF_STRING variable.
The sample script below shows how to use the scripting feature to restrict participants calling a specific VEQ
to a whitelist of VMRs.
////////////////////////////////
// A sample script that implements a whitelist of VMRs for a VEQ.
// VMRs 1000, 2000, 3000, and any VMR starting with 44 or 76 will
// be allowed.
var whitelist_vmrs = [
"1000",
// Specify list of VMRs; add or remove VMRs from this list.
"2000",
// Make sure you use the syntax ""
"3000",
];
var whitelist_patterns = [
"^44",
// The ^ causes the pattern match at the beginning of the string.
"^76"
// So 441000 will match but 100044 will not.
];
////////////////////////////////
// Match against individual VMRs. ACCEPT if any of them matches.
//
if (0 <= whitelist_vmrs.indexOf(DTMF_STRING))
{
return ACCEPT;
}
////////////////////////////////
// Match against patterns. ACCEPT if any of them matches.
//
for (i=0; i Troubleshooting Utilities
> Ping and ping the FQDNs (virtual and physical) of the other cluster(s). Do this on each cluster.

To create or join a supercluster
1 Go to Network > RealPresence DMAs.
2 In the Actions list, click Join Supercluster.
Note: Allow supercluster join operations to complete
You can only add one cluster to a supercluster at a time. Wait until the current join operation is
completely finished before attempting to add another cluster to the supercluster. The join operation
may take several minutes, and the time required increases as the number of clusters in the
supercluster increases.

3 In the Join Supercluster dialog, do one of the following:
 To create a new supercluster, enter the FQDN or host name of the virtual management interface
for the other Polycom RealPresence DMA cluster with which to form the supercluster. Be sure the
other cluster is the one whose data store you want shared with the supercluster.
 To add this system to an existing supercluster, enter the FQDN or host name of the virtual
management interface of one of the clusters in the supercluster.
Note: Create required DNS records
You may specify an IP address instead, but the host names (virtual and physical) of every cluster in
the supercluster must be resolvable by all the other clusters. For a superclustered system, A/AAAA
records on your DNS server(s) for each physical host name, physical IP address, and virtual host
name are mandatory. See Add Required DNS Records for the Polycom RealPresence DMA System.

4 Enter the user name and password with which to log into the Polycom RealPresence DMA cluster
you specified.
5 Click OK.
A prompt warns you that the system will restart and local data will be overwritten, and asks you to
confirm.
6 Click Yes.
The cluster you’re logged in to connects to the cluster you specified and establishes or joins the
supercluster. It obtains supercluster-wide configuration and data (this may take a few minutes). A
dialog informs you when the process is complete and the cluster is ready to restart. Shortly after that,
the cluster logs you out and restarts.
7 Click OK to log out immediately, or simply wait.
Note: Restart your browser
You may need to restart your browser or flush your browser cache in order to log back into the system.

Polycom, Inc.

231

Superclustering

8 Log back in and verify that the Supercluster Status pane of the Dashboard shows the correct
number of servers and clusters, and there are no warnings.
9 Go to Network > RealPresence DMAs, verify that the status of each RealPresence DMA cluster is
Superclustered, and reassign territory responsibilities as needed.

To remove a cluster from the supercluster
Note: Remove a cluster only while its servers are operational
If possible, remove a cluster only while its server or servers are on line. If you must remove a cluster
while one or both servers are off line, be aware that an offline server may be in an inconsistent state
when it’s brought back on line. If this occurs, the system attempts to auto-correct the situation. But if
the auto-correction steps fail, the only supported procedure for fixing a server in this state is to
re-install it from media.

1 Make sure that there are no calls on the cluster, and that all of its MCUs are out of service. See MCU
Procedures.
2 Reassign all of the cluster’s territory responsibilities to a different cluster.
3 Go to Network > RealPresence DMAs. In the list, select the cluster you want to remove.
4 In the Actions list, select Remove from Supercluster.
5 When asked to confirm that you want to remove the cluster, click Yes.
The selected cluster is removed from the supercluster. A dialog informs you when the process is
complete. If the cluster you removed is the one you’re logged in to, it logs you out and restarts.
6 Click OK to log out immediately, or simply wait.
Note: Restart your browser
You may need to restart your browser or flush your browser cache in order to log back into the system.

7 Log into the system you removed and verify on the Supercluster Status pane of the Dashboard
that the system is no longer superclustered.
See also:
About Superclustering
DMAs
Join Supercluster Dialog

Polycom, Inc.

232

Call Server Configuration

This section describes the Polycom® RealPresence® Distributed Media Application™ (DMA®) 7000
system’s configuration tools and tasks related to its Call Server:
● About the Call Server Capabilities
● Call Server Settings
● Domains
● Dial Rules
● Preliminary/Postliminary Scripting
● Hunt Groups
● Device Authentication
● Registration Policy
● Prefix Service
● Embedded DNS
● History Retention Settings
These are settings and features that are shared across superclustered systems. See Introduction to the
Polycom RealPresence DMA System.

About the Call Server Capabilities
The Polycom RealPresence DMA system’s Call Server capabilities provide gatekeeper functionality (if
H.323 signaling is enabled), SIP proxy server and registrar functionality (if SIP signaling is enabled), and
bandwidth management.
The system can also function as an H.323 <-> SIP gateway.
Note: Call server characteristics
In H.323, DTMF tones are usually sent over the H.323 signaling path. In SIP, DTMF tones are usually
sent over the media path as a special RTP payload packet (see RFC 4733). Because of this difference
and because the RealPresence DMA system isn’t in the media path, its gateway function doesn’t
support DTMF transmission.
The gateway function also doesn’t support content sharing or AES encryption.
The RealPresence DMA system’s gateway function is used only for calls to registered endpoints, SIP
peers, and H.323 gatekeepers. It’s not used for calls to virtual meeting rooms (VMRs), virtual entry
queues (VEQs), external addresses, or IP addresses.

In addition, the system can be integrated with a Juniper Networks Service Resource Controller (SRC) to
provide bandwidth assurance services.
Polycom, Inc.

233

Call Server Configuration

Call server configuration begins with enabling the desired signaling on each cluster’s Signaling Settings
page. Other Call Server settings are shared across all systems in a supercluster and set on the Admin >
Call Server pages.
Note: IPV4 addresses preferred for signaling communication
In an IPv4 + IPv6 environment, the Polycom RealPresence DMA system gatekeeper prefers the IPv4
address for devices that register with both. For example, if endpoint A is a dual-stack device (that is, it
supports both IPv4 and IPv6) and registers over IPv6 to a Polycom RealPresence DMA system that’s
also dual-stack, the RRQ (Registration Request) message informs the RealPresence DMA
gatekeeper of the endpoint's IPv6 and IPv4 addresses (as well as its E.164 alias, etc.).
If endpoint A dials the E.164 address of another dual-stack endpoint (endpoint B), the RealPresence
DMA gatekeeper gives preference to the IPv4 address by sending endpoint B's IPv4 address in the
ACF (Admission Confirm) message to endpoint A. Even though the initial ARQ and corresponding
ACF were over IPv6, the expected behavior is that endpoint A will continue the H.323 signaling
session to endpoint B over IPv4 since the RealPresence DMA gatekeeper informed endpoint A of
endpoint B's IPv4 signaling IP.

See also:
Call Server Configuration
Call Server Settings

Call Server Settings
On the Call Server Settings page, you can specify certain gatekeeper and SIP proxy settings used by the
Polycom RealPresence DMA system Call Server. These settings are shared across the supercluster and
apply to all the clusters.
The following table describes the fields on the page.
Field

Description

General Settings
Allow calls to/from rogue
endpoints

If this option is selected, the Call Server permits rogue endpoints to place and
receive calls. Rogue endpoints are endpoints that are in sites managed by the
system, but are not registered and active.
Turning this option off blocks calls from and to rogue endpoints.
This option has no effect on other unregistered network devices (such as
MCUs, GKs, and SBCs) or on endpoints that are not in sites managed by the
system.

Allow calls to inactive endpoints

If this option is selected, the Call Server considers inactive as well as active
endpoints when attempting to resolve an address using the Dial registered
endpoints by alias dial rule (see The Default Dial Plan and Suggestions for
Modifications).
Turning this option off can prevent the aliases of registrations that are no
longer active from masking the aliases of endpoints registered to other call
servers. This is useful in situations where an endpoint might have an active
registration with one Call Server and an inactive registration with another
(such as a mobile device that moves from a Call Server handling registrations
through an SBC to a different Call Server in the network).

Polycom, Inc.

234

Call Server Configuration

Field

Description

Available bandwidth limit (percent)

Sets the maximum percentage of the available bandwidth that can be
allocated to a single call.
If the requested bandwidth exceeds this value, the Call Server “downspeeds”
(reduces the bit rate of) the call, but only to the user’s downspeed minimum.
If there is insufficient bandwidth to comply with both this setting and the
downspeed minimum, the call is rejected.

Territory failover delay (seconds)

The number of seconds a territory’s backup cluster waits after losing contact
with the primary before it takes over the territory.
Must be in the range 6-300.

Timeout for call forwarding when
no answer (seconds)

The number of seconds to wait for the called endpoint to answer (fully
connect) before forwarding the call, if call forwarding on no answer is enabled
for the called endpoint.
Must be in the range 5-32.

Registration refresh interval
(seconds)

For H.323 endpoints, specifies how often registered endpoints send “keep
alive” messages to the Call Server. Endpoints that fail to send “keep alive”
messages on time are flagged as inactive.
For SIP endpoints, specifies the refresh interval used if the endpoint didn’t
specify an interval or specified one greater than this value.
Must be greater than or equal to the minimum SIP registration interval and in
the range 150-9999.

Lync conference ID query timeout
(seconds)

When integrated with a Microsoft® Lync 2013 environment, limits the duration
of queries to the Lync 2013 server for a dialed conference ID.
Must be in the range 1-20.

Bit rate to bandwidth conversion
factor

The factor used to derive the bandwidth needed for a call from a specified bit
rate. You can use any value from 1.000 to 5.000 (the system supports up to
three decimal places of precision).
This value not only affects site topology bandwidth limit calculations, but also
affects bit rate and bandwidth statistics that the system reports for calls.
Note: Before version 6.2, this value was 2.5 and not configurable. If you
upgrade a system running software prior to version 6.2 to version 6.2 or later,
the conversion factor remains at 2.5 after the upgrade (although it is now
configurable). If you restore a pre-6.2 backup to a version 6.2 or later system,
the conversion factor becomes the value configured in the backup you
restore.
Note: Bandwidth calculations for H.323 calls require that the hosting MCU be
actively registered to the RealPresence DMA system.

Polycom, Inc.

235

Call Server Configuration

Field

Description

For SIP calls gatewayed to an
external gatekeeper, use the
H.323 email ID as the destination

If this option is selected, when the system uses dial rules to attempt to resolve
a SIP call to an external gatekeeper, the Call Server sets the destination in the
LRQ message to the H.323 email ID (such as 1234@example.com) rather
than utilizing the E.164 number alone (such as 1234).
Some external gatekeepers, such as the RealPresence Access Director
system, may need the additional domain information in the LRQ message to
correctly resolve the LRQ request.
If this option is off, SIP calls gatewayed by the RealPresence DMA system to
a RealPresence Access Director configured as an external H.323 gatekeeper
fail because the gatekeeper doesn't have enough information to route the call.
Note: This option affects communications with all external H.323 gatekeepers
to which the RealPresence DMA system gateways SIP calls.

SIP Settings
Minimum SIP registration interval
(seconds)

The minimum time between “keep alive” messages to SIP endpoints.
Must be less than or equal to the registration refresh interval and in the range
150-3600.

SIP OPTIONS ping timer
(seconds)

The frequency with which the system sends SIP OPTIONS requests when no
other SIP traffic is received from the SIP peer.
Must be in the range 1-10000. The default value is 10.

SIP OPTIONS ping failure status
codes

Specifies which responses to the OPTIONS request indicate that a SIP peer
is not responsive.
Valid input is a comma-separated list or dash-separated range of three-digit
numeric codes; an empty field is acceptable as well.
The default value is 503.

SIP max breadth

The maximum number of SIP peers that will be tried at once.
This option applies when the Routing policy for a dial rule with the action
Resolve to external SIP peer is set to All in parallel (forking).
Must be in the range 1-99. The default value is 60.

Try next SIP peer timeout
(seconds)

The timeout in seconds when sending a SIP OPTIONS ping or an INVITE to a
SIP peer. This value can be a numeric value in the range 0.1-31.0.
The default value is 5.0.

SIP peer dial rule timeout
(seconds)

The number of seconds after invoking the dial rule that the dial attempt is
cancelled.
Must be in the range 1-300. The default value is 25.

Nonresponsive SIP peer status
codes

Specifies which responses to an initial SIP INVITE indicate that a SIP peer is
not responsive.
Valid input is a comma-separated list or dash-separated range of three-digit
numeric codes; an empty field is acceptable as well.
The default value is 503.

Polycom, Inc.

236

Call Server Configuration

Field

Description

H.323 Settings
Gatekeeper call mode

Direct call mode — The Call Server processes only H.225.0 RAS call control
messages. The endpoints exchange other call signaling and media control
messages directly, bypassing the gatekeeper.
Routed call mode — The Call Server proxies all H.323 signaling messages.

Accept H.323 neighbor requests
only from specified external
gatekeepers

If this option is selected, the Call Server accepts H.323 location requests
(LRQs) only from gatekeepers configured on the External Gatekeeper page
(see External Gatekeeper).

Resolve H.323 Email-ID dial
strings to other registered H.323
aliases

If this option is selected, the Call Server resolves email ID dial strings to
another local alias by using the user part of the email address. For example,
the dial string 1234@mycompany.com would resolve to the endpoint
registered as 1234.

Automatically assign enterprise
users’ email addresses as H.323
email IDs

If this option is selected and the system is integrated with Active Directory, an
endpoint associated with an enterprise user is assigned the user’s email
address (if that address hasn’t already been explicitly assigned to another
endpoint).

Location request hop count

The initial hop count the Call Server uses when it sends LRQs to neighbored
gatekeepers.

Location request timeout
(seconds)

The number of seconds to wait for a response from a neighbored gatekeeper.

IRQ sending interval (seconds)

The interval at which the system sends IRQ messages to H.323 endpoints in
a call, requesting QoS (quality of service) reports.
Must be in the range 10-600.

Terminate calls based on failed
responses to IRQs

If this option is selected, the Call Server terminates a call if it sends an IRQ
(Information Request) to an endpoint that signaled support for IRQs, and the
endpoint either fails to respond or responds with an IRR (Information Request
Response) containing an invalidCall field. This is the correct behavior
according to the H.323 ITU Specification, and it prevents a call license from
being used unnecessarily for a call that’s no longer active.
Some endpoints (VVX prior to v.4.0.1; Sony PCS1, XG80, and G70; and
possibly others) signal support for IRQs but don’t properly handle IRQ/IRR
messaging, causing active calls to be disconnected if this option is selected.
To avoid this problem with such endpoints, leave this option off.
Note: This setting has no effect on calls from endpoints that don’t signal
support for IRQs.

Dynamically blacklist signaling
from hyperactive endpoints

If this option is selected, the Call Server adds H.323 endpoints to its blacklist
(ignoring their signaling messages) when they send duplicate RRQ or GRQ
messages in excess of the criteria you specify below.
When an endpoint is blacklisted, the Call Server:
• Stops interpreting, responding to, auditing, or logging messages of that
type from the endpoint.
• Creates Alert 5002 and corresponding SNMP trap.
• Logs the blacklisting.

Polycom, Inc.

237

Call Server Configuration

Field

Description
Gatekeeper Blacklist Settings
Message Type

You can specify the blacklist settings separately for RRQ (Registration
Request) and GRQ (Gatekeeper Request) messages.

Threshold

The number of duplicate messages within the specified interval that causes
an endpoint to be blacklisted.

Interval (msec)

The interval in milliseconds to which the threshold applies.

Quarantine

If this option is selected, endpoints that are blacklisted are also quarantined.
They remain in Quarantined or Quarantined (Inactive) status (unable to make
or receive calls) until manually removed from quarantine. See Endpoints.

Apply to VBP

If this option is selected, video border proxies (VBPs) can be blacklisted. If a
VBP is blacklisted, none of the endpoints behind it can register.

Remove non-hyperactive
endpoints from blacklist
after specified interval
(minutes)

The interval for which an endpoint must be well-behaved (that is, not exceed
the blacklisting threshold for the specified interval) in order to be removed
from the blacklist and once again allowed to register.
When an endpoint is removed from the blacklist, the Call Server:
• Starts interpreting, responding to, auditing, and logging messages of that
type from the endpoint.
• Clears the alert and SNMP trap.
• Logs the removal from the blacklist.
Note: If the endpoint was quarantined as well as blacklisted, it remains
quarantined.

See also:
Call Server Configuration
About the Call Server Capabilities

Domains
On the Domains page, you can add administrative domains to or remove them from the list of domains from
which registrations are accepted.
If the list is empty, all domains are considered local, and the system accepts endpoint registrations from any
domain. Otherwise, it accepts registrations only from the listed domains. This is a supercluster-wide
configuration.
Calls that have a non-local domain in the dialed string do not resolve to any locally registered endpoints,
and can only resolve to a VEQ or VMR if the Conference rooms belong to every domain check box is
checked.

Polycom, Inc.

238

Call Server Configuration

Note: Resolve to External Address dial rule and local domains
The Resolve to external address dial rule action (see Add Dial Rule Dialog) doesn’t match against
domains that are considered local. If the list of domains is empty and all domains are considered local,
this dial rule action won’t match any dial string and can’t be used.
In some circumstances (depending on network topology and configuration), dialing loops can develop
if you don't restrict the RealPresence DMA system to specific domains.

The following table describes the fields on the page.
Field

Description

Add new local domain

Enter a domain and click Add to add it to the Local domains list. IP
addresses (including IP addresses with the wildcard character) and domain
names are accepted.
Domain names must be valid and full domains, but you can replace a single
host label within a domain with the wildcard character to match multiple
subdomains. For instance:, *.mycompany.com matches:
eng.mycompany.com
fin.mycompany.com
And eng.*.mycompany.com matches:
eng.sanjose.mycompany.com
eng.austin.mycompany.com
Subdomains are not local if the domain is listed without a wildcard character.
For example, if the domain mycompany.com is entered without any other
mycompany domains, this would NOT match eng.mycompany.com.

Local domains

The list of domains from which the system accepts registrations. Select a
domain and click Remove to remove it from the list. Click Restore Defaults
to remove all domains so that the system accepts registrations from any
domain.

Locally registered SIP endpoints
belong to every local domain

Specifies that call requests for locally registered SIP endpoints don’t have to
match the domain. For example, if there is an endpoint registered as
‘sip:johnsmith@1.1.1.1’ and this option is enabled, a call to
'sip:johnsmith@mycompany.com’ may be connected to that endpoint.
If this option is not selected, call requests must exactly match the URI of the
registered endpoint.

Polycom, Inc.

239

Call Server Configuration

Field

Description

Email IDs of registered H.323
endpoints belong to every local
domain

Specifies that call requests for locally registered H.323 endpoints’ email IDs
don’t have to match the domain. For example, if there is an endpoint
registered as ‘h323:johnsmith@1.1.1.1’ and this option is enabled, a call to
'h323:johnsmith@mycompany.com’ may be connected to that endpoint.
If this option is not selected, call requests must exactly match the URI of the
registered endpoint.

Conference rooms and virtual
entry queues belong to every
domain

Specifies that if the dial string specifies a conference room (VMR) or virtual
entry queue (VEQ) on the Polycom RealPresence DMA system and includes
a domain, a dial rule implementing the Resolve to conference room ID or
Resolve to virtual entry queue actions (such as dial rule #2 or #3 of the
default dial plan) ignores the domain and routes the call to that conference
room or VEQ.
If this option is not selected, a dial string’s domain must be a local domain for
the system to route the call to a conference room or VEQ.

See also:
Call Server Configuration
About the Call Server Capabilities

Dial Rules
Dial rules specify how the Polycom RealPresence DMA system Call Server uses the dial string to determine
where to route the call. This dial string may include an IP address, a string of numbers that begin with a
prefix associated with a service, a string that begins with a country code and city code, or a string that
matches a particular alias for a device.
Dial strings may match multiple dial rules, but the rules have a priority order. When the Polycom
RealPresence DMA system Call Server receives a call request and associated dial string, it applies the first
matched (highest priority) dial rule.
The Call Server comes with a default dial plan installed that provides the most commonly needed address
resolution processing. On the Dial Rules page, you can add, edit, remove, and change the order of the dial
rules that make up the system’s dial plan. This is a supercluster-wide configuration.
The Call Server can optionally have a separate dial plan used only for untrusted (“unauthorized” or “guest”)
SIP calls. These are calls from devices not registered with the RealPresence DMA system and outside the
corporate firewall (but not part of a federated enterprise). These calls typically come to the RealPresence
DMA system via session border controllers (SBCs) such as a Polycom RealPresence Access Director or
Acme Packet Session Border Controller device.
You can configure the system to recognize and accept such calls on the Signaling Settings page (see
H.323 and SIP Signaling). On the Dial Rules page, you can create a separate set of “guest” dial rules used
only for these untrusted calls.
A dial rule consists of an optional preliminary script to modify dial strings and the action to be performed,
which you select from a well-defined list of actions. These actions encapsulate potentially complex dial
resolution logic, which shields you from having to deal with these complexities.
For instance, the Resolve to registered endpoint action applies all the associated system configurations
and performs various searches on the internal endpoint registration records to determine if the inbound call
Polycom, Inc.

240

Call Server Configuration

is attempting to reach another registered endpoint. It automatically adjusts for signaling protocol
(SIP/H.323), case, and standard dial string deviations to locate a registered endpoint. You don’t have to
account for these variables in your dial plan because the logic behind the action does so for you.
You can test the current dial rules using the Test Dial Rules command. You can specify various caller
parameters and a dial string, and see how the current dial rules handle such a call. See Test Dial Rules
Dialog.
The Dial Rules page contains two lists, one for authorized calls and one for unauthorized calls. The former
contains the system’s default dial plan. The latter is empty unless you add rules to it. Both lists contain the
same fields. The following table describes the fields in the two lists.
Column

Description

Order

The priority order of the rules. Use the Move Up and Move Down commands
to change the priority of a rule.

Description

Brief description of the rule.

Action

Action performed by the rule.

Preliminary Enabled

Indicates whether a script filters or transforms the dial string before the action
is performed.

Enabled

Indicates whether the rule is turned on.

See also:
Call Server Configuration
Test Dial Rules Dialog
The Default Dial Plan and Suggestions for Modifications
Add Dial Rule Dialog
Edit Dial Rule Dialog

Test Dial Rules Dialog
The Test Dial Rules dialog provides a testing mechanism for the current dial plan. You can specify various
caller parameters and a dial string, and see how the each dial rule handles such a call and what its final
disposition is.
The following table describes the fields in the Test Dial Rules dialog.

Polycom, Inc.

241

Call Server Configuration

Field

Description

Dial string

Enter a dial string to test. Then click Test. For SIP, the dial string should
always specify the schema prefix (sip or sips). For example:
sips:rbruce@10.47.7.9

Caller site

Select a site in order to set the four caller site variables:
• CALLER_SITE_NAME
• CALLER_SITE_DIGITS
• CALLER_SITE_COUNTRY_CODE
• CALLER_SITE_AREA_CODE
These variables can’t be set directly and are display only.

CALLER_H323ID

Test caller’s H323-ID or blank.

CALLER_E164

Test caller’s H.323 E.164 alias or blank.

CALLER_TEL_URI

Test caller’s SIP tel URI or blank.

CALLER_SIP_URI

Test caller’s SIP sip URI or blank.

VMR/Lync Conf ID

This field specifies the return value of the function
“getConferenceRoomOrID()”, and is only populated when the dial rule
simulates an outbound call to an endpoint from a conference based on a VMR
or Lync conference ID.
If the dial rule simulates a call to a VMR or Lync conference ID or a dial-in call,
this field is blank.

Test route output

Displays the results of applying each rule (including its preliminary, if any) to
the dial string.
For instance, testing the dial string example shown above against the default
dial plan might result in the following:
#1:SipAlias[sips:rbruce@10.47.7.9] is not registered. H323-ID[rbruce]
is not registered.
#2:The room [rbruce] does not exist.
#3:No entry queue is found.
#4:Domain [10.47.7.9] is not within our administration.
#5:The call was accepted by this dial rule.

Final result

Displays the final outcome of the dial rule processing. The final outcome for
the example above would be:
Transformed dial string is [sips:rbruce@10.47.7.9]. The call was
accepted by dial rule #5.

See also:
Dial Rules
Add Dial Rule Dialog
Edit Dial Rule Dialog
Preliminary/Postliminary Scripting

Polycom, Inc.

242

Call Server Configuration

The Default Dial Plan and Suggestions for Modifications
The Polycom RealPresence DMA system is configured by default with a generic dial plan that covers many
common scenarios and may prove adequate for your needs. It’s described in the following table.
Rule

Effect

Dial registered endpoints by alias

If the dial string is the alias or SIP URI of a registered endpoint, the call
is routed to that endpoint.

Dial by conference room ID

Otherwise, if the dial string is the dial-in number of a conference room
on the Polycom RealPresence DMA system, the call is routed to that
conference room.

Dial by virtual entry queue ID

Otherwise, if the dial string is the dial-in number of a virtual entry queue
on the Polycom RealPresence DMA system, the call is routed to that
VEQ.

Dial to RealConnectTM conference

Otherwise, if the dial string is the dial-in number of a Lync conference
on the Lync AVMCU, the call is routed to an available Polycom MCU
that supports Lync 2013 and automatically connected to the
corresponding Lync conference on the AVMCU. (If no Polycom MCUs
that support Lync 2013 are available, the conference fails to start).

Dial services by prefix

Otherwise, if the dial string begins with the configured prefix of a service
(such as an MCU, ISDN gateway, SBC, neighbor gatekeeper, SIP peer
proxy, or simplified ISDN dialing service) the call is routed to that
service.
Note: For a SIP peer, the dial string must either include the protocol or
consist of only the prefix and user name (no @domain). For instance, if
the SIP peer’s prefix is 123, the dial string for a call to
alice@polycom.com must be one of the following:
sip:123alice@polycom.com
123alice

Dial external networks by H.323
URL, email ID, or SIP URI

Otherwise, if the address is an external address, the call is routed to
that external address (H.323 and SIP calls use the designated SBC for
the originating site to reach addresses outside the enterprise network;
see Edit Site Dialog).
Examples of external addresses:
H323:johnsmith@someothercompany.com
sip:johnsmith@someothercompany.com

Dial endpoints by IP address

Otherwise, if the address is an IP address, the call is routed to that IP
address (H.323 calls use the designated SBC for the originating site to
reach addresses outside the enterprise network).
Examples of IP addresses:
1.2.3.4
1.2.3.4##abc
sip:abc@1.2.3.4
sip:1.2.3.4@mycompany.com

Polycom, Inc.

243

Call Server Configuration

If you have special configuration needs and want to modify the dial plan, be aware that some of the default
dial rules are necessary for “normal” operation. Removing or modifying them takes the system out of
compliance with ITU and IEEE standards.
Here are some suggestions and guidelines for modifying the dial plan:
● To add an MCU, ISDN gateway, SBC, neighbor gatekeeper, SIP peer, or simplified dialing service
that can be dialed by prefix, configure the prefix range of the new service on the appropriate page.
No dial plan change is necessary, since Rule Dial services by prefix of the default dial plan takes care
of dialing by prefix.
● You can remove or disable a default dial rule if you don't want the associated functionality.
But note that Rule Dial endpoints by IP address (Dial endpoints by IP address) is used in several
scenarios where calls are received from neighbor gatekeepers or SBCs. Removing it breaks these
scenarios.
● If certain dial strings are matching on the wrong dial rule, you may need to re-order the rules.
● In some circumstances (depending on the dial plan and the network topology and configuration), dial
rules using the Resolve to external address action (like Rule 5 of the default dial plan) or the
Resolve to IP address action (like Rule 6) can enable dialing loops to develop, especially if servers
reference each other either directly or via DNS.
Common ways to avoid dialing loops include:
 Use domain restrictions to ensure that the RealPresence DMA system and its peers are each
responsible for specific domains (see Add External SIP Peer Dialog and Domains).
 Use a preliminary script like the sample script “SUBSTITUTE DOMAIN (SIP)” (see Sample
Preliminary and Postliminary Scripts) to change the domain of a SIP URI dial string to something
that won’t create a dialing loop.
 Use a postliminary script to similarly change the domain before sending to a peer.
 Use configuration options on the peers to prevent loops.
 Create a dial rule that uses the Block action and a preliminary script to enhance the system’s
ability to prevent dialing loops for specific types of calls. The preliminary script ensures that the
dial rule only matches the types of calls you want to block. This dial rule should be ordered after
other dial rules that are expected to resolve the intended call requests.
For example, a dial rule with the Block action using the following preliminary script blocks all call
requests that use a prefix of “44” if they have not been resolved by previous dial rules:
println("DIAL_STRING=" + DIAL_STRING);
var prefix='44'
var re = RegExp('^(sip:|sips:|h323:|tel:)?'+ prefix +'.*')
if(! DIAL_STRING.match(re))
{
println("NEXT_RULE");
return NEXT_RULE;
}
println("ACCEPT and terminate 44 prefix calls if they were not resolved
by previous dial rules");

Polycom, Inc.

244

Call Server Configuration

● You can add a filtering preliminary script to any dial rule to restrict the behavior of that rule.
For example, if you know that all the aliases of a specific neighbor gatekeeper are exactly ten digits
long, you may want to route calls to that gatekeeper only if the dial string begins with a certain prefix
followed by exactly ten digits.
To accomplish this, add a preliminary script to the service prefix dial rule that rejects all dial strings
that begin with the prefix, but aren’t followed by exactly ten digits.
● To exclude certain dial strings, combine a filtering preliminary script with the Block action.
● You can use a preliminary script to modify the dial strings accepted by any of the rules.
For example, to be able to call an enterprise partner by dialing the prefix 7 followed by an alias in the
partner’s namespace, configure a Resolve to external at transforms the string 7xxxx to
H323:xxxx@enterprisepartner.com.
This type of dial string modification is also useful if you are using Lync conference dial strings with
prefixes. To route a dial string with a prefix to a Lync conference ID, configure a Resolve to Lync
conference ID action with a preliminary script that removes the prefix from the dial string (1234567
would become 4567, for example).
● If your enterprise includes another gatekeeper and you want to route calls to that gatekeeper without
a prefix, add a dial rule using the Resolve to external gatekeeper action.
● If your enterprise includes a SIP peer and you want to route calls to that peer without a prefix, add a
dial rule using the Resolve to external SIP peer action.
If you have multiple SIP peers, a call matching the rule is routed to the first one to answer. You may
want to specify the domain(s) for which each is responsible (see Add External SIP Peer Dialog).
When routing to a SIP peer, the Polycom RealPresence DMA system gives up its ability to route the
call to other locations if the peer rejects the call. Consequently, a dial rule using the Resolve to
external SIP peer action should generally be the last rule in the dial plan.
Note: SIP<->H.323 gateway considerations
In a mixed H.323 and SIP environment, the Polycom RealPresence DMA system acts as a seamless
gateway. If an H.323 device sends it a Location Request (LRQ) and the dial plan contains a dial rule
using the Resolve to external SIP peer action, the RealPresence DMA system will respond with a
Location Confirm (LCF) because it can resolve the address by routing the H.323 call through its
gateway to the SIP peer(s).
You can prevent H.323 calls from being routed to SIP peers by restricting which calls are routed to
them in one or more of the following ways:
• Assign each SIP peer an authorized domain or domains (this is a good idea in any case in order to
avoid dialing loops). See Edit External SIP Peer Dialog.
• Assign each SIP peer a prefix or prefix range. See Edit External SIP Peer Dialog.
• Add a preliminary script to the dial rule using the Resolve to external SIP peer action that ensures
that the rule will only match a SIP address. See Preliminary/Postliminary Scripting.
Make the dial rule using the Resolve to external SIP peer action the last rule and ensure that all
H.323 calls will match against one of the preceding dial rules.

See also:
Dial Rules
Edit Dial Rule Dialog
Preliminary/Postliminary Scripting

Polycom, Inc.

245

Call Server Configuration

Add Dial Rule Dialog
The following table describes the fields in the Add Dial Rule dialog.
Field

Description

Dial Rule
Description

The text description displayed on the Dial Rules page.

Action

The action to be performed. When you select some actions, additional
settings become available.
See the following table of dial rule actions for more information about the
actions and the additional settings associated with them.

Enabled

Clearing this check box lets you turn off a rule without deleting it.

Preliminary

A preliminary is an executable script, written in the Javascript language, that
defines processing actions (filtering or transformation) that are part of a dial
rule and may be applied to a dial string before the dial rule’s action is
performed.
Sample Preliminary and Postliminary Scripts provides some examples you
can experiment with and modify for your purposes.

Enabled

Lets you turn a preliminary on or off without deleting it.

Script

Type (or paste) the preliminary script you want to apply. Then click Debug
this script to open the Script Debugging Dialog for
Preliminaries/Postliminaries and test the script with various variables.

The following table describes the Action options and how the system attempts to resolve the destination
address (dial string) for each.

Polycom, Inc.

246

Call Server Configuration

For this action:

The system attempts to resolve the address as follows:

Block

Blocks the call.

Resolve to IP address

Tries to treat the dial string as an IP address, and if it can, assumes it’s the address
(and port, if included) of an unregistered endpoint. If no port is specified, it uses the
default port of the signaling protocol.
If the dial string contains the characters “##,” it tries to do this using the characters
before “##.”
For SIP:
• If the domain part is an address not controlled by the RealPresence DMA
system (or supercluster), the dial string is resolved unchanged.
• If the domain part is an address controlled by the RealPresence DMA system (or
supercluster) and the user part is an IP address (and possibly “##”), the user part
is resolved to a SIP URI.
• If the characters before the first “##” resolve to an IP address, the characters
after that are treated as the user part of a URI.
For H.323, if the characters before the first “##” resolve to an IP address, the
characters after that are converted into the destinationInfo (ACF) or
destinationAddress (Setup) as follows:
• If possible, encoded as a dialedDigits address.
• Otherwise, if possible, encoded as a url-ID.
• Otherwise, encoded as an h323-ID.

Resolve to registered
endpoint

Looks for a registered endpoint (active or inactive) that has the same alias or
signaling address.
Note: This action employs the H.323<->SIP gateway function if applicable.

Polycom, Inc.

247

Call Server Configuration

For this action:

The system attempts to resolve the address as follows:

Resolve to Lync conference
ID

Queries an integrated Lync SIP peer for a Lync AVMCU-based conference with a
matching conference ID. This dial rule action enables Polycom RealConnectTM
functionality. See Scheduled Conferences with Polycom RealConnect™.
When selected, the following fields are available:
• Conference template
When checked, you can select the conference template used to start the
conference. If you leave this option unchanged, the Default conference
template configured in Admin > Conference Manager > Conference
Settings will be used. Keep in mind that the conference template must specify
a Conference mode of AVC only, or the conference will not start. See
Considerations and Requirements for Lync 2013 Integration.
• MCU pool order
Select the MCU pool order to use for MCUs that provide Lync AVMCU cascade
functionality. If you leave this option unchecked, the dial rule will use the default
pool order configured in the Default MCU pool order field on the Admin >
Conference Manager > Conference Settings page.
• Available SIP peers / Selected SIP peers selection area
This area lists the names of Available SIP peers and any Selected SIP peers.
With the provided arrow buttons, you can move SIP peers between the
Available and Selected areas. When the dial rule is executed, the system will
query the selected SIP peers to find which one is hosting the Lync conference.
Note: For an external SIP Peer to be listed in the Available SIP peers area, it
must be listed on the Network > External SIP Peers page and have the
following configuration:
 A Type of Microsoft
 The Enable RealConnectTM conferences check box selected in the Lync
Integration tab
Note: Polycom recommends ordering this rule so that it appears before any rule
with the action Resolve to external SIP peer. If the Resolve to external SIP peer
dial rule doesn’t successfully route a call, the call is aborted and no subsequent dial
rules will be attempted. Polycom also recommends that this rule not appear higher
than its default order in the list of dial rules, because this can prevent valid aliases,
VMRs, and VEQs from being dialed and can result in reduced system
performance.

Resolve to service prefix

Looks for a service prefix that matches the beginning of the dial string (not counting
the URI scheme, if present).
Note: For a SIP peer, the dial string must either include the protocol or consist of
only the prefix and user name (no @domain). For instance, if the SIP peer’s prefix
is 123, the dial string for a call to alice@polycom.com must be one of the following:
sip:123alice@polycom.com
123alice

Polycom, Inc.

248

Call Server Configuration

For this action:

The system attempts to resolve the address as follows:

Resolve to external SIP peer

Checks the domain of the dial string against all of the rule’s selected peers, looking
for a peer proxy responsible for that domain. If the dial string matches the domain
of one of the selected SIP peers, this rule will either successfully route the call, or
the call will be aborted; no subsequent dial rules will be attempted.
After selecting this action for a rule, select a Routing policy. The policy affects the
way the system resolves dial strings to SIP peers:
• All in parallel (forking)
The system uses all SIP peers simultaneously to try to resolve the dial string.
• Weighted round-robin
You can assign each SIP peer a weight in the range 1-100, with a higher weight
giving a SIP peer higher priority; the system tries each SIP peer sequentially
according to the SIP peer’s assigned weight. You can assign a SIP peer
different weights in different dial rules.
After choosing a routing policy, move the SIP peers to which the rule applies from
the Available SIP peers box to the Selected SIP peers box. If the Weighted
round-robin routing policy is selected, choose a weight for the selected SIP peer
using the Edit weight button.
Note: This action employs the H.323<->SIP gateway function if applicable.

Resolve to external
gatekeeper

If the dial string appears to be an H.323 alias, simultaneously sends LRQ
messages to all of the rule’s selected gatekeepers.
After selecting this action for a rule, move the gatekeepers to which the rule applies
from the Available gatekeepers box to the Selected gatekeepers box.
Note: This action employs the H.323<->SIP gateway function if applicable.

Resolve to external address

Determines if the dial string is a well-formed instance of an external address type to
which the rule applies, and if so, uses the resolution procedures specified in the
applicable standard for that address type.
After selecting this action for a rule, select the address type or types to which the
rule applies. The address types and applicable standards used to resolve them
are:
• SIP URI: RFCs 3261 and 3263
• H.323 url-ID: H.323 specification, Annex O
• H.323 Email-ID: H.225.0 specification, Appendix IV

Resolve to conference room
ID

Looks for a conference room (virtual meeting room, or VMR) that matches the dial
string.

Resolve to virtual entry
queue

Looks for a shared-number entry queue that matches the dial string.

See also:
Dial Rules
The Default Dial Plan and Suggestions for Modifications
Preliminary/Postliminary Scripting

Polycom, Inc.

249

Call Server Configuration

Edit Dial Rule Dialog
The following table describes the fields in the Edit Dial Rule dialog.
Field

Description

Dial Rule
Description

The text description displayed on the Dial Rules page.

Action

The action to be performed. When you select some actions, additional
settings become available.
See the table of dial rule actions below for more information about the actions
and the additional settings associated with them.

Enabled

Clearing this check box lets you turn off a rule without deleting it.

Preliminary

Enabled

Lets you turn a preliminary on or off without deleting it.

Script

Type (or paste) the preliminary script you want to apply. Then click Debug
this script to open the Script Debugging Dialog for
Preliminaries/Postliminaries and test the script with various variables.

The following table describes the Action options and how the system attempts to resolve the destination
address (dial string) for each.

Polycom, Inc.

250

Call Server Configuration

For this action:

The system attempts to resolve the address as follows:

Block

Blocks the call.

Resolve to IP address

Resolve to registered
endpoint

Looks for a registered endpoint (active or inactive) that has the same alias or
signaling address.
Note: This action employs the H.323<->SIP gateway function if applicable.

Polycom, Inc.

251

Call Server Configuration

For this action:

The system attempts to resolve the address as follows:

Resolve to Lync conference
ID

Resolve to service prefix

Polycom, Inc.

252

Call Server Configuration

For this action:

The system attempts to resolve the address as follows:

Resolve to external SIP peer

Resolve to external
gatekeeper

Resolve to external address

Resolve to conference room
ID

Looks for a conference room (virtual meeting room, or VMR) that matches the dial
string.

Resolve to virtual entry
queue

Looks for a shared-number entry queue that matches the dial string.

See also:
Dial Rules
The Default Dial Plan and Suggestions for Modifications

Polycom, Inc.

253

Call Server Configuration

Preliminary/Postliminary Scripting
A preliminary is an executable script, written in the Javascript language, that defines processing actions
(filtering or transformation) to be applied to a dial string before the dial rule’s action is performed.
A postliminary is an executable script, written in the Javascript language, that defines dial string
transformations to be applied before querying an external device (gatekeeper, SIP peer, SBC, or MCU).
Transformation scripts output some modification of the DIAL_STRING variable (which is initially set to the
dial string being evaluated).
Filtering scripts may pass the dial string on to the dial rule’s action (if the filter criteria aren’t met) or return
one of the following:
● NEXT_RULE: Skips the rule being processed and passes the dial string to the next rule.
● BLOCK: Rejects the call.
See Sample Preliminary and Postliminary Scripts for some examples.

Predefined Preliminary/Postliminary Scripting Variables
The following table describes the predefined variables you can use in a preliminary or postliminary script.
The script can evaluate a variable or change its value (the change isn’t preserved after the script completes).
Variable

Initial value

CALLER_E164

For H.323 calls only, an array variable initially set to the set of E.164
addresses of the caller. The length of the array is 0 if the caller doesn’t have
an E.164 address.

CALLER_H323ID

Array variable initially set to the set of H323ID addresses of the caller. The
length of the array is 0 if the caller doesn’t have an H323ID address.

CALLER_IS_IPV6

“TRUE” if the caller is an IPv6 endpoint. Blank otherwise.

CALLER_SIP_URI

Array variable initially set to the set of SIP URI addresses of the caller. The
length of the array is 0 if the caller doesn’t have a SIP URI address.

CALLER_SITE_AREA
_CODE

Area code of the caller’s site. Blank if the site doesn’t have an area code.

CALLER_SITE_COUNTRY_COD
E

Country code of the caller’s site. Blank if the site doesn’t have a country
code.

CALLER_SITE_DIGITS

The number of subscriber number digits in the caller’s site (that is, the length
of a phone number at the site, excluding area code). Blank if the site doesn’t
have a number of digits.

CALLER_SITE_NAME

The name of the caller’s site.

CALLER_SITE_SITE
_CODE

The site code of the caller’s site.

CALLER_TEL_URI

Array variable initially set to the set of Tel URI addresses of the caller. The
length of the array is 0 if the caller doesn’t have a Tel URI address.

Polycom, Inc.

254

Call Server Configuration

Variable

Initial value

DIAL_STRING

Initially set to the dial string being evaluated. If the script modifies the
DIAL_STRING value, the modified value is used as the input to the dial rule
action.
For SIP, when the DIAL_STRING is modified by the script, it’s use depends
on the dial rule action:

INPUT_SIP_HEADERS

For SIP calls only, an associative array containing the SIP headers in the
received SIP INVITE message.
Usage example:
if(INPUT_SIP_HEADERS["Supported"].matches(/.*ms-forking.
*/))
{
...
}

OUTPUT_SIP_HEADERS

An empty associative array. Headers that the script adds to this array replace
the corresponding headers in the received SIP INVITE message. If a header
added to this array isn’t in the received INVITE message, it’s added to the
INVITE message.
Usage example 1:
var list = OUTPUT_SIP_HEADERS.get("User-Agent");
if (list == null)
{
list = new java.util.LinkedList();
OUTPUT_SIP_HEADERS.put("User-Agent", list);
}
list.add("Someone. Not a RealPresence DMA 7000.");
Usage example 2:
var list = OUTPUT_SIP_HEADERS.get("Some-Custom-Header");
if (list == null)
{
list = new java.util.LinkedList();
OUTPUT_SIP_HEADERS.put("Some-Custom-Header", list);
}
list.add("Whatever you want");

Preliminary/Postliminary Scripting Functions
The following table describes the functions you can use in a preliminary or postliminary script. The
parentheses at the end of the function name contain the parameters, if any, that the function accepts.

Polycom, Inc.

255

Call Server Configuration

Function name and parameters

Details

getConferenceRoomOrID()

Return value:
• For dial-outs to endpoints from VMRs or Polycom RealConnectTM
conferences, returns the VMR or Lync Conference ID.
• For dial-outs to the VMR or Polycom RealConnectTM conferences, and for
dial-ins, returns the empty string.

getHeader()

Return value: Returns the contents of the specified SIP header in the original
SIP INVITE request.
Note: The return value is not changed if the SIP header is changed with
setHeader.

setHeader(,
)

Replaces the current contents of the specified SIP header in the output
version of the SIP INVITE request with .
Return value: None.
Note: Any changes made using setHeader do not affect subsequent values
returned by getHeader.

getDisplayName()

Return value: Returns the display name portion of .
Note: This function assumes that uses the format of a SIP INVITE “To”
header.

getUser()

Return value: Returns the user portion of .
Note: This function assumes that uses the format of a SIP INVITE “To”
header.

getParameterString()

Return value: Returns the parameter string portion of .
Note: This function assumes that uses the format of a SIP INVITE “To”
header.

appendParameterString(, )

Return value: Returns the result of appending to the end of
, using the format of a SIP INVITE “To” header.

removeHeader()

Removes the header named from the SIP INVITE.
Return value: None.

getPeerHost()

Return value:
• If invoked from an External SIP Peer postliminary script, returns the Next
hop address configured for this SIP peer.
• Otherwise, returns the empty string.

getPeerNetOrNextHop()

Return value:
• If invoked from an External SIP Peer postliminary script, returns one of the
following:
 The Destination network value configured for this SIP peer, if defined
 The Next hop address for this SIP peer, if the Destination network
setting is not configured
• If not invoked from an External SIP Peer postliminary script, returns the
empty string.

Polycom, Inc.

256

Call Server Configuration

Function name and parameters

Details

getPeerPort()

Return value:
• If invoked from an External SIP Peer postliminary script, returns the IP
network Port configured for this SIP peer.
• Otherwise, returns the empty string.

getPeerTransport()

Return value:
• If invoked from an External SIP Peer postliminary script, returns the
Transport type configured for this SIP peer.
• Otherwise, returns the empty string.

How Dial Rule Actions Affect SIP Headers
The following table shows how different dial rule actions apply a preliminary script’s modified dial string to
the output SIP headers in a SIP call.
Dial rule action

Output SIP headers

Resolve to registered endpoint

The To header is replaced with the modified dial string. The request URI is
based on the contact address of the registered endpoint, and not replaced
with the modified dial string.

Resolve to external address

The To header and the request URI are both replaced with the modified dial
string.

Resolve to service prefix

For a SIP peer proxy of type OCS:
The To header is replaced with the modified dial string. The request URI is
based on the address, port, and transport type of the proxy, and not
replaced with the modified dial string.
For a SIP peer proxy of type Other:
The To header and the request URI are both replaced with the modified dial
string.

Resolve to peer proxy

Resolve to IP address

Polycom, Inc.

The To header and the request URI are both replaced with the modified dial
string.

257

Call Server Configuration

See also:
Dial Rules
External Gatekeeper
External SIP Peer
External H.323 SBC
Add MCU Dialog
Script Debugging Dialog for Preliminaries/Postliminaries
Sample Preliminary and Postliminary Scripts

Script Debugging Dialog for Preliminaries/Postliminaries
The Script Debugging dialog lets you test a Javascript executable script that you’ve added as a preliminary
to a dial rule or a postliminary for an external gatekeeper, SIP peer, SBC, or MCU. It lets you specify
parameters of a call and the dial string, and see what effect the script has on the dial string.
The following table describes the fields in the Script Debugging dialog.
Field

Description

Dial string

This is the DIAL_STRING variable in the script, which is initially set to the dial
string being evaluated. Enter a dial string to test. Alternatively, provide the
entire SIP INVITE message. Then click Execute Script.
Note: For SIP, the script should always specify the schema prefix (sip or sips).
For instance:
DIAL_STRING = "sip:xxx@10.33.120.58"

Caller site

Select a site in order to set the first four caller variables.

Caller variables

Lists variables that can be used in the script to represent caller alias values.
Enter an alias value to test for that variable.

VMR/Lync Conf ID

This field specifies the return value of the function
getConferenceRoomOrID().
See Preliminary/Postliminary Scripting for a description of the
getConferenceRoomOrID() function.
If the script simulates a call to a VMR or Lync conference ID or a dial-in call,
this field is blank.

Final result

Displays the outcome of running the script.
For a dial rule preliminary, if the script rejected the dial string (skipping the dial
rule action and passing it on to the next dial rule), a message tells you so.
Otherwise, the transformed dial string is displayed.

Script output

Displays any output produced by the script (e.g., println statements).

Output SIP headers

For an external SIP peer’s postliminary, displays the headers produced by the
script.

Polycom, Inc.

258

Call Server Configuration

See also:
Preliminary/Postliminary Scripting
Sample Preliminary and Postliminary Scripts

Sample Preliminary and Postliminary Scripts
A preliminary is an executable script, written in the Javascript language, that defines processing actions
(filtering or transformation) to be applied to a dial string before the dial rule’s action is performed.
A postliminary is an executable script, written in the Javascript language, that defines dial string
transformations to be applied before querying an external device (gatekeeper, SIP peer, SBC, or MCU).
Transformation scripts output some modification of the DIAL_STRING variable (which is initially set to the
dial string being evaluated).
Filtering scripts may pass the dial string on to the dial rule’s action (if the filter criteria aren’t met) or return
one of the following:
● NEXT_RULE: Skips the rule being processed and passes the dial string to the next rule.
● BLOCK: Rejects the call.
The following sample scripts address many of the scenarios for which you might need a preliminary or
postliminary script. You can use them as templates or starting points for your scripts.
// Example preliminary and postliminary scripts
///////////////////////////////
// STRIP PREFIX
// If the dial string has prefix 99, remove it
// 991234 --> 1234
DIAL_STRING = DIAL_STRING.replace(/^99/,"");

///////////////////////////////
// ADD PREFIX
// Add prefix 99 to the dial string
// 1234 --> 991234
DIAL_STRING = "99" + DIAL_STRING;

///////////////////////////////
// STRIP PREFIX (SIP)
// If the dial string is a SIP URI with prefix 99 in the user part, remove it
// SIP:991234@abc.com --> sip:1234@abc.com
DIAL_STRING = DIAL_STRING.replace(/^sip:99([^@]*@)/i,"sip:$1");

///////////////////////////////
// ADD PREFIX (SIP)
Polycom, Inc.

259

Call Server Configuration

// If the dial string is a SIP URI, add prefix 99 to the user part
// SIP:1234@abc.com --> sip:991234@abc.com
DIAL_STRING = DIAL_STRING.replace(/^sip:([^@]*@)/i,"sip:99$1");

///////////////////////////////
// SUBSTITUTE DOMAIN (SIP)
// If the dial string is a SIP URI, change the domain part to "example.com"
// SIP:1234@abc.com --> sip:1234@example.com
DIAL_STRING = DIAL_STRING.replace(/^sip:([^@]*)@(.*)/i,"sip:$1@example.com");

///////////////////////////////
// FILTER
// If the dial string has prefix 99, do not match on this rule.
// 991234 --> NEXT_RULE

Skip to the next rule.

if (DIAL_STRING.match(/^99/))
{
return NEXT_RULE;
}

///////////////////////////////
// FILTER (Inverted)
// Do not match on this rule unless the dial string has prefix 99.
// 1234 --> NEXT_RULE
if (!DIAL_STRING.match(/^99/))
{
return NEXT_RULE;
}

///////////////////////////////
// FILTER (SIP)
// If the dial string is a SIP URI with domain "example.com", do not match on this rule.
// Skip to the next rule.
// sip:1234@example.com --> NEXT_RULE
if (DIAL_STRING.toLowerCase().match(/^sip:[^@]*@example\.com/))
{
return NEXT_RULE;
}

///////////////////////////////
// PRINTLN
// Print out the information available to the script for this call.
Polycom, Inc.

260

Call Server Configuration

//
//
//
//

Information printed using the print or println functions
is saved as a call audit event, which is viewable in the
DMA interface under Reports > Call History, and also in the
Script Debugging dialog box.

println("DIAL_STRING: " + DIAL_STRING);
println("CALLER_SITE_NAME: " + CALLER_SITE_NAME);
println("CALLER_SITE_COUNTRY_CODE: " + CALLER_SITE_COUNTRY_CODE);
println("CALLER_SITE_AREA_CODE: " + CALLER_SITE_AREA_CODE);
println("CALLER_SITE_DIGITS: " + CALLER_SITE_DIGITS);
println("CALLER_H323ID: " + CALLER_H323ID);
println("CALLER_E164: " + CALLER_E164);
println("CALLER_TEL_URI: " + CALLER_TEL_URI);
println("CALLER_SIP_URI: " + CALLER_SIP_URI);

///////////////////////////////
// FILTER (Site)
// Do not allow callers from the atlanta site to use this rule.
// (Caller site == "atlanta") --> NEXT_RULE
if (CALLER_SITE_NAME == "atlanta")
{
return NEXT_RULE;
}

///////////////////////////////
// SITE BASED NUMERIC NICKNAMES
// Allow caller to omit country and area code when calling locally.
// Assumes that country and area codes are set in site topology.
// Assumes that all endpoints are registered with their full alias, including
// country and area code.
// 5551212 --> 14045551212
if (DIAL_STRING.length == CALLER_SITE_DIGITS)
{
DIAL_STRING = CALLER_SITE_COUNTRY_CODE + CALLER_SITE_AREA_CODE + DIAL_STRING;
}
else if (DIAL_STRING.length == ( parseInt(CALLER_SITE_AREA_CODE.length,10)
+ parseInt(CALLER_SITE_DIGITS,10)))
{
DIAL_STRING = CALLER_SITE_COUNTRY_CODE + DIAL_STRING;
}

///////////////////////////////
// SITE BASED NUMERIC NICKNAMES (SIP)
// Allow caller to omit country and area code when calling locally.
// Assumes that country and area codes are set in site topology.
Polycom, Inc.

261

Call Server Configuration

// Assumes that all endpoints are registered with their full alias, including
// country and area code.
// sip:5551212@example.com --> sip:14045551212@example.com
if (DIAL_STRING.toLowerCase().match(/^sip:[^@]*@example\.com/))
{
user = DIAL_STRING.replace(/^sip:([^@]*)@.*/i,"$1");
if (user.length == CALLER_SITE_DIGITS)
{
user = CALLER_SITE_COUNTRY_CODE + CALLER_SITE_AREA_CODE + user;
}
else if (user.length == ( parseInt(CALLER_SITE_AREA_CODE.length,10)
+ parseInt(CALLER_SITE_DIGITS,10)))
{
user = CALLER_SITE_COUNTRY_CODE + user;
}
DIAL_STRING = "sip:" + user + "@example.com";
}

///////////////////////////////
// Limiting calls to a certain numeric dial range.
// (like the range specified Conference Settings screen)
//
var minGeneratedRoomId = 1000;
var maxGeneratedRoomId = 9999;
var number

= parseInt(DIAL_STRING.replace(/^sip:([^@]*)@?(.*)/i,"$1"));

if (NaN != number && number > minGeneratedRoomId && number < maxGeneratedRoomId)
{
return;
}
return NEXT_RULE;
////////////////////////////////
// A sample script that routes all dial-out calls from a
// whitelist of VMRs to a SIP peer with prefix 11. All other dial-out
// calls will be routed to a SIP peer with prefix 22.
// The getConferenceRoomOrID() function returns a value only when
// the call is a dial-out from a VMR or Lync scheduled conference
// to an endpoint.
var whitelist_vmrs = [
"1000",
// Specify list of VMRs; add or remove VMRs from this list.
"2000",
// Make sure you use the syntax ""
"3000",
];
var prefix = "22";

Polycom, Inc.

262

Call Server Configuration

////////////////////////////////
// Match against individual VMRs. ACCEPT if any of them matches.
//
if (0 <= whitelist_vmrs.indexOf(getConferenceRoomOrID()))
{
prefix = "11";
}
DIAL_STRING = prefix + DIAL_STRING;

See also:
Preliminary/Postliminary Scripting
Script Debugging Dialog for Preliminaries/Postliminaries

Hunt Groups
A hunt group is a set of endpoints that share an alias or aliases. Hunt groups can be used to define a dial
string shared by a group of people, such as a technical support number. When the Polycom RealPresence
DMA system Call Server resolves a dial string to the hunt group’s alias, it selects a member of the group
and tries to terminate the call to that member.
The system selects hunt group members in round-robin fashion. It skips members that are in a call or have
unconditional call forwarding enabled. If the selected group member rejects the call or doesn’t answer
before the timeout, the system tries the next group member.
If all members have been attempted (or skipped) without successfully terminating the call, the system sends
the BUSY message to the caller.
Registered endpoints can add themselves to a hunt group by dialing the vertical service code (VSC) for
joining (default is *71) followed by the hunt group alias. They can leave a hunt group by dialing the VSC for
leaving (default is *72) followed by the hunt group alias. An endpoint can belong to multiple hunt groups.
The Hunt Groups page lists the defined hunt groups and lets you add, edit, and delete hunt groups. The
following table describes the fields in the list.
Column

Description

Name

Hunt group name.

Description

Brief description of the hunt group.

Aliases

The aliases (dial strings) that resolve to this hunt group.

Members

The endpoints included in the hunt group.

Enabled

Indicates whether the hunt group is being used.

See also:
Call Server Configuration
Edit Hunt Group Dialog

Polycom, Inc.

263

Call Server Configuration

Add Hunt Group Dialog
The Add Hunt Group dialog lets you define a new hunt group in the system and add members to it. The
following table describes the fields in the dialog.
Field

Description

General Info
Name

Hunt group name.

Description

The text description displayed in the Hunt Groups list.

Enabled

Clearing this check box lets you define a new hunt group without putting it
immediately into service.

No answer timeout

Number of seconds to wait for a hunt group member to answer a call before
giving up and trying another member.

Aliases

Lists the aliases (dial strings) that resolve to this hunt group. Click Add to add
an alias. Click Edit or Delete to change or remove the selected alias.

Hunt Group Members
Search

Search for endpoints by alias, IP address, or registration status.

Available endpoints

Lists the endpoints that match the search criteria.

Member endpoints

Lists the endpoints to include in the hunt group. Use the arrow buttons to
move endpoints from one list to the other.

See also:
Hunt Groups
Add Alias Dialog
Edit Alias Dialog

Edit Hunt Group Dialog
The Edit Hunt Group dialog lets you modify the selected hunt group and add or remove members. The
following table describes the fields in the dialog.
Field

Description

General Info
Name

Hunt group name.

Description

The text description displayed in the Hunt Groups list.

Enabled

Clearing this check box lets you stop using a hunt group without deleting it.

No answer timeout

Number of seconds to wait for a hunt group member to answer a call before
giving up and trying another member.

Polycom, Inc.

264

Call Server Configuration

Field

Description

Aliases

Lists the aliases (dial strings) that resolve to this hunt group. Click Add to add
an alias. Click Edit or Delete to change or remove the selected alias.

Hunt Group Members
Search

Search for endpoints by alias, IP address, or registration status.

Available endpoints

Lists the endpoints that match the search criteria.

Member endpoints

Lists the endpoints to include in the hunt group. Use the arrow buttons to
move endpoints from one list to the other.

See also:
Dashboard

Call Server Registrations Pane
Displays the total number of active (including active quarantined) and inactive (including inactive
quarantined and blocked) endpoint registrations and the number that failed in the past 24 hours. Hover over
a registration number to see the limit.
Also displays the total number of registrations for each cluster of the supercluster. Hover over a cluster’s
total to see the breakdown between active and inactive.
Click a column heading to sort on that column. Click the Link button to go to the Endpoints page.
See also:
Dashboard

Cluster Info Pane
Displays detailed information about the selected cluster. For a two-server cluster, the pane contains a tab
for each server. The tab label indicates which server is currently active. Each tab contains the following
information about the server:
● Current time and uptime
● Server, Proxias, and application software version numbers
● Hardware model and serial number
● Time source
● Management network MAC and IP addresses
● Signaling network MAC and IP addresses (if configured for split network)
● CPU usage percentage (all cores), as reported by Hyperic SIGAR
● Memory usage (hover over the bar chart to see details)
It’s normal for memory usage to be high.
● Swap space (total and free)
● Disk space usage (actual and percentage)
● Log space usage (actual and percentage) and next scheduled log purge
Click the Link button to go to the Logging Settings page.
See also:
Dashboard

Conference History – Max Participants Pane
Displays a bar graph showing variations in the maximum number of Conference Manager conference
participants over the time span you select.
The graph shows the data for all Conference Manager clusters. The Ad-hoc participants category includes
all dial-outs and all dial-ins to non-scheduled conferences. The Other participants category includes all

Polycom, Inc.

343

System Management and Maintenance

dial-ins to conferences scheduled via Polycom Conferencing for Outlook (calendared conferences) or via
an API client such as the Polycom RealPresence Resource Manager system.
Click the Link button to go to the Conference History page.
See also:
Dashboard

Conference Manager MCUs Pane
Displays information about all the MCUs that are managed by Conference Manager to host conference
rooms (virtual meeting rooms, or VMRs).
The information shown includes the MCU’s connection and service status, its capabilities (recording, IVR,
and SVC), its reliability (in terms of disconnects and call failures), and the number of ports in use and
available to Conference Manager.
Hover over an icon to see an explanation of it. Click a column heading to sort on that column. Click the Link
button to go to the MCUs page, or click an MCU name to go to the MCUs page with that MCU selected.
Note: MCUs and conference manager
An MCU may be connected to up to three Conference Manager clusters. If one of the three
Conference Managers loses its connection to the MCU, this is counted as 0.33 disconnects. If all
connections to the MCU are lost, this is counted as 1 disconnect.

Note: MCUs and resource usage
The RealPresence DMA system reports port numbers based on CIF resource usage. Version 8.1 and
later Polycom MCUs report HD720p30 port numbers. In general, 3 CIF = 1 HD720p30, but it varies
depending on bridge/card type and other factors.
See your Polycom RMX or RealPresence Collaboration Server documentation for more detailed
information about resource usage.

See also:
Dashboard

Conference Manager Usage Pane
Displays usage information for Conference Manager, either for all Conference Manager clusters or for the
selected cluster.
The information shown includes the territories for which Conference Manager is enabled, the number of
conferences and participants, the port usage, and the number of local users and custom conference rooms.
Note: MCUs and resource usage
The RealPresence DMA system reports port numbers based on CIF resource usage. Version 8.1 and
later Polycom MCUs report HD720p30 port numbers. In general, 3 CIF = 1 HD720p30, but it varies
depending on bridge/card type and other factors.
See your Polycom RMX or RealPresence Collaboration Server documentation for more detailed
information about resource usage.

Polycom, Inc.

344

System Management and Maintenance

See also:
Dashboard

Exchange Server Integration Pane
If the Polycom RealPresence DMA system is integrated with a Microsoft Exchange server (see Microsoft
Exchange Server Integration), displays the following:
● The integration status, which can be one of the following:
 Unavailable — A service status or inter-server communication problem prevented determination
of the integration status.
 Error — The system was unable to establish a connection to the Exchange server. This could be
a network or Exchange server problem, or it could be a login failure.
 Awaiting Active Directory — The system isn’t integrated with the Active Directory, required for
Exchange server integration.
 Primary SMTP mailbox not found — The mailbox configured for the Polycom RealPresence
DMA system isn’t in the system’s Active Directory cache.
 Subscription pending — The Polycom RealPresence DMA system has asked the Exchange
server to send it notifications and is waiting to receive its first notification to confirm that the
Exchange server can communicate with the system. If this status persists for more than a minute
or so, there is likely a configuration problem (such as an invalid certificate or the Exchange server
is unable to resolve the RealPresence DMA system’s FQDN).
 Exchange authentication failed — The credentials for the Polycom RealPresence DMA
system’s mailbox are no longer valid (e.g., the password has expired).
 OK — The Polycom RealPresence DMA system is receiving and processing Polycom
Conferencing meeting notifications from the Exchange server.
● The host name or IP address for the Exchange server as entered on the Microsoft Exchange Server
page.
● The Polycom RealPresence DMA system’s mailbox address.
● The number of Polycom Conferencing meetings today.
Click the Link button to go to the Microsoft Exchange Server page.
See also:
Dashboard

Juniper Networks SRC Integration Pane
If the Polycom RealPresence DMA system is integrated with a Juniper Networks Service Resource
Controller (see Juniper Networks SRC Integration), displays the following:
● The IP address or host name of the configured SRC server.
● The configured Server port.
● The configured Client ID.
● The configured Subscriber URI.
● The average request/response interval over the last ten interactions with the configured SRC server.
Click the Link button to go to the Juniper Networks SRC page.

Polycom, Inc.

345

System Management and Maintenance

See also:
Dashboard

License Status Pane
Displays the license status of the selected cluster and the number of licensed and active calls. Note that a
call that has multiple “legs” (spans multiple clusters) uses a license for each leg of the call (each cluster it
spans).
Click the Link button to go to the Licenses page (only available if the selected cluster is the one on which
you’re logged in).
See also:
Dashboard

RealPresence Resource Manager Integration Pane
If the Polycom RealPresence DMA system is integrated with a Polycom RealPresence Resource Manager
system (see RealPresence Resource Manager Integration), displays the following:
● Host name or IP address of the RealPresence Resource Manager system.
● User name used to log into the RealPresence Resource Manager system.
● Time when site topology data was last updated from the RealPresence Resource Manager system.
● Number of territories, sites, site links, and network (MPLS) clouds in the site topology data obtained
from the RealPresence Resource Manager system.
Click the Link button to go to the RealPresence Resource Manager page.
See also:
Dashboard

Signaling Settings Pane
Displays the H.323 and SIP signaling settings for the selected cluster, including whether each is enabled
and what ports are assigned.
Click the Link button to go to the Signaling Settings page.
See also:
Dashboard

Supercluster Status Pane
Displays the status of each server in every cluster of the supercluster, the status of its private, management,
and signaling interfaces, and the territory for which it’s responsible. A territory is green if being managed by
its primary cluster, yellow if being managed by its backup cluster, and red if it’s out of service (no cluster is
managing it). Hover over a name or icon to see more details.
The icons near each server’s name in the Server column indicate the status of the server:
●

- Active primary server: This server is active, and the cluster is in service.

●

- Active backup server: This server is the backup, and the cluster is in service.

Polycom, Inc.

346

System Management and Maintenance

- Indicates one of the following:

●

 Out of service: The server is out of service. It is either offline, busied out, or an administrator has
issued the Stop Using command to this server.
 Unreachable from : The server is unreachable from one or some of the
clusters in the supercluster.
 Unreachable: The server is unreachable from all other clusters in the supercluster. During an
outage of one server in a two-server supercluster, the server that is in service will show this status.
Click the Link button to go to the DMAs page.
See also:
Dashboard

Territory Status Pane
Lists each territory, its capabilities, and the primary and backup cluster responsible for it. Hover over the
territory name to see more details. The territories are color-coded, each color with its own tooltips:
● Green: Active on primary cluster - The primary cluster for the territory is in service. The backup
cluster may or may not be assigned.
● Yellow: Indicates one of the following:
 Active on primary cluster - The primary cluster for the territory is unreachable from some
clusters including the backup cluster. The backup cluster is not in service or is not assigned.
 Active on backup cluster - The primary cluster for the territory is not in service or not assigned,
but the backup cluster is in service.
 Active on both primary and backup clusters - The primary cluster for the territory is
unreachable from some clusters including the backup cluster, and the backup cluster is in service.
The ownership of the territory is split between the primary and backup clusters.
● Red: Indicates one of the following:
 Not active; associated clusters not in service - A primary or backup cluster is assigned to the
territory (or both), but neither the primary nor the backup cluster are in service.
 Not active; no primary or backup cluster assigned - No clusters are assigned to the territory.
Hover over a cluster name to see more details. Note that a cluster is considered in service if it is reachable
from the backup cluster, even it is unreachable from some of the other clusters. A cluster is considered not
in service if it has been given the Stop Using command, is busied out, or is unreachable.
Hover over a capabilities icon to see an explanation of it. Click a column heading to sort on that column.
Click the Link button to go to the Territories page.
See also:
Dashboard

User Login History Pane
Displays the following information about logins by your user ID:
● The server you’re currently logged in to.
● The time, date, server logged in to, and source (host name or IP address) of the last successful login
(prior to your current session) by your user ID.

Polycom, Inc.

347

System Management and Maintenance

● The time, date, server, and source of the last failed login attempt by your user ID.
● The number of consecutive failures before your current successful login.
See also:
Dashboard

Alerts
On various pages and dashboard panes, the alert icon is used to indicate an abnormal condition, problem,
or just something you should be aware of. Hover over the icon to see details.
A summary of alert status appears in the menu bar, showing how many alerts exist across all clusters of a
supercluster and how many are new (that is, that you haven’t viewed yet).
When you click the summary data, an expanded alerts list appears, displaying the date and time, alert code,
and description of each alert. In many cases, the alert description is a link to the relevant page for
investigating the issue. A Help button to the right of the alert description displays the help topic for that alert,
which contains additional information about the causes and recommendations for dealing with the alert.
The following topics describe the alerts by category, followed by what alerts are contained in the category:
● Supercluster Status (1000 series)
● Territory Status (1100 series)
● Asynchronous Operation (1200 series)
● RealPresence Resource Manager System Integration (2000 series)
● Active Directory Integration (2100 series)
● Exchange Server Integration (2200 series)
● Database Status (2400 series)
● Lync Integration (2600 series)
● Signaling (3000 series)
● Certificate (3100 series)
● Licenses (3200 series)
● Networks (3300 series)
● Server Resources (3400 series)
● Data Synchronization (3600 series)
● System Health and Availability (3800 series)
● MCUs (4000 series)
● Endpoints (5000 series)
● Conference Manager (6000 series)
● Conference Status (6100 series)
● Lync Presence Publishing (6200 series)
● Call Server (7000 series)
● Call Bandwidth Management (7100 series)

Polycom, Inc.

348

System Management and Maintenance

Supercluster Status
The following alerts provide information on changes in cluster and supercluster status.

Alert 1001
Cluster is busied out as of YYYY-MM-DD HH:MM GMT+/-H[:MM].
You or another administrator busied out the cluster, perhaps for maintenance.
A busied-out cluster allows existing calls and conferences to continue and accepts new calls for existing
conferences, but doesn’t accept other new calls and conferences.
Once all existing calls and conferences have ended, the cluster is out of service.
Click the link to go to the DMAs page.
See also:
Alerts

Alert 1002
Cluster is out of service as of YYYY-MM-DD HH:MM GMT+/-H[:MM].
You or another administrator took the cluster out of service (or busied out the cluster, and now all calls and
conferences have ended).
An out-of-service cluster is still running and accessible via the management interface, but doesn’t accept
any calls or registrations.
Click the link to go to the DMAs page.
See also:
Alerts

Alert 1003
Cluster is orphaned.
The replication link with the specified cluster seems to be corrupted.
Click the link to go to the DMAs page. Try removing that cluster from the supercluster and then rejoining.
See also:
Alerts

Alert 1004
Cluster is not reachable. Last heartbeat received YYYY-MM-DD HH:MM
GMT+/-H[:MM].
The specified cluster is not sending scheduled heartbeats. Possible reasons include:
● The cluster may simply be very busy and have fallen behind in sending heartbeats.
● An internal process could be stuck.
● The server(s) may be offline or rebooting.
Polycom, Inc.

349

System Management and Maintenance

● There may be a network problem.
Click the link to go to the DMAs page.
See also:
Alerts

Territory Status
The following alerts provide information on changes in territory status.

Alert 1103
No clusters assigned to .
The specified territory or territories are not assigned to a cluster, so any responsibilities assigned to the
territories are not being fulfilled.
Click the link to go to the Territories page. Assign a primary and backup cluster for every territory in your
site topology.
See also:
Alerts

Alert 1105
: Primary cluster and backup cluster are not
reachable. Territory may not be functioning.
The cluster from which the alert originated is unable to communicate with the specified territory’s primary
and backup clusters.
This may be a temporary problem, in which case this alert will be cleared as soon as the alerting cluster is
once again able to communicate with the clusters in question.
If this alert reoccurs frequently but quickly goes away, that suggests intermittent spurious network problems.
If it persists for more than about 15-30 seconds, it may indicate serious network problems. It’s also possible
that someone shut both clusters down, or shut down one and the other then failed, or both failed (unlikely).
Click the link to go to the Territories page. To enable conferencing to continue in the territory (at diminished
capacity), assign it to some other cluster.
See also:
Alerts

Alert 1106
: Cluster is not reachable. Territory may not be
functioning.
The cluster from which the alert originated is unable to communicate with the specified territory’s primary
cluster, and there is no backup cluster.
This may be a temporary problem, in which case this alert will be cleared as soon as the alerting cluster is
once again able to communicate with the cluster in question.

Polycom, Inc.

350

System Management and Maintenance

If this alert reoccurs frequently but quickly goes away, that suggests intermittent spurious network problems.
If it persists for more than about 15-30 seconds, it may indicate serious network problems. It’s also possible
that someone shut the cluster down or that it failed.
Click the link to go to the Territories page. To enable conferencing to continue in the territory (at diminished
capacity), assign it to some other cluster.
We recommend assigning a backup cluster for each territory.
See also:
Alerts

Alert 1107
: Primary cluster associated with territory is not
reachable. But backup cluster is reachable.
The cluster from which the alert originated is unable to communicate with the specified territory’s primary
cluster, but can communicate with the backup cluster.
This may be a temporary problem, in which case this alert will be cleared as soon as the alerting cluster is
once again able to communicate with the cluster in question.
If this alert reoccurs frequently but quickly goes away, that suggests intermittent network problems. If it
persists, it will be followed by Alert 1108, indicating that the territory has failed over to the backup cluster.
The backup cluster allows conferencing to continue in the territory (at diminished capacity) and fulfills any
other responsibilities assigned to the territory.
Click the link to go to the Territories page. Determine whether the cluster was deliberately shut down. If not,
try pinging the cluster’s IP addresses.
If this is a two-server cluster, and you can’t ping either the virtual or physical IP addresses, look for a network
problem. It’s unlikely that both servers have failed simultaneously.
If you can ping the cluster, the OS is running, but the application may be in a bad state. Try rebooting the
server(s).
See also:
Alerts

Alert 1108
: Territory has failed over from to .
The territory’s primary cluster is unreachable, and its backup cluster has taken over.
This may indicate a network problem. It’s also possible that someone shut the cluster down or that it failed.
The backup cluster allows conferencing to continue in the territory (at diminished capacity) and fulfills any
other responsibilities assigned to the territory.
Click the link to go to the Territories page. Determine whether the cluster was deliberately shut down. If not,
try pinging the cluster’s IP addresses.
If this is a two-server cluster, and you can’t ping either the virtual or physical IP addresses, look for a network
problem. It’s unlikely that both servers have failed simultaneously.

Polycom, Inc.

351

System Management and Maintenance

If you can ping the cluster, the OS is running, but the application may be in a bad state. Try rebooting the
server(s).
See also:
Alerts

Asynchronous Operation
The following alerts provide information on asynchronous states between servers in a cluster or
supercluster.

Alert 1201
Configuration synchronization checking was initiated by on at
and is currently in progress.
The specified user started a configuration synchronization checking procedure on the specified server. The
procedure is currently running; the system clears this alert when checking is complete. See Check
Configuration Synchronization for information on this operation and where to find the output from the
procedure.
Click the link to go to the Network > DMAs page.
See also:
Alerts

RealPresence Resource Manager System Integration
The following alerts provide information on RealPresence Resource Manager system integration events and
changes in integration status.

Alert 2001

An error occurred when the cluster responsible for RealPresence Resource Manager integration tried to
synchronized data with the Polycom RealPresence Resource Manager system. The alert text describes the
nature of the problem, which may require remedial action on the Polycom RealPresence Resource Manager
system.
See also:
Alerts

Alert 2002
Resource management system unreachable. Last contact on:
YYYY-MM-DD HH:MM GMT+/-H[:MM].
The cluster responsible for RealPresence Resource Manager integration was unable to connect to the
Polycom RealPresence Resource Manager system.
This may indicate a network problem or a problem with the Polycom RealPresence Resource Manager
system.

Polycom, Inc.

352

System Management and Maintenance

Try logging into the Polycom RealPresence Resource Manager system. If you can do so, make sure the
login credentials that the RealPresence DMA system uses to connect to it are still valid.
See also:
Alerts

Alert 2004
Resource management server has inconsistent territory definitions in its
site topology.
The system is integrated with a Polycom RealPresence Resource Manager system, and there is a problem
with the territory definitions or responsibility assignments in the site topology data imported from that
system.
On the Polycom RealPresence Resource Manager system, configure territories properly (for instance, no
duplicate names) and in way that meets the needs of the RealPresence DMA system. Assign
responsibilities (primary and backup) for the territories to the appropriate RealPresence DMA clusters. A
territory can only host conference rooms if it’s assigned to a RealPresence DMA cluster.
See also:
Alerts

Active Directory Integration
The following alerts provide information on changes in Active Directory integration status.

Alert 2101
Active Directory user and group cache update was not successful on cluster .
The cluster responsible for Active Directory integration was unable to update the cache of user and group
data.
This may indicate a network problem or a problem with the AD.
If the cluster was unable to log into the AD server, alert 2107 is also generated.
Click the link to go to the Microsoft Active Directory page and check the Active Directory Connection
section.
See also:
Alerts

Alert 2102
Zero enterprise conference rooms exist on cluster .
The cluster responsible for Active Directory integration successfully retrieved user and group data, but no
conference rooms were generated.
This may indicate that no directory attribute was specified from which to generate conference room IDs, or
that the chosen attribute resulted in empty (null) conference room IDs after the system removed the
characters to remove.

Polycom, Inc.

353

System Management and Maintenance

Click the link to go to the Microsoft Active Directory page and check the Enterprise Conference Room
ID Generation section. If necessary, check the Active Directory and determine an appropriate directory
attribute to use.
See also:
Alerts

Alert 2104
Active Directory service is not available. Both primary cluster and backup
cluster are not operational.
The primary and backup cluster for the territory responsible for Active Directory integration are both
unreachable.
This may indicate serious network problems. It’s also possible that someone shut both clusters down, or
shut down one and the other then failed, or both failed (unlikely).
Click the link to go to the DMAs page to begin troubleshooting. Determine whether the clusters were
deliberately shut down. If not, try pinging the clusters’ IP addresses.
Other clusters can continue using the shared data store from the last cache update, so there is no immediate
AD-related problem. But the unavailable clusters probably have other territory-related responsibilities
(Conference Manager and/or Call Server), so you may need to assign the affected territory to some other
cluster(s).
See also:
Alerts

Alert 2105
Active Directory service is not available. Cluster is not operational.
The primary cluster for the territory responsible for Active Directory integration is unreachable, and it has no
backup cluster.
This may indicate a network problem. It’s also possible that someone shut the cluster down or that it failed.
Click the link to go to the DMAs page to begin troubleshooting. Determine whether the cluster was
deliberately shut down. If not, try pinging the cluster’s IP addresses.
Other clusters can continue using the shared data store from the last cache update, so there is no immediate
AD-related problem. But the unavailable cluster probably has other territory-related responsibilities
(Conference Manager and/or Call Server), so you may need to assign the affected territory to some other
cluster.
We recommend assigning a backup cluster for each territory.
See also:
Alerts

Polycom, Inc.

354

System Management and Maintenance

Alert 2106
Cluster : Failed connection from to Active Directory for user
authentications at YYYY-MM-DD HH:MM GMT+/-H[:MM].
The specified server tried to connect to the Active Directory in order to authenticate a user’s credentials and
was unable to do so. This may indicate a network problem or a problem with the AD itself.
If the network and the AD itself both appear to be OK, the connection attempt may have failed because the
cluster was unable to log into the AD server.
Click the link to go to the Microsoft Active Directory page. Make sure the login credentials that the
RealPresence DMA system uses to connect to Active Directory are still valid and update them if necessary.
See also:
Alerts

Alert 2107
Failed connection from to Active Directory for user caching at YYYY-MM-DD
HH:MM GMT+/-H[:MM].
The cluster responsible for Active Directory integration was unable to log into the AD server.
Click the link to go to the Microsoft Active Directory page.
See also:
Alerts

Alert 2108
: Active Directory primary cluster associated with territory
is not reachable. But backup cluster is reachable.
The territory’s primary cluster assigned to do Active Directory integration is not reachable. The territory’s
backup cluster assigned to do Active Directory integration is reachable.
This may indicate a network problem. It’s also possible that someone shut the primary cluster down or that
it failed.
Click the link to go to the Network > DMAs page. Log in to the affected cluster, if possible, and check the
health of the cluster. Determine whether the cluster was deliberately shut down. If not, try pinging the
cluster’s IP addresses.
See also
Alerts

Exchange Server Integration
The following alerts provide information on changes in Exchange server integration status.

Polycom, Inc.

355

System Management and Maintenance

Alert 2201
Exchange server integration primary cluster is not operational. Integration by
backup cluster .
The primary cluster for the territory responsible for Exchange server integration is unreachable, and its
backup cluster has taken over responsibility for monitoring the Polycom Conferencing user mailbox and
accepting or declining the meeting invitations received.
This may indicate a network problem. It’s also possible that someone shut the cluster down or that it failed.
Click the link to go to the DMAs page to begin troubleshooting.
See also:
Alerts

Alert 2202
Exchange server integration is not available. Both primary cluster and backup
cluster are not operational.
The primary and backup clusters for the territory responsible for Exchange server integration are both
unreachable.
This may indicate serious network problems. It’s also possible that someone shut both clusters down, or
shut down one and the other then failed, or both failed (unlikely).
Click the link to go to the DMAs page to begin troubleshooting. Determine whether the clusters were
deliberately shut down. If not, try pinging the clusters’ IP addresses.
See also:
Alerts

Alert 2203
Exchange server integration is not available. Cluster is not operational.
The primary cluster for the territory responsible for Exchange server integration is unreachable, and it has
no backup cluster.
This may indicate a network problem. It’s also possible that someone shut the cluster down or that it failed.
Click the link to go to the DMAs page to begin troubleshooting.
See also:
Alerts

Database Status
The following alerts provide information on database events and changes in database status.

Polycom, Inc.

356

System Management and Maintenance

Alert 2401
Connection to the history/audit database for cluster has failed.
The specified cluster is unable to communicate with its shared call history database. This may indicate a
network problem, or a software failure within the cluster. The server(s) may need to be rebooted.
Go to the DMAs page to begin troubleshooting.
See also:
Alerts

Alert 2402
Connection to the configuration database for cluster has failed.
The specified cluster is unable to communicate with its shared configuration database. This may indicate a
network problem, or a software failure within the cluster. The server(s) may need to be rebooted.
Go to the DMAs page to begin troubleshooting.
See also:
Alerts

Lync Integration
The following alerts provide information on changes in Microsoft Lync 2013 integration.

Alert 2601
Cluster : Cannot reach Lync server for presence publishing.
The cluster cannot communicate with the specified Lync server at the currently configured Next hop
address. This could indicate a network problem, or a problem with the Lync server.
Click the link to go to the Network > External SIP Peers page to begin troubleshooting. Try to ping the Lync
server’s Next hop address to verify basic connectivity.
See also:
Alerts

Alert 2602
Cluster : Cannot authenticate with for presence publishing.
The cluster cannot authenticate with the specified Lync server; presence will not be published for Polycom
conference contacts.
This could indicate incorrect RealPresence DMA system or Lync server configuration. Begin
troubleshooting by verifying that the Presence Publishing settings on the Admin > Conference Manager
> Conference Settings page are correct.
Click the link to go to the Network > External SIP Peers page.
See also:
Alerts
Polycom, Inc.

357

System Management and Maintenance

Alert 2603
Cluster : Invalid Lync account URI configured for Lync server .
The system is unable to authenticate with the Lync server using the currently configured Lync account URI.
Click the link to go to the Network > External SIP Peers page to begin troubleshooting. Try reentering the
Lync account URI for the Lync server in the External SIP Peer configuration area.
See also:
Alerts

Alert 2604
Cluster : Cannot reach Lync server to resolve conference IDs for
RealConnectTM conferences.
The system is unable to connect to the specified Lync server at the currently configured Next hop address.
Attempts to connect to a Lync conference through the RealPresence DMA system will fail.
This could indicate a network problem, or that someone has shut down the Lync server.
Click the link to go to the Network > External SIP Peers page to begin troubleshooting. Try pinging the
specified Lync server’s IP address. If it is reachable, verify that the Next hop address, Port, and Transport
type settings on this page are correct.
See also:
Alerts

Alert 2605
Cluster : Cannot authenticate with to resolve conference IDs for
RealConnectTM conferences.
The system can’t authenticate with the specified Lync server, preventing RealConnectTM conference ID
resolution. Attempts to connect to RealConnectTM conferences through the RealPresence DMA system will
fail.
Click the link to go to the Network > External SIP Peers page to begin troubleshooting. Verify that the
Transport Type is set to TLS, and that the Lync account URI on the Lync Integration tab is correct. If the
RealPresence DMA system configuration is correct, investigate the Lync server’s configuration.
See also:
Alerts

Signaling
The following alerts provide information on signaling events and changes in signaling status.

Alert 3001
No signaling interface enabled for cluster . SIP or H.323 must be configured to
allow calls.
The specified cluster has neither H.323 nor SIP signaling enabled and is unable to accept calls.
Polycom, Inc.

358

System Management and Maintenance

To use the cluster for anything other than logging into the management interface, you must enable signaling.
If you’re logged in to that cluster, click the link to go to the Signaling Settings page. If not, log into that
cluster and go to Admin > Local Cluster > Signaling Settings.
See also:
Alerts

Certificate
The following alerts provide information on changes in certificate status such as certificate expirations and
incompatibilities.

Alert 3101
Cluster : The server certificate has expired.
The specified cluster’s server certificate has expired. This is the public certificate that the cluster uses to
identify itself to devices configured for secure communication. The cluster can no longer communicate with
any such devices, including MCUs, endpoints, the AD server, and the Exchange server.
If you’re logged in to that cluster, click the link to go to the Certificates page. If not, log into that cluster (your
browser will warn you not to do this, and you’ll have to override its advice) and go to Admin > Local Cluster
> Certificates.
See also:
Alerts

Alert 3102
Cluster : The server certificate will expire within 1 day. All system access may be
lost.
The specified cluster’s server certificate is about to expire. This is the public certificate that the cluster uses
to identify itself to devices configured for secure communication. If you allow it to expire, the cluster will no
longer be able to communicate with any such devices, including MCUs, endpoints, the AD server, and the
Exchange server.
If you’re logged in to that cluster, click the link to go to the Certificates page. If not, log into that cluster and
go to Admin > Local Cluster > Certificates.
See also:
Alerts

Alert 3103
Cluster : The server certificate will expire within days. All system
access may be lost.
The specified cluster’s server certificate will soon expire. This is the public certificate that the cluster uses
to identify itself to devices configured for secure communication. If you allow it to expire, the cluster will no
longer be able to communicate with any such devices, including MCUs, endpoints, the AD server, and the
Exchange server.

Polycom, Inc.

359

System Management and Maintenance

If you’re logged in to that cluster, click the link to go to the Certificates page. If not, log into that cluster and
go to Admin > Local Cluster > Certificates.
See also:
Alerts

Alert 3104
Cluster : One or more CA certificates have expired.
The specified cluster has an expired CA certificate or certificates. When a CA certificate expires, the
certificates signed by that certificate authority are no longer accepted. Depending on its security settings,
the cluster may refuse connections from devices presenting a certificate signed by a CA whose certificate
has expired, including MCUs, endpoints, the AD server, and the Exchange server.
If you’re logged in to that cluster, click the link to go to the Certificates page. If not, log into that cluster and
go to Admin > Local Cluster > Certificates.
If that cluster has Skip validation of certificates for inbound connections turned off, you won’t be able
to log into it. Contact Polycom Global Services.
See also:
Alerts

Alert 3105
Cluster : One or more CA certificates will expire within 30 days.
The specified cluster has a CA certificate or certificates that will expire soon. When a CA certificate expires,
the certificates signed by that certificate authority are no longer accepted. If you allow the CA certificate(s)
to expire, depending on its security settings, the cluster may refuse connections from any devices
presenting a certificate signed by a CA whose certificate has expired, including MCUs, endpoints, the AD
server, and the Exchange server.
If you’re logged in to that cluster, click the link to go to the Certificates page. If not, log into that cluster and
go to Admin > Local Cluster > Certificates.
See also:
Alerts

Alert 3108
Cluster : The server SSL certificate is incompatible with the cluster's network
settings.
The specified server’s SSL certificate does not match the cluster’s domain information or other network
configuration. Perhaps the network configuration was changed, and the SSL certificate is now out of date.
If you’re logged in to that cluster, click the link to go to the Certificates page. If not, log in to that cluster and
go to Admin > Local Cluster > Certificates. Try regenerating the SSL certificate in question.
See also:
Alerts

Polycom, Inc.

360

System Management and Maintenance

Licenses
The following alerts provide information on changes in licensing status.

Alert 3201
Cluster has no license key(s). System will allow up to 10 concurrent calls.
You haven’t entered the license key(s) for the specified cluster.
If you’re logged in to that cluster, click the link to go to the Licenses page. If not, log into that cluster and go
to Admin > Local Cluster > Licenses.
Without a valid license, the cluster is limited to ten simultaneous calls.
See also:
Alerts

Alert 3202
Invalid license key(s) applied to cluster . System will allow up to 10 concurrent
calls.
The specified cluster has an invalid license key or keys.
If you’re logged in to that cluster, click the link to go to the Licenses page. If not, log into that cluster and go
to Admin > Local Cluster > Licenses.
Without a valid license, the cluster is limited to ten simultaneous calls.
See also:
Alerts

Alert 3203
The EULA for cluster has not been accepted. All calls are blocked on this
cluster.
The system version has changed, and the End User License Agreement has not yet been accepted. The
specified cluster won’t accept any inbound calls, or place outbound calls, until a user with Administrator
privileges accepts the agreement upon login.
Click the link to go to the Licenses page, where you can view the EULA acceptance status and details.
See also:
Alerts

Alert 3204
Cluster : Cannot connect to licensing server .
The specified cluster cannot connect to the licensing server, or there is no licensing server configured for
this cluster.
If you’re logged in to that cluster, click the link to go to the Licenses page to view licensing details. Check
the status of licensing by logging in to the RealPresence Platform Director system

Polycom, Inc.

361

System Management and Maintenance

Garmin 7000 Polycom RealPresence DMA System Operations Guide User Manual To The 156a113a E3cd 4b93 B579 00256a680052

Navigation menu

Versions of this User Manual:

Views

Navigation