Polycom RealPresence DMA 7000 System Operation Manual

Table of Contents

Quick Links

Download this manual

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.

Table of Contents

Summary of Contents for Polycom RealPresence DMA 7000 System

Page 1 Operations Guide 6.2 | December 2014 | 3725-76302-001P ® ® ® Polycom RealPresence 7000 System The Polycom RealPresence DMA 7000 System is also known and certified as the DMA System.
Page 2: Limitation Of Liability
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.
Page 3: Table Of Contents
License the Polycom RealPresence DMA System ....... . . 30...
Page 4 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 .
Page 5 Names/Aliases in a Mixed H.323 and SIP Environment ......92 Naming ITP Systems Properly for Recognition by the Polycom RealPresence DMA System Add Endpoint Dialog .
Page 6 Polycom Solution and Integration Support ........
Page 7 Class of Service ............186 Default Polycom Conference Contacts Presence Settings ..... . . 186 Remove Contacts from Active Directory Dialog .
Page 8 Add Site Dialog ............286 Polycom, Inc.
Page 9 Management and Maintenance Overview ........337 Polycom, Inc.
Page 10 Certificate ............359 Polycom, Inc.
Page 11 Diagnostics for your Polycom Server ........
Page 12 Exporting Network Usage Data ..........427 Polycom RealPresence DMA System SNMP Support ....430 SNMP Overview .
Page 13: Polycom Realpresence Dma
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...
Page 14 (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.
Page 15 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.
Page 16: The Polycom Realpresence Dma System's Three Configurations
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).
Page 17 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.
Page 18: System Capabilities And Constraints
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.
Page 19: System Port Usage
 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...
Page 20 HTTPS. Upgrade status monitoring (only while upgrade process is running). 36000-61000 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 HTTP.
Page 21: Polycom Solution Support
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.
Page 22: Settings Dialog
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).
Page 23 Call History • • • Conference History • • • Registration History • • • Network Usage • • • Microsoft Active Directory Integration • Enterprise Passcode Errors Orphaned Groups and Users • • • Conference Room Errors Polycom, Inc.
Page 24 Registration Policy • Device Authentication • • • Prefix Service Embedded DNS • History Retention Settings • • Admin > Integrations > Microsoft Active Directory • Microsoft Exchange Server • RealPresence Resource Manager • Juniper Networks SRC • Polycom, Inc.
Page 25 Help Contents • • • - Settings. Displays Settings dialog. • • • - Log Out. Logs you out of the Polycom RealPresence DMA • • • system. - Help. Opens the online help topic for the page you’re • •...
Page 26: Open Source Software
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.
Page 27: Polycom Realpresence Dma System Initial Configuration Summary
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.
Page 28: Add Required Dns Records For The Polycom Realpresence Dma System
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): ●...
Page 29: Additional Dns Records For The H.323 Gatekeeper
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.
Page 30: Verify That Dns Is Working For All Addresses
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: ●...
Page 31: License The Realpresence Dma System, Virtual Edition
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.
Page 32: Configure The Call Server And Optionally Create A Supercluster
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...
Page 33: Set Up Mcus
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...
Page 34: Connect To Microsoft Active Directory
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 ®...
Page 35: Set Up Conference Templates
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.
Page 36: Test The System
● 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: ●...
Page 37: System Security
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.
Page 38: How Certificates Are Used By The Polycom Realpresence Dma System
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).
Page 39 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.
Page 40: Frequently Asked Questions
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.
Page 41: Certificate Settings
(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.
Page 42: 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.
Page 43: Add Certificates Dialog
Subject Alternative Additional identities bound to the subject of the certificate. Names 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.
Page 44: Certificate Procedures
● 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).
Page 45: Create A Certificate Signing Request In The Realpresence Dma System
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.
Page 46: Install A Certificate In The Realpresence Dma System
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:...
Page 47: Remove A Certificate From The Realpresence Dma System
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.
Page 48: 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.
Page 49 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.
Page 50 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.
Page 51 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.
Page 52 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).
Page 53: The Consequences Of Enabling Maximum Security Mode
● 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.
Page 54 ● 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.
Page 55: Enabling File Uploads In Maximum Security With Mozilla Firefox
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.
Page 56: Local Password
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.
Page 57: Local User Account
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 Turns on disabling of inactive accounts and lets you specify the inactivity threshold (days) threshold that triggers disabling. See also: System Security Login Policy Settings Polycom, Inc.
Page 58: Banner
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.
Page 59: Reset System 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.
Page 60 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.
Page 61: Local Cluster Configuration
These are cluster-specific settings that are not part of the data store shared across superclustered systems. 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.
Page 62 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...
Page 63 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.
Page 64 Show Link Details Click to see details about link settings and information. This information may be useful to Polycom Global Services when troubleshooting a network issue. LAN Security Settings 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.
Page 65 IP addresses of up to three domain name servers. At least one DNS server is required. DNS 2 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 DNS 3 create A and/or AAAA records for IPv4 and IPv6, respectively, as well as the corresponding PTR records, on your DNS server(s).
Page 66: Routing Configuration Dialog
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.
Page 67: Time Settings
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.
Page 68: Licenses
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.
Page 69: Licenses For The Virtual Edition
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.
Page 70: Signaling Settings
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.
Page 71 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...
Page 72 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.
Page 73 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.
Page 74: Add Guest Port Dialog
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.
Page 75: Edit Guest Port Dialog
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.
Page 76: Add Guest Prefix Dialog
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.
Page 77: Edit Guest Prefix Dialog
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.
Page 78: Alerting Settings
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.
Page 79: Local Cluster Configuration Procedures
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.
Page 80 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:...
Page 81: Configure Signaling
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 >...
Page 82 Add one or more dial rules to be used for routing “unauthorized” or “guest” calls. See Dial Rules. An unauthorized call rule can route calls to a conference room ID (virtual meeting room, or VMR), a virtual entry queue (VEQ), or a SIP peer. Polycom, Inc.
Page 83: Configure Logging
The system sends the data once per hour over a secured (TLS) connection to a Polycom collection point (customerusagedatacollection.polycom.com). There is no access by any customer or others to view the data received at the collection point. The raw data will be viewable only by Polycom. To avoid any impact to Polycom, Inc.
Page 84: Enable Or Disable Automatic Data Collection
System serial numbers and license information are sent without anonymization and may be used to help improve customer experiences. In total, less than 100KB of data per hour is collected and sent. Polycom’s collection and use of this data complies with Polycom’s Privacy Policy.
Page 85: Device Management
Device Management This section describes the following Polycom ® RealPresence ® Distributed Media Application™ (DMA ® 7000 system’s network device management pages: Active Calls ● Endpoints ● Site Statistics ● Site Link Statistics ● External Gatekeeper ● External SIP Peer ●...
Page 86: Call Details Dialog
It provides detailed information about the selected call. Keep in mind that some of the settings on the Call Server Settings page can affect the values reflected for a call. The following table describes the fields in the dialog. Polycom, Inc.
Page 87 Status (active/ended and pinned/unpinned) • Start time and end time • Duration • Signaling protocol(s) • Polycom RealPresence DMA server(s) involved • Unique call ID • Dial string, if available • Final dial string (after processing by dial rules) Originator Displays the source device’s:...
Page 88 Note: If the system is configured to let devices subscribe to a conference without being participants in the conference (see Security Settings), the call history doesn’t include data for such non-participant subscriptions. But be aware that a subscription to a conference by a non-participant consumes a call license. Polycom, Inc.
Page 89: Endpoints
See also: Active Calls Endpoints The Endpoints page provides access to information about the devices known to the Polycom RealPresence DMA system. From it, you can: ● View details about a device. ● View the call history or registration history of a device.
Page 90 Admission Policy Indicates the admission policy applied to the device: • Allow • Block • Quarantine • Reject Compliance Level Indicates whether the device is compliant or noncompliant with the applicable registration policy script (see Registration Policy). Polycom, Inc.
Page 91 Opens the Edit Endpoint dialog for the selected endpoint, where you can change its information and settings. If multiple endpoints are selected, opens the Edit Endpoint dialog, where you can change the device authentication, permanent registration, and class of service settings. Polycom, Inc.
Page 92: Names/Aliases In A Mixed H.323 And Sip Environment
Names/Aliases in a Mixed H.323 and SIP Environment An endpoint that supports both H.323 and SIP can register with the Polycom RealPresence DMA system’s gatekeeper and SIP registrar using the same name/alias. When the RealPresence DMA system receives a call for that endpoint, it uses the protocol of the calling endpoint.
Page 93: Naming Itp Systems Properly For Recognition By The Polycom Realpresence Dma System
A Polycom Immersive Telepresence (ITP) room system contains multiple displays and codecs (endpoints). If the ITP system is using SIP or H.323 signaling (not Cisco TIP signaling), then in order for the Polycom RealPresence DMA system to recognize these devices as part of an ITP system, they must have names that properly identify them.
Page 94: Add Endpoint Dialog
The minimum bit rate to which calls from this device can be downspeeded to rate (kbps) manage bandwidth. If this minimum isn’t available, the call is dropped. Model Optional model number/name for the device. Version Optional version information for the device. Polycom, Inc.
Page 95: Edit Device Dialog
If the device doesn’t answer, forward calls to the specified alias. Registered endpoints can activate this feature by dialing the vertical service code (VSC) for it (default is *73) followed by the alias. They can deactivate it by dialing the VSC alone. Polycom, Inc.
Page 96: Edit Devices Dialog
If this minimum isn’t available, the call is dropped. Alert when endpoint If one of the selected devices unregisters from the Call Server or its registration unregisters expires, an informational alert is triggered (see Alert 5003). See also: Endpoints Edit Device Dialog Polycom, Inc.
Page 97: Add Alias Dialog
See also: Endpoints Site Statistics The Site Statistics page lists the sites defined in the Polycom RealPresence DMA system’s site topology and, for those controlled by the system, traffic and QoS statistics. Network clouds and the default internet site aren’t included.
Page 98: Site Link Statistics
Sites Site Link Statistics The Site Link Statistics page lists the site links defined in the Polycom RealPresence DMA system’s site topology and, for those controlled by the system, traffic and QoS statistics. The following table describes the fields in the list.
Page 99: External Gatekeeper
But note that a Polycom RealPresence DMA supercluster can manage multiple locations as a single H.323 zone, with the clusters acting as a single virtual gatekeeper. This allows the gatekeeper function to be geographically distributed, but managed centrally.
Page 100: Add External Gatekeeper Dialog
Prefer routed If selected (the default), the system forces all calls to this gatekeeper to routed mode. This setting must be enabled to avoid interoperability issues with Polycom CMA and Avaya gatekeepers, and possibly others as well. Authentication Mode In this section, you can configure the system to send its H.235 credentials when it sends address resolution requests to that gatekeeper.
Page 101: Edit External Gatekeeper Dialog
Enabled Clearing this check box lets you stop sending H.235 credentials to the external gatekeeper without deleting them. Name The H.235 name of the Polycom RealPresence DMA system. Password The H.235 password for the Polycom RealPresence DMA system. Confirm password Algorithm Select the encryption algorithm for H.235 authentication.
Page 102 Prefer routed If selected (the default), the system forces all calls to this gatekeeper to routed mode. This setting must be enabled to avoid interoperability issues with Polycom CMA and Avaya gatekeepers, and possibly others as well. Authentication Mode In this section, you can configure the system to send its H.235 credentials when it sends address resolution requests to that gatekeeper.
Page 103: External Sip Peer
This is a supercluster-wide configuration. But note that a Polycom RealPresence DMA system supercluster can provide proxy service for any or all domains in the enterprise, allowing the SIP function to be distributed, but managed centrally.
Page 104: Add External Sip Peer Dialog
Selecting Microsoft implicitly adds the Destination network value to the Domain List (if not already there) and automatically selects the Postliminary settings that are correct for most deployments in Microsoft environments, but you can modify them if necessary. Note: Selecting Microsoft enables the Lync Integration tab. Polycom, Inc.
Page 105 If Type is set to Microsoft, this field is required and is used for the peer’s domain. ™ Note: This field is used as the SIP domain for Polycom RealConnect conferences. Port The SIP signaling port number. Defaults to the standard UDP/TCP port, 5060.
Page 106 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...
Page 107 Resolve to external SIP peer action. If another dial rule action, such as Resolve to external address, is applied to the call, there is no association to this peer and its authentication settings aren’t used. Polycom, Inc.
Page 108 Admin > Conference Manager > Conference Settings page will be blank. The maximum Polycom conference contacts to publish is 25,000. Enable RealConnect Indicates whether or not this Lync SIP peer should be cascaded with Polycom conferences MCUs for Polycom RealConnect conferences. If enabled, this Lync SIP peer will be used to resolve Lync conference IDs.
Page 109: Edit External Sip Peer Dialog
Selecting Microsoft implicitly adds the Destination network value to the Domain List (if not already there) and automatically selects the Postliminary settings that are correct for most deployments in Microsoft environments, but you can modify them if necessary. Polycom, Inc.
Page 110 If Type is set to Microsoft, this field is required and is used for the peer’s domain. ™ Note: This field is used as the SIP domain for Polycom RealConnect conferences. Port The SIP signaling port number. Defaults to the standard UDP/TCP port, 5060.
Page 111 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...
Page 112 Resolve to external SIP peer action. If another dial rule action, such as Resolve to external address, is applied to the call, there is no association to this peer and its authentication settings aren’t used. Polycom, Inc.
Page 113 Admin > Conference Manager > Conference Settings page will be blank. The maximum Polycom conference contacts to publish is 25,000. Enable RealConnect Indicates whether or not this Lync SIP peer should be cascaded with Polycom conferences MCUs for Polycom RealConnect conferences. If enabled, this Lync SIP peer will be used to resolve Lync conference IDs.
Page 114: Sip Peer Postliminary Output Format Options
Use original request’s To — The To header from the original request is copied and used as is. Equivalent to template: "#otdisplay#" <#otscheme#:#otuser#@#othost#> No Display, use original request’s To — The To header from the original request is copied and used. If a display parameter is present, it’s removed. Equivalent to template: <#otscheme#:#otuser#@#othost> Polycom, Inc.
Page 115 Use user as host (RR) — Uses the user in the original, if specified, as the host value, otherwise the host value is used as is. Equivalent to template: #orscheme#:#oruser# (but if no original user is present, the host value is used as is) Polycom, Inc.
Page 116 In addition to the variables, you can enter any values acceptable for the Request-URI or To header. For the Request-URI, the contents of the Template field specify only the URI portion of the full Request line. Depending on network configuration, a Route header may be required. Polycom, Inc.
Page 117 <sip:#otuser#@#othost#> <sip:user@host> <sip:user@host> displayname #otdisplay# displayname <sip:user@host> <sip:#otuser#@#phost#> <sip:user@peerHostIp> displayname #otdisplay# displayname <sip:user@host> <sip:#otuser#@foo.bar> <sip:user@foo.bar> See also: External SIP Peer Add External SIP Peer Dialog Edit External SIP Peer Dialog Add Outbound Registration Dialog Edit Outbound Registration Dialog Polycom, Inc.
Page 118: Add Authentication Dialog
User name The user name to use for authentications in this realm. Password The password to use for authentications in this realm. Confirm password See also: External SIP Peer Add External SIP Peer Dialog Edit External SIP Peer Dialog Polycom, Inc.
Page 119: Add Outbound Registration Dialog
(#delimited) defined in Free Form Template Variables. Click Edit or Delete to edit or delete the selected header. See also: External SIP Peer Add External SIP Peer Dialog Edit External SIP Peer Dialog Polycom, Inc.
Page 120: Edit Outbound Registration Dialog
(#delimited) defined in Free Form Template Variables. Click Edit or Delete to edit or delete the selected header. See also: External SIP Peer Add External SIP Peer Dialog Edit External SIP Peer Dialog Polycom, Inc.
Page 121: External H.323 Sbc
(in response to the LRQ), rather than waiting until later in the call setup. In order to perform early CAC, the Polycom RealPresence DMA system must know the caller’s media address, which isn’t provided in the LRQ and is unknowable for an ordinary gatekeeper. If the gatekeeper is also an SBC, however, it proxies the media.
Page 122: Add External H.323 Sbc Dialog
Lets you turn a postliminary on or off without deleting it. Script Type (or paste) the postliminary 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. Polycom, Inc.
Page 123: Edit External H.323 Sbc Dialog
Lets you turn a postliminary on or off without deleting it. Script Type (or paste) the postliminary 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. Polycom, Inc.
Page 124 Device Management See also: External H.323 SBC Script Debugging Dialog for Preliminaries/Postliminaries Polycom, Inc.
Page 125: Mcu Management
● MCUs The MCUs page shows the MCUs, or media servers, known to the Polycom RealPresence DMA system. In a superclustered system, this list encompasses all MCUs throughout the supercluster and is the same on all clusters in the supercluster. It includes: ●...
Page 126 MCUs in order to use them as part of the Conference Manager’s conferencing resource pool. The Polycom RealPresence DMA system supports the use of Polycom MGC MCUs, but not as part of the Conference Manager’s conferencing resource pool. They can register with the Call Server as standalone MCUs (dialed by IP or prefix) and/or ISDN gateways.
Page 127: Considerations When Using Mcus With The Realpresence Dma System
Make sure the SIP_REGISTER_ONLY_ONCE flag is set to NO or not present. In order for the Polycom RealPresence DMA system to assign an alternate gatekeeper to an MCU, the MCU must be in a territory that has a backup RealPresence DMA system assigned to it.
Page 128 The number of video and voice ports on the MCU that are either reserved for cascading or off-limits to the Polycom RealPresence DMA system. This feature cannot be used with an integrated Polycom RealPresence Resource Manager system, which can’t share MCUs with the RealPresence DMA system.
Page 129 MCU Pools The MCU pools in which this MCU is used, if it’s enabled for conference rooms (available as a conferencing resource for the Polycom RealPresence DMA system’s Conference Manager). Site The site in which the MCU is located (see Sites).
Page 130 If the MCUs are quarantined, this becomes Unquarantine. Note: Quarantining is intended only for MCUs that are registered with the Polycom RealPresence DMA system’s Call Server as standalone MCUs and/or ISDN gateways, but are not available to the Conference Manager as conferencing resources.
Page 131: Add Mcu Dialog
MCU Management Add MCU Dialog Lets you add an MCU, gateway, or combination of the two to the pool of devices available to the Polycom RealPresence DMA system. Note: MCU support The Polycom RealPresence DMA system supports the use of Cisco Codian 4200, 4500, and MSE 8000 series MCUs as part of the Conference Manager’s conferencing resource pool, but their Media...
Page 132 Password for the administrative user ID. Video ports reserved for non-DMA The number of video ports on this MCU that are off-limits to the Polycom RealPresence DMA system. Note: This feature is not for use with an integrated Polycom RealPresence Resource Manager system.
Page 133 MCU). If not, and SIP is enabled, this field is required. Transport type The SIP transport type to use with this MCU. If the Polycom RealPresence DMA system‘s security settings don’t allow unencrypted connections, this must be TLS.
Page 134 Type (or paste) the postliminary 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. See also: MCUs MCU Procedures Add Session Profile Dialog Edit Session Profile Dialog Polycom, Inc.
Page 135: Edit Mcu Dialog
MCUs in order to use them as part of the Conference Manager’s conferencing resource pool. The Polycom RealPresence DMA system supports the use of Polycom MGC MCUs, but not as part of the Conference Manager’s conferencing resource pool. They can register with the Call Server as standalone MCUs (dialed by IP or prefix) and/or ISDN gateways.
Page 136 Password for the administrative user ID. Video ports reserved for non-DMA The number of video ports on this MCU that are off-limits to the Polycom RealPresence DMA system. Note: This feature is not for use with an integrated Polycom RealPresence Resource Manager system.
Page 137 MCU). If not, and SIP is enabled, this field is required. Transport type The SIP transport type to use with this MCU. If the Polycom RealPresence DMA system‘s security settings don’t allow unencrypted connections, this must be TLS.
Page 138 Lets you turn a postliminary on or off without deleting it. Script Type (or paste) the postliminary 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. Polycom, Inc.
Page 139: Add Session Profile Dialog
Select the protocol(s) for this profile. PSTN Only H.320 and PSTN are relevant when editing a profile you added. The H.323 other two are selected if the gateway specified them when registering. See also: Add MCU Dialog Edit MCU Dialog Polycom, Inc.
Page 140: Isdn Gateway Selection Process
MCU Management ISDN Gateway Selection Process When the dial string begins with a simplified ISDN gateway dialing prefix, the Polycom RealPresence DMA system chooses an ISDN gateway by applying the following steps: 1 Strip the ISDN gateway dialing prefix from the dial string, leaving the E.164 number.
Page 141 Voice ports reserved for non-DMA use to the desired values. Note: MCUs and RealPresence Resource Manager systems This feature is not for use with a Polycom RealPresence Resource Manager system. The RealPresence Resource Manager system must have exclusive use of any MCUs on which it directly schedules conferences.
Page 142 1 On the Dashboard, verify that there are no calls and conferences on the MCU you want to delete. 2 Go to Network > MCU > MCUs. 3 In the MCUs list, select the MCU you want to remove from the Polycom RealPresence DMA system’s pool of available conferencing resources.
Page 143: Mcu Pools
The MCU Pools list shows the MCU pools, or logical groupings of media servers, that are defined in the Polycom RealPresence DMA system. In a superclustered system, this list is the same on all clusters in the supercluster. A pool may group MCUs based on location, capability, or some other factor.
Page 144: Add Mcu Pool Dialog
Description of the pool. This should be something meaningful, such as the geographic location of the MCUs that the pool contains. Available MCUs Lists the MCUs available to the Polycom RealPresence DMA system. Selected MCUs Lists the MCUs included in the pool. The arrow buttons move MCUs from one list to the other.
Page 145: Mcu Pool Procedures
Brief description of the pool. This should be something meaningful, such as the geographic location of the MCUs that the pool contains. Available MCUs Lists the MCUs available to the Polycom RealPresence DMA system. Selected MCUs Lists the MCUs included in the pool. The arrow buttons move MCUs from one list to the other.
Page 146: Mcu Pool Orders
MCU Pool Orders The MCU Pool Orders list shows the MCU pool orders that are defined in the Polycom RealPresence DMA system. In a superclustered system, this list is the same on all clusters in the supercluster. A pool order contains one or more MCU pools and specifies the order of preference in which the pools are used.
Page 147: Add Mcu Pool Order Dialog
The up/down arrow buttons change the priority rankings of the pools. Fall back to any available MCU Indicates whether this pool order is set to fall back to any available MCU if there are no available MCUs in its pools. Polycom, Inc.
Page 148: Edit Mcu Pool Order Dialog
MCU availability and reliability issues. See MCU Availability and Reliability Tracking. The Polycom RealPresence DMA system chooses an MCU for a user’s conference by applying the following rules in order: 1 Select the MCU pool order: a Use the pool order directly assigned to the user’s conference room.
Page 149: Mcu Availability And Reliability Tracking
3. 5 If no MCUs are available in any of the MCU pools in the pool order:  If fallback is enabled, select the best MCU available to the Polycom RealPresence DMA system, based on the system’s capability algorithm.
Page 150 MCUs during a failover scenario. So, for example, if you want to avoid routing any more calls to an MCU after two consecutive failed calls, provide enough excess capacity that the remaining MCUs never all reach 43% port usage during a failure. Polycom, Inc.
Page 151: Mcu Pool Order Procedures
1 Go to Network > MCU > MCU Pool Orders. 2 In the MCU Pool Orders list, select the pool order, and in the Actions list, click Edit. 3 In the Edit MCU Pool Order dialog, edit the fields as required. See Edit MCU Pool Dialog. Polycom, Inc.
Page 152 2 In the MCU Pool Orders list, select the pool order, and in the Actions list, select Delete. 3 When asked to confirm that you want to delete the selected MCU, click Yes. See also: MCU Pool Orders Add MCU Pool Order Dialog Edit MCU Pool Order Dialog Polycom, Inc.
Page 153: Integrations With Other Systems
● Whenever you force a cache refresh using the Update button. ● To authenticate login passwords. ● To create or delete Polycom conference contacts whenever a publishable VMR is created or deleted (only if the RealPresence DMA system is integrated with Microsoft Lync 2013 and contact creation is enabled).
Page 154: Microsoft Active Directory Page
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, to help customers successfully design, deploy, optimize, and manage Polycom visual communication within their third-party UC environments.
Page 155 Description Connection Status <server name and icons> The Polycom RealPresence DMA system server(s) and one or more of the following status icons for each: Warning – Appears only if an error has occurred. Hover over it to see a description of the problem or problems.
Page 156 IP address of a specific global catalog server, not the DNS domain name. The Polycom RealPresence DMA system can only integrate with one forest. A special “Exchange forest” (in which all users are disabled) won’t work because the system doesn’t support conferencing for disabled users.
Page 157 2254 for syntax information. Base DN Can be used to restrict the Polycom RealPresence DMA system to work with a subset of the Active Directory (such as one tree of multiple trees, a subtree, or a domain). Leave the default setting, All Domains, initially. See...
Page 158 Maximum characters used Desired length of conference room IDs. The Polycom RealPresence DMA system strips excess characters from the beginning, not the end. If you specify 7, the room IDs will contain the last 7 valid characters from the Active Directory attribute being used.
Page 159: Active Directory Integration Procedure
AD integration by the RealPresence DMA system have different requirements. Don’t try to use the same account for both purposes. In particular, the whitelist of machines that the Polycom RealPresence Resource Manager system is allowed to log into should contain only the RealPresence Resource Manager system, while the whitelist of machines the RealPresence DMA system is allowed to log into should contain only the domain controllers.
Page 160 Log out and log back in using your named enterprise account. d Secure the service account by removing all user roles and marking it disabled in the RealPresence DMA system (not in the Active Directory). See Edit User Dialog. Polycom, Inc.
Page 161: Understanding Base Dn
Leaving user roles assigned to the service account represents a serious security risk. For best security, remove all user roles and mark this account disabled in the Polycom RealPresence DMA system (not the Active Directory) so that this account can’t be used for conferencing or for logging into the Polycom RealPresence DMA system management interface.
Page 162 AD forest. If you want to restrict the system to a subset of the Active Directory (such as one tree of multiple trees, a subtree, a domain, or an organizational unit), select the corresponding base DN entry from the list. See also: Microsoft Active Directory ® Integration Active Directory Integration Procedure About the System’s Directory Queries Polycom, Inc.
Page 163: Adding Passcodes For Enterprise Users
Dialog). Note: Cisco Codian MCUs and passcodes If Cisco Codian MCUs are included in the Polycom RealPresence DMA system’s pool of conferencing resources, don’t assign a chairperson passcode without also assigning a conference passcode. If a conference with only one passcode (either chairperson or conference) lands on a Codian MCU, all callers to the conference must enter that passcode.
Page 164: About The System's Directory Queries
Microsoft Active Directory Page Active Directory Integration Procedure Active Directory Integration Report About the System’s Directory Queries The Polycom RealPresence DMA system uses the following subtree scope LDAP queries. In a standard AD configuration, all these queries use indexes. User Search ●...
Page 165 The base variable depends on the Base DN setting on the Microsoft Active Directory page. If it’s set to the default, All Domains, the base variable is the domain DN, as shown by the example. Otherwise, the base variable is the same as Base DN. See Understanding Base Polycom, Inc.
Page 166 The base variable depends on the domain name being queried. ● Filter: same as in User Search ● Index used: same as in User Search ● Attributes returned: sAMAccountName, attribute(s) not in global catalog Domain Search This search queries LDAP. Polycom, Inc.
Page 167: Microsoft ® Lync ® 2013 Integration
The RealPresence DMA system allows you to integrate with Microsoft Lync 2013 Standard Edition and Enterprise Edition environments. When you integrate the RealPresence DMA system into a Lync 2013 environment, the system communicates with the Lync servers and Active Directory to provide contact Polycom, Inc.
Page 168: Lync 2010 Vs. Lync 2013 Integration
RealPresence DMA system. When the RealPresence DMA system is integrated with Lync 2013, Lync clients that connect to RealPresence DMA system VMRs may be hosted on the Lync AVMCU, and can be part of RealPresence DMA system conferences via a cascade link that the Polycom MCU creates with the AVMCU.
Page 169: Automatic Contact Creation And Configuration
Polycom MCUs Polycom RealConnect ™ scheduled conferences require that the RealPresence DMA system manage at least one Polycom MCU that supports Lync 2013. Non-Polycom MCUs are not supported. ™ Polycom RealConnect uses Microsoft Outlook meeting invitations to deliver conference information to participants.
Page 170: Lync And Non-Lync Endpoint Collaboration
Microsoft Lync documentation for more details on specific call flows. ● Users of Lync 2013 clients can select a Polycom conference contact in the contact list and drag it to an ongoing Lync 2013 conversation window, starting a video call.
Page 171: Lync 2010 And 2013 Client / Server Feature Support
Integrate RealPresence DMA and Lync 2013 Refer to the Polycom Unified Communications in a Microsoft Environment Solution Deployment Guide for the tasks needed to integrate the RealPresence DMA system with Lync 2013. If you need the RealPresence DMA system to automatically create conference contacts in Active Directory, ensure that your system is integrated with Microsoft Active Directory before proceeding.
Page 172: Diagnose Presence Problems
● Check for any active system alerts The description of any active system alerts can indicate potential issues with integration. See the online help or the Polycom RealPresence DMA 7000 System Operations Guide for a description of the alert text.
Page 173: Polycom Solution And Integration Support
The Polycom RealPresence DMA system supports the use of Cisco Codian 4200, 4500, and MSE 8000 series MCUs as part of its conferencing resource pool. If you use Codian MCUs to host Polycom Conferencing (calendared) meetings, be aware of these limitations: ●...
Page 174: Exchange Server Integration Procedure
Directory domain controller) has an A record for the RealPresence DMA system that resolves the system’s FQDN to its virtual IP address. 3 On the Microsoft Exchange server, create the Polycom Conferencing user that the add-in will automatically invite to Polycom Conferencing meetings.
Page 175: Realpresence Resource Manager Integration
IP address) of the Exchange server. 6 Specify the login credentials for the system on the Exchange server. 7 Set Territory to the territory of the Polycom RealPresence DMA cluster to be responsible for calendaring. 8 If you have multiple Exchange servers behind a load balancer, under Accept Exchange notifications from these additional IP addresses, add the IP address of each individual Exchange server.
Page 176 RealPresence Resource Manager system calculates call bandwidth requirements using a conversion factor of 2.5, Polycom recommends using a Bit rate to bandwidth conversion factor value of 2.5 if you integrate with a RealPresence Resource Manager system. Otherwise, you will need to alter the bandwidth restrictions for your site topology to take into account the conversion factor value so that the RealPresence DMA system’s call bandwidth requirement calculations are predictable.
Page 177: Realpresence Resource Manager Page
RealPresence Resource Manager integration is not supported in Maximum security mode. See Consequences of Enabling Maximum Security Mode. If you want to support cascading for bandwidth, but don’t have a Polycom RealPresence Resource Manager system, you must create site topology information on the Polycom RealPresence DMA system. See Site Topology.
Page 178: Join Realpresence Resource Manager Dialog
RealPresence Resource Manager Integration Join RealPresence Resource Manager Dialog Integrate the Polycom RealPresence DMA system with a Polycom RealPresence Resource Manager system to obtain site topology information and user-to-device association information. Note: Maximum security mode and RealPresence Resource Manager integration RealPresence Resource Manager integration is not supported in Maximum security mode.
Page 179: Realpresence Resource Manager Integration Procedures
FQDN in this field. In the event of an outage, the RealPresence DMA system will contact DNS for an alternative RealPresence Resource Manager system to use. See the Polycom RealPresence Resource Manager System Operations Guide for more information on RealPresence Resource Manager system geographic redundancy.
Page 180 2 In the Actions list, select Join RealPresence Resource Manager. 3 In the Join RealPresence Resource Manager dialog, enter the host name or IP address of the Polycom RealPresence Resource Manager system and the credentials with which to log into it. Then click OK.
Page 181: Juniper Networks Src Integration
Integrations with Other Systems Juniper Networks SRC Integration You can integrate the Polycom RealPresence DMA system’s Call Server with a Juniper Networks SRC Series Session and Resource Control module to provide bandwidth assurance services. This allows the RealPresence DMA system to consult a configured policy on the Juniper SRC system at call time to assure and/or reserve required network resources for a call.
Page 182: Juniper Networks Src Integration Procedure
SRC server about the endpoint you specified and confirms that the query is successful. A dialog informs you that the configuration has been updated. 6 Click OK. See also: Juniper Networks SRC Integration Juniper Networks SRC Page Polycom, Inc.
Page 183: Conference Manager Configuration
On the Conference Settings page, you can define the default class of service and bit rate limits, a dialing prefix, and various default conference properties for the Polycom RealPresence DMA system. If the system is integrated with a Microsoft® Lync 2013 environment, you can also configure system-wide default settings related to Presence Publishing for Polycom conference contacts.
Page 184 (VMRs). Default Conference Duration Default maximum duration of a conference (in hours and minutes) or Unlimited (the maximum in this case depends on the MCU). Presence Publishing This section allows you to configure Polycom conference contact presence options. Polycom, Inc.
Page 185 After you edit this field, it may take some time for the change to be seen in the Lync client, depending on how many conference contacts the RealPresence DMA system is managing. Note: This field is enabled when the Create Polycom conference contacts check box is checked. Polycom, Inc.
Page 186: Class Of Service
The following table illustrates the two modes of operation for the Default Polycom conference contacts presence settings field on the Admin > Conference Manager > Conference Settings page. The choices available for this field depend on the status of the Publish presence for Polycom conference contacts and Create Polycom conference contacts check boxes.
Page 187: Remove Contacts From Active Directory Dialog
Shared Number Dialing Remove Contacts from Active Directory Dialog If you disable the Publish presence for Polycom conference contacts option and Active Directory integration is enabled, the Remove Contacts from Active Directory action becomes available in the left-hand navigation pane. For systems integrated with a Microsoft® Lync 2013 environment, this action allows you to remove any contacts in Active Directory created by the RealPresence DMA system.
Page 188: Conference Templates
A conference template specifies a set of conference properties, such as the line (bit) rate and video display mode. Note: Cisco Codian template settings The Polycom RealPresence DMA system supports the use of some Cisco Codian MCUs, and conference templates can include Codian-specific settings. Two Types of Templates You can create a conference template in two ways: ●...
Page 189 Conference Manager Configuration Standalone Templates Standalone templates defined in the Polycom RealPresence DMA system free you from having to ensure that the exact same RealPresence Collaboration Server or RMX profiles exist on all the MCUs. You specify the desired conference properties directly in the template.
Page 190: Template Priority
● If the system selected a Cisco Codian MCU, it uses the Codian-specific settings of the specified template. ● If the system selected a Polycom RealPresence Collaboration Server or RMX MCU, it falls back to its default conference template (see Conference Settings).
Page 191: About Cascading
MCUs on which those conference may take place. See your Polycom RealPresence Collaboration Server or RMX documentation for information about conference IVR services. This feature is not supported on Cisco Codian MCUs.
Page 192 Manager system to obtain its site topology data. See RealPresence Resource Manager Integration. 3 On the Polycom RealPresence DMA system, enable cascading for bandwidth in some or all of your conference templates. If you don’t have a Polycom RealPresence Resource Manager system, you must define your site topology in the Polycom RealPresence DMA system instead of importing it.
Page 193 Dialog). Once a conference with cascading for size enabled has started (the “hub” MCU has been chosen), the Polycom RealPresence DMA system does the following for each subsequent participant that dials into that conference: 3 From among the MCUs that are currently part of the conference and have ports available that are not reserved for cascading, the RealPresence DMA system randomly selects one of the MCUs closest to the hub MCU.
Page 194: Conference Templates List
The name of the template. Description A description of the template. The Polycom RealPresence DMA system comes with a Factory Template that has a default set of conference parameters. You can edit that template and create additional templates. See also:...
Page 195 MCU transcodes the video stream to each device in the conference to provide an optimal experience, based on its capabilities. This is the only mode that supports the use of Polycom MCU profiles, third-party and legacy endpoints, and Codian and legacy RMX MCUs.
Page 196 The maximum bit rate at which endpoints can connect to conferences using this template. If Video switching is selected, the minimum line rate is 768 kbps (except for SD resolution, available only on v7 and newer Polycom MCUs with MPM+ or MPMx cards). Advanced Settings...
Page 197 TIP, and non-TIP content is used with non-TIP endpoints. Requires minimum line rate of 1024 kbps and HD resolution (720 or better). Available only on v7.6 and newer Polycom MCUs. MS AVMCU cascade When integrated with a Lync 2013 environment, controls behavior of the mode cascade link with the Lync 2013 AVMCU.
Page 198 Enable gathering Enables the gathering phase for conferences using this template. Available only on v6.0 and newer Polycom MCUs. Not available if Video switching is selected. This is a time period (configurable on the MCU) at the beginning of a conference when people are connecting.
Page 199 Enables a conference to change to lecture mode when the current speaker speaks for 30 seconds. When another participant starts talking, it returns to the previous video layout. Not available if Video switching or Same layout is selected, or if Telepresence mode is Yes. Polycom, Inc.
Page 200 Off— Telepresence mode is off, regardless of whether a telepresence endpoint is present. We recommend always using Auto. Available only on v6.0 and newer Polycom MCUs that are licensed for telepresence mode. For information on Polycom MCU licensing and activation, refer to the MCU’s Getting Started Guide.
Page 201 Override default conference IVR Links this template to the specific conference IVR service selected in the list service below. Note: The Polycom MCU conference IVR service is separate and distinct from the RealPresence DMA system’s SIP-only shared number dialing feature (see Shared Number Dialing).
Page 202 Immediately — Recording starts automatically when the conference starts. • Upon Request — Recording can be initiated manually by the chairperson or an operator. Conference recording requires a Polycom RealPresence Capture Server or RSS recording system and an MCU that supports recording. Polycom, Inc.
Page 203 MCUs, with the number of MCUs that have the link shown in parentheses. Available only on v7 and newer Polycom MCUs. Audio only Limits recording to the audio channel of the conference.
Page 204: Edit Conference Template Dialog
Settings section applies to all MCUs. The Cisco Codian section appears only if the system is licensed to use Cisco Codian MCUs, and its settings apply only if a Codian MCU is selected for the call. The other sections apply only if a Polycom RealPresence Collaboration Server or RMX MCU is selected. Field...
Page 205 MCU transcodes the video stream to each device in the conference to provide an optimal experience, based on its capabilities. This is the only mode that supports the use of Polycom MCU profiles, third-party and legacy endpoints, and Codian and legacy RMX MCUs.
Page 206 The maximum bit rate at which endpoints can connect to conferences using this template. If Video switching is selected, the minimum line rate is 768 kbps (except for SD resolution, available only on v7 and newer Polycom MCUs with MPM+ or MPMx cards). Advanced Settings...
Page 207 TIP, and non-TIP content is used with non-TIP endpoints. Requires minimum line rate of 1024 kbps and HD resolution (720 or better). Available only on v7.6 and newer Polycom MCUs. MS AVMCU cascade When integrated with a Lync 2013 environment, controls behavior of the mode cascade link with the Lync 2013 AVMCU.
Page 208 Enable gathering Enables the gathering phase for conferences using this template. Available only on v6.0 and newer Polycom MCUs. Not available if Video switching is selected. This is a time period (configurable on the MCU) at the beginning of a conference when people are connecting.
Page 209 Enables a conference to change to lecture mode when the current speaker speaks for 30 seconds. When another participant starts talking, it returns to the previous video layout. Not available if Video switching or Same layout is selected, or if Telepresence mode is Yes. Polycom, Inc.
Page 210 Off— Telepresence mode is off, regardless of whether a telepresence endpoint is present. We recommend always using Auto. Available only on v6.0 and newer Polycom MCUs that are licensed for telepresence mode. For information on Polycom MCU licensing and activation, refer to the MCU’s Getting Started Guide.
Page 211 Override default conference IVR Links this template to the specific conference IVR service selected in the list service below. Note: The Polycom MCU conference IVR service is separate and distinct from the RealPresence DMA system’s SIP-only shared number dialing feature (see Shared Number Dialing).
Page 212 Immediately — Recording starts automatically when the conference starts. • Upon Request — Recording can be initiated manually by the chairperson or an operator. Conference recording requires a Polycom RealPresence Capture Server or RSS recording system and an MCU that supports recording. Polycom, Inc.
Page 213 MCUs, with the number of MCUs that have the link shown in parentheses. Available only on v7 and newer Polycom MCUs. Audio only Limits recording to the audio channel of the conference.
Page 214: Select Layout Dialog
2 In the Actions list, click Add. 3 In the Add Conference Template dialog, specify all the conference properties for this template: a In Common Settings, enter an appropriate name and description. b Complete the remaining sections as desired. See Add Conference Template Dialog. Polycom, Inc.
Page 215 Check Use existing profile and select the one you want from the RMX profile name list. The list contains the profiles available on the RealPresence Collaboration Server and RMX MCUs that have been added to the Polycom RealPresence DMA system. If no MCUs have been added to the system, the list is disabled.
Page 216: Ivr Prompt Sets
Note: No media file format validation The RealPresence DMA system doesn’t examine the contents of the media files to validate the format. The call flow currently uses only one video slide, General_Slide.jpg. The following table lists the audio prompt files it uses. Polycom, Inc.
Page 217 The following table describes the parts of the IVR Prompt Sets page. Field Description Archive File Name The name of the archive (.zip) file containing the prompt set. Prompt Set Name The name of the prompt set as specified in the manifest file. Polycom, Inc.
Page 218: Shared Number Dialing
(virtual entry queues) by routing them to an appropriate Polycom RealPresence Collaboration Server or RMX MCU entry queue. Depending on the MCU type and version, Polycom MCUs can have two kinds of entry queues for providing callers with interactive voice response (IVR) services: ●...
Page 219 IVR service. 4 If this is a RealPresence DMA-controlled entry queue: a The Polycom RealPresence DMA system uses its call flow, voice prompts, and video slides, sending commands to the MCU to control the interaction with the caller (display slides, play prompts, collect tones, etc.).
Page 220 Conference Manager Configuration includes only the system’s domain name or IP address, the Polycom RealPresence DMA system uses the Direct Dial VEQ for it. For MCU-controlled VEQs, to create a unique experience, you must create the corresponding entry queue on the RealPresence Collaboration Server and RMX MCUs to be used.
Page 221: Add Virtual Entry Queue Dialog
RMX entry queue The RealPresence Collaboration Server or RMX entry queue to use for this VEQ. The list includes all entry queues available on the Polycom MCUs connected to the system, with the number of MCUs that have each entry queue shown in parentheses.
Page 222: Add Direct Dial Virtual Entry Queue Dialog
RMX entry queue The RealPresence Collaboration Server or RMX entry queue to use for this VEQ. The list includes all entry queues available on the Polycom MCUs connected to the system, with the number of MCUs that have each entry queue shown in parentheses.
Page 223: Edit Direct Dial Virtual Entry Queue Dialog
RMX entry queue The RealPresence Collaboration Server or RMX entry queue to use for this VEQ. The list includes all entry queues available on the Polycom MCUs connected to the system, with the number of MCUs that have each entry queue shown in parentheses.
Page 224: Script Debugging Dialog For Veq Scripts
RMX entry queue The RealPresence Collaboration Server or RMX entry queue to use for this VEQ. The list includes all entry queues available on the Polycom MCUs connected to the system, with the number of MCUs that have each entry queue shown in parentheses.
Page 225: Sample Virtual Entry Queue Script
// 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<whitelist_patterns.length; i++) if (DTMF_STRING.match(whitelist_patterns[i])) return ACCEPT; return REJECT; Polycom, Inc.
Page 226: Superclustering
A supercluster is a set of up to five Polycom RealPresence DMA system clusters that are geographically dispersed, but still centrally managed. The clusters in a supercluster are all peers. There is no “master” or “primary”...
Page 227: Dmas
Mode. See also: Supercluster Procedures DMAs The DMAs page lets you create, view, and manage a supercluster of Polycom RealPresence DMA systems (see About Superclustering). If the system you’re logged in to is not (and has not been) part of a supercluster, the list contains only that system.
Page 228 Be sure you create a new supercluster by joining the cluster you’re logged in to to the cluster that has the data and configuration you want to preserve. For instance, if one of the clusters is integrated with your Polycom RealPresence Resource Manager system, join the other cluster to it, not the other way around.
Page 229 Restart Supercluster Services and Reset Supercluster Services are emergency actions that should only be taken when instructed to do so by a Polycom Global Services representative. They’re intended only for resolving data store replication problems that can’t be resolved by other means.
Page 230: Join Supercluster Dialog
Supercluster Procedures Join Supercluster Dialog In the Supercluster page’s action list, the Join Supercluster command lets you add a Polycom RealPresence DMA system to an existing supercluster or create a new one. It opens the Join Supercluster dialog, where you can specify any cluster in the supercluster to join. If the cluster you specify isn’t already part of an existing supercluster, joining to it creates a new supercluster that gets its shared data store from the cluster you specify.
Page 231: Supercluster Procedures
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.
Page 232 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.
Page 233: Call Server Configuration
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.
Page 234: Call Server Settings
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.).
Page 235 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.
Page 236 Specifies which responses to an initial SIP INVITE indicate that a SIP peer is codes 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.
Page 237 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.
Page 238: Domains
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.
Page 239 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.
Page 240: Dial Rules
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.
Page 241: 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.
Page 242 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.
Page 243: The Default Dial Plan And Suggestions For Modifications
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.
Page 244 “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.
Page 245 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.
Page 246: Add Dial Rule Dialog
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.
Page 247 Otherwise, if possible, encoded as a url-ID. • Otherwise, encoded as an h323-ID. Resolve to registered Looks for a registered endpoint (active or inactive) that has the same alias or endpoint signaling address. Note: This action employs the H.323<->SIP gateway function if applicable. Polycom, Inc.
Page 248 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.
Page 249 Looks for a conference room (virtual meeting room, or VMR) that matches the dial string. Resolve to virtual entry Looks for a shared-number entry queue that matches the dial string. queue See also: Dial Rules The Default Dial Plan and Suggestions for Modifications Preliminary/Postliminary Scripting Polycom, Inc.
Page 250: Edit Dial Rule Dialog
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.
Page 251 Otherwise, if possible, encoded as a url-ID. • Otherwise, encoded as an h323-ID. Resolve to registered Looks for a registered endpoint (active or inactive) that has the same alias or endpoint signaling address. Note: This action employs the H.323<->SIP gateway function if applicable. Polycom, Inc.
Page 252 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.
Page 253 Looks for a conference room (virtual meeting room, or VMR) that matches the dial string. Resolve to virtual entry Looks for a shared-number entry queue that matches the dial string. queue See also: Dial Rules The Default Dial Plan and Suggestions for Modifications Polycom, Inc.
Page 254: Preliminary/Postliminary Scripting
The site code of the caller’s site. _CODE 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.
Page 255: Preliminary/Postliminary Scripting Functions
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.
Page 256 Function name and parameters Details getConferenceRoomOrID() Return value: • For dial-outs to endpoints from VMRs or Polycom RealConnect conferences, returns the VMR or Lync Conference ID. • For dial-outs to the VMR or Polycom RealConnect conferences, and for dial-ins, returns the empty string.
Page 257: How Dial Rule Actions Affect Sip Headers
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 IP address The To header and the request URI are both replaced with the modified dial string. Polycom, Inc.
Page 258: Script Debugging Dialog For Preliminaries/Postliminaries
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.
Page 259: Sample Preliminary And Postliminary Scripts
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.
Page 260 // 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.
Page 261 + 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.
Page 262 // 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 "<vmr number>"<comma> "3000", var prefix = "22"; Polycom, Inc.
Page 263: 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...
Page 264: Add Hunt Group Dialog
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.
Page 265: Add Alias Dialog
Device authentication enhances security by requiring devices registering with or calling the Polycom RealPresence DMA system to provide credentials that the system can authenticate. In turn, the Polycom RealPresence DMA system may need to authenticate itself to an external SIP peer or gatekeeper.
Page 266 Network Settings page (allowing each cluster of a supercluster to have its own realm). If no domain is specified on the Network Settings page, the default realm value is sip.dma. Clear the check box to change the string in the Realm field. Polycom, Inc.
Page 267: Add Device Authentication Dialog
Inbound Authentication tab is selected. It lets you add a device’s authentication credentials to the list of entries against which the Call Server checks a device’s credentials. The following table describes the fields in the Add Device Authentication dialog. Polycom, Inc.
Page 268: Edit Device Authentication Dialog
On the Registration Policy page, you can specify policies to control registration by endpoints. To do so, you define the following: ● Compliance policy: Write an executable script (using the Javascript language) that specifies the criteria for determining whether an endpoint is compliant or noncompliant with the registration policy. Polycom, Inc.
Page 269 Some dial rule actions, such as Resolve to registered endpoint, can route calls to endpoints with an inactive registration. Deleting the registration record is the only way to prevent resolution to an inactive endpoint. Polycom, Inc.
Page 270: Registration Policy Scripting
The script can evaluate a variable or change its value (the change isn’t preserved after the script completes). Variable Initial value EP_DEFINED_IN_CMA “TRUE” if the Polycom RealPresence DMA system is integrated with a RealPresence Resource Manager system and the endpoint is defined in that system. EP_H323_DIALEDDIGITS_ALIAS Endpoint alias value associated with H.323 dialedDigits or blank.
Page 271 Endpoint alias value associated with SIP TEL: URI or blank. This is an array that can contain multiple values. Separate the values with commas. EP_VERSION Endpoint software version number. REG_IS_PERMANENT “TRUE” if endpoint is already permanently registered. Blank otherwise. Polycom, Inc.
Page 272: Script Debugging Dialog For Registration Policy Scripts
Run Script to see the results of applying the script using those variable values. Repeat as often as necessary, using different variable values. If necessary, make changes to your script and then test some more, until you’re satisfied that the script accomplishes what you intended. Polycom, Inc.
Page 273: Sample Registration Policy Scripts
// (NOTE: typically this is used when DMA has public internet connectivity or in conjunction with the DMA Guest Port feature) var result = COMPLIANT; if (EP_REG_IS_SIP && EP_MODEL != null && EP_MODEL.toLowerCase() == "friendly-scanner") EP_EXCEPTION += "SIPVicious is not allowed."; result = NONCOMPLIANT; return result; /////////////////////////////// Polycom, Inc.
Page 274 // *** Note this does not take into account IPv6 addressing *** var nparts; var IPstring; whitelist = new Array( "10.20.30.40", // specify exact match IP address using quotes /192.168.3.*/, // specify regular expression to match using slashes "192.168.174.233" Polycom, Inc.
Page 275: Prefix Service
Dialing Prefix Dialog). ● Edit the name, vertical service code, or description of the forwarding and hunt group services and enable or disable them (see Edit Vertical Service Code Dialog). The following table describes the fields in the list. Polycom, Inc.
Page 276: Add Simplified Isdn Gateway Dialing Prefix Dialog
ISDN gateway dialing service for using external ISDN gateways. Note: ISDN gateway vs. H.323<->SIP gateway This feature is not related to the Polycom RealPresence DMA system’s built-in H.323<->SIP gateway. Simplified ISDN gateway dialing is for routing calls to H.320 or PSTN protocol gateways.
Page 277: Edit Simplified Isdn Gateway Dialing Prefix Dialog
Note: ISDN gateway vs. H.323<->SIP gateway This feature is not related to the Polycom RealPresence DMA system’s built-in H.323<->SIP gateway. Simplified ISDN gateway dialing is for routing calls to H.320 or PSTN protocol gateways. This feature isn’t supported for calls from SIP endpoints, but SIP endpoints can make ISDN gateway...
Page 278: Edit Vertical Service Code Dialog
The embedded DNS capability of the Polycom RealPresence DMA system automates this procedure. Each Polycom RealPresence DMA server hosts its own embedded DNS server. It publishes a DNS CNAME record for each site. That CNAME record maps to the active cluster with which endpoints at the site should register.
Page 279 DNS service resolves dma.<newsubdomain> to the IP address of the cluster. If you wish to use this feature, your enterprise DNS must place the Polycom RealPresence DMA supercluster in charge of resolving the sub-domain specified on this page. To do this, you must: ●...
Page 280: History Retention Settings
11,000 1,000 Contact Polycom Global Services if you want to discuss the possibility of changing the retention limits. The History Retention Settings page lets you specify whether to retain registration history records, and if so, whether to include registration keep-alive messages. You can also specify how many repeated low-value signaling records to retain.
Page 281 2 Specify whether to record registration history, and if so, whether to include keep-alive messages. 3 Specify how many low-value signaling records to retain. 4 Click Update. A dialog informs you that the configuration has been updated. 5 Click OK. See also: Call Server Configuration Polycom, Inc.
Page 282: Site Topology
● Site-to-site exclusion — A site-to-site connection that the site topology doesn’t permit a voice or video call to use. ● Territory — A collection of one or more sites for which a Polycom RealPresence DMA cluster is responsible. Territories serve multiple purposes in a Polycom RealPresence DMA system deployment.
Page 283: Bandwidth Management
Integration with a Polycom RealPresence Resource Manager system is not supported in Maximum security mode. ● If you don’t have a Polycom RealPresence Resource Manager system, enter site topology information about your network directly into the Polycom RealPresence DMA system’s site topology pages.
Page 284: Sites
The Sites page contains a list of the sites defined in the site topology. If the system is integrated with a Polycom RealPresence Resource Manager system, it receives this information from that system, and this page is read-only. If not, you can enter site information.
Page 285: Site Information Dialog
The total bandwidth limit for voice and video calls. Max Per-Call Bit Rate (kbps) The per-call bit rate limit for voice and video calls. Territory The territory to which the site belongs, which determines the Polycom RealPresence DMA cluster responsible for it. See also: About Site Topology...
Page 286: Add Site Dialog
About Site Topology Sites Add Site Dialog Lets you define a new site in the Polycom RealPresence DMA system’s site topology and specify which subnets are associated with it. The following table describes the fields in the dialog. Field Description...
Page 287 Server Settings page is used in this calculation. Territory Settings Territory Assigns the site to a territory, and thus to a Polycom RealPresence DMA cluster. ISDN Number Assignment Assignment method The ISDN number assignment method for the devices in this site. The numbers being assigned are endpoint aliases in the form of E.164 numbers,...
Page 288 The number of digits in the Call Line Identifier (CLID), which is the dialed number. The maximum is 17. For example, in the United States, the number of digits in the CLID is often 7 for outside local calls and 11 for callers in a different area code. Polycom, Inc.
Page 289 The call signaling port for the SBC or ALG. Subnets Lists the subnets in the site. Click Add to add a subnet. Select a subnet in the table and click Edit or Delete to modify or remove it. Subnet Name The unique name of the subnet. Polycom, Inc.
Page 290: Edit Site Dialog
Site Topology Configuration Procedures Edit Site Dialog Lets you edit a site in the Polycom RealPresence DMA system’s site topology and add or edit a subnet associated with the site. The following table describes the fields in the dialog. Field...
Page 291 Server Settings page is used in this calculation. Territory Settings Territory Assigns the site to a territory, and thus to a Polycom RealPresence DMA cluster. ISDN Number Assignment Assignment method The ISDN number assignment method for the devices in this site. The numbers being assigned are endpoint aliases in the form of E.164 numbers,...
Page 292 The number of digits in the Call Line Identifier (CLID), which is the dialed number. The maximum is 17. For example, in the United States, the number of digits in the CLID is often 7 for outside local calls and 11 for callers in a different area code. Polycom, Inc.
Page 293 The call signaling port for the SBC or ALG. Subnets Lists the subnets in the site. Click Add to add a subnet. Select a subnet in the table and click Edit or Delete to modify or remove it. Subnet Name The unique name of the subnet. Polycom, Inc.
Page 294: Add Subnet Dialog
You can assign a subnet to only one site. The following table describes the fields in the dialog. Field Description Name The name of the subnet. Required and must be unique. IP address The IP address of the subnet. Polycom, Inc.
Page 295: Edit Subnet Dialog
1 bits in the routing prefix mask). This value, together with the IP Address, defines the subnet. For IPv4, a value of 24 is equivalent to specifying a dotted-quad subnet mask of 255.255.255.0. A value of 16 is equivalent to specifying a subnet mask of 255.255.0.0. Polycom, Inc.
Page 296: Site Links
The total bandwidth limit for voice and video calls, which you set at the gateway or router. Max Per-Call Bit Rate (kbps) The per-call bit rate limit for voice and video calls, which you set at the gateway or router. Polycom, Inc.
Page 297: Add Site Link Dialog
Site Topology Configuration Procedures Add Site Link Dialog Lets you define a new site link in the Polycom RealPresence DMA system’s site topology. A link can connect two sites, or it can connect a site to an MPLS network cloud (see Network Clouds).
Page 298: Site-To-Site Exclusions
To Site Name of the other site. See also: About Site Topology Add Site-to-Site Exclusion Wizard Site Topology Configuration Procedures Add Site-to-Site Exclusion Wizard Lets you define a new site-to-site exclusion in the Polycom RealPresence DMA system’s site topology. Polycom, Inc.
Page 299: Territories
The Territories page lists the territories defined in the site topology. On the right, it displays information about the selected territory. A territory contains one or more sites for which a Polycom RealPresence DMA cluster is responsible. By default, there is one territory named Default DMA Territory.
Page 300: Add Territory Dialog
Add Territory Dialog Edit Territory Dialog Site Topology Configuration Procedures Add Territory Dialog Lets you define a new territory in the Polycom RealPresence DMA system’s site topology. The following table describes the fields in the dialog. Field Description Territory Info Name A meaningful name for the territory (up to 128 characters).
Page 301: Edit Territory Dialog
Selecting a site and moving it to the Associated sites list changes its territory assignment to this territory. Associated sites Lists sites linked to this territory. Changes you make to this list aren’t implemented until you click OK. Polycom, Inc.
Page 302: Network Clouds
Add Network Cloud Dialog Edit Network Cloud Dialog Site Topology Configuration Procedures Add Network Cloud Dialog Lets you define a new MPLS network cloud in the Polycom RealPresence DMA system’s site topology. The following table describes the fields in the dialog. Field Description...
Page 303: Edit Network Cloud Dialog
About Site Topology Network Clouds Site Topology Configuration Procedures Edit Network Cloud Dialog Lets you edit an MPLS network cloud in the Polycom RealPresence DMA system’s site topology. The following table describes the fields in the dialog. Field Description Cloud Info Name A meaningful name for the cloud (up to 128 characters).
Page 304: Site Topology Configuration Procedures
In the Linked Sites section, display the sites you defined. See Add Network Cloud Dialog. d Select the first site linked to this cloud and click the arrow button to move it to the Linked Sites list. The Add Site Link dialog appears. Polycom, Inc.
Page 305 Note: RealPresence Resource Manager integration replaces data If in the future you integrate this system with a RealPresence Resource Manager system, the site topology information from the RealPresence Resource Manager system will replace the information you entered. See also: About Site Topology Polycom, Inc.
Page 306: Users And Groups
User Roles Overview The Polycom RealPresence DMA system has four user roles, or classes of users, each with its own set of permissions. Every user account has one or more user roles (but only three of the four roles must be explicitly assigned).
Page 307: Adding Users Overview
You can add users to the system in two ways: ● Add users manually to the Polycom RealPresence DMA system. These are known as local users. When adding users manually, you must assign them conference rooms and any specific roles they should have.
Page 308: Users
Microsoft Active Directory Integration. If you have a Polycom RealPresence Resource Manager that you want to integrate with the Polycom RealPresence DMA system, you must create a local user account for the RealPresence Resource Manager system, which enables it to log into the RealPresence DMA system’s RealPresence Platform API. This account should have administrator and provisioner roles.
Page 309 Note: A user account that has neither a conference room nor an explicitly assigned role serves no purpose. Roles The user’s explicitly assigned user roles. All users automatically have the Conferencing User role; it’s not listed or explicitly assigned (but a conference room ID is required). See User Roles Overview. Polycom, Inc.
Page 310: Add User Dialog
This is the password that enables users with explicitly assigned Confirm password roles to log into the system management interface (see User Roles Overview). The password must satisfy the local password rules specified for the system (see Local Password). Polycom, Inc.
Page 311 Dialog). But if the Polycom RealPresence DMA system is integrated with a Polycom RealPresence Resource Manager system, it receives user-to-device association information from that system, and you can only associate users with devices on the Polycom RealPresence Resource Manager system. Polycom, Inc.
Page 312: Edit User Dialog
Note: Cisco MCUs and passcodes If Cisco Codian MCUs are included in the Polycom RealPresence DMA system’s pool of conferencing resources, don’t assign a chairperson passcode without also assigning a conference passcode. If a conference with only one passcode (either chairperson or conference) lands on a Codian MCU, all callers to the conference must enter that passcode.
Page 313 If Class of service is selected, lets you specify the maximum bit rate for the user. Minimum downspeed rate (kbps) If Class of service is selected, lets you specify the minimum bit rate to which the user’s calls can be reduced (downspeeded). Polycom, Inc.
Page 314 See also: Note: Cisco MCUs and passcodes If Cisco Codian MCUs are included in the Polycom RealPresence DMA system’s pool of conferencing resources, don’t assign a chairperson passcode without also assigning a conference passcode. If a conference with only one passcode (either chairperson or conference) lands on a Codian MCU, all callers to the conference must enter that passcode.
Page 315: Authentication Required Dialog
● Calendared conference rooms created automatically when the user uses the Polycom Conferencing Add-in for Microsoft Outlook to set up Polycom Conference meetings in Outlook. You can modify some of the settings for these conference rooms, but not the ones set in the meeting invitation.
Page 316 Conference Settings) plus room ID. Conference Template The template used by the conference room, which defines the conference properties (or links to the Polycom RealPresence Collaboration Server or RMX profile) used for its conferences. See Conference Templates. The template assignment can be made at the conference room level, AD group level, or system default level.
Page 317: Add Conference Room Dialog
You can’t delete enterprise conference rooms, calendared meeting (Polycom Conferencing for Outlook) conference rooms, or scheduled conference rooms created by the Polycom RealPresence Resource Manager system via the API. You can only delete custom conference rooms added manually in the Polycom RealPresence DMA system or via the API.
Page 318 Conference Settings). Conference template The template used by the conference room, which defines the conference properties (or links to the Polycom RealPresence Collaboration Server or RMX profile) used for its conferences (see Conference Templates). If not selected, the room uses the highest-priority template associated with any group to which the user belongs, or if none, the system’s default template (see...
Page 319 If the INVITE message doesn’t contain a resource priority value, the RealPresence DMA system provides the value assigned here to the MCU on behalf of the endpoint. In either case, the resource priority value is recorded in the call property changes. Polycom, Inc.
Page 320 Admin > Conference Manager > Conference Settings page. Note: This property is visible only if the Publish presence for Polycom conference contacts check box is enabled on the Admin > Conference Manager >...
Page 321 Like the dial-outs to participants, this dial-out takes place when the conference starts. Note: If no Polycom MCU with ISDN service is available in the MCU pool order used by this conference room, the conference fails. Note: When the last participant leaves the VMR (that is, when only participants on the audio conferencing bridge remain), the link to the audio conferencing bridge is terminated and the conference ends.
Page 322: Edit Conference Room Dialog
Conference Settings). Conference template The template used by the conference room, which defines the conference properties (or links to the Polycom RealPresence Collaboration Server or RMX profile) used for its conferences (see Conference Templates). If not selected, the room uses the highest-priority template associated with any group to which the user belongs, or if none, the system’s default template (see...
Page 323 (see Conference Settings), set this to the namespace being used for resource priority values. If the namespace being used isn’t listed, select Custom and enter the name in the box below the list. Polycom, Inc.
Page 324 Admin > Conference Manager > Conference Settings page. Note: This property is visible only if the Publish presence for Polycom conference contacts check box is enabled on the Admin > Conference Manager >...
Page 325 Like the dial-outs to participants, this dial-out takes place when the conference starts. Note: If no Polycom MCU with ISDN service is available in the MCU pool order used by this conference room, the conference fails. Note: When the last participant leaves the VMR (that is, when only participants on the audio conferencing bridge remain), the link to the audio conferencing bridge is terminated and the conference ends.
Page 326: Add Dial-Out Participant Dialog
1 Log in as admin and go to User > Users. The Users page appears. 2 Create a local user account for yourself with the Administrator role. See To add a local user. 3 Log out and log back in using your new local account. Polycom, Inc.
Page 327 IDs, or user passwords. For local users, you can change everything but the user ID. In maximum security mode, changing a user’s password requires you to authenticate yourself by entering your password when prompted. 5 Click OK. Polycom, Inc.
Page 328: Conference Rooms Procedures
Dial-out Presets and do the following: a Ensure that this room or user has a chairperson passcode and that you’ve selected a conference template that’s linked to a Polycom RealPresence Collaboration Server or RMX conference IVR service and requires a chairperson to start the conference.
Page 329: Groups
Edit Conference Room Dialog Users Procedures Groups Groups functionality is available only if your Polycom RealPresence DMA system is integrated with an Active Directory. User groups are defined in your Active Directory and imported into the Polycom RealPresence DMA system from there.
Page 330 The Groups page provides access to information about enterprise groups. From it, you can: ● Import enterprise groups. ● Specify Polycom RealPresence DMA system roles to be assigned to members of a group. ● Specify a conference template and MCU pool order to be used for a group.
Page 331: Import Enterprise Groups Dialog
If Class of service is selected, specifies the maximum bit rate for the group. Minimum downspeed bit rate If Class of service is selected, specifies the minimum bit rate to which the (kbps) group’s calls can be reduced (downspeeded). Polycom, Inc.
Page 332 Settings). The template assignment can be made at the conference room level, AD group level, or system default level. It defines the conference properties (or links to the Polycom MCU profile) used for its conferences. See Conference Templates. MCU pool order Select to assign the group an MCU pool order other than the system’s default...
Page 333 Admin > Conference Manager > Conference Settings page. Note: This property is visible only if the Publish presence for Polycom conference contacts check box is enabled on the Admin > Conference Manager >...
Page 334: Enterprise Groups Procedures
The ability to assign defined Polycom RealPresence DMA user roles to an enterprise group lets you manage administrative access to the Polycom RealPresence DMA system in your Active Directory.
Page 335: Login Sessions
Host Address The IP address from which the user logged in. Node Name The Polycom RealPresence DMA system server on which the user logged in. Creation Time The time and date when the user logged in. To terminate a user’s login session 1 In the Login Sessions list, select the login session you want to terminate.
Page 336: Change Password Dialog
Enter a new password. The password must satisfy the local password rules specified for the system (see Local Password). Confirm new password Retype the password to confirm that you entered it correctly. See also: Security Settings Users and Groups Polycom, Inc.
Page 337: System Management And Maintenance
● Administrator Responsibilities As a Polycom RealPresence DMA system administrator, you’re responsible for the installation and ongoing maintenance of the system. You should be familiar with the following configurations, tasks, and operations: ● Installing licenses when the system is first installed and when additional call capacity is added. See Licenses.
Page 338: Administrative Best Practices
Proper time management helps ensure that your cluster operates efficiently and helps in diagnosing any issues that may arise in the future. Proper system time is also essential for accurate audit and CDR data. ● Unless otherwise instructed by Polycom Global Services, always use the High Security setting. See Security Settings.
Page 339: Provisioner Responsibilities
● Export CDRs regularly and back them up securely (preferably offsite as well as onsite). Provisioner Responsibilities As a Polycom RealPresence DMA system provisioner, you have access to many of the same features and functions as the system administrator (see...
Page 340: Microsoft Active Directory Health
Any values above zero are indicators of bandwidth saturation and suggest that it’s time to increase network bandwidth. Microsoft Active Directory health If the Polycom RealPresence DMA system is integrated with an Active Directory, check the following (you must be logged in as an enterprise user): ● Reports > Microsoft Active Directory Integration (see Active Directory Integration Report).
Page 341: Security Configuration
Exporting Network Usage Data. CDR export If you want to preserve detailed call and conference history data in spreadsheet form off the Polycom RealPresence DMA system, periodically download the system’s CDR (call detail record) data to your PC. Call Detail Records (CDRs).
Page 342: Active Directory Integration Pane
The total for all clusters includes the total of all legs of cluster-spanning calls. If H.323 signaling is enabled, the call mode (direct or routed) is also shown. Click a column heading to sort on that column. Click the Link button to go to the Active Calls page. Polycom, Inc.
Page 343: Call Server Registrations 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.
Page 344: Conference Manager Mcus Pane
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.
Page 345: Exchange Server Integration Pane
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: ...
Page 346: License Status Pane
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.
Page 347: Territory Status 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.
Page 348: Alerts
(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.
Page 349: Supercluster Status
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.
Page 350: Territory Status
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.
Page 351 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.
Page 352: Asynchronous Operation
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.
Page 353: Active Directory Integration
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 <system-name>...
Page 354 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.
Page 355: Exchange Server Integration
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.
Page 356: Database Status
<b-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.
Page 357: Lync Integration
Alert 2602 Cluster <cluster>: Cannot authenticate with <lyncserver> 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 >...
Page 358: Signaling
The following alerts provide information on signaling events and changes in signaling status. Alert 3001 No signaling interface enabled for cluster <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.
Page 359: Certificate
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.
Page 360 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 <cluster>: One or more CA certificates will expire within 30 days.
Page 361: Licenses
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.
Page 362: Networks
Either the cluster contains two servers but was incorrectly configured as a single-server cluster, or there is only one server in the cluster but something is connected its GB2 port. On a single-server cluster, don’t use the server’s GB2 port for anything. Polycom, Inc.
Page 363 ● The virtual or management host name A or AAAA record configured in the specified DNS server is missing ● The virtual or management host name A or AAAA record configured in the specified DNS server references the incorrect address Polycom, Inc.
Page 364: Server Resources
The alert text describes the nature of the problem, which may require additional configuration of the DNS server(s) or network settings for the cluster. Refer to the Polycom RealPresence DMA 7000 System Operations Guide for more information regarding DNS configuration.
Page 365 The cause may also be a system health problem or a runaway process. Go to Maintenance > Troubleshooting Utilities > Top to see if a process is monopolizing CPU resources. Create a new backup and download it, and then contact Polycom Global Services. See also: Alerts Polycom, Inc.
Page 366: Data Synchronization
Cluster <cluster>: Local time differs by more than ten seconds between servers. The time on the two servers in the specified cluster has drifted apart by an unusually large amount. This may indicate a configuration issue or a problem with one of the servers. Contact Polycom Global Services. See also: Alerts Polycom, Inc.
Page 367: System Health And Availability
In the specified cluster, the local users are different on the two servers, indicating that their internal databases aren’t consistent. Try to determine which server’s data is incorrect and reboot it. See also: Alerts System Health and Availability The following alerts provide information on changes in the health and availability of the system. Polycom, Inc.
Page 368: Mcus
Click the link to go to the Network > DMAs page. See also: Alerts MCUs The following alerts provide information on changes in the status of connected MCUs. Polycom, Inc.
Page 369 Polycom MCUs use synchronous communications. In order to efficiently manage multiple calls as quickly as possible, the Polycom RealPresence DMA system uses multiple connections per MCU. By default, a RealPresence Collaboration Server or RMX MCU allows up to 20 connections per user (the MAX_NUMBER_OF_MANAGEMENT_SESSIONS_PER_USER system flag).
Page 370 MCU <mcu> call failure rate is > 0.4 and < 0.8. The specified MCU’s number of consecutive failed calls has changed, and the calculated failure rate metric is now between 0.4 (some calls are failing) and 0.8 (most calls are failing). Polycom, Inc.
Page 371 MCU (perhaps a media card has been removed or added). This alert appears as soon as the video port capacity of this MCU becomes 0, and is automatically cleared after two minutes. Click the link to go to the Network > MCU > MCUs page. See also: Alerts Polycom, Inc.
Page 372: Endpoints
<N> number of conferences in a row. This condition is likely caused by an MCU software issue. This alert replaces Alert 4016. Click the link to go to the Network > MCU > MCUs page. See also: Alerts Alert 4016 Endpoints The following alerts provide information on communication issues with endpoints. Polycom, Inc.
Page 373 H.323 ID or SIP URI of the device doesn't specify its endpoint number or the number of endpoints in the ITP system, as it should. The H.323 ID or SIP URI must be updated on the endpoints of the ITP system. See Naming ITP Systems Properly for Recognition by the Polycom RealPresence DMA System. See also: Alerts Alert 5002 One or more endpoints are sending too much <signaling_type>...
Page 374: Conference Manager
A preset dialout from the conference using the conference room identifier <VMR> has failed for the specified reason. This alert automatically clears after two minutes. Click the link to go to the Network > Users page to find the specified VMR number and begin troubleshooting. See also: Alerts Polycom, Inc.
Page 375: Lync Presence Publishing
<NN> of <MM> Polycom conference contacts will not be published due to Lync server configuration ‘MaxEndpointExpiration’ value <expire>. The system was unable to publish presence status for the specified number of Polycom conference contacts because the Lync server has been configured with a maximum endpoint logon period of <expire> seconds.
Page 376 Polycom conference contacts configured for publishing exceeds ‘Maximum Polycom conference contacts to publish’ configured on the system. The system was unable to publish presence status for the specified number of Polycom conference contacts because the Maximum Polycom conference contacts to publish value configured in the Lync server’s External SIP Peer properties has been reached.
Page 377 Admin > Integrations > Microsoft Active Directory page. Click the link to go to the Admin > Integrations > Microsoft Active Directory page, and verify that the Domain, Domain/user name, and Password fields are correct. See also: Alerts Polycom, Inc.
Page 378: Call Server
For details on enabling Windows Remote Management on your Active Directory system, refer to the Polycom Unified Communications in a Microsoft Environment Solution Deployment Guide. Click the link to go to the Admin > Integrations > Microsoft Active Directory page.
Page 379: Call Bandwidth Management
If your system is a two-server cluster, in the File Download dialog you can select which server’s logs to download. ● Download Archived Logs — Downloads the selected log file archive. Polycom, Inc.
Page 380: System Logs Procedures
The archives are Gzip-compressed tar files. Each archive contains a number of individual log files. The detailed technical data in the log files is not useful to you, but can help Polycom Global Services resolve problems and provide technical support for your system.
Page 381 Click the command to see the Download History list. 3 In the Actions list, click Delete Archived Logs. A confirmation dialog appears. 4 Click Yes. See also: Management and Maintenance Overview Recommended Regular Maintenance Alerts Call Detail Records (CDRs) Polycom, Inc.
Page 382: Troubleshooting Utilities
Each command is run on each server in the cluster, and the results are displayed in a separate panel for each server. Ping Use Ping to verify that the Polycom RealPresence DMA system’s servers can communicate with another device in the network. To run ping on each server 1 Go to Maintenance >...
Page 383: Sar
This operation may take several minutes and may consume significant memory and CPU resources. Polycom recommends against invoking this utility during peak traffic periods or while other resource intensive tasks are underway (such as system backups, CDR downloads, or Microsoft Active Directory integration updates).
Page 384: Diagnostics For Your Polycom Server
Recommended Regular Maintenance Diagnostics for your Polycom Server If your RealPresence DMA system was shipped with a Polycom Rack Server 620, you need to have a monitor and USB keyboard in order to run server diagnostics. Perform these diagnostics only under the guidance of Polycom Global Services.
Page 385 For a two-server cluster, make system configuration changes, including restores, only when both servers are running and clustered. If the system is shut down or in a bad state, the Polycom RealPresence DMA USB Configuration Utility (on the USB flash drive used to initially configure the network and system parameters) can restore the Polycom RealPresence DMA system from a backup file (full or configuration-only) that you load onto the USB flash drive.
Page 386: Confirm Restore Dialog
Restoring from a backup restarts the system and terminates all active conferences. Note: Restoring backups with resource management integration You can restore the system while it’s integrated with a Polycom RealPresence Resource Manager system, but the result depends on the state when the backup you’re restoring from was made.
Page 387 The system asks if you want to restore now from the backup file you just uploaded. 6 If you don’t want to restore (and restart the system) now, click Manually Later. When you’re ready to restore, use the procedure that follows this one. Polycom, Inc.
Page 388 4 Select the backup file from which you want to restore. 5 In the Actions list, click Restore Selected. The Confirm Restore dialog appears. 6 Read the warning, make sure that you want to continue, select which data you want to restore, and click OK. Polycom, Inc.
Page 389 If the system was integrated with AD, go to Admin > Integrations > Microsoft Active Directory and re-enable the integration. To restore from a backup file on the Polycom RealPresence DMA system’s USB flash drive Note: Restoring with the USB configuration utility When you use the USB Configuration Utility to restore a backup, you can’t select which data to...
Page 390 6 Select the backup file from which you want to restore the system and click Open. The utility displays an error message if the file isn’t a valid Polycom RealPresence DMA system backup. Otherwise, it confirms that the backup file is in place.
Page 391: Upgrading The Software
Note: Virtual host names and IP addresses unnecessary for single servers This version of the Polycom RealPresence DMA system eliminates the need for virtual host name(s) and IP addresses in a single-server system. 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...
Page 392: Basic Upgrade Procedures
Using a maintenance window with no calls on the system also eliminates any concerns about whether the remaining clusters of a supercluster have sufficient capacity to handle the load of the cluster being upgraded. Polycom, Inc.
Page 393 Most upgrades will require a restart. 7 If this cluster is part of a supercluster, do the following: a If integrated with a Polycom RealPresence Resource Manager system, go to Admin > Integrations > RealPresence Resource Manager and terminate the integration.
Page 394 Go to Network > Site Topology > Territories and reassign territory responsibilities back to this cluster. Or, if previously integrated with a Polycom RealPresence Resource Manager system, go to Admin > Integrations > RealPresence Resource Manager and reestablish the integration.
Page 395 3 If this cluster is part of a supercluster and you’re rolling back after rejoining the supercluster, do the following: a If integrated with a Polycom RealPresence Resource Manager system, go to Admin > Integrations > RealPresence Resource Manager and terminate the integration.
Page 396: Incompatible Software Version Supercluster Upgrades
Go to Network > Site Topology > Territories and reassign territory responsibilities back to this cluster. Or, if previously integrated with a Polycom RealPresence Resource Manager system, go to Admin > Integrations > RealPresence Resource Manager and reestablish the integration.
Page 397: Factors To Consider For An Incremental Supercluster Upgrade
To successfully redirect these endpoints to a Call Server in the new supercluster, one of the following may be necessary:  Managed endpoints may be re-provisioned by the Polycom RealPresence Resource Manager system, or third-party endpoint management system responsible for them.
Page 398: Simplified Supercluster Upgrade (Complete Service Outage)
2 On each cluster in the supercluster, do the following: a Go to Maintenance > Software Upgrade. b In the Actions list, click Upload. c Select the upgrade package file and click Open. The File Upload dialog indicates when the upload is complete. Polycom, Inc.
Page 399 LCDs display DMA Clustered (in a single-server system, the LCD displays DMA Ready), and you’re able to log back in. 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.
Page 400 Go to Network > Site Topology > Territories and restore the territory assignments that you recorded at step of this procedure. Or, if previously integrated with a Polycom RealPresence Resource Manager system, go to Admin > Integrations > RealPresence Resource Manager and reestablish the integration.
Page 401: Complex Supercluster Upgrade (Some Service Maintained)
When upgrading from a version prior to 6.1 to a version 6.1 or later system, you must contact your Polycom sales representative to obtain a license for the Virtual Edition system. Virtual Edition systems have no basic call capability if they are not licensed.
Page 402: Expanding An Unpatched System
1 Unpack, inspect, and physically install the second server as described in its Getting Started Guide. Mount it in the rack adjacent to the first Polycom RealPresence DMA system server (or close enough to connect them with an Ethernet cable).
Page 403: Expanding A Patched System
1 Unpack, inspect, and physically install the second server as described in its Getting Started Guide. Mount it in the rack adjacent to the first Polycom RealPresence DMA system server (or close enough to connect them with an Ethernet cable).
Page 404: Replacing A Failed Server
Replacing a server is essentially the same process as adding a second server to a single-server system. As in that situation, you must make sure that both servers are running the same version of the Polycom RealPresence DMA system software.
Page 405 System Management and Maintenance Caution: Always shut down properly Don’t turn off a Polycom RealPresence DMA system server by simply unplugging it or otherwise removing power, especially if it’s going to remain off for some time. If a server loses power without being properly shut down, the RAID controller fails to shut down, eventually depleting its battery.
Page 406: System Reports
System Reports This chapter section describes the following Polycom ® RealPresence ® Distributed Media Application™ (DMA ® ) 7000 system reports topics: Alert History ● Call History ● Conference History ● Call Detail Records (CDRs) ● Registration History Report ●...
Page 407 CDRSearchExport.tar. This is a troubleshooting feature. To aid in resolving a problem, Polycom Global Services may ask you to use specific search criteria to retrieve certain call records, download them, and send the file to them for analysis of the records.
Page 408: Export History
After you search for conferences, the Conference History page lists all the conferences in the time range you specified. If there are more than 500, the first page lists the first 500, and the arrow buttons below the list let you view other pages. The following table describes the fields in the list. Polycom, Inc.
Page 409: Export History
Time the call ended (session closed). Originator The originating device’s display name, name, alias, or IP address (in that order of preference), depending on what it provided in the call signaling. If the originator is an MCU, the MCU name. Polycom, Inc.
Page 410: Conference Events
Name of the call property. Value Value assigned to the property. Time Date and time of the property change. Sequence Identifies when in the order of changes to this call this property change occurred. See also: System Reports Call History Polycom, Inc.
Page 411: Call Detail Records (Cdrs)
System Reports Call Detail Records (CDRs) In addition to the online call and conference history reports, the Polycom RealPresence DMA system generates call detail records (CDRs) for all calls and conferences, which you can download. The procedure for exporting CDRs and the record layouts are described in the sections that follow.
Page 412 For Polycom and Cisco Immersive Telepresence (ITP) rooms using Cisco TIP signaling, all the codecs (endpoint devices in the room) signal using a single session, producing a single CDR. For Polycom ITP systems using SIP signaling (but not H.323), if the codecs follow the prescribed naming convention (see...
Page 413 The RealPresence DMA cluster handling the VMR, or blank if not a VMR call. VEQCluster The RealPresence DMA cluster handling the VEQ, or blank if no VEQ. userRole If VMR call, the role of the caller in conference: • PARTICIPANT • CHAIRPERSON (entered passcode) Null if not VMR call. Polycom, Inc.
Page 414 For an immersive telepresence room, the number of screens the room has. For a Polycom SIP ITP call, this is determined from the system name; for a Polycom or Cisco TIP call, it’s the x-cisco-multiple-screen parameter value.
Page 415 Zero (0) if the call was audio only. Available only for AVC calls using SIP or TIP signaling to a version 8.1 or newer hardware-based Polycom MCU with MPMx cards. Otherwise, blank. videoPeakJitter The peak jitter (in milliseconds) on the video channel. Zero (0) if the call was audio only.
Page 416: Conference Record Layouts
Changes each time the format of CDRs changes. type CONF confType One of the following: • PCO — for Polycom Conferencing for Outlook (calendared) conferences • LYNC — for Lync conferences • AD-HOC — for all other conferences cluster The RealPresence DMA cluster serving the VMR.
Page 417 Note: Voice calls may use video ports if voice ports aren’t available. Note: The RealPresence DMA system reports port numbers based on resource usage for CIF calls. Version 8.1 and later Polycom MCUs report port numbers based on resource usage for HD720p30 calls. In general, 3 CIF = 1 HD720p30, but it varies depending on bridge/card type and other factors.
Page 418: Registration History Report
Conference History Registration History Report If the Polycom RealPresence DMA system Call Server is providing H.323 gatekeeper or SIP registrar services, the Registration History page provides access to information about registered devices. It also provides information about external SIP peers with which the system is registered, if any.
Page 419: Registration History Procedures
3 For more search options, click the down arrow to the left. The search panel expands, revealing a complete set of registration start and end time options and the Territory, Owner, Site, Protocol, Status, and Device Type filters. Polycom, Inc.
Page 420: Active Directory Integration Report
Conference History Active Directory Integration Report If the Polycom RealPresence DMA system is integrated with your Active Directory, it reads the Active Directory daily to refresh the information in its cache. It also rereads the directory whenever you update the directory integration settings (Admin >...
Page 421 • Not required: no groups from that domain have been imported into the Polycom RealPresence DMA system and all attributes needed were in the global catalog. • Partially loaded or Unable to load: see Error Message and the list of groups with incomplete information for more details.
Page 422: Orphaned Groups And Users Report
The Orphaned Groups and Users page reports information about enterprise users and groups that are no longer in the Active Directory or are no longer accessible to the Polycom RealPresence DMA system, but for which the system has local data (typically, local conference rooms or customized enterprise conference rooms).
Page 423: Conference Room Errors Report
Active Directory Integration Report Enterprise Passcode Errors Report Conference Room Errors Report If the Polycom RealPresence DMA system is integrated with your Active Directory, it can create a conference room (virtual meeting room) for each enterprise user. See Microsoft Active Directory ®...
Page 424: Exporting Conference Room Errors Data
You can open the CSV file with Microsoft Excel or another spreadsheet application. The file contains the same data you see displayed on the Conference Room Errors page. See also: ® Microsoft Active Directory Integration Active Directory Integration Report Orphaned Groups and Users Report Polycom, Inc.
Page 425: Enterprise Passcode Errors Report
Passcodes for Enterprise Users. The Polycom RealPresence DMA system reads the Active Directory daily to refresh the information in its cache. It also rereads the directory whenever you update the directory integration settings (Admin > Integrations > Microsoft Active Directory).
Page 426: Exporting Enterprise Passcode Errors Data
● The cluster, territory, or throttlepoint (site, site link, or subnet) whose data you want to see. ● The specific call, QoS, and bandwidth data you want to see. The data matching the criteria you chose is graphed below. Polycom, Inc.
Page 427: Exporting Network Usage Data
Maximum jitter of all QoS reports of all video channels in the scope during the time interval (milliseconds). avg_video_delay Mean delay of all QoS reports of all video channels in the scope during the time interval (milliseconds). Polycom, Inc.
Page 428 Max concurrent calls using H.323 signaling in the scope during the time interval. gateway_calls Max concurrent calls using the SIP to H.323 gateway in the scope during the time interval. conference_calls Max concurrent Conference Manager calls in the scope during the time interval. Polycom, Inc.
Page 429 6 When the download is complete, click Close. You can open the CSV file with Microsoft Excel or another spreadsheet application. The file contains a line for each data point. See also: System Reports Call History About Site Topology Polycom, Inc.
Page 430: Polycom Realpresence Dma System Snmp Support
SNMP management systems, see the appropriate documentation for your application. ● An SNMP agent The SNMP agent is the software component within the Polycom system that maintains the data for the system and reports these data, as needed, to managing systems. The agent and MIB reside on the same system.
Page 431: Snmp Notifications
A key feature of SNMP is the ability to generate notifications from an SNMP agent. Notifications are called as such because they are sent, unsolicited and asynchronous to the SNMP manager from the Polycom system. Notifications can indicate improper user authentication, restarts, the closing of a connection, loss of connection to another system, or other significant events.
Page 432: Configure Snmp
Polycom RealPresence DMA System SNMP Support Configure SNMP The RealPresence DMA system uses SNMP to provide a standardized framework and a common language used monitoring and managing the system. Note that you should understand how your SNMP management system is configured to properly configure the RealPresence DMA system’s SNMP transport protocol, version, authentication, and privacy settings.
Page 433: Add An Snmp Notification User
Polycom RealPresence DMA System SNMP Support Setting Description Community For SNMPv2c, specifies the context for the information, which is the SNMP group to which the devices and management stations running SNMP belong. The RealPresence DMA system has only one valid context—by default, public—which is identified by this Community name.
Page 434: Edit Notification User Dialog
Polycom RealPresence DMA System SNMP Support Field Description Encryption type The privacy protocol for the connection between the RealPresence DMA system and the SNMP agent. Encryption type options: • No encryption • DES–Uses a 56-bit key with a 56-bit salt to encrypt the SNMPv3 packet •...
Page 435: Edit Notification Agent Dialog
Polycom RealPresence DMA System SNMP Support 1 Click Add Agent. 2 Configure the settings in the Add Notification Agent dialog box. Field Description Enable agent Select to enable the notification agent. Clear to stop using this agent without deleting it.
Page 436: Download Mibs
Notification Users list. Download MIBs You can download any of the Polycom MIBs from the SNMP Settings page. Polycom recommends using a MIB browser to explore the DMA system MIB. The DMA system MIB is self-documenting, including information about the purpose of specific traps and inform notifications.
Page 437 A definition file for standard conventions included for reference. Third-Party MIB-Dell-10892 The primary MIB for the Polycom-branded Dell server. It provides 36 traps from the server motherboard, including system type, voltages, and temperature readings. For more information, see the Dell SNMP documentation.

Polycom RealPresence DMA 7000 System Operation Manual

Polycom Realpresence DMA

Polycom Realpresence DMA System Initial Configuration Summary

System Security

Local Cluster Configuration

Device Management

MCU Management

Integrations with Other Systems

Conference Manager Configuration

Superclustering

Call Server Configuration

Site Topology

Users and Groups

System Management and Maintenance

Quick Links

Related Manuals for Polycom RealPresence DMA 7000 System

Summary of Contents for Polycom RealPresence DMA 7000 System