VMX-DIAL

MIB Reference — IPNetwork Monitor · Updated September 09, 2026

All MIBsVMX-DIAL

Category: VoIP and Telephony

Description: Manages VMX dial-on-demand ISDN interface triggers and call routing parameters.

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 VMX-DIAL?

VMX-DIAL is a vendor MIB, associated with Octel/VMX voice messaging systems, for managing dial-on-demand ISDN interface triggers and call routing on integrated voice messaging/dial platforms. It exposes system identity objects (system name, serial number, system ID) alongside voice-messaging traffic counters for voice and fax messages sent/received, played greetings, and call duration seconds sent/received. Its monitoring value covers both system identity/software status (systemID, sysSerialNum) and operational message/call throughput — tracking sentVoiceMsgs, recvVoiceMsgs, sentFaxMsgs, recvFaxMsgs, and secSent/secRecv to gauge messaging system load and detect anomalies like a sudden drop in received messages suggesting a dial-trunk or ISDN link failure. It is tied to the Octel voice messaging platform's proprietary object structure (visible in the octel/octelOIDs/octelPlatforms objects) rather than an IETF standard. It is typically deployed on Octel/VMX integrated voice messaging systems connected via ISDN dial-on-demand trunks. Engineers can download the VMX-DIAL file directly to load it into their MIB browser.

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

  • Octel VMX200/300 voice messaging systems

Monitoring Examples

An admin polls sentVoiceMsgs, recvVoiceMsgs, sentFaxMsgs, and recvFaxMsgs alongside secSent/secRecv to track voice-messaging system throughput, and checks systemID/sysSerialNum under octelPlatforms to confirm which platform instance is reporting. A sharp drop in recvVoiceMsgs and recvNames while secRecv remains flat could indicate an ISDN dial-on-demand trigger failing to establish inbound call sessions.

What Can Be Monitored

  • voice/fax messages sent and received
  • call seconds sent/received
  • system identity and serial number
  • played greeting/name counts
Imported Objects

From RFC-1212

OBJECT-TYPE

From RFC1155-SMI

Counter
Gauge
IpAddress
NetworkAddress
TimeTicks
enterprises

From RFC1158-MIB

sysDescr

From RFC1213-MIB

DisplayString
OIDs

RFC description

Manages OCtel VMX200/300 dial system configuration, message statistics, and hardware error reporting.

Start monitoring Octel VMX voice messaging systems 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 VMX-DIAL