Introduction
Introduction Monitoring with anynode SBC
For full use of all features and queries described in this technote, anynode version 4.14 or higher is required. Earlier versions may not support the extended monitoring capabilities introduced with this release.
anynode, as a Session Border Controller, is an essential component for ensuring seamless and secure connectivity in VoIP networks. However, like any critical network element, it is vital to maintain a clear overview of its performance and system integrity. This is where monitoring comes into play.
Monitoring not only ensures the operational reliability of anynode but also enables the early detection of potential issues, allowing proactive measures to be taken before they disrupt communication flow. This is particularly crucial in scenarios with high call volumes and stringent quality requirements. The ability to access precise data and maintain an up-to-date overview of the anynode installation’s status is more than just an advantage – it is a necessity.
Discover in this technote how you can pro actively monitor the status and performance of your VoIP systems using the powerful monitoring features of anynode.
Overview
anynode offers a variety of monitoring services. Depending on your infrastructure and available management tools you can pick the best option. SNMP and WMI have all the system details available. SMTP, HTTP and REST send out alerts based on defined conditions.
SNMP
With the Simple Network Management Protocol (SNMP), numerous parameters such as license status, CPU usage, and interface status can be centrally monitored. Through its Management Information Base (MIB), anynode provides detailed insights into system health, nodes, routes, licenses, and certificates. Additionally, SNMP traps enable real-time notifications for critical events such as status changes or upcoming expiration dates, allowing potential issues to be identified early.
SNMP is ideal for scenarios where centralized monitoring and management of network components are essential. It suits environments with complex VoIP infrastructures, high call volumes, or strict service level requirements. Typical use cases include monitoring system performance, ensuring compliance with operational thresholds, identifying bottlenecks, and receiving real-time alerts for critical events. SNMP is especially valuable in proactive troubleshooting, capacity planning, and maintaining communication networks' overall reliability and security.
SNMP is a widely supported protocol that is recommended for monitoring and managing Windows and Linux systems. On Windows, SNMP can be used for basic system and network device monitoring, though it is gradually being replaced by more modern alternatives like WMI or WinRM. On Linux, SNMP is a standard choice for monitoring system metrics and network infrastructure due to its lightweight nature and compatibility with various tools. For optimal security, access should be restricted to trusted networks.
Both SNMP and WMI can expose sensitive information if improperly secured. Both interfaces must be used within secure internal networks rather than exposed to external ones.
WMI
WMI (Windows Management Instrumentation) is highly recommended for managing and monitoring Windows systems. WMI is not natively available for Linux.
Windows Management Instrumentation (WMI) enables comprehensive monitoring and management of Windows systems. It provides access to system resources, applications, and event logs, allowing performance data to be monitored, configurations managed, and issues diagnosed. WMI supports task automation, enhances security, and integrates seamlessly with monitoring tools, making it ideal for managing complex Windows environments.
WMI is ideal for scenarios where detailed monitoring and management of Windows systems are required. It is commonly used for tracking system performance, diagnosing application or system issues, managing configurations, and automating routine administrative tasks. WMI is particularly valuable in environments with complex Windows infrastructures, ensuring operational stability, enhancing security, and supporting compliance monitoring.
WMI interfaces should generally not be exposed to external interfaces for security reasons. WMI provides extensive access to system-level information, which could be exploited if an attacker gains unauthorized access. Limit WMI access to trusted internal networks or VPN connections.
SMTP
SMTP (Simple Mail Transfer Protocol) is an easy way to monitor anynode when no dedicated monitoring system is available. However, it is inherently limited since no alerts can be sent if anynode itself is down. Like HTTP and REST, SMTP monitoring only focuses on events, making it a lightweight but basic option for keeping track of system statuses and receiving notifications.
HTTP
HTTP monitoring in anynode allows for basic status updates and notifications via standard HTTP requests. It is a simple way to retrieve information about anynode's state without requiring complex integrations. However, like REST and SMTP monitoring, HTTP monitoring is limited in that it can only provide updates while anynode is operational. If the service is down, no data can be transmitted, which restricts its effectiveness for critical monitoring scenarios.
REST
REST monitoring in anynode leverages the Representational State Transfer (REST) API to provide status updates and notifications. It allows external systems to query anynode for specific status information or to receive event notifications. This approach is highly flexible and integrates seamlessly with modern monitoring tools. However, like SMTP and HTTP monitoring, REST monitoring depends on anynode being operational to provide information, as it only processes events while the system is running.
Automating routine tasks and processes through the REST API reduces manual effort and minimizes errors, making system management more efficient and reliable.
Supplied sample scripts provided with every anynode installation offer a valuable resource for administrators and developers. These scripts serve as practical examples and simplify the introduction to using the API. The PowerShell module, which is automatically installed with anynode, provides easy access to the REST API, further simplifying the integration and automation processes.
Refer to our REST documentation for more details.
SIP Capture with Wireshark
The SIP Capture with Wireshark chapter explains how administrators can perform targeted SIP packet captures directly from anynode for quick diagnostics, call-flow verification, and troubleshooting interoperability or media issues. It also highlights important considerations when installing and configuring Wireshark, especially on Windows systems. Since the HEPv3 protocol used by anynode is not natively supported by any standard application on Windows—including Wireshark itself—additional setup steps or external tools may be required to interpret encapsulated data correctly. The chapter concludes with guidance on using HEPv3 for structured SIP export to external analysis solutions, complementing local Wireshark captures for broader monitoring workflows.