voip Integration
avaya-aes (en)


ServicePilot voip-avaya-aes


# Avaya AES

Overview

The ServicePilot Avaya AES package collects information for Avaya Application Enablement Services servers.

Description

The Avaya AES package uses SNMP to query Avaya Application Enablement Services servers. The statistics gathered in this way include:

  • System information
  • CPU, Memory and Disk utilization
  • Definity LAN Gateway service status
  • Transport Layer service status
  • AEP Link status and messaging usage
  • Device Media Call Control service status, license, session, device and memory usage
  • TSAPI service status license, link, clients, memory and stream usage
  • Network interface statistics

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:

    • UDP/161 (SNMP): Between ServicePilot Manager and Avaya Application Enablement Services servers
    • ICMP/Echo Request (Ping): Between ServicePilot Manager and Avaya Application Enablement Services servers
    • UDP/162 (SNMP Trap): (Optional) Between Avaya Application Enablement Services servers and ServicePilot Agent
  • Third Party Configuration

    • SNMP configured on the Avaya AES (Security: SNMP v2c read-only access from the ServicePilot Manager IP address)
    • See Avaya Application Notes for details
  • 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-aes 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-aes;;;;;;;;voip-avaya-aes;;127.0.0.1;Y;Y;Y;Y;Y;Y;Y"

Key field notes

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

  1. Basic Parameters tab:

    1. IP Address: Specify the IP address, host name or FQDN for the Avaya AES server, as resolvable by the machine on which ServicePilot Manager is running
  2. Monitoring Options 1 tab, tick the different checkboxes to enable the monitoring options. The options available are:

    1. Telephony Services API monitoring.
    2. DMCC Monitoring monitoring.
    3. Transport Layer Protocol monitoring.
    4. Definity Lan Gateway monitoring.
  3. Monitoring Options 2 tab, tick the different checkboxes to enable the monitoring options. The options available are:

    1. DMCC License monitoring.
    2. TSAPI License monitoring.
    3. AEP Links monitoring.
voip avaya-aes 0

voip avaya-aes 1