CISCO-VISM-XGCP-EXT :: vismXgcpRestartInProgressTdmax

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › CISCO-VISM-XGCP-EXT › vismXgcpRestartInProgressTdmax

vismXgcpRestartInProgressTdmax

Module: CISCO-VISM-XGCP-EXT

OID (symbolic): CISCO-VISM-XGCP-EXT::vismXgcpRestartInProgressTdmax

OID (numeric): 1.3.6.1.4.1.351.110.5.5.5.2.3

Node type: OBJECT-TYPE

Type: Integer32

Access: read-write

Description: 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.

What is vismXgcpRestartInProgressTdmax?

This read-write Integer32 (1-5000 seconds) is the maximum waiting delay (Tdmax) used as the timeout for the gateway to send a Restart In Progress message with restart method RM:disconnected, after an endpoint has become disconnected because retransmission retries to the call agent timed out. An admin cares because this ceiling bounds how long the gateway will wait before formally notifying the call agent that the endpoint is disconnected. For example, an operator wanting faster call-agent awareness of a disconnected endpoint would lower this Tdmax so the RSIP with RM:disconnected is sent sooner after the disconnection is detected.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.351.110.5.5.5.2.3
snmpwalk -v2c -c public <target> CISCO-VISM-XGCP-EXT::vismXgcpRestartInProgressTdmax

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.351.110.5.5.5.2.3.1
snmpget -v2c -c public <target> CISCO-VISM-XGCP-EXT::vismXgcpRestartInProgressTdmax.1

Set instance 1 (SNMPv2c):

snmpset -v2c -c private <target> 1.3.6.1.4.1.351.110.5.5.5.2.3.1 i <value>

Start monitoring Cisco VISM (Voice Interworking Service Module) card, MGX platform (legacy) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CISCO-VISM-XGCP-EXT::vismXgcpRestartInProgressTdmax OID value, configure state conditions and alerts, and monitor any Cisco VISM (Voice Interworking Service Module) card, MGX platform (legacy) from a single console.

OID Breakdown

Upper-level ancestors (10 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.351stratacomCISCOWAN-SMI
1.3.6.1.4.1.351.110basisBASIS-MIB
1.3.6.1.4.1.351.110.5basisServicesBASIS-MIB
1.3.6.1.4.1.351.110.5.5voiceBASIS-MIB
Numeric OIDNameModule
1.3.6.1.4.1.351.110.5.5.5vismXgcpExtensionGrpCISCO-VISM-XGCP-EXT
1.3.6.1.4.1.351.110.5.5.5.2vismXgcpEnhancementsObjectsCISCO-VISM-XGCP-EXT
1.3.6.1.4.1.351.110.5.5.5.2.3vismXgcpRestartInProgressTdmaxCISCO-VISM-XGCP-EXT