APAPPS-MIB

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › APAPPS-MIB

Organization: Acme Packet, Inc

Last Updated: 2012-03-07

Category: Telephony and VoIP, Vendor: Acme Packet

Description: Acme Packet SBC applications management including service configuration and runtime status.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

What Is APAPPS-MIB?

APAPPS-MIB is a proprietary module for Acme Packet Session Border Controllers, covering application-layer services that ride on top of the SBC's core SIP/media handling, notably ENUM and DNS resolution services. It exposes runtime status tables for configured ENUM and DNS servers, including their network addresses and reachability state. This makes it useful for monitoring the software-service health of the SBC's number-translation and name-resolution subsystems, letting an operator detect when an upstream ENUM or DNS server the SBC depends on has become unreachable or degraded. It is a vendor-specific extension that sits alongside Acme Packet's other proprietary MIBs (license, syslog, software inventory) rather than a standards-based module. It is deployed in carrier and enterprise VoIP environments where the SBC must resolve E.164 numbers via ENUM or hostnames via DNS to route calls correctly. Network engineers evaluating or troubleshooting this functionality can download the APAPPS-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in APAPPS-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

  • Acme Packet Session Border Controller (SBC)

Monitoring Examples

An operator would poll apAppsENUMServerStatusTable, keyed by apAppsENUMConfigName and apAppsENUMServerInetAddress, and read apAppsENUMServerStatus to see whether a configured ENUM server is currently reachable. Similarly, apAppsDnsServerStatusTable entries indexed by apAppsDnsInterfaceName and apAppsDnsServerInetAddress expose apAppsDnsServerStatus per DNS server. A status flip to down/unreachable on either table would indicate the SBC has lost its ability to resolve ENUM lookups or DNS names, which could cause call routing failures.

What Can Be Monitored

  • ENUM server reachability status
  • DNS server reachability status
  • configured ENUM server addresses
  • configured DNS server addresses per interface
Imported Objects

From ACMEPACKET-SMI

acmepacketMgmtOBJECT-IDENTITY

From ACMEPACKET-TC

ApHardwareModuleFamily
ApPhyPortType
ApPresence
ApRedundancyState
ApServerStatus

From INET-ADDRESS-MIB

InetAddress
InetAddressType

From SNMPv2-CONF

MODULE-COMPLIANCE
NOTIFICATION-GROUP
OBJECT-GROUP

From SNMPv2-SMI

Gauge32
Integer32
MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-TYPE

From SNMPv2-TC

DisplayString
TEXTUAL-CONVENTION
TruthValue
OIDs

RFC description

Acme Packet applications MIB for managing ENUM server status, DNS configuration, and application-level functions in Acme Packet devices.

Start monitoring Acme Packet (Oracle) Session Border Controller with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download APAPPS-MIB