MITEL-MN3100-CALL-CONTROL-MIB

All MIBs › MITEL-MN3100-CALL-CONTROL-MIB

Organization: MITEL Networks Corporation

Last Updated: 2003--0-3-

Category: Telephony/VoIP

Description: Manages MITEL MN3100 call control state, active calls, and trunk usage.

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-MN3100-CALL-CONTROL-MIB?

MITEL-MN3100-CALL-CONTROL-MIB is a Mitel proprietary MIB for the MN3100 call-control platform, part of Mitel's IP telephony product line, exposing call server identification alongside call-control state such as active calls and trunk usage. Its sample objects show a mitelIdCallServers identification branch including a specific model designation (mitelIdCsIpera1000), indicating the MIB is used to positively identify which call server model is deployed. It is used primarily to monitor the software status of the call-control application — verifying the call server type in service and tracking real-time active call counts and trunk/channel occupancy to detect congestion or degraded call handling. No explicit external MIB dependency is stated, though it sits within Mitel's broader proprietary telephony MIB tree. It is deployed in enterprise voice environments running Mitel MN3100/Ipera call servers, where MITEL-MN3100-CALL-CONTROL-MIB SNMP monitoring supports tracking of trunk occupancy and call-handling health.

IPNetwork Monitor allows you to monitor SNMP objects defined in MITEL-MN3100-CALL-CONTROL-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 MN3100 call server
Mitel Ipera 1000 IP-PBX

Monitoring Examples

The mitelIdCsIpera1000 object under mitelIdCallServers confirms the specific call server model in service; an admin would then poll the associated active-call and trunk-usage state to detect when trunk occupancy nears capacity, signaling potential call blocking or degraded voice service during peak load.

What Can Be Monitored

call server model identification
active call count
trunk/channel usage
call-control operational state

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 mitelCallCtrlFaultOccur OID:

Select a Mitel MN3100 call server / Ipera 1000 IP-PBX 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 mitelCallCtrlFaultOccur 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 mitelCallCtrlFaultOccur 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 mitelCallCtrlFailedSeizeLineNotif	1.3.6.1.4.1.1027.1.2.4.0.406			The mitelMn3100CallCtrlFaultNotif trap indicates that the call control has failed to seize a line.
NTF mitelCallCtrlDdiMappingErrorNotif	1.3.6.1.4.1.1027.1.2.4.0.407			The mitelCallCtrlDdiMappingErrorNotif trap indicates that a DDI mapping has failed.
mitelProprietary	1.3.6.1.4.1.1027.4
mitelCallControl	1.3.6.1.4.1.1027.4.9			The MITEL Call CONTROL MIB module.
mitelCallCtrlFaultTable	1.3.6.1.4.1.1027.4.9.1		not-accessible	The Call Control Fault table.
mitelCallCtrlFaultEntry	1.3.6.1.4.1.1027.4.9.1.1		not-accessible	An entry in the mitelCallCtrlFaultTable.
I32 mitelCallCtrlFaultTblIndex	1.3.6.1.4.1.1027.4.9.1.1.1	Integer32	read-only	The index of the fault table.
INT mitelCallCtrlFaultId	1.3.6.1.4.1.1027.4.9.1.1.2	INTEGER	read-only	The mitelCallCtrlFaultId indicates the id of the fault.
INT mitelCallCtrlFaultStatus	1.3.6.1.4.1.1027.4.9.1.1.3	INTEGER	read-only	The mitelCallCtrlFaultStatus indicates whether the fault is raised or cleared.
C32 mitelCallCtrlFaultOccurEx	1.3.6.1.4.1.1027.4.9.1.1.4	Counter32	read-only	The mitelCallCtrlFaultOccur indicates the occurence of the fault since the last system restart

RFC description

Mitel MN3100 PBX/communications platform vendor-specific MIB for call control and telephony feature management.

Start monitoring Mitel MN3100 call server / Ipera 1000 IP-PBX 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-MN3100-CALL-CONTROL-MIB