Operations Guide 6.
Copyright© 2014, Polycom, Inc. All rights reserved. No part of this document may be reproduced, translated into another language or format, or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of Polycom, Inc. 6001 America Center Drive San Jose, CA 95002 USA Polycom®, the Polycom logo and the names and marks associated with Polycom products are trademarks and/or service marks of Polycom, Inc.
Contents Polycom® RealPresence DMA® 7000 System Overview . . . . . . . . . . . . . . . . . . . 15 Introduction to the Polycom RealPresence DMA System . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 The Polycom RealPresence DMA System’s Primary Functions . . . . . . . . . . . . . . . . . . . . 15 The Polycom RealPresence DMA System’s Three Configurations . . . . . . . . . . . . . . . . . 18 System Capabilities and Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents System Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Security Certificates Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 How Certificates Work . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Forms of Certificates Accepted by the Polycom RealPresence DMA System . . . . . . . . .
Contents Logging Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 Alerting Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 Local Cluster Configuration Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 Add Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents MCU Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124 MCUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124 Considerations when using MCUs with the RealPresence DMA system . . . . . . . . . . . . 126 Add MCU Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129 Edit MCU Dialog Box . . .
Contents Resource Management System Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180 Join Resource Management System Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181 Resource Management System Integration Procedures . . . . . . . . . . . . . . . . . . . . . . . . 181 Juniper Networks SRC Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183 Juniper Networks SRC Page . . . . . . . . . . . . . . .
Contents The Default Dial Plan and Suggestions for Modifications . . . . . . . . . . . . . . . . . . . . . . . . 241 Add Dial Rule Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244 Edit Dial Rule Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248 Preliminary/Postliminary Scripting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Edit Territory Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296 Network Clouds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297 Add Network Cloud Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297 Edit Network Cloud Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Certificates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336 Network usage data export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336 CDR export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336 Dashboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Alert 2401 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349 Alert 2402 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349 Alert 2601 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350 Alert 2602 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Alert 3803 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361 Alert 4001 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361 Alert 4002 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361 Alert 4003 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Backup and Restore Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376 Upgrading the Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380 Basic Upgrade Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382 Incompatible Software Version Supercluster Upgrades . . . . . . . . . . . . . . . . . . . . . . . . .
Contents SNMP Framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419 SNMP Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420 SNMP Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420 Configure SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Polycom® RealPresence DMA® 7000 System Overview This chapter provides an overview of the Polycom® Distributed Media Application™ (RealPresence DMA®) 7000 system.
Polycom® RealPresence DMA® 7000 System Overview The Polycom RealPresence DMA system integrates with your Microsoft® Active Directory®, automating the task of provisioning users with virtual meeting rooms (VMRs), which are available for use at any time for multipoint video conferencing. Combined with its advanced resource management, this makes reservationless (ad hoc) video conferencing on a large scale feasible and efficient, reducing or eliminating the need for conference scheduling.
Polycom® RealPresence DMA® 7000 System Overview ● Billing and usage data retrieval ● Resource availability queries The API uses XML encoding over HTTPS transport and adheres to a Representational State Transfer (REST) architecture.
Polycom® RealPresence DMA® 7000 System Overview For multipoint conferencing, the MCU doesn't have to do processing-intensive mixing and transcoding to optimize the experience for each device. Instead, it simply passes the video stream from each device to each device, including the enhancement layers that provide the best quality the device can support. Polycom’s SVC solution focuses on the temporal and spatial dimensions.
Polycom® RealPresence DMA® 7000 System Overview ● Ability to ping the other server’s public physical address ● Ability to ping the default gateway In the event of a tie, the server already hosting the public virtual address wins. Failover to the backup server takes about five seconds in the event of a graceful shutdown and about twenty seconds in the event of a power loss or other failure.
Polycom® RealPresence DMA® 7000 System Overview Note: Clusters vs. Superclusters Technically, a standalone Polycom RealPresence DMA system (two-server or single-server) is a supercluster that contains one cluster. All the system configuration and other data that’s shared across a supercluster is kept in the same data store. At any time, another Polycom RealPresence DMA system can be integrated with it to create a two-cluster supercluster that shares its data store.
Polycom® RealPresence DMA® 7000 System Overview ● Number of IRQ messages sent per second: 100 ● Number of history records retained per cluster: 500,000 registration history 2,000,000 registration signaling history 500,000 call history 12,500,000 call signaling history 200,000 conference history 10,000 CDR export history System Port Usage The table below lists the inbound ports that may be open on the Polycom RealPresence DMA system, depending on signaling and security settings, integrations, a
Polycom® RealPresence DMA® 7000 System Overview Port Protocol Description 8444 TCP HTTPS. Supercluster communication. 8989 TCP LDAP. OpenDJ replication (superclustering). 9090 TCP HTTPS. Upgrade status monitoring (only while upgrade process is running). 36000-61000 TCP Ephemeral port range. The table below lists the remote ports to which the Polycom RealPresence DMA system may connect, depending on signaling and security settings, integrations, and system configuration.
Polycom® RealPresence DMA® 7000 System Overview Port Protocol Description 8989 TCP OpenDJ replication (superclustering). 36000-61000 TCP Ephemeral port range. Polycom Solution Support Polycom Implementation and Maintenance services provide support for Polycom solution components only. Additional services for supported third-party Unified Communications (UC) environments integrated with Polycom solutions are available from Polycom Global Services and its certified Partners.
Polycom® RealPresence DMA® 7000 System Overview 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. Settings Dialog Box The Settings dialog box opens when you click the button to the right of the menus. It displays your user name and the address of the RealPresence DMA server you’re logged into.
Polycom® RealPresence DMA® 7000 System Overview Menu/Icon Admin Provisioner Auditor MCU > MCUs1 • • MCU > MCU Pools1 • • MCU > MCU Pool Orders1 • • Site Statistics1 • • Site Link Statistics1 • • Site Topology > Sites1 • • Site Topology > Site Links1 • • Site Topology > Site-to-Site Exclusions1 • • Site Topology > Network Clouds1 • • Site Topology > Territories1 • • External Gatekeeper1 • • External SIP Peer1 • • External H.
Polycom® RealPresence DMA® 7000 System Overview Menu/Icon Admin Provisioner Auditor Maintenance System Log Files4 • Troubleshooting Utilities > Ping, Traceroute, Top, I/O Stats, SAR, NTP Status • Shutdown and Restart • Software Upgrade • Backup and Restore • • Admin > Conference Manager > Conference Settings • Conference Templates • IVR Prompt Sets • Shared Number Dialing • Admin > Call Server > Call Server Settings • Domains • Dial Rules • Hunt Groups • Registration Policy
Polycom® RealPresence DMA® 7000 System Overview Menu/Icon Admin Provisioner Auditor Admin > Login Policy Settings > Local Password • Session • Local User Account • Banner • Access Policy Settings • Admin > Local Cluster > Network Settings • Signaling Settings • Time Settings • Licenses • Logging Settings • SNMP Settings • Security Settings • Certificates • About RealPresence DMA 7000 • • • Help Contents • • • Settings. Displays Settings dialog box. • • • Log Out.
Polycom® RealPresence DMA® 7000 System Overview Open Source Software License Information Refer to the Polycom RealPresence DMA 7000 System Offer of Open Source Software for a list of the open source software packages used in the Polycom RealPresence DMA system, the applicable license for each, and the internet address where you can find it. To obtain the source code for any of these packages, email your request to Open.Source@Polycom.com.
Polycom® RealPresence DMA® System Initial Configuration Summary This chapter describes the configuration tasks required to complete your implementation of a new Polycom® RealPresence® Distributed Media Application™ (DMA®) 7000 system once installation and initial network configuration are complete. This chapter assumes you’ve completed the server configuration procedure in the Getting Started Guide (available at support.polycom.
Polycom® RealPresence DMA® System Initial Configuration Summary Add Required DNS Records for the Polycom RealPresence DMA System Note: Consult an Expert If you’re not familiar with DNS administration, the creation of various kinds of DNS resource records (A/AAAA,NAPTR, NS, and SRV), your enterprise’s DNS implementation, and tuning for load balancing (if needed), please consult with someone who is.
Polycom® RealPresence DMA® System Initial Configuration Summary ● SRV records for each transport protocol that identify the host names of the SIP proxies that service a particular domain. Configure these statically to point to the host names of the Call Servers in the domain. Here are example records for two clusters: _sips._tcp.example.com. _sips._tcp.example.com. dma-europe.example.com. _sip._tcp.example.com. _sip._tcp.example.com. dma-europe.example.com. _sip._udp.example.com. _sip._udp.example.com.
Polycom® RealPresence DMA® System Initial Configuration Summary specify is the one in the Call server sub-domain controlled by RealPresence DMA field on the Embedded DNS page. Here are example records for two two-server clusters: callservers.example.com. callservers.example.com. callservers.example.com. callservers.example.com. 86400 86400 86400 86400 IN IN IN IN NS NS NS NS dma-asia-server1.example.com. dma-asia-server2.example.com. dma-europe-server1.example.com. dma-europe-server2.example.com.
Polycom® RealPresence DMA® System Initial Configuration Summary Note: API Licenses An API license isn’t required in order for a Polycom RealPresence Resource Manager system to access the API. It’s only needed for a client application that you or a third party develop. License the RealPresence DMA System, Appliance Edition You should have received either one or two license numbers for each cluster, depending on whether you ordered a single-server or two-server cluster.
Polycom® RealPresence DMA® System Initial Configuration Summary Enable and configure SIP digest authentication. Enable and configure special handling for untrusted (“unauthorized” or “guest”) calls from SIP session border controllers (SBCs). To set up signaling, follow the procedure in Configure Signaling on page 83.
Polycom® RealPresence DMA® System Initial Configuration Summary 3 Assign the Administrator role to your named enterprise account, and remove the Polycom RealPresence DMA system’s user roles (see User Roles Overview on page 301) from the service account used to integrate with Active Directory. See Connect to Microsoft Active Directory® on page 36 and Microsoft Active Directory® Integration on page 152. 4 Log out and log back in using your enterprise user ID and password.
Polycom® RealPresence DMA® System Initial Configuration Summary You must organize MCUs configured as conferencing resources into one or more MCU pools (logical groupings of media servers). Then, you can define one or more MCU pool orders that specify the order of preference in which MCU pools are used.
Polycom® RealPresence DMA® System Initial Configuration Summary Before integrating with Active Directory, be sure that one or more DNS servers are specified (this should have been done during installation and initial setup). See Network Settings on page 63.
Polycom® RealPresence DMA® System Initial Configuration Summary When you add a custom conference room to a user (either local or enterprise), you can choose which template that conference room uses. To add conference templates, see Conference Templates Procedures on page 216. To change conference settings, see Conference Settings on page 185. To customize the conferencing experience for an enterprise group, see Enterprise Groups Procedures on page 329.
System Security This chapter describes the following Polycom® RealPresence® Distributed Media Application™ (DMA®) 7000 system security topics: ● Security Certificates Overview ● Certificate Settings ● Certificate Procedures ● Security Settings ● The Consequences of Enabling Maximum Security Mode ● Login Policy Settings ● Reset System Passwords Security Certificates Overview How Certificates Work X.
System Security Encoding Protocol / File Type PEM (Base64-encoded ASCII text) PKCS #7 protocol P7B file Certificate chain containing: • A signed certificate for the system, authenticating its public key. • The CA’s public certificate. • Sometimes intermediate certificates. Upload file or paste into text box. CER (single certificate) file Signed certificate for the system, authenticating its public key. Upload file or paste into text box.
System Security 2 When the Polycom RealPresence DMA system connects to a Microsoft Active Directory server, it may present a certificate to the server to identify itself. If Active Directory is configured to require a client certificate (this is not the default), the Polycom RealPresence DMA system offers the same SSL server certificate that it offers to browsers connecting to the system management interface.
System Security Frequently Asked Questions Q. Is it secure to send my certificate request through email? A. Yes. The certificate request, signed certificate, intermediate certificates, and authority certificates that are sent through email don’t contain any secret information. There is no security risk in letting untrusted third parties see their contents.
System Security Certificate Settings The following table describes the fields on the Certificate Settings page. Column Description Enable OCSP Enables the use of Online Certificate Status Protocol as a means of obtaining the revocation status of a certificate presented to the system. If OCSP responder URL is not specified, the system checks the certificate’s AuthorityInfoAccess (AIA) extension fields for the location of an OCSP responder: • If there is none, the certificate fails validation.
System Security See also: Security Certificates Overview on page 39 Certificate Signing Request Dialog Box on page 44 Add Certificates Dialog Box on page 45 Certificate Details Dialog Box on page 45 Certificate Procedures on page 46 Certificate Information Dialog Box The Certificate Information dialog box appears when you click Create Certificate Signing Request in the Actions list (if a signing request has already been issued, you’re first asked whether to use the existing one or create a new one).
System Security Add Certificates Dialog Box The Add Certificates dialog box appears when you click Add Certificates in the Actions list. It lets you install signed certificates or certificate chains. You can do so in two ways: ● Upload a PFX, PEM, or P7B certificate file. ● Paste PEM-format certificate text into the dialog box. The following table describes the fields in the dialog box.
System Security See also: Security Certificates Overview on page 39 Certificate Settings on page 43 Certificate Procedures Certificate procedures include the following: ● Install your chosen certificate authority’s public certificate, if necessary, so that the Polycom RealPresence DMA system trusts that certificate authority. ● Create a certificate signing request to submit to the certificate authority.
System Security 2 If you’re using a certificate authority that isn’t listed, obtain a copy of your certificate authority’s public certificate. The certificate must be either a single X.509 certificate or a PKCS#7 certificate chain. If it’s ASCII text, it’s in PEM format, and starts with the text -----BEGIN CERTIFICATE-----. If it’s a file, it can be either PEM or DER encoded. 3 In the Actions list, select Add Certificates.
System Security 5 Copy the entire contents of the Encoded Request box (including the text -----BEGIN NEW CERTIFICATE REQUEST----- and -----END NEW CERTIFICATE REQUEST-----) and submit it to your certificate authority. Depending on the certificate authority, your CSR may be submitted via email or by pasting into a web page. 6 Click OK to close the dialog box. When your certificate authority has processed your request, it sends you a signed public certificate for your Polycom RealPresence DMA system.
System Security If you have a PFX, P7B, or single certificate file, click Upload certificate, enter the password (if any) for the file, and browse to the file or enter the path and file name. If you have PEM-format text, copy the certificate text, click Paste certificate, and paste it into the text box below. You can paste multiple PEM certificates one after the other. 4 Click OK.
System Security 3 In the Actions list, select Display Details and confirm that you’ve selected the correct certificate. Then click OK. 4 In the Actions list, select Delete Certificate. 5 When asked to confirm, click Yes. A dialog box informs you that the certificate has been deleted. 6 Click OK. 7 Click Restart to Apply Saved Changes, and when asked to confirm that you want to restart the system so that certificate changes can take effect, click OK.
System Security Caution: High Security Setting Recommended We recommend always using the High security setting unless you have a specific and compelling need to allow one of the insecure capabilities. We recommend the Maximum security setting only for those environments where the most stringent security protocols must be adhered to. Enabling Maximum security is irreversible and has significant consequences (see The Consequences of Enabling Maximum Security Mode on page 55).
System Security Field Description Allow unencrypted connections to the Active Directory Normally, the Polycom RealPresence DMA system connects to Active Directory using SSL or TLS encryption. But if the Active Directory server or servers (including domain controllers if you import global groups) aren’t configured to support encryption, the Polycom RealPresence DMA system can only connect using an unencrypted protocol. This option allows such connections if an encrypted connection can’t be established.
System Security Field Description Skip certificate validation for server connecting Normally, when the Polycom RealPresence DMA system connects to a server, it validates that server’s certificate. This option configures the system to accept any certificate presented to it without validating it. We recommend using valid certificates for all servers that the system may need to contact rather than enabling this option.
System Security Field Description The following settings may be configured in any security mode. Skip certificate validation for user login sessions This option may be configured in any security mode. 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 mTLS for administrative connections).
System Security See also: System Security on page 39 Certificate Settings on page 43 Login Policy Settings on page 57 Reset System Passwords on page 61 The Consequences of Enabling Maximum Security Mode Enabling the Maximum security setting is irreversible and has the following significant consequences: ● All unencrypted protocols and unsecured access methods are disabled, and the enhanced support feature is disabled.
System Security ● If the system is integrated with Microsoft Active Directory, only one local user can have the Administrator role, and no local users can have the Provisioner or Auditor role. If there are multiple local administrators when you enable Maximum security, the system prompts you to choose one local user to retain the Administrator role. All other local users, if any, become conferencing users only and can’t log into the management interface.
System Security Enabling File Uploads in Maximum Security with Mozilla Firefox The Mozilla Firefox browser uses its own certificate database instead of the certificate database of the OS. If you use only that browser to access the Polycom RealPresence DMA system, the certificate(s) needed to securely connect to the system may be only in the Firefox certificate database and not in the Windows certificate store. This causes a problem for file uploads.
System Security Local Password The Local Password page lets you increase system security by specifying age, length, and complexity requirements for the passwords of local administrator, auditor, and provisioner users. These rules don’t apply to conferencing users’ conference and chairperson passcodes, or to Active Directory users. The following table describes the fields on the Local Password page.
System Security Field Description Active system sessions Specify the number of simultaneous login sessions by all users or select Unlimited. Note: If this limit is reached, but none of the logged-in users is an Administrator, the first Administrator user to arrive is granted access, and the system terminates the non-Administrator session that’s been idle the longest. Active sessions per user Specify the number of simultaneous login sessions per user ID or select Unlimited.
System Security Banner A login banner is a message that appears when users attempt to access the system. They must acknowledge the message before they can log in. The Banner page lets you enable the banner and select or create the message it displays. The message may contain up to 1500 characters. If the system is in Maximum Security mode, the login banner is enabled and can’t be disabled. The following table describes the fields on the Banner page.
System Security Field Description Accept management connections from these IP addresses and address ranges on ports 8443 (GUI/API) and 161 (SNMP) Enables the input field below and restricts management access to the IP addresses or address ranges added to the list. If this box is unchecked, the list and input field are disabled. The existing contents of the list, if any, remain unchanged so that it can be re-enabled at any time without having to re-enter the addresses.
System Security 5 Wait a few minutes to log back in. See also: System Security on page 39 Security Settings on page 50 The Consequences of Enabling Maximum Security Mode on page 55 Login Policy Settings on page 57 Access Policy Settings on page 60 Polycom, Inc.
Local Cluster Configuration This chapter describes the following Polycom® RealPresence® Distributed Media Application™ (DMA®) 7000 system configuration topics: ● Network Settings ● Time Settings ● Licenses ● Signaling Settings ● Alerting Settings ● Logging Settings ● Local Cluster Configuration Procedures ● Automatically Send Usage Data These are cluster-specific settings that are not part of the data store shared across superclustered systems.
Local Cluster Configuration Caution: Network Settings Changes Require a Restart Changing some network settings (host names, IP addresses, or domains) requires a system restart and terminates all active conferences. If the system is using a CA-provided identity certificate, changing some network settings (host names or IP addresses) also requires you to update the certificate. (If the system is using a self-signed certificate, an updated one is automatically created.
Local Cluster Configuration Field Description System split network setting Specifies whether to combine or split the system’s management and signaling interfaces. If the same network will be used for both management (administrative access) and signaling, the signaling IP addresses and Shared Signaling Network Settings section below are not used.
Local Cluster Configuration Field Description Shared Management Network Settings The settings in this section apply to the entire system (both servers in two-server configuration), whether management and signaling are combined or separate. Virtual host name Virtual host name and IP address(es) for the system’s management (or combined) network interface. For a one-server configuration, these fields are disabled.
Local Cluster Configuration Field Description Password Confirm password The password for the user name entered above. EAP Method The Extensible Authentication Protocol method used to establish trust with the authentication server (this is also known as the outer authentication protocol). Protocol When a TLS tunnel is established with the authentication server, the protocol used within the tunnel (this is also known as the inner authentication protocol).
Local Cluster Configuration Field Description Management DSCP The Differentiated Services Code Point value (0 - 63) to put in the DS field of IP packet headers on outbound packets associated with management traffic (including communications to other clusters. The DSCP value is used to classify packets for quality of service (QoS) purposes. If you’re not sure what value to use, leave the default of 0.
Local Cluster Configuration Field Description Host/Network The IP address of the destination network host or segment. Prefix length The CIDR (Classless Inter-Domain Routing) prefix size value (the number of leading 1 bits in the routing prefix mask). This value, together with the Host/Network address, defines the subnet for this route. For IPv4, a prefix length of 24 is equivalent to specifying a dotted-quad subnet mask of 255.255.255.0.
Local Cluster Configuration Field Description Manually set system time We don’t recommend setting time and date manually. NTP Servers Specify up to three time servers for maintaining system time (we recommend three). Enter IP addresses or fully qualified domain names. See also: Local Cluster Configuration on page 63 Local Cluster Configuration Procedures on page 81 Licenses The Polycom RealPresence DMA system is licensed for the number of concurrent calls it can handle and optionally for API access.
Local Cluster Configuration Field Description Date accepted The GMT date and time of EULA acceptance. Automatically send usage data Select to help improve this product by sending anonymous usage data to Polycom. See Automatically Send Usage Data on page 85 for more information. Licenses for the Virtual Edition The following table describes the fields on the Licenses page when using the Virtual Edition of the RealPresence DMA system.
Local Cluster Configuration Field Description Date accepted The GMT date and time of EULA acceptance. Automatically send usage data Select to help improve this product by sending anonymous usage data to Polycom. See Automatically Send Usage Data on page 85 for more information. See also: Local Cluster Configuration on page 63 Local Cluster Configuration Procedures on page 81 Signaling Settings On the Signaling Settings page, you can configure H.323 and SIP signaling.
Local Cluster Configuration ● Configure specific ports or prefixes for untrusted (“unauthorized” or “guest”) SIP calls that can only access specific resources (VMRs, VEQs, or a SIP peer). H.323 Device Authentication In an environment where H.235 authentication is used, H.323 devices include their credentials (name and password) in registration and signaling (RAS) requests.
Local Cluster Configuration You can route such untrusted (“unauthorized” or “guest”) calls by creating a separate set of “guest” dial rules used only for these untrusted calls. See Dial Rules on page 239. Depending on the SIP SBC and how it’s configured, such calls can be distinguished in one of two ways: ● By port: The SBC routes untrusted calls to a specific port. ● By prefix: The SBC adds a specific prefix in the Request-URI of the first INVITE message for the call.
Local Cluster Configuration Field Description Enable H.323 device authentication Check the box to turn on H.323 device authentication. Click Device authentication settings to go to the Device Authentication page and add authentication credentials (see Device Authentication on page 261). SIP Settings Enable SIP signaling Enables the system to receive Session Initiation Protocol (SIP) calls. Caution: Disabling SIP terminates any existing SIP calls.
Local Cluster Configuration Field Description Require certificate validation for TLS Check the box to enable mutual TLS (mTLS), requiring each caller to present a valid certificate. Unauthorized ports Lists the ports used by your SBC(s) for untrusted calls, showing the transport type for each and, for TLS, whether a certificate is required. The Authentication column indicates whether calls to that port are passed without challenge, challenged for authentication credentials, or blocked.
Local Cluster Configuration Field Description Require certificate validation for TLS For TLS transport, check this box to enable mutual TLS (mTLS), requiring callers to present a valid certificate. Note: If Skip certificate validation for encrypted signaling is turned off on the Security Settings page, then Require certificate validation for TLS is turned on for both authorized and unauthorized ports, and it can’t be turned off. See Security Settings on page 50.
Local Cluster Configuration Field Description Require certificate validation for TLS For TLS transport, check this box to enable mutual TLS (mTLS), requiring callers to present a valid certificate. Note: If Skip certificate validation for encrypted signaling is turned off on the Security Settings page, then Require certificate validation for TLS is turned on for both authorized and unauthorized ports, and it can’t be turned off. See Security Settings on page 50.
Local Cluster Configuration Field Description Strip prefix Check this box to have the system immediately strip this prefix from the INVITE message. Authentication Select one of the following: • None — The system doesn’t issue authentication challenges or check authentication credentials for calls with this prefix. • Authenticate — The system issues authentication challenges and checks authentication credentials for calls with this prefix.
Local Cluster Configuration See also: Signaling Settings on page 72 Local Cluster Configuration Procedures on page 81 Logging Settings The following table describes the fields on the Logging Settings page. Field Description Logging level Leave the default, Debug, unless advised to change it by Polycom support. Production reduces system overhead and log file sizes, but omits information that’s useful for troubleshooting. Verbose debug is not recommended for production systems.
Local Cluster Configuration Alerting Settings The Alerting Settings page allows you to configure thresholds for system alerts. Here, you can enable or disable certain alerts, and control when they will be triggered. Note: SNMP and System Alerts Configuration Since the triggering of SNMP alerts coincides with system alerts, configuration on this page applies to both system alerts and SNMP alerts. The Threshold Value column on the right of the page lists the configurable value for each alert’s threshold.
Local Cluster Configuration ● Configure Logging If you’re performing the initial configuration of your Polycom RealPresence DMA system, study Polycom® RealPresence DMA® System Initial Configuration Summary on page 29 before you continue. Other tasks are required that are described elsewhere. Add Licenses Adding licenses to your Polycom RealPresence DMA system is a two-step process: ● Request a software activation key code for each server. ● Enter the activation key codes into the system.
Local Cluster Configuration To enter license activation key codes 1 Go to Admin > Local Cluster > Licenses. 2 In the Activation key field for the first (or only) server, enter the activation key code that was generated for that server’s serial number. Caution: Activation Keys Linked to the Server Serial Number An activation key is linked to a specific server’s serial number. Each Activation Key field is labeled with a serial number.
Local Cluster Configuration Note: Understanding SIP Communications The system only answers UDP calls if that transport is enabled. But for communications back to the endpoint, it uses the transport protocol that the endpoint requested (provided that the transport is enabled, and for TCP, that unencrypted connections are permitted). For more information about this and other aspects of SIP, see RFC 3261.
Local Cluster Configuration Note: SIP URL Dialing Format From SIP endpoints, users generally must dial (if a prefix is being used): @ Depending on local DNS configuration, the host name could be the RealPresence DMA system’s FQDN or a shorter name that DNS can resolve. For example, if the RealPresence DMA system’s virtual host name is dma-virt, the E.
Local Cluster Configuration starting and ending calls and conferences, data is never sent between 5 minutes before the hour and 5 minutes after the hour.
Device Management This chapter 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 ● External H.
Device Management appears when you click Show Call Details (in the Actions list). See Call Details Dialog Box on page 88 for descriptions of the data. Note: Cluster vs. Supercluster Call Statistics If a call traverses multiple clusters in a supercluster, it’s counted as a single call, but it appears in the results of each cluster it touches when you search by cluster. Therefore, the sum of the number of calls for each cluster may be greater than the total number of calls for the entire supercluster.
Device Management Tab/Field/Column Description Call Info Call Info Displays the call’s: • 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: • Name and authentication name • Authentication status • Model and version • Aliases • IP address or host name • Registration st
Device Management Tab/Field/Column Description Bandwidth Available only after the call has ended. The table at the top lists each throttle point that the call traverses and shows its: • Bit rate limit per call (kbps) • Total capacity (kbps) • Used bit rate (kbps) in each class of service • Weight (%) • Territory If the throttle point is a subnet, site, or site link, a link takes you to the corresponding site topology page with the throttle point entity selected.
Device Management Tab/Field/Column Description Property Changes Lists each property change in the call, showing the value, time, and sequence number of the associated event. QoS Quality of service data is only available if one of the endpoints is a registered H.323 endpoint that supports IRQs. This tab displays a graph showing how QoS varied during the call. The horizontal scale and frequency of data points (dots on the lines of the graph) vary based on the length of the call.
Device Management The system matches any string you enter against the beginning of the values for which you entered it. If you enter “10.33.17” in the IP address field, it displays devices whose IP addresses are in that subnet. To search for a string not at the beginning of the field, you can use an asterisk (*) as a wildcard. Leave a field empty (or select the blank entry from a list) to match all values. Check Exceptions to find devices for which the registration policy script returned an exception.
Device Management Column Description Registration Status The registration status of the device: • Active — The device is registered and can make and receive calls. • Inactive — The device’s registration has expired. Whether it can make and receive calls depends on the system’s rogue call policy (see Call Server Settings on page 234) and. It can register again. • Quarantined — The device is registered, but it can’t make or receive calls.
Device Management Command Description Delete Removes the registration of the selected endpoint(s) with the Call Server and deletes the endpoint(s) from the Polycom RealPresence DMA system. A dialog box asks you to confirm. Unregistered endpoints are treated like rogue endpoints (see Call Server Settings on page 234). The device can register again. Associate User Opens the Associate User dialog box for the selected endpoint, where you can associate this device with a user.
Device Management ● If you know an endpoint has stopped supporting a protocol, manually delete its inactive registration for that protocol. 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.
Device Management See also: Device Management on page 87 Add Endpoint Dialog Box on page 96 Edit Device Dialog Box on page 97 Associate User Dialog Box on page 99 Active Calls on page 87 Add Endpoint Dialog Box The Add Endpoint dialog box lets you manually add a device to the system.
Device Management See also: Endpoints on page 91 Add Alias Dialog Box on page 99 Edit Alias Dialog Box on page 99 Edit Device Dialog Box The Edit Device dialog box lets you change a device’s class of service settings, add aliases, and edit or delete added aliases. You can’t edit or delete aliases with which the device registered. The following table describes the parts of the dialog box. Field Description Device type The device’s signaling protocol (H.323 or SIP). Signaling address For an H.
Device Management Field Description Forward if no answer 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. Forward if busy If the device is busy, forward calls to the specified alias. Registered endpoints can activate this feature by dialing the VSC for it (default is *74) followed by the alias.
Device Management See also: Endpoints on page 91 Edit Device Dialog Box on page 97 Add Alias Dialog Box The Add Alias dialog box lets you specify an alias for the H.323 device you’re adding or editing. Enter the alias in the Value box and click OK. See also: Endpoints on page 91 Add Endpoint Dialog Box on page 96 Edit Device Dialog Box on page 97 Edit Alias Dialog Box The Edit Alias dialog box lets you change the selected alias for the H.323 device you’re editing.
Device Management 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. The following table describes the fields in the list. Column Description Site Name Name of the site. Number of Calls Number of active calls. Bandwidth Used % Percentage of available bandwidth in use.
Device Management Column Description Avg Bit Rate (kbps) Average bit rate of the active calls. Note: Bit rate is not the same as bandwidth. Since the bit rate applies in both directions and there is overhead, the actual bandwidth consumed is about 2.5 times the bit rate. Packet Loss % Average packet loss percentage of the active calls. Avg Jitter (msec) Average jitter rate of the active calls. Avg Delay (msec) Average delay rate of the active calls. Territory Territory to which the site belongs.
Device Management Column Description Name The name of the neighbored gatekeeper. Description Brief description of the gatekeeper. Address Host name or IP address of the gatekeeper. Prefix Range The dial string prefix(es) assigned to this neighbor gatekeeper. If your dial plan uses the Dial services by prefix dial rule (in the default dial plan) to route calls to services, all dial strings beginning with an assigned prefix are forwarded to this gatekeeper for resolution.
Device Management Column Description 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. Enabled Clearing this check box lets you stop sending H.
Device Management Column Description RAS port The RAS (Registration, Admission and Status) channel port number. Leave set to 1719 unless you know the gatekeeper is using a non-standard port number. Prefix range The dial string prefix or prefix range for which the external gatekeeper is responsible. Enter a single prefix (44), a range of prefixes (44-47), multiple prefixes separated by commas (44,46), or a combination (41, 44-47, 49).
Device Management External SIP Peer On the External SIP Peer page, you can add or remove SIP servers or devices from the list of SIP peers to which the system can route calls and from which it may receive calls. 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.
Device Management Field Description External SIP Peer Enabled Clearing this check box lets you stop using an external SIP peer without deleting it. Name Peer name or number. Must be unique among SIP peers. Description The text description displayed in the External SIP Peer list. Type For a Microsoft Office Communications Server, Lync Server 2010, or Lync Server 2013, select Microsoft. Otherwise, select Other.
Device Management Field Description Downgrade If selected, and if this peer doesn’t support TLS, the system can change the Request-URI schema from sips to sip and route the call to this peer. If not selected, the system routes a TLS call to this peer only if this peer supports TLS. Prefix range The dial string prefix(es) assigned to this SIP peer.
Device Management Field Description Postliminary Use output format Enables dial string transformations using the To header and Request-URI option settings below instead of a customized script. Note: The system generates a script that implements the settings made in this section. To see (and perhaps copy) the generated script, you can temporarily select Use customized script.
Device Management Field Description Authentication Select one: • Handle authentication — When it receives a 401 (Unauthorized) response from this SIP peer, the Call Server presents its authentication credentials. • Pass authentication — When it receives a 401 response from this SIP peer, the Call Server passes it to the source of the request. Note: SIP authentication requests are never passed to an H.323 endpoint (a gateway call).
Device Management See also: External SIP Peer on page 105 SIP Peer Postliminary Output Format Options on page 114 Device Authentication on page 261 Add Authentication Dialog Box on page 117 Edit Authentication Dialog Box on page 118 Add Outbound Registration Dialog Box on page 118 Edit Outbound Registration Dialog Box on page 119 Script Debugging Dialog Box for Preliminaries/Postliminaries on page 254 Edit External SIP Peer Dialog Box The following table describes the fields in the Edit External SIP Peer
Device Management Field Description Port The SIP signaling port number. Defaults to the standard UDP/TCP port, 5060. If the peer server is using a different port number, specify it. Note: For a Microsoft Lync 2013 SIP peer, the port should be 5061. If left blank, the system uses the full RFC 3263 procedure to determine the port via DNS. Transport type The transport protocol to use when contacting this peer server. The default is UDP.
Device Management Field Description Domain List If your dial plan uses a rule to apply the Resolve to external SIP peer action, you can restrict calls to this peer server to specific domains by adding the authorized domains to this list. If this list is empty, all domains can resolve to this peer. Note: In some circumstances (depending on network topology and configuration), dialing loops can develop if you don't restrict peer servers to specific domains.
Device Management Field Description Authentication On this tab, you can configure SIP digest authentication, as specified in RFC 3261, for this SIP peer and add or edit authentication credentials. SIP authentication must be enabled and configured on the Device Authentication page. Note: The digest authentication settings for this peer are used only in conjunction with a dial rule specifying the Resolve to external SIP peer action.
Device Management Field Description Lync account URI Account ID the RealPresence DMA system should use when resolving Lync conference IDs. This field is enabled when Enable combined RealPresence-Lync scheduled conferences is checked. External Registration Lists any outbound registration configurations associated with this SIP peer and lets you add, edit, or delete registrations. Multiple registrations may be associated with a SIP peer.
Device Management <#pscheme#:#otuser#@#orhost#> No Display, use peer’s Destination Network or next hop address — Uses the Destination network value if specified, otherwise the peer’s Next hop address value. If a display parameter is present, it’s removed. Equivalent to template: <#pscheme#:#otuser#@#pnetORphost#> Default To header for Microsoft.
Device Management Original user, configured peer’s Destination Network or next hop address — Uses the user in the original, if specified, but replaces the host with the Destination network value, if specified, or the peer’s Next hop address value. Equivalent to template: #pscheme#:#otuser#@#pnetORphost# Default Request-URI for Microsoft. — Equivalent to template: sip:#phost#:#pport#;transport=#ptransport# Free Form Template — Format defined in associated Template field is used without further modification.
Device Management To Header and Request-URI Header Examples The tables below show some examples of To header and Request-URI header transformations using the variables described in Free Form Template Variables on page 116. Original To Header Template Result sip:user@host #orscheme#:atest sip:atest sip:user@host #orscheme#:#oruser#@#orhost# sip:user@host sip:host #orscheme#:#oruser#@foo.bar sip:foo.bar sip:user@host #orscheme#:#oruser#@foo.bar sip:user@foo.bar sip:host sips:#oruser#@foo.
Device Management authentication credentials that the system uses if challenged by an external device (see Device Authentication on page 261). The following table describes the fields in the dialog box. Field Description Realm Unique string that identifies the protection domain to which this set of credentials applies. Generally includes the host or domain name of the SIP peer. See RFC 2617 and RFC 3261. User name The user name to use for authentications in this realm.
Device Management The following table describes the fields in the Add Outbound Registration dialog box. Field Description Enabled Clearing this check box lets you stop using this registration without deleting the registration information. Address of record The AOR with which the system registers (see registration rules in RFC 3261), such as: sip:1000@dma.polycom.
Device Management Field Description Enabled Clearing this check box lets you stop using this registration without deleting the registration information. Address of record The AOR with which the system registers (see registration rules in RFC 3261), such as: sip:1000@dma.polycom.com Territory to perform registration Responsibility for registering must be assigned to a territory, thus making the primary or backup RealPresence DMA cluster for the territory responsible, depending on which is active.
Device Management Note: SBC Configuration Only H.323 SBCs are added to the External H.323 SBC page. SIP SBCs are configured as SIP peers (see External SIP Peer on page 105) and/or on a per-site basis (see Edit Site Dialog Box on page 285). H.323 SBCs that are added to the External H.323 SBC page are reached by prefix-based dialing (rule 4 of the default dial plan; see The Default Dial Plan and Suggestions for Modifications on page 241).
Device Management Add External H.323 SBC Dialog Box The following table describes the fields in the Add External H.323 SBC dialog box. Note: SBC Configuration Only H.323 SBCs are added to the External H.323 SBC page. SIP SBCs are configured as SIP peers (see External SIP Peer on page 105) and/or on a per-site basis (see Edit Site Dialog Box on page 285). H.323 SBCs that are added to the External H.
Device Management Edit External H.323 SBC Dialog Box The following table describes the fields in the Edit External H.323 SBC dialog box. Note: SBC Configuration Only H.323 SBCs are added to the External H.323 SBC page. SIP SBCs are configured as SIP peers (see External SIP Peer on page 105) and/or on a per-site basis (see Edit Site Dialog Box on page 285). H.323 SBCs that are added to the External H.
MCU Management This chapter describes the Polycom® RealPresence® Distributed Media Application™ (DMA®) 7000 system’s MCU management tools and tasks: ● MCUs ● MCU Pools ● MCU Pool Orders 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.
MCU Management Note: MCUs and ISDN Gateway Selection MCU pools and pool orders are not used to select an ISDN gateway for simplified gateway dialing. See ISDN Gateway Selection Process on page 139. When a Polycom RealPresence Collaboration Server or RMX MCU is functioning as an ISDN gateway, each call through the gateway consumes two ports, one for the ISDN side and one for the H.323 side.
MCU Management Note: Resource Usage Reporting 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. See your Polycom RealPresence Collaboration Server or RMX system documentation for more detailed information about resource usage.
MCU Management Column Description Connection and service status and capabilities: Connected Disconnected Connected securely (encrypted connection) In service Out of service Busied out Not licensed Supports conference recording Doesn’t support conference recording Supports shared number dialing IVR service Functions as a gateway Supports SVC conferences (see SVC Conferencing Support on page 17) Warning Supports cascaded conferences with Lync 2013 MCUs Hover over an icon to see the associated status m
MCU Management Column Description Registration Status The registration status of the device with the Call Server: • Active — The device is registered and can make and receive calls. • Inactive — The device’s registration has expired. Whether it can make and receive calls depends on the system’s rogue call policy (see Call Server Settings on page 234). It can register again. • Permanent — The device’s registration never expires.
MCU Management Command Description Start Using Enables the Polycom RealPresence DMA system to start using the selected MCUs as conferencing resources or ISDN gateways (for simplified gateway dialing). This command only affects Conference Manager and simplified gateway dialing functionality. It doesn’t affect MCUs that are simply registered with the Call Server. Stop Using Stops the Polycom RealPresence DMA system from using the selected MCUs as conferencing resources or ISDN gateways.
MCU Management 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 Port Reservation feature is not supported. This feature must be set to Disabled on Cisco Codian MCUs in order to use them as part of the Conference Manager’s conferencing resource pool.
MCU Management Field Description Admin user ID Administrative user ID with which the Polycom RealPresence DMA system can log into the MCU. For a maximum security environment, this must be a machine account created on the MCU. Note that the RMX and RealPresence Collaboration Server MCUs use case-sensitive machine names (and thus FQDNs) when creating machine accounts. Password Password for the administrative user ID.
MCU Management Field Description Signaling IP for SIP The address that the MCU uses for SIP signaling. If you specify the login information for the MCU, this field is optional (the system can get the address from the 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. Signaling type Select SIP, H.
MCU Management Field Description Gateway Profiles Copy from entry for ISDN gateway Lets you copy the delimiter and session profiles from another ISDN gateway instead of entering them below. This is especially useful for MGC devices because each ISDN network card must be registered separately, but all cards support the same gateway configuration. Dial string delimiter The dial string delimiter used to separate the session profile prefix from the ISDN E.164 number.
MCU Management 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 Port Reservation feature is not supported. This feature must be set to Disabled on Cisco Codian MCUs in order to use them as part of the Conference Manager’s conferencing resource pool.
MCU Management Field Description Admin user ID Administrative user ID with which the Polycom RealPresence DMA system can log into the MCU. For a maximum security environment, this must be a machine account created on the MCU. Note that the RMX and RealPresence Collaboration Server MCUs use case-sensitive machine names (and thus FQDNs) when creating machine accounts. Password Password for the administrative user ID.
MCU Management Field Description Signaling IP for H.323 The dialing prefix assigned to the MCU, if any. MCUs without a prefix are unavailable for direct prefix-based dialing. MCUs don’t need a prefix to be used as conferencing resources by the Conference Manager.
MCU Management Field Description Minimum downspeed bit rate (kbps) Select the minimum bit rate to which calls to this MCU can be downspeeded to manage bandwidth. If this minimum isn’t available, the call is dropped. The minimum that applies to a call is the higher of the MCU’s and the calling endpoint’s. Permanent Prevents the MCU’s registration with the Call Server from ever expiring. For MCUs, this option should always be selected (the default).
MCU Management See also: MCUs on page 124 MCU Procedures on page 139 Add Session Profile Dialog Box on page 138 Edit Session Profile Dialog Box on page 138 Add Session Profile Dialog Box Lets you add a session profile prefix to the ISDN gateway. The following table describes the fields in the dialog box. Field Description Session profile Numeric dial string prefix for this profile. Bit rate Bit rate of calls using this profile. H.320 H.323 PSTN SIP Select the protocol(s) for this profile. Only H.
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.
MCU Management 4 To set aside some of the MCU’s capacity for the Polycom CMA system’s use, set Video ports reserved for CMA system and Voice ports reserved for CMA system to the desired values (requires RMX v6.0 and above). The ports reserved for the Polycom CMA system can be used by that system for scheduled conferences. Note: MCUs and RealPresence Resource Manager Systems This feature is not for use with a Polycom RealPresence Resource Manager system.
MCU Management 8 Click OK. 9 If the MCU is configured as a conferencing resource, optionally change the MCU pool(s) to which it’s assigned. See MCU Pools on page 142. Pools and pool orders are used to determine which MCU is used for a conference. See MCU Pool Orders on page 145. To delete an MCU 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.
MCU Management See also: MCUs on page 124 Add MCU Dialog Box on page 129 Edit MCU Dialog Box on page 133 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. Note: MCU Pools vs.
MCU Management The following table describes the fields in the list. Column Description Name Name of the MCU pool. Description Description of the pool, such as the geographic location of the MCUs it contains. MCUs The MCUs that are in the pool. The Actions list associated with the MCU Pools list contains the items in the following table. Command Description Add Opens the Add MCU Pool dialog box, where you can define a new pool.
MCU Management Field Description Name Name of the MCU pool. Description 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.
MCU Management See also: MCU Pools on page 142 Add MCU Pool Dialog Box on page 143 Edit MCU Pool Dialog Box on page 143 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. Note: MCU Pools vs.
MCU Management Column Description MCU Pools The MCU pools that are in the pool order. Fallback Indicates whether this pool order is set to fall back to any available MCU if there are no available MCUs in its pools. The Actions list associated with the MCU Pool Orders list contains the items in the following table. Command Description Add Opens the Add MCU Pool Order dialog box, where you can define a new pool order.
MCU Management See also: MCU Pool Orders on page 145 MCU Pool Order Procedures on page 150 Edit MCU Pool Order Dialog Box Lets you edit an MCU pool order. The following table describes the fields in the dialog box. Field Description Name Name of the MCU pool order. Description Brief description of the pool order. Available MCU pools Lists the MCU pools available to the Polycom RealPresence DMA system. Selected MCU pools Lists the pools included in the pool order in their priority order.
MCU Management MCU has IVR service required by user’s conference template. MCU has recording capability required by user’s conference template. If there are multiple MCUs that are equally capable, select the least used, as determined by the following formula: port_availability = (free_video_ports / total_video_ports) + (0.0001 * free_audio_ports / total_audio_ports) mixer_availability = (total_video_ports - 2 * active_dma_conferences) / total_video_ports + 0.
MCU Management ● When calls to a specific MCU fail, the RealPresence DMA system reduces the MCU’s reliability score, causing it to be selected less frequently than other MCUs. An MCU’s reliability depends on the number of consecutive failed calls. As that number increases, the RealPresence DMA system treats a growing percentage of the MCU’s ports as if they were in use.
MCU Management Note: Calculating MCU Reliability After each call, the RealPresence DMA system recalculates the reliability of an MCU as the weighted average of the result for the current call (1 for success, 0 for failure) and the reliability of all previous calls, using this formula: reliability = (current_call + (weight * previous_reliability)) / (1 + weight) For example, if weight is 5, previous reliability is 1 (no previous failed calls), and the call is successful, the reliability remains 1: (1 + (5 *
MCU Management 3 In the Edit MCU Pool Order dialog box, edit the fields as required. See Edit MCU Pool Dialog Box on page 143. 4 Click OK. The changes you made appear in the MCU Pool Orders list. To delete an MCU Pool Order 1 Go to Network > MCU > MCU Pool Orders. 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.
Integrations with Other Systems This chapter describes the following Polycom® RealPresence® Distributed Media Application™ (DMA®) 7000 system configuration topics related to integrating the system with external systems: ● Microsoft Active Directory® Integration ● Microsoft Lync 2013 Integration ● Microsoft Exchange Server Integration ● Resource Management System Integration ● Juniper Networks SRC Integration Microsoft Active Directory® Integration When you integrate the Polycom RealPresence DMA system with
Integrations with Other Systems See also: Microsoft Active Directory Page on page 153 Active Directory Integration Procedure on page 157 Understanding Base DN on page 160 Adding Passcodes for Enterprise Users on page 162 About the System’s Directory Queries on page 163 Active Directory Integration Report on page 409 Conference Room Errors Report on page 412 Groups on page 325 Enterprise Groups Procedures on page 329 Microsoft Active Directory Page The following table describes the fields on the Microsoft
Integrations with Other Systems Field Description Conference room errors Number of enterprise users for whom conference rooms couldn’t be generated. If you’re an administrator, this label is a link to the Conference Room Errors Report report. Note: If you don’t specify an Active Directory attribute for conference room ID generation, the number of errors equals the number of users.
Integrations with Other Systems Field Description IP address or host name If this option is selected, the system attempts to connect to the Microsoft Active Directory domain controller specified. For a single-domain forest, enter the host name or IP address of a domain controller. For a multi-domain forest, we don’t recommend using this option. If you must, enter the host name or IP address of a specific global catalog server, not the DNS domain name.
Integrations with Other Systems Field Description Enterprise Conference Room ID Generation Directory attribute The name of the Active Directory attribute from which the Polycom RealPresence DMA system should derive conference room IDs (virtual meeting room numbers). Generally, organizations use a phone number field for this. The attribute must be in the Active Directory schema and preferably should be replicated across the enterprise via the Global Catalog server mechanism.
Integrations with Other Systems Field Description Conference directory attribute The name of the Active Directory attribute that contains the conference passcodes. In choosing an attribute, remember that passcodes must be numeric. The attribute must be in the Active Directory schema and preferably should be replicated across the enterprise via the Global Catalog server mechanism. But if the attribute isn’t in the Global Catalog, the system queries each domain controller for the data.
Integrations with Other Systems Note: Active Directory Integration Accounts If you have a Polycom RealPresence Resource Manager or CMA system, be aware that the machine account used for AD integration by the RealPresence Resource Manager or CMA system and the service account used for AD integration by the RealPresence DMA system have different requirements. Don’t try to use the same account for both purposes.
Integrations with Other Systems c Specify the number of characters to use. After the system strips out characters to remove, it removes characters in excess of this number from the beginning of the string. Note: Save Passcode Generation for Later Leave the Enterprise Chairperson and Conference Passcode Generation section alone for now. Once the system is integrated successfully, if you want to add passcode support, see Adding Passcodes for Enterprise Users on page 162. 6 Click Update.
Integrations with Other Systems 12 If, in step 9, there were many conference room errors, try to determine the reason and fix it: a Go to Reports > Conference Room Errors and verify that the time on the report is after the time when you last completed step 7. b Review the list of duplicate and invalid conference room IDs. Consider whether using a different Active Directory attribute, increasing the conference room ID length, or editing the characters to remove will resolve the majority of problems.
Integrations with Other Systems nwind.com (0) nwind.net (11) eng.nwind.com (1) west.eng.nwind.com (2) mkt.nwind.com (6) fin.nwind.com (9) [Org. unit: Planning (10)] west.mkt.nwind.com (7) east.eng.nwind.com (3) team1.east.eng.nwind.com (4) east.mkt.nwind.com (8) team2.east.eng.nwind.
Integrations with Other Systems Adding Passcodes for Enterprise Users Polycom RMX and RealPresence Collaboration Server MCUs provide two optional security features for conferences, which the Polycom RealPresence DMA system fully supports: ● Conference Passcode — A numeric passcode that callers must enter in order to join the conference. ● Chairperson Passcode — A numeric passcode that callers can enter to identify themselves as conference chairpersons.
Integrations with Other Systems b Specify the Active Directory attribute from which to generate conference passcodes and the number of characters to use. 5 Click Update. After a short time, the system confirms that Active Directory configuration has been updated. 6 Note the time. Click OK. 7 Confirm that passcode generation worked as expected. a Go to Reports > Enterprise Passcode Errors and verify that the time on the report is after the time when you last completed step 6.
Integrations with Other Systems User Search This search queries the global catalog. In a standard AD configuration, all the filter attributes and attributes returned are replicated to the global catalog. ● Base: 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 empty, as shown. Otherwise, the base variable is the same as Base DN. See Understanding Base DN on page 160.
Integrations with Other Systems ● Base: DC=dma,DC=eng,DC=local 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 DN on page 160.
Integrations with Other Systems Domain Search This search queries LDAP. The system runs this query only when it restarts (if already integrated with the Active Directory) and when you click the Update button on the Microsoft Active Directory page. ● Base: CN=Configuration,DC=dma,DC=eng,DC=local The base variable depends on the forest root DN (the distinguished name of the Active Directory forest root domain). See Active Directory Integration Report on page 409.
Integrations with Other Systems 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 presence and conference interaction between MCUs managed by the RealPresence DMA system and the Lync AVMCU.
Integrations with Other Systems When non-Lync endpoints dial the meeting ID in the meeting invitation, the incoming call is acted on by the Dial by Lync Conference ID dial rule. This dial rule causes the RealPresence DMA system to search any configured and selected SIP peers for a matching Lync conference. If the conference ID isn’t resolved on a Lync server, the system continues to resolve the conference ID using the next dial rule in the list.
Integrations with Other Systems Note: Point to point calls between Polycom endpoints and Lync 2013 clients When you register a Polycom endpoint to a RealPresence DMA system and make a point to point call to a Lync 2013 client, the conference may not have video because the H.261 and H.263 video codecs are not supported by the Lync 2013 client. As a workaround for Polycom HDX and RealPresence Group Series endpoints, register the endpoint to the Lync 2013 server before starting the conference.
Integrations with Other Systems Feature Client Server Uses SVC cascading between Microsoft AVMCU and Polycom MCU Meet Now calls to a VMR Lync 2013 Lync 2013 Yes Escalated conferences Lync client drag and drop multi-party call Lync 2013 Lync 2013 Yes Direct point-to-point Lync call to a VMR Lync 2010 Lync 2013 Lync 2010 Lync 2013 No DMA registered endpoint calling point to point to a Lync client Lync 2010 Lync 2013 Lync 2010 Lync 2013 No If a Lync 2013 client, all calls will be audio onl
Integrations with Other Systems ● Unique name for the Lync Trusted Application (used when adding the RealPresence DMA system to the Lync topology) The following procedures assume that you have gathered the required information and completed the preliminary setup tasks.
Integrations with Other Systems 5 Enter a Next hop address. This value refers to the FQDN or IP address of the Lync pool, not an individual server within a pool. 6 Enter the domain of the Lync pool in the Destination network field. 7 Enter a Port number of 5061. 8 Enter a Transport type of TLS. 9 Enter a prefix or multiple prefixes in the Prefix range field (for example, 99) and enable the Strip prefix check box. See the Add External SIP Peer Dialog Box on page 105 for more information.
Integrations with Other Systems 6 (Optional) Use the drop-down list to select a conference template to use for calls routed by this dial rule. Keep in mind that the conference template must specify a Conference mode of AVC only, or the conference will not start. See page 169. 7 Select a SIP peer from the Available SIP peers selection area. 8 Use the right arrow button to move the SIP peer to the Selected SIP peers area.
Integrations with Other Systems a (Optional) Modify the VMR display name pattern if necessary. This text will be precede the VMR number of the conference contact in the Lync contact window. b (Optional) Populate the OU for contacts field. If left blank, the system creates resources in the CN=Users container. 6 Modify the Default Polycom conference contacts presence settings field to suit your environment.
Integrations with Other Systems Microsoft Exchange Server Integration On the Microsoft Exchange Server page, you can integrate the Polycom RealPresence DMA system with your Microsoft Exchange Server, enabling users who install the Polycom Conferencing Add-in for Microsoft Outlook to set up Polycom Conferencing meetings in Outlook. When you integrate the RealPresence DMA system with an Exchange server, it connects to the Exchange server as the Polycom Conferencing user and subscribes to notifications.
Integrations with Other Systems ● The meeting’s duration exceeds the system’s Conference Duration setting (see Conference Settings on page 185). ● The conference or chairperson passcode is not valid (see Adding Passcodes for Enterprise Users on page 162). Note: Considerations for Calendaring and Scheduling Calendaring is not the same as scheduling.
Integrations with Other Systems Exchange Server Integration Procedure To integrate the Polycom RealPresence DMA system with your Exchange server Note: Tips for Exchange Integration Unless the Allow unencrypted calendar notifications from Exchange server security option is enabled (see Security Settings on page 50), the Polycom RealPresence DMA system offers the same SSL server certificate that it offers to browsers connecting to the system management interface.
Integrations with Other Systems 10 Click OK. 11 Install the Polycom Conferencing Add-in for Microsoft Outlook on your PC and create the configuration to be distributed to your users (see the online help for the Add-in). Optionally, customize the invitation template(s). 12 Distribute the Polycom Conferencing Add-in for Microsoft Outlook, its configuration file, and customized templates to your users (see the System Administrator Guide for the Polycom® Conferencing Add-in for Microsoft® Outlook®).
Integrations with Other Systems Note: Considerations for RealPresence Resource Manager Integration A RealPresence Resource Manager system (but not a CMA system) can also be integrated to (connected to) the RealPresence DMA system. This enables it to use the RealPresence DMA system’s RealPresence Platform API to set up and monitor scheduled and preset dial-out (anytime) conferences using the RealPresence DMA system’s resources (see RealPresence® Platform API on page 16).
Integrations with Other Systems See also: Integrations with Other Systems on page 152 Resource Management System Page on page 180 Join Resource Management System Dialog Box on page 181 Resource Management System Integration Procedures on page 181 Resource Management System Page The Resource Management System page contains the Join Resource Management System command, which you use to integrate to your Polycom RealPresence Resource Manager or CMA system.
Integrations with Other Systems Join Resource Management System Dialog Box Lets you integrate the Polycom RealPresence DMA system with a Polycom RealPresence Resource Manager or CMA system to obtain site topology information and user-to-device association information. Note: Maximum Security Mode and Resource Management Integration RealPresence Resource Manager or CMA integration is not supported in Maximum security mode. See The Consequences of Enabling Maximum Security Mode on page 55.
Integrations with Other Systems Note: Add Required DNS Servers to the System DNS servers must be able to resolve the RealPresence DMA system’s FQDN to its IP address. See Add Required DNS Records for the Polycom RealPresence DMA System on page 30. In addition, the DNS servers must be able to resolve the Polycom RealPresence Resource Manager or CMA system’s FQDN to its IP address. This is necessary even if you specify the Polycom RealPresence Resource Manager or CMA system’s IP address when you join it.
Integrations with Other Systems 3 When asked to confirm that you want to leave, click Yes. The system connects to the Polycom RealPresence Resource Manager or CMA system and terminates the integration. A dialog box informs you when the process is complete. 4 On the Resource Management System page, verify that the system is no longer integrated with the Polycom RealPresence Resource Manager or CMA system.
Integrations with Other Systems Field Description Client password The password with which the Polycom RealPresence DMA system logs into the SRC server. Subscriber URI The subscriber URI of an endpoint known to the SRC server, specified as in this example: ip:ipAddress=192.168.70.228 This can be any endpoint for which the SRC server will return information when queried to test the connection.
Conference Manager Configuration This chapter describes the following Polycom® RealPresence® Distributed Media Application™ (DMA®) 7000 system configuration topics related to the Conference Manager functionality: ● Conference Settings ● Conference Templates ● IVR Prompt Sets ● Shared Number Dialing Conference Settings 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
Conference Manager Configuration Field Description Dialing prefix Numeric dial string prefix for calling VMRs and VEQs. If neighboring with a Polycom gatekeeper on which the Simplified Dialing service is enabled and uses a prefix of 9 (the default), don’t use 90-99. The neighbor gatekeeper recognizes the 9 as a known prefix and ignores the second digit. If a prefix is specified, it’s used for SIP calls as well so that the same number can be dialed from both H.323 and SIP endpoints.
Conference Manager Configuration Field Description Default resource priority value If your organization has implemented a resource prioritization mechanism, set this to the default priority value assigned to a conference if the specific conference room (VMR) doesn’t have a higher value. If using a custom namespace, enter the value in the box to the right of the list. The string namespace:value is used in the SIP Resource-Priority header of outbound calls from conference rooms (VMRs).
Conference Manager Configuration Field Description VMR display name pattern The text pattern that describes the name of the VMR contact. This text will precede the VMR number when displayed in the Lync contact window (for example, a VMR display name pattern of “Conference room” would create display names of “Conference room ”). The maximum pattern length is 63 characters.
Conference Manager Configuration 2 On the Conference Settings page, make the appropriate selections. 3 Click Update. See also: Conference Templates on page 190 IVR Prompt Sets on page 218 Shared Number Dialing on page 220 Remove Contacts from Active Directory Dialog Box 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.
Conference Manager Configuration See also: Conference Settings on page 185 Microsoft Lync 2013 Integration on page 167 Conference Templates Conference templates are used to create users’ conference rooms, which define a user’s conference experience. A conference template specifies a set of conference properties, such as the line (bit) rate and video display mode.
Conference Manager Configuration standalone templates. When you link a template with an MCU profile, the MCU’s profile settings take priority over values set in the RealPresence DMA system template. Note: MCU Pools vs. Profiles You can also use a template linked to a RealPresence Collaboration Server or RMX profile to preferentially route conferences to MCUs that have the profile. But we recommend that you create MCU pools and pool orders for this purpose instead of using profiles.
Conference Manager Configuration An enterprise user can be associated with multiple enterprise groups, and each group may or may not have a specifically assigned template. You can rank the conference templates by priority, so that the system knows which template to use when the user is associated with more than one.
Conference Manager Configuration Note: Bypass IVR Service Passcode Prompt Callers to conferences with passcodes (PINs) can bypass the IVR service’s passcode prompting by appending their passcode to the dial string, following the protocol-appropriate delimiter: • H.
Conference Manager Configuration Note: Cascading for Bandwidth Topology Cascading for bandwidth uses a hub-and-spoke configuration; each cascaded MCU is only one link away from the “hub” MCU that hosts the conference. To host the conference, the system chooses the same MCU that it would have chosen in the absence of cascading. See MCU Selection Process on page 147.
Conference Manager Configuration Note Cascading for Size vs. Cascading for Bandwidth Cascading for size differs from cascading for bandwidth in two primary ways: • Cascading for size doesn’t use site topology information to choose additional MCUs to use for a conference. • Cascading for size supports a second level of cascade links so that a cascaded MCU can be either one link away from the “hub” MCU hosting the conference (this is a “spoke” MCU) or two links away (a “leaf” MCU linked to a “spoke”).
Conference Manager Configuration Column Description Priority The priority ranking of the template. Name 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.
Conference Manager Configuration Field Description Conference Settings Conference mode One of the following: • AVC only — Standard video conferencing mode supporting the H.264 Advanced Video Coding (AVC) compression standard. In an AVC conference, the MCU transcodes the video stream to each device in the conference to provide an optimal experience, based on its capabilities.
Conference Manager Configuration Field Description Cascade for size Enables conferences using this template to span Polycom MCUs to achieve conference sizes larger than a single MCU can accommodate. This option and Cascade for bandwidth are mutually exclusive. See About Cascading on page 193 for more information about enabling cascading of conferences. Video switching (VSW) Enables a special conferencing mode that provides HD video while using MCU resources more efficiently.
Conference Manager Configuration Field Description Line rate 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). Audio only Sets the conference to be audio only. This limits line rate to a maximum of 128 kbps and disables numerous video settings.
Conference Manager Configuration Field Description MS AVMCU cascade mode When integrated with a Lync 2013 environment, controls behavior of the cascade link with the Lync 2013 AVMCU. • Resource Optimized — The cascade link between the RealPresence DMA system and the Lync 2013 server’s AVMCU will be capable of HD video resolutions, which will increase MCU resource usage.
Conference Manager Configuration Field Description RMX Video Quality People Video Definition Video quality Offers two video optimizations: • Motion — higher frame rate • Sharpness — higher resolution Not available if Conference mode is set to SVC only. Max resolution (v7) Enables you to choose a resolution setting that limits the conference to no more than that resolution regardless of the line rate and resolution capabilities of the MCU and endpoints. Auto (the default) imposes no limit.
Conference Manager Configuration Field Description Content protocol Content channel protocol options: • Use H.263. • Use H.264 if available, otherwise use H.263. • Use H.264 cascade and SVC optimized. • Use H.264 HD. Content resolution Specifies the resolution of the content channel for the conference and cascade link. Available only when Content protocol is set to H.264 cascade and SVC optimized. H.264 high profile Enables the H.
Conference Manager Configuration Field Description Telepresence mode (v6) Support for telepresence conference rooms joining the conference: • Auto (default) — A conference is automatically put into telepresence mode when a telepresence endpoint (RPX, TPX, ATX, or OTX) joins. • On— Telepresence mode is on, regardless of whether a telepresence endpoint is present. • Off— Telepresence mode is off, regardless of whether a telepresence endpoint is present. We recommend always using Auto.
Conference Manager Configuration Field Description RMX Conference IVR Override default conference IVR service Links this template to the specific conference IVR service selected in the list 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 on page 220). For most purposes, this option should not be selected.
Conference Manager Configuration Field Description Audio only Limits recording to the audio channel of the conference. Indication of recording Displays a red dot recording indicator in the upper left corner of the video layout. Available only on v7.1 and newer Polycom MCUs. Cisco Codian Floor and chair control Specifies how much control conference participants may have: • Do not allow floor or chair control — Participants have no control.
Conference Manager Configuration Field Description Conference custom layout Enables the Conference layout desired setting, where you can select the number and arrangement of video frames by clicking the image. Conference layout desired With Conference custom layout enabled, allows you to select the number and arrangement of video frames by clicking the image. Once a layout is chosen, a small representation of it appears here. See Select Layout Dialog Box on page 216.
Conference Manager Configuration Field Description Conference Settings Conference mode One of the following: • AVC only — Standard video conferencing mode supporting the H.264 Advanced Video Coding (AVC) compression standard. In an AVC conference, the MCU transcodes the video stream to each device in the conference to provide an optimal experience, based on its capabilities.
Conference Manager Configuration Field Description Cascade for size Enables conferences using this template to span Polycom MCUs to achieve conference sizes larger than a single MCU can accommodate. This option and Cascade for bandwidth are mutually exclusive. See About Cascading on page 193 for more information about enabling cascading of conferences. Video switching (VSW) Enables a special conferencing mode that provides HD video while using MCU resources more efficiently.
Conference Manager Configuration Field Description Line rate 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). Audio only Sets the conference to be audio only. This limits line rate to a maximum of 128 kbps and disables numerous video settings.
Conference Manager Configuration Field Description MS AVMCU cascade mode When integrated with a Lync 2013 environment, controls behavior of the cascade link with the Lync 2013 AVMCU. • Resource Optimized — The cascade link between the RealPresence DMA system and the Lync 2013 server’s AVMCU will be capable of HD video resolutions, which will increase MCU resource usage.
Conference Manager Configuration Field Description RMX Video Quality People Video Definition Video quality Offers two video optimizations: • Motion — higher frame rate • Sharpness — higher resolution Not available if Conference mode is set to SVC only. Max resolution (v7) Enables you to choose a resolution setting that limits the conference to no more than that resolution regardless of the line rate and resolution capabilities of the MCU and endpoints. Auto (the default) imposes no limit.
Conference Manager Configuration Field Description Content protocol Content channel protocol options: • Use H.263. • Use H.264 if available, otherwise use H.263. • Use H.264 cascade and SVC optimized. • Use H.264 HD. Content resolution Specifies the resolution of the content channel for the conference and cascade link. Available only when Content protocol is set to H.264 cascade and SVC optimized. H.264 high profile Enables the H.
Conference Manager Configuration Field Description Telepresence mode (v6) Support for telepresence conference rooms joining the conference: • Auto (default) — A conference is automatically put into telepresence mode when a telepresence endpoint (RPX, TPX, ATX, or OTX) joins. • On— Telepresence mode is on, regardless of whether a telepresence endpoint is present. • Off— Telepresence mode is off, regardless of whether a telepresence endpoint is present. We recommend always using Auto.
Conference Manager Configuration Field Description RMX Conference IVR Override default conference IVR service Links this template to the specific conference IVR service selected in the list 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 on page 220). For most purposes, this option should not be selected.
Conference Manager Configuration Field Description Audio only Limits recording to the audio channel of the conference. Indication of recording Displays a red dot recording indicator in the upper left corner of the video layout. Available only on v7.1 and newer Polycom MCUs. Cisco Codian Floor and chair control Specifies how much control conference participants may have: • Do not allow floor or chair control — Participants have no control.
Conference Manager Configuration Field Description Conference custom layout Enables the Conference layout desired setting, where you can select the number and arrangement of video frames by clicking the image. Conference layout desired With Conference custom layout enabled, allows you to select the number and arrangement of video frames by clicking the image. Once a layout is chosen, a small representation of it appears here. See Select Layout Dialog Box on page 216.
Conference Manager Configuration To add a conference template linked to a RealPresence Collaboration Server or RMX profile 1 Go to Admin > Conference Manager > Conference Templates. 2 In the Actions list, click Add. 3 In the Add Conference Template dialog box, specify all the conference properties for this template: a In Common Settings, enter an appropriate name and description. b Click the RMX General Settings tab. c Check Use existing profile and select the one you want from the RMX profile name list.
Conference Manager Configuration See also: Conference Templates on page 190 Add Conference Template Dialog Box on page 196 Edit Conference Template Dialog Box on page 206 IVR Prompt Sets A prompt set contains a set of media files (audio prompts and video slides) that provide the caller experience for a RealPresence DMA-controlled IVR service. The RealPresence DMA system comes with a factory default call flow and corresponding prompt set.
Conference Manager Configuration Prompt File Name Prompt Text Chairperson_Identifier.wav For conference chairperson services, enter the chairperson password. All other participants, please wait. Chairperson_PIN_Invalid.wav Invalid chairperson password. Chairperson_PIN_Invalid_Retry.wav Invalid chairperson password. Please try again. Conference_Full.wav The conference is full. You cannot join at this time. Conference_Locked.wav The conference is locked. You cannot join at this time.
Conference Manager Configuration Field Description Prompt Set Details Displays the following information about the selected prompt set: • Prompt set and archive names. • Application name (currently always dma7000). • Archive checksum (to verify validity) • Number of media files (.wav and .jpg) in the prompt set. Included Media Status Lists the media files in the prompt set, the IVR call flow, or both. The icon to the left shows the status of each. Hover over a file to see an explanation of the status.
Conference Manager Configuration 2 The Polycom RealPresence DMA system recognizes the dialed number as a VEQ number and routes the call to a Polycom RealPresence Collaboration Server or RMX MCU configured to provide the IVR experience (MCU-controlled or RealPresence DMA-controlled) that’s associated with the VEQ number dialed.
Conference Manager Configuration You can create up to 60 different VEQs to provide different IVR experiences (for instance, different language prompts or different greetings). You can designate one of the MCU-controlled VEQs as the Direct Dial VEQ, and the system will use it for calls dialed without a VEQ or VMR number. For instance, if a call’s dial string includes only the system’s domain name or IP address, the Polycom RealPresence DMA system uses the Direct Dial VEQ for it.
Conference Manager Configuration See also: Add Direct Dial Virtual Entry Queue Dialog Box on page 224 Edit Virtual Entry Queue Dialog Box on page 224 Edit Direct Dial Virtual Entry Queue Dialog Box on page 225 Conference Templates on page 190 Conference Settings on page 185 IVR Prompt Sets on page 218 Add Virtual Entry Queue Dialog Box Lets you add a virtual entry queue (VEQ) to the list of configured VEQs on the Shared Number Dialing page. The table below describes the fields in the dialog box.
Conference Manager Configuration Field Description Request operator transfer DTMF The DTMF command for requesting an operator. Note: If this digit string matches a VMR number, that VMR becomes unreachable. Timeout to cancel operator request (sec) The length of time after requesting an operator that a caller is given to cancel that request (1-10 seconds). Note: An operator request can be canceled by entering any DTMF key.
Conference Manager Configuration Field Description 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. Note: Polycom MCUs refer to entry queues designed for a RealPresence DMA-controlled VEQ as “External IVR” because RealPresence DMA-based IVR control is external to the MCU.
Superclustering This chapter describes the Polycom® RealPresence® Distributed Media Application™ (DMA®) 7000 system’s superclustering capability. It includes the following topics: ● About Superclustering ● RealPresence DMAs ● Join Supercluster Dialog Box ● Supercluster Procedures About Superclustering The two-server configuration of the Polycom RealPresence DMA system is configured as a co-located two-server cluster, which enhances the reliability of the system by providing a measure of redundancy.
Superclustering Create four territories, assign a primary cluster for each, and assign the fifth cluster as backup for all four. Create five territories, assign a primary cluster for each, and make each cluster the backup for one of the other territories. Use some hybrid of the above that best suits your enterprise network’s distribution of sites, users, and traffic. Keep in mind that only three territories can host conference rooms.
Superclustering ● Add the system to an existing supercluster by pointing it to one of the existing clusters in the supercluster. The system you’re logged into becomes one of the clusters in that supercluster, and its local data store is largely replaced by a copy of the shared supercluster data store.
Superclustering The Start Using command puts the selected cluster back into service: ● New calls and conferences are allowed to start. The cluster begins bandwidth management. ● The cluster assumes control of any territories for which it has primary responsibility, or for which it has backup responsibility and the primary cluster is offline.
Superclustering See also: About Superclustering on page 226 Supercluster Procedures on page 230 Join Supercluster Dialog Box 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 box, where you can specify any cluster in the supercluster to join.
Superclustering 2 In the Actions list, click Join Supercluster. Note: Allow Supercluster Join Operations to Complete You can only add one cluster to a supercluster at a time. Wait until the current join operation is completely finished before attempting to add another cluster to the supercluster. The join operation may take several minutes, and the time required increases as the number of clusters in the supercluster increases.
Superclustering To remove a cluster from the supercluster Note: Remove a Cluster Only While its Servers are Operational If possible, remove a cluster only while its server or servers are on line. If you must remove a cluster while one or both servers are off line, be aware that an offline server may be in an inconsistent state when it’s brought back on line. If this occurs, the system attempts to auto-correct the situation.
Call Server Configuration This chapter describes the Polycom® RealPresence® Distributed Media Application™ (DMA®) 7000 system’s configuration tools and tasks related to its Call Server: ● About the Call Server Capabilities ● Call Server Settings ● Domains ● Dial Rules ● Hunt Groups ● Device Authentication ● Registration Policy ● Prefix Service ● Embedded DNS ● History Retention Settings These are settings and features that are shared across superclustered systems.
Call Server Configuration Note: IPV4 Addresses Preferred for Signaling Communication In an IPv4 + IPv6 environment, the Polycom RealPresence DMA system gatekeeper prefers the IPv4 address for devices that register with both.
Call Server Configuration Field Description Available bandwidth limit (percent) Sets the maximum percentage of the available bandwidth that can be allocated to a single call. If the requested bandwidth exceeds this value, the Call Server “downspeeds” (reduces the bit rate of) the call, but only to the user’s downspeed minimum. If there is insufficient bandwidth to comply with both this setting and the downspeed minimum, the call is rejected.
Call Server Configuration Field Description SIP max breadth The maximum number of concurrent parallel branches due to forking of a request. H.323 Settings Gatekeeper call mode Direct call mode — The Call Server processes only H.225.0 RAS call control messages. The endpoints exchange other call signaling and media control messages directly, bypassing the gatekeeper. Routed call mode — The Call Server proxies all H.323 signaling messages. Accept H.
Call Server Configuration Field Description Dynamically blacklist signaling from hyperactive endpoints If this option is selected, the Call Server adds H.323 endpoints to its blacklist (ignoring their signaling messages) when they send duplicate RRQ or GRQ messages in excess of the criteria you specify below. When an endpoint is blacklisted, the Call Server: • Stops interpreting, responding to, auditing, or logging messages of that type from the endpoint.
Call Server Configuration Calls that have a non-local domain in the dialed string do not resolve to any locally registered endpoints, and can only resolve to a VEQ or VMR if the Conference rooms belong to every domain check box is checked. Note: Resolve to External Address Dial Rule and Local Domains The Resolve to external address dial rule action (see Add Dial Rule Dialog Box on page 244) doesn’t match against domains that are considered local.
Call Server Configuration Field Description Email IDs of registered H.323 endpoints belong to every local domain Specifies that call requests for locally registered H.323 endpoints’ email IDs don’t have to match the domain. For example, if there is an endpoint registered as ‘h323:johnsmith@1.1.1.1’ and this option is enabled, a call to 'h323:johnsmith@mycompany.com’ may be connected to that endpoint. If this option is not selected, call requests must exactly match the URI of the registered endpoint.
Call Server Configuration For instance, the Resolve to registered endpoint action applies all the associated system configurations and performs various searches on the internal endpoint registration records to determine if the inbound call is attempting to reach another registered endpoint. It automatically adjusts for signaling protocol (SIP/H.323), case, and standard dial string deviations to locate a registered endpoint.
Call Server Configuration Field Description Caller site Select a site in order to set the four caller site variables: • CALLER_SITE_NAME • CALLER_SITE_DIGITS • CALLER_SITE_COUNTRY_CODE • CALLER_SITE_AREA_CODE These variables can’t be set directly and are display only. CALLER_H323ID Test caller’s H323-ID or blank. CALLER_E164 Test caller’s H.323 E.164 alias or blank. CALLER_TEL_URI Test caller’s SIP tel URI or blank. CALLER_SIP_URI Test caller’s SIP sip URI or blank.
Call Server Configuration Rule Effect 1 Dial registered endpoints by alias If the dial string is the alias or SIP URI of a registered endpoint, the call is routed to that endpoint. 2 Dial by conference room ID Otherwise, if the dial string is the dial-in number of a conference room on the Polycom RealPresence DMA system, the call is routed to that conference room.
Call Server Configuration ● To add an MCU, ISDN gateway, SBC, neighbor gatekeeper, SIP peer, or simplified dialing service that can be dialed by prefix, configure the prefix range of the new service on the appropriate page. No dial plan change is necessary, since Rule Dial services by prefix of the default dial plan takes care of dialing by prefix. ● You can remove or disable a default dial rule if you don't want the associated functionality.
Call Server Configuration ● If your enterprise includes a SIP peer and you want to route calls to that peer without a prefix, add a dial rule using the Resolve to external SIP peer action. If you have multiple SIP peers, a call matching the rule is routed to the first one to answer. You may want to specify the domain(s) for which each is responsible (see Add External SIP Peer Dialog Box on page 105).
Call Server Configuration Field Description Preliminary A preliminary is an executable script, written in the Javascript language, that defines processing actions (filtering or transformation) that are part of a dial rule and may be applied to a dial string before the dial rule’s action is performed. Sample Preliminary and Postliminary Scripts on page 255 provides some examples you can experiment with and modify for your purposes. Enabled Lets you turn a preliminary on or off without deleting it.
Call Server Configuration For this action: The system attempts to resolve the address as follows: Resolve to Lync conference ID Resolves to a Lync conference that resides on a selected SIP peer. When selected, the following fields are available: • Conference template When checked, you can select the conference template used to start the conference. If left unchecked, or if checked and unchanged, the Default conference template configured in Admin > Conference Manager > Conference Settings will be used.
Call Server Configuration For this action: The system attempts to resolve the address as follows: Resolve to external address Determines if the dial string is a well-formed instance of an external address type to which the rule applies, and if so, uses the resolution procedures specified in the applicable standard for that address type. After selecting this action for a rule, select the address type or types to which the rule applies.
Call Server Configuration Edit Dial Rule Dialog Box The following table describes the fields in the Edit Dial Rule dialog box. Field Description Dial Rule Description The text description displayed on the Dial Rules page. Action The action to be performed. When you select some actions, additional settings become available. See the table of dial rule actions below for more information about the actions and the additional settings associated with them.
Call Server Configuration For this action: The system attempts to resolve the address as follows: Block Blocks the call. Resolve to IP address Tries to treat the dial string as an IP address, and if it can, assumes it’s the address (and port, if included) of an unregistered endpoint. If no port is specified, it uses the default port of the signaling protocol. If the dial string contains the characters “##,” it tries to do this using the characters before “##.
Call Server Configuration For this action: The system attempts to resolve the address as follows: Resolve to Lync conference ID Resolves to a Lync conference that resides on a selected SIP peer. When selected, the following fields are available: • Conference template When checked, you can select the conference template used to start the conference. If left unchecked, or if checked and unchanged, the Default conference template configured in Admin > Conference Manager > Conference Settings will be used.
Call Server Configuration For this action: The system attempts to resolve the address as follows: Resolve to external address Determines if the dial string is a well-formed instance of an external address type to which the rule applies, and if so, uses the resolution procedures specified in the applicable standard for that address type. After selecting this action for a rule, select the address type or types to which the rule applies.
Call Server Configuration Variable Initial value CALLER_SIP_URI Array variable initially set to the set of SIP URI addresses of the caller. The length of the array is 0 if the caller doesn’t have a SIP URI address. CALLER_SITE_AREA _CODE Area code of the caller’s site. Blank if the site doesn’t have an area code. CALLER_SITE_COUNTRY_COD E Country code of the caller’s site. Blank if the site doesn’t have a country code.
Call Server Configuration Variable Initial value INPUT_SIP_HEADERS For SIP calls only, an associative array containing the SIP headers in the received SIP INVITE message. Usage example: if(INPUT_SIP_HEADERS["Supported"].matches(/.*ms-forking. */)) { ... } OUTPUT_SIP_HEADERS An empty associative array. Headers that the script adds to this array replace the corresponding headers in the received SIP INVITE message.
Call Server Configuration Dial Rule Action Output SIP Headers Resolve to service prefix For a SIP peer proxy of type OCS: The To header is replaced with the modified dial string. The request URI is based on the address, port, and transport type of the proxy, and not replaced with the modified dial string. For a SIP peer proxy of type Other: The To header and the request URI are both replaced with the modified dial string.
Call Server Configuration Field Description Caller variables Lists variables that can be used in the script to represent caller alias values. Enter an alias value to test for that variable. Final result Displays the outcome of running the script. For a dial rule preliminary, if the script rejected the dial string (skipping the dial rule action and passing it on to the next dial rule), a message tells you so. Otherwise, the transformed dial string is displayed.
Call Server Configuration /////////////////////////////// // 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) // If the dial string is a SIP URI, add prefix 99 to the user part // SIP:1234@abc.com --> sip:991234@abc.com DIAL_STRING = DIAL_STRING.
Call Server Configuration return NEXT_RULE; } /////////////////////////////// // PRINTLN // Print out the information available to the script for this call. // Information printed using the print or println functions // is saved as a call audit event, which is viewable in the // DMA interface under Reports > Call History, and also in the // Script Debugging dialog box.
Call Server Configuration /////////////////////////////// // 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. // Assumes that all endpoints are registered with their full alias, including // country and area code. // sip:5551212@example.com --> sip:14045551212@example.com if (DIAL_STRING.toLowerCase().match(/^sip:[^@]*@example\.com/)) { user = DIAL_STRING.replace(/^sip:([^@]*)@.
Call Server Configuration The system selects hunt group members in round-robin fashion. It skips members that are in a call or have unconditional call forwarding enabled. If the selected group member rejects the call or doesn’t answer before the timeout, the system tries the next group member. If all members have been attempted (or skipped) without successfully terminating the call, the system sends the BUSY message to the caller.
Call Server Configuration Field Description Available endpoints Lists the endpoints that match the search criteria. Member endpoints Lists the endpoints to include in the hunt group. Use the arrow buttons to move endpoints from one list to the other. See also: Hunt Groups on page 258 Add Alias Dialog Box on page 260 Edit Alias Dialog Box on page 261 Edit Hunt Group Dialog Box The Edit Hunt Group dialog box lets you modify the selected hunt group and add or remove members.
Call Server Configuration See also: Hunt Groups on page 258 Add Hunt Group Dialog Box on page 259 Edit Hunt Group Dialog Box on page 260 Edit Alias Dialog Box The Edit Alias dialog box lets you change an alias value assigned to the hunt group. Edit the alias in the Value box and click OK. Aliases should be specified by their fully qualified dial string. For example, to specify that H.323 callers can call the hunt group by dialing 1234, enter 1234.
Call Server Configuration The Call Server intercepts and responds to authentication challenges from SIP peers on behalf of some or all devices calling though the Call Server. This feature allows authentication security between the Call Server and its peers to be completely separate from security between the endpoints and the Call Server.
Call Server Configuration Field Description Shared Outbound Authentication (table of authentication entries) Lists the authentication credential entries defined for general use by the Call Server to authenticate its requests, showing the realm in which the entry is valid and the user name. You can add, edit, or delete credential entries. Use the Realm or Name field and Search button above the list to narrow the list.
Call Server Configuration Field Description Device Authentication Name The name that the device includes in registration and signaling requests or responses to authentication challenges. Note: The name and password for a device are whatever values the person who configured it specified. They don’t uniquely identify a specific device; multiple devices can have the same name and password.
Call Server Configuration Field Description Allow site-less registrations If this option is selected, endpoints that don’t belong to a configured site or territory can register with the Call Server. Otherwise, only endpoints in a subnet configured in the site topology can register. When compliant Select the action to take when the registration policy script returns COMPLIANT. When noncompliant Select the action to take when the registration policy script returns NONCOMPLIANT.
Call Server Configuration an exception to non-compliant endpoints allows you to find them on the Endpoints page so that you can contact the owners. Note: Registration Policy Scripting Tips When you click Update, a Javascript parser evaluates the registration policy script. If there is a syntax error in the script, an error message reports the problem and asks if you still want to update. You may do so in order to save a work in progress, but the script won’t be used until it’s valid.
Call Server Configuration Variable Initial value EP_IS_IPV4 “TRUE” if EP_IP is an IPv4 address. Blank otherwise. EP_IS_IPV6 “TRUE” if EP_IP is an IPv6 address. Blank otherwise. EP_MODEL Endpoint model. EP_OWNER Endpoint owner. EP_OWNER_DOMAIN Endpoint owner's domain. EP_REG_IS_H323 “TRUE” if the registration request uses H.323 signaling. Blank otherwise. EP_REG_IS_SIP “TRUE” if the registration request uses SIP signaling. Blank otherwise.
Call Server Configuration Variable Initial value REG_SUBNET_IP_ADDRESS IP address of the subnet where the endpoint is attempting to register. Enter it here in normal dot or colon notation (such as 1.2.3.4 for IPv4). In the script, this is represented as an array. If the IP address is IPv4, there are 4 elements in the array. If the IP address is IPv6, there are 8 elements in the array. REG_SUBNET_MASK IP mask of the subnet where the endpoint is attempting to register.
Call Server Configuration The following sample scripts illustrate some of the ways in which registration requests can be evaluated. You can use them as templates or starting points for your scripts. /////////////////////////////// // Reject endpoints with the specified problem software version and all // SIP registrations. Record an appropriate exception for each case. // var result = COMPLIANT; if (EP_VERSION == "1.2.3.4") { EP_EXCEPTION += "Problem version 1.2.3.4 is not allowed\n"; result = NONCOMPLIANT
Call Server Configuration if (DDlength > 0) { if (DDlength != SumDigits) return NONCOMPLIANT; } /////////////////////////////// // Reject aliases that don't start with CC and AC (country code and area code); // otherwise accept. // var CCAndAC = REG_SITE_COUNTRY_CODE + REG_SITE_AREA_CODE; var DD_CCAndAC = EP_H323_DIALEDDIGITS_ALIAS[0].substring(0,CCAndAC.length); if (DD_CCAndAC != CCAndAC) return NONCOMPLIANT; /////////////////////////////// // Reject aliases that don't start with AC (area code).
Call Server Configuration IPstring = EP_IP[i]; } else { IPstring += "." + EP_IP[i] } } for (i=0; i
Call Server Configuration See also: Call Server Configuration on page 233 Add Simplified ISDN Gateway Dialing Prefix Dialog Box on page 272 Edit Simplified ISDN Gateway Dialing Prefix Dialog Box on page 273 Add Simplified ISDN Gateway Dialing Prefix Dialog Box The Add Simplified ISDN Gateway Dialing Prefix dialog box lets you create a new prefix-driven simplified ISDN gateway dialing service for using external ISDN gateways. Note: ISDN Gateway vs. H.
Call Server Configuration Edit Simplified ISDN Gateway Dialing Prefix Dialog Box The Edit Simplified ISDN Gateway Dialing Prefix dialog box lets you edit a prefix-driven simplified ISDN gateway dialing service. 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.
Call Server Configuration Column Description Type The type of service. Display only. Name A display name for this service. Code The vertical service code (VSC) for this service. Must consist of an asterisk/star (*) followed by two digits. Registered endpoints can activate this feature by dialing the VSC followed by the alias. They can deactivate it by dialing the VSC alone. Description Brief description of the service. Enabled Clearing this check box lets you turn off the service.
Call Server Configuration The following table describes the fields on the Embedded DNS page. Field Description Enable embedded DNS service Enables the embedded DNS servers. Call server sub-domain controlled by RealPresence DMA The fully qualified domain name of the enterprise domain for which the RealPresence DMA system is to provide DNS. For instance, for the base domain example.com, the sub-domain that the RealPresence DMA system services might be: callservers.example.
Call Server Configuration History Retention Settings The Polycom RealPresence DMA system is preconfigured with the number of history records of various types to retain. When the retention limit for a record type is reached, the system purges a specific number of the oldest records of that type. The following table shows the retention limit for each record type and how many are purged at a time when the retention limit is reached.
Call Server Configuration 3 Specify how many low-value signaling records to retain. 4 Click Update. A dialog box informs you that the configuration has been updated. 5 Click OK. See also: Call Server Configuration on page 233 Polycom, Inc.
Site Topology This chapter describes the following Polycom® RealPresence® Distributed Media Application™ (DMA®) 7000 site topology configuration topics: ● About Site Topology ● Sites ● Site Links ● Site-to-Site Exclusions ● Territories ● Network Clouds ● Site Topology Configuration Procedures About Site Topology Site topology information logically describes your network and its interfaces to other networks, including the following elements: ● Site — A local area network (LAN) that generally corresponds wit
Site Topology Note: Integration Not Supported in Maximum Security Mode Integration with a Polycom RealPresence Resource Manager or CMA system is not supported in Maximum security mode. ● If you don’t have a Polycom RealPresence Resource Manager or CMA system, enter site topology information about your network directly into the Polycom RealPresence DMA system’s site topology pages.
Site Topology The protocol-specific routing settings for a site determine whether and how calls from that site can traverse the firewall to reach endpoints outside the enterprise network: ● Via a transparent firewall ● Via the specified SBC ● Not at all The site’s routing settings are used when the dial string is resolved by a dial rule using the Resolve to external address or Resolve to IP address action (rules 5 and 6, respectively, of the default dial plan; see Dial Rules on page 239).
Site Topology Site Information Dialog Box Lets you view information about the selected site, including which subnets are associated with it and counts of the devices it contains. The following table describes the fields in the dialog box, all of which are read-only. Field Description Site Info Site name Name of the site. Note: If the system’s embedded DNS service is enabled (see Embedded DNS on page 274), the system uses the site name to create the Logical host name (see below).
Site Topology Add Site Dialog Box 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 box. Field Description General Info General Settings Site name A meaningful name for the site (up to 128 characters).
Site Topology Field Description 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, which can be dialed by both IP endpoints registered to the Call Server and ISDN endpoints dialing in through an ISDN gateway. The assignment options are: • No assignment. Select this option when you don’t want to define a range of E.164 aliases for the site. • Manual assignment.
Site Topology Field Description Country code The country code for the site’s location. Click the CC button to select from a list of countries. To apply ITU dialing rules, the system must compare the country code of the gateway site with the country code of the call’s destination. Area code The city or area code for the site’s location. Leading zeroes are optional. For example, the city code for Paris is 01, but you can enter either 01 or 1 in this field.
Site Topology Field Description Allowed via H.323-aware firewall Allows H.323 calls to the internet through a firewall. Allowed via H.323-aware SBC or ALG Enables H.323 calls to the internet through the specified session border controller (SBC) or application layer gateway (ALG). Call signaling address (IPv4) The call signaling address for the H.323 SBC or ALG. Port The call signaling port for the H.323 SBC or ALG. SIP Routing Internet calls are not allowed Disables SIP calls to the internet.
Site Topology Field Description General Info General Settings Site name A meaningful name for the site (up to 128 characters). Note: If the system’s embedded DNS service is enabled (see Embedded DNS on page 274), the system uses the site name to create the Logical host name (see Site Information Dialog Box on page 281). We strongly recommend: • Using site names that contain only characters permitted in a host name (letters, numbers, and internal hyphens).
Site Topology Field Description 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, which can be dialed by both IP endpoints registered to the Call Server and ISDN endpoints dialing in through an ISDN gateway. The assignment options are: • No assignment. Select this option when you don’t want to define a range of E.164 aliases for the site. • Manual assignment.
Site Topology Field Description Country code The country code for the site’s location. Click the CC button to select from a list of countries. To apply ITU dialing rules, the system must compare the country code of the gateway site with the country code of the call’s destination. Area code The city or area code for the site’s location. Leading zeroes are optional. For example, the city code for Paris is 01, but you can enter either 01 or 1 in this field.
Site Topology Field Description Allowed via H.323-aware firewall Allows H.323 calls to the internet through a firewall. Allowed via H.323-aware SBC or ALG Enables H.323 calls to the internet through the specified session border controller (SBC) or application layer gateway (ALG). Call signaling address (IPv4) The call signaling address for the H.323 SBC or ALG. Port The call signaling port for the H.323 SBC or ALG. SIP Routing Internet calls are not allowed Disables SIP calls to the internet.
Site Topology Note: Subnets and Sites You can assign a subnet to only one site. The following table describes the fields in the dialog box. Field Description Name The name of the subnet. Required and must be unique. IP address The IP address of the subnet. Subnet mask length The CIDR (Classless Inter-Domain Routing) prefix size value (the number of leading 1 bits in the routing prefix mask). This value, together with the IP Address, defines the subnet.
Site Topology Field Description Subnet mask length The CIDR (Classless Inter-Domain Routing) prefix size value (the number of leading 1 bits in the routing prefix mask). This value, together with the 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. Max bandwidth (Mbps) The total bandwidth limit for voice and video calls.
Site Topology Column Description Max Total Bandwidth (Mbps) 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.
Site Topology Field Description Name A meaningful name for the link (up to 128 characters). Description A brief description of the link (up to 200 characters). From site The originating site of the link (view only). To site The destination site of the link (view only). Max bandwidth (Mbps) The total bandwidth limit for voice and video calls, which you set at the gateway or router. Max bit rate (kbps) The per-call bit rate limit for voice and video calls, which you set at the gateway or router.
Site Topology 2 In the Actions list, click Add. 3 In Step 1 of the wizard, select the first site for the exclusion. Click Next. If the site you want isn’t displayed in the list, you can search by site name or territory. 4 In Step 2 of the wizard, select the second site for the exclusion. Click Next. 5 In Step 3 of the wizard, review the exclusion and click Done if it’s correct.
Site Topology Column/Section Description Primary Cluster The primary Polycom RealPresence DMA cluster responsible for this territory. Backup Cluster The backup Polycom RealPresence DMA cluster, if any, responsible for this territory. You must have a supercluster consisting of at least two Polycom RealPresence DMA clusters in order to specify a backup. Host Conference Rooms Indicates whether this territory is used for hosting conference rooms (VMRs, or virtual meeting rooms).
Site Topology Field Description Available sites Lists sites found and shows the territory, if any, to which each currently belongs. 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.
Site Topology See also: About Site Topology on page 278 Territories on page 294 Site Topology Configuration Procedures on page 299 Network Clouds The Network Clouds page contains a list of the MPLS (Multiprotocol Label Switching) network clouds defined in the site topology. Note: Network Clouds vs. the Internet/VPN Site Don’t confuse this with the Internet/VPN site. MPLS is a special technology typically offered via a private WAN environment, providing more reliability than the Internet.
Site Topology Field Description Associated Sites Search Sites Enter search string or leave blank to find all sites. Search Result Lists sites found and shows the territory, if any, to which each belongs. Select a site and click the right arrow to open the Add Site Link dialog box (see Add Site Link Dialog Box on page 292). Associated Sites Lists sites linked to the cloud and shows the territory, if any, to which each belongs.
Site Topology Site Topology Configuration Procedures To configure your site topology in the RealPresence DMA system 1 Go to Network > Site Topology > Sites. Initially, the list of sites contains only an entry named Internet/VPN, which can’t be edited. 2 For each site in your network topology, do the following: a In the Actions list, click Add. b In the Add Site dialog box, complete the General Info section. See Add Site Dialog Box on page 282.
Site Topology 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 box appears. e Define the link. See Add Site Link Dialog Box on page 292. f Repeat the previous two steps for each additional site linked to this cloud. g Click OK. 8 Go to Network > Site Topology > Site-to-Site Exclusions, and for each exclusion in your network topology, do the following: a In the Actions list, click Add.
Users and Groups This chapter describes the following Polycom® RealPresence® Distributed Media Application™ (DMA®) 7000 system management topics related to users and groups: ● User Roles Overview ● Adding Users Overview ● Users ● Groups ● Login Sessions ● Change Password Dialog Box User Roles Overview The Polycom RealPresence DMA system has four user roles, or classes of users, each with its own set of permissions.
Users and Groups Role Description Provisioner Responsible for the management of Conferencing User accounts. Can create or modify only users with no role other than Conferencing User, but can view all local users. Must be an enterprise user to view all enterprise users. Can view history reports. If you have a Polycom RealPresence Resource Manager system or any other API client, assign this role to its users who should have provisioning rights and responsibilities.
Users and Groups Note: Enterprise vs. Local Users You must be an enterprise user (with the appropriate user role assignments) to see and work with enterprise users. A local user can only see other local users, regardless of user roles. A newly installed system has a single local user account, admin. We strongly recommend that, as part of initial system setup, you create a local user account for yourself with the Administrator role, log in using that account, and delete the admin user account.
Users and Groups The system matches any string you enter against the beginning of the value for which you’re searching. For the Search users field at the top, it matches against user ID, first name, and last name. For instance, if you enter “sa” in the Search users field, it displays the users whose user ID, first name, or last name begins with “sa.” To search for a string not at the beginning of the field, you can use an asterisk (*) as a wildcard.
Users and Groups Column Description Associated Endpoints The endpoints associated with the user, if any. Passcodes The numeric passcodes specified for this user, if any: • Chairperson passcode — Passcode that identifies chairpersons in the user’s conferences. • Conference passcode — Passcode that callers must enter to join the user’s conferences. For enterprise users, passcodes (both kinds) generally come from the Active Directory. See Adding Passcodes for Enterprise Users on page 162.
Users and Groups Field Description User pass-through to CDR Optional value to put in the userDataA field of call CDRs associated with this user. For instance, this might be a user ID from some external system or database. Account disabled If checked, the user can’t host conferences (the user’s conference room or rooms are not available) and can’t access the system management interface.
Users and Groups Field Description Associated Roles Available roles Lists the roles available for assignment to the user. 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 on page 301. Selected roles Lists the roles selected for assignment to the user. Conference Passcodes Chairperson passcode The numeric passcode that identifies chairpersons in the user’s conferences.
Users and Groups Field Description User ID The user’s login name. Password Confirm password The user’s system login password (not conference or chairperson passcode). This is the password that enables users with explicitly assigned roles to log into the system management interface (see User Roles Overview on page 301). The password must satisfy the local password rules specified for the system (see Local Password on page 58).
Users and Groups Field Description 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). Associated Endpoints Associated endpoints Lists the endpoints associated with the user. Click Select to open the Select Associated Endpoints dialog box and associate an endpoint with the user (see Select Associated Endpoints Dialog Box on page 310). Click Delete to delete an associated endpoint.
Users and Groups 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.
Users and Groups ● One enterprise conference room (if this is an enterprise user) automatically assigned to the user as part of the Active Directory integration process. You can’t delete this conference room, but you can modify it. ● Custom conference rooms manually added using the Add command in this dialog box. ● 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.
Users and Groups Field Description Initial Start Time For a conference room created by the Polycom RealPresence DMA system for a calendared meeting (Polycom Conferencing for Outlook), the start time and date of the meeting. For a conference room created by the Polycom RealPresence Resource Manager system (via the RealPresence DMA system API) for a non-Lync scheduled meeting, the start time and date of the meeting.
Users and Groups Field Description Room ID The unique ID of the conference room. Click Generate to let the system pick an available ID (from the range set in Conference Settings). If using alphanumeric conference room IDs, don’t include multiple consecutive spaces or the following characters: ()&%#@|"':;, If the ID includes any other punctuation characters, it must start with an alphanumeric character and end with an alphanumeric character. Dial-in # Number used to dial into conference room.
Users and Groups Field Description Chairperson passcode The numeric passcode that identifies chairpersons in this room’s conferences. If none, the room’s conferences don’t include the chairperson feature. If the user has a chairperson passcode, it appears here. You can change it to a different passcode for this room only. Must contain numeric characters only (the digits 0-9) and may be up to 16 digits long. Can’t be the same as the conference passcode.
Users and Groups Field Description Resource priority value If the RealPresence DMA system is deployed in an AS-SIP environment with a resource prioritization mechanism and Local Session Controller (LSC), set this to the priority value to assign to conferences using this conference room. If using a custom namespace, enter the value in the box below the list.
Users and Groups Field Description Dial-out Presets If selected, this conference room is for a preset dial-out conference, referred to in the Polycom RealPresence Resource Manager system as an Anytime conference. When someone dials in and starts a conference, the system dials out to the entries in the Dial-out Participants list. (See the notes below for exceptions.) Clearing this check box lets you turn off the automatic dial-out temporarily without losing the configuration data.
Users and Groups See also: Users on page 303 Conference Rooms Dialog Box on page 310 Add Dial-out Participant Dialog Box on page 321 Edit Dial-out Participant Dialog Box on page 321 Conference Rooms Procedures on page 323 Edit Conference Room Dialog Box Lets you view or modify a conference room’s details. The following table describes the parts of the Edit Conference Room dialog box. Field Description Room ID The unique ID of the conference room.
Users and Groups Field Description MCU pool order MCU pool order used by this conference room, which is used to determine which MCU hosts a conference (see MCU Pool Orders on page 145). If not selected, the room uses the highest-priority pool order associated with any group to which the user belongs, or if none, the system’s default pool order (see Conference Settings on page 185). Max participants Maximum number of callers allowed to join the conference. Automatic means the MCU’s maximum is used.
Users and Groups Field Description Resource priority namespace In an Assured Services SIP (AS-SIP) environment, a Local Session Controller (LSC) can provide priority-based precedence and preemption services to ensure that the most important calls get through.
Users and Groups Field Description Conference Duration Maximum duration of a conference (in hours and minutes) or Unlimited (the maximum in this case depends on the MCU). If not selected, the room uses the longest duration associated with any group to which the user belongs, or if none, the system’s default maximum duration. (see Conference Settings on page 185). Calendar Event This section appears only for calendared meeting (Polycom Conferencing for Outlook) conference rooms.
Users and Groups See also: Users on page 303 Conference Rooms Dialog Box on page 310 Conference Rooms Procedures on page 323 Add Dial-out Participant Dialog Box Lets you add a participant to the conference room’s Dial-out Participants list. When someone dials into the conference room and starts a conference, the system dials out to the participants in the list. The following table describes the parts of the Add Dial-out Participant dialog box.
Users and Groups To remove the default admin account and create a local account for yourself with administrative privileges 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 on page 322. 3 Log out and log back in using your new local account. 4 Go to Users > Users and delete the admin account. See To delete a local user on page 323. To find a user or users 1 Go to User > Users.
Users and Groups 3 Select the user and click Edit. 4 As required, edit the General Info, Roles, and Conference Passcodes sections of the User Properties dialog box. See Edit User Dialog Box on page 307. For enterprise users, you can change their roles and their chairperson and conference passcodes, and you can enable or disable their accounts, but you can’t change user names, user IDs, or user passwords. For local users, you can change everything but the user ID.
Users and Groups b To link this preset conference to an external audio conferencing bridge (for hosting audio-only participants), in the Digits field enter the E.164 number for connecting to that bridge, and in the IVR DTMF field enter any DTMF digits (such as an access code or PIN) to send to the audio conferencing bridge after connecting (use p to specify a pause). This capability requires a Polycom MCU with ISDN service.
Users and Groups See also: Users on page 303 Conference Rooms Dialog Box on page 310 Add Conference Room Dialog Box on page 312 Edit Conference Room Dialog Box on page 317 Users Procedures on page 321 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. Note: Enterprise vs.
Users and Groups Field Description Conference Template Template assigned to the group, if any, which defines the conference properties (or links to the Polycom MCU profile) used for its conferences. See Conference Templates on page 190. The template assignment can be made at the conference room, AD group, or system default level. MCU Pool Order MCU pool order assigned to this group, if any, which is used to determine which MCU hosts a conference. See MCU Pool Orders on page 145.
Users and Groups See also: Users on page 303 Groups on page 325 Enterprise Groups Procedures on page 329 Edit Group Dialog Box The following table describes the fields in the Edit Group dialog box. Field Description Class of service Select to assign the group a class of service other than the system’s default (see Conference Settings on page 185).
Users and Groups Field Description Presence publishing options In a Microsoft® Lync 2013 environment, you can configure presence publishing (the publishing of VMR status to a Lync 2013 client contact list) for any VMR that belongs to a member of this group. Enable this check box to override the system-wide default presence publishing settings defined on the Admin > Conference Manager > Conference Settings page.
Users and Groups Enterprise Groups Procedures The Polycom RealPresence DMA system’s ability to import an enterprise group and assign it a conference template lets you customize the conferencing experience for all members of the group. 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.
Users and Groups 2 Optionally, in the Actions list, click Move Up until your new conference template has Priority 1. This ensures that users who have access to multiple conference templates will use this one for their enterprise conference room. You can choose a different priority level, but then some members of the group for which you created the template may end up using a higher-ranking template.
Users and Groups See also: Session on page 58 Users and Groups on page 301 Change Password Dialog Box The system may be configured to expire local user passwords after a certain number of days (see Local Password on page 58). If your password has expired when you try to log into the system, the Change Password dialog box prompts you for a new password. You can change your password at other times by going to User > Change Passwords (but not more often than specified on the Local Password page).
System Management and Maintenance This chapter describes the following Polycom® RealPresence® Distributed Media Application™ (DMA®) 7000 system operations topics: ● Management and Maintenance Overview ● Recommended Regular Maintenance ● Dashboard ● Alerts ● System Log Files ● Troubleshooting Utilities ● Diagnostics for your Dell Server ● Backing Up and Restoring ● Upgrading the Software ● Adding a Second Server ● Replacing a Failed Server ● Shutting Down and Restarting Management and Maintenance Overview T
● Using the system tools provided to aid with system and network diagnostics, monitoring, and troubleshooting. See Troubleshooting Utilities on page 372. Should the need arise, Polycom Global Services personnel may ask you to run these tools. ● Upgrading the system when upgrades/patches are made available. See Upgrading the Software on page 380. Administrative Best Practices The following are some of our recommendations for administrative best practices: ● Perform the recommended regular maintenance.
● Download log archives regularly and back them up securely (preferably offsite as well as onsite). Delete downloaded log archives to free up disk space. ● 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 Polycom RealPresence DMA System User Roles and Their Access Privileges on page 24).
Go to Maintenance > Backup and Restore and download and delete backup files (see Backing Up and Restoring on page 374). Go to Maintenance > System Log Files and download and delete log file archives (you must have the Auditor role to do so; see System Log Files on page 370). Go to Admin > Local Cluster > Logging Settings and reducing the retention period for log archives (see Logging Settings on page 80).
Certificates Go to Admin > Local Cluster > Certificates and verify that the list of certificates contains the certificates you’ve installed and looks as you would expect (an archived screen capture may be helpful for comparison). Display the details for any certificate you’ve installed and verify they are as expected (again, an archived screen capture may be helpful for comparison). Network usage data export The system stores up to approximately 1 GB of network usage data, deleting the oldest as needed.
See also: Active Directory Integration Pane on page 337 Call Server Active Calls Pane on page 337 Call Server Registrations Pane on page 338 Cluster Info Pane on page 338 Conference History – Max Participants Pane on page 338 Conference Manager MCUs Pane on page 339 Conference Manager Usage Pane on page 339 Exchange Server Integration Pane on page 340 License Status Pane on page 340 Resource Management System Integration Pane on page 340 Signaling Settings Pane on page 341 Supercluster Status Pane on page 3
Call Server Registrations Pane Displays the total number of active (including active quarantined) and inactive (including inactive quarantined and blocked) endpoint registrations and the number that failed in the past 24 hours. Hover over a registration number to see the limit. Also displays the total number of registrations for each cluster of the supercluster. Hover over a cluster’s total to see the breakdown between active and inactive. Click a column heading to sort on that column.
See also: Dashboard on page 336 Conference Manager MCUs Pane Displays information about all the MCUs that are managed by Conference Manager to host conference rooms (virtual meeting rooms, or VMRs). The information shown includes the MCU’s connection and service status, its capabilities (recording, IVR, and SVC), its reliability (in terms of disconnects and call failures), and the number of ports in use and available to Conference Manager. Hover over an icon to see an explanation of it.
Exchange Server Integration Pane If the Polycom RealPresence DMA system is integrated with a Microsoft Exchange server (see Microsoft Exchange Server Integration on page 175), displays the following: ● The integration status, which can be one of the following: Unavailable — A service status or inter-server communication problem prevented determination of the integration status. Error — The system was unable to establish a connection to the Exchange server.
● User name used to log into the RealPresence Resource Manager or CMA system. ● Time when site topology data was last updated from the RealPresence Resource Manager or CMA system. ● Number of territories, sites, site links, and network (MPLS) clouds in the site topology data obtained from the RealPresence Resource Manager or CMA system. Click the Link button to go to the Polycom RealPresence Resource Manager or CMA System page. See also: Dashboard on page 336 Signaling Settings Pane Displays the H.
User Login History Pane Displays the following information about logins by your user ID: ● The server you’re currently logged into. ● The time, date, server logged into, and source (host name or IP address) of the last successful login (prior to your current session) by your user ID. ● The time, date, server, and source of the last failed login attempt by your user ID. ● The number of consecutive failures before your current successful login.
Click the link to go to the RealPresence DMAs page. See also: Alerts on page 342 Alert 1003 Cluster is orphaned. The replication link with the specified cluster seems to be corrupted. Click the link to go to the RealPresence DMAs page. Try removing that cluster from the supercluster and then rejoining. See also: Alerts on page 342 Alert 1004 No heartbeats from cluster . Last heartbeat received YYYY-MM-DD HH:MM GMT+/-H[:MM]. The specified cluster is not sending scheduled heartbeats.
Alert 1105 : Primary cluster and backup cluster are not reachable. Territory may not be functioning. The cluster from which the alert originated is unable to communicate with the specified territory’s primary and backup clusters. This may be a temporary problem, in which case this alert will be cleared as soon as the alerting cluster is once again able to communicate with the clusters in question.
If this alert reoccurs frequently but quickly goes away, that suggests intermittent network problems. If it persists, it will be followed by Alert 1108, indicating that the territory has failed over to the backup cluster. The backup cluster allows conferencing to continue in the territory (at diminished capacity) and fulfills any other responsibilities assigned to the territory. Click the link to go to the Territories page. Determine whether the cluster was deliberately shut down.
Alert 2002 Resource management system unreachable. Last contact on: YYYY-MM-DD HH:MM GMT+/-H[:MM]. The cluster responsible for RealPresence Resource Manager or CMA integration was unable to connect to the Polycom RealPresence Resource Manager or CMA system. This may indicate a network problem or a problem with the Polycom RealPresence Resource Manager or CMA system. Try logging into the Polycom RealPresence Resource Manager or CMA system.
Alert 2102 Zero enterprise conference rooms exist on cluster . The cluster responsible for Active Directory integration successfully retrieved user and group data, but no conference rooms were generated. This may indicate that no directory attribute was specified from which to generate conference room IDs, or that the chosen attribute resulted in empty (null) conference room IDs after the system removed the characters to remove.
(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 on page 342 Alert 2106 Cluster : Failed connection from to Active Directory for user authentications at YYYY-MM-DD HH:MM GMT+/-H[:MM]. The specified server tried to connect to the Active Directory in order to authenticate a user’s credentials and was unable to do so.
Alert 2202 Exchange server integration is not available. Both primary cluster and backup cluster are not operational. The primary and backup clusters for the territory responsible for Exchange server integration are both unreachable. This may indicate serious network problems. It’s also possible that someone shut both clusters down, or shut down one and the other then failed, or both failed (unlikely). Click the link to go to the RealPresence DMAs page to begin troubleshooting.
See also: Alerts on page 342 Alert 2601 : Cannot reach Lync server for presence publishing. The cluster cannot communicate with the specified Lync server at the currently configured Next hop address. This could indicate a network problem, or a problem with the Lync server. Click the link to go to the Network > External SIP Peers page to begin troubleshooting. Try to ping the Lync server’s Next hop address to verify basic connectivity.
Click the link to go to the Network > External SIP Peers page to begin troubleshooting. Try pinging the specified Lync server’s IP address. If it is reachable, verify that the Next hop address, Port, and Transport type settings on this page are correct. See also: Alerts on page 342 Alert 2605 : Cannot authenticate with to resolve conference IDs. The system can’t authenticate with the specified Lync server, preventing Lync conference ID resolution.
Alert 3102 Cluster : The server certificate will expire within 1 day. All system access may be lost. The specified cluster’s server certificate is about to expire. This is the public certificate that the cluster uses to identify itself to devices configured for secure communication. If you allow it to expire, the cluster will no longer be able to communicate with any such devices, including MCUs, endpoints, the AD server, and the Exchange server.
Alert 3105 Cluster : One or more CA certificates will expire within 30 days. The specified cluster has a CA certificate or certificates that will expire soon. When a CA certificate expires, the certificates signed by that certificate authority are no longer accepted.
Alert 3203 The EULA for cluster has not been accepted. All calls are blocked on this cluster. The system version has changed, and the End User License Agreement has not yet been accepted. The specified cluster won’t accept any inbound calls, or place outbound calls, until a user with Administrator privileges accepts the agreement upon login. Click the link to go to the Licenses page, where you can view the EULA acceptance status and details.
Alert 3301 Cluster is configured for 2 servers, but only a single server is detected. One of the servers in the specified cluster is not responding to the other server over the private network that connects them. This could be a hardware problem, or the server in question may just need to be rebooted. It’s also possible that the private network connection between the two servers has failed. Check the ethernet cable connecting the GB2 ports and replace it if necessary.
Alert 3305 Cluster : A public signaling network error exists on . The specified server has detected a problem with the signaling network connection. This could be a problem with the GB3 port (eth2 interface), the ethernet cable connecting the server to the enterprise network switch, or that switch. Or, the server in question may just need to be rebooted.
Alert 3310 : DNS cannot resolve . cannot be reached. The specified cluster can’t resolve the domain name of this Active Directory, MCU, ISDN gateway, or DMA cluster. The specified service is currently unreachable. This could indicate a network problem, or that the specified domain name entry is incorrect in the DMA cluster’s configuration.
Alert 3404 Cluster : Log files on server are close to capacity limit and may be purged within 24 hours. Log archives on the specified cluster have reached the percentage of capacity that triggers an alert, set on the Alerting Settings page. Click the link to go to the System Log Files page. We recommend routinely downloading archived logs and then deleting them from the system. See also: Alerts on page 342 Alert 3405 Server CPU utilization >50% and <75%.
Possible explanations: ● Someone upgraded one server of the cluster while the other was turned off or otherwise unavailable. ● An expansion server was added to a single-server cluster, but the new server wasn’t patched to the same software level as the existing server. ● An RMA replacement server wasn’t patched to the same software level as the existing server. If you’re logged into that cluster, click the link to go to the Software Upgrade page.
Alert 3605 Cluster : Custom conference rooms differ between servers. In the specified cluster, the custom conference room counts 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 on page 342 Alert 3606 Cluster : Local users differ between servers.
Use the failure details as a starting point for troubleshooting. If the failure is not hardware or network related, and you are unable to access the server, it may need to be rebooted. Click the link to go to the Network > DMAs page.
See also: Alerts on page 342 Alert 4004 MCU is configured with insufficient user connections. The system was unable to establish an additional management session connection to the specified MCU. Possible explanations: ● IP connectivity between the system and the MCU has been lost. ● This MCU doesn’t allow sufficient connections per user. Polycom MCUs use synchronous communications.
Click the link to go to the Network > MCU > MCUs page to begin troubleshooting. Check the network connection between this MCU and the RealPresence DMA cluster. See also: Alerts on page 342 Alert 4010 MCU disconnect rate is > 4. The DMA cluster has lost connection with the specified MCU more than four times in the past 24 hours. This most likely indicates a network problem, but it could also indicate that the MCU or RealPresence DMA system is under very heavy load.
Alert 4013 MCU is connected with no port capacity. The specified MCU has no ports available for call traffic. This could indicate that the specified MCU is at capacity, or possibly a network problem. This alert appears as soon as the 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 to begin troubleshooting.
The H.323 ID or SIP user name must be updated on the endpoints of the ITP system. See Naming ITP Systems Properly for Recognition by the Polycom RealPresence DMA System on page 95. See also: Alerts on page 342 Alert 5002 One or more endpoints is sending too much H.323 signaling traffic, has been temporarily blacklisted, and may have been quarantined. At least one device, in violation of the H.323 standard, is sending GRQ (gatekeeper request) or RRQ (registration request) messages several times a second.
Alert 6002 Shared number dialing VEQ references entry queue which is not configured on any MCUs. The specified entry queue used by the VEQ is not configured on an MCU. If the VEQ is a Direct Dial VEQ, is “Direct Dial”. Click the link to go to Admin > Conference Manager > Shared Number Dialing / to begin troubleshooting. Ensure that at least one MCU configured in Network > MCU > MCUs has the specified entry queue configured. See Shared Number Dialing on page 220.
See also: Alerts on page 342 Alert 6104 Ongoing conference on MCU failed over to MCU : . A conference using the conference room identifier has been moved from to 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 on page 342 Polycom, Inc.
Alert 6201 : Errors in presence publication for Lync server . Presence for of Polycom conference contacts will not be published due to Lync server configuration ‘MaxEndpointExpiration’ value . 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 seconds.
If suitable for your environment, either increase the ‘MaxEndpointExpiration’ value on the Lync server, or decrease the number of Polycom conference contacts configured for publishing. Click the link to go to the Network > External SIP Peers page. See also: Alerts on page 342 Alert 7001 Failed registration data incomplete: history limited to hours. Registration data retention settings are too low for the system to determine the number of failed registrations in the past 24 hours.
System Log Files The System Log Files page lists the available system log file archives and lets you run the following Action list commands: ● Roll Logs — Closes and archives the current log files and starts new log files. If you have a supercluster, you’re prompted to choose the cluster whose log files you want to roll. ● Download Active Logs — Creates and downloads an archive that contains snapshots of the current log files, but doesn’t close the current log files.
System Logs Procedures To download a log archive to your PC or workstation 1 Go to Maintenance > System Log Files. The System Log Files page appears. 2 To download a listed log archive: a Select the file you want. b In the Actions list, click Download Archived Logs. c In the dialog box, select a location and click Save. 3 To download an archive of the currently open log files (but not close them): a In the Actions list, click Download Active Logs.
See also: Management and Maintenance Overview on page 332 Recommended Regular Maintenance on page 334 Alerts on page 342 Call Detail Records (CDRs) on page 400 Troubleshooting Utilities The Polycom RealPresence DMA system’s Troubleshooting Utilities submenu includes several useful network and system status commands, which you can run and view the output of in the system’s familiar graphical interface.
I/O Stats Use I/O Stats to see CPU resource allocation and read/write statistics for each server. To run iostat on each server » Go to Maintenance > Troubleshooting Utilities > I/O Stats. The system displays results of the command for each server. SAR Use SAR to see a complete system activity report (from the preceding midnight to the current time) for each server. To run sar on each server » Go to Maintenance > Troubleshooting Utilities > SAR. The system displays results of the command for each server.
Backing Up and Restoring Every night, each Polycom RealPresence DMA system cluster creates a configuration-only backup of the system, which includes: ● Local user account information (including local data for enterprise users, such as conference room attributes) ● System configuration data ● Supercluster and resource management system integration data (if applicable) At any time, you can create either a configuration-only backup or a full backup, which adds all the transactional data, including logs, CDRs,
Note: Best Practices for Backup Data We strongly suggest that you: • Download backup files regularly for safekeeping • Delete backup files after downloading in order to free up disk space. • If you need to preserve transactional data and be able to restore it, regularly perform a full backup and download it from the cluster.
● History, network usage, and log data Which data you can restore depends on: ● The type of backup file (full or config-only) you selected. ● For a restore from a non-identical software version, which restore operations the current version supports for the source version data. Caution: Restoring Config-Only Backups Restoring feature and system configuration, but not network configuration (or vice versa) will result in invalid primary or backup cluster assignments for some territories.
5 Click Close. To create a new backup file 1 Go to Maintenance > Backup and Restore. 2 Verify that the oldest backup file listed is one you don’t want to keep or have already downloaded. Only ten files are saved. Creating a new backup will delete the oldest file (unless there are fewer than ten). 3 In the Actions list, click Create New (Full) to create a full backup or Create New (Config Only) to create a configuration-only backup (no transaction data).
9 Click OK. The system logs you out and the server reboots (typically, this takes about five minutes). After it comes back up, in a two-server cluster, the second server syncs to it, thus being restored to the same state. Depending on the configuration changes being applied, it may reboot so the changes can take effect. When done, both servers’ LCDs display RealPresence DMA Clustered.
c 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 restore.
5 In the RealPresence DMA USB Configuration Utility window, click Copy a Backup to the USB flash drive. 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. The utility’s main window states that The USB flash drive is ready to restore the system from a backup file.
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 addresses become the upgraded version's physical host name(s) and IP addresses, so accessing the system doesn't change.
Basic Upgrade Procedures Caution: Upgrade Considerations Always check the upgrade version release notes before installing an upgrade. The upgrade installation process automatically creates a backup, which enables you to roll back an upgrade (restore the previous version) if necessary. As a precaution, however, we recommend that you download a recent backup file before you begin to install an upgrade. See Backing Up and Restoring on page 374. You can roll back only the last applied upgrade.
5 Click Close. The Upgrade Package Details section displays information about the file you uploaded. The description includes an estimated install time. 6 Verify that the upgrade package is correct. If a system restart is required, make sure that there are no calls on the system. Most upgrades will require a restart.
a In a two-server cluster, verify on the Dashboard that both servers are up and the private network connection is operating properly. b Go to Maintenance > Software Upgrade and check the Operation History table. c If the upgrade requires a new license activation key code or codes, obtain and install them as described in Add Licenses on page 82. 12 If this cluster is part of a supercluster, do the following: a Go to Network > RealPresence DMAs, and rejoin this cluster to the supercluster.
Note: Give the System Time to Restart Wait about five minutes before trying to log back into the system. You may need to restart your browser or flush your browser cache in order to do log back in. f Log back into the cluster you removed and verify on the Supercluster Status pane of the Dashboard that the cluster is no longer part of the supercluster. g Return to Maintenance > Software Upgrade. 4 In the Actions list, click Roll Back. A confirmation dialog box appears. 5 Click Yes.
See also: Management and Maintenance Overview on page 332 Upgrading the Software on page 380 Incompatible Software Version Supercluster Upgrades All the clusters in a supercluster must be running compatible software versions. Patch releases will generally be compatible, and can be installed using the procedure in Basic Upgrade Procedures on page 382. But major and minor version upgrades will not be compatible.
Factors to Consider for an Incremental Supercluster Upgrade Before deciding to attempt an incremental supercluster software upgrade, be aware of the following: ● An incremental upgrade can easily take five times as long as the simplified method. ● As clusters are removed from the existing supercluster and upgraded, its capacity is reduced. As the new supercluster is being built, it won’t be at full capacity until all clusters are upgraded.
Caution: Upgrade Considerations Always check the upgrade version release notes before installing an upgrade. The upgrade installation process automatically creates a backup, which enables you to roll back an upgrade (restore the previous version) if necessary. As a precaution, however, we recommend that you download a recent backup file before you begin to install an upgrade. See Backing Up and Restoring on page 374. You can roll back only the last applied upgrade.
e Remove each cluster except the one you’re logged into from the supercluster. As each cluster is removed, it restarts. 4 On the cluster you’re logged into (let’s call it cluster A), do the following: a Go to Maintenance > Software Upgrade. b In the Actions list, click Upgrade. A confirmation dialog box appears. c Click Yes. If a restart is required, a dialog box informs you that the upgrade is starting. Shortly after that, the system logs you out and restarts.
Note: Restart Your Browser if Necessary You may need to restart your browser or flush your browser cache in order to log back into the system. e Log back in and, in a two-server cluster, verify on the Dashboard that both servers are up and the private network connection is operating properly. f Go to Maintenance > Software Upgrade and check the Operation History table. g If the upgrade requires a new license activation key code or codes, obtain and install them as described in Add Licenses on page 82.
Adding a Second Server A single-server Polycom RealPresence DMA system can be upgraded to a fault-tolerant two-server cluster at any time. For an overview of how a two-server cluster works and its advantages, see Two-server Cluster Configuration on page 18. To form a two-server cluster, both servers must be running the same version of the Polycom RealPresence DMA system software.
See also: Management and Maintenance Overview on page 332 Adding a Second Server on page 391 Expanding a Patched System on page 392 Expanding a Patched System To expand a patched single-server system into a two-server cluster 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 one of the provided crossover Ethernet cables).
13 On the Dashboard, check the License Status, Supercluster Status, and Cluster Info panes to verify that you now have a properly configured two-server cluster. See also: Management and Maintenance Overview on page 332 Adding a Second Server on page 391 Expanding an Unpatched System on page 391 Replacing a Failed Server Replacing a server is essentially the same process as adding a second server to a single-server system.
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. If that happens, the server can’t be restarted without user input, requiring a keyboard and monitor. There is no mechanism for shutting down an entire supercluster.
System Reports This chapter 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 ● Active Directory Integration Report ● Orphaned Groups and Users Report ● Conference Room Errors Report ● Enterprise Passcode Errors Report ● Network Usage Report Alert History The Alert History page lets you view all the system alerts for the time period yo
The Start After and Start Before settings are always active and define the time range during which the calls to find begin. Optionally, use End Before to find only calls that ended by the specified time. Use End After to find calls that extended beyond the specified time; this is useful for finding very long calls. When setting the date/time range for your search, keep in mind that retrieving a large number of records can take some time.
Column Description Ingress Cluster The cluster (first, if more than one) that handled the call. Call ID Unique identifier for the call. Export History The Call History page’s Export History list provides a record of the CDR exports (all call and conference data for the specified period) and search results exports from the system. It appears when you click the Show Export History command (in the Actions list).
Column Description Conference Room ID The conference room ID. Start Time Time the conference began (first conference event). End Time Time the conference ended (last conference event). Cluster The cluster that handled the conference. Export History The Conference History page’s Export History list provides a record of the CDR exports (all call and conference data for the specified period) and search results exports from the system.
Column Description Destination The destination 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 destination is an MCU, the MCU name; if a VSC, the VSC value (not including the VSC). Cluster The cluster (first, if more than one) that handled the call. The Display Call History command (in the Actions list) takes you to the Call History page and displays the call that was selected in the Associated Calls list.
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. Exporting CDR Data From the Call History or Conference History page, you can use the Export CDR Data command to download call detail records (CDRs) for the time period you specify.
Note: ITP Systems and CDRs 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.
Field Description dialString Initial dial string as supplied by the originator. If multiple call records, this value is the same across all segments of the call. destEndpoint The destination endpoint’s display name, name, alias, or IP address (in that order of preference), depending on what it provided in the call signaling. If the destination is an MCU, the MCU name; if a VSC, the VSC value (not including the VSC character).
Field Description userDataA The value from the User pass-through to CDR field of the user associated with the endpoint (see Edit User Dialog Box on page 307). For point-to-point calls, this is the user associated with the endpoint that started this call. userDataB For VMR calls, the value from the Conference room pass-through to CDR field of the conference room (VMR) to which the call connected (see Edit Conference Room Dialog Box on page 317).
Field Description maxVideoResolution The maximum vertical resolution used on the video channel, followed by the maximum frame rate while at the maximum resolution, as reported by the MCU at the end of the call. For instance: 720p30 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.
Field Description origSignalingId For SIP point-to-point or VMR calls (dialin=TRUE), the complete From header of the INVITE received from the endpoint. For VMR SIP dial-outs (dialin=FALSE), the To header sent by the RealPresence DMA system to the MCU. Otherwise, blank. origCallId The SIP or H.323 call ID of the call between the originating endpoint and the RealPresence DMA system. For VMR dial-outs, the call ID of the call between the RealPresence DMA system and the MCU. destCallId The SIP or H.
Field Description endTime YYYY-MM-DDTHH:MM:SS.FFF[+|-|Z][HH:MM] (ISO 8601 syntax, where FFF is milliseconds and Z is zero offset) This is when the last participant left the conference. userID Conference room (VMR) owner, shown as: domain\user Domain is LOCAL for non-AD users. If this is a Lync conference, this field is empty. roomID Conference room (VMR) number or Lync conference ID. partCount Maximum number of concurrent calls in the conference (high water mark).
Field Description mcuNameList The MCU(s) used by the conference. If there is more than one (due to cascading or an MCU failover), this is a comma-separated list enclosed in quotes. If the conference was cascaded, the hub MCU is listed first. If there was a failover, the original MCU is listed first. confDisplayNameList The conference display name of the conference as it appears on the MCU.
setting the date/time range for your search, keep in mind that retrieving a large number of records can take some time. Note: Viewing Registration History You can also access the registration history of a specific device by selecting it on the Endpoints page and clicking View Registration History. The registrations that match your search criteria are listed below the search fields.
4 Optionally, specify a start or end time range and any filter criteria you want to use. Then click Search. The system displays the devices matching your search criteria. See also: System Reports on page 395 Call History on page 395 Conference History on page 397 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.
Field Description Site The Active Directory site name for the system. Available only if Auto-discover from FQDN (serverless bind) is selected on the Microsoft Active Directory® Integration page. If serverless bind is enabled, but no site is retrieved, the reason could be: • Site could not be determined: the system’s subnet isn’t mapped to a site (see http://support.microsoft.com//kb/889031). • Auto-discover failed or is disabled: could be problem with DNS domain name or missing SRV records on DNS server.
Orphaned Groups and Users Report If the Polycom RealPresence DMA system is integrated with your Active Directory, it generates an orphaned groups and users report whenever you manually update the directory connection (Admin > Integrations > Microsoft Active Directory) and when the system updates automatically to refresh its cache.
3 When prompted to confirm, click OK. The system removes the orphaned user data. See also: Microsoft Active Directory® Integration on page 152 Active Directory Integration Report on page 409 Enterprise Passcode Errors Report on page 414 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® Integration on page 152.
Note: Duplicate Conference Room IDs Duplicate conference room IDs are not disabled; they can be used for conferencing. But if both users associated with that conference room ID try to hold a conference at the same time, they end up in the same conference. The following table describes the fields in the list. Column Description Problem Description of the issue with this room ID (Blank, Duplicate, or Invalid).
Enterprise Passcode Errors Report If the Polycom RealPresence DMA system is integrated with your Active Directory, conference and chairperson passcodes for enterprise users can be maintained in the Active Directory. See Adding Passcodes for Enterprise Users on page 162. The Polycom RealPresence DMA system reads the Active Directory daily to refresh the information in its cache.
Column Description First Name The enterprise user’s first name. Notes For an invalid passcode, shows the generated value (after the system stripped non-numeric characters out of the attribute value and truncated it if necessary). For duplicate chairperson and conference passcodes, shows the raw attribute value of each and the duplicate value generated (after stripping non-numeric characters and truncating if necessary).
Exporting Network Usage Data From the Network Usage page, you can use the Export Network Usage Data command to download a CSV (comma-separated values) file containing all the network usage data point records for the time period you specify. The system retains the most recent 8 million data points. The file includes a network usage data point record for each throttlepoint, territory, and cluster for each minute of the time period.
Field Description max_video_delay Maximum delay of all QoS reports of all video channels in the scope during the time interval (milliseconds). avg_audio_jitter Mean jitter of all QoS reports of all audio channels in the scope during the time interval (milliseconds). max_audio_jitter Maximum jitter of all QoS reports of all audio channels in the scope during the time interval (milliseconds).
To download network usage data 1 Go to Reports > Network Usage. 2 In the Actions list, click Export Network Usage Data. 3 In the Export Time Frame dialog box, set the Start Date and time and the End Date and time you want to include. The defaults provide all network usage data for the current day. 4 Click OK. 5 Choose a path and filename for the network usage file and click Save. The File Download dialog shows the progress. 6 When the download is complete, click Close.
Polycom RealPresence DMA System SNMP Support This chapter provides a discussion of the Polycom® RealPresence® Distributed Media Application™ (DMA®) SNMP support. It includes these topics: ● SNMP Overview ● Configure SNMP ● Download MIBs SNMP Overview SNMP is an application-layer protocol that provides a message format for communication between SNMP managers and agents. SNMP provides a standardized framework and a common language used for the monitoring and management of resources in a network.
Polycom RealPresence DMA System SNMP Support self-documenting, including information about the purpose of specific traps and inform notifications. Third-party MIBs accessible through the Polycom system may include both hardware and software system MIBs. 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.
Polycom RealPresence DMA System SNMP Support To enable SNMP messaging you must perform the following: ● Enable the SNMP Agent ● Add an SNMP Notification User ● Add an SNMP Notification Agent Enable the SNMP Agent You can enable the SNMP Agent. To enable the SNMP agent 1 Go to Admin > Local Cluster > SNMP Settings. 2 Configure the following settings for the connection between the RealPresence DMA system and the SNMP agent. Setting Description SNMP Version Specifies the version of SNMP you want to use.
Polycom RealPresence DMA System SNMP Support Setting Description V3 Local Engine Id For SNMPv3 only. Displays the RealPresence DMA system contextEngineID for SNMPv3. Security User For SNMPv3 only. Specifies the security name required to access a monitored MIB object. This name cannot be snmpuser. 3 Click Update. Add an SNMP Notification User The Add Notification User dialog box lets you add a security user authorized to receive notifications. For SNMPv3 notifications, a security user is required.
Polycom RealPresence DMA System SNMP Support 4 Click OK. The user displays in the Notification Users list. Edit Notification User Dialog Box The Edit Notification User dialog box lets you modify a security user authorized to receive SNMPv3 notifications. Setting Description Security user The security user name authorized to receive notifications (Traps or Informs). Authentication type The authentication protocol.
Polycom RealPresence DMA System SNMP Support Field Description Port The port that the RealPresence DMA system uses to send notifications. Default port–162 Notification type The type of notification that this agent sends to the notification receiver: • Inform–The agent sends an unsolicited message to a notification receiver and expects or requires the receiver to respond with a confirmation message.
Polycom RealPresence DMA System SNMP Support 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. To download the MIB package for a DMA system 1 Go to Admin > SNMP Settings. 2 Click Download MIBs. 3 In the MIBs dialog box, select the MIB of interest and click Download.
