voip Integration
acme-packet-sbc (en)


ServicePilot voip-acme-packet-sbc


# Acme Packet SBC

Overview

The ServicePilot Acme Packet SBC package collects Acme Packet SBC statistics.

Description

The Acme Packet SBC package uses SNMP to query Acme Packet SBCs. The statistics gathered in this way include:

  • System state
  • Route statistics
  • Domain statistics
  • Network interface statistics

The Acme Packet SBC package will also configure the ServicePilot Agent to collect CDRs using FTP, either as a client or server. 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 with a firewall, all of the following flows must be opened:

    • UDP/161 (SNMP): Between ServicePilot Manager and Acme Packet SBC
    • ICMP/Echo Request (Ping): Between ServicePilot Manager and Acme Packet SBC
    • 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
    • TCP/21 (Default) (FTP Control): Between ServicePilot Agent and Acme Packet SBC when operating as an FTP Client
    • TCP/1024-65535 (FTP Data): Between Acme Packet SBC and ServicePilot Agent when operating as an FTP Client (Active mode)
    • TCP/20,1024-65535 (FTP Data): Between ServicePilot Agent and Acme Packet SBC when operating as an FTP Client (Passive mode)
    • TCP/21 (Default) (FTP Control): Between Acme Packet SBC and ServicePilot Agent when operating as an FTP Server
    • TCP/1024-65535 (FTP Data): Between ServicePilot Agent and Acme Packet SBC when operating as an FTP Server (Active mode)
    • UDP/162 (SNMP Trap): (Optional) Between Acme Packet SBC and ServicePilot Agent
  • Third Party Configuration

    • SNMP configured on the Acme Packet SBC (Security: SNMP v2c read-only access from the ServicePilot Manager IP address)
    • Either an FTP user for Acme Packet SBC FTP server access or a scheduled task on the Acme Packet SBC to send CDRs to the ServicePilot Agent using FTP
    • An empty directory uniquely used to store the downloaded CDR files on the machine hosting 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 package 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. 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-acme-packet-sbc 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-acme-packet-sbc;;;;;;;;voip-acme-packet-sbc;;127.0.0.1;;60;FTP Server;;;;;;;;;;Y;Y;N;0*|+*;N;;;1;20;150;4;3;50;400;3"

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/FQDN: Specify the IP address, host name or FQDN for the Acme Packet SBC, as resolvable by the machine on which ServicePilot Manager is running
    2. Customer Name: Specify the customer name. This should match the Acme Packet SBC VoIP Customer Name
    3. Polling Frequency (sec): Specify the frequency, in seconds, at which ServicePilot will poll the Acme Packet SBC
  2. Call Collection 1 tab:

    1. CDR Collection FTP Type: Select the type of FTP for CDR collection, Client or Server
      1. Client: ServicePilot will initiate the download of the CDR files
      2. Server: A scheduled task on the FTP server will send the CDR files to ServicePilot
    2. FTP IP Address: Specify the IP Address of the FTP Server for CDR collection
    3. FTP Port: Specify the port number of the FTP Server's command channel (default 21)
    4. FTP Pasv Mode: Select this if the FTP server operates in passive mode
    5. Use Windows FTP Proxy definition: Select this to use Windows FTP proxy definition
    6. FTP User: Specify the username of the FTP login account
    7. FTP Password: Specify the password of the FTP login account
    8. FTP Path: Specify the path of the CDRs to collect on the FTP Server
  3. Call Collection 2 tab:

    1. Local Ticket Folder: Specify the path of the directory where the downloaded CDR files are located
    2. New CDR Format: Selected by default
    3. Delete local files once processed: Select this to delete the downloaded CDR files once they have been processed
    4. Ignore calls with 0 duration: Ignore calls with a duration of 0 seconds
    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: Select this option to mask user portion of the SIP address
    7. Number of trailing digits to mask: Define the number of trailing digits to mask
    8. Length of number before digit masking takes effect: Define the length of number before digit masking takes effect
  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"

Notes

If collecting call records using the ServicePilot Agent FTP Server then a voip-ftp-server package will need to be imported into the configuration.

voip acme-packet-sbc 0

voip acme-packet-sbc 1