voip Integration
alcatel-oxe (en)


ServicePilot voip-alcatel-oxe


# Alcatel OXE Monitoring

Overview

The ServicePilot Alcatel OXE Monitoring package collects information for Alcatel OmniPCX Enterprise Communication Servers.

Description

The Alcatel OXE Monitoring package uses SNMP to query Alcatel OmniPCX Enterprise Communication Servers. A standalone or single system, a cluster with main and standby call servers or a spatially redundant system systems can be monitored with virtual IP addresses. The statistics gathered in this way include:

  • Service status
  • Conference, DSP and CAC usage per IP Domain
  • SIP and other set registration counts
  • CPU, Memory and Disk utilization for each Call Server
  • Network interface statistics

The Alcatel OXE Monitoring package also configures the ServicePilot Agent to obtain Alcatel OmniPCX Enterprise Communication Server inventory and performance details using Telnet of SSH connections. Details collected include:

  • Trunk Cards
  • Infrastructure Cards
  • PCS Cards
  • Links
  • DECT Cards
  • Phone Reboots

The Alcatel OXE Monitoring package will also configure the ServicePilot Agent to collect CDRs as stream sent to ServicePilot.

These details are used as the basis for call statistics and call quality statistics.

Requirements

  • SNMP must be installed and configured on each Alcatel OmniPCX Enterprise Communication Server (Security: SNMP v2c read-only access from the ServicePilot Manager IP address)
  • A Telnet or SSH user
  • CDR collection configured

  • 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 Alcatel OmniPCX Enterprise Communication Servers physical IP addresses
    • ICMP/Echo Request (Ping): Between ServicePilot Manager and Alcatel OmniPCX Enterprise Communication Servers physical IP addresses
    • 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/23 (Default) (Telnet) or TCP/22 (Default) (SSH): Between ServicePilot Agent and Alcatel OmniPCX Enterprise Communication Server Cluster virtual IP addresses or physical IP address if no virtual IP addresses exist
    • TCP/21 (Default) (FTP Control): Between ServicePilot Agent and Alcatel OmniPCX Enterprise Communication Server Cluster virtual IP addresses or physical IP address if no virtual IP addresses exist when collecting CDR as an FTP Client
    • TCP/1024-65535 (FTP Data): Between Alcatel OmniPCX Enterprise Communication Server Cluster virtual IP addresses or physical IP address if no virtual IP addresses exist and ServicePilot Agent when collecting CDR as an FTP Client (Active mode)
    • TCP/20,1024-65535 (FTP Data): Between ServicePilot Agent and Alcatel OmniPCX Enterprise Communication Server Cluster virtual IP addresses or physical IP address if no virtual IP addresses exist when collecting CDR as an FTP Client (Passive mode)
    • TCP/2533 (Default) (CDR): Between ServicePilot Agent and Alcatel OmniPCX Enterprise Communication Server Cluster virtual IP addresses or physical IP address if no virtual IP addresses exist when collecting CDR on-the-fly over Ethernet
    • UDP/162 (SNMP Trap): (Optional) Between Alcatel OmniPCX Enterprise Communication Servers and 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.

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-alcatel-oxe 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

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

  1. Basic Parameters tab:

    1. Alcatel OXE Architecture: Choose between the following architectures:
      1. Stand-Alone or Single (1 Physical or Virtual IP Address)
      2. Cluster
      3. Spacial Redundancy
    2. Cluster Virtual IP Address: Specify the IP Address of the Cluster
    3. Customer Name (matching Alcatel VoIP Customer Name): Specify the Customer Name (Note that it should be the same as Alcatel VoIP Customer Name)
  2. Call Servers tab:

    1. Main CS Physical IP Address: Specify the Physical IP Address of the Main Call Server
    2. Main CS Virtual IP Address: Specify the Virtual IP Address of the Main Call Server
    3. Standby CS Physical IP Address: Specify the Physical IP Address of the Standby Call Server
    4. Standby CS Virtual IP Address: Specify the Virtual IP Address of the Standby Call Server
  3. OXE Connection tab:

    1. Enable OXE Collection: Tick to enable OXE data collection
    2. Connexion Mode: Choose between the following two network protocol:
      1. Telnet: Plain text data transmission (includes usernames and passwords)
      2. SSH: Encrypted data transmission
    3. Telnet/SSH Port TCP SNMP Port on the remote system being monitored where the SNMP service will respond to requests (Default: 23).
    4. Login: Specify Login name. (Default: mtcl)
    5. Password: Specify Password.
    6. Polling Frequency: Specify the frequency (in seconds) at which ServicePilot will poll the OXE device (min 60 secs)
    7. Discovery Frequency: Specify the frequency (in seconds) at which ServicePilot will run discovery scripts
    8. Min time between requests: Specify the minimum time interval (in milliseconds) between the SNMP requests
    9. Connection number by OXE: Specify the maximum number of connections by OXE
  4. Resources tab:

    1. Media Gateways to discover: Specify a list of media gateways to include in the discovery, separated by
    2. Media Gateways to exclude from discovery: Specify a list of media gateways to exclude from the discovery, separated by |
    3. Trunk Groups to discover: specify a list of Trunk Groups to include in the discovery, separated by |
    4. Trunk Groups to exclude from discovery: Specify a list of Trunk Groups to exclude from the discovery, separated by |
    5. Trunk Cards: Tick to enable Trunk Card discovery
    6. Trunk Card Discovery: Select the type of cards to include in the discovery
      1. Only Active cards
      2. All (includes out of service and unregistered cards)
    7. Trunk cards to discover: Specify a list of trunk cards to include in the discovery, separated by |
    8. Trunk cards to exclude from discovery: Specify a list of trunk cards to exclude from the discovery, separated by |
    9. Infrastructure Cards: Tick to enable infrastructure cards discovery
    10. Infrastructure Cards to discover: Specify a list of infrastructure cards to include in the discovery, separated by |
    11. Infrastructure cards to exclude from discovery: Specify a list of infrastructure cards to exclude from the discovery, separated by |
    12. PCS Cards: Tick to enable PCS cards discovery
    13. DECT Cards: Tick to enable DECT Cards discovery
    14. Phone Reboot: Tick to enable Phone Reboot logs discovery
    15. Phone Reboot log interval: Specify the time interval (in minutes) at which retrieve phone reboot logs
    16. IP Domains: Tick to enable IP Domains discovery
  5. Call Log tab:

    1. Read Call Log: Tick to enable call log monitoring
    2. Call Collection Type: Select the method of call collection
      1. Directory
      2. FTP Client
      3. OnTheFly over Ethernet
    3. OnTheFly Port: Specify the connection port for OnTheFly over Ethernet call log collection
    4. FTP Port: Specify the connection port through which ServicePilot will connect to the FTP Server
    5. Username: Specify the username of the FTP login account
    6. Password: Specify the password of the FTP login account
    7. Passive Mode: Tick if the FTP server operates in Passive mode
    8. Use Proxy: Tick to enable connection to the FTP server via a proxy
    9. Accounting Directory: Specify the accounting directory from which to collect call logs
    10. IP Directory: Specify the IP address of the directory from which to collect call logs
    11. Decompress Files: Tick to enable file decompression
    12. Delete Files: Tick to delete the call logs after processing
    13. Polling Frequency: Specify the frequency (in seconds) of call logs collection
    14. Ignore calls with duration=0: Tick to ignore call with 0 seconds duration in the statistics
    15. Only calls with IP: Tick to include only calls with IP in the statistics
    16. 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).
    17. Mask Extensions: Tick to enable masking of user portions in numbers
    18. Mask n last digits: Specify the number of trailing digits to mask
    19. When extension contains at least n digits: Specify the minimum number of digits that a number must contain for masking to take effect
  6. Voice Quality tab:

    1. Good Packet Loss Rate: Specify the maximum packet loss rate for a good call (in %)
    2. Good BFI <: Specify the maximum BFI (in %) for a good call
    3. Good Delay (ms) <: Specify the maximum delay (in ms) for a good call
    4. Good MOS Score <: Specify the minimum MOS score for a good call
    5. Medium Packet Loss Rate: Specify the maximum packet loss rate for a medium call (in %)
    6. Medium BFI <: Specify the maximum BFI (in %) for a medium call
    7. Medium Delay (ms) <: Specify the maximum delay (in ms) for a medium call
    8. Medium MOS Score: Specify the minimum MOS score for a medium call

Notes

  1. Check for other devices collecting CDR from the Alcatel OmniPCX Enterprise Communication Servers as different collectors might conflict with each other.