USR-CALEA-MIB
The USR-CALEA-MIB provides SNMP objects for monitoring and managing Law Enforcement Interception (CALEA) compliance features on CommWorks USR (now Cisco) network equipment, specifically tracking call detail records, interception session states, and wiretap activation status.
Imported Objects
Objects
30 total| Object Name |
|---|
usrCaleaThe commWorks enterprise defined MIB objects
for CALEA MODULE-IDENTITY .1.3.6.1.4.1.77.1.1.92 |
IMPORTSThe commWorks enterprise defined MIB objects
for CALEA Unknown .1.3.6.1.4.1.77.1.1.92 |
usrCaleaConnConfig OBJECT IDENTIFIER .1.3.6.1.4.1.77.1.1.92.1 |
usrCaleaDFAddrThis four octet value identifies the IP address of
the Intercept Platform in DF that terminates the d-Interfacerw IpAddress .1.3.6.1.4.1.77.1.1.92.1.1 |
usrCaleaDFPortThis value identifies the port number of
the Intercept Platform in DF that terminates the d-Interfacerw Integer32 .1.3.6.1.4.1.77.1.1.92.1.2 |
usrCaleaDFAlarmStatusThis value identifies whether the Alarm is to be raised
when the DF is unreachable. A value of 1 is enabled,
and a value of 2 is disabled.rw Integer32 (1 | 2) .1.3.6.1.4.1.77.1.1.92.1.3 |
usrCaleaPingTimeoutThis value identifies the timeout value for each ping
request that is sent outrw Integer32 .1.3.6.1.4.1.77.1.1.92.1.4 |
usrCaleaPingFrequencyThis value identifies the number of seconds separating two
ping requests for the same host.rw Integer32 .1.3.6.1.4.1.77.1.1.92.1.5 |
usrCaleaPingMissesAllowedThis value identifies the number of misses that will be
allowed before declaring a host unreachablerw Integer32 .1.3.6.1.4.1.77.1.1.92.1.6 |
usrCaleaLifeTimerThis is the value of lifetime that PDSN requests for each session.
Currently supported values are 30..65535.rw Integer32 .1.3.6.1.4.1.77.1.1.92.1.7 |
usrCaleaRespTimerNumber of seconds to wait for the Response from DF.
Currently supported values are 1..15.rw Integer32 .1.3.6.1.4.1.77.1.1.92.1.8 |
usrCaleaNumRegReqRetransNumber of times the registration request is retransmittedrw Integer32 .1.3.6.1.4.1.77.1.1.92.1.9 |
usrCaleaMaxSessionsNumber of times the registration request is retransmittedrw Integer32 .1.3.6.1.4.1.77.1.1.92.1.10 |
usrCaleaDFAuthEnabledThis value identifies whether authentication is enabled
between DF and PDSN. A value of 1 is enabled,
and a value of 2 is disabled.rw Integer32 (1 | 2) .1.3.6.1.4.1.77.1.1.92.1.11 |
usrCaleaDFSecretThis value identifies the secret used for authentication
between PDSN and DF.rw UsrSecretDisplay .1.3.6.1.4.1.77.1.1.92.1.12 |
usrCaleaConnStats OBJECT IDENTIFIER .1.3.6.1.4.1.77.1.1.92.2 |
usrCaleaSessionsThis value identifies the table holding all the sessions with DF SEQUENCE OF UsrCaleaSessionEntry .1.3.6.1.4.1.77.1.1.92.2.1 |
usrCaleaSessionEntryThis variable represents one entry in the DF Session Table. UsrCaleaSessionEntry .1.3.6.1.4.1.77.1.1.92.2.1.1 |
usrCaleaNumIPPacketsDuplicatedThis value identifies the number of IP packets that have been duplicated
for this mobile node in this sessionro Integer32 .1.3.6.1.4.1.77.1.1.92.2.1.1.1 |
usrCaleaHomeIPAddressThis value identifies Home IP Address of the mobile being tappedro IpAddress .1.3.6.1.4.1.77.1.1.92.2.1.1.2 |
usrCaleaPacketManagerIPAddressThis value identifies IP Address of the Packet Manager to which packets will be copied.ro IpAddress .1.3.6.1.4.1.77.1.1.92.2.1.1.3 |
usrCaleaSessionKeyThis value identifies the key used by PDSN to communicate with the DF.
The key is unique for this particular session.ro Integer32 .1.3.6.1.4.1.77.1.1.92.2.1.1.4 |
usrCaleaImsiThis value identifies the IMSI of the mobile being tappedro OCTET STRING .1.3.6.1.4.1.77.1.1.92.2.1.1.5 |
usrCaleaNAIThis value identifies the NAI of the mobile being tappedro DisplayString .1.3.6.1.4.1.77.1.1.92.2.1.1.6 |
usrCaleaTraps OBJECT IDENTIFIER .1.3.6.1.4.1.77.1.1.92.3 |
usrCaleaDeliveryFunctionUnreachableThis trap is generated when delivery function is unreachable. NOTIFICATION-TYPE .1.3.6.1.4.1.77.1.1.92.3.1 |
usrCaleaDeliveryFunctionUnreachableClearThis trap is generated when delivery function is reachable again. NOTIFICATION-TYPE .1.3.6.1.4.1.77.1.1.92.3.2 |
usrCaleaCfmConfig OBJECT IDENTIFIER .1.3.6.1.4.1.77.1.1.92.4 |
usrCaleaConfigFileNameThe name of the configuration file for VHA. If
this value is empty, then the default file name
is @file://VHAProcess.cfg.ro UsrDisplayString .1.3.6.1.4.1.77.1.1.92.4.1 |
usrCaleaCfmStatusThe Configuration File Manager Flag for
saving VHA configurable parameters.rw UsrConfigStatus .1.3.6.1.4.1.77.1.1.92.4.2 |
More MIBs from Lanmanager
Browse all LanmanagerMIBs →The USR-USER-MAN-MIB facilitates the monitoring and management of user authentication sessions, active login states, and access control policies on commWorks (US Robotics) network infrastructure devices. This module enables administrators to track real-time user connectivity metrics and enforce security configurations via SNMP.
The Cip-MIB provides enterprise-specific SNMP objects for monitoring and managing commWorks CIP (Common Industrial Protocol) devices, enabling the tracking of industrial automation session states, communication errors, and device operational parameters.
The USR-VHA-MIB provides SNMP management access for commWorks VHA (Virtual Host Appliance) devices, enabling monitoring of virtualization-specific metrics such as session states, resource utilization, and interface statistics. This module facilitates the tracking of virtual host availability and performance parameters critical for maintaining the operational integrity of commWorks virtual infrastructure.
The USR-FA-MIB provides management objects for monitoring Wireless Foreign Agent session states, tunnel configurations, and mobility parameters on CommWorks enterprise wireless infrastructure. This module enables the tracking of mobile node registration, handover events, and Foreign Agent resource utilization within a Mobile IP environment.
Standard SNMP MIB module defining data structures for UsrUserMan-MIB.
The ROBOEXEC-RESOURCES-MIB defines commWorks enterprise-specific objects for monitoring system resource utilization and operational status of RoboExec appliances. This module provides granular visibility into device health metrics, including CPU load, memory consumption, and process states, enabling administrators to track performance thresholds and resource exhaustion on RoboExec hardware.