ATM2-MIB :: atmSigDetectCldPtyEvents

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsATM2-MIBatmSigDetectCldPtyEvents

atmSigDetectCldPtyEvents

Module: ATM2-MIB

OID (symbolic): ATM2-MIB::atmSigDetectCldPtyEvents

OID (numeric): 1.3.6.1.2.1.37.1.14.1.3.1.9

Node type: OBJECT-TYPE

Type: Counter32

Access: read-only

Description: Number of Called Party Responsible For Unsuccessful Call detected on this interface. This counter is incremented when a RELEASE, RELEASE COMPLETE (only when not preceded by a RELEASE message for the same call), ADD PARTY REJECT, or STATUS message that contains one of the following cause code values is received (Note: These cause values apply to both UNI3.0 and UNI3.1):

Cause Value Meaning

17 user busy 18 no user responding 21 call rejected 22 number changed 23 user rejects all calls with calling line identification restriction (CLIR) 27 destination out of order 31 normal, unspecified 88 incompatible destination

NOTE: For this counter, RELEASE COMPLETE messages that are a reply to a previous RELEASE message and contain the same cause value, are redundant (for counting purposes) and should not be

counted.

Note: Cause Value #30 'response to STATUS ENQUIRY' was not included in this memo since it did not apply to a hard failure.

What is atmSigDetectCldPtyEvents?

This is a read-only counter tracking failures where the called party caused unsuccessful calls on an ATM interface. It counts specific cause codes like user busy indicating the remote endpoint rejected the call. A counter of 100 shows 100 call attempts failed due to called party conditions.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.2.1.37.1.14.1.3.1.9
snmpwalk -v2c -c public <target> ATM2-MIB::atmSigDetectCldPtyEvents

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.2.1.37.1.14.1.3.1.9.1
snmpget -v2c -c public <target> ATM2-MIB::atmSigDetectCldPtyEvents.1

Start monitoring ATM switches/interfaces using SVC signaling with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the ATM2-MIB::atmSigDetectCldPtyEvents OID value, configure state conditions and alerts, and monitor any ATM switches/interfaces using SVC signaling from a single console.

OID Breakdown

Upper-level ancestors (8 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.2mgmtAXON-MIB
1.3.6.1.2.1mib_2AXON-MIB
1.3.6.1.2.1.37atmMIBATM-MIB
1.3.6.1.2.1.37.1atmMIBObjectsATM-MIB
Numeric OIDNameModule
1.3.6.1.2.1.37.1.14atm2MIBATM2-MIB
1.3.6.1.2.1.37.1.14.1atm2MIBObjectsATM2-MIB
1.3.6.1.2.1.37.1.14.1.3atmSigStatTableATM2-MIB
1.3.6.1.2.1.37.1.14.1.3.1atmSigStatEntryATM2-MIB
1.3.6.1.2.1.37.1.14.1.3.1.9atmSigDetectCldPtyEventsATM2-MIB