Poly Group Series devices

Application Version and Upgrade Details

Introduction

Polycom RealPresence Group Series is the only standards based group video conferencing system that is certified with Skype for Business and Office 365. This native integration, without expensive and complex gateways, extends the benefits of your Skype for Business investment while delivering an unmatched quality of experience from your meeting rooms.

The Skype for Business interface is available on RealPresence Touch for an experience that is consistent with the workflow users are already familiar with. Polycom RealPresence Group Series has certified interoperability with Zoom and BlueJeans.

This interoperability delivers a simple one-touch meeting experience, enterprise calendar integration and the best in-room meeting experience in the market today for subscribers of cloud video services.

Prerequisites

• OpsRamp Classic Gateway 14.0.0 and above.
• OpsRamp NextGen Gateway 14.0.0 and above.
  Note: OpsRamp recommends using the latest Gateway version for full coverage of recent bug fixes, enhancements, etc.

Default Monitoring Configurations

Poly-Group-Series have default Global Device Management Policies, Global Templates, Global Monitors and Global metrics in OpsRamp. Users can customize these default monitoring configurations as per their business use cases by cloning respective global templates and global Device Management Policies. OpsRamp recommends performing this activity before installing the app to avoid noise alerts and data.

1. Default Global Device Management Policies

   OpsRamp has a Global Device Management Policy for each Native Type of Poly Group Series. You can find these Device Management Policies at Setup > Resources > Device Management Policies, search with suggested names in global scope. Each Device Management Policy follows below naming convention:

   {appName nativeType - version}

   Ex: poly-group-series Poly Group Series - 1 (i.e, appName = poly-group-series , nativeType = Poly Group Series , version = 1)

2. Default Global Templates

   OpsRamp has a Global template for each Native Type of Poly-Group-Series. You can find these templates at Setup > Monitoring > Templates, search with suggested names in global scope. Each template follows below naming convention:

   {appName nativeType 'Template' - version}

   Ex: poly-group-series Poly Group Series Template - 1(i.e, appName = poly-group-series , nativeType = Poly Group Series,version=1)

3. Default Global Monitors

   OpsRamp has a Global Monitors for each Native Type which has monitoring support. You can find these monitors at Setup > Monitoring > Monitors, search with suggested names in global scope. Each Monitors follows below naming convention:

   {monitorKey appName nativeType - version}

   Ex: Poly Group Series Monitor poly-group-series Poly Group Series1 (i.e, monitorKey = Poly Group Series Monitor, appName = poly-group-series , nativeType = Poly Group Series, version = 1)

Configure and Install the Poly Group Series Integration

1. From All Clients, select a client.
2. Go to Setup > Account.
3. Select the Integrations and Apps tab.
4. The Installed Integrations page, where all the installed applications are displayed.
   Note: If there are no installed applications, it will navigate to the ADD APP page.
5. Click + ADD on the Installed Integrations page. The Available Integrations and Apps page displays all the available applications along with the newly created application with the version.
   Note: You can even search for the application using the search option available. Also you can use the All Categories option to search.

6. Click ADD in the Poly Group Series application.
7. In the Configurations page, click + ADD. The Add Configuration page appears.
8. Enter the below mentioned BASIC INFORMATION:

Notes:

• IP Address/Host Name and Port should be accessible from Gateway.
• Select App Failure Notifications; if turned on, you will be notified in case of an application failure that is, Connectivity Exception, Authentication Exception.

9. Select the below mentioned Custom Attribute:

Note: The custom attribute that you add here will be assigned to all the resources that are created by the integration. You can add a maximum of five custom attributes (key and value pair).

10. In the RESOURCE TYPE section, select:
    • ALL: All the existing and future resources will be discovered.
    • SELECT: You can select one or multiple resources to be discovered.
11. In the DISCOVERY SCHEDULE section, select Recurrence Pattern to add one of the following patterns:
    • Minutes
    • Hourly
    • Daily
    • Weekly
    • Monthly
12. Click ADD.

Now the configuration is saved and displayed on the configurations page after you save it.
Note: From the same page, you may Edit and Remove the created configuration.

13. Click NEXT
14. Below are the optional steps you can perform on the Installation page.

• Under the ADVANCED SETTINGS, Select the Bypass Resource Reconciliation option, if you wish to bypass resource reconciliation when encountering the same resources discovered by multiple applications.

  Note: If two different applications provide identical discovery attributes, two separate resources will be generated with those respective attributes from the individual discoveries.

• Click +ADD to create a new collector by providing a name or use the pre-populated name.

15. Select an existing registered profile.

16. Click FINISH.

The integration is now installed and displayed on the Installed Integration page. Use the search field to find the installed application.

Modify the Configuration

• See Modify an Installed Integration or Application article.

  Note: Select the Poly Group Series application.

View the Poly Group Series device details

The Poly Group Series integration is displayed in the Infrastructure > Resources > Network Devices > VoIP. You can navigate to the Attributes tab to view the discovery details, and Metrics tab to view the metric details for Poly Group Series.

Supported Alert Custom Macros

Customize the alert subject and description with below macros then it will generate alert based on customisation.
Supported macros keys:

Supported Metrics

Risks, Limitations & Assumptions

• Application can handle Critical/Recovery failure notifications for below two cases when user enables App Failure Notifications in configuration:
  • Connectivity Exception
  • Authentication Exception
• Application will not send any duplicate/repeat failure alert notification until the already existing critical alert is recovered.
• Support for Macro replacement for threshold breach alerts (i.e, customisation for threshold breach alert’s subject, description).
• No support of showing activity log and applied time.
• This application supports both Classic Gateway and NextGen Gateway.