CISCO-ATM2-MIB :: ciscoatmSigEmitCldPtyEvents

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › CISCO-ATM2-MIB › ciscoatmSigEmitCldPtyEvents

ciscoatmSigEmitCldPtyEvents

Module: CISCO-ATM2-MIB

OID (symbolic): CISCO-ATM2-MIB::ciscoatmSigEmitCldPtyEvents

OID (numeric): 1.3.6.1.4.1.9.10.23.1.1.1.14

Node type: OBJECT-TYPE

Type: Counter32

Access: read-only

Description: Number of Called Party Responsible For Unsuccessful Call transmitted from this interface. This counter is incremented when a RELEASE, RELEASE COMPLETE (only when not preceded by a RELEASE mesg for the same call), ADD PARTY REJECT, or STATUS message that contains one of the following cause code values is transmitted (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 id 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 ciscoatmSigEmitCldPtyEvents?

This counter increments when this interface itself transmits a message attributing a call failure to the called party. This is this switch relaying that failure verdict back toward whoever originated the call, confirming the called-party-attributable cause was generated toward the far end, useful for distinguishing whether this switch detected the bad news itself or is simply passing it along from further downstream. This counter rising in tandem with ciscoatmSigDetectCldPtyEvents on the same interface for the same call pattern confirms this switch is both seeing and relaying genuine called-party failures rather than manufacturing them.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.9.10.23.1.1.1.14
snmpwalk -v2c -c public <target> CISCO-ATM2-MIB::ciscoatmSigEmitCldPtyEvents

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.9.10.23.1.1.1.14.1
snmpget -v2c -c public <target> CISCO-ATM2-MIB::ciscoatmSigEmitCldPtyEvents.1

Start monitoring Cisco routers/switches with ATM interfaces with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CISCO-ATM2-MIB::ciscoatmSigEmitCldPtyEvents OID value, configure state conditions and alerts, and monitor any Cisco routers/switches with ATM interfaces 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.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.9ciscoCAT2600-MIB
1.3.6.1.4.1.9.10ciscoExperimentCISCO-SMI
Numeric OIDNameModule
1.3.6.1.4.1.9.10.23ciscoAtm2MIBCISCO-ATM2-MIB
1.3.6.1.4.1.9.10.23.1ciscoatm2MIBObjectsCISCO-ATM2-MIB
1.3.6.1.4.1.9.10.23.1.1ciscoatmSigStatTableCISCO-ATM2-MIB
1.3.6.1.4.1.9.10.23.1.1.1ciscoatmSigStatEntryCISCO-ATM2-MIB
1.3.6.1.4.1.9.10.23.1.1.1.14ciscoatmSigEmitCldPtyEventsCISCO-ATM2-MIB