All MIBs › US-SRX-UCE-MIB
Organization: Siemens Network Convergence LLC
Last Updated: 2008-06-11
Category: VoIP and Telephony
Description: Monitors Siemens SRX Unified Communications Engine service state and subscriber sessions.
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 US-SRX-UCE-MIB?
US-SRX-UCE-MIB is a private enterprise MIB for Siemens' SRX Universal Call Engine (UCE), a component of Siemens' unified communications/telephony gateway platform, focused on monitoring call-processing service state and subscriber session activity. It exposes a rich set of performance counters covering incoming and outgoing half-calls, call completion (reaching address-complete and answer states), forward and backward release counts, and total call releases, alongside multiple counters for aborted call attempts broken down by cause (unavailable resources, no route available, no trunk available, gateway resource unavailable, codec unavailable). Its monitoring focus is squarely on software/service-level performance and fault status of the call-processing engine: elevated abort counters for a specific cause reveal capacity or routing problems (e.g., trunk exhaustion or codec mismatch) affecting call setup success in near real time. It depends on general telephony/VoIP call-model concepts (PDP-style call state) rather than a specific IETF MIB. It is deployed in carrier or enterprise unified-communications environments running Siemens SRX gateway/call-engine platforms, where the US-SRX-UCE-MIB MIB is polled to assess call-processing health.
IPNetwork Monitor allows you to monitor SNMP objects defined in US-SRX-UCE-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
- Siemens SRX Universal Call Engine gateways
Monitoring Examples
An operator monitoring call health would track usSrxUceIncomingHalfCallsCounter and usSrxUceOutgoingHalfCallsCounter against usSrxUceCallsReachAnswerCounter to compute call-completion ratios over a polling interval. A spike in usSrxUceAbortForNoTrunkAvailableCounter or usSrxUceAbortForCodecUnavailableCounter would immediately point to trunk exhaustion or codec negotiation failures as the root cause of a drop in successful calls, distinct from a generic usSrxUceTotalReleaseCounter increase. usSrxUceForwardReleaseCounter and usSrxUceBackwardReleaseCounter further distinguish which side of the call initiated normal termination, aiding root-cause analysis of call-quality complaints.
What Can Be Monitored
- incoming/outgoing half-call counts
- calls reaching address-complete/answer
- forward/backward/total release counts
- call aborts by cause (no trunk, no route, codec unavailable, resource unavailable)
Imported Objects
From SNMPv2-SMI
| Counter32 | |
| MODULE-IDENTITY | |
| OBJECT-TYPE |
| hiq8000Admin | OBJECT-IDENTITY |
From SURPASS-RTP-MIB
| surpassRtp | MODULE-IDENTITY |
How to Use in IPNetwork Monitor
Example using usSrxUceIncomingHalfCallsCounter OID:
OIDs
RFC description
Siemens Universal Call Engine statistics and performance monitoring for VoIP call processing and SIP routing.
Start monitoring Siemens SRX Universal Call Engine gateways (call-completion/abort-cause counter 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.