CISCO-VISM-XGCP-EXT

All MIBs › CISCO-VISM-XGCP-EXT

Organization: Cisco Systems, Inc.

Last Updated: 2003-07-11

Category: Cisco Devices, Telephony and VoIP

Description: Extends xGCP (MGCP/H.248) media gateway control protocol parameters on Cisco VISM ATM voice gateway modules.

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-VISM-XGCP-EXT?

This MIB extends xGCP (a generic term covering MGCP and related media gateway control protocols) support on Cisco VISM voice modules, exposing protocol configuration such as timeouts and ports, and per-peer message statistics for gateway control signaling. It surfaces software/protocol-level status rather than hardware telemetry, specifically message counters for command types like Create Connection successes and failures. Administrators use it to monitor call-control signaling health by watching connection-creation success counts against failure counts to detect a rising rate of failed connection attempts, which points to call agent or network signaling problems. It complements CISCO-VISM-MODULE-MIB's card-level call statistics by providing protocol-specific signaling detail. It is deployed on Cisco MGX 8000-series WAN switches running VISM modules configured for MGCP/xGCP-based voice gateway control. Engineers can download the CISCO-VISM-XGCP-EXT file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in CISCO-VISM-XGCP-EXT. 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 MGX 8000-series WAN switches with VISM modules

Monitoring Examples

An administrator would poll vismXgcpMsgStatTable / vismXgcpMsgStatEntry, comparing vismXgcpCrcxCnts to vismXgcpCrcxFailCnts for a specific vismXgcpPeerNumber to detect a spike in failed connection-creation requests, indicating a problem with the call agent or peer relationship. The vismXgcpPeerTable would be checked to confirm the peer's vismXgcpPeerProtocolNumber and vismXgcpPeerPort are correctly configured. vismXgcpRequestMaxTimeout tuning might be considered if failures correlate with slow call agent responses.

What Can Be Monitored

xGCP peer configuration (protocol, port)
CRCX (connection creation) success/failure counts
request timeout settings
per-peer message statistics

Imported Objects

From BASIS-MIB

voice

OBJECT-IDENTITY

From CISCOWAN-SMI

ciscoWan

OBJECT-IDENTITY

From SNMPv2-CONF

MODULE-COMPLIANCE
OBJECT-GROUP

From SNMPv2-SMI

Counter32
Integer32
IpAddress
MODULE-IDENTITY
OBJECT-TYPE

How to Use in IPNetwork Monitor

Example using vismXgcpCrcxCnts OID:

Select a Cisco VISM (Voice Interworking Service Module) card, MGX platform (legacy) 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 vismXgcpCrcxCnts into the Find box to locate it in the OID tree, selecting the specific row/instance you want to monitor since this is a table column, then select it and click OK. This refers to the count of CRCX (Create Connection) messages received from the call agent since 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

OID symbolic	OID numeric	Type	Access	Description
vismXgcpExtensionGrp	1.3.6.1.4.1.351.110.5.5.5
vismXgcpCoreObjects	1.3.6.1.4.1.351.110.5.5.5.1
I32 vismXgcpRequestMaxTimeout	1.3.6.1.4.1.351.110.5.5.5.1.1	Integer32	read-write	This object specifies the maximum timeout value. This timer value is used along with xgcpRequestTimeout and xgcpRequestRetries (in xgcpGrp.my) to determine the exponential retry interval for retransmitting unacknowledged xgcp messages. The value of this timer has to be greater than or equal to xgcpRequestTimeout. The default value of this object is 500 milliseconds. When the value of this object changes vismXgcpCoreObjects changed trap will be sent.
I32 vismXgcpPort	1.3.6.1.4.1.351.110.5.5.5.1.2	Integer32	read-write	This object is used to configure the local UDP port on VISM used by the SGCP and MGCP protocols to communicate with the call agent. The UDP port is used together with vismIpAddress to identify the local end of a SGCP/MGCP connection. The default value of this object is 2427. In VISM 1.5 this object always defaults to 2427 and is read-only.
vismXgcpPeerTable	1.3.6.1.4.1.351.110.5.5.5.1.3		not-accessible	This table is used to provision peer-specific XGCP configuration information. Each table entry corresponds to an XGCP peer name / peer XGCP variant combination.
vismXgcpPeerEntry	1.3.6.1.4.1.351.110.5.5.5.1.3.1		not-accessible	Each row is identified by XGCP peer name and peer XGCP protocol number combination. This means, if an MGC uses more than one variant of XGCP (i.e MGCP, SGCP 1.0, SGCP 1.1 etc), an entry will be maintained for each of the protocols. mgcNumber and mgcProtocolNumber from MGMIB are used as foreign index to this table. Entries in this table are implicitly created by the agent. An entry shall be created when an entry is created in the mgcProtocolTable and when mgcProtocolNumber refers to an XGCP variant (i.e MGCP, SGCP 1.0, SGCP 1.1 etc) as supported protocol. An entry shall be deleted if the corresponding entry in the mgcProtocolTable is deleted. As both mgcProtocolTable and vismXgcpPeerTable have mgcNumber and mgcProtocolNumber as index, referential integrity between the two tables is automatically ensured.
I32 vismXgcpPeerNumber	1.3.6.1.4.1.351.110.5.5.5.1.3.1.1	Integer32	read-only	The value of this object is the same as mgcNumber from MGMIB.
I32 vismXgcpPeerProtocolNumber	1.3.6.1.4.1.351.110.5.5.5.1.3.1.2	Integer32	read-only	The value of this object is the same as mgcProtocolNumber from MGMIB.
I32 vismXgcpPeerPort	1.3.6.1.4.1.351.110.5.5.5.1.3.1.3	Integer32	read-write	This object is used to configure the local UDP port on VISM used by the SGCP and MGCP protocols to communicate with the call agent. The UDP port is used together with vismIpAddress to identify the local end of a SGCP/MGCP connection. If the protocol configured for the call agent is MGCP 1.0, the default port is 2727. In all other cases, the default value of this object is 2427. In VISM 1.5 this object always defaults to 2427 and is read-only.
vismXgcpMsgStatTable	1.3.6.1.4.1.351.110.5.5.5.1.4		not-accessible	This table is an extension to the xgcpMsgStatTable contained in the XGCP MIB. This table provides per-message type based detailed statistics information.
vismXgcpMsgStatEntry	1.3.6.1.4.1.351.110.5.5.5.1.4.1		not-accessible	The row of the vismXgcpMsgStatTable contains additional information about XGCP message statistics beyond that provided by the XGCP MIB.
IP vismXgcpIpAddress	1.3.6.1.4.1.351.110.5.5.5.1.4.1.1	IpAddress	read-only	This object specifies the IP address of the Media Gateway Controller. The value of this object is the same as xgcpIpAddress of XGCP-MIB.
C32 vismXgcpCrcxCntsEx	1.3.6.1.4.1.351.110.5.5.5.1.4.1.2	Counter32	read-only	This refers to the count of CRCX (Create Connection) messages received from the call agent since reset.
C32 vismXgcpCrcxFailCnts	1.3.6.1.4.1.351.110.5.5.5.1.4.1.3	Counter32	read-only	This refers to the count of CRCX (Create Connection) messages received from the call agent that were responded to with a failure return code.
C32 vismXgcpMdcxCnts	1.3.6.1.4.1.351.110.5.5.5.1.4.1.4	Counter32	read-only	This refers to the count of MDCX (Modify Connection) messages received from the call agent since reset.
C32 vismXgcpMdcxFailCnts	1.3.6.1.4.1.351.110.5.5.5.1.4.1.5	Counter32	read-only	This refers to the count of MDCX (Modify Connection) messages received from the call agent that were responded to with a failure return code.
C32 vismXgcpDlcxRcvCnts	1.3.6.1.4.1.351.110.5.5.5.1.4.1.6	Counter32	read-only	This refers to the count of DLCX (Delete Connection) messages received from the call agent since reset.
C32 vismXgcpDlcxRcvFailCnts	1.3.6.1.4.1.351.110.5.5.5.1.4.1.7	Counter32	read-only	This refers to the count of DLCX (Delete Connection) messages received from the call agent that were responded to with a failure return code.
C32 vismXgcpDlcxSentCnts	1.3.6.1.4.1.351.110.5.5.5.1.4.1.8	Counter32	read-only	This refers to the count of DLCX (Delete Connection) messages sent to the call agent since reset.
C32 vismXgcpDlcxSentFailCnts	1.3.6.1.4.1.351.110.5.5.5.1.4.1.9	Counter32	read-only	This refers to the count of DLCX (Delete Connection) messages sent to the call agent for which a response with failure return code was received or which timed out waiting for an acknowledgement.
C32 vismXgcpRqntCnts	1.3.6.1.4.1.351.110.5.5.5.1.4.1.10	Counter32	read-only	This refers to the count of RQNT (Request Notify) messages received from the call agent since reset.
C32 vismXgcpRqntFailCnts	1.3.6.1.4.1.351.110.5.5.5.1.4.1.11	Counter32	read-only	This refers to the count of RQNT (Request Notify) messages received from the call agent that were responded to with a failure return code.
C32 vismXgcpNtfyCnts	1.3.6.1.4.1.351.110.5.5.5.1.4.1.12	Counter32	read-only	This refers to the count of NTFY (Notify) messages sent to the call agent since reset.
C32 vismXgcpNtfyFailCnts	1.3.6.1.4.1.351.110.5.5.5.1.4.1.13	Counter32	read-only	This refers to the count of NTFY (Notify) messages sent to the call agent for which a response with failure return code was received or which timed out waiting for a response.
C32 vismXgcpAuepCnts	1.3.6.1.4.1.351.110.5.5.5.1.4.1.14	Counter32	read-only	This refers to the count of AUEP (Audit Endpoint) messages received from the call agent since reset.
C32 vismXgcpAuepFailCnts	1.3.6.1.4.1.351.110.5.5.5.1.4.1.15	Counter32	read-only	This refers to the count of AUEP (Audit Endpoint) messages received from the call agent that were responded to with a failure return code.
C32 vismXgcpAucxCnts	1.3.6.1.4.1.351.110.5.5.5.1.4.1.16	Counter32	read-only	This refers to the count of AUCX (Audit Connection) messages received from the call agent since reset.
C32 vismXgcpAucxFailCnts	1.3.6.1.4.1.351.110.5.5.5.1.4.1.17	Counter32	read-only	This refers to the count of AUCX (Audit Connection) messages received from the call agent that were responded to with a failure return code.
C32 vismXgcpRsipCnts	1.3.6.1.4.1.351.110.5.5.5.1.4.1.18	Counter32	read-only	This refers to the count of RSIP (Restart In Progress) messages sent to the call agent since reset.
C32 vismXgcpRsipFailCnts	1.3.6.1.4.1.351.110.5.5.5.1.4.1.19	Counter32	read-only	This refers to the count of RSIP (Restart In Progress) messages sent to the call agent for which a response with failure return code was received or which timed out waiting for a response.
vismXgcpEnhancementsObjects	1.3.6.1.4.1.351.110.5.5.5.2
I32 vismXgcpRestartInProgressTdinit	1.3.6.1.4.1.351.110.5.5.5.2.1	Integer32	read-write	The endpoint becomes disconnected when it tries to communicate with the call agent and the retransmission procedure times out after retrying. The endpoint in disconnected state starts the disconnected timer initialised to the random value and uniformly distributed between 1 and initial waiting delay (Tdinit) in seconds. The gateway waits for either the end of this timer, or the reception of call agent command or the detection of local user activity for the endpoint. When the disconnected timer elapses, or when a command is received from the call agent or when there is a local user activity, the Media Gateway sends the Restart In Progress command with the restart method as RM:disconnected to the Media Gateway Controller. The initial waiting delay (Tdinit) timeout value is defined by this MIB object. The recommended value of this object is 15 seconds.
I32 vismXgcpRestartInProgressTdmin	1.3.6.1.4.1.351.110.5.5.5.2.2	Integer32	read-write	The endpoint becomes disconnected when it tries to communicate with the call agent and the retransmission procedure times out after retrying. The endpoint in disconnected state starts the disconnected timer initialised to the random value and uniformly distributed between 1 and initial waiting delay (Tdinit) in seconds. The gateway waits for either the end of this timer, or the reception of call agent command or the detection of local user activity for the endpoint. When the disconnected timer elapses, or when a command is received from the call agent or when there is a local user activity, the Media Gateway sends the Restart In Progress command with the restart method as RM:disconnected to the Media Gateway Controller. In case of local user activity, a provisionable disconnected minimum waiting delay (Tdmin) must have been elapsed since the gateway became disconnected. The minimum waiting delay (Tdmin) timeout value used by the Media Gateway to send the Restart In Progress with the restart method as RM:disconnected to the Media Gateway Controller if there is any local user activity is defined by this object. Media Gateway initiated delete connection (DLCX) or restart in progress (RSIP) commands are not considered as local user activity. The events observed on the TDM interface or on the network constitute the local user activity. The recommended value of this object is 15 seconds.
I32 vismXgcpRestartInProgressTdmax	1.3.6.1.4.1.351.110.5.5.5.2.3	Integer32	read-write	The maximum waiting delay (Tdmax) timeout value used by the Media Gateway to send the Restart In Progress with the restart method as RM:disconnected to the Media Gateway Controller when the endpoint has become disconnected is defined by this object. The endpoint becomes disconnected when it tries to communicate with the call agent and the retransmission procedure times out after retrying. The endpoint in disconnected state starts the disconnected timer initialised to the random value and uniformly distributed between 1 and initial waiting delay (Tdinit) in seconds. The gateway waits for either the end of this timer, or the reception of call agent command or the detection of local user activity for the endpoint. When the disconnected timer elapses, or when a command is received from the call agent or when there is a local user activity, the Media Gateway sends the Restart In Progress command with the restart method as RM:disconnected to the Media Gateway Controller. If the disconnected procedure still left the endpoint disconnected, the disconnected timer is doubled subject to a provisionable disconnected maximum waiting delay (Tdmax) in seconds and the gateway starts the new disconnected procedure again. Once the maximum value is reached, the subsequent disconnected Restart In Progress commands use the maximum waiting delay (Tdmax). The recommended value of this object is 600 seconds.
ciscoVismXgcpExtMIB	1.3.6.1.4.1.351.150.94			The MIB module contain the XGCP MIB feature in VISM
ciscoVismXgcpExtMIBConformance	1.3.6.1.4.1.351.150.94.2
ciscoVismXgcpExtMIBGroups	1.3.6.1.4.1.351.150.94.2.1
ciscoVismXgcpExtensionGroup	1.3.6.1.4.1.351.150.94.2.1.1			The collection of objects which are used to represent VISM XGCP MIB.
ciscoVismXgcpCoreGroup	1.3.6.1.4.1.351.150.94.2.1.2			The collection of objects which are used to represent VISM peer XGCP MIB configuration.
ciscoVismXgcpStatsGroup	1.3.6.1.4.1.351.150.94.2.1.3			The collection of objects which are used to represent VISM peer XGCP MIB Statistics information.
ciscoVismXgcpEnhancementGroup	1.3.6.1.4.1.351.150.94.2.1.4			The collection of objects which are used to represent VISM XGCP Enhancement.
ciscoVismXgcpExtMIBCompliances	1.3.6.1.4.1.351.150.94.2.2
ciscoVismXgcpExtCompliance	1.3.6.1.4.1.351.150.94.2.2.1			The compliance statement for objects related to VISM-XGCP-MIB.

RFC description

Extends XGCP (eXternal Gateway Control Protocol) MIB with VISM-specific features.

Start monitoring Cisco VISM (Voice Interworking Service Module) card, MGX platform (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.

Download CISCO-VISM-XGCP-EXT