CISCO-USP-MIB

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCISCO-USP-MIB

Organization: Cisco Systems, Inc.

Last Updated: 2018-02-28

Category: Cisco Devices, Telephony and VoIP

Description: Manages Unified Survivable Remote Site Telephony (SRST) Platform or Universal Service Plane providing call processing failover.

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 CISCO-USP-MIB?

This is a Cisco private MIB for managing the Cisco Unified SIP Proxy (CUSP), a Session Initiation Protocol proxy server appliance/software used by enterprises to aggregate and route SIP-based voice/UC traffic through a centralized architecture. It exposes a mix of performance counters, capacity/licensing data, and system health objects: call statistics (total calls, failed calls, dropped calls, calls-per-second), server group state, license limits and license state, and system uptime, CPU, memory, and disk usage. Its explicit purpose is monitoring both software status, such as SIP proxy service state, license validity, and call processing health, and hardware/OS-level resource status like CPU/memory/disk consumption and uptime since last counter reset, making it valuable for spotting a proxy that's overloaded, low on license capacity, or approaching resource exhaustion before it drops calls. It builds on standard SIP/telephony monitoring concepts and integrates with Cisco's broader Unified Communications MIB family, with its own notification group for CPU/memory threshold and server-group state traps. It is deployed on Cisco CUSP appliances/VMs sitting at the core of enterprise or service-provider SIP trunking and UC deployments, making CISCO-USP-MIB SNMP monitoring central to catching an overloaded or license-constrained proxy before it drops calls.

IPNetwork Monitor allows you to monitor SNMP objects defined in CISCO-USP-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

  • Cisco Unified SIP Proxy (CUSP) appliance
  • Cisco UC/SIP trunking infrastructure

Monitoring Examples

An operator would poll cuspTotalCalls, cuspTotalFailedCalls, and cuspCPS alongside cuspSystemState to gauge whether the SIP proxy is healthy and how loaded it is, then check cuspConfiguredMemory versus cuspMemoryUsed and cuspDiskSpaceUsed to catch resource pressure. A rising cuspTotalFailedCalls count combined with high cuspMemoryUsed would point to the proxy struggling under load and dropping calls, while cuspLicenseState/cuspLicenseLimit would reveal if the failures are actually due to exceeding licensed call capacity. cuspSystemUpTime and cuspLastCounterResetTime give context for how long the current statistics have been accumulating.

What Can Be Monitored

  • total calls processed
  • total failed calls
  • calls per second (CPS)
  • system uptime
  • memory and disk usage
  • license state and limit
Imported Objects

From CISCO-SMI

ciscoMgmtOBJECT-IDENTITY

From SNMPv2-CONF

MODULE-COMPLIANCE
NOTIFICATION-GROUP
OBJECT-GROUP

From SNMPv2-SMI

Counter32
Integer32
MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-TYPE
Unsigned32

From SNMPv2-TC

DateAndTime
TimeStamp
TruthValue

How to Use in IPNetwork Monitor

Example using cuspTotalCalls OID:

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.
OIDs

RFC description

Vendor-private MIB for Cisco Unified SIP Proxy (CUSP) service, managing SIP proxy server metrics including call rates, CPU, memory, licenses, and fault notifications.

Start monitoring Cisco Unified SIP Proxy (CUSP) appliance 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 CISCO-USP-MIB