MITEL-VOICE-MAIL-MIB

All MIBs › MITEL-VOICE-MAIL-MIB

Organization: MITEL Networks Corporation

Last Updated: 2002-04-02

Category: Telephony/VoIP

Description: Monitors MITEL Networks voice mail system mailbox status and message counts.

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 MITEL-VOICE-MAIL-MIB?

MITEL-VOICE-MAIL-MIB is a Mitel Networks enterprise MIB, part of the Mitel Application Monitor suite, intended for monitoring the voice mail application on Mitel unified-communications platforms such as the Ipera 1000 call server. It is positioned to expose mailbox status and message-count information as part of Mitel's broader application/software-status monitoring identification tree (mitelIdCallServers, mitelIdCsIpera1000). This falls under software/service-status monitoring: it is meant to let an administrator confirm the voice mail service is running and check mailbox/message load rather than monitor physical hardware sensors. It depends on the shared Mitel enterprise identification structure (mitelProprietary/mitelIdentification) used across the Application Monitor MIB family for identifying specific call-server products. It is deployed in Mitel-based enterprise voice/UC environments alongside Ipera 1000 and related call server hardware. Engineers can download the MITEL-VOICE-MAIL-MIB file directly to load it into their MIB browser.

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

Mitel Ipera 1000 call server
Mitel voice mail/UC platform

Monitoring Examples

Because sample_objects only shows the identification tree (mitel, mitelProprietary, mitelIdentification, mitelIdCallServers, mitelIdCsIpera1000) and no mailbox-level objects, an administrator's realistic use is confirming via the identification objects that a given call server is recognized as an Ipera 1000 before polling the voice-mail-specific mailbox and message-count objects described by the module's stated purpose. Exact mailbox/message-count object names cannot be confirmed from the data provided.

What Can Be Monitored

call server product identification
voice mail service status (per module description)
mailbox message counts (per module description)

Imported Objects

From SNMPv2-CONF

NOTIFICATION-GROUP

From SNMPv2-SMI

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

How to Use in IPNetwork Monitor

Example using mitelVoiceMailFaultOccur OID:

Select a Mitel Ipera 1000 call server / voice mail platform 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 mitelVoiceMailFaultOccur 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 mitelVoiceMailFaultOccur indicates the occurence of the fault since the last system restart. 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

OID symbolic	OID numeric	Type	Access	Description
mitel	1.3.6.1.4.1.1027
mitelIdentification	1.3.6.1.4.1.1027.1
mitelIdCallServers	1.3.6.1.4.1.1027.1.2
mitelIdCsIpera1000	1.3.6.1.4.1.1027.1.2.4
mitelIpera1000Notifications	1.3.6.1.4.1.1027.1.2.4.0			Call Server Ipera 1000 Notifications.
NTF mitelVoiceMailDiskNearlyFullNotif	1.3.6.1.4.1.1027.1.2.4.0.408			The mitelVoiceMailDiskNearlyFullNotif trap indicates that the disk for voice mail is nearly full.
NTF mitelVoiceMailDiskFullNotif	1.3.6.1.4.1.1027.1.2.4.0.409			The mitelVoiceMailDiskFullNotif trap indicates that the disk device for voice mail is full.
mitelProprietary	1.3.6.1.4.1.1027.4
mitelVoiceMail	1.3.6.1.4.1.1027.4.10			The Mitel Application Monitor MIB.
mitelVoiceMailFaultTable	1.3.6.1.4.1.1027.4.10.1		not-accessible	The Voice Mail Fault table.
mitelVoiceMailFaultEntry	1.3.6.1.4.1.1027.4.10.1.1		not-accessible	An entry in the mitelVoiceMailFaultTable.
I32 mitelVoiceMailFaultTblIndex	1.3.6.1.4.1.1027.4.10.1.1.1	Integer32	read-only	The index of the fault table.
INT mitelVoiceMailFaultId	1.3.6.1.4.1.1027.4.10.1.1.2	INTEGER	read-only	The mitelVoiceMailFaultId indicates the id of the fault.
INT mitelVoiceMailFaultStatus	1.3.6.1.4.1.1027.4.10.1.1.3	INTEGER	read-only	The mitelVoiceMailFaultStatus indicates whether the fault is set or cleared or transient
C32 mitelVoiceMailFaultOccurEx	1.3.6.1.4.1.1027.4.10.1.1.4	Counter32	read-only	The mitelVoiceMailFaultOccur indicates the occurence of the fault since the last system restart

RFC description

MITEL voice mail monitoring and fault detection for call server systems.

Start monitoring Mitel Ipera 1000 call server / voice mail platform 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 MITEL-VOICE-MAIL-MIB