Supported Versions
Poly Group Series (310,500,700) Conference Systems

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 12.0.1 and above.

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 integration

  1. From All Clients, select a client.
  2. Go to Setup > Integrations and Apps.
  3. Click Manage Apps.
    Notes:
    • If there are already installed applications, it will redirect to the INSTALLED APPS page, where all the installed applications are displayed.
    • If there are no installed applications, it will navigate to the ADD APP page.
Linux Install Integration
  1. Click + ADD on the INSTALLED APP page. The ADD APP 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.
Linux Install Integration
  1. Click ADD in the Poly Group Series application.
  2. In the Configurations page, click + ADD. The Add Configuration page appears.
  3. Enter the below mentioned BASIC INFORMATION:
FunctionalityDescription
NameEnter the name for the configuration.
IP Address/Host NameIP address/host name of the target.
PortPort

Note: By default 161 is added.
SNMP VersionSelect the SNMP Version from the drop down.

Note: By default version2c is added.
Community StringEnter the community string information

Note: Select App Failure Notifications; if turned on, you will be notified in case of an application failure that is, Connectivity Exception, Authentication Exception.

  1. 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.
  2. In the DISCOVERY SCHEDULE section, select Recurrence Pattern to add one of the following patterns:
    • Minutes
    • Hourly
    • Daily
    • Weekly
    • Monthly
  3. Click ADD.
Linux Install Integration
  1. 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.
  2. Click NEXT
  3. In the Installation page, select an existing registered gateway profile, and click FINISH.
Linux Install Integration

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

Modify the Configuration

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.

Linux Install Integration
Linux Install Integration

Supported Metrics

Metric NamesDisplay NameUnitsDescription
poly_group_CalendarSyncPoly Group Calendar SyncMonitors connection to calendar service. possible values 1:"Disabled" , 2:"Registered" , 3:"Error"
poly_group_ProvisioningStatusPoly Group Provisioning StatusMonitor connection to provisioning server. possible values 1:"Disabled" , 2:"Connected" , 3:"Error"

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.
  • No support for Macro replacement for threshold breach alerts (i.e, customisation for threshold breach alert’s subject, description).
  • Component level thresholds can be configured on each resource level.
  • No support of showing activity log and applied time.
  • No support for the option to get Latest snapshot metric.
  • Application is not compatible with Cluster Gateway.