10. 07. 2026 Matteo Cipolletta NetEye Extension Packs

Announcing the New NetEye Extension Pack for Audiocodes Devices in NetEye 4.49

With the NetEye 4.49 release, we’re extending the coverage of our NetEye Extension Packs (NEPs) by introducing a new package specifically focused on Audiocodes device monitoring, implemented through Centreon plugins over SNMP. This article explains:

  • When the Audiocodes NEP will be available
  • What it does and which aspects of Audiocodes devices it monitors
  • How it’s integrated into NetEye

Availability

The new NEP for Audiocodes will be released and supported starting with:

  • NetEye: version 4.49 (and compatible later versions)

It’s distributed via the official NEP repository, alongside existing NetEye Extension Packs, and follows the standard NetEye release and support lifecycle.

Like other NEPs:

  • It’s installed using nep-setup
  • It provides Audiocodes‑specific Commands, Service Templates, and Service Sets in Icinga Director
  • It integrates with the standard NetEye SNMP / agentless host templates and variable model

What Is This NEP?

The nep-network-audiocodes package provides out-of-the-box SNMP-based monitoring for Audiocodes devices (SBCs and media gateways) within NetEye. It leverages the Centreon Audiocodes SNMP plugin and integrates it seamlessly into the Icinga Director workflow, keeping the configuration experience consistent with the rest of NetEye.

What does it monitor?

The NEP ships with pre-configured service templates covering the most critical aspects of Audiocodes infrastructure:

Service TemplateDescription
CPUMonitors processor utilization on the Audiocodes device
HardwareChecks hardware component health status
InterfacesTracks network interface state and performance metrics
SBC CallsMonitors active Session Border Controller call sessions
Trunk StatusVerifies SIP trunk availability and registration state
MemoryTracks memory utilization and thresholds

These templates are grouped into service sets, allowing administrators to assign the full monitoring scope to a host in a single action based on host variables – no manual service-by-service configuration required.


How Is It Integrated?

The NEP follows the standard NetEye Extension Pack architecture:

  1. Vendor registration: A script adds Audiocodes to the NetEye vendor list automatically.
  2. Plugin installation: The Centreon plugin for Audiocodes SNMP is deployed, with proper handling for different deployment types (single_node, cluster, and satellite).
  3. Director configuration: Service templates, service sets, and director commands are imported, ready to be assigned to monitored hosts.

Prerequisites

  • NetEye at the required version (see prerequisites.ini in the package)
  • SNMP enabled and configured on target Audiocodes devices
  • Required NetEye modules enabled on the host (Icinga Director)
  • Compatible NEP extension pack base version installed

Installation

Installation follows the standard NEP deployment workflow:

# Install the package
nep-setup install nep-network-audiocodes

Once installed, the service templates and service sets are available in the Icinga Director and can be assigned to any Audiocodes host.


Summary

The new Audiocodes NEP continues our effort to expand NetEye’s out-of-the-box monitoring capabilities for network infrastructure. By packaging proven Centreon SNMP plugins into the NEP framework, we reduce the manual configuration effort for operations teams while ensuring consistent, reliable monitoring of Audiocodes SBC and media gateway deployments.

These Solutions are Engineered by Humans

Did you find this article interesting? Does it match your skill set? Our customers often present us with problems that need customized solutions. In fact, we’re currently hiring for roles just like this and others here at Würth IT Italy.

Matteo Cipolletta

Matteo Cipolletta

Author

Matteo Cipolletta

Archive