Supported Versions
REST API: REST API V1 and V2
Poly Trio 8800

Introduction

Polycom Trio is a modern conference room smartphone. Integrating our legendary voice quality, with powerful video and content performance, Polycom Trio can easily transform conference rooms of all sizes into collaborative, hassle-free team environments. Polycom-Trio helps you:

  • Discover and monitor your Polycom devices.
  • Check device availability and reliability.

Pre-requisites

OpsRamp Classic Gateway 12.0.1 and above.

Default monitoring configurations

Poly-Trio application has default Global Device Management Policies, Global Templates, Global Monitors and Global metrics in OpsRamp. You can customize these default monitoring configurations as per your business use cases by cloning respective Global Templates and Global Device Management Policies. OpsRamp recommends doing this activity before installing the application 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-Trio. You can find those 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-trio Poly Trio - 1 (i.e, appName = poly-trio, nativeType = Poly Trio, version = 1)

  2. Default Global Templates

    OpsRamp has a Global Template for each Native Type of POLY-TRIO. You can find those templates at Setup -> Monitoring -> Templates -> Search with suggested names in global scope. Each template follows below naming convention:

    {appName nativeType 'Template' - version}

    Ex: poly-trio Poly Trio Template - 1 (i.e, appName = poly-trio, nativeType = Poly Trio, version = 1)

  3. Default Global Monitors

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

    {monitorKey appName nativeType - version}

    Ex: Poly Trio Monitor poly-trio Poly Trio 1 (i.e, monitorKey = Poly Trio Monitor, appName = poly-trio nativeType = Poly Trio, 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 Trio 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.
Host Name / IP AddressProvide the Host Name / IP Address.
Resource Instance NameEnter the resource instance name
PortPort
Note: By default 443 is added.
CredentialsSelect the credentials from the drop-down list.
Note: Click + Add to create a credential.

Notes:

  • By default the isSecure checkbox is selected.
  • 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 Polycom-Trio details

The Polycom Trio 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 Polycom-Trio.

Linux Install Integration
Linux Install Integration

Supported metrics

Metric NameMetric Display NameUnitDescription
polycom_trio_Current_CPU_UsagePolycom Trio Current CPU UtilizationpercentThe actual CPU Utilization at a specific point in time.
polycom_trio_Average_CPU_UsagePolycom Trio Average CPU UtilizationpercentProvides device average CPU usage.
polycom_trio_Used_MemoryPolycom Trio Memory Used in MbytesmegabytesProvides the amount of memory used.
polycom_trio_Free_MemoryPolycom Trio Free Memory in MbytesmegabytesProvides device-free memory details.
polycom_trio_Memory_UtilizationPolycom Trio Memory UtilizationpercentProvides device memory usage details.
polycom_trio_Packets_LostPolycom Trio Call Data Packets LostcountProvides packets lost information while transmission
polycom_trio_JitterPolycom Trio Jitter Delay TimemillisecondsVariation in the time delay between the signal transmission and its receipt over a network connection.
polycom_trio_Max_JitterPolycom Trio Max Jitter Delay TimemillisecondsMaximum variation in the time delay between the signal transmission and its receipt over a network connection.
polycom_trio_LatencyPolycom Trio Call LatencymillisecondsThe time taken for the data to get to the destination across the network.
polycom_trio_RxMOSCQPolycom Trio Remote Conversational MOS ScorecountThe ranking or score of the quality of voice and video sessions geted from remote conversational quality tests.
polycom_trio_TxMOSCQPolycom Trio Local Conversational MOS ScorecountThe ranking or score of the quality of voice and video sessions geted from local conversational quality tests.
polycom_trio_RxMOSLQPolycom Trio Remote Listening MOS ScorecountThe ranking or score of the quality of voice and video sessions geted from remote listening quality tests.
polycom_trio_TxMOSLQPolycom Trio Local Listening MOS ScorecountThe ranking or score of the quality of voice and video sessions geted from local listening quality tests.
polycom_trio_Calendar_Connection_StatusPolycom Trio Calendar Connection StatusProvides calendar service connection status.
polycom_trio_AppStatePolycom Trio AppStateProvides polycom device state info.

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 existed critical alert is recovered.
  • Macro replacement limitation (i.e, customisation for threshold breach alert subject, description).
  • Application cannot control monitoring pause/resume actions based on above alerts.
  • Metrics can be used to monitor Poly Trio resources and can generate alerts based on the threshold values.
  • 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.