voip Integration
call-quality-by-zone-or-network (en)


ServicePilot voip-call-quality-by-zone-or-network


# Call Quality by Zone Or Network

Overview

The ServicePilot Call Quality by Zone Or Network package configures the ServicePilot Agent with general configuration parameters used across all VoIP packages.

Description

The Call Quality by Zone Or Network package configures the ServicePilot Agent with Call Quality Statistics configuration parameters. One Call Quality by Zone Or Network package is expected to be deployed per ServicePilot Agent. Call Quality Statistics can be enabled:

  • By network subnet
  • By network zone

Statistics can also be split by vendor or all merged together.

Requirements

  • Network Flows - It is is necessary to ensure network connectivity between ServicePilot and the monitored device. In case of a network infrastructure using a firewall, all the ports below must be opened:

  • ServicePilot Manager Web server access (by default TCP/80 when using HTTP or TCP/443 when using HTTPS although this port is configurable): Between ServicePilot Agent and ServicePilot Manager

  • ServicePilot Requirements

    • ServicePilot Manager minimum version: 8.5
    • ServicePilot Agent minimum version: 8.5 installed and configured
    • One instance of the Call Quality by Zone Or Network package must be imported per ServicePilot Agent deployed

Installation

Before adding a resource to monitor, make certain that all pre-requisites are in place and if a ServicePilot Agent is required, that it is communicating correctly with the ServicePilot Manager.

Add resource using Views Configuration web interface

  1. As an administrative user of ServicePilot, open the ServicePilot web interface.
  2. Navigate to Administration. The Configuration > Views web page will open.
  3. Click on the view in which to place the new resource in the Views hierarchy on the left of the interface. The View editor section will show the existing view contents.
  4. From the Packages list on the right of the interface, click and drag the voip-call-quality-by-zone-or-network package into the View editor and let go.
  5. The Package properties dialog box will open to allow resource configuration.
  6. Click OK to close the Package properties dialog box. Note that the dialog box will not close if required parameters are not set.
  7. Click Save to apply the new resource to ServicePilot configuration.

Key field notes

  1. In the Monitoring Policies tab, specify the policy or policies to apply to the package

  2. Zone/Networks tab:

    1. Call Quality: Select the type of call quality monitoring, by Zone or Network
    2. Vendors: Select whether to aggregate the vendors in a single view or separate them in different views
    3. Customer Name: [Optional - only for aggregate vendors] Specify a customer name

Note: If separate vendors used, you will need to import an additional package voip-call-quality-by-network-view by vendor type deployed in your configuration

Notes

  1. If configuring a ServicePilot Agent to split Call Quality Statistics by network zone then a zone XML file defining the zones needs to be placed in the following location:

    1. In the AgentsData folder for the ServicePilot Agent:
      
        <Work Folder>\AgentsData\VoIPAgent_<ServicePilot Agent Hostname or not present for local agent>_Zones.xml
        e.g.: D:\ServicePilotConfig\AgentsData\VoIPAgent_SERVER1_Zones.xml
        e.g.: D:\ServicePilotConfig\AgentsData\VoIPAgent_Zones.xml
        

The following example can be used as a template for the zone XML file defining your zones:

<zones>
  <zone name="Europe">
    <zone name="London">
      <includes>
        <single ip="10.1.1.5" />
      </includes>
      <excludes />
    </zone>
    <zone name="Other Europe">
      <includes>
        <subnet ip="10.1.0.0" mask="255.255.0.0" />
      </includes>
      <excludes />
    </zone>
  </zone>
  <zone name="US">
    <zone name="Other US">
      <includes>
        <subnet ip="10.2.0.0" mask="255.255.0.0" />
      </includes>
      <excludes>
        <range from="10.2.1.5" to="10.2.1.10" />
      </excludes>
    </zone>
    <zone name="Boston">
      <includes>
        <range from="10.2.1.5" to="10.2.1.10" />
      </includes>
      <excludes />
    </zone>
  </zone>
  <zone name="Mauritius">
    <includes>
      <subnet ip="10.3.0.0" mask="255.255.0.0" />
    </includes>
    <excludes />
  </zone>
</zones>