CISCO-VISM-XGCP-EXT :: vismXgcpRestartInProgressTdmin

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

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

vismXgcpRestartInProgressTdmin

Module: CISCO-VISM-XGCP-EXT

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

OID (numeric): 1.3.6.1.4.1.351.110.5.5.5.2.2

Node type: OBJECT-TYPE

Type: Integer32

Access: read-write

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

What is vismXgcpRestartInProgressTdmin?

This read-write Integer32 (0-100 seconds) sets the minimum bound of the random range used to seed the disconnected-state timer, which is uniformly distributed between 1 and Tdinit, when an endpoint loses communication with the call agent. An admin cares because this minimum bound, together with Tdinit, shapes the randomization window used to stagger reconnection attempts and avoid a synchronized retry storm. For example, an operator fine-tuning reconnection behavior after a widespread outage would adjust this minimum alongside Tdinit to control how spread out endpoint reconnection attempts are.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.351.110.5.5.5.2.2
snmpwalk -v2c -c public <target> CISCO-VISM-XGCP-EXT::vismXgcpRestartInProgressTdmin

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.351.110.5.5.5.2.2.1
snmpget -v2c -c public <target> CISCO-VISM-XGCP-EXT::vismXgcpRestartInProgressTdmin.1

Set instance 1 (SNMPv2c):

snmpset -v2c -c private <target> 1.3.6.1.4.1.351.110.5.5.5.2.2.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::vismXgcpRestartInProgressTdmin 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.2vismXgcpRestartInProgressTdminCISCO-VISM-XGCP-EXT