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 Template
Description
CPU
Monitors processor utilization on the Audiocodes device
Hardware
Checks hardware component health status
Interfaces
Tracks network interface state and performance metrics
SBC Calls
Monitors active Session Border Controller call sessions
Trunk Status
Verifies SIP trunk availability and registration state
Memory
Tracks 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:
Vendor registration: A script adds Audiocodes to the NetEye vendor list automatically.
Plugin installation: The Centreon plugin for Audiocodes SNMP is deployed, with proper handling for different deployment types (single_node, cluster, and satellite).
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.
During our consulting activities we frequently find ourselves having to collect data from SNMP devices that do not support SNMPv3 for data encryption. This type of traffic is readable on the network and can create security problems and noncompliance with Read More
SNMP monitoring is the standard method for obtaining information and metrics from network devices. Typically, we focus on extracting data from a single interface to monitor its status, traffic, or errors. But in many cases, we’re only interested in getting Read More
This document describes the steps required to build, configure, and operate a Podman container based on php:8.2-cli, with the SNMP extension enabled, intended for executing monitoring plugins within a NetEye/Icinga environment. Pulling the base image podman pull docker.io/php:8.2-cli Containerfile for Read More
First of all, I'll briefly explain what the "Tornado" in NetEye actually is. Tornado is a Complex Event Processor that receives reports of events from data sources such as monitoring, email, and SNMP Traps, matches them against rules you've configured, Read More
We're thrilled to share our exciting experience at OSMC 2023. This event was like a deep dive into the world of open-source monitoring, where we discovered some fantastic developments in the field. Throughout the conference, we enjoyed engaging talks and Read More