APCODEC-MIB

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › APCODEC-MIB

Organization: Acme Packet, Inc

Last Updated: 2012-07-16

Category: Telephony and VoIP, Vendor: Acme Packet

Description: Acme Packet SBC media codec transcoding resource utilization and configuration 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 APCODEC-MIB?

APCODEC-MIB is a proprietary MIB from Acme Packet (now part of Oracle Communications) for their Session Border Controller (SBC) product line, covering media codec usage and transcoding resource management. It exposes per-realm statistics counting calls by negotiated codec type, including PCMU, PCMA, G.722, G.723, several G.726 bit-rate variants, and G.728, along with objects describing transcoding resource utilization and configuration. Monitoring here is a software/service performance matter tied to VoIP call handling: per-codec count tables reveal the real-time call mix and load per realm, and the transcoding resource objects let an admin watch consumption of limited transcoding capacity on the SBC, flagging resource exhaustion that would cause call setup failures. It builds on Acme Packet's proprietary SBC MIB architecture and depends on the realm/session concepts defined elsewhere in Acme Packet's broader MIB suite. It is deployed on Acme Packet Net-Net Session Border Controllers at VoIP/SIP trunk network edges, where codec and transcoding capacity monitoring is important for call quality and capacity planning. Engineers can download the APCODEC-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in APCODEC-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 (Oracle) Session Border Controller

Monitoring Examples

An administrator would poll apCodecRealmStatsTable per realm, comparing apCodecRealmCountPCMU and apCodecRealmCountPCMA against lower-bandwidth codecs such as apCodecRealmCountG723 and the apCodecRealmCountG726-16/24/32/40 counters, revealing the codec mix in use and its bandwidth implications. Monitoring apCodecTranscodingResourceMIBObjects utilization alongside these per-codec counts shows when transcoding resources are approaching exhaustion, a leading indicator of call setup failures on the SBC. A sudden rise in apCodecRealmCountOther could indicate unexpected or misconfigured codec negotiation on a realm.

What Can Be Monitored

  • per-realm call counts by codec type (PCMU/PCMA/G.722/G.723/G.726/G.728)
  • transcoding resource utilization
  • codec/transcoding configuration
Imported Objects

From ACMEPACKET-SMI

acmepacketMgmtOBJECT-IDENTITY

From ACMEPACKET-TC

ApPercentage

From APSYSMGMT-MIB

apSigRealmStatsEntryOBJECT-TYPE

From SNMPv2-CONF

MODULE-COMPLIANCE
NOTIFICATION-GROUP
OBJECT-GROUP

From SNMPv2-SMI

Counter32
Gauge32
Integer32
MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-TYPE

From SNMPv2-TC

DisplayString
TEXTUAL-CONVENTION

How to Use in IPNetwork Monitor

Example using apCodecTranscodingResourcesHigh OID:

Select an Acme Packet (Oracle) Session Border Controller as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type apCodecTranscodingResourcesHigh into the Find box to locate it in the OID tree, then select it and click OK. The highest number of transcoding resources in-use in the past. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is a Counter32-type OID, Value bounds is the most useful condition here — trigger an alert if the counter increases sharply between polls relative to its normal baseline, since an unexpected spike often reflects a real change in traffic or activity. Click Finish to create the monitor; you can adjust any parameter later.
OIDs

RFC description

Codec and transcoding statistics for Acme Packet Session Router/Director.

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