voip Integration
aastra-monitoring (en)


ServicePilot voip-aastra-monitoring


# Aastra Monitoring

Overview

The ServicePilot Aastra Monitoring package collects information for Aastra Call Servers and Gateways.

Description

The Aastra Monitoring package uses SNMP to query Aastra Call Servers and Gateways. Standalone Call Servers, Clustered Call Servers and Gateways can be queried. The statistics gathered in this way include:

  • Link Connection Status
  • Service status
  • Hardware and software status
  • CPU, Memory and Disk utilization for each Call Server or Gateway
  • Network interface statistics

The Aastra Monitoring package also configures the ServicePilot Agent to obtain Aastra Trunk statistics by processing Ticktel information. Details collected include Trunk call counts by type and direction.

The Aastra Monitoring package will also configure the ServicePilot Agent to collect Aastra RTCP-XR provided data. These details are used as the basis for call statistics and call quality statistics.

Requirements

  • Network Flows - It 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 Aastra Call Servers and Gateways
    • UDP/162 (SNMP Trap): (Optional) Between Aastra Call Servers and Gateways and ServicePilot Agent
    • ICMP/Echo Request (Ping): Between ServicePilot Manager and Aastra Call Servers and Gateways
    • TCP/443 (Web secure access): Between ServicePilot Agent and Aastra Gateways
    • UDP/5060 (Default) (RTCP-XR): Between Aastra endpoints (IP phones and media gateways) and ServicePilot Agent
    • 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
  • Third Party Configuration

    • SNMP Service must be installed, configured (Security: SNMP v1 read-only access from the ServicePilot Manager IP address) and started on each target PBX server
    • Login account with read permissions on the Aastra Gateways for Ticktel processing
    • Configure the Aastra media endpoints to send RTCP-XR to the ServicePilot Agent
  • ServicePilot Requirements

    • ServicePilot Manager minimum version: 8.5
    • ServicePilot Agent minimum version: 8.5 installed and configured
    • A Call Quality by Zone Or Network resource imported into the configuration for the ServicePilot Agent

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-aastra-monitoring package into the View editor and let go.
  5. The Resource properties dialog box will open to allow resource configuration.
  6. Click OK to close the Resource 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. Basic Parameters tab:

    1. Aastra Device Type: Select the device type to monitor, Standalone, Cluster or Gateway
    2. Virtual IP...:Virtual(Cluster) or physical(Standalone or Gateway) IP Address of device
  2. Call Server Parameters tab (only for Cluster type):

    1. Primary Aastra Call Server: Name of Primary Aastra Call Server
    2. IP address ACS 1: Specify the IP address, host name or FQDN for the primary Aastra Call Server, as resolvable by the machine on which ServicePilot Manager is running
    3. Secondary Aastra Call Server: Name of Secondary Aastra Call Server
    4. IP address ACS 2: Specify the IP address, host name or FQDN for the secondary Aastra Call Server, as resolvable by the machine on which ServicePilot Manager is running
  3. Customer and RTCP-XR tab:

    1. Customer Name (matching Aastra VoIP Customer Name): If ServicePilot has been set up in multi-tenant environment, then the customer name is to be presented here, otherwise this field is to be left blank.
    2. Enable RTCP-XR Tickets processing: if is set, RTCP-XR processing will be enabled
    3. RTCP-XR Port: Port where we will receive RTCP-XR control informations
    4. External extension pattern: A pipe separated list of Like Operator patterns to Specify an extension as external to the enterprise. Starting the list with an ! will reverse the meaning, so then list internal extensions instead (Default: 0|+). See the Like Operator (Visual Basic).
    5. Mask Extensions: if set, masking will be enabled
    6. Number of trailing digits to mask: specify number of trailing digits to mask
    7. Length of number before digit masking takes effect: specify length of number before digit masking takes place
  4. Good Call Quality tab. Here you can define the thresholds of a "good quality call". Complete the fields as follows:

    1. Good Loss Rate<(%): Define the percentage loss rate under which a call will be qualified as "good".
    2. Good Jitter<(ms): Define the value of Jitter in milliseconds under which a call will be qualified as "good".
    3. Good Latency<(ms): Define the value of latency in milliseconds under which a call will be qualified as "good".
    4. Good MOS>: Define the mean opinion score above which a call will be qualified as "good".
  5. Medium Call Quality tab. Here you can define the thresholds of a "medium quality call". Complete the fields as follows:

    1. Medium Loss Rate<(%): Define the percentage loss rate under which a call will be qualified as "medium".
    2. Medium Jitter<(ms):Define the value of Jitter in milliseconds under which a call will be qualified as "medium".
    3. Medium Latency<(ms): Define the value of latency in milliseconds under which a call will be qualified as "medium".
    4. Medium MOS>: Define the mean opinion score above which a call will be qualified as "medium".
  6. Ticktel tab:

    1. Enable Ticktel processing: Enable Ticktel to get statistics of historical calls from Aastra device
    2. Ticktel download login (Aastra web secure access): username set on the Aastra device for secure access
    3. Ticktel download password (Aastra web secure access): password set on the Aastra device for secure access
    4. Polling frequency (sec): number of seconds before polling the device for sending the statistics
    5. External extension pattern: A pipe separated list of Like Operator patterns to Specify an extension as external to the enterprise. Starting the list with an ! will reverse the meaning, so then list internal extensions instead (Default: 0|+). See the Like Operator (Visual Basic).
    6. Mask Extensions: if set, masking will be enabled
    7. Number of trailing digits to mask: specify number of trailing digits to mask
    8. Length of number before digit masking takes effect: specify length of number before digit masking takes place

We can help you

Or call us at +33 2 40 60 13 30