All MIBs › CISCO-WAN-PERSISTENT-XGCP-EVENTS-MIB
Organization: Cisco Systems, Inc.
Last Updated: 2003-10-20
Category: Telephony and VoIP, Vendor: Cisco Devices
Description:
Manages Cisco WAN persistent XGCP event notification configurations for media gateway signaling.
Imported Objects
From CISCOWAN-SMI
| ciscoWan | OBJECT-IDENTITY |
From SNMP-FRAMEWORK-MIB
| SnmpAdminString |
From SNMPv2-CONF
| MODULE-COMPLIANCE | |
| OBJECT-GROUP |
From SNMPv2-SMI
| Integer32 | |
| MODULE-IDENTITY | |
| OBJECT-TYPE |
From SNMPv2-TC
| RowStatus |
What Is CISCO-WAN-PERSISTENT-XGCP-EVENTS-MIB?
CISCO-WAN-PERSISTENT-XGCP-EVENTS-MIB manages persistent XGCP (a generic term covering MGCP/SGCP-style gateway control protocols) event notification configuration for Call Agent (CA) to media gateway signaling on Cisco WAN platforms. It exposes a simple table of named events (persistentXgcpEventName) that should persist across gateway resets, controlled via row status. Its monitoring role is configuration-state verification for VoIP/media-gateway control signaling: confirming which XGCP events (e.g., off-hook, on-hook, or fax-tone detection style events) remain registered as persistent so the Call Agent continues to receive them after a gateway reload, with an unexpected missing or inactive entry signaling a lost event registration that could cause call-control signaling gaps. It is a companion MIB to the broader Cisco WAN media-gateway control MIB set (including CISCO-WAN-SRCP-MIB and CISCO-WAN-MG-MIB) built on MGCP/SGCP-family concepts rather than a specific IETF standard. Administrators typically start with a CISCO-WAN-PERSISTENT-XGCP-EVENTS-MIB download from Cisco's MIB repository so the module can be compiled into their SNMP tooling before it is deployed in Cisco MGX-based media gateway/Call Agent voice networks.
IPNetwork Monitor allows you to monitor SNMP objects defined in CISCO-WAN-PERSISTENT-XGCP-EVENTS-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.
What Can Be Monitored
- persistent event registrations
- event names configured
- row status/activation of persistent events
Supported Devices
- Cisco WAN media gateways (MGX-based Call Agent/gateway platforms)
Monitoring Examples
An operator would check persistentXgcpEventsTable, indexed by persistentXgcpEventNum, to confirm persistentXgcpEventName entries for critical signaling events retain a persistentXgcpEventRowStatus of active after a gateway reboot. If an expected event's row status reverts to notInService, the Call Agent may stop receiving that event notification from the media gateway, causing a call-control signaling failure.
OIDs
| OID symbolic | OID numeric | Type | Access | Description |
|---|---|---|---|---|
| ciscoWanPersistentXgcpEventsMIB | 1.3.6.1.4.1.351.150.18 | The MIB module for managing CA(Call Agent) events. | ||
| ciscoWanPersistentXgcpEventsMIBObjects | 1.3.6.1.4.1.351.150.18.1 | |||
| persistentXgcpEvents | 1.3.6.1.4.1.351.150.18.1.1 | |||
| persistentXgcpEventsTable | 1.3.6.1.4.1.351.150.18.1.1.1 | not-accessible | The persistentXgcpEventsTable contains configuration information about xGCP events which involve a persistent notification request. | |
| persistentXgcpEventsEntry | 1.3.6.1.4.1.351.150.18.1.1.1.1 | not-accessible | An entry in the persistentXgcpEventsTable. Each entry consists of persistentXgcpEventNum - Index to the persistentXgcpEventsTable. persistentXgcpEventName - Name of the xGCP event that needs persistent notification to the call agent for example 't/hd'. persistentXgcpEventRowStatus -This indicates whether an xGCP event is added in this entry or not. This table is not created implicitly. The user can add xGCP event or delete an xGCP event. | |
| I32 persistentXgcpEventNum | 1.3.6.1.4.1.351.150.18.1.1.1.1.1 | Integer32 | not-accessible | This object is a index to persistentXgcpEventsTable. |
| STR persistentXgcpEventName | 1.3.6.1.4.1.351.150.18.1.1.1.1.2 | SnmpAdminString | read-write | This object holds the name of the event for example 't/hd' or 't/hu'. |
| ROW persistentXgcpEventRowStatus | 1.3.6.1.4.1.351.150.18.1.1.1.1.3 | RowStatus | read-write | This object allows to add or delete an entry. Modifying an entry is not allowed. An entry may be created using the 'createAndGo' option. When the row is successfully created, the RowStatus would be set to 'active' by the agent. An entry may be deleted by setting the RowStatus to 'destroy'. Other options such as `CreateAndWait', 'notInService', 'notReady' will not be used. For creating an entry the persistentXgcpEventNum and persistentXgcpEventName must be provided. This object tells call control whether or not a particular xGCP event is added or not, based on this the call control module will decide whether or not to notify (NTFY) call agent when a particular xGCP event is received, without waiting for CA to request for that event. |
| persistentXgcpEventsMIBConformance | 1.3.6.1.4.1.351.150.18.2 | |||
| persistentXgcpEventsMIBCompliances | 1.3.6.1.4.1.351.150.18.2.1 | |||
| persistentXgcpEventsMIBCompliance | 1.3.6.1.4.1.351.150.18.2.1.1 | The complaince statement for persistent Xgcp events which implement persistentXgcpEvents MIB. | ||
| persistentXgcpEventsMIBGroups | 1.3.6.1.4.1.351.150.18.2.2 | |||
| persistentXgcpEventsMIBGroup | 1.3.6.1.4.1.351.150.18.2.2.1 | This group contains objects related to configuration of persistent xGCP events. |
RFC description
Cisco WAN MIB for managing Media Gateway Control Protocol (xGCP) event enablement/disablement to Call Agents in VISM devices for asynchronous event notification.
Start monitoring Cisco WAN media gateways (MGX-based, legacy) 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.