CISCO-USP-MIB :: cuspTotalCalls

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCISCO-USP-MIBcuspTotalCalls

cuspTotalCalls

Module: CISCO-USP-MIB

OID (symbolic): CISCO-USP-MIB::cuspTotalCalls

OID (numeric): 1.3.6.1.4.1.9.9.827.1.1.10.1

Node type: OBJECT-TYPE

Type: Counter32

Access: read-only

Description: This object gives the total number of calls since the last counter reset.

What is cuspTotalCalls?

This counter reports the total number of calls the CUSP system has processed since the counters were last reset. An admin uses this as the primary call-volume metric, comparing it against cuspTotalFailedCalls to compute an overall call success rate for the SIP proxy. If cuspTotalCalls shows 100,000 and cuspTotalFailedCalls shows 500, the admin can calculate a 0.5 percent failure rate to judge whether the proxy is performing acceptably.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.9.9.827.1.1.10.1
snmpwalk -v2c -c public <target> CISCO-USP-MIB::cuspTotalCalls

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.9.9.827.1.1.10.1.1
snmpget -v2c -c public <target> CISCO-USP-MIB::cuspTotalCalls.1

Start monitoring Cisco Unified SIP Proxy (CUSP) appliance with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CISCO-USP-MIB::cuspTotalCalls OID value, configure state conditions and alerts, and monitor any Cisco Unified SIP Proxy (CUSP) appliance from a single console.

How to Use in IPNetwork Monitor

Select a Cisco Unified SIP Proxy (CUSP) appliance 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 cuspTotalCalls into the Find box to locate it in the OID tree, then select it and click OK. This object gives the total number of calls since the last counter reset. 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.

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.9ciscoMgmtCISCO-SMI
Numeric OIDNameModule
1.3.6.1.4.1.9.9.827ciscoUspMIBCISCO-USP-MIB
1.3.6.1.4.1.9.9.827.1ciscoUspMIBObjectsCISCO-USP-MIB
1.3.6.1.4.1.9.9.827.1.1cuspScalarCISCO-USP-MIB
1.3.6.1.4.1.9.9.827.1.1.10cuspCallStatsCISCO-USP-MIB
1.3.6.1.4.1.9.9.827.1.1.10.1cuspTotalCallsCISCO-USP-MIB