Poly VoIP phones

Introduction

The Polycom VVX business VoIP phone is a modern four-line basic VoIP desk phone that delivers reliable performance and an enterprise grade sound quality.

The Poly CCX Business Media Phone is an entry-level, open-SIP device with a color touch-screen display that is certified for use with Microsoft Teams and Skype.

Pre-requisites

• OpsRamp Classic Gateway 12.0.1 and above.

Default monitoring configurations

Poly VOIP Phone application has default Global Device Management Policies, Global Templates, Global Monitors, and Global Metrics in OpsRamp. You can customize these default monitoring configurations as 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 VOIP Phone. 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-voip-phone Poly VOIP Phone - 1 (i.e, appName = poly-voip-phone, nativeType = Poly VOIP Phone, version = 1)

2. Default Global Templates

   OpsRamp has a Global Template for each Native Type of Poly VOIP Phone. 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-voip-phone Poly VOIP Phone Template - 1 (i.e, appName = poly-voip-phone, nativeType = Poly VOIP Phone, version = 1)

3. Default Global Monitors

   OpsRamp has a Global Monitors for each Native Type which has monitoring support. You can 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 VOIP Phone Monitor poly-voip-phone Poly VOIP Phone 1 (i.e, monitorKey = Poly VOIP Phone Monitor, appName = poly-voip-phone, nativeType = Poly VOIP Phone, 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.

4. 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.

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

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.

8. In the Custom Attributes section, select the custom attribute key and value from the dropdown boxes.
   Note:
   • The custom attribute that you add here will be assigned to all the resources that are created by the configuration.
   • You can add a maximum of 5 custom attributes (key and value pair).
   • The custom attribute that you add should be created at the client level.
9. 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.
10. In the DISCOVERY SCHEDULE section, select Recurrence Pattern to add one of the following patterns:
    • Minutes
    • Hourly
    • Daily
    • Weekly
    • Monthly
11. 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.

12. Click NEXT
13. In the Installation page, select an existing registered gateway profile, and click FINISH.

The application 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 VOIP Phone application.

View the Poly VoIP phones details

The Poly VoIP phones 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 VoIP phones.

Supported Alert Custom Macros

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

                                ${resource.name}

                                ${resource.ip}

                                ${resource.mac}

                                ${resource.aliasname}

                                ${resource.os}

                                ${resource.type}

                                ${resource.dnsname}

                                ${resource.alternateip}

                                ${resource.make}

                                ${resource.model}

                                ${resource.serialnumber}

                                ${resource.systemId}

                                ${Custome Attributes in the resource}

                                ${parent.resource.name}

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 existed critical alert is recovered.
• Support for Macro replacement for threshold breach alerts (i.e, customisation for threshold breach alert’s subject, description).
• Application cannot control monitoring pause/resume actions based on above alerts.
• Metrics can be used to monitor Poly VoIP phone 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.
• Support for the option to get Latest snapshot metric.