Polycom® DMA™ 7000 System Operations Guide 5.
Trademark Information Polycom®, the Polycom “Triangles” logo, and the names and marks associated with Polycom’s products are trademarks and/or service marks of Polycom, Inc., and are registered and/or common-law marks in the United States and various other countries. All other trademarks are the property of their respective owners. Java is a registered trademark of Oracle America, Inc., and/or its affiliates. Patent Information The accompanying product may be protected by one or more U.S.
Contents 1 Polycom® DMA™ 7000 System Overview ............. 1 Introduction to the Polycom DMA System . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 The Polycom DMA System’s Primary Functions . . . . . . . . . . . . . . . . . . 1 The Polycom DMA System’s Three Configurations . . . . . . . . . . . . . . . 3 System Capabilities and Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Polycom Solution Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DMA Operations Guide Certificate Details Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Certificate Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Install a Certificate Authority’s Certificate . . . . . . . . . . . . . . . . . . . . . . 41 Create a Certificate Signing Request in the DMA System . . . . . . . . . . 42 Install a Certificate in the DMA System . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Add External Gatekeeper Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 Edit External Gatekeeper Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 External SIP Peer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 Add External SIP Peer Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 Edit External SIP Peer Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DMA Operations Guide Exchange Server Integration Procedure . . . . . . . . . . . . . . . . . . . . . . . . 167 Resource Management System Integration . . . . . . . . . . . . . . . . . . . . . . . . 169 Resource Management System Page . . . . . . . . . . . . . . . . . . . . . . . . . . 170 Join Resource Management System Dialog Box . . . . . . . . . . . . . . . . . 171 Resource Management System Integration Procedures . . . . . . . . . . 172 Juniper Networks SRC Integration . . . . . . . . . . . . . . . . .
Contents The Default Dial Plan and Suggestions for Modifications . . . . . . . . . 228 Add Dial Rule Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232 Edit Dial Rule Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234 Script Debugging Dialog Box for Preliminaries/Postliminaries . . . . 235 Sample Preliminary and Postliminary Scripts . . . . . . . . . . . . . . . . . . . . . . 236 Hunt Groups . . . . . . . . . . . . . . . . . . . . . .
DMA Operations Guide Network Clouds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285 Add Network Cloud Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286 Edit Network Cloud Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287 Site Topology Configuration Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . 287 12 Users and Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Conference Manager Usage Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335 Exchange Server Integration Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335 License Status Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336 Resource Management System Integration Pane . . . . . . . . . . . . . . . . 336 Signaling Settings Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337 Supercluster Status Pane .
DMA Operations Guide Alert 3303 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349 Alert 3304 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349 Alert 3305 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350 Alert 3401 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350 Alert 3402 . . . . . . . . . . . . . .
Contents 14 System Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383 Alert History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383 Call History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384 Export History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385 Conference History . . . . . . . . . . . . . . . . . . . . . . . . .
DMA Operations Guide xii Polycom, Inc.
1 Polycom® DMA™ 7000 System Overview This chapter provides an overview of the Polycom® Distributed Media Application™ (DMA™) 7000 system. It includes these topics: • Introduction to the Polycom DMA System • Polycom Solution Support • Working in the Polycom DMA System • Third-Party Software Introduction to the Polycom DMA System The Polycom DMA system is a highly reliable and scalable video collaboration infrastructure solution based on the Polycom® Proxias™ application server.
DMA Operations Guide Introduction to the Polycom DMA System The Polycom DMA system integrates with your Microsoft® Active Directory®, automating the task of provisioning users for video conferencing. Combined with its advanced resource management, this makes reservationless video conferencing on a large scale feasible and efficient, reducing or eliminating the need for conference scheduling.
Polycom® DMA™ 7000 System Overview Introduction to the Polycom DMA System • Provisioning • Conference control and monitoring • Call control and dial-out • 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. No separate license is needed in order for a Polycom RealPresence Resource Manager system to integrate with the DMA system via the API.
DMA Operations Guide Introduction to the Polycom DMA System The two servers communicate over the private network connecting them. To determine which one should host the public virtual IP address, each server uses three criteria: • Ability to ping its own public physical address • Ability to ping the other server’s public physical address • Ability to ping the default gateway In the event of a tie, the server already hosting the public virtual address wins.
Polycom® DMA™ 7000 System Overview Introduction to the Polycom DMA System Superclustering To provide geographic redundancy and better network traffic management, up to five geographically distributed Polycom DMA system clusters (twoserver or single-server) can be integrated into a supercluster. All five clusters can be Call Servers (function as gatekeeper, SIP proxy, SIP registrar, and gateway). Up to three can be designated as Conference Managers (manage an MCU resource pool to host conference rooms).
DMA Operations Guide Polycom Solution Support • Size of Active Directory supported: 1,000,000 users and 1,000,000 groups (up to 10,000 groups may be imported) The following capabilities and constraints apply to each cluster in the supercluster: • Number of registrations: 15000 • Number of concurrent H.
Polycom® DMA™ 7000 System Overview Working in the Polycom DMA System Professional Services for Microsoft Integration is mandatory for Polycom Conferencing for Microsoft Outlook and Microsoft Office Communications Server or Lync Server 2010 integrations. For more information, please visit www.polycom.com/services/professional_services/ or contact your local Polycom representative.
DMA Operations Guide Working in the Polycom DMA System In addition, you can change the text size used in the system interface and the maximum number of columns in the Dashboard. Note that larger text sizes will affect how much you can see in a given window or screen size and may require frequent scrolling.
Polycom® DMA™ 7000 System Overview Working in the Polycom DMA System Table 1-1 Management interface access privileges Menu/Icon Admin Provisioner Auditor Users 2 • • Groups • Login Sessions 1 • • Change Password • • • Call History • • • Conference History • • • Registration History • • • Network Usage • • Microsoft Active Directory Integration 3 • Enterprise Passcode Errors 3 • Orphaned Groups and Users • Conference Room Errors 3 • User > Reports > • Maintenance
DMA Operations Guide Working in the Polycom DMA System Table 1-1 Management interface access privileges Menu/Icon Admin Provisioner Hunt Groups • • Device Authentication • Registration Policy • Prefix Service 1 • Embedded DNS • History Retention Settings • Auditor • • Admin > Integrations > Microsoft Active Directory • Microsoft Exchange Server • Polycom RealPresence Resource Manager or CMA System • Juniper Networks SRC • Admin > Login Policy Settings > Local Password • Sessi
Polycom® DMA™ 7000 System Overview Working in the Polycom DMA System Table 1-1 Management interface access privileges Menu/Icon Admin Provisioner Auditor Settings. Displays Settings dialog box. • • • Log Out. Logs you out of the Polycom DMA system. • • • Help. Opens the online help topic for the page you’re viewing. • • • 1. Provisioners have view-only access. 2. Must be an enterprise user to see enterprise users.
DMA Operations Guide Third-Party Software Table 1-2 API resource access privileges (continued) API Resource Admin Provisioner Auditor status • • • subscription1 • • user-role • • Conference Room Owner • 1. Conference Room Owners can only access resources that they own and can’t use PUT, POST, or DELETE methods on their user account or conference rooms. 2.
Polycom® DMA™ 7000 System Overview Third-Party Software 4 Contact Polycom Global Services for the root password for the Polycom DMA server. 5 Use ssh to log into the server as root. 6 Upload the modified software via wget or scp. 7 Find the module you’re replacing and install the new version to that location. 8 Reboot the system. License Information The following table contains license information for the open source software packages used in the Polycom DMA system.
DMA Operations Guide Third-Party Software Software Version License Link commonshttpclient 3.0.1 Apache License, Version 2 http://www.apache.org/licenses/LICENSE-2.0 commons-io 1.4 Apache License, Version 2 http://www.apache.org/licenses/LICENSE-2.0 commons-jexl 1.0 Apache License, Version 2 http://www.apache.org/licenses/LICENSE-2.0 commonsjxpath 1.2 Apache License, Version 2 http://www.apache.org/licenses/LICENSE-2.0 commons-lang 2.3 Apache License, Version 2 http://www.apache.
Polycom® DMA™ 7000 System Overview Third-Party Software Software Version License Link Jboss-cache 1.4.1.sp14 LGPLv2.1 http://www.gnu.org/licenses/old-licenses/lgpl-2.1.html Jboss-jaxws 2.0.0.GA LGPLv2.1 http://www.gnu.org/licenses/old-licenses/lgpl-2.1.html Jboss-jmx 4.2.1.GA LGPLv2.1 http://www.gnu.org/licenses/old-licenses/lgpl-2.1.html Jbossremoting 2.2.2.sp1 LGPLv2.1 http://www.gnu.org/licenses/old-licenses/lgpl-2.1.html Jbossserialization 4.2.1.GA LGPLv2.1 http://www.gnu.
DMA Operations Guide Third-Party Software Software Version License Link Python Part of Centos distrib. Python Software Foundation License Version 2 http://python.org/download/releases/2.6.2/license Quartz 1.5.2 Apache License, Version 2 http://www.apache.org/licenses/LICENSE-2.0 sudo 1.7.2p1 ISCL https://www.isc.org/software/license Xerces2 See JBoss. Apache License, Version 2 http://www.apache.org/licenses/LICENSE-2.0 OpenFire Apache License, Version 2 http://www.igniterealtime.
Polycom® DMA™ 7000 System Overview Third-Party Software Software Version License W3C XML Schema Test Collection v. 1.16.2 W3C SOFTWARE NOTICE AND LICENSE Mesa 3-D graphics library v. 5 The core Mesa library is licensed according to the terms of the XFree86copyright (an MIT-style license). The Mesa source code is licensed under SGI FREE SOFTWARE LICENSE B (Version 1.1 [02/22/2000]) Byte Code Engineering Library (BCEL) v. 5 Apache 1.1 Regexp Regular Expression Package v. 1.2 Apache 1.
DMA Operations Guide Software Version Third-Party Software License libpng official PNG reference library (general permissive license) Libungif - An uncompressed GIF library (general permissive license) Ant Apache 2.0 XML Resolver Library Apache 2.0 ICU4J ICU License NekoHTML Apache-like (1.1) Jing (general permissive) RelaxNGCC (general permissive) RELAX NG Object Model/ Parser MIT License XFree86VidMode Extension Version 1.
Polycom® DMA™ 7000 System Overview Third-Party Software Software Version License 7-Zip See file. Some files are LGPLv2.1; some have unRAR restriction; some are licensed under AES code license. UPX GPL LZMA Software Development Kit Common Public License (CPL) Polycom, Inc.
DMA Operations Guide 20 Third-Party Software Polycom, Inc.
2 Polycom® DMA™ System Initial Configuration Summary This chapter describes the configuration tasks required to complete your implementation of a new Polycom® 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.
DMA Operations Guide Add Required DNS Records for the Polycom DMA System Note These topics outline the configuration tasks that are generally required. You may wish to complete other optional configuration tasks, including: • Enable cascading of conferences (see “About Cascading” on page 182). • Configure calendaring service (“Microsoft Exchange Server Integration” on page 164).
Polycom® DMA™ System Initial Configuration Summary Add Required DNS Records for the Polycom DMA System Additional DNS Records for SIP Proxy To support the use of your Polycom DMA system as a SIP proxy server and ease future network administrative burdens, create the following DNS records (for each cluster in a supercluster, if applicable): • Optionally, NAPTR records that describe the transport protocols supported by the SIP proxies at a domain and identify the preferred protocol.
DMA Operations Guide License the Polycom DMA System Additional DNS Records for the Optional Embedded DNS Feature To support DNS publishing by your Polycom DMA system’s embedded DNS servers (see “Embedded DNS” on page 259), a DNS NS record is needed for each cluster in the supercluster. These records identify the Polycom DMA system’s embedded DNS servers as authoritative for the specified logical host name. Here are example records for two clusters: callservers.example.com. 86400 IN NS dma-asia.example.
Polycom® DMA™ System Initial Configuration Summary Set Up Signaling • Whether the RealPresence Platform Application Programming Interface (API) is enabled. The API provides an API client application with programmatic access to the Polycom DMA system (see “RealPresence Platform API” on page 2). In a supercluster, all clusters must have the same API licensing status. Note An API license isn’t required in order for a Polycom RealPresence Resource Manager system to access the API.
DMA Operations Guide Configure the Call Server and Optionally Create a Supercluster To configure signaling, follow the procedure in “Configure Signaling” on page 73.
Polycom® DMA™ System Initial Configuration Summary Set Up MCUs 1 As the default local administrative user (admin), create a local user account for yourself with the Administrator role, log in using that account, and delete the admin user account. See “Adding Users Overview” on page 293 and “Users Procedures” on page 313. 2 Create the Active Directory service account (read-only user account) that the Polycom DMA system will use to read and integrate with Active Directory.
DMA Operations Guide Set Up MCUs Make sure that each MCU is in a site belonging to a territory for which the Polycom DMA system is responsible. If you’re deploying a supercluster (see “Configure the Call Server and Optionally Create a Supercluster” on page 26 and “About Superclustering” on page 209), make sure that each territory has a primary and backup cluster assigned to it. If the primary cluster becomes unavailable, the MCUs registered to it can re-register to the backup.
Polycom® DMA™ System Initial Configuration Summary Set Up MCUs Both methods allow you to specify most conference parameters: • General information such as line rate, encryption, auto termination, and H.
DMA Operations Guide Connect to Microsoft Active Directory Connect to Microsoft Active Directory Connecting to Microsoft® Active Directory® simplifies the task of deploying conferencing to a large organization. All Polycom DMA system access to the Active Directory server is read-only and minimally impacts the directory performance. See “Microsoft Active Directory Integration” on page 147.
Polycom® DMA™ System Initial Configuration Summary Set Up Conference Templates Enterprise groups can have their own conference templates that provide a custom conferencing experience (see “Conference Templates” on page 179). They can also have their own MCU pool order, which preferentially routes conferences to certain MCUs (see “MCU Pool Orders” on page 141).
DMA Operations Guide Test the System Have some endpoints register with the Polycom DMA Call Server and make point-to-point calls to each other. On the Dashboard (see “Dashboard” on page 331), verify that: • The information in the Cluster Info pane looks correct, including the time, network settings, and system resource information.
3 System Security This chapter describes the following Polycom® 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.
DMA Operations Guide Security Certificates Overview • When a client connects to a server, the server shows its signed public certificate to the client. Trust is established because the certificate has been signed by the certificate authority, and the client has been configured to trust the certificate authority. Forms of Certificates Accepted by the Polycom DMA System X.509 certificates come in several forms (encoding and protocol).
Security Certificates Overview System Security How Certificates Are Used by the Polycom DMA System The Polycom DMA system uses X.509 certificates in the following ways: 1 When a user logs into the Polycom DMA system’s browser-based management interface, the Polycom DMA system (server) offers an X.509 certificate to identify itself to the browser (client). The Polycom DMA system’s certificate must have been signed by a certificate authority (see “Certificate Procedures” on page 40).
DMA Operations Guide Certificate Settings 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.
Certificate Settings System Security Table 3-1 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.
DMA Operations Guide Certificate Settings See also: “Security Certificates Overview” on page 33 “Certificate Information Dialog Box” on page 38 “Certificate Signing Request Dialog Box” on page 38 “Add Certificates Dialog Box” on page 39 “Certificate Details Dialog Box” on page 39 “Certificate Procedures” on page 40 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 i
Certificate Settings System Security The Encoded Request box below displays the encoded certificate request text, which you can select and copy. See also: “Security Certificates Overview” on page 33 “Certificate Settings” on page 36 “Certificate Procedures” on page 40 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.
DMA Operations Guide Certificate Procedures Table 3-4 Sections in the Certificate Details dialog box Section Description Certificate Info Purpose and alias of the certificate. Issued To Information about the entity to which the certificate was issued and the certificate serial number. Issued By Information about the issuer. Validity Issue and expiration dates. Fingerprints SHA1 and MD5 fingerprints (checksums) for confirming certificate.
Certificate Procedures System Security Note If you’re configuring the Polycom DMA system to support Polycom’s solution for the Microsoft OCS or Lync environment, you can use Microsoft’s Certificate Wizard to request and obtain a PFX file (a password-protected PKCS12 file containing a private key and public key for the system, and the CA’s certificate). Once you have the PFX file, you’re ready to install it.
DMA Operations Guide Certificate Procedures 4 In the Add Certificates dialog box, do one of the following: — If you have a file, click Upload certificate, enter the password (if any) for the file, and browse to the file or enter the path and file name. — If you have PEM-format text, copy the certificate text, click Paste certificate, and paste it into the text box below. 5 Click OK. 6 Verify that the certificate appears in the list as a Trusted Root CA.
Certificate Procedures System Security In the Certificate Information dialog box, enter the identifying information for your Polycom DMA system (see “Certificate Information Dialog Box” on page 38) and click OK. 4 The Certificate Signing Request dialog box displays the encoded request (see “Certificate Signing Request Dialog Box” on page 38).
DMA Operations Guide Certificate Procedures • PEM-format encoded text that you received in an email or on a secure web page. Caution Installing or removing certificates requires a system restart and terminates all active conferences. When you install or remove a certificate, the change is made to the certificate store immediately, but the system can’t implement the change until it restarts and reads the changed certificate store.
Certificate Procedures System Security See also: “Security Certificates Overview” on page 33 “Certificate Settings” on page 36 “Certificate Procedures” on page 40 Remove a Certificate from the DMA System There are two kinds of certificate removal: • Removing the certificate of a Trusted Root CA so that the system no longer trusts certificates signed by that certificate authority.
DMA Operations Guide Security Settings 7 Click Restart to Apply Saved Changes, and when asked to confirm that you want to restart the system so that certificate changes can take effect, click OK. To remove a signed certificate and revert to the default self-signed certificate 1 Go to Certificates. 2 In the Actions list, select Revert to Default Certificate. 3 When asked to confirm, click Yes. A dialog box informs you that the system has reverted to a self-signed certificate. 4 Click OK.
Security Settings System Security Caution 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 new 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 52).
DMA Operations Guide Security Settings Table 3-5 Fields on the Security Settings page (continued) Field Description Allow unencrypted connections to the Active Directory Normally, the Polycom 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 DMA system can only connect using an unencrypted protocol.
Security Settings System Security Table 3-5 Fields on the Security Settings page (continued) Field Description Allow basic authentication to Exchange server Normally, if calendaring is enabled, the Polycom DMA system authenticates itself with the Exchange server using NTLM authentication. If this option is selected, the Polycom DMA system still attempts to use NTLM first.
DMA Operations Guide Security Settings Table 3-5 Fields on the Security Settings page (continued) Field Description 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 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).
Security Settings System Security Table 3-5 Fields on the Security Settings page (continued) Field Description Disable enhanced support Enhanced support allows Polycom Global Services personnel to securely access the system when normal access methods aren’t possible. For example, enhanced support could allow support of a DMA system when console access is disabled and system errors prevent access to the management interface.
DMA Operations Guide The Consequences of Enabling Maximum Security Mode See also: “System Security” on page 33 “Certificate Settings” on page 36 “The Consequences of Enabling Maximum Security Mode” on page 52 “Login Policy Settings” on page 55 “Reset System Passwords” on page 59 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 Consequences of Enabling Maximum Security Mode System Security • On the Banner page, Enable login banner is selected and can’t be disabled. • On the Login Sessions page, the Terminate Session action is not available. • On the Troubleshooting Utilities menu, Top is removed. • In the Add User and Edit User dialog boxes, conference and chairperson passwords are obscured. • After Maximum security is enabled, users must change their passwords.
DMA Operations Guide The Consequences of Enabling Maximum Security Mode • Other configuration settings have stricter limits and constraints (each is set to the noted default if below that level when you enable Maximum security): — Session configuration limits: » Sessions per system is 4-80 (default is 40). » Sessions per user is 1-10 (default is 5). » Session timeout is 5-60 minutes (default is 10).
Login Policy Settings System Security The entire trust chain must be imported (the system’s signed certificate, intermediate certificates, if any, and the root CA’s certificate). When importing a certificate, let Internet Explorer automatically select a certificate store.
DMA Operations Guide Login Policy Settings Table 3-6 Fields on the Local Password Settings page Field Description Password Management Maximum password age (days) Specify at what age a password expires (30-180 days). Minimum password age (days) Specify how frequently a password can be changed (1-30 days). Minimum length Specify the number of characters a password must contain (8-30).
Login Policy Settings System Security Table 3-7 Fields on the Session Settings page 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.
DMA Operations Guide Login Policy Settings Table 3-8 Fields on the Local User Account page (continued) Field Description Customize user account lockout duration (minutes) If selected, specify how long the user’s account remains locked. If not selected, the lockout is indefinite, and a user with a locked account must contact an Administrator to unlock it.
Reset System Passwords System Security See also: “System Security” on page 33 “Login Policy Settings” on page 55 Reset System Passwords In an extremely high-security environment, security compliance policies may require that all passwords be changed at certain intervals, including operating system passwords. The Reset System Passwords page is available only if the system is in maximum security mode.
DMA Operations Guide 60 Reset System Passwords Polycom, Inc.
4 Local Cluster Configuration This chapter describes the following Polycom® Distributed Media Application™ (DMA™) 7000 system configuration topics: • Network Settings • Time Settings • Licenses • Signaling Settings • Logging Settings • Local Cluster Configuration Procedures These are cluster-specific settings that are not part of the data store shared across superclustered systems. See “Introduction to the Polycom DMA System” on page 1.
DMA Operations Guide Network Settings Network Settings The following table describes the fields on the Network Settings page. These values are normally set in the USB Configuration Utility during system installation and rarely need to be changed. See the Getting Started Guide. Caution Changing some network settings (host names, IP addresses, or domains) requires a system restart and terminates all active conferences.
Network Settings Local Cluster Configuration Table 4-1 Fields on the Network Settings page (continued) Field Description Server 1 Status, host name, and IP address(es) of the primary server. The IP type and network setting determine which of the IP fields in this section are enabled. Host names may contain only letters, numbers, and internal dashes (hyphens), and may not include a domain. The reserved values appserv* and dmamgk-* may not be used for host names.
DMA Operations Guide Network Settings Table 4-1 Fields on the Network Settings page (continued) Field Description Shared Signaling Network Settings The settings in this section are enabled only if management and signaling traffic are on separate networks. If so, they apply to the entire system (both servers in two-server configuration). The settings are the same as those in Shared Management Network Settings, except that under Signaling Link, the signaling network interface (eth2) can be disabled.
Network Settings Local Cluster Configuration See also: “Local Cluster Configuration” on page 61 “Routing Configuration Dialog Box” on page 65 “Local Cluster Configuration Procedures” on page 71 Routing Configuration Dialog Box In the Network page’s action list, the Routing Configuration command opens the Routing Configuration dialog box, where you can add or delete network routing rules (IPv4, IPv6, or both, depending on the System IP type setting on the Network page).
DMA Operations Guide Time Settings See also: “Network Settings” on page 62 Time Settings The following table describes the fields on the Time Settings page. These values are normally set in the USB Configuration Utility during system installation and rarely need to be changed. See the Getting Started Guide. Caution Changing time settings requires a system restart and terminates all active conferences.
Licenses Local Cluster Configuration Licenses The Polycom DMA system is licensed for the number of concurrent calls it can handle and optionally for API access. See “License the Polycom DMA System” on page 24 for more information about licensing. The following table describes the fields on the Licenses page. Table 4-4 Fields on the Licenses page Field Description Active License Licensed calls The maximum number of concurrent calls that the license enables.
DMA Operations Guide Signaling Settings Either H.323 signaling, SIP signaling, or both must be enabled in order for the Polycom DMA system’s Conference Manager to receive calls for multipoint conferences (virtual meeting rooms, or VMRs) and distribute them among its pool of MCUs. XMPP Signaling If XMPP signaling is enabled, the Polycom DMA system’s Call Server operates as an XMPP server, providing chat and presence services to the XMPP clients that log into it.
Signaling Settings Local Cluster Configuration Table 4-5 Fields on the Signaling Settings page (continued) Field Description H.323 multicast Enables the system to support gatekeeper discovery (GRQ messages from endpoints) as described in the H.323 and H.225.0 specifications. SIP Settings Enable SIP signaling Enables the system to receive Session Initiation Protocol (SIP) calls. Caution: Disabling SIP terminates any existing SIP calls. When you click Update, the system prompts you to confirm.
DMA Operations Guide Logging Settings See also: “Local Cluster Configuration” on page 61 “Local Cluster Configuration Procedures” on page 71 Logging Settings The following table describes the fields on the Logging Settings page. Table 4-6 Fields on the Logging Settings page Field Description Logging level Leave the default, Production, unless advised to change it by Polycom support. Debug is useful for troubleshooting. Verbose debug is not recommended for production systems.
Local Cluster Configuration Procedures Local Cluster Configuration See also: “Local Cluster Configuration” on page 61 “Local Cluster Configuration Procedures” on page 71 Local Cluster Configuration Procedures This section describes the following Polycom DMA 7000 system configuration procedures: • Add Licenses • Configure Signaling • Configure Logging If you’re performing the initial configuration of your Polycom DMA system, study “Polycom® DMA™ System Initial Configuration Summary” on page 21 befor
DMA Operations Guide Local Cluster Configuration Procedures 9 When the activation key for the first (or only) server appears, record it: Server A: __________-__________-_________-___________ 10 If you have a single-server Polycom DMA system, you’re finished with this procedure. Continue to the next procedure. 11 If you have a two-server cluster, repeat steps 6–8, this time entering the second license number you received and the second server’s serial number (also recorded in step 2).
Local Cluster Configuration Procedures Local Cluster Configuration Configure Signaling To configure signaling 1 Go to Admin > Local Cluster > Signaling Settings. 2 To make the system accessible via H.323 calls: 3 a Select Enable H.323 signaling. b Leave the default port numbers (1720 for H.225, 1719 for RAS) unless you have a good reason for changing them. c Select H.323 multicast to support gatekeeper discovery messages from endpoints.
DMA Operations Guide Local Cluster Configuration Procedures 6 Click OK. The system processes the configuration. The Status field shows the current H.323 signaling state. See also: “Signaling Settings” on page 67 Configure Logging To configure logging 1 Go to Admin > Local Cluster > Logging Settings. 2 Change Rolling frequency and Retention period as desired. 3 If requested to do so by Polycom support, change Logging level. 4 Click Update.
5 Device Management This chapter describes the following Polycom® 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 SBC Other Network menu topics are addressed in the following chapters: • “Superclustering” on page 209 (DMAs) • “MCU Management” on page 119 • “Site Topology” on page 263 Active Calls The Active Calls page lets you moni
DMA Operations Guide Active Calls Note Specifying a filter that includes too many active calls can be a drain on system resources. The calls that match your search criteria (up to 500) appear in the lower list. You can pin a call that you want to study. This moves it to the upper list, and it remains there, even after the call ends, until you unpin it. Details about the selected call are available in the Call Info, Originator, Destination, and Bandwidth tabs of the pane on the right.
Active Calls Device Management Call Details Dialog Box The Call Details dialog box appears when you click Show Call Details on the Active Calls page or Call History page. It provides detailed information about the selected call. The following table describes the fields in the dialog box.
DMA Operations Guide Active Calls Table 5-2 Call Details dialog box (continued) Tab/Field/Column Description Bandwidth 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.
Endpoints Device Management See also: “Active Calls” on page 75 Endpoints The Endpoints page provides access to information about the devices known to the Polycom DMA system. From it, you can: • View details about a device. • View the call history or registration history of a device. • Add aliases for a device, edit or delete added aliases (but not aliases with which the device registered), and configure the class of service settings. • Block a device, which prevents it from registering.
DMA Operations Guide Endpoints 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.
Endpoints Device Management Table 5-3 Information in the Endpoints list (continued) Column Description 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 221) and. It can register again. • Quarantined — The device is registered, but it can’t make or receive calls.
DMA Operations Guide Endpoints The Actions list associated with the Endpoints list contains the items in the following table. Table 5-4 Endpoint commands Command Description View Details Opens the Device Details dialog box for the selected endpoint. Add Opens the Add Device dialog box, where you can manually add a device to the system. Edit Opens the Edit Device dialog box for the selected endpoint, where you can change its information and settings.
Endpoints Device Management Names/Aliases in a Mixed H.323 and SIP Environment An endpoint that supports both H.323 and SIP can register with the Polycom DMA system’s gatekeeper and SIP registrar using the same name/alias. When the Polycom DMA system receives a call for that endpoint, it uses the protocol of the calling endpoint.
DMA Operations Guide Endpoints Note The Polycom DMA system’s ability to recognize ITP calls and treat them as one assures the same class of service and device authentication settings for all the endpoints in the ITP system, but not other registration settings. It’s up to you to ensure that the maximum and minimum bit rates and other registration settings are consistent. This capability also doesn’t ensure the availability of sufficient MCU ports for all the endpoints (codecs) in the ITP system.
Endpoints Device Management Table 5-5 Add Device dialog box Field Description Device type The device’s signaling protocol (H.323 or SIP). Signaling address For an H.323 device, the H.225 call signaling address (and optionally, port) of the device. Either this or the RAS address is required. RAS address For an H.323 device, the RAS (Registration, Admission and Status) channel address (and optionally, port) of the device. Aliases For an H.323 device, lists the device’s aliases.
DMA Operations Guide Endpoints 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. Table 5-6 Edit Device dialog box Field Description Device type The device’s signaling protocol (H.323 or SIP). Signaling address For an H.323 device, the H.
Endpoints Device Management Table 5-6 Edit Device dialog box (continued) 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.
DMA Operations Guide Endpoints Table 5-7 Edit Device dialog box (continued) Field Description Class of service Select to modify the class of service and the bit rate limits for calls to and from the selected devices. A call between two devices receives the higher class of service of the two. Maximum bit rate (kbps) The maximum bit rate for calls to and from the selected devices.
Site Statistics Device Management Associate User Dialog Box Note If the Polycom DMA system is integrated with a Polycom RealPresence Resource Manager or CMA system, it receives user-to-device association information from that system, and you can only associate users with devices on the Polycom RealPresence Resource Manager or CMA system. The Associate User dialog box lets you associate the selected device with a user.
DMA Operations Guide Site Link Statistics Table 5-8 Information in the Site Statistics list (continued) Column Description 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. Cluster Cluster responsible for the territory to which the site belongs.
External Gatekeeper Device Management Table 5-9 Information in the Site Link Statistics list (continued) Column Description Avg Delay (msec) Average delay rate of the active calls. Territory Territory to which the site belongs. Cluster Cluster responsible for the territory to which the site belongs. See also: “Device Management” on page 75 “Site Links” on page 279 External Gatekeeper On the External Gatekeeper page, you can add or remove neighbor gatekeepers.
DMA Operations Guide External Gatekeeper The following table describes the fields in the list. Table 5-10 Fields in the External Gatekeeper list 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.
External Gatekeeper Device Management Table 5-11 Add External Gatekeeper dialog box Column Description 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).
DMA Operations Guide External Gatekeeper Table 5-11 Add External Gatekeeper dialog box Column Description Postliminary A postliminary is an executable script, written in the Javascript language, that defines dial string transformations to be applied before querying the external gatekeeper. Enabled Lets you turn a postliminary on or off without deleting it. Script Type (or paste) the postliminary script you want to apply.
External Gatekeeper Device Management Table 5-12 Edit External Gatekeeper dialog box Column Description 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).
DMA Operations Guide External SIP Peer Table 5-12 Edit External Gatekeeper dialog box Column Description Postliminary A postliminary is an executable script, written in the Javascript language, that defines dial string transformations to be applied before querying the external gatekeeper. Enabled Lets you turn a postliminary on or off without deleting it. Script Type (or paste) the postliminary script you want to apply.
External SIP Peer Device Management Table 5-13 Fields in the External SIP Peer list (continued) Column Description Prefix Range The dial string prefix(es) assigned to this peer server. 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 peer server for resolution. Enabled Indicates whether the system is using the peer server.
DMA Operations Guide External SIP Peer Table 5-14 Add External SIP Peer dialog box Field Description Destination network Host name, FQDN, or network domain label of the peer server, with or without port and URL parameters. If specified, this value by default replaces the non-user portion of a URL (after the @ symbol) of the To header and Request-URI for forwarded messages, and just the Request-URI for REGISTER messages.
External SIP Peer Device Management Table 5-14 Add External SIP Peer dialog box Field Description Type For a Microsoft Office Communications Server or Lync Server 2010, select Microsoft. Otherwise, select Other. Selecting Microsoft implicitly adds the Destination network value to the Domain List (if not already there) and automatically selects the Postliminary settings that are correct for most deployments with Lync Server 2010, but you can modify them if necessary.
DMA Operations Guide External SIP Peer Table 5-14 Add External SIP Peer dialog box 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.
External SIP Peer Device Management Table 5-14 Add External SIP Peer dialog box 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.
DMA Operations Guide External SIP Peer See also: “External SIP Peer” on page 96 “SIP Peer Postliminary Output Format Options” on page 107 “Device Authentication” on page 243 “Add Authentication Dialog Box” on page 111 “Edit Authentication Dialog Box” on page 111 “Add Outbound Registration Dialog Box” on page 112 “Edit Outbound Registration Dialog Box” on page 113 “Script Debugging Dialog Box for Preliminaries/Postliminaries” on page 235 Edit External SIP Peer Dialog Box The following table describes the
External SIP Peer Device Management Table 5-15 Edit External SIP Peer dialog box 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. If left blank, the system uses the full RFC 3263 procedure to determine the port via DNS. Use route header Add a Route header with the peer’s Next hop address value to the message. Applies to both forwarded messages and external REGISTER messages.
DMA Operations Guide External SIP Peer Table 5-15 Edit External SIP Peer dialog box 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. Register externally Some external SIP peers require peers to register with them as an endpoint does, using a REGISTER message.
External SIP Peer Device Management Table 5-15 Edit External SIP Peer dialog box Field Description Copy all parameters of original “To” headers Copies any parameters included in the original To header to the To header sent to this peer. This setting applies to all format options. Format Select a predefined format from the list, or select Free Form Template and define the format in the associated Template field.
DMA Operations Guide External SIP Peer Table 5-15 Edit External SIP Peer dialog box 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).
External SIP Peer Device Management SIP Peer Postliminary Output Format Options This section includes the following information to help with the postliminary settings for an external SIP peer: • To Header Format Options • Request-URI Format Options • Free Form Template Variables • To Header and Request-URI Examples To Header Format Options The settings available on the Format list for the To header are described below.
DMA Operations Guide External SIP Peer Request-URI Format Options The settings available on the Format list for the Request-URI are described below (RR= requires route header): Use original request’s URI (RR) — The original request’s URI is copied and moved. Equivalent to template: #orscheme#:#oruser#@#orhost# No user, original request’s host (RR) — The user in the original, if any, is removed, but the original host is used.
External SIP Peer Device Management Free Form Template Variables In the Template fields on the Postliminary tab, and when specifying a Request-URI or other headers for outbound registration (see “Add Outbound Registration Dialog Box” on page 112), you can use the variables in the table below entered as #variable name# (case insensitive). The system replaces the variables with the corresponding values as shown below. You can also use these variables (without # delimiters) in a customized script.
DMA Operations Guide External SIP Peer To Header and Request-URI Examples The tables below show some examples of To header and Request-URI transformations using the variables described in “Free Form Template Variables” on page 109. Table 5-17 To header examples Original 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.
External SIP Peer Device Management Add Authentication Dialog Box The Add Authentication dialog box lets you add an authentication credential entry either for a specific external SIP peer (see “Edit External SIP Peer Dialog Box” on page 102) or to the general list of outbound authentication credentials that the system uses if challenged by an external device (see “Device Authentication” on page 243). The following table describes the fields in the dialog box.
DMA Operations Guide External SIP Peer See also: “External SIP Peer” on page 96 “Add External SIP Peer Dialog Box” on page 97 “Edit External SIP Peer Dialog Box” on page 102 Add Outbound Registration Dialog Box Some external SIP peers require peers to register with them as an endpoint does, using a REGISTER message (also known as pilot registration).
External SIP Peer Device Management Table 5-21 Add Outbound Registration dialog box Field Description Password The password to use for the authentication credentials if the external peer challenges the registration request. Confirm password Request-URI The Request-URI to include when registering with this SIP peer, specified using the variables (#delimited) defined in “Free Form Template Variables” on page 109. Other headers Additional headers to include when registering with this SIP peer.
DMA Operations Guide External SBC Table 5-22 Edit Outbound Registration dialog box Field Description Contact address format Select IP or DNS to specify that the contact header should use the virtual IP address or virtual DNS name of the cluster currently managing the territory. If the territory responsibility switches to the other cluster, it re-sends the registration using its IP address or DNS name. Select Free Form to specify that the contact header should use the FQDN you enter.
External SBC Device Management Note This page is only for H.323 SBCs. SIP SBCs are configured as SIP peers. See “External SIP Peer” on page 96. For most configurations, H.323 SBCs should be configured on a per site basis on the Sites page. There are three reasons to configure an H.323 SBC on the External SBC page: • To create a prefix service that allows dialing through the specific SBC by prefix. • To define a postliminary script to be applied when dialing through the SBC.
DMA Operations Guide External SBC See also: “Device Management” on page 75 “Add External SBC Dialog Box” on page 116 “Edit External SBC Dialog Box” on page 117 Add External SBC Dialog Box The following table describes the fields in the Add External SBC dialog box. Table 5-24 Add External SBC dialog box Column Description External SBC Enabled Clearing this check box lets you stop using an external SBC without deleting it. Name SBC unit name.
External SBC Device Management Table 5-24 Add External SBC dialog box Column Description Postliminary A postliminary is an executable script, written in the Javascript language, that defines dial string transformations to be applied before querying the external SBC. Enabled Lets you turn a postliminary on or off without deleting it. Script Type (or paste) the postliminary script you want to apply.
DMA Operations Guide External SBC Table 5-25 Edit External SBC dialog box Column Description Prefix range The dial string prefix or prefix range for which the external SBC is responsible. Enter a single prefix (44), a range of prefixes (44-47), or multiple prefixes separated by commas (44,46) 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 SBC for resolution.
6 MCU Management This chapter describes the Polycom® Distributed Media Application™ (DMA™) 7000 system’s MCU management tools and tasks: • MCUs • MCU Pools • MCU Pool Orders Note MCU pools were called MCU zones in earlier versions of the Polycom DMA system. The name was changed to avoid confusion with the concept of gatekeeper zones. MCUs The MCUs page shows the MCUs, or media servers, known to the Polycom DMA system.
DMA Operations Guide MCUs 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. Every conference room (VMR) is associated with an MCU pool order. The pool(s) to which an MCU belongs, and the pool order(s) to which a pool belongs, are used to determine which MCU is used to host a conference.
MCUs MCU Management Note The Polycom 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.
DMA Operations Guide MCUs Table 6-1 Information in the MCU list Column Description Signaling Type The type of signaling for which the MCU is configured: H.323, SIP, or both. Ports Reserved The number of video and voice ports on the MCU that are reserved for the Polycom CMA system and therefore off-limits to the Polycom DMA system. Applies only to MCUs that are enabled for conference rooms (available as a conferencing resource for the Polycom DMA system’s Conference Manager).
MCUs MCU Management Table 6-1 Information in the MCU list Column Description Exceptions Shows any exceptions with which the device was flagged as a result of applying a registration policy. MCU Pools The MCU pools in which this MCU is used, if it’s enabled for conference rooms (available as a conferencing resource for the Polycom DMA system’s Conference Manager). Site The site in which the MCU is located. See “Sites” on page 265.
DMA Operations Guide MCUs Table 6-2 MCU commands Command Description Busy Out Stops the Polycom DMA system from creating new conferences on the selected MCUs, but allows existing conferences to continue and accepts new calls to those conferences. A dialog box asks you to confirm. If any of the MCUs are ISDN gateways, the system stops using them for simplified gateway dialing. This gracefully winds down the system’s use of the MCU as a conferencing resource.
MCUs MCU Management “MCU Procedures” on page 134 “MCU Pools” on page 137 “MCU Pool Orders” on page 141 Add MCU Dialog Box Lets you add an MCU, gateway, or combination of the two to the pool of devices available to the Polycom DMA system. Note The Polycom 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.
DMA Operations Guide MCUs Table 6-3 Add MCU dialog box Field Description Video ports reserved for CMA system The number of video ports on this MCU that are off-limits to the Polycom DMA system. Set this to the number of ports you want to reserve for your Polycom CMA system to use for scheduled conferences (requires RMX v6.0 or later). Note: This feature is not for use with a Polycom RealPresence Resource Manager system.
MCUs MCU Management Table 6-3 Add MCU dialog box Field Description Enable for conference rooms Makes the MCU available as a conferencing resource for the Polycom DMA system’s Conference Manager. Up to 64 MCUs can be enabled for conference rooms. Caution: Before adding an MCU to the DMA system’s conferencing resources, make sure that MCU isn’t already a RealPresence Resource Manager system conferencing resource.
DMA Operations Guide MCUs Table 6-3 Add MCU dialog box Field Description Session Profile table Lists the defined session profile prefixes. A session profile prefix is a numeric dial string prefix that specifies a bit rate for the call and which protocols it supports. Click Add to add a session profile. Click Edit or Delete to change or delete the selected profile. You can’t change or delete session profiles that the MCU/gateway registered with, only those that you added.
MCUs MCU Management Note The Polycom 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.
DMA Operations Guide MCUs Table 6-4 Edit MCU dialog box Field Description Voice ports reserved for CMA system The number of voice ports on this MCU that are off-limits to the Polycom DMA system. Set this to the number of ports you want to reserve for your Polycom CMA system to use for scheduled conferences (requires RMX v6.0 or later). Note: This feature is not for use with a Polycom RealPresence Resource Manager system.
MCUs MCU Management Table 6-4 Edit MCU dialog box Field Description Enable gateway profiles Makes the MCU available as an ISDN gateway device and enables the Gateway Profiles tab for configuring the gateway. The process by which the system selects an ISDN gateway for a call is described in “ISDN Gateway Selection Process” on page 133. Class of service Select to specify the default class of service and the bit rate limits for this MCU.
DMA Operations Guide MCUs Table 6-4 Edit MCU dialog box Field Description Postliminary A postliminary is an executable script, written in the Javascript language, that defines dial transformations to be applied before routing the call to the MCU/gateway. Enabled Lets you turn a postliminary on or off without deleting it. Script Type (or paste) the postliminary script you want to apply.
MCUs MCU Management Edit Session Profile Dialog Box Lets you edit the selected session profile. You can’t edit session profiles that the MCU/gateway registered with, only those that you added. The following table describes the fields in the dialog box. Table 6-6 Add Session Profile dialog box Field Description Session profile Numeric dial string prefix for this profile. Bit rate Bit rate of calls using this profile. H.320 Select the protocol(s) for this profile. PSTN Only H.
DMA Operations Guide MCUs 8 If the call fails because of no capacity on the selected gateway, select the next gateway left in 7. If none, start again at 1 (omitting the gateway that failed). If none left, reject the call. MCU Procedures Note See all the notes in “MCUs” on page 119. To view information about an MCU 1 Go to Network > MCU > MCUs. The MCUs list appears. 2 In the list, select the MCU and in the Actions list, click View Details.
MCUs MCU Management 6 Click OK. The new MCU appears in the MCUs list. If the MCU is configured as a conferencing resource, it’s placed into service. 7 If the MCU is configured as a conferencing resource, add it to the desired MCU pool(s). See “MCU Pools” on page 137. The pool(s) to which the MCU belongs, and the pool order(s) to which a pool belongs, are used to determine which MCU is used for a conference. See “MCU Pool Orders” on page 141.
DMA Operations Guide MCUs 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 137. The pool(s) to which the MCU belongs, and the pool order(s) to which a pool belongs, are used to determine which MCU is used for a conference. See “MCU Pool Orders” on page 141. 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 Pools MCU Management to those conferences. It also excludes these MCUs from consideration for simplified ISDN dialing calls. This has no effect on the MCUs themselves, which continue to accept any calls from other sources. To start using one or more MCUs for conferencing and simplified ISDN dialing again 1 Go to Network > MCU > MCUs. 2 In the MCUs list, select the out-of-service MCUs of interest. 3 In the Actions list, select Start Using.
DMA Operations Guide MCU Pools Note If you have a Polycom RealPresence Resource Manager system that uses the DMA system API to schedule conferences on the DMA system’s conferencing resources (MCU pools), you must create MCU pools and pool orders specifically for the use of the RealPresence Resource Manager system. The pool orders should be named in such a way that: • They appear at the top of the pool order list presented in the RealPresence Resource Manager system.
MCU Pools MCU Management Table 6-8 MCU Pools commands Command Description Add Opens the Add MCU Pool dialog box, where you can define a new pool. Edit Opens the Edit MCU Pool dialog box for the selected pool, where you can change its name, description, and the MCUs it includes. Delete Removes the selected MCU pool from the list of pools that are available. A dialog box informs you of the effect on pool orders and asks you to confirm.
DMA Operations Guide MCU Pools Table 6-10 Edit MCU Pool dialog box 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 DMA system. Selected MCUs Lists the MCUs included in the pool. The arrow buttons move MCUs from one list to the other.
MCU Pool Orders MCU Management Click OK. 4 The changes you made appear in the MCU Pools list. To delete an MCU Pool 1 Go to Network > MCU > MCU Pools. 2 In the MCU Pools list, select the MCU pool you want to remove. 3 In the Actions list, select Delete. If the pool is included in one or more pool orders, the system warns you and provides information about the consequences of deleting it. When asked to confirm that you want to delete the selected MCU pool, click Yes.
DMA Operations Guide MCU Pool Orders Note If you have a Polycom RealPresence Resource Manager system that uses the DMA system API to schedule conferences on the DMA system’s conferencing resources (MCU pools), you must create MCU pools and pool orders specifically for the use of the RealPresence Resource Manager system. The pool orders should be named in such a way that: • They appear at the top of the pool order list presented in the RealPresence Resource Manager system.
MCU Pool Orders MCU Management Table 6-11 Information in the MCU Pool Orders list Column Description Priority Priority ranking of the pool order. Name Name of the pool order. Description Brief description of the pool order. 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.
DMA Operations Guide MCU Pool Orders Table 6-13 Add MCU Pool Order 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 system. Selected MCU pools Lists the pools included in the pool order in their priority order. The left/right arrow buttons move pools in and out of the list. The up/down arrow buttons change the priority rankings of the pools.
MCU Pool Orders MCU Management MCU Pool Order Procedures To view the MCU Pool Orders list >> Go to Network > MCU > MCU Pool Orders. The MCU Pool Orders list appears. To add an MCU Pool Order 1 Go to Network > MCU > MCU Pool Orders. 2 In the Actions list, click Add. 3 In the Add MCU Pool dialog box, complete editable fields. All are mandatory. See “Add MCU Pool Dialog Box” on page 139. 4 Click OK. The new MCU pool order appears in the MCU Pool Orders list.
DMA Operations Guide 146 MCU Pool Orders Polycom, Inc.
7 Integrations with Other Systems This chapter describes the following Polycom® Distributed Media Application™ (DMA™) 7000 system configuration topics related to integrating the system with external systems: • Microsoft Active Directory Integration • Microsoft Exchange Server Integration • Resource Management System Integration • Juniper Networks SRC Integration Microsoft Active Directory Integration When you integrate the Polycom DMA system with your Microsoft Active Directory, the enterprise user
DMA Operations Guide Microsoft Active Directory Integration Note Polycom Implementation and Maintenance services provide support for Polycom solution components only. Additional services for supported third-party Unified Communications (UC) environments integrated with Polycom solutions are available from Polycom Global Services, and its certified Partners, to help customers successfully design, deploy, optimize, and manage Polycom visual communication within their third-party UC environments.
Microsoft Active Directory Integration Integrations with Other Systems Microsoft Active Directory Page The following table describes the fields on the Microsoft Active Directory page. Table 7-1 Fields on the Microsoft Active Directory page Field Description Enable integration with Microsoft Active Directory® Server Enables the Active Directory integration fields and the Update button, which initiates a connection to the Microsoft Active Directory.
DMA Operations Guide Microsoft Active Directory Integration Table 7-1 Fields on the Microsoft Active Directory page (continued) 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.
Microsoft Active Directory Integration Integrations with Other Systems Table 7-1 Fields on the Microsoft Active Directory page (continued) Field Description Domain\user name LDAP service account user ID for system access to the Active Directory. Must be set up in the Active Directory, but should not have Windows login privileges.
DMA Operations Guide Microsoft Active Directory Integration Table 7-1 Fields on the Microsoft Active Directory page (continued) Field Description Enterprise Conference Room ID Generation Directory attribute The name of the Active Directory attribute from which the Polycom DMA system should derive conference room IDs (virtual meeting room numbers). Generally, organizations use a phone number field for this.
Microsoft Active Directory Integration Integrations with Other Systems Table 7-1 Fields on the Microsoft Active Directory page (continued) 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.
DMA Operations Guide Microsoft Active Directory Integration Note 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 DMA system have different requirements. Don’t try to use the same account for both purposes.
Microsoft Active Directory Integration Integrations with Other Systems a Specify the Active Directory attribute from which to generate room IDs. Your users will be happier if room IDs are numeric and not longer than necessary to ensure uniqueness. Phone numbers are the most likely choice, or maybe employee ID numbers. b If necessary, edit the contents of the Characters to remove field. If you use phone numbers, the default contents of this field should be adequate to ensure a numeric room ID.
DMA Operations Guide Microsoft Active Directory Integration Caution Leaving user roles assigned to the service account represents a serious security risk. For best security, remove all user roles so that this account can’t be used for logging into the Polycom DMA system management interface.
Microsoft Active Directory Integration Integrations with Other Systems Understanding Base DN The Base DN field is where you can specify the distinguished name (DN) of a subset of the Active Directory hierarchy (a domain, subset of domains, or organizational unit) to which you want to restrict the Polycom DMA system. It acts like a filter. The diagram below illustrates how choosing different Base DN values affects which parts of a forest are included in the directory integration. nwind.com (0) nwind.
DMA Operations Guide Microsoft Active Directory Integration After the system has successfully connected to the Active Directory, the list contains entries for each domain in the AD forest. If you want to restrict the system to a subset of the Active Directory (such as one tree of multiple trees, a subtree, a domain, or an organizational unit), select the corresponding base DN entry from the list.
Microsoft Active Directory Integration Integrations with Other Systems When you generate passcodes for enterprise users, the Polycom DMA system retrieves the values in the designated Active Directory attributes and removes any non-numeric characters from them. If the resulting numeric passcode is longer than the maximum for that passcode type, it strips the excess characters from the beginning of the string.
DMA Operations Guide Microsoft Active Directory Integration Note Unless users have already been provisioned with passcodes in your Active Directory or you’re using an existing attribute, most users will probably not have passcodes assigned. Duplicate and invalid passcodes should be your main concern because they could indicate a problem with the type of data in the selected attributes or with the number of characters you elected to use.
Microsoft Active Directory Integration Integrations with Other Systems 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 157. • Filter: (&(objectCategory=person)(UserAccountControl: 1.2.840.113556.1.4.803:=512)(sAMAccountName=*) (!(userAccountControl:1.2.840.113556.1.4.
DMA Operations Guide Microsoft Active Directory Integration Global Group Membership Search This search queries LDAP. • 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 157.
Microsoft Active Directory Integration Integrations with Other Systems • Attributes returned: lDAPDisplayName, isMemberOfPartialAttributeSet Configurable Attribute Domain Search This search queries LDAP. The system runs this query only if the Attribute Replication Search determined that one or more of the configurable Active Directory attributes that it needs to retrieve (for generating conference room IDs, chairperson passcodes, and conference passcodes) isn’t in the global catalog.
DMA Operations Guide Microsoft Exchange Server Integration • 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 157. • Filter: (&(objectCategory=person)(UserAccountControl: 1.2.840.113556.1.4.803:=512)(sAMAccountName=*) (&(!(userAccountControl:1.2.840.113556.1.4.
Microsoft Exchange Server Integration Integrations with Other Systems Note Polycom Implementation and Maintenance services provide support for Polycom solution components only. Additional services for supported third-party Unified Communications (UC) environments integrated with Polycom solutions are available from Polycom Global Services, and its certified Partners, to help customers successfully design, deploy, optimize, and manage Polycom visual communication within their third-party UC environments.
DMA Operations Guide Microsoft Exchange Server Integration Note Calendaring is not the same as scheduling. Using the Polycom Conferencing Add-in for Microsoft Outlook to set up a meeting appointment doesn’t reserve video resources, and invitations aren’t declined due to lack of resources. The Polycom DMA system supports the use of Cisco Codian 4200, 4500, and MSE 8000 series MCUs as part of its conferencing resource pool.
Microsoft Exchange Server Integration Integrations with Other Systems Table 7-2 Fields on the Microsoft Exchange Server page (continued) Field Description Password The password for the Polycom Conferencing user ID. Territory Select a territory, thereby determining which Polycom DMA cluster is responsible for integrating with the Exchange server and monitoring the Polycom Conferencing infrastructure mailbox. See “Territories” on page 282 for more information.
DMA Operations Guide Microsoft Exchange Server Integration Caution Create a dedicated Polycom Conferencing mailbox that’s used specifically and exclusively for the purpose of receiving Polycom Conferencing meeting invitations. This is important because the Polycom DMA system will delete all messages from the Inbox when it checks this mailbox for meeting invitations. When creating the user ID for the system, be sure to specify the same domain used to integrate with the Active Directory.
Resource Management System Integration Integrations with Other Systems Resource Management System Integration Integrating with a resource management system (either a Polycom RealPresence Resource Manager system or a Polycom CMA system) provides the Polycom DMA system with: • All site topology information configured in the RealPresence Resource Manager or CMA system. • All user-to-device associations configured in the RealPresence Resource Manager or CMA system.
DMA Operations Guide Resource Management System Integration 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. Note RealPresence Resource Manager or CMA integration is not supported in Maximum security mode. See “The Consequences of Enabling Maximum Security Mode” on page 52.
Resource Management System Integration Integrations with Other Systems The list on this page displays information about the Polycom RealPresence Resource Manager or CMA system. The following table describes the fields in the list. Table 7-3 Fields in the Resource Management System list Field Description Host name Name of the system. IP Address IP address of the system. Model Type of system. Version Software version of the system.
DMA Operations Guide Resource Management System Integration The following table describes the fields in the dialog box. Table 7-4 Fields in the Join Resource Management System dialog box Field Description Host name or IP address The Polycom RealPresence Resource Manager or CMA system with which to integrate. User name Administrative user ID with which the Polycom DMA system can log into the Polycom RealPresence Resource Manager or CMA system. Password Password for the administrative user ID.
Juniper Networks SRC Integration Integrations with Other Systems 4 When asked to confirm that you want to join, click Yes. The system connects to the Polycom RealPresence Resource Manager or CMA system, establishes the integration, and obtains site topology and user-to-device association data (this may take a few minutes). A dialog box informs you when the process is complete. 5 On the Resource Management System page, verify the integration information.
DMA Operations Guide Juniper Networks SRC Integration In addition, the DMA system’s priority-based QoS packet marking (Gold/Silver/Bronze class of service) is applied by the Juniper SRC system throughout the network it controls. See also: “Integrations with Other Systems” on page 147 “Juniper Networks SRC Page” on page 174 “Juniper Networks SRC Integration Procedure” on page 175 Juniper Networks SRC Page The following table describes the fields on the Juniper Networks SRC page.
Juniper Networks SRC Integration Integrations with Other Systems Juniper Networks SRC Integration Procedure To configure SRC integration 1 Go to Admin > Integrations > Juniper Networks SRC. 2 Check Enable integration with Juniper Networks® SRC and specify the address of the SRC server. 3 Specify the login credentials for the system to connect to the SRC server. 4 Specify the subscriber URI of an endpoint known to the SRC server, specified as in this example: ip:ipAddress=192.168.70.
DMA Operations Guide 176 Juniper Networks SRC Integration Polycom, Inc.
8 Conference Manager Configuration This chapter describes the following Polycom® Distributed Media Application™ (DMA™) 7000 system configuration topics related to the Conference Manager functionality: • Conference Settings • Conference Templates • 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 DMA system.
DMA Operations Guide Conference Settings Table 8-1 Fields on the Conference Settings page (continued) Field Dialing prefix Description E.164 dial string prefix for calling the system. 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.
Conference Templates Conference Manager Configuration Click Update. 3 See also: “Conference Templates” on page 179 “Shared Number Dialing” on page 204 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.
DMA Operations Guide Conference Templates • If a conference with encryption enabled is forced to land on an MCU that doesn’t support encryption, that property is ignored. To preferentially route conferences to certain MCUs, use MCU pool orders. See “MCU Pools” on page 137 and “MCU Pool Orders” on page 141. Templates Linked to RMX Profiles Linking a template to an RMX profile lets you access profile properties that aren’t currently available in a standalone template.
Conference Templates Conference Manager Configuration Template Priority A user (local or enterprise) has one or more conference rooms. Each room may either use the system’s default template (specified on the Conference Settings page) or use a specifically assigned template. (Typically, most conference rooms use the default template.) An enterprise user can be associated with multiple enterprise groups, and each group may or may not have a specifically assigned template.
DMA Operations Guide Conference Templates On the Conference IVR tab of the Add Conference Template and Edit Conference Template dialog boxes, the list contains the names of all the conference IVR services available on the currently connected MCUs. If an IVR service is only available on some of the connected MCUs, its entry shows how many of the MCUs have that IVR service (for instance, 2 of 3).
Conference Templates Conference Manager Configuration On the Polycom DMA system, enable cascading in some or all of your conference templates. 3 If you don’t have a Polycom RealPresence Resource Manager or CMA system, you must define your site topology in the Polycom DMA system instead of importing it. See “Site Topology” on page 263. Note Cascading always uses a hub-and-spoke configuration so that each cascaded MCU is only one link away from the “hub” MCU, which hosts the conference.
DMA Operations Guide Conference Templates The Polycom DMA system comes with a Factory Template that has a default set of conference parameters. You can edit that template and create additional templates. See also: “Conference Templates” on page 179 “Add Conference Template Dialog Box” on page 184 “Edit Conference Template Dialog Box” on page 193 “Conference Templates Procedures” on page 202 Add Conference Template Dialog Box Lets you add a conference template.
Conference Templates Conference Manager Configuration Table 8-3 Add Conference Template dialog box (continued) Field Description Cascaded conference Enables conferences using this template to span RMX MCUs. Cascading requires site topology information, which the Polycom DMA system can get from a Polycom RealPresence Resource Manager or CMA system (see “Resource Management System Integration” on page 169) or you can create (see “Site Topology” on page 263).
DMA Operations Guide Conference Templates Table 8-3 Add Conference Template dialog box (continued) Field Description Resolution Available only if Video switching is selected. Offers the following resolution settings: Line rate • H.264 720p30 • H.264 1080p30 (available only on RMX MCUs with MPM+ or MPMx cards) • H.264 SD 30 (available only on RMX v7 MCUs with MPM+ or MPMx cards) • H.264 720p60 (available only on RMX v7 MCUs with MPM+ or MPMx cards) • H.
Conference Templates Conference Manager Configuration Table 8-3 Add Conference Template dialog box (continued) Field Description TIP compatibility Enables compatibility with Cisco’s Telepresence Interoperability Protocol, either for video only or for both video and content. Conferences can include both endpoints that don't support TIP and Cisco TelePresence® System (CTS) endpoints. Requires minimum line rate of 1024 kbps and HD resolution (720 or better). Available only on RMX v7.6 or later MCUs.
DMA Operations Guide Conference Templates Table 8-3 Add Conference Template dialog box (continued) Field Description Auto brightness Enables automatic balancing of brightness levels to compensate for an endpoint sending a dim image. Available only on RMX v7 MCUs.
Conference Templates Conference Manager Configuration Table 8-3 Add Conference Template dialog box (continued) Field Description Auto layout Lets the system select the video layout based on the number of participants in conference. Clear the check box to select a specific layout (below). Not available if Video switching is selected or Telepresence mode is Yes.
DMA Operations Guide Conference Templates Table 8-3 Add Conference Template dialog box (continued) Field Description Keyboard suppression Enables the MCU to detect and suppress keyboard noise. Available only on MCUs with MPM+ or MPMx cards. Audio clarity Improves the voice quality in conference of a PSTN endpoint. Available only on RMX v7 MCUs. RMX Skins Lets you choose the display appearance (skin) for conferences using this template. Not available if Telepresence mode is Yes.
Conference Templates Conference Manager Configuration Table 8-3 Add Conference Template dialog box (continued) Field Description RMX Recording Record conference The conference recording setting for this template: • Disabled — Recording isn’t available for conferences using this template. • Immediately — Recording starts automatically when the conference starts. • Upon Request — Recording can be initiated manually by the chairperson or an operator.
DMA Operations Guide Conference Templates Table 8-3 Add Conference Template dialog box (continued) Field Description Layout control via FECC/DTMF Enables participants to change their individual layouts using far end camera control, with or without fallback to touchtone commands for endpoints that don’t support FECC. FECC without fallback is available only on Codian v4.1 MCUs.
Conference Templates Conference Manager Configuration Edit Conference Template Dialog Box Lets you edit a conference template. The following table describes the fields in the dialog box. The Common Settings section applies to all MCUs. The Cisco Codian section appears only if the system is licensed to use Cisco Codian MCUs, and its settings apply only if a Codian MCU is selected for the call. The other sections apply only if an RMX MCU is selected.
DMA Operations Guide Conference Templates Table 8-4 Edit Conference Template dialog box (continued) Field Description Video switching (VSW) Enables a special conferencing mode that provides HD video while using MCU resources more efficiently. All participants see the current speaker full screen (the current speaker sees the previous speaker). If this mode is enabled: • The minimum line rate available is 768 kbps (except for SD resolution, available only on RMX v7 MCUs with MPM+ or MPMx cards).
Conference Templates Conference Manager Configuration Table 8-4 Edit Conference Template dialog box (continued) Field Description Line rate The maximum bit rate at which endpoints can connect to conferences using this template. If Video switching is selected, the lowest line rate available depends on the Resolution setting chosen. Encryption Specifies the media encryption setting for conferences using this template: • No encryption — All endpoints join unencrypted.
DMA Operations Guide Conference Templates Table 8-4 Edit Conference Template dialog box (continued) Field Description Access number 1 Optional access numbers to display on the Gathering Phase slide. Access number 2 Info1 Info2 Info3 Optional free-form text fields to display on the Gathering Phase slide. Refer to the RMX Administrator’s Guide to see an example of the slide and the location and appearance of these fields.
Conference Templates Conference Manager Configuration Table 8-4 Edit Conference Template dialog box (continued) Field Description RMX Video Settings Presentation mode Enables a conference to change to lecture mode when the current speaker speaks for 30 seconds. When another participant starts talking, it returns to the previous video layout. Not available if Video switching or Same layout is selected, or if Telepresence mode is Yes.
DMA Operations Guide Conference Templates Table 8-4 Edit Conference Template dialog box (continued) Field Description Telepresence mode 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. • Yes — Telepresence mode is on, regardless of whether a telepresence endpoint is present.
Conference Templates Conference Manager Configuration Table 8-4 Edit Conference Template dialog box (continued) Field Description RMX Conference IVR Override default conference IVR service Links this template to the specific conference IVR service selected in the list below. For most purposes, this option should not be selected. That enables the system to choose one of two defaults, depending on whether callers need to be prompted for passcodes.
DMA Operations Guide Conference Templates Table 8-4 Edit Conference Template dialog box (continued) Field Description Recording link Select a specific recording link or the MCU’s default. The list contains the names of all recording links available on the connected MCUs, with the number of MCUs that have the link shown in parentheses. Available only on RMX v7 MCUs. Audio only Limits recording to the audio channel of the conference.
Conference Templates Conference Manager Configuration Table 8-4 Edit Conference Template dialog box (continued) Field Description Allow DTMF *6 to mute audio Enables conference participants to mute themselves using the *6 touchtone command. Available only on Codian v4.1 MCUs. Content channel video Enables the conference to support a second video stream for content. This setting works only if Content Status is enabled on the MCU.
DMA Operations Guide Conference Templates See also: “Conference Templates” on page 179 “Add Conference Template Dialog Box” on page 184 “Edit Conference Template Dialog Box” on page 193 “Conference Templates Procedures” on page 202 Conference Templates Procedures To view the Conference Templates list >> Go to Admin > Conference Manager > Conference Templates. The Conference Templates list appears.
Conference Templates Conference Manager Configuration c Check Use existing profile and select the one you want from the RMX profile name list. The list contains the profiles available on the RMX MCUs that have been added to the Polycom DMA system. 4 Click OK. The new template appears in the Conference Templates list. To edit a conference template 1 Go to Admin > Conference Manager > Conference Templates.
DMA Operations Guide Shared Number Dialing See also: “Conference Templates” on page 179 “Add Conference Template Dialog Box” on page 184 “Edit Conference Template Dialog Box” on page 193 Shared Number Dialing The shared number dialing feature enables you to publicize a shared number that can be used to reach multiple conferences, or virtual meeting rooms (VMRs). After callers dial the shared number, they’re prompted for the VMR number to which they want to connect.
Shared Number Dialing Conference Manager Configuration Note The entry queues created for shared number dialing must have the IVR service provider only setting selected. See your Polycom RMX documentation. When selecting an MCU to handle IVR for a VEQ, the Polycom DMA system chooses from among those that have the RMX entry queue specified for that VEQ, without regard to MCU pool orders.
DMA Operations Guide Shared Number Dialing Table 8-6 The fields in the Add Virtual Entry Queue dialog box Field Description Virtual entry queue The VEQ number. Description A meaningful description for this VEQ and its IVR experience, such as which language is used. VMR entry attempts The number of times a caller can enter an invalid VMR number before the system rejects the call. RMX entry queue The RMX entry queue to use for this VEQ.
Shared Number Dialing Conference Manager Configuration Edit Virtual Entry Queue Dialog Box Lets you edit the virtual entry queue (VEQ) selected on the Shared Number Dialing page. The table below describes the fields in the dialog box. Table 8-8 The fields in the Edit Virtual Entry Queue dialog box Field Description Virtual entry queue The VEQ number. Description A meaningful description for this VEQ and its IVR experience, such as which language is used.
DMA Operations Guide 208 Shared Number Dialing Polycom, Inc.
9 Superclustering This chapter describes the Polycom® Distributed Media Application™ (DMA™) 7000 system’s superclustering capability. It includes the following topics: • About Superclustering • DMAs • Join Supercluster Dialog Box • Supercluster Procedures About Superclustering The two-server configuration of the Polycom DMA system is configured as a co-located two-server cluster, which enhances the reliability of the system by providing a measure of redundancy.
DMA Operations Guide About Superclustering assign a primary cluster and a backup cluster for each territory. When the primary cluster is online, it controls the territory and carries out all of the responsibilities belonging to the territory. When the primary cluster is offline, the backup cluster assumes control of the territory and carries out all of the territory’s responsibilities.
DMAs Superclustering Note All the clusters in a supercluster must be running compatible software versions. Patch releases of the same major version will generally be compatible, but major version upgrades will not be compatible. Major version software upgrades of a supercluster take careful planning. See “Incompatible Software Version Supercluster Upgrades” on page 371. If you’re planning to form a supercluster, we encourage you to upgrade to the latest version before doing so.
DMA Operations Guide DMAs Caution When you add the cluster you’re logged into to an existing supercluster, virtually all of that cluster’s data and configuration are replaced by the shared data and configuration of the supercluster. This includes, among other things, users, groups, conference rooms, site topology, Conference Manager configuration, Call Server configuration, and integrations.
DMAs Superclustering The Stop Using command takes the selected cluster immediately out of service: • Existing calls and conferences on the selected cluster are disconnected. No new calls or conferences are allowed to start. All registrations are rejected. The cluster ceases to manage bandwidth. • Territories for which the selected cluster has primary responsibility and a different cluster has backup responsibility are transferred to the backup cluster.
DMA Operations Guide DMAs Table 9-1 Fields on the DMAs page Column Description Host Name Virtual host name of the cluster’s signaling interface. IP Address Virtual IP address of the clusters signaling interface. Model Type of system. Currently, only DMA 7000 systems may join a supercluster. Version Software version of the system. RAS Port The UDP port the cluster uses for H.323 RAS (Registration, Admission and Status) signaling. SIP TCP Port The TCP port number the cluster uses for SIP.
Supercluster Procedures Superclustering Note All the clusters in a supercluster must be running compatible software versions. Patch releases of the same major version will generally be compatible, but major version upgrades will not be compatible. If the software version of the system you’re adding isn’t compatible with the supercluster or cluster to which you’re joining it, a message tells you so and the join operation is terminated.
DMA Operations Guide Supercluster Procedures 2 In the Actions list, click Join Supercluster. Note 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.
Supercluster Procedures Superclustering 8 Log back in and verify that the Supercluster Status pane of the Dashboard shows the correct number of servers and clusters, and there are no warnings. 9 Go to Network > DMAs, verify that the status of each DMA cluster is Superclustered, and reassign territory responsibilities as needed. To remove a cluster from the supercluster Note If possible, remove a cluster only while its server or servers are on line.
DMA Operations Guide 218 Supercluster Procedures Polycom, Inc.
10 Call Server Configuration This chapter describes the Polycom® 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.
DMA Operations Guide About the Call Server Capabilities About the Call Server Capabilities The Polycom DMA system’s Call Server capabilities provide gatekeeper functionality (if H.323 signaling is enabled), SIP proxy server and registrar functionality (if SIP signaling is enabled), XMPP server (if XMPP signaling is enabled), and bandwidth management. The system can also function as an H.323 <-> SIP gateway.
Call Server Settings Call Server Configuration Call Server Settings On the Call Server Settings page, you can specify certain gatekeeper and SIP proxy settings used by the Polycom DMA system Call Server. These settings are shared across the supercluster and apply to all the clusters. The following table describes the fields on the page.
DMA Operations Guide Call Server Settings Table 10-1 Fields on the Call Server Settings page (continued) Field Description Allow calls to inactive endpoints If this option is selected, the Call Server considers inactive as well as active endpoints when attempting to resolve an address using the Dial registered endpoints by alias dial rule (see “The Default Dial Plan and Suggestions for Modifications” on page 228).
Call Server Settings Call Server Configuration Table 10-1 Fields on the Call Server Settings page (continued) Field Description Registration refresh interval (seconds) For H.323 endpoints, specifies how often registered endpoints send “keep alive” messages to the Call Server. Endpoints that fail to send “keep alive” messages on time are flagged as inactive. For SIP endpoints, specifies the refresh interval used if the endpoint didn’t specify an interval or specified one greater than this value.
DMA Operations Guide Domains Domains On the Domains page, you can add administrative domains to or remove them from the list of domains from which registrations are accepted. If the list is empty, all domains are considered local, and the system accepts endpoint registrations from any domain. Otherwise, it accepts registrations only from the listed domains. This is a supercluster-wide configuration.
Dial Rules Call Server Configuration Table 10-2 Fields on the Domains page (continued) Field Description Locally registered SIP endpoints belong to every local domain Specifies that call requests for locally registered SIP endpoints don’t have to match the domain. For example, if there is an endpoint registered as ‘sip:johnsmith@1.1.1.1’ and this option is enabled, a call to 'sip:johnsmith@mycompany.com’ may be connected to that endpoint.
DMA Operations Guide Dial Rules The Call Server comes with a default dial plan installed that provides the most commonly needed address resolution processing. On the Dial Rules page, you can add, edit, remove, and change the order of the dial rules that make up the system’s dial plan. This is a supercluster-wide configuration. A dial rule consists of an optional preliminary script you can create to modify dial strings and the action to be performed, which you select from a well-defined list of actions.
Dial Rules Call Server Configuration Test Dial Rules Dialog Box The Test Dial Rules dialog box provides a testing mechanism for the current dial plan. You can specify various caller parameters and a dial string, and see how the each dial rule handles such a call and what its final disposition is. The following table describes the fields in the Test Dial Rules dialog box.
DMA Operations Guide Dial Rules See also: “Dial Rules” on page 225 “Add Dial Rule Dialog Box” on page 232 “Edit Dial Rule Dialog Box” on page 234 “The Default Dial Plan and Suggestions for Modifications” on page 228 The Default Dial Plan and Suggestions for Modifications The Polycom DMA system is configured by default with a generic dial plan that covers many common scenarios and may prove adequate for your needs. It’s described in the table below.
Dial Rules Call Server Configuration Table 10-5 How the default dial plan works (continued) Rule Effect 4 Otherwise, if the dial string begins with the configured prefix of a service (such as an MCU, ISDN gateway, SBC, neighbor gatekeeper, SIP peer proxy, or simplified ISDN dialing service) the call is routed to that service. Dial services by prefix Note: For a SIP peer, the dial string must consist of only the prefix and user name (no @domain).
DMA Operations Guide Dial Rules • In some circumstances (depending on the dial plan and the network topology and configuration), dial rules using the Resolve to external address action (like Rule 5 of the default dial plan) or the Resolve to IP address action (like Rule 6) can enable dialing loops to develop, especially if servers reference each other either directly or via DNS.
Dial Rules Call Server Configuration Note In a mixed H.323 and SIP environment, be aware that the Polycom DMA system acts as a seamless gateway. If an H.323 device sends it a Location Request (LRQ) and the dial plan contains a dial rule using the Resolve to external SIP peer action, the DMA system will respond with a Location Confirm (LCF) because it can resolve the address by routing the H.323 call through its gateway to the SIP peer(s). You can prevent H.
DMA Operations Guide Dial Rules See also: “Dial Rules” on page 225 “Add Dial Rule Dialog Box” on page 232 “Edit Dial Rule Dialog Box” on page 234 “Script Debugging Dialog Box for Preliminaries/Postliminaries” on page 235 “Sample Preliminary and Postliminary Scripts” on page 236 Add Dial Rule Dialog Box The following table describes the fields in the Add Dial Rule dialog box.
Dial Rules Call Server Configuration Table 10-7 Dial rule actions 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 that it’s the address of an unregistered endpoint. Resolve to registered endpoint Looks for a registered endpoint (active or inactive) that has the same alias or signaling address. Note: This action employs the H.
DMA Operations Guide Dial Rules Edit Dial Rule Dialog Box The following table describes the fields in the Edit Dial Rule dialog box. Table 10-8 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 below for more information about the actions.
Dial Rules Call Server Configuration Table 10-9 Dial rule actions (continued) For this action: The system attempts to resolve the address as follows: Resolve to service prefix Looks for a service prefix that matches the beginning of the dial string (not counting the URI scheme, if present). Note: For a SIP peer, the dial string must either include the protocol or consist of only the prefix and user name (no @domain).
DMA Operations Guide Sample Preliminary and Postliminary Scripts Table 10-10 Script Debugging dialog box Field Description Dial string This is the DIAL_STRING variable in the script, which is initially set to the dial string being evaluated. Enter a dial string to test. Alternatively, provide the entire SIP INVITE message. Then click Execute Script. Note: For SIP, the script should always specify the schema prefix (sip or sips). For instance: DIAL_STRING = "sip:xxx@10.33.120.
Sample Preliminary and Postliminary Scripts Call Server Configuration Transformation scripts output some modification of the DIAL_STRING variable (which is initially set to the dial string being evaluated). Filtering scripts may pass the dial string on to the dial rule’s action (if the filter criteria aren’t met) or return one of the following: • NEXT_RULE: Skips the rule being processed and passes the dial string to the next rule. • BLOCK: Rejects the call.
DMA Operations Guide Sample Preliminary and Postliminary Scripts // If the dial string has prefix 99, do not match on this rule. // 991234 --> NEXT_RULE if(DIAL_STRING.match(/^99/)) { return NEXT_RULE; } Skip to the next rule. /////////////////////////////// // FILTER (Inverted) // Do not match on this rule unless the dial string has prefix 99. // 1234 --> NEXT_RULE if(!DIAL_STRING.
Sample Preliminary and Postliminary Scripts Call Server Configuration /////////////////////////////// // SITE BASED NUMERIC NICKNAMES // Allow caller to omit country and area code when calling locally. // Assumes that country and area codes are set in site topology. // Assumes that all endpoints are registered with their full alias, including // country and area code. // 5551212 --> 14045551212 if(DIAL_STRING.
DMA Operations Guide Hunt Groups “External SBC” on page 114 Hunt Groups A hunt group is a set of endpoints that share an alias or aliases. Hunt groups can be used to define a dial string shared by a group of people, such as a technical support number. When the Polycom DMA system Call Server resolves a dial string to the hunt group’s alias, it selects a member of the group and tries to terminate the call to that member. The system selects hunt group members in round-robin fashion.
Hunt Groups Call Server Configuration Add Hunt Group Dialog Box The Add Hunt Group dialog box lets you define a new hunt group in the system and add members to it. The following table describes the fields in the dialog box. Table 10-12 Add Hunt Group dialog box Field Description General Info Name Hunt group name. Description The text description displayed in the Hunt Groups list. Enabled Clearing this check box lets you define a new hunt group without putting it immediately into service.
DMA Operations Guide Hunt Groups Table 10-13 Edit Hunt Group dialog box Field Description General Info Name Hunt group name. Description The text description displayed in the Hunt Groups list. Enabled Clearing this check box lets you stop using a hunt group without deleting it. No answer timeout Number of seconds to wait for a hunt group member to answer a call before giving up and trying another member. Aliases Lists the aliases (dial strings) that resolve to this hunt group.
Device Authentication Call Server Configuration 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. To specify that SIP callers can call the hunt group by dialing 1234, enter sip:1234@mydomain.com.
DMA Operations Guide Device Authentication Inbound H.323 Device Authentication In an environment where H.235 authentication is used, H.323 devices include their credentials (name and password) in registration and signaling (RAS) requests. The Polycom DMA system authenticates requests as follows: • If the request is a signaling request (ARQ, BRQ, DRQ) from an unregistered endpoint, the Call Server doesn’t authenticate the credentials.
Device Authentication Call Server Configuration When you add an external SIP peer, you can specify whether the Call Server handles challenges (401 and 407) on behalf of the source of the call or passes them on to the source of the call. You can also define authentication credentials specifically for that SIP peer. See “Add External SIP Peer Dialog Box” on page 97. Note For H.323, when you add a neighbor gatekeeper, you can configure the system to send its H.
DMA Operations Guide Device Authentication Table 10-14 Fields on the Device Authentication page (continued) Field Description Name Lists the devices in the system’s device authentication list. Use the Search names field and Search button above the list to narrow the list. The system finds devices whose names begin with the search string.
Device Authentication Call Server Configuration Table 10-15 Add Device Authentication dialog box 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 the device specified. They don’t uniquely identify a specific device; multiple devices can have the same name and password.
DMA Operations Guide Registration Policy See also: “Device Authentication” on page 243 Registration Policy On the Registration Policy page, you can specify policies to control registration by endpoints. To do so, you define the following: • Compliance policy: Write an executable script (using the Javascript language) that specifies the criteria for determining whether an endpoint is compliant or noncompliant with the registration policy.
Registration Policy Call Server Configuration Table 10-17 Fields on the Registration Policy page Field Description 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. Policy Applies Select whether to apply the registration policy script only to new registrations or also to changed re-registrations.
DMA Operations Guide Registration Policy Registration Policy Scripting A registration policy script is an executable script, written in the Javascript language, that defines the criteria to be applied to registration requests in order to determine what to do with them. The script can specify any number of criteria, and they can be as broad or narrow as you want. A script can return COMPLIANT or NONCOMPLIANT.
Registration Policy Call Server Configuration Table 10-18 Predefined variables for registration policy scripts (continued) Variable Initial value EP_H323_H323_ID_ALIAS Endpoint alias value associated with H.323 H323-ID or blank. This is an array that can contain multiple values. Separate the values with commas. EP_H323_TRANSPORTID_ALIAS Endpoint alias value associated with H.323 transportID or blank. This is an array that can contain multiple values. Separate the values with commas.
DMA Operations Guide Registration Policy Table 10-18 Predefined variables for registration policy scripts (continued) Variable Initial value EP_SIP_TEL_URI_ALIAS Endpoint alias value associated with SIP TEL: URI or blank. This is an array that can contain multiple values. Separate the values with commas. EP_VERSION Endpoint software version number. REG_IS_PERMANENT “TRUE” if endpoint is already permanently registered. Blank otherwise.
Registration Policy Call Server Configuration Script Debugging Dialog Box for Registration Policy Scripts When you click Debug this script on the Registration Policy page, the Script Debugging dialog box appears, in which you can test your script. The dialog box lets you enter or select test values for the predefined variables (see “Registration Policy Scripting” on page 250 for a list of these). Select an Endpoint Site and Subnet to populate the site/subnet-related fields, which are read-only.
DMA Operations Guide Registration Policy /////////////////////////////// // Reject SIP Registrations // if (!EP_REG_IS_H323) return NONCOMPLIANT; /////////////////////////////// // Reject aliases that aren’t the right length otherwise accept! // IF REG_SITE_COUNTRY_CODE = 1 // AND IF REG_SITE_AREA_CODE = 303 // AND IF REG_SITE_DIGITS = 4 // AND IF EP_H323_DIALEDDIGITS_ALIAS[0].
Registration Policy Call Server Configuration whitelist = new Array( “10.20.30.40”, “192.168.3.14”, “192.168.174.233” ); if (EP_IS_IPV4) { nparts = 4; } for (i = 0; i
DMA Operations Guide Prefix Service Prefix Service The Prefix Service page provides a complete list of all configured prefixes in one place, so you can easily determine what prefixes are in use and whether any conflicts exist. For your convenience, its Actions list lets you do the following: • Add, edit, or delete any of the devices without having to navigate back to the specific page for that device type.
Prefix Service Call Server Configuration 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 This feature is not related to the Polycom DMA system’s built-in H.323<->SIP gateway. Simplified ISDN gateway dialing is for routing calls to H.320 or PSTN protocol gateways. The following table describes the fields in the dialog box.
DMA Operations Guide Prefix Service Note This feature is not related to the Polycom DMA system’s built-in H.323<->SIP gateway. Simplified ISDN gateway dialing is for routing calls to H.320 or PSTN protocol gateways. The following table describes the fields in the dialog box. Table 10-21 Fields in the Edit Simplified ISDN Gateway Dialing Prefix dialog box Column Description Name A display name for this service. Description Brief description of the service.
Embedded DNS Call Server Configuration The following table describes the fields in the dialog box. Table 10-22 Fields in the Edit Vertical Service Code dialog box 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.
DMA Operations Guide Embedded DNS You can enable these embedded DNS servers on the Embedded DNS page. This is a supercluster-wide setting. If you wish to use this feature, your enterprise DNS must place the Polycom DMA system supercluster in charge of resolving a sub-domain. To do this, you must: • Add NS records to your enterprise DNS so that it refers requests to resolve the site-based logical host name to these embedded DNS servers.
History Retention Settings Call Server Configuration For instance, if the fully qualified domain name for the logical Call Server domain is callservers.example.com, the correct domain name for endpoints in the paris site is: callserver-paris.callservers.example.com Note Enter all network/DNS-related information in all lower case to avoid possible case-sensitivity issues with various devices and ensure interoperability.
DMA Operations Guide History Retention Settings Table 10-24 Fields on the History Retention Settings page (continued) Field Description Conference history records to retain The number of conference records to retain on each cluster for retrieval on the Conference History page (see “Conference History” on page 386). CDR export history records to retain The number of records of CDR export operations to retain on each cluster (see “Export History” on page 385).
11 Site Topology This chapter describes the following Polycom® 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: Polycom, Inc.
DMA Operations Guide About Site Topology Note Site topology information provides a logical model representation of a network topology, not necessarily a fully accurate literal representation of a full network. The Polycom DMA system uses site topology information for a variety of purposes, including cascading of conferences, bandwidth management, Session Border Controller selection, and cluster responsibility management in a supercluster.
Sites Site Topology See also: “Sites” on page 265 “Site Links” on page 279 “Site-to-Site Exclusions” on page 281 “Territories” on page 282 “Network Clouds” on page 285 “Site Topology Configuration Procedures” on page 287 Sites The Sites page contains a list of the sites defined in the site topology. If the system is integrated with a Polycom RealPresence Resource Manager or CMA system, it receives this information from that system, and this page is read-only. If not, you can enter site information.
DMA Operations Guide Sites Table 11-1 Information in the Sites list (continued) Column Description Max Bandwidth (Mbps) The total bandwidth limit for voice and video calls. Max Bit Rate (kbps) The per-call bit rate limit for voice and video 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.
Sites Site Topology Table 11-2 Site Information dialog box (continued) Field Description VBPs The number of Polycom Video Border Proxy NAT/firewall traversal appliances in the site. Endpoints The number of registered endpoints in the site. Subnets A list of the subnets in the site. See also: “About Site Topology” on page 263 “Sites” on page 265 Add Site Dialog Box Lets you define a new site in the Polycom DMA system’s site topology and specify which subnets are associated with it.
DMA Operations Guide Sites Table 11-3 Add Site dialog box (continued) Field Description Territory Settings Territory Assigns the site to a territory, and thus to a Polycom DMA cluster. ISDN Number Assignment Assignment method The ISDN number assignment method for the devices in this site. The numbers being assigned are endpoint aliases in the form of E.164 numbers, which can be dialed by both IP endpoints registered to the Call Server and ISDN endpoints dialing in through an ISDN gateway.
Sites Site Topology Table 11-3 Add Site dialog box (continued) Field Dialing method Description The ISDN inward dialing method for the site: • DID (Direct Inward Dial). Select this option if your ISDN gateway is provisioned with a range of phone numbers from the ISDN service provider, and each of these numbers will be assigned to an endpoint as an alias. • Gateway Extension Dialing.
DMA Operations Guide Sites Table 11-3 Add Site dialog box (continued) Field Length of subscriber number Description The number of digits in a phone number. For example, in the United States and other areas using the North American Numbering Plan (NANP), subscriber numbers have seven digits. ISDN Range Assignment (for DID dialing method) Length of call line identifier The number of digits in the Call Line Identifier (CLID), which is the dialed number. The maximum is 17.
Sites Site Topology Table 11-3 Add Site dialog box (continued) Field Description Allowed via H.323-aware SBC or ALG Allows H.323 calls to the internet only through an H.323 session border controller (SBC) or application layer gateway (ALG). Call signaling address (IPv4) The call signaling address for the H.323 SBC. Port The call signaling port for the H.323 SBC. SIP Routing Internet calls are not allowed Disables SIP calls to the internet.
DMA Operations Guide Sites Edit Site Dialog Box Lets you edit a site in the Polycom DMA system’s site topology and add or edit a subnet associated with the site. The following table describes the fields in the dialog box. Table 11-4 Edit Site dialog box Field Description General Info General Settings Site name A meaningful name for the site (up to 128 characters). Description A brief description of the site (up to 200 characters).
Sites Site Topology Table 11-4 Edit Site dialog box (continued) 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.
DMA Operations Guide Sites Table 11-4 Edit Site dialog box (continued) Field Description ISDN Outbound Dialing Override ITU dialing rules Check this box to override the standard dialing rules, established by the International Telecommunications Union, when dialing out using an ISDN gateway. The default setting, which does not override ITU dialing rules, is usually accurate for placing outbound calls.
Sites Site Topology Table 11-4 Edit Site dialog box (continued) Field Description ISDN Number Ranges The number ranges available for assignment to endpoints in the site. Click Add to add a new range of numbers. Click Edit or Delete to change or delete the selected range. The start and end numbers in the range should be entered with the same number of digits. If the range is 303-223-1000 to 1999, enter 3032231000 and 3032231999.
DMA Operations Guide Sites Table 11-4 Edit Site dialog box (continued) Field Description Call signaling address (IPv4) The call signaling address for the SBC. Port The call signaling port for the SBC. Subnets Lists the subnets in the site. Click Add to add a subnet. Select a subnet in the table and click Edit or Delete to modify or remove it. Subnet Name The unique name of the subnet. IP Address The IP address that defines the subnet. Subnet Mask The subnet mask for the site.
Sites Site Topology Add Subnet Dialog Box Lets you add subnets to the site you’re adding or editing. The following table describes the fields in the dialog box. Table 11-5 Add Subnet dialog box Field Description Name The name of the subnet. Required and must be unique. IP address The IP address that defines the subnet. Subnet mask The subnet mask, such as 255.255.255.0. Max bandwidth (Mbps) The total bandwidth limit for voice and video calls. If not specified, the site limit applies.
DMA Operations Guide Sites Edit Subnet Dialog Box Lets you edit a subnet associated with a site. The following table describes the fields in the dialog box. Table 11-6 Edit Subnet dialog box Field Description Name The name of the subnet. Required and must be unique. IP address The IP address that defines the subnet. Subnet mask The subnet mask, such as 255.255.255.0. Max bandwidth (Mbps) The total bandwidth limit for voice and video calls. If not specified, the site limit applies.
Site Links Site Topology Site Links The Site Links page contains a list of the links defined in the site topology. A link can connect two sites, or it can connect a site to an MPLS network cloud (see “Network Clouds” on page 285). Links between sites must be configured in order to enable calls between sites. In order for an endpoint in site A to call an endpoint in site B, there must be a link path (either direct, via other linked sites, or via an MPLS network cloud) connecting site A and site B.
DMA Operations Guide Site Links Table 11-8 Add Site Link dialog box 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. Can’t be changed when creating a site-to-cloud link. To site The destination site of the link. Can’t be changed when creating a site-to-cloud link.
Site-to-Site Exclusions Site Topology See also: “About Site Topology” on page 263 “Site Links” on page 279 “Site Topology Configuration Procedures” on page 287 Site-to-Site Exclusions The Site-to-Site Exclusions page contains a list of the site-to-site connections that the site topology doesn’t permit a call or session to use. If the system is integrated with a Polycom RealPresence Resource Manager or CMA system, it receives this information from that system, and this page is read-only.
DMA Operations Guide Territories 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.
Territories Site Topology The commands in the Actions list let you add a territory and edit or delete territories, or if the system is integrated with a Polycom RealPresence Resource Manager or CMA system, view details for a territory. The following table describes the fields in the list and the sections on the right. Table 11-11 Information on the Territories page Column/Section Description Name Name of the territory. Description Description of the territory.
DMA Operations Guide Territories Table 11-12 Add Territory dialog box (continued) Field Description Primary cluster The primary Polycom DMA cluster responsible for this territory. Backup cluster The backup Polycom DMA cluster, if any, responsible for this territory. You must have a supercluster consisting of at least two Polycom DMA clusters in order to specify a backup.
Network Clouds Site Topology Table 11-13 Edit Territory dialog box (continued) Field Description Primary cluster The primary Polycom DMA cluster responsible for this territory. Backup cluster The backup Polycom DMA cluster, if any, responsible for this territory. You must have a supercluster consisting of at least two Polycom DMA clusters in order to specify a backup.
DMA Operations Guide Network Clouds The commands in the Actions list let you add an MPLS cloud and edit or delete existing MPLS clouds. The following table describes the fields in the list. Table 11-14 Information in the Network Clouds list Column/Section Description Name Name of the cloud. Description Description of the cloud.
Site Topology Configuration Procedures Site Topology See also: “About Site Topology” on page 263 “Network Clouds” on page 285 “Site Topology Configuration Procedures” on page 287 Edit Network Cloud Dialog Box Lets you edit an MPLS network cloud in the Polycom DMA system’s site topology. The following table describes the fields in the dialog box. Table 11-16 Edit Network Cloud dialog box Field Description Cloud Info Name A meaningful name for the cloud (up to 128 characters).
DMA Operations Guide Site Topology Configuration Procedures 2 3 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 267. c To enable IP calls to/from the site, complete the ISDN Number Assignment, H.323 Routing and/or SIP Routing sections. d In the Subnets section, specify the subnet or subnets that make up the site. See “Add Subnet Dialog Box” on page 277.
Site Topology Configuration Procedures 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. 8 e Define the link. See “Add Site Link Dialog Box” on page 279. f Repeat the previous two steps for each additional site linked to this cloud. g Click OK.
DMA Operations Guide 290 Site Topology Configuration Procedures Polycom, Inc.
12 Users and Groups This chapter describes the following Polycom® Distributed Media Application™ (DMA™) 7000 system management topics related to users and groups: Polycom, Inc.
DMA Operations Guide User Roles Overview User Roles Overview The Polycom DMA system has four user roles, or classes of users, each with its own set of permissions. Every user account has one or more user roles (but only three of the four roles must be explicitly assigned). The following table briefly describes the user roles. See “Polycom DMA System User Roles and Their Access Privileges” on page 8 for detailed information on which commands are available to each user role.
Adding Users Overview Users and Groups If your system is integrated with an Active Directory, all enterprise users are automatically Conferencing Users. You can use enterprise groups to manage assignment of the other user roles. See “Enterprise Groups Procedures” on page 322. Note 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.
DMA Operations Guide Users 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. See the caution and first procedure in “Users Procedures” on page 313. You can then create other local user accounts or integrate with an Active Directory and assign additional roles to the appropriate enterprise users.
Users Users and Groups Caution If you have a Polycom RealPresence Resource Manager system (or another API client) that connects to the DMA system’s RealPresence Platform API, be aware that authorized users of that system (or other API client) can add local users, edit passcodes, add and edit conference rooms (VMRs), and view information about users and conference rooms. (Ordinary Conferencing Users can only access their own user information and the conference rooms they own.
DMA Operations Guide Users Table 12-2 Information in the Users list (continued) Column Description Domain The domain associated with the user. All users added manually to the system are in the LOCAL domain. Class of Service The class of service assigned to the user, which determines the priority of the user’s calls. Conference Rooms The user’s conference room or rooms (virtual meeting rooms, or VMRs).
Users Users and Groups See also: “User Roles Overview” on page 292 “Adding Users Overview” on page 293 “Add User Dialog Box” on page 297 “Edit User Dialog Box” on page 300 “Conference Rooms Dialog Box” on page 303 “Users Procedures” on page 313 “Conference Rooms Procedures” on page 315 Add User Dialog Box The following table describes the parts of the Add User dialog box, which lets you add local users to the system.
DMA Operations Guide Users Table 12-3 Add User dialog box (continued) Field Description Conference room territory The territory to which the user’s conference rooms (virtual meeting rooms, or VMRs) are assigned. A conference room’s territory assignment determines which DMA cluster hosts its conferences (the primary cluster for the territory, or its backup cluster if necessary).
Users Users and Groups Table 12-3 Add User dialog box (continued) 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 292. Selected roles Lists the roles selected for assignment to the user.
DMA Operations Guide Users Edit User Dialog Box The following table describes the parts of the Edit User dialog box. The User ID is not editable. The other General Info items are editable only for local (not enterprise) users. Table 12-4 Edit User dialog box Field Description General Info First name The user’s first name. Last name The user’s last name. User ID The user’s login name. Password The user’s system login password (not conference or chairperson passcode).
Users Users and Groups Table 12-4 Edit User dialog box (continued) Field Description Class of service Select to assign the user a class of service, which determines the priority of the user’s calls. If not selected, the user receives the highest class of service associated with any group to which the user belongs, or if none, the system’s default class of service. See “Conference Settings” on page 177. Note: A class of service may also be assigned to an endpoint. See “Endpoints” on page 79.
DMA Operations Guide Users Table 12-4 Edit User dialog box (continued) Field Description Conference Passcodes Chairperson passcode The numeric passcode that identifies chairpersons in the user’s conferences. If none, the user’s conferences don’t include the chairperson feature. 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. The passcode can also be set individually for each of the user’s conference rooms.
Users Users and Groups Lets you associate an endpoint with the selected user. Use the search fields at the top of the dialog box to find the endpoint you want to associate with this user. Select it in the table below and click OK. The dialog box closes and the endpoint is added to the user’s Associated endpoints list. Note You can also manage endpoint associations on the Endpoints page (see “Associate User Dialog Box” on page 89).
DMA Operations Guide Users Table 12-5 Conference Rooms dialog box Field Description Room ID The unique ID of the room. Icons identify enterprise conference rooms and calendared meeting (Polycom Conferencing for Outlook) conference rooms. Dial-in # Number used to dial into conference room. Automatically set to the dialing prefix (see “Conference Settings” on page 177) plus room ID.
Users Users and Groups Table 12-5 Conference Rooms dialog box (continued) Field Description Add Opens the Add Conference Room dialog box, where you can create a new custom conference room for this user. Edit Opens the Edit Conference Room dialog box, where you can modify the selected conference room. Delete Deletes the selected conference room. You’re prompted to confirm.
DMA Operations Guide Users Table 12-6 Add Conference Room dialog box 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 alphabetic character and end with an alphanumeric character.
Users Users and Groups Table 12-6 Add Conference Room dialog box (continued) Field Description Max participants Maximum number of callers allowed to join the conference. Automatic means the MCU’s maximum is used. If not selected, the room uses the system’s default maximum. See “Conference Settings” on page 177. 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.
DMA Operations Guide Users Table 12-6 Add Conference Room dialog box (continued) 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 entries in the Dial-out Participants list.
Users Users and Groups See also: “Users” on page 294 “Conference Rooms Dialog Box” on page 303 “Add Dial-out Participant Dialog Box” on page 312 “Edit Dial-out Participant Dialog Box” on page 313 “Conference Rooms Procedures” on page 315 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.
DMA Operations Guide Users Table 12-7 Edit Conference Room dialog box (continued) Field Description Conference template The template used by the conference room, which defines the conference properties (or links to the RMX profile) used for its conferences. See “Conference Templates” on page 179. If not selected, the room uses the highest-priority template associated with any group to which the user belongs, or if none, the system’s default template. See “Conference Settings” on page 177.
Users Users and Groups Table 12-7 Edit Conference Room dialog box (continued) 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 177.
DMA Operations Guide Users Table 12-7 Edit Conference Room dialog box (continued) Field Description Audio-Only IVR Dial-out Enables you to link this preset conference to an external audio conferencing bridge. Requires an RMX MCU with ISDN service configured. In the Digits field, specify the E.164 number that the RMX ISDN service must dial to connect to the audio conferencing bridge.
Users Users and Groups See also: “Add Conference Room Dialog Box” on page 305 “Edit Conference Room Dialog Box” on page 309 Edit Dial-out Participant Dialog Box Lets you edit a participant in the conference room’s Dial-out Participants list, changing the name or dial string for the participant. 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 Edit Dial-out Participant dialog box.
DMA Operations Guide Users To find a user or users 1 Go to User > Users. The Users page appears. 2 For a simple search, enter a search string in the Search users field and press ENTER. The system matches the string you enter against the beginning of the user ID, first name, and last name. If you enter “sa” it displays users whose IDs or first or last names begin with “sa.” To search for a string not at the beginning of the field, you can use an asterisk (*) as a wildcard.
Users Users and Groups 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 300. 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. 5 Click OK. To delete a local user 1 Go to User > Users.
DMA Operations Guide Users a Ensure that this room or user has a chairperson passcode and that you’ve selected a conference template that’s linked to an RMX conference IVR service and requires a chairperson to start the conference. Note For further security and to prevent lines from being placed into conference without a human answering the call, specify a conference passcode as well so the called participants are prompted to enter it before being placed into conference.
Groups Users and Groups b To link this preset conference to an external audio conferencing bridge, 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 an RMX MCU with ISDN service. c Under Dial-out Participants, add the participants to be called when the conference starts.
DMA Operations Guide Groups Note 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. Microsoft Active Directory provides two group types and four group scopes. The Polycom DMA system supports only security groups (not distribution groups) with universal or global scope. The Groups page provides access to information about enterprise groups.
Groups Users and Groups Table 12-10 Fields on the Groups page (continued) Field Description 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 141. The pool order assignment can be made at the conference room level, AD group level, or system default level. Territory Territory to which the group’s conference rooms (virtual meeting rooms, or VMRs) are assigned.
DMA Operations Guide Groups Table 12-11 Fields in the Import Enterprise Groups dialog box Field Description Search domain Optionally, select a domain to search. Group To find all groups, leave blank. To find groups beginning with a specific letter or letters, enter the string. Then click Search. You can use a wildcard (*) for more complex searches, such as: Search results • s*admins • *eng* Lists the security groups in your Active Directory that match the search string.
Groups Users and Groups Edit Group Dialog Box The following table describes the fields in the Edit Group dialog box. Table 12-12 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 177). Maximum bit rate (kbps) If Class of service is selected, specifies the maximum bit rate for the group.
DMA Operations Guide Groups Table 12-12 Fields in the Edit Group dialog box (continued) Field Description Available roles Lists the Polycom DMA system roles available for automatic assignment to members of this group (all users automatically have the Conferencing User role; it’s not listed or explicitly assigned). See “User Roles Overview” on page 292. Use the arrows to move roles from the Available roles box to the Selected roles box or vice versa.
Groups Users and Groups 4 In the Import Enterprise Groups dialog box, use Search to find the system administration group you created. Then move it to the Groups to import box and click OK. See “Import Enterprise Groups Dialog Box” on page 319. 5 On the Groups page, select your new group and, in the Actions list, click Edit. 6 In the Edit Group dialog box, move the user roles you want to give members of this group to the Selected roles box. See “Edit Group Dialog Box” on page 321. 7 Click OK.
DMA Operations Guide Login Sessions 5 Click OK. See also: “Users” on page 294 “Groups” on page 317 “Import Enterprise Groups Dialog Box” on page 319 “Edit Group Dialog Box” on page 321 Login Sessions The Login Sessions page displays information about the currently active user login sessions and enables you to terminate a login session. You must be an Administrator user to terminate a login session. Note Session termination is not supported in Maximum security mode.
Change Password Dialog Box Users and Groups See also: “Session” on page 56 “Users and Groups” on page 291 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 55). If your password has expired when you try to log into the system, the Change Password dialog box prompts you for a new password.
DMA Operations Guide 326 Change Password Dialog Box Polycom, Inc.
13 System Management and Maintenance This chapter describes the following Polycom® Distributed Media Application™ (DMA™) 7000 system operations topics: • Management and Maintenance Overview • Recommended Regular Maintenance • Dashboard • Alerts • System Log Files • Troubleshooting Utilities • Backing Up and Restoring • Upgrading the Software • Adding a Second Server • Replacing a Failed Server • Shutting Down and Restarting Management and Maintenance Overview The Polycom DMA system re
DMA Operations Guide Management and Maintenance Overview Administrator Responsibilities As a Polycom DMA system administrator, you’re responsible for the installation and ongoing maintenance of the system. You should be familiar with the following configurations, tasks, and operations: • Installing licenses when the system is first installed and when additional call capacity is added. See “Licenses” on page 67. • Monitoring system health and performing the recommended regular maintenance.
Recommended Regular Maintenance System Management and Maintenance Auditor Responsibilities As a Polycom DMA system auditor, you’re responsible for managing the system’s logging and history retention. You should be familiar with the following configurations and operations: • Configuring logging for the system. See “Logging Settings” on page 70. These settings affect the number and the contents of the log archives available for download from the system. See “System Log Files” on page 356.
DMA Operations Guide Recommended Regular Maintenance General system health and capacity checks On the Dashboard (see “Dashboard” on page 331), verify that: • There are no alerts indicating problems with any part of the system.
Dashboard System Management and Maintenance • Reports > Orphaned Groups and Users (see “Orphaned Groups and Users Report” on page 397). Verify that the number of orphans is not unexpectedly large. • Reports > Enterprise Passcode Errors (see “Enterprise Passcode Errors Report” on page 400). If you’re assigning conference and/or chairperson passcodes to enterprise users, verify that the number of passcode errors is not unexpectedly large.
DMA Operations Guide Dashboard The Dashboard is highly customizable. Initially, it contains six default panes. You can close any of these that you don’t want, and you can add others. You can add multiple copies of the same pane, each showing information for a different cluster. Click the Add Panes button to see the panes that are available. In the Settings dialog box (see “Settings Dialog Box” on page 7), you can specify the maximum number of columns for the Dashboard.
Dashboard System Management and Maintenance • The AD server address and user ID used. • The number of enterprise conference rooms created. Click the Link button to go to the Microsoft Active Directory page. See also: “Dashboard” on page 331 Call Server Active Calls Pane Displays the current number of calls in total and for each cluster of the supercluster and the licensed call limit in total and for each cluster. In a superclustered environment, a call may span multiple clusters.
DMA Operations Guide Dashboard • Server, Proxias, and application software version numbers • Hardware model and serial number • Time source • Management network MAC and IP addresses • Signaling network MAC and IP addresses (if configured for split network) • CPU usage percentage (all cores), as reported by Hyperic SIGAR • Memory usage (hover over the bar chart to see details) It’s normal for memory usage to be high.
Dashboard System Management and Maintenance Note An MCU may be connected to up to three Conference Manager clusters. If one of the three Conference Managers loses its connection to the MCU, this is counted as 0.33 disconnects. If all connections to the MCU are lost, this is counted as 1 disconnect. See also: “Dashboard” on page 331 Conference Manager Usage Pane Displays usage information for Conference Manager, either for all Conference Manager clusters or for the selected cluster.
DMA Operations Guide Dashboard — Exchange authentication failed — The credentials for the Polycom DMA system’s mailbox are no longer valid (e.g., the password has expired). — OK — The Polycom DMA system is receiving and processing Polycom Conferencing meeting notifications from the Exchange server. • The host name or IP address for the Exchange server as entered on the Microsoft Exchange Server page. • The Polycom DMA system’s mailbox address. • The number of Polycom Conferencing meetings today.
Dashboard System Management and Maintenance See also: “Dashboard” on page 331 Signaling Settings Pane Displays the H.323 and SIP signaling settings for the selected cluster, including whether each is enabled and what ports are assigned. Click the Link button to go to the Signaling Settings page.
DMA Operations Guide Alerts 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.
Alerts System Management and Maintenance Alert 1002 Cluster is out of service as of YYYY-MM-DD HH:MM GMT+/-H[:MM]. You or another administrator took the cluster out of service (or busied out the cluster, and now all calls and conferences have ended). An out-of-service cluster is still running and accessible via the management interface, but doesn’t accept any calls or registrations. Click the link to go to the DMAs page. See also: “Alerts” on page 338 Alert 1003 Cluster is orphaned.
DMA Operations Guide Alerts Click the link to go to the Territories page. To enable conferencing to continue in the territory (at diminished capacity), assign it to some other cluster. See also: “Alerts” on page 338 Alert 1102 Territory not active; cluster is not operational. The territory’s primary cluster is unreachable and it has no backup cluster. This may indicate a network problem. It’s also possible that someone shut the cluster down or that it failed.
Alerts System Management and Maintenance Click the link to go to the Territories page. Determine whether the cluster was deliberately shut down. If not, try pinging the cluster’s IP addresses. If this is a two-server cluster, and you can’t ping either the virtual or physical IP addresses, look for a network problem. It’s unlikely that both servers have failed simultaneously. If you can ping the cluster, the OS is running, but the application may be in a bad state. Try rebooting the server(s).
DMA Operations Guide Alerts Alert 2004 Resource management server has inconsistent territory definitions in its site topology. The system is integrated with a Polycom RealPresence Resource Manager or CMA system, and there is a problem with the territory definitions or responsibility assignments in the site topology data imported from that system.
Alerts System Management and Maintenance See also: “Alerts” on page 338 Alert 2103 Active Directory primary caching cluster is not operational. Caching by backup cluster . The primary cluster for the territory responsible for Active Directory integration is unreachable, and its backup cluster has taken over responsibility for the caching of AD data. This may indicate a network problem. It’s also possible that someone shut the cluster down or that it failed.
DMA Operations Guide Alerts See also: “Alerts” on page 338 Alert 2105 Active Directory service is not available. Cluster is not operational. The primary cluster for the territory responsible for Active Directory integration is unreachable, and it has no backup cluster. This may indicate a network problem. It’s also possible that someone shut the cluster down or that it failed. Click the link to go to the DMAs page to begin troubleshooting.
Alerts System Management and Maintenance See also: “Alerts” on page 338 Alert 2201 Calendaring primary integration cluster is not operational. Integration by backup cluster . The primary cluster for the territory responsible for Exchange server integration is unreachable, and its backup cluster has taken over responsibility for monitoring the Polycom Conferencing user mailbox and accepting or declining the meeting invitations received. This may indicate a network problem.
DMA Operations Guide Alerts Click the link to go to the DMAs page to begin troubleshooting. See also: “Alerts” on page 338 Alert 3001 No signaling interface enabled for cluster . SIP or H.323 must be configured to allow calls. The specified cluster has neither H.323 or SIP signaling enabled and is unable to accept calls. To use the cluster for anything other than logging into the management interface, you must enable signaling.
Alerts System Management and Maintenance If you’re logged into that cluster, click the link to go to the Certificates page. If not, log into that cluster and go to Admin > Local Cluster > Certificates. See also: “Alerts” on page 338 Alert 3103 Cluster : The server certificate will expire within days. All system access may be lost. The specified cluster’s server certificate will soon expire.
DMA Operations Guide Alerts Alert 3105 Cluster : One or more CA certificates will expire within 30 days. The specified cluster has a CA certificate or certificates that will expire soon. When a CA certificate expires, the certificates signed by that certificate authority are no longer accepted.
Alerts System Management and Maintenance 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.
DMA Operations Guide Alerts This could be a problem with the GB1 port (eth0 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. See also: “Alerts” on page 338 Alert 3305 Cluster : A signaling network error exists on . The specified server has detected a problem with the signaling network connection.
Alerts System Management and Maintenance 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 338 Alert 3403 Cluster : Log files on server exceed the capacity limit and will be purged within 24 hours. Log archives on the specified cluster exceed the 1 GB capacity limit for logs. After midnight, the system will delete sufficient log archives to get below the 1 GB limit.
DMA Operations Guide Alerts Create a new backup and download it, and then contact Polycom Global Services. See also: “Alerts” on page 338 Alert 3406 Server CPU utilization > 75%. The specified server’s CPU and/or I/O bandwidth usage is exceptionally high. This can be caused by activities such as backup creation, CDR downloading, logging at too high a level, or refreshing an extremely large Active Directory cache. The cause may also be a system health problem or a runaway process.
Alerts System Management and Maintenance See also: “Alerts” on page 338 Alert 3602 Cluster : Local time differs by more than ten seconds between servers. The time on the two servers in the specified cluster has drifted apart by an unusually large amount. This may indicate a misconfiguration or a problem with one of the servers. Contact Polycom Global Services. See also: “Alerts” on page 338 Alert 3603 Cluster : Enterprise directory integration is not consistent between servers.
DMA Operations Guide Alerts Try to determine which server’s data is incorrect and reboot it. See also: “Alerts” on page 338 Alert 3606 Cluster : Local users differ between servers. In the specified cluster, the local users are different on the two servers, indicating that their internal databases aren’t consistent. Try to determine which server’s data is incorrect and reboot it. See also: “Alerts” on page 338 Alert 4001 MCU “” is currently busied out.
Alerts System Management and Maintenance See also: “Alerts” on page 338 Alert 5001 ITP system attempting to register with ID is improperly configured. A device that identifies itself as an ITP (interactive telepresence) system has registered with the Call Server, but the H.323 ID of the device doesn't specify its endpoint number or the number of endpoints in the ITP system, as it should. The H.323 ID must be updated on the endpoints of the ITP system.
DMA Operations Guide System Log Files See also: “Alerts” on page 338 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. Click the link to go to the History Retention Settings page and increase the number of registration records to retain on each cluster.
System Log Files System Management and Maintenance In such a situation, your support representative may ask you to download log archives and send them to Polycom Global Services. You may be asked to manually roll logs in order to begin gathering data anew. After a certain amount of the activity of interest, you may be asked to download the active logs and send them to Polycom Global Services. The following table describes the fields in the System Log Files list.
DMA Operations Guide System Log Files a In the Actions list, click Download Active Logs. b In the dialog box, specify a location and file name, and click Save. To manually roll the system logs 1 Go to Maintenance > System Log Files. The System Log Files page appears. 2 In the Actions list, click Roll Logs. If you have a supercluster, you’re prompted to choose the cluster whose log files you want to roll. 3 If applicable, select a cluster. Wait a few seconds.
Troubleshooting Utilities System Management and Maintenance Troubleshooting Utilities The Polycom 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. Each command is run on each server in the cluster, and the results are displayed in a separate panel for each server.
DMA Operations Guide Backing Up and Restoring 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 system activity report 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 System Management and Maintenance In addition, the Polycom DMA USB Configuration Utility (on the USB stick used to initially configure the network and system parameters) can restore the Polycom DMA system from a backup file that you load onto the USB stick. Note We strongly suggest that you: • Download backup files regularly for safekeeping.
DMA Operations Guide Backing Up and Restoring Backup and Restore Procedures Caution Restoring from a backup requires a system restart and terminates all active conferences. Note You can restore the system while it’s integrated with a Polycom RealPresence Resource Manager or CMA system, but the result depends on the state when the backup you’re restoring from was made.
Backing Up and Restoring System Management and Maintenance 3 In the Actions list, click Create New. A confirmation dialog tells you the backup archive was created. 4 Click OK. To upload a 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. Uploading a backup will delete the oldest file (unless there are fewer than ten). 3 In the Actions list, click Upload.
DMA Operations Guide Backing Up and Restoring 6 When asked to confirm that you want to restore, click Yes. A dialog box informs you when all files have been restored. 7 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.
Backing Up and Restoring System Management and Maintenance 5 In the DMA USB Configuration Utility window, click Copy a Backup to the USB Stick. 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 DMA system backup. Otherwise, it confirms that the backup file is in place. The utility’s main window states that The USB stick is ready to restore the system from a backup file.
DMA Operations Guide Upgrading the Software Upgrading the Software The Polycom DMA system’s Software Upgrade page lets you upload a software upgrade package and install the upgrade on your system (both servers, if present). It also lets you roll back to the previous version, if necessary. This process can be used for patches, minor upgrades, and major upgrades.
Upgrading the Software System Management and Maintenance Basic Upgrade Procedures Note 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 360.
DMA Operations Guide Upgrading the Software 7 If this cluster is part of a supercluster, do the following: a Go to Network > Site Topology > Territories and reassign the cluster’s territory responsibilities. Wait a few minutes and verify on another cluster that the change has been replicated. b Go to Network > DMAs and take it out of service (or busy it out and wait for all calls to end). c Select this cluster and click Remove from Supercluster.
Upgrading the Software System Management and Maintenance c If the upgrade requires a new license activation key code or codes, obtain and install them as described in “Add Licenses” on page 71. 12 If this cluster is part of a supercluster, do the following: a Go to Network > DMAs, and rejoin this cluster to the supercluster. See “Supercluster Procedures” on page 215.
DMA Operations Guide Upgrading the Software Note 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. 4 e 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. f Return to Maintenance > Software Upgrade. In the Actions list, click Roll Back. A confirmation dialog box appears. 5 Click Yes.
Upgrading the Software System Management and Maintenance 9 Call Polycom Global Services if: — After waiting significantly longer than the estimated install time, you’re still unable to log back in. — You can log in, but the Dashboard shows only one server for a two-server cluster. — The package version numbers on the two servers are not the same.
DMA Operations Guide Upgrading the Software Caution We strongly recommend upgrading a supercluster only during a system-wide maintenance window when there are no calls or conferences on the system and all clusters can be taken out of service. This makes the process significantly faster and easier. If you must upgrade incrementally, be aware of the limited capacity available at any given point in the process.
Upgrading the Software System Management and Maintenance • As the clusters for some endpoints are removed from the existing supercluster and join the new one, the video network becomes partitioned with separate islands of endpoints. • Some endpoints don’t respond well to a gatekeeper change (such as a signaled alternate gatekeeper).
DMA Operations Guide Upgrading the Software Simplified Supercluster Upgrade (Complete Service Outage) If it’s possible to schedule the upgrade for a maintenance window during which there is no service, we strongly recommend doing so, as described below. This greatly shortens and simplifies the process. To upgrade a supercluster by taking all clusters out of service 1 Put the upgrade package file somewhere on or accessible from your PC.
Upgrading the Software System Management and Maintenance 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. d Click OK to log out immediately, or simply wait. Note If you have assistants to help you, they can perform steps 5 and 6, upgrading all the other clusters simultaneously, while the upgrade package is being installed on cluster A.
DMA Operations Guide Upgrading the Software Note 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.
Adding a Second Server System Management and Maintenance Complex Supercluster Upgrade (Some Service Maintained) Please contact Polycom Global Services for instructions and assistance.
DMA Operations Guide Adding a Second Server Expanding an Unpatched System To expand an unpatched 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 DMA system server (or close enough to connect them with one of the provided crossover Ethernet cables).
Adding a Second Server System Management and Maintenance 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 DMA system server (or close enough to connect them with one of the provided crossover Ethernet cables). 2 Connect the GB 1 Ethernet port of the new server to the enterprise network.
DMA Operations Guide Replacing a Failed Server 11 When the first server displays DMA Ready, turn on the second server. The second server boots, detects the presence of Server 1, gets its configuration settings from it, and joins the cluster. When done, both servers’ LCDs display DMA Clustered. 12 Log into the system, go to Admin >Local Cluster > Licenses, and follow the procedure for obtaining and entering a license activation key. See “Add Licenses” on page 71.
Shutting Down and Restarting System Management and Maintenance See also: “Management and Maintenance Overview” on page 327 “Recommended Regular Maintenance” on page 329 Shutting Down and Restarting The Polycom DMA system’s Shutdown and Restart page lets you restart the system or turn it off completely. These commands affect both servers in a two-server cluster. Both shutting down and restarting will terminate all existing calls and log out all current users.
DMA Operations Guide 382 Shutting Down and Restarting Polycom, Inc.
14 System Reports This chapter describes the following Polycom® 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
DMA Operations Guide Call History Call History The Call History page lets you view detailed records of calls and download CDRs (call detail records). The list includes point-to-point calls through Call Server and VMR calls through Conference Manager. The search pane above the list lets you find calls matching the criteria you specify. Click the down arrow to expand the search pane. You can search for an originator or destination device by its name, alias, or IP address.
Call History System Reports Table 14-1 Information in the Call History list Column Description Originator Source of the call (the device’s display name, if available; otherwise, its name, alias, or IP address, in that order of preference). Dial String Dial string sent by originator, when available. Destination Destination of the call (the device’s display name, if available; otherwise, its name, alias, or IP address, in that order of preference).
DMA Operations Guide Conference History See also: “System Reports” on page 383 “Call Detail Records (CDRs)” on page 388 Conference History The Conference History page lets you view detailed records of conferences and download CDRs (call detail records). The fields at the top of the page let you specify the starting and ending date and time or the conference room number (VMR number) for which you want to view conference records.
Conference History System Reports Table 14-4 Information in the Conference History page Export History list Column Description User User ID of the person who performed the export. Export Type One of the following: • CDR for CDR exports • Call History for search results exports Date of Export Date and time of the export. Cluster The cluster from which the export took place. Associated Calls The Associated Calls list shows all the calls associated with the selected conference.
DMA Operations Guide Call Detail Records (CDRs) Property Changes The Property Changes list provides more information about the selected conference, listing every change in the value of a conference property during the course of the conference. The following table describes the fields in the list. Table 14-6 Information in the Property Changes list Column Description Name Name of the call property. Value Value assigned to the property. Time Date and time of the property change.
Call Detail Records (CDRs) System Reports Click OK. 4 A Save dialog box prompts you to select a location for the downloaded file. The default filename is cdrExport.zip, but you can change that. Choose a path and filename for the CDR file and click Save. 5 The File Download dialog shows the progress. When the download is complete, click Close.
DMA Operations Guide Call Detail Records (CDRs) Table 14-7 Call CDR (continued) Field Description origEndpoint The originating endpoint’s name, display name, alias, or IP address (in that order of preference), depending on what it provided in the call signaling. dialString Initial dial string as supplied by the originator. If multiple call records, this value is the same across all segments of the call.
Call Detail Records (CDRs) System Reports Table 14-7 Call CDR (continued) Field Description VEQCluster Virtual cluster ID; the cluster handling the VEQ, or blank if no VEQ. 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 300). For point-to-point calls, this is the user associated with the endpoint that started this call.
DMA Operations Guide Call Detail Records (CDRs) Table 14-8 Conference CDR (continued) Field Description cluster Virtual cluster ID; the cluster serving the VMR. confUUID Unique identifier for the conference. startTime YYYY-MM-DD HH:MM:SS GMT+/-H[:MM] endTime YYYY-MM-DD HH:MM:SS GMT+/-H[:MM] userID User ID of the conference room (VMR) owner. roomID Conference room (VMR) number. partCount Maximum number of calls in the conference (high water mark).
Registration History Report System Reports Registration History Report If the Polycom DMA system Call Server is providing H.323 gatekeeper or SIP registrar services, the Registration History page provides access to information about registered devices. It also provides information about external SIP peers with which the system is registered, if any. The search pane above the list lets you find registrations matching the criteria you specify. Click the down arrow to expand the search pane.
DMA Operations Guide Active Directory Integration Report Registration History Procedures To find a device or devices 1 Go to Reports > Registration History. The Registration History page appears. 2 For a simple search of the current day’s registration history, enter a search string in the Alias, Owner, or IP address field. Select Status, Protocol Type, or Device Type values to apply those filters. Then click Search.
Active Directory Integration Report System Reports The following table describes the information displayed at the top of the page and the fields in the two lists. Table 14-10 Fields on the Active Directory Integration page Field Description Status OK indicates that the cluster successfully connected to the Active Directory during the last update. A padlock indicates that the connection was encrypted.
DMA Operations Guide Active Directory Integration Report Table 14-10 Fields on the Active Directory Integration page (continued) Field Description Status Indicates if the system contacted a domain controller in that domain (in order to retrieve attributes not in the global catalog or to get member information for its global groups) and the results: • Not required: no groups from that domain have been imported into the Polycom DMA system and all attributes needed were in the global catalog.
Orphaned Groups and Users Report System Reports Orphaned Groups and Users Report If the Polycom 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.
DMA Operations Guide Conference Room Errors Report To remove orphaned user data from the system 1 Go to Reports > Orphaned Groups and Users. 2 In the Actions list, click Clean Orphaned Users. 3 When prompted to confirm, click OK. The system removes the orphaned user data.
Conference Room Errors Report System Reports If you don’t specify a directory attribute from which to generate conference room IDs, this number is zero and the report contains nothing else of value.
DMA Operations Guide Enterprise Passcode Errors Report Exporting Conference Room Errors Data From the Conference Room Errors page, you can use the Export Room Errors Report command to download a CSV (comma-separated values) file containing all the data in the conference room errors report. To download conference room errors data 1 Go to Reports > Conference Room Errors. 2 In the Actions list, click Export Room Errors Report. 3 In the Exporting Conference Room Errors Report dialog box, click Download.
Enterprise Passcode Errors Report System Reports Note You must be an enterprise user (with the appropriate user role assignments) to see the enterprise passcode errors report. A local user can’t access this page, regardless of user roles.
DMA Operations Guide Network Usage Report Exporting Enterprise Passcode Errors Data From the Conference Room Errors page, you can use the Export Enterprise Passcode Errors Report command to download a CSV (comma-separated values) file containing all the data in the enterprise passcode errors report. To download enterprise passcode errors data 1 Go to Reports > Enterprise Passcode Errors. 2 In the Actions list, click Export Enterprise Passcode Errors Report.
Network Usage Report System Reports 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.
DMA Operations Guide Network Usage Report Table 14-14 Network Usage record layout (continued) 404 Field Description max_video_jitter Maximum jitter of all QoS reports of all video channels in the scope during the time interval (milliseconds). avg_video_delay Mean delay of all QoS reports of all video channels in the scope during the time interval (milliseconds). max_video_delay Maximum delay of all QoS reports of all video channels in the scope during the time interval (milliseconds).
Network Usage Report System Reports Table 14-14 Network Usage record layout (continued) Field Description h323_calls Max concurrent calls using H.323 signaling in the scope during the time interval. gateway_calls Max concurrent calls using the SIP to H.323 gateway in the scope during the time interval. conference_calls Max concurrent Conference Manager calls in the scope during the time interval. To download network usage data 1 Go to Reports > Network Usage.
DMA Operations Guide 406 Network Usage Report Polycom, Inc.
15 Polycom DMA System SNMP Support This chapter provides a discussion of the Polycom® Distributed Media Application™ (DMA™) SNMP support. It includes these topics: • SNMP Overview • SNMP Settings • SNMP Procedures • The Polycom DMA System MIB SNMP Overview Simple Network Management Protocol (SNMP) is a communication protocol that allows network management systems to manage resources across a network. SNMP can be transmitted over TCP or UDP.
DMA Operations Guide SNMP Overview We recommend using a MIB browser to explore the PolycomDMA system MIB, but a copy of the MIB is available in “The Polycom DMA System MIB” on page 418. The DMA system MIB is self-documenting, including information about the purpose of specific traps and inform notifications. Note that you should understand how your SNMP management system is configured in order to properly configure the DMA system’s SNMP transport protocol, version, authentication, and privacy settings.
SNMP Settings Polycom DMA System SNMP Support List of Available SNMP MIBs The following table describes the MIBs that are on the Polycom DMA system. You can download any of them from the SNMP Settings page. See “SNMP Procedures” on page 417. Table 15-1 SNMP MIBs on the system Name Description JVM-MANAGEMENT-MIB MIB for monitoring the state of the Java Virtual Machine. MIB-Dell-10892 The primary MIB for the Polycom-branded Dell server.
DMA Operations Guide SNMP Settings Table 15-2 Information on the SNMP Settings page Setting Description Enable SNMP monitoring Enables the SNMP settings fields below. SNMP version Select the version to enable: • v2c • v3 See “SNMP Versions Supported” on page 408 for a comparison of the two versions. Transport Specify the transport protocol for SNMP communications: TCP—This protocol has error-recovery services, message delivery is assured, and messages are delivered in the order they were sent.
SNMP Settings Polycom DMA System SNMP Support Table 15-2 Information on the SNMP Settings page (continued) Setting Description Local engine ID When SNMP monitoring is enabled, displays the administratively unique identifier for the default context of the system’s SNMP protocol engine. For SNMPv3, the local engine ID is used in generating the authentication and encryption keys.
DMA Operations Guide SNMP Settings Table 15-2 Information on the SNMP Settings page (continued) Setting Type Description The notification type for this agent: • Inform—An unsolicited message sent to a notification receiver for which the agent expects/requires a confirmation message. Introduced with SNMP version 2c, this option is not supported by systems that only support SNMP version 1.
SNMP Settings Polycom DMA System SNMP Support Table 15-3 Add Notification User dialog box Setting Description Security user The security user name authorized to receive notifications (Traps or Informs). Authentication type The authentication protocol. These protocols are used to create unique fixed-size message digests of a variable length message. Possible values for authentication protocol are: • MD5—Creates a digest of 128 bits (16 bytes). • SHA—Creates a digest of 160 bits (20 bytes).
DMA Operations Guide SNMP Settings Edit Notification User Dialog Box The Edit Notification User dialog box lets you modify a security user authorized to receive SNMPv3 notifications. The following table describes the fields in the dialog box. Table 15-4 Edit Notification User dialog box Setting Description Security user The security user name authorized to receive notifications (Traps or Informs). Authentication type The authentication protocol.
SNMP Settings Polycom DMA System SNMP Support Add Notification Agent Dialog Box The Add Notification Agent dialog box lets you add an SNMP agent to the system, specifying what kinds of notifications it sends and to whom. To limit the effect on system performance, a maximum of 8 agents may be defined. The following table describes the fields in the dialog box. Table 15-5 Add Notification Agent dialog box Setting Description Enable agent Enables the notification agent defined below.
DMA Operations Guide SNMP Settings Edit Notification Agent Dialog Box The Edit Notification Agent dialog box lets you enable, disable, or modify an SNMP notification agent. The following table describes the fields in the dialog box. Table 15-6 Edit Notification Agent dialog box Setting Description Enable agent Enables the notification agent defined below. Clearing this check box lets you stop using this agent without deleting it.
SNMP Procedures Polycom DMA System SNMP Support SNMP Procedures To enable and configure SNMP monitoring 1 Go to Admin > Local Cluster > SNMP Settings. 2 Select Enable SNMP monitoring and select an SNMP version. For information on the SNMP versions, see “SNMP Overview” on page 407. 3 Configure the SNMP version, transport protocol, and other settings. If using SNMPv3, configure the security user, authentication, and privacy settings. For descriptions, see “SNMP Settings” on page 409.
DMA Operations Guide The Polycom DMA System MIB 3 In the MIBs dialog box, select the MIB of interest and click Download. 4 Specify a name and location, and click Save. Polycom recommends using a MIB browser to explore the DMA system MIB, but a copy of the MIB is available in “The Polycom DMA System MIB” on page 418. The DMA system MIB is self-documenting, including information about the purpose of specific traps and inform notifications.
The Polycom DMA System MIB --------------------------------------------------- .2.1.2.1.1 .2.1.2.1.2 .2.1.2.1.3 .2.1.2.1.3.1 .2.1.2.1.3.1.1 .2.1.2.1.3.1.2 .2.1.2.1.3.1.3 .2.1.2.1.3.1.4 .2.1.2.1.3.1.5 .2.1.2.1.3.1.6 .2.1.2.1.3.1.7 .2.1.2.1.3.1.8 .2.1.2.1.3.1.9 .2.1.3 .2.1.3.1 .2.1.3.1.1 .2.1.3.1.1.1 .2.1.3.1.1.2 .2.1.3.1.1.2.1 .2.1.3.1.1.2.1.1 .2.1.3.1.1.2.1.2 .2.1.3.1.1.2.1.3 .2.1.3.1.1.2.1.4 .2.1.3.1.2 .2.1.3.1.2.1 .2.1.3.1.2.1.1 .2.1.3.1.2.1.1.1 .2.1.3.1.2.1.1.2 .2.1.3.1.2.1.1.3 .2.1.3.1.2.1.1.4 .2.1.3.
DMA Operations Guide --------------------------------------------------- 420 .2.1.3.2.1 .2.1.3.2.1.1 .2.1.3.2.1.1.1 .2.1.3.2.1.1.2 .2.1.3.2.1.1.3 .2.1.3.2.1.2 .2.1.3.2.1.2.1 .2.1.3.2.1.2.2 .2.1.3.2.1.2.3 .2.1.3.2.1.2.4 .2.1.4 .2.2 .2.2.1 .2.2.1.1 .2.2.1.2 .2.2.1.2.1 .2.2.1.2.1.1 .2.2.1.2.1.1.1 .2.2.1.2.1.1.2 .2.2.1.2.1.1.3 .2.2.1.2.2 .2.2.1.2.2.1 .2.2.1.2.2.1.1 .2.2.1.2.2.1.2 .2.2.1.2.2.1.3 .2.2.1.2.3 .2.2.1.2.3.1 .2.2.1.2.3.1.1 .2.2.1.2.3.1.2 .2.2.1.2.3.1.3 .2.2.1.2.3.1.4 .2.2.1.2.3.1.5 .2.2.1.3 .2.2.1.
The Polycom DMA System MIB --------------------------------------------------- .2.2.1.3.3.1.2 .2.2.1.3.3.1.3 .2.2.1.3.3.1.4 .2.2.1.3.3.1.5 .2.2.1.3.3.1.6 .2.2.1.3.3.1.7 .2.2.1.3.4 .2.2.1.3.4.1 .2.2.1.3.4.1.1 .2.2.1.3.4.1.2 .2.2.1.3.4.1.3 .2.2.1.3.4.1.4 .2.2.1.3.4.1.5 .2.2.1.3.4.1.6 .2.2.1.3.4.1.7 .2.2.1.4 .2.2.1.4.1 .2.2.1.4.1.1 .2.2.1.4.1.1.1 .2.2.1.4.1.1.2 .2.2.1.4.1.1.3 .2.2.1.4.2 .2.2.1.4.2.1 .2.2.1.4.2.1.1 .2.2.1.4.2.1.2 .2.2.1.4.2.1.3 .2.2.1.4.2.1.4 .2.2.1.4.2.1.5 .2.2.1.4.2.1.6 .2.2.1.4.3 .2.2.1.4.
DMA Operations Guide --------------------------------------------------- 422 .2.2.2.1 .2.2.2.1.1 .2.2.2.1.2 .2.2.2.1.2.1 .2.2.2.1.2.1.1 .2.2.2.1.2.1.2 .2.2.2.1.2.1.3 .2.2.2.1.2.1.4 .2.2.2.1.2.1.5 .2.2.2.1.2.1.6 .2.2.2.1.3 .2.2.2.1.3.1 .2.2.2.1.3.1.1 .2.2.2.1.3.1.2 .2.2.2.1.3.1.3 .2.2.2.1.3.1.4 .2.2.2.1.3.1.5 .2.2.2.1.3.1.6 .2.2.2.1.3.1.7 .2.2.2.1.4 .2.2.2.1.4.1 .2.2.2.1.4.1.1 .2.2.2.1.4.1.2 .2.2.2.1.4.1.3 .2.2.2.1.4.1.4 .2.2.2.1.4.1.5 .2.2.2.1.4.1.6 .2.2.2.2 .2.2.2.2.1 .2.2.2.2.2 .2.2.2.2.2.1 .2.2.2.2.2.
The Polycom DMA System MIB --------------------------------------------------- .2.2.3.3.1 .2.2.3.3.1.1 .2.2.3.3.1.2 .2.2.3.3.1.3 .2.2.3.3.1.4 .2.2.3.3.1.5 .2.2.4 .2.2.4.1 .2.2.4.1.1 .2.2.4.1.1.1 .2.2.4.1.1.2 .2.2.4.1.1.2.1 .2.2.4.1.1.2.1.1 .2.2.4.1.1.2.1.2 .2.2.4.1.2 .2.2.4.1.2.1 .2.2.4.1.2.1.1 .2.2.4.1.2.1.1.1 .2.2.4.1.2.1.1.2 .2.2.4.1.2.1.1.3 .2.2.4.1.2.1.1.4 .2.2.4.1.2.1.1.5 .2.2.4.1.2.1.1.6 .2.2.4.1.2.1.1.7 .2.2.4.1.2.2 .2.2.4.1.2.2.1 .2.2.4.1.2.2.1.1 .2.2.4.1.2.2.1.2 .2.2.4.1.2.2.1.3 .2.2.4.1.2.2.1.
DMA Operations Guide --------------------------------------------------- 424 .2.2.4.2.1.2.1 .2.2.4.2.1.2.1.1 .2.2.4.2.1.2.1.2 .2.3 .2.3.1 .2.3.1.1 .2.3.1.1.1 .2.3.1.1.2 .2.3.1.1.2.1 .2.3.1.1.2.1.1 .2.3.1.1.2.1.2 .2.3.1.1.2.1.3 .2.3.1.1.2.1.4 .2.3.1.1.2.1.5 .2.3.1.1.2.1.6 .2.3.1.1.3 .2.3.1.1.4 .2.3.1.1.4.1 .2.3.1.1.4.1.1 .2.3.1.1.4.1.2 .2.3.1.1.4.1.3 .2.3.1.1.4.1.4 .2.3.1.1.4.1.5 .2.3.1.1.4.1.6 .2.3.1.1.5 .2.3.1.1.6 .2.3.1.1.6.1 .2.3.1.1.6.1.1 .2.3.1.1.6.1.2 .2.3.1.1.6.1.3 .2.3.1.1.6.1.4 .2.3.1.1.6.1.5 .
The Polycom DMA System MIB --------------------------------------------------- .2.3.3.1.1 .2.3.3.1.2 .2.3.3.1.2.1 .2.3.3.1.2.1.1 .2.3.3.1.2.1.2 .2.3.3.1.2.1.3 .2.3.3.1.2.1.4 .2.3.3.1.2.1.5 .2.4 .2.4.1 .2.4.1.1 .2.4.1.2 .2.4.1.2.1 .2.4.1.2.1.1 .2.4.1.2.1.2 .2.4.1.2.1.3 .2.4.1.2.1.4 .2.4.1.2.1.5 .2.4.1.2.1.6 .2.5 .2.5.1 .2.5.1.1 .2.5.1.2 .2.5.1.3 .2.5.1.4 .2.5.1.5 .2.5.2 .2.5.2.0 .2.5.2.0.1001 .2.5.2.0.1002 .2.5.2.0.1003 .2.5.2.0.1004 .2.5.2.0.1005 .2.5.2.0.1101 .2.5.2.0.1102 .2.5.2.0.1103 .2.5.2.0.1104 .2.
DMA Operations Guide -------------------------------------------- .2.5.2.0.3101 .2.5.2.0.3102 .2.5.2.0.3103 .2.5.2.0.3104 .2.5.2.0.3105 .2.5.2.0.3201 .2.5.2.0.3202 .2.5.2.0.3301 .2.5.2.0.3302 .2.5.2.0.3303 .2.5.2.0.3304 .2.5.2.0.3305 .2.5.2.0.3401 .2.5.2.0.3402 .2.5.2.0.3403 .2.5.2.0.3404 .2.5.2.0.3405 .2.5.2.0.3406 .2.5.2.0.3501 .2.5.2.0.3502 .2.5.2.0.3503 .2.5.2.0.3601 .2.5.2.0.3602 .2.5.2.0.3603 .2.5.2.0.3604 .2.5.2.0.3605 .2.5.2.0.3606 .2.5.2.0.4001 .2.5.2.0.4002 .2.5.2.0.4003 .2.5.2.0.5001 .2.5.2.0.
The Polycom DMA System MIB Polycom DMA System SNMP Support FROM SNMPv2-SMI OBJECT-GROUP, NOTIFICATION-GROUP, MODULE-COMPLIANCE FROM SNMPv2-CONF polycom FROM POLYCOM-BASE-MIB ; dma MODULE-IDENTITY LAST-UPDATED “201109220000Z” ORGANIZATION “Polycom, Inc.” CONTACT-INFO “http://www.polycom.com/dma” DESCRIPTION “This MIB defines the SNMP interface for monitoring the Polycom Distributed Media Application(tm) DMA(tm) 7000 system. Copyright (c) 2011 Polycom, Inc.
DMA Operations Guide -- dma.2 dmaMonitoring1 STATUS DESCRIPTION ::= { dma 2 The Polycom DMA System MIB OBJECT-IDENTITY current “This OID contains the DMA system’s monitoring data exposed over SNMP.” } -- DMA CONFIG -- dma.2.1 dmaConfig OBJECT-IDENTITY STATUS current DESCRIPTION “Contains configuration data for the DMA system.” ::= { dmaMonitoring1 1 } -- dma.2.1.1 cfgIdentity OBJECT-IDENTITY STATUS current DESCRIPTION “Identification info for the server from which data is being retrieved.
The Polycom DMA System MIB Polycom DMA System SNMP Support cfgProdInfoHWModel OBJECT-TYPE SYNTAX GeneralString MAX-ACCESS read-only STATUS current DESCRIPTION “Server’s hardware model.” ::= { cfgProdInfoHardwareInfo 1 } -- dma.2.1.1.1.3.2 cfgProdInfoHWSerialNumber OBJECT-TYPE SYNTAX GeneralString MAX-ACCESS read-only STATUS current DESCRIPTION “Server’s serial number (used for license keys).” ::= { cfgProdInfoHardwareInfo 2 } -- dma.2.1.1.1.
DMA Operations Guide The Polycom DMA System MIB -- dma.2.1.2 cfgServer OBJECT-IDENTITY STATUS current DESCRIPTION “Configuration applied to the server from which data is being retrieved.” ::= { dmaConfig 2 } -- dma.2.1.2.1 cfgNetwork OBJECT-IDENTITY STATUS current DESCRIPTION “Contains info about the server’s network settings.” ::= { cfgServer 1 } -- dma.2.1.2.1.1 cfgNetworkHostname OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-only STATUS current DESCRIPTION “The hostname configured for the server.
The Polycom DMA System MIB cfgIfEnabled cfgIfMACAddress cfgIfIPv4Address cfgIfIPv4SubnetMask cfgIfIPv4Gateway cfgIfIPv6Address cfgIfIPv6PrefixLength Polycom DMA System SNMP Support TruthValue, DisplayString, IpAddress, IpAddress, IpAddress, Ipv6Address, Unsigned32 } -- dma.2.1.2.1.3.1.1 cfgIfIndex OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS not-accessible STATUS current DESCRIPTION “cfgInterfacesTable index.” ::= { cfgInterfacesEntry 1 } -- dma.2.1.2.1.3.1.
DMA Operations Guide The Polycom DMA System MIB cfgIfIPv4SubnetMask OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-only STATUS current DESCRIPTION “IPv4 subnet mask assigned to this interface.” ::= { cfgInterfacesEntry 6 } -- dma.2.1.2.1.3.1.7 cfgIfIPv4Gateway OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-only STATUS current DESCRIPTION “IPv4 gateway assigned to this interface.” ::= { cfgInterfacesEntry 7 } -- dma.2.1.2.1.3.1.
The Polycom DMA System MIB Polycom DMA System SNMP Support cfgCsTerritoriesCount OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION “Number of indexed entries in cfgCsTerritoriesTable.” ::= { cfgCsSiteTopology 1 } -- dma.2.1.3.1.1.2 cfgCsTerritoriesTable OBJECT-TYPE SYNTAX SEQUENCE OF CfgCsTerritoriesEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION “Configured territories.” ::= { cfgCsSiteTopology 2 } -- dma.2.1.3.1.1.2.
DMA Operations Guide The Polycom DMA System MIB SYNTAX GeneralString MAX-ACCESS read-only STATUS current DESCRIPTION “Cluster assigned primary responsibility for this territory.” ::= { cfgCsTerritoriesEntry 3 } -- dma.2.1.3.1.1.2.1.4 cfgCsTerritoryBackupCluster OBJECT-TYPE SYNTAX GeneralString MAX-ACCESS read-only STATUS current DESCRIPTION “Cluster assigned backup responsibility for this territory.” ::= { cfgCsTerritoriesEntry 4 } -- dma.2.1.3.1.
The Polycom DMA System MIB Polycom DMA System SNMP Support SYNTAX GeneralString MAX-ACCESS read-only STATUS current DESCRIPTION “Address of the Active Directory server.” ::= { cfgCsIntDirSvcMSActiveDirectory 3 } -- dma.2.1.3.1.2.1.1.4 cfgCsIntMSADUserId OBJECT-TYPE SYNTAX GeneralString MAX-ACCESS read-only STATUS current DESCRIPTION “User ID of the service account used to integrate with Active Directory.” ::= { cfgCsIntDirSvcMSActiveDirectory 4 } -- dma.2.1.3.1.2.
DMA Operations Guide The Polycom DMA System MIB -- dma.2.1.3.1.2.2.1.4 cfgCsIntMSExchUserId OBJECT-TYPE SYNTAX GeneralString MAX-ACCESS read-only STATUS current DESCRIPTION “User ID of the service account used to integrate with Exchange.” ::= { cfgCsIntCalMSExchange 4 } -- dma.2.1.3.1.2.3 cfgCsIntSiteTopology OBJECT-IDENTITY STATUS current DESCRIPTION “Configurations for site topology service integration.” ::= { cfgCsIntegrations 3 } -- dma.2.1.3.1.2.3.
The Polycom DMA System MIB Polycom DMA System SNMP Support -- dma.2.1.3.1.2.4.1 cfgCsIntNetBandwidthManagement OBJECT-IDENTITY STATUS current DESCRIPTION “Configurations for bandwidth management integrations.” ::= { cfgCsIntNetwork 1 } -- dma.2.1.3.1.2.4.1.1 cfgCsIntNetBWMgmtJuniperSRC OBJECT-IDENTITY STATUS current DESCRIPTION “Configuration for Juniper Networks SRC integration.” ::= { cfgCsIntNetBandwidthManagement 1 } -- dma.2.1.3.1.2.4.1.1.
DMA Operations Guide The Polycom DMA System MIB ::= { cfgCsIntNetBWMgmtJuniperSRC 5 } -- dma.2.1.3.2 cfgCsCluster OBJECT-IDENTITY STATUS current DESCRIPTION “Call server configuration specific to the cluster from which data is being retrieved.” ::= { cfgCallserver 2 } -- dma.2.1.3.2.1 cfgCsSignaling OBJECT-IDENTITY STATUS current DESCRIPTION “Signaling configuration for the cluster.” ::= { cfgCsCluster 1 } -- dma.2.1.3.2.1.1 cfgCsSgnlH323 OBJECT-IDENTITY STATUS current DESCRIPTION “H.
The Polycom DMA System MIB Polycom DMA System SNMP Support -- dma.2.1.3.2.1.2.1 cfgCsSgnlSIPEnabled OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-only STATUS current DESCRIPTION “True if SIP signaling is enabled.” ::= { cfgCsSgnlSIP 1 } -- dma.2.1.3.2.1.2.2 cfgCsSgnlSIPTCPPort OBJECT-TYPE SYNTAX PortNumber MAX-ACCESS read-only STATUS current DESCRIPTION “The configured TCP transport SIP port.” ::= { cfgCsSgnlSIP 2 } -- dma.2.1.3.2.1.2.
DMA Operations Guide The Polycom DMA System MIB DESCRIPTION “Status of DMA servers.” ::= { dmaStatus 1 } -- dma.2.2.1.1 stServerCount OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION “Number of indexed entries in the tables within stServers.” ::= { stServers 1 } -- dma.2.2.1.2 stIdentity OBJECT-IDENTITY STATUS current DESCRIPTION “Server identity statuses.” ::= { stServers 2 } -- dma.2.2.1.2.
The Polycom DMA System MIB Polycom DMA System SNMP Support stHWHostName OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-only STATUS current DESCRIPTION “Name of the server.” ::= { stHardwareInfoEntry 2 } -- dma.2.2.1.2.1.1.3 stHWSerialNumber OBJECT-TYPE SYNTAX GeneralString MAX-ACCESS read-only STATUS current DESCRIPTION “Server’s serial number.” ::= { stHardwareInfoEntry 3 } -- dma.2.2.1.2.
DMA Operations Guide The Polycom DMA System MIB MAX-ACCESS read-only STATUS current DESCRIPTION “Hostname of the server.” ::= { stVersionEntry 2 } -- dma.2.2.1.2.2.1.3 stVerVersion OBJECT-TYPE SYNTAX GeneralString MAX-ACCESS read-only STATUS current DESCRIPTION “Product version of the server.” ::= { stVersionEntry 3 } -- dma.2.2.1.2.3 stSystemInfoTable OBJECT-TYPE SYNTAX SEQUENCE OF StSystemInfoEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION “Server statuses.” ::= { stIdentity 3 } -- dma.2.2.1.
The Polycom DMA System MIB Polycom DMA System SNMP Support MAX-ACCESS read-only STATUS current DESCRIPTION “Hostname of the server.” ::= { stSystemInfoEntry 2 } -- dma.2.2.1.2.3.1.3 stSysInfoSystemDate OBJECT-TYPE SYNTAX DateAndTime MAX-ACCESS read-only STATUS current DESCRIPTION “Server’s current system date.” ::= { stSystemInfoEntry 3 } -- dma.2.2.1.2.3.1.4 stSysInfoUptime OBJECT-TYPE SYNTAX TimeTicks MAX-ACCESS read-only STATUS current DESCRIPTION “How long the server has been powered up.
DMA Operations Guide The Polycom DMA System MIB INDEX { stNetClusterAffilIndex } ::= { stNetClusterAffiliationTable 1 } StNetClusterAffiliationEntry ::= { stNetClusterAffilIndex stNetClusterAffilHostName stNetClusterAffilClusterName } SEQUENCE Unsigned32, DisplayString, DisplayString -- dma.2.2.1.3.1.1.1 stNetClusterAffilIndex OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS not-accessible STATUS current DESCRIPTION “stNetClusterAffiliationTable index.” ::= { stNetClusterAffiliationEntry 1 } -- dma.2.2.1.3.1.1.
The Polycom DMA System MIB StNetPrivateInterfaceEntry { stNetPvtIndex stNetPvtHostName stNetPvtInterfaceName stNetPvtLinkStatus stNetPvtMACAddress stNetPvtIPv4Address stNetPvtIPv6Address } Polycom DMA System SNMP Support ::= SEQUENCE Unsigned32, DisplayString, GeneralString, INTEGER, DisplayString, IpAddress, Ipv6Address -- dma.2.2.1.3.2.1.1 stNetPvtIndex OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS not-accessible STATUS current DESCRIPTION “stNetPrivateInterfaceTable index.
DMA Operations Guide The Polycom DMA System MIB DESCRIPTION “MAC address of the private network interface.” ::= { stNetPrivateInterfaceEntry 5 } -- dma.2.2.1.3.2.1.6 stNetPvtIPv4Address OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-only STATUS current DESCRIPTION “IPv4 address assigned to the private network interface.” ::= { stNetPrivateInterfaceEntry 6 } -- dma.2.2.1.3.2.1.
The Polycom DMA System MIB Polycom DMA System SNMP Support MAX-ACCESS not-accessible STATUS current DESCRIPTION “stNetManagementInterfaceTable index.” ::= { stNetManagementInterfaceEntry 1 } -- dma.2.2.1.3.3.1.2 stNetMgmtHostName OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-only STATUS current DESCRIPTION “Hostname of the server.” ::= { stNetManagementInterfaceEntry 2 } -- dma.2.2.1.3.3.1.
DMA Operations Guide The Polycom DMA System MIB STATUS current DESCRIPTION “IPv6 address assigned to the management network interface.” ::= { stNetManagementInterfaceEntry 7 } -- dma.2.2.1.3.4 stNetSignalingInterfaceTable OBJECT-TYPE SYNTAX SEQUENCE OF StNetSignalingInterfaceEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION “Information about the signaling network interfaces of servers.” ::= { stNetwork 4 } -- dma.2.2.1.3.4.
The Polycom DMA System MIB Polycom DMA System SNMP Support SYNTAX GeneralString MAX-ACCESS read-only STATUS current DESCRIPTION “Name of the network interface configured for signaling network.” ::= { stNetSignalingInterfaceEntry 3 } -- dma.2.2.1.3.4.1.4 stNetSgnlLinkStatus OBJECT-TYPE SYNTAX INTEGER { up(1), down(2) } MAX-ACCESS read-only STATUS current DESCRIPTION “Link status of the signaling network interface.” ::= { stNetSignalingInterfaceEntry 4 } -- dma.2.2.1.3.4.1.
DMA Operations Guide The Polycom DMA System MIB DESCRIPTION “CPU usage information for the servers.” ::= { stResources 1 } -- dma.2.2.1.4.1.1 stRsrcCPUUsageEntry OBJECT-TYPE SYNTAX StRsrcCPUUsageEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION “An entry in stRsrcCPUUsageTable.” INDEX { stRsrcCPUUsageIndex } ::= { stRsrcCPUUsageTable 1 } StRsrcCPUUsageEntry ::= SEQUENCE { stRsrcCPUUsageIndex stRsrcCPUUsageHostName stRsrcCPUUsageCPUUtilizationPct } Unsigned32, DisplayString, Unsigned32 -- dma.2.
The Polycom DMA System MIB Polycom DMA System SNMP Support -- dma.2.2.1.4.2.1 stRsrcMemoryUsageEntry OBJECT-TYPE SYNTAX StRsrcMemoryUsageEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION “An entry in stRsrcMemoryUsageTable.
DMA Operations Guide The Polycom DMA System MIB ::= { stRsrcMemoryUsageEntry 4 } -- dma.2.2.1.4.2.1.5 stRsrcMemUsageUsed OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION “System memory used by processes (MB).” ::= { stRsrcMemoryUsageEntry 5 } -- dma.2.2.1.4.2.1.6 stRsrcMemUsageFree OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION “System memory unused (MB).” ::= { stRsrcMemoryUsageEntry 6 } -- dma.2.2.1.4.
The Polycom DMA System MIB Polycom DMA System SNMP Support -- dma.2.2.1.4.3.1.2 stRsrcSwapHostName OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-only STATUS current DESCRIPTION “Hostname of the server.” ::= { stRsrcSwapSpaceEntry 2 } -- dma.2.2.1.4.3.1.3 stRsrcSwapTotal OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION “Total swap space allocated in the system (MB).” ::= { stRsrcSwapSpaceEntry 3 } -- dma.2.2.1.4.3.1.
DMA Operations Guide The Polycom DMA System MIB -- dma.2.2.1.4.4.1.1 stRsrcDiskIndex OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS not-accessible STATUS current DESCRIPTION “stRsrcDiskSpaceTable index.” ::= { stRsrcDiskSpaceEntry 1 } -- dma.2.2.1.4.4.1.2 stRsrcDiskHostName OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-only STATUS current DESCRIPTION “Hostname of the server.” ::= { stRsrcDiskSpaceEntry 2 } -- dma.2.2.1.4.4.1.
The Polycom DMA System MIB Polycom DMA System SNMP Support { stRsrcLogIndex stRsrcLogHostName stRsrcLogTotal stRsrcLogUsed stRsrcLogWarningThreshold stRsrcLogNextPurge Unsigned32, DisplayString, Unsigned32, Unsigned32, Unsigned32, DateAndTime } -- dma.2.2.1.4.5.1.1 stRsrcLogIndex OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS not-accessible STATUS current DESCRIPTION “stRsrcLogSpaceTable index.” ::= { stRsrcLogSpaceEntry 1 } -- dma.2.2.1.4.5.1.
DMA Operations Guide The Polycom DMA System MIB stRsrcLogNextPurge OBJECT-TYPE SYNTAX DateAndTime MAX-ACCESS read-only STATUS current DESCRIPTION “Date at which log archives will be subject to purging, based on age and configuration.” ::= { stRsrcLogSpaceEntry 6 } -- dma.2.2.2 stDevices OBJECT-IDENTITY STATUS current DESCRIPTION “Status of devices connecting to DMA systems.” ::= { dmaStatus 2 } -- dma.2.2.2.1 stMCUs OBJECT-IDENTITY STATUS current DESCRIPTION “Status of MCUs connecting to DMA systems.
The Polycom DMA System MIB stMCUStHasAlert stMCUStRecordingAvailable stMCUStIVRAvailable Polycom DMA System SNMP Support TruthValue, TruthValue, TruthValue } -- dma.2.2.2.1.2.1.1 stMCUStIndex OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS not-accessible STATUS current DESCRIPTION “stMCUStatusTable index.” ::= { stMCUStatusEntry 1 } -- dma.2.2.2.1.2.1.2 stMCUStName OBJECT-TYPE SYNTAX GeneralString MAX-ACCESS read-only STATUS current DESCRIPTION “Name of the MCU.” ::= { stMCUStatusEntry 2 } -- dma.2.2.2.1.2.1.
DMA Operations Guide The Polycom DMA System MIB STATUS current DESCRIPTION “True if the MCU can provide IVR services.” ::= { stMCUStatusEntry 6 } -- dma.2.2.2.1.3 stMCUVideoPortUsageTable OBJECT-TYPE SYNTAX SEQUENCE OF StMCUVideoPortUsageEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION “Video port usage information for configured MCUs.” ::= { stMCUs 3 } -- dma.2.2.2.1.3.
The Polycom DMA System MIB Polycom DMA System SNMP Support SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION “Total video ports available on the MCU.” ::= { stMCUVideoPortUsageEntry 3 } -- dma.2.2.2.1.3.1.4 stMCUVidUsageMCUUsed OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION “Video ports in use on the MCU.” ::= { stMCUVideoPortUsageEntry 4 } -- dma.2.2.2.1.3.1.
DMA Operations Guide The Polycom DMA System MIB STATUS current DESCRIPTION “An entry in stMCUVoicePortUsageTable.” INDEX { stMCUVoxUsageIndex } ::= { stMCUVoicePortUsageTable 1 } StMCUVoicePortUsageEntry ::= SEQUENCE { stMCUVoxUsageIndex Unsigned32, stMCUVoxUsageName GeneralString, stMCUVoxUsageMCUTotal Unsigned32, stMCUVoxUsageMCUUsed Unsigned32, stMCUVoxUsageDMATotal Unsigned32, stMCUVoxUsageDMAUsed Unsigned32 } -- dma.2.2.2.1.4.1.
The Polycom DMA System MIB Polycom DMA System SNMP Support MAX-ACCESS read-only STATUS current DESCRIPTION “Total voice ports on the MCU available to DMA.” ::= { stMCUVoicePortUsageEntry 5 } -- dma.2.2.2.1.4.1.6 stMCUVoxUsageDMAUsed OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION “Voice ports in use on the MCU by DMA.” ::= { stMCUVoicePortUsageEntry 6 } -- dma.2.2.2.
DMA Operations Guide The Polycom DMA System MIB } -- dma.2.2.2.2.2.1.1 stMCUPCConnStIndex OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS not-accessible STATUS current DESCRIPTION “stMCUPCConnectionStatusTable index.” ::= { stMCUPCConnectionStatusEntry 1 } -- dma.2.2.2.2.2.1.2 stMCUPCConnStName OBJECT-TYPE SYNTAX GeneralString MAX-ACCESS read-only STATUS current DESCRIPTION “Name of the MCU.” ::= { stMCUPCConnectionStatusEntry 2 } -- dma.2.2.2.2.2.1.
The Polycom DMA System MIB Polycom DMA System SNMP Support ::= { stMCUPCReliabilityStatsTable 1 } StMCUPCReliabilityStatsEntry ::= SEQUENCE { stMCUPCRelIndex Unsigned32, stMCUPCRelName GeneralString, stMCUPCRelClusterName DisplayString, stMCUPCRelDisconnects Unsigned32, stMCUPCRelCallFailureRate Unsigned32 } -- dma.2.2.2.2.3.1.1 stMCUPCRelIndex OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS not-accessible STATUS current DESCRIPTION “stMCUPCReliabilityStatsTable index.
DMA Operations Guide The Polycom DMA System MIB MAX-ACCESS read-only STATUS current DESCRIPTION “Current call failure rate observed by this cluster. This integer should be divided by 100 to get the intended value.” ::= { stMCUPCReliabilityStatsEntry 5 } -- dma.2.2.3 stClusters OBJECT-IDENTITY STATUS current DESCRIPTION “Information about clusters in the DMA supercluster.” ::= { dmaStatus 3 } -- dma.2.2.3.
The Polycom DMA System MIB Polycom DMA System SNMP Support DESCRIPTION “stClustersTable index.” ::= { stClustersEntry 1 } -- dma.2.2.3.2.1.2 stClClusterName OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-only STATUS current DESCRIPTION “Name of the cluster.” ::= { stClustersEntry 2 } -- dma.2.2.3.2.1.3 stClClusterStatus OBJECT-TYPE SYNTAX INTEGER { inService(1), busyOut(2), outOfService(3) } MAX-ACCESS read-only STATUS current DESCRIPTION “Service status of the cluster.
DMA Operations Guide The Polycom DMA System MIB MAX-ACCESS not-accessible STATUS current DESCRIPTION “stLicensesTable index.” ::= { stLicensesEntry 1 } -- dma.2.2.3.3.1.2 stLicClusterName OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-only STATUS current DESCRIPTION “Name of the cluster.” ::= { stLicensesEntry 2 } -- dma.2.2.3.3.1.3 stLicLicenseStatus OBJECT-TYPE SYNTAX INTEGER { valid(1), invalid(2), notInstalled(3) } MAX-ACCESS read-only STATUS current DESCRIPTION “State of the cluster’s license.
The Polycom DMA System MIB Polycom DMA System SNMP Support -- dma.2.2.4.1.1 stCsSiteTopology OBJECT-IDENTITY STATUS current DESCRIPTION “Supercluster-wide site topology status.” ::= { stCsSupercluster 1 } -- dma.2.2.4.1.1.1 stCsConfMgrTerritoriesCount OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION “Number of indexed entries in stCsConfMgrTerritoriesTable.” ::= { stCsSiteTopology 1 } -- dma.2.2.4.1.1.
DMA Operations Guide The Polycom DMA System MIB DESCRIPTION “Name of the territory.” ::= { stCsConfMgrTerritoriesEntry 2 } -- dma.2.2.4.1.2 stCsIntegrations OBJECT-IDENTITY STATUS current DESCRIPTION “Status for systems with which the DMA integrates.” ::= { stCsSupercluster 2 } -- dma.2.2.4.1.2.1 stCsIntDirectoryService OBJECT-IDENTITY STATUS current DESCRIPTION “Status for directory service integration.” ::= { stCsIntegrations 1 } -- dma.2.2.4.1.2.1.
The Polycom DMA System MIB Polycom DMA System SNMP Support stCsIntMSADCachingServer OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-only STATUS current DESCRIPTION “Name of server performing AD caching.” ::= { stCsIntDirSvcMSActiveDirectory 4 } -- dma.2.2.4.1.2.1.1.5 stCsIntMSADConnectionSecure OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-only STATUS current DESCRIPTION “True if connection to AD is encrypted.” ::= { stCsIntDirSvcMSActiveDirectory 5 } -- dma.2.2.4.1.2.1.1.
DMA Operations Guide The Polycom DMA System MIB -- dma.2.2.4.1.2.2.1.2 stCsIntMSExchSubscriptionStatus OBJECT-TYPE SYNTAX INTEGER { unknown(1), unavailable(2), error(3), disabled(4), ignoredNoEnterpriseDirectory(5), ignoredMailboxNotFound(6), authFailed(7), subscriptionPending(8), processingOk(9) } MAX-ACCESS read-only STATUS current DESCRIPTION “Status of Exchange mailbox subscription and processing.” ::= { stCsIntCalMSExchange 2 } -- dma.2.2.4.1.2.2.1.
The Polycom DMA System MIB Polycom DMA System SNMP Support -- dma.2.2.4.1.2.3.1 stCsIntSiteTopoPolycomCMA OBJECT-IDENTITY STATUS current DESCRIPTION “Status for Polycom CMA system integration.” ::= { stCsIntSiteTopology 1 } -- dma.2.2.4.1.2.3.1.1 stCsIntPlcmCMAEnabled OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-only STATUS current DESCRIPTION “True if CMA integration is enabled.” ::= { stCsIntSiteTopoPolycomCMA 1 } -- dma.2.2.4.1.2.3.1.
DMA Operations Guide The Polycom DMA System MIB stCsIntPlcmCMASites OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION “Number of sites provided by the CMA system.” ::= { stCsIntSiteTopoPolycomCMA 6 } -- dma.2.2.4.1.2.3.1.7 stCsIntPlcmCMASiteLinks OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION “Number of site links provided by the CMA system.” ::= { stCsIntSiteTopoPolycomCMA 7 } -- dma.2.2.4.1.2.3.1.
The Polycom DMA System MIB Polycom DMA System SNMP Support stCsDevices OBJECT-IDENTITY STATUS current DESCRIPTION “Status for devices connecting to the DMA call server.” ::= { stCallserver 2 } -- dma.2.2.4.2.1 stCsConfMgrMCUs OBJECT-IDENTITY STATUS current DESCRIPTION “Status for MCUs connecting to the DMA call server.” ::= { stCsDevices 1 } -- dma.2.2.4.2.1.
DMA Operations Guide The Polycom DMA System MIB -- dma.2.2.4.2.1.2.1.2 stCsCMMCUName OBJECT-TYPE SYNTAX GeneralString MAX-ACCESS read-only STATUS current DESCRIPTION “Name of the MCU.” ::= { stCsConfMgrMCUsEntry 2 } -- DMA USAGE -- dma.2.3 dmaUsage OBJECT-IDENTITY STATUS current DESCRIPTION “Contains usage data for the DMA system.” ::= { dmaMonitoring1 3 } -- dma.2.3.1 useConfHistory OBJECT-IDENTITY STATUS current DESCRIPTION “Contains conference history data.” ::= { dmaUsage 1 } -- dma.2.3.1.
The Polycom DMA System MIB Polycom DMA System SNMP Support STATUS current DESCRIPTION “An entry in useCHMaxPartsLast60MinutesTable.
DMA Operations Guide The Polycom DMA System MIB SYNTAX MAX-ACCESS STATUS DESCRIPTION Unsigned32 read-only current “Maxmimum number of concurrent ad-hoc calls recorded on the cluster during the specified one-minute interval.” ::= { useCHMaxPartsLast60MinutesEntry 5 } -- dma.2.3.1.1.2.1.
The Polycom DMA System MIB Polycom DMA System SNMP Support } -- dma.2.3.1.1.4.1.1 useCHMaxParts24HrIndex OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS not-accessible STATUS current DESCRIPTION “useCHMaxPartsLast24HoursTable index.” ::= { useCHMaxPartsLast24HoursEntry 1 } -- dma.2.3.1.1.4.1.2 useCHMaxParts24HrClusterName OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-only STATUS current DESCRIPTION “Cluster in which the participant count entry was recorded.” ::= { useCHMaxPartsLast24HoursEntry 2 } -- dma.2.3.
DMA Operations Guide The Polycom DMA System MIB the cluster during the specified one-hour interval.” ::= { useCHMaxPartsLast24HoursEntry 6 } -- dma.2.3.1.1.5 useCHMaxPartsLast180DaysCount OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION “Number of indexed entries in useCHMaxPartsLast180DaysTable.” ::= { useConfHistoryMaximumParticipants 5 } -- dma.2.3.1.1.
The Polycom DMA System MIB Polycom DMA System SNMP Support MAX-ACCESS read-only STATUS current DESCRIPTION “Cluster in which the participant count entry was recorded.” ::= { useCHMaxPartsLast180DaysEntry 2 } -- dma.2.3.1.1.6.1.3 useCHMaxParts180DaysTimestamp OBJECT-TYPE SYNTAX DateAndTime MAX-ACCESS read-only STATUS current DESCRIPTION “Time at which the participant count entry was recorded.” ::= { useCHMaxPartsLast180DaysEntry 3 } -- dma.2.3.1.1.6.1.
DMA Operations Guide The Polycom DMA System MIB ::= { useCurrentConferences 1 } -- dma.2.3.2.1.1 useConfMgrUsageCount OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION “Number of indexed entries in useConfMgrUsageTable.” ::= { useCurrentConfsConfManagerUsage 1 } -- dma.2.3.2.1.2 useConfMgrUsageTable OBJECT-TYPE SYNTAX SEQUENCE OF UseConfMgrUsageEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION “Usage information (conferences, calls, etc.
The Polycom DMA System MIB Polycom DMA System SNMP Support useCMUsageClusterName OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-only STATUS current DESCRIPTION “Name of the cluster in which the usage data was recorded.” ::= { useConfMgrUsageEntry 2 } -- dma.2.3.2.1.2.1.3 useCMUsageActiveConfs OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION “Number of active conferences being serviced by the cluster.” ::= { useConfMgrUsageEntry 3 } -- dma.2.3.2.1.2.1.
DMA Operations Guide The Polycom DMA System MIB MAX-ACCESS read-only STATUS current DESCRIPTION “Number of voice ports used in the cluster.” ::= { useConfMgrUsageEntry 8 } -- dma.2.3.2.1.2.1.9 useCMUsageLocalUsers OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION “Number of local users in the cluster’s database.” ::= { useConfMgrUsageEntry 9 } -- dma.2.3.2.1.2.1.
The Polycom DMA System MIB Polycom DMA System SNMP Support useDevRegistrationsEntry OBJECT-TYPE SYNTAX UseDevRegistrationsEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION “An entry in useDevRegistrationsTable.
DMA Operations Guide The Polycom DMA System MIB useDevRegFailedEndpointRegLast24Hours OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION “Number of registration attempts that resulted in failure over the last 24 hours, as determined by retained registration history.” ::= { useDevRegistrationsEntry 5 } -- DMA ALERTS -- dma.2.4 dmaAlerts OBJECT-IDENTITY STATUS current DESCRIPTION “Contains alert data for the DMA system.” ::= { dmaMonitoring1 4 } -- dma.2.4.
The Polycom DMA System MIB alActAlertIndex alActAlertID alActAlertTimestamp alActAlertCode alActAlertSeverity alActAlertDescription Polycom DMA System SNMP Support Unsigned32, GeneralString, DateAndTime, Unsigned32, INTEGER, OCTET STRING } -- dma.2.4.1.2.1.1 alActAlertIndex OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS not-accessible STATUS current DESCRIPTION “alActiveAlertsTable index.” ::= { alActiveAlertsEntry 1 } -- dma.2.4.1.2.1.
DMA Operations Guide The Polycom DMA System MIB alActAlertDescription OBJECT-TYPE SYNTAX OCTET STRING MAX-ACCESS read-only STATUS current DESCRIPTION “Text of the alert message.” ::= { alActiveAlertsEntry 6 } -- DMA NOTIFICATIONS -- dma.2.5 dmaNotifications OBJECT-IDENTITY STATUS current DESCRIPTION “DMA alert notifications.” ::= { dmaMonitoring1 5 } -- dma.2.5.1 ntfObjects OBJECT-IDENTITY STATUS current DESCRIPTION “Objects that will be included in alert notifications.” ::= { dmaNotifications 1 } -- dma.
The Polycom DMA System MIB Polycom DMA System SNMP Support STATUS current DESCRIPTION “Severity of the alert.” ::= { ntfObjects 4 } -- dma.2.5.1.5 ntfObjAlertDescription OBJECT-TYPE SYNTAX OCTET STRING MAX-ACCESS accessible-for-notify STATUS current DESCRIPTION “Text of the alert message.” ::= { ntfObjects 5 } -- dma.2.5.2 ntfAlertNotifications OBJECT-IDENTITY STATUS current DESCRIPTION “Contains alert notification objects.” ::= { dmaNotifications 2 } -- dma.2.5.2.
DMA Operations Guide The Polycom DMA System MIB ::= { ntfAlertNotificationObjects 1002 } -- dma.2.5.2.0.1003 ntfAlertClusterOrphan NOTIFICATION-TYPE OBJECTS { ntfObjAlertID, ntfObjAlertTimestamp, ntfObjAlertCode, ntfObjAlertSeverity, ntfObjAlertDescription } STATUS current DESCRIPTION “A cluster’s replication link is no longer valid.” ::= { ntfAlertNotificationObjects 1003 } -- dma.2.5.2.0.
The Polycom DMA System MIB Polycom DMA System SNMP Support ntfObjAlertTimestamp, ntfObjAlertCode, ntfObjAlertSeverity, ntfObjAlertDescription } STATUS current DESCRIPTION “A territory with both a primary and backup cluster configured is inactive because neither cluster is in a viable state.” ::= { ntfAlertNotificationObjects 1101 } -- dma.2.5.2.0.
DMA Operations Guide The Polycom DMA System MIB STATUS current DESCRIPTION “A territory with a primary and backup cluster configured is currently running on its backup cluster.” ::= { ntfAlertNotificationObjects 1104 } -- dma.2.5.2.0.2001 ntfAlertCMAUser NOTIFICATION-TYPE OBJECTS { ntfObjAlertID, ntfObjAlertTimestamp, ntfObjAlertCode, ntfObjAlertSeverity, ntfObjAlertDescription } STATUS current DESCRIPTION “An error occurred while attempting to synchronize data to the Polycom CMA system.
The Polycom DMA System MIB Polycom DMA System SNMP Support -- dma.2.5.2.0.2102 ntfAlertEntDirNoConfRooms NOTIFICATION-TYPE OBJECTS { ntfObjAlertID, ntfObjAlertTimestamp, ntfObjAlertCode, ntfObjAlertSeverity, ntfObjAlertDescription } STATUS current DESCRIPTION “After successfully updating user and group data from the Active Directory server, no conference rooms were generated.” ::= { ntfAlertNotificationObjects 2102 } -- dma.2.5.2.0.
DMA Operations Guide The Polycom DMA System MIB { ntfObjAlertID, ntfObjAlertTimestamp, ntfObjAlertCode, ntfObjAlertSeverity, ntfObjAlertDescription } STATUS current DESCRIPTION “The user and group data cache cannot be updated from the Active Directory server because the primary cluster for the responsible territory is not in a viable state and no backup cluster is configured.” ::= { ntfAlertNotificationObjects 2105 } -- dma.2.5.2.0.
The Polycom DMA System MIB Polycom DMA System SNMP Support ntfObjAlertSeverity, ntfObjAlertDescription } STATUS current DESCRIPTION “The primary cluster servicing the territory responsible for Exchange integration is not in a viable state; the backup cluster is currently assuming this duty.” ::= { ntfAlertNotificationObjects 2201 } -- dma.2.5.2.0.
DMA Operations Guide The Polycom DMA System MIB STATUS current DESCRIPTION “No signaling interface is enabled for the cluster; calls to the cluster cannot be processed.” ::= { ntfAlertNotificationObjects 3001 } -- dma.2.5.2.0.3101 ntfAlertCertExpired NOTIFICATION-TYPE OBJECTS { ntfObjAlertID, ntfObjAlertTimestamp, ntfObjAlertCode, ntfObjAlertSeverity, ntfObjAlertDescription } STATUS current DESCRIPTION “The cluster’s server certificate has expired.” ::= { ntfAlertNotificationObjects 3101 } -- dma.2.5.2.0.
The Polycom DMA System MIB Polycom DMA System SNMP Support { ntfObjAlertID, ntfObjAlertTimestamp, ntfObjAlertCode, ntfObjAlertSeverity, ntfObjAlertDescription } STATUS current DESCRIPTION “One or more CA certificates on the cluster has expired.” ::= { ntfAlertNotificationObjects 3104 } -- dma.2.5.2.0.
DMA Operations Guide The Polycom DMA System MIB DESCRIPTION “An invalid license key is installed on the cluster.” ::= { ntfAlertNotificationObjects 3202 } -- dma.2.5.2.0.3301 ntfAlertNetworkSingleNodeDetected NOTIFICATION-TYPE OBJECTS { ntfObjAlertID, ntfObjAlertTimestamp, ntfObjAlertCode, ntfObjAlertSeverity, ntfObjAlertDescription } STATUS current DESCRIPTION “A cluster is configured to have two servers, but communication between the two servers is not working.
The Polycom DMA System MIB Polycom DMA System SNMP Support { ntfObjAlertID, ntfObjAlertTimestamp, ntfObjAlertCode, ntfObjAlertSeverity, ntfObjAlertDescription } STATUS current DESCRIPTION “The public management (or combined) network interface has a problem.” ::= { ntfAlertNotificationObjects 3304 } -- dma.2.5.2.0.
DMA Operations Guide The Polycom DMA System MIB DESCRIPTION “The age of older log archives on the server is approaching the configured retention period and will be subject to purging.” ::= { ntfAlertNotificationObjects 3402 } -- dma.2.5.2.0.
The Polycom DMA System MIB Polycom DMA System SNMP Support -- dma.2.5.2.0.3406 ntfAlertResourceCPUOver75Percent NOTIFICATION-TYPE OBJECTS { ntfObjAlertID, ntfObjAlertTimestamp, ntfObjAlertCode, ntfObjAlertSeverity, ntfObjAlertDescription } STATUS current DESCRIPTION “The server’s CPU usage is exceptionally high.” ::= { ntfAlertNotificationObjects 3406 } -- dma.2.5.2.0.
DMA Operations Guide The Polycom DMA System MIB ntfObjAlertDescription } STATUS current DESCRIPTION “The server has never completed a full system scan.” ::= { ntfAlertNotificationObjects 3503 } -- dma.2.5.2.0.3601 ntfAlertDataSyncVersion NOTIFICATION-TYPE OBJECTS { ntfObjAlertID, ntfObjAlertTimestamp, ntfObjAlertCode, ntfObjAlertSeverity, ntfObjAlertDescription } STATUS current DESCRIPTION “The cluster contains servers running different versions of the DMA software.
The Polycom DMA System MIB Polycom DMA System SNMP Support -- dma.2.5.2.0.3604 ntfAlertDataSyncADConfRooms NOTIFICATION-TYPE OBJECTS { ntfObjAlertID, ntfObjAlertTimestamp, ntfObjAlertCode, ntfObjAlertSeverity, ntfObjAlertDescription } STATUS current DESCRIPTION “The cluster’s servers have different counts of enterprise conference rooms.” ::= { ntfAlertNotificationObjects 3604 } -- dma.2.5.2.0.
DMA Operations Guide The Polycom DMA System MIB ntfObjAlertDescription } STATUS current DESCRIPTION “An MCU is in the busied-out state.” ::= { ntfAlertNotificationObjects 4001 } -- dma.2.5.2.0.4002 ntfAlertMCUOutOfService NOTIFICATION-TYPE OBJECTS { ntfObjAlertID, ntfObjAlertTimestamp, ntfObjAlertCode, ntfObjAlertSeverity, ntfObjAlertDescription } STATUS current DESCRIPTION “An MCU is in the out-of-service state.” ::= { ntfAlertNotificationObjects 4002 } -- dma.2.5.2.0.
The Polycom DMA System MIB Polycom DMA System SNMP Support -- dma.2.5.2.0.6001 ntfAlertConfMgrNoTerritories NOTIFICATION-TYPE OBJECTS { ntfObjAlertID, ntfObjAlertTimestamp, ntfObjAlertCode, ntfObjAlertSeverity, ntfObjAlertDescription } STATUS current DESCRIPTION “No territories are configured to host conference rooms; the DMA conference manager cannot process conferences.” ::= { ntfAlertNotificationObjects 6001 } -- dma.2.5.2.0.
DMA Operations Guide ---- -- --- --- ---- ------- ---- --- 504 The Polycom DMA System MIB dmaConfig cfgIdentity cfgProductInfo cfgProdInfoManufacturer, cfgProdInfoModel, cfgProdInfoHardwareInfo cfgProdInfoHWModel, cfgProdInfoHWSerialNumber, cfgProdInfoSoftwareInfo cfgProdInfoSWVersion, cfgProdInfoSWExtendedVersion cfgProdInfoSWExtVerPlatformVersion, cfgProdInfoSWExtVerApplicationVersion, cfgServer cfgNetwork cfgNetworkHostname, cfgInterfacesCount, cfgInterfacesTable cfgInterfacesEntry cfgIfIndex
The Polycom DMA System MIB --- ---- ---- -- -- Polycom DMA System SNMP Support cfgCsIntMSExchUserId, cfgCsIntSiteTopology cfgCsIntSiteTopoPolycomCMA cfgCsIntPlcmCMAEnabled, cfgCsIntPlcmCMAServerAddress, cfgCsIntPlcmCMAUserId, cfgCsIntNetwork cfgCsIntNetBandwidthManagement cfgCsIntNetBWMgmtJuniperSRC cfgCsIntJuniperSRCEnabled, cfgCsIntJuniperSRCServerAddress, cfgCsIntJuniperSRCServerPort, cfgCsIntJuniperSRCUserId, cfgCsIntJuniperSRCSubscriberURI, cfgCsCluster cfgCsSignaling cfgCsSgnlH323 cfgCsSgnlH323
DMA Operations Guide --- ----- ---- ---- ---- ----- ---- 506 The Polycom DMA System MIB stSystemInfoEntry stSysInfoIndex stSysInfoHostName, stSysInfoSystemDate, stSysInfoUptime, stSysInfoTimeSource, stNetwork stNetClusterAffiliationTable stNetClusterAffiliationEntry stNetClusterAffilIndex stNetClusterAffilHostName, stNetClusterAffilClusterName, stNetPrivateInterfaceTable stNetPrivateInterfaceEntry stNetPvtIndex stNetPvtHostName, stNetPvtInterfaceName, stNetPvtLinkStatus, stNetPvtMACAddress, stNetP
The Polycom DMA System MIB ---- ---- ---- ------ ---- ---- Polycom DMA System SNMP Support stRsrcMemUsageBuffersAndCache, stRsrcMemUsageUsed, stRsrcMemUsageFree, stRsrcSwapSpaceTable stRsrcSwapSpaceEntry stRsrcSwapIndex stRsrcSwapHostName, stRsrcSwapTotal, stRsrcSwapUsed, stRsrcDiskSpaceTable stRsrcDiskSpaceEntry stRsrcDiskIndex stRsrcDiskHostName, stRsrcDiskTotal, stRsrcDiskUsed, stRsrcLogSpaceTable stRsrcLogSpaceEntry stRsrcLogIndex stRsrcLogHostName, stRsrcLogTotal, stRsrcLogUsed, stRsrcLogWarnin
DMA Operations Guide ----- ---- ----- ---- ---------- --- 508 The Polycom DMA System MIB stMCUVoxUsageDMAUsed, stMCUsPerCluster stMCUsPerClusterCount, stMCUPCConnectionStatusTable stMCUPCConnectionStatusEntry stMCUPCConnStIndex stMCUPCConnStName, stMCUPCConnStClusterName, stMCUPCConnStConnectionStatus, stMCUPCReliabilityStatsTable stMCUPCReliabilityStatsEntry stMCUPCRelIndex stMCUPCRelName, stMCUPCRelClusterName, stMCUPCRelDisconnects, stMCUPCRelCallFailureRate, stClusters stClustersCount, stCluste
The Polycom DMA System MIB Polycom DMA System SNMP Support stCsIntMSExchEnabled, stCsIntMSExchSubscriptionStatus, stCsIntMSExchIntegratingCluster, stCsIntMSExchIntegratingServer, stCsIntMSExchMailbox, stCsIntMSExchMeetingsToday, stCsIntSiteTopology stCsIntSiteTopoPolycomCMA stCsIntPlcmCMAEnabled, stCsIntPlcmCMAConnectionStatus, stCsIntPlcmCMALastContactDate, stCsIntPlcmCMATimeSinceLastRefresh, stCsIntPlcmCMATerritories, stCsIntPlcmCMASites, stCsIntPlcmCMASiteLinks, stCsIntPlcmCMAMPLSClouds, stCsIntNetwork
DMA Operations Guide --- ---- ------ ------ The Polycom DMA System MIB useCHMaxPartsLast24HoursEntry useCHMaxParts24HrIndex useCHMaxParts24HrClusterName, useCHMaxParts24HrTimestamp, useCHMaxParts24HrMaxSimultaneousCalls, useCHMaxParts24HrMaxAdHocCalls, useCHMaxParts24HrMaxPCOCalls, useCHMaxPartsLast180DaysCount, useCHMaxPartsLast180DaysTable useCHMaxPartsLast180DaysEntry useCHMaxParts180DaysIndex useCHMaxParts180DaysClusterName, useCHMaxParts180DaysTimestamp, useCHMaxParts180DaysMaxSimultaneousCalls,
The Polycom DMA System MIB ------ Polycom DMA System SNMP Support dmaAlerts alActiveAlerts alActiveAlertsCount, alActiveAlertsTable alActiveAlertsEntry alActAlertIndex alActAlertID, alActAlertTimestamp, alActAlertCode, alActAlertSeverity, alActAlertDescription } STATUS current DESCRIPTION “Conformance group for dmaAlerts.” ::= { dmaConformanceGroups 4 } -- .2.9.1.5.1 dmaConformanceNtfObjects -- .2.9.1.5.2 dmaConformanceNtfAlertNotifications -- .2.9.1.
DMA Operations Guide The Polycom DMA System MIB ntfAlertClusterUnreachable, ntfAlertClusterPendingReplication, ntfAlertTerritoryNotActiveBothClustersNotInService, ntfAlertTerritoryNotActiveClusterNotInService, ntfAlertTerritoryNoClustersAssigned, ntfAlertTerritoryPrimaryClusterNotInService, ntfAlertCMAUser, ntfAlertCMAUnreachable, ntfAlertEntDirIntegrationFailed, ntfAlertEntDirNoConfRooms, ntfAlertEntDirPrimaryClusterNotInService, ntfAlertEntDirNotAvailable, ntfAlertEntDirNotAvailableNoBackup, ntfAlertEnt
The Polycom DMA System MIB Polycom DMA System SNMP Support ntfAlertConfMgrNoTerritories, ntfAlertCallServerRegistrationDataIncomplete } STATUS current DESCRIPTION “Conformance group for alert notifications.” ::= { dmaConformanceNotifications 2 } -- .2.10 dmaCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION “Specification of MIB object compliance.” MODULE POLYCOM-DMA-MIB MANDATORY-GROUPS { -- .2.9.1.1 dmaConformanceConfig, -- .2.9.1.2 dmaConformanceStatus, -- .2.9.1.3 dmaConformanceUsage, -- .2.9.1.
DMA Operations Guide 514 The Polycom DMA System MIB Polycom, Inc.
Index A access, system interface 8 account lockout configuration 57 activation keys 67 active calls list 75 Active Directory 30, 147 integration procedure 153 integration report 394 queries 160 settings 149 add alias dialog 242 add conference templates dialog 184 add device authentication dialog 246 add direct dial virtual entry queue dialog 206 add hunt group dialog 241 add MCU dialog 125 add MCU pool dialog 139 add MCU pool order dialog 143 add virtual entry queue dialog 205 adding conference passcodes 15
DMA Operations Guide CMA system integration 169, 171 CMA system page, Polycom 170 commands, system monitoring 359 conference cascading 182 history 386 IVR service 181 settings 177 conference manager overview 1 setup 177 conference passcodes adding 158 editing 302 enterprise errors report 400 enterprise users 158 export errors data 402 conference room add or edit 303 errors report 398 export errors data 400 procedures 315 conference templates about 179 add dialog 184 assigning to enterprise groups 322 casca
Index enterprise passcode errors report 400 enterprise passcodes export errors data 402 entry queue, direct dial virtual add 206 entry queue, direct virtual edit 207 entry queue, virtual 204 add 205 edit 207 errors conference room 398 enterprise passcode 400 Exchange Server integration 164 integration procedure 167 exclusion, site-to-site 281 expansion, system 377, 378, 379 export CDR data 388 enterprise passcode errors data 402 invalid conference rooms data 400 network usage data 403 export history 385, 3
DMA Operations Guide L layout, video frame 201 LDAP 30, 147, 149, 153 leave CMA 172 license the system 24 licenses open source software 12 system 67 local cluster configuration 71 logging configuration 70 login banner 58 login failure, settings 57 login policy settings 55 login sessions 324 login sessions, settings 56 logs, system 356 M maintenance overview 327 recommended 329 management certificate 36 device 75 MCU 119 overview 327 system 327 users and groups 291 MCU add dialog 125 edit dialog 128 list 11
Index change dialog 325 permissions, user 292 ping command 359 Polycom CMA system integration 169 procedures 172 Polycom CMA system page 170 Polycom Conferencing meetings 164 pool orders, MCU add 143 edit 144 list 141 procedures 145 pools, MCU add 139 edit 139 list 137 procedures 140 port usage 6 postliminary scripts, sample 236 prefix dialing 177 service 256 preliminary scripts, sample 236 priority, template 181 procedures Active Directory integration 153 certificates 40 CMA integration 172 conference roo
DMA Operations Guide system 33 select layout dialog 201 server adding 377, 378, 379 replacing 380 settings 61 session and resource controller (SRC) 173 session configuration 56 sessions, login 324 settings Active Directory integration 149 calendaring 166 cluster 61 conference 177 history retention 261 logging 70 network 62 signaling 67 time 66 settings dialog 7 setup conference manager 177 conference templates 31 initial 21 MCUs 27 security 26 supercluster 211 testing 31 shared number dialing 204 add direc
Index reports 383 security 33 testing 31 time 66 views 8 working in 7 T templates, conference about 179 add dialog 184 assigning to enterprise groups 322 cascading 182 edit dialog 193 IVR service 181 list 183 priority 181 procedures 202 setting up 31 types of 179 video frame layout 201 territory add 283 edit 284 list 282 testing initial setup 31 text size 7 time settings 66 tools, system management 359 top command 359 topology, site 263, 287 traceroute command 359 Trusted Root CA install 41 remove 45 two-s
DMA Operations Guide 522 Polycom, Inc.
