APLICENSE-MIB

MIB Reference — IPNetwork Monitor · Updated September 09, 2026

All MIBsAPLICENSE-MIB

Organization: Acme Packet, Inc

Last Updated: 2012-07-16

Category: Telephony and VoIP, Vendor: Acme Packet

Description: Acme Packet SBC software license entitlement status and capacity management.

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 APLICENSE-MIB?

APLICENSE-MIB is a proprietary module for Acme Packet Session Border Controllers that tracks software license entitlements and feature capacity on the device. It exposes a license inventory table listing each installed license key along with its capacity, install date, activation window, and expiration date. This is squarely a software-status monitoring module: it lets operators track license expiry dates and per-feature entitlement (SIP, MGCP, H.323, IWF interworking) so they can be alerted before a license lapses and disables call-handling capacity. It is a self-contained vendor MIB with no strong dependency on other standard MIBs beyond common SNMPv2 conventions, and it also defines its own notification objects for license-related traps. It is deployed in any Acme Packet SBC installation where licensed call capacity or protocol features need to be tracked for compliance and capacity planning. Network engineers evaluating or troubleshooting this functionality can download the APLICENSE-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in APLICENSE-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 administrator would poll apLicenseTable, indexed by apLicenseIndex, reading apLicenseCapacity and apLicenseExpireDate to see how much licensed capacity remains and when it lapses, alongside apLicenseInstallDate/apLicenseBeginDate for activation history. Boolean-style feature flags such as apLicenseSIPFeature, apLicenseMGCPFeature, apLicenseH323Feature, and apLicenseIWFFeature reveal which signaling protocols are currently licensed. A license entry approaching its apLicenseExpireDate would trigger proactive renewal before SIP/MGCP/H.323 call handling is disabled.

What Can Be Monitored

  • license capacity per feature
  • license install/begin/expire dates
  • SIP feature license status
  • MGCP feature license status
  • H.323 feature license status
  • IWF interworking license status
Imported Objects

From ACMEPACKET-SMI

acmepacketMgmtOBJECT-IDENTITY

From SNMPv2-CONF

MODULE-COMPLIANCE
NOTIFICATION-GROUP
OBJECT-GROUP

From SNMPv2-SMI

Integer32
MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-TYPE
Unsigned32

From SNMPv2-TC

DisplayString
TruthValue
OIDs

RFC description

Acme Packet license inventory MIB for tracking software licenses on Session Router and Session Director platforms.

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 APLICENSE-MIB