voip Integration
avaya-session-border-controller (en)


ServicePilot voip-avaya-session-border-controller


# Avaya Session Border Controller

Overview

The ServicePilot Manager Avaya Session Border Controller package collects information from Avaya Session Border Controller for Enterprise or SIPERA SBC servers.

Description

This package automatically configures the ServicePilot Manager to collect statistics from the Avaya Session Border Controller to query Avaya Session Border Controller for Enterprise servers on which SNMP Service has been configured. The statistics gathered in this way include:

  • SIP Call statistics
  • SIP Registration statistics
  • SIP Protocol Message statistics
  • SIP Protocol Error statistics

Requirements

  • SNMP must be installed and configured on the Avaya Session Border Controller for Enterprise (Security: SNMP v2c read-only access from the ServicePilot Manager IP address)

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

    • UDP/161 (SNMP): Between ServicePilot Manager and Avaya Session Border Controller for Enterprise
    • ICMP/Echo Request (Ping): Between ServicePilot Manager and Avaya Session Border Controller for Enterprise
    • UDP/162 (SNMP Trap): (Optional) Between Avaya Session Border Controller for Enterprise and ServicePilot Agent
  • ServicePilot Requirements

    • ServicePilot Manager minimum version: 8.5

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. Resources can be added to ServicePilot configuration in a number of ways:

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-avaya-session-border-controller 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.

Add resource by changing servicepilot.conf configuration file

Resources can be added to ServicePilot configuration by directly editing the servicepilot.conf or other included YAML configuration files. The ServicePilot web interface can be used to make these changes and apply them to the running configuration.

  1. As an administrative user of ServicePilot, open the ServicePilot web interface.
  2. Navigate to Administration.
  3. Navigate to Configuration > Edit configuration.
  4. Expand the configuration to find the provisioning: and then packages: section of the view in which the new resource will be placed.
  5. Add the example package configuration line below.
  6. Click on the green - package: word to open then Package properties dialog box to allow resource configuration.
  7. Click OK to close the Package properties dialog box. Note that the dialog box will not close if required parameters are not set.
  8. Click Save to apply the new resource to ServicePilot configuration.

Example:

- package: "voip-avaya-session-border-controller;;;;;;;;voip-avaya-session-border-controller;;127.0.0.1"

Key field notes

  1. Basic Parameters tab:
    1. IP address: Specify the IP address, host name or FQDN for the Avaya Session Border Controller, as resolvable by the machine on which ServicePilot Manager is running
voip avaya-session-border-controller 0

voip avaya-session-border-controller 1

voip avaya-session-border-controller 2