H320ENTITY-MIB

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › H320ENTITY-MIB

Organization: ITU-T

Last Updated: 1998-12-18

Category: Domain: Telephony/VoIP

Description: ITU-T H.320 entity MIB for managing ISDN videoconferencing system components and call control resources.

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

H320ENTITY-MIB is an ITU-T standards-based MIB (not vendor-specific) supporting the common management functions of H.320 videoconferencing entities, including H.320 terminals, Multipoint Control Units (MCUs), and H.320/H.323 gateways used in ISDN-based videoconferencing systems. It exposes configuration and status data related to call control resources and entity identification common across these H.320 device roles. Its monitoring relevance includes tracking call control resource status and endpoint/entity operational state, giving visibility into whether videoconferencing call resources are available or in use, which is a software/service-level status indicator for the conferencing platform. As an ITU-T standard, it is designed to be referenced alongside other H.32x family MIBs (e.g., H.323, terminal/gateway-specific MIBs) that build on this common entity foundation. It is typically deployed in enterprise or carrier ISDN videoconferencing environments on terminals, MCUs, and gateways from any compliant vendor. Engineers implementing or auditing this functionality typically reference the H320ENTITY-MIB RFC/standard documentation for the authoritative specification.

IPNetwork Monitor allows you to monitor SNMP objects defined in H320ENTITY-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

  • vendor-neutral, standards-based MIB, not tied to a specific manufacturer
  • ITU-T H.320 terminals, MCUs, and gateways (ISDN videoconferencing systems)

Monitoring Examples

No sample objects were provided for this MIB, so exact object names cannot be confirmed, but based on the ITU-T H.320 entity model one would expect objects identifying entity type (terminal/MCU/gateway) and call control resource counts or states. An administrator would poll such entity-status objects to confirm an MCU has available call resources before scheduling a new conference bridge. A resource-exhausted state would explain why new videoconference calls are being rejected.

What Can Be Monitored

  • entity type identification
  • call control resource status
  • conferencing resource availability
Imported Objects

From MULTI-MEDIA-MIB-TC

MmTerminalAudioCapability
MmTerminalDataCapability
MmTerminalLineRateCapability
MmTerminalVideoCapability
mmH320RootOBJECT-IDENTITY

From SNMPv2-CONF

MODULE-COMPLIANCE
OBJECT-GROUP

From SNMPv2-SMI

Counter32
Gauge32
Integer32
MODULE-IDENTITY
OBJECT-TYPE

From SNMPv2-TC

DisplayString

How to Use in IPNetwork Monitor

Example using h221StatsInVideoFrames OID:

Select a device implementing H320ENTITY-MIB 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 h221StatsInVideoFrames into the Find box to locate it in the OID tree, selecting the specific row/instance you want to monitor since this is a table column, then select it and click OK. The total number of video BCH frames received. 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

H.320 entity MIB supporting ITU-T H.320 protocol terminals, MCUs, and H.320/H.323 gateways for multimedia communications.

Start monitoring Vendor-neutral ITU-T H.320 terminal/MCU/gateway, any manufacturer 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 H320ENTITY-MIB