Supported Versions
REST API: REST API V1 and V2
Gateway version: 9.0 HF cluster gateway or higher.

The Polycom VVX 250 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 400 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.

Step 1: Install the integration

  1. From All Clients, choose a client.
  2. Go to Setup > Integrations > Integrations.
  3. From Available Integrations, select Adapter > Poly VVX/CCX Phone.
PolyVVX1
  1. From Install Poly VVX/CCX Phone, enter:
Object NameDescription
NameConfiguration name.
Gateway ProfileGateway management profile associated with the client.
  1. Click Install.
    The POLYCOM-VVX-CCX INTEGRATION page displays the installed integration in the CONFIGURATION section.
PolyVVX2

Step 2: Configure the integration

  1. From CONFIGURATION, click + Add.
  2. From the Create Adapter Configuration page, enter:
    • Name: Configuration name.
    • Protocol: Enter the value
    • HostName/IP Address: IP address or host name of the target.
    • Resource Instance Name: Update the resource name.
    • Notification Alerts: Select TRUE or FALSE.
      Note:
      • By default False is selected.
      • If you select TRUE, App will handle Critical/Recovery failure alert notifications for Connectivity, Authentication Exceptions.
  3. From the Credentials section, select Custom and enter the target device Username and Password.
  4. From the Resource Types & Metrics section, select the metrics and Availability you want.
    The Resource Types & Metrics section automatically displays the target device resource type such as VOIP.
  5. (Optional) Select the metrics from the Metrics section.
    Use Import to read in metrics and Export to save metrics locally.
  6. (Optional) From the Discovery Schedule section, select the checkbox to add a Recurrence Pattern. Choose one of the following intervals:
    • Minutes
    • Hourly
    • Daily
    • Weekly
    • Monthly
  7. From the Monitoring Schedule section, select target device monitoring frequency. The default frequency is set to 30 minutes.
  8. Click Save.
PolyVVX3

After saving the configuration, the resources are discovered and monitoring is done as specified in the configuration profile.
The configuration is saved and displayed on the page.

PolyVVX4

Step 3: View the Polycom VVX/CCX details details

The Polycom VVX/CCX integration is displayed in the Infrastructure > Resources > Network Devices > VoIP.

PolyVVX5

The basic information of the Polycom VVX/CCX is displayed under Attributes, you can check the below information:

Object NameDescription
Device TypeInformation of the device type.
Resource TypeInformation of the resource type.
Resource NameName of the resource.
Host NameName of the host device.
Alias NameThe name that you have created.
IP AddressIP address of the device.
MAC AddressThe MAC address of the device.
ModelModel number of the device.
App StatusInformation related to the status of the application.
Calendar AccountInformation related to calendar accounts.
Calendar Connection StatusStatus of the calendar connection.
FirmwareSoftware instructions residing in non-volatile storage that holds the content without power.

Supported metrics

Metric NameMetric Display NameUnit
polycom_vvx_ccx_Current_CPU_Utilization

Current CPU utilization of the device.
Current CPU Utilization%
polycom_vvx_ccx_Average_CPU_Utilization

Average CPU utilization of the device
Average CPU Utilization%
polycom_vvx_ccx_FreeMemory

Provides device free memory details
Free Memory in MbytesMB
polycom_vvx_ccx_MemoryUtilization

Provides device memory usage details
Memory Used in Mbytes%
polycom_vvx_ccx_UsedMemory

Provides the amount of memory used
Memory UsageMB
polycom_vvx_ccx_SIP_Status

Provides line info Registration Status. Possible outcomes are - 0 - Unregistered, 1 - Registered
SIP Status
polycom_vvx_ccx_PacketsLost

Provides packets lost information while transmission
Data Packets Lostcount
polycom_vvx_ccx_TxMOSLQ

The ranking/score of the quality of voice and video sessions obtained from local listening quality tests.
Local Conversational MOS Scorecount
polycom_vvx_ccx_RxMOSLQ

The ranking/score of the quality of voice and video sessions obtained from remote listening quality tests.
Remote Conversational MOS Scorecount
polycom_vvx_ccx_TxMOSCQ

The ranking/score of the quality of voice and video sessions obtained from local conversational quality tests.
Local Listening MOS Scorecount
polycom_vvx_ccx_RxMOSCQ

The ranking/score of the quality of voice and video sessions obtained from remote conversational quality tests.
Remote Listening MOS Scorecount
polycom_vvx_ccx_Latency

Time taken for some data to get to its destination across the network.
Latencyms
polycom_vvx_ccx_MaxJitter

Maximum Variation in time delay between when a signal is transmitted and when it's received over a network connection.
Max Jitter Timems
polycom_vvx_ccx_Jitter

Variation in time delay between when a signal is transmitted and when it's received over a network connection.
Jitter Timems
polycom_vvx_ccx_AppState

Provides polycom device state info. Possible outcomes are 0 - Unknown, 1 - AppStateMenu, 2 - AppStateCall.
AppState

Risks, Limitations & Assumptions

  • Component level threshold configuration is not possible.
  • Resource level metric threshold customization and frequency setting are not possible.
  • Usability issues in app configuration page while adding/editing.
  • Optional configuration parameters cannot be defined.
  • App upgrade is a manual process without version change