Nortel-MsCarrier-MscPassport-TdmaIwfMIB :: mscTdmaBcLastResponseCode

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › Nortel-MsCarrier-MscPassport-TdmaIwfMIB › mscTdmaBcLastResponseCode

mscTdmaBcLastResponseCode

Module: Nortel-MsCarrier-MscPassport-TdmaIwfMIB

OID (symbolic): Nortel-MsCarrier-MscPassport-TdmaIwfMIB::mscTdmaBcLastResponseCode

OID (numeric): 1.3.6.1.4.1.562.36.2.1.136.101.1.3

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-only

Description: This attribute indicates the MSC/IWF Interface Protocol (MIP) Message Router (MMR) response code returned for the last call which was active on this particular TdmaIwfBearerChannel. This attribute has one of the following values: noCause: No cause available. unassignedNumber: Unallocated or unassigned number. noRouteToDest: No route to destination. normalClearing: The call was terminated normally. userBusy: User busy. noResponse: No carrier. userNoAnswer: No answer from user. invalidNumberFormat: Translation or routing problem. unspecNormal: Normal, unspecified. temporaryFailure: Temporary failure. channelUnavailable: Channel unavailable. resourceUnavailable: Resources unavailable to handle call. qosUnavailabled: Specified rate of call unavailable. serviceUnavailable: Service not implemented. unimplementedOption: Option not implemented. invalidCallRefValue: Invalid call reference value. invalidChannel: Identified channel does not exist. unspecInvalidMessage: Invalid message, unspecified. missingMandatoryIe: Missing mandatory information element. invalidMessageType: Message type not implemented. incompatibleMessage: Message not compatible with call state. timerRecovery: Recovery on timer expiration. protocolError: Protocol error, unspecified.

What is mscTdmaBcLastResponseCode?

Reports the MSC/IWF Interface Protocol (MIP) Message Router response/cause code from the last call that was active on this bearer channel, covering outcomes from normalClearing through a long list of failure causes (unassignedNumber, noRouteToDest, userBusy, channelUnavailable, resourceUnavailable, protocol errors, etc.). This is one of the first things an admin checks when investigating why a specific call or channel failed, since it gives the specific standards-based cause code rather than just a generic failure flag.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.562.36.2.1.136.101.1.3
snmpwalk -v2c -c public <target> Nortel-MsCarrier-MscPassport-TdmaIwfMIB::mscTdmaBcLastResponseCode

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.562.36.2.1.136.101.1.3.1
snmpget -v2c -c public <target> Nortel-MsCarrier-MscPassport-TdmaIwfMIB::mscTdmaBcLastResponseCode.1

Start monitoring Nortel MsCarrier MscPassport switch (TDMA mobile interworking function) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the Nortel-MsCarrier-MscPassport-TdmaIwfMIB::mscTdmaBcLastResponseCode OID value, configure state conditions and alerts, and monitor any Nortel MsCarrier MscPassport switch (TDMA mobile interworking function) from a single console.

OID Breakdown

Upper-level ancestors (10 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.562nortelCPM-NORTEL-MIB
1.3.6.1.4.1.562.36msCarrierNortel-MsCarrier-MscPassport-UsefulDefinitionsMIB
1.3.6.1.4.1.562.36.2mscPassportNortel-MsCarrier-MscPassport-UsefulDefinitionsMIB
1.3.6.1.4.1.562.36.2.1mscComponentsNortel-MsCarrier-MscPassport-UsefulDefinitionsMIB
Numeric OIDNameModule
1.3.6.1.4.1.562.36.2.1.136mscTdmaBcNortel-MsCarrier-MscPassport-TdmaIwfMIB
1.3.6.1.4.1.562.36.2.1.136.101mscTdmaBcOperTableNortel-MsCarrier-MscPassport-TdmaIwfMIB
1.3.6.1.4.1.562.36.2.1.136.101.1mscTdmaBcOperEntryNortel-MsCarrier-MscPassport-TdmaIwfMIB
1.3.6.1.4.1.562.36.2.1.136.101.1.3mscTdmaBcLastResponseCodeNortel-MsCarrier-MscPassport-TdmaIwfMIB