All MIBs › CISCO-VISM-DSX0-MIB › ds0CasMinDelayDialTime
ds0CasMinDelayDialTime
Module: CISCO-VISM-DSX0-MIB
OID (symbolic): CISCO-VISM-DSX0-MIB::ds0CasMinDelayDialTime
OID (numeric): 1.3.6.1.4.1.351.110.4.7.1.1.25
Node type: OBJECT-TYPE
Type: Integer32
Access: read-write
Description: This is an object for an E & M signaling protocol like wink-start for this ds0. The difference is that the address-control signal is different from wink. The originating VISM, on receiving a seize (AB=11) from the PBX, responds by sending the delay-dial (AB=11) signal back to the PBX. When the originating VISM is ready to collect the digits, it sends a start-dial (AB=00) signal. This operation is symmetric. So the terminating VISM, on seizing a trunk, should receive AB=11 (as an ack that the trunk is operational). Subsequently, when it receives the start signal (AB=00) from the connected PBX, it should outpulse the digits. The rest of the operation is similiar to wink-start.
The allowed range for this object is 100..1000 with units in milliseconds.
In delay-dial operation, the outgoing interface (this interface), after sending a seize signal (AB = 11), waits for the delay-dial signal (AB = 11). The delay-dial signal, apart from acknowledging the seize signal, tells this interface that the connected equipment is not ready for the digits yet. This object specifies the time in milliseconds, after which incoming AB=11 will be interpreted by this interface as the delay-dial signal.
What is ds0CasMinDelayDialTime?
This Integer32 (in milliseconds) is used for an E&M signaling protocol similar to wink-start on this DS0, where the address-control signal differs from a standard wink; the originating VISM responds to a seize with a delay-dial signal before sending start-dial once ready to collect digits. This timing governs how the two ends of a CAS trunk negotiate readiness to exchange dialed digits, so misconfiguration can desynchronize call setup between the originating and terminating gateways. For instance, an admin integrating with legacy E&M PBX equipment using this delay-dial variant would tune ds0CasMinDelayDialTime to match the expected timing on that equipment.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.351.110.4.7.1.1.25 snmpwalk -v2c -c public <target> CISCO-VISM-DSX0-MIB::ds0CasMinDelayDialTime
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.351.110.4.7.1.1.25.1 snmpget -v2c -c public <target> CISCO-VISM-DSX0-MIB::ds0CasMinDelayDialTime.1
Set instance 1 (SNMPv2c):
snmpset -v2c -c private <target> 1.3.6.1.4.1.351.110.4.7.1.1.25.1 i <value>
SNMPv3 example:
snmpget -v3 -l authPriv -u snmpv3-user -a SHA -A "AuthPassword1" -x AES -X "PrivPassword1" <target> ds0CasMinDelayDialTime.1
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-DSX0-MIB::ds0CasMinDelayDialTime 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 OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | AirPair-MIB |
| 1.3.6 | dod | AirPair-MIB |
| 1.3.6.1 | internet | AirPair-MIB |
| 1.3.6.1.4 | private | AirPair-MIB |
| 1.3.6.1.4.1 | enterprises | AirPair-MIB |
| 1.3.6.1.4.1.351 | stratacom | CISCOWAN-SMI |
| 1.3.6.1.4.1.351.110 | basis | BASIS-MIB |
| 1.3.6.1.4.1.351.110.4 | basisLines | BASIS-MIB |
| 1.3.6.1.4.1.351.110.4.7 | dsx0Vism | BASIS-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.351.110.4.7.1 | dsx0VismCnfTable | CISCO-VISM-DSX0-MIB |
| 1.3.6.1.4.1.351.110.4.7.1.1 | dsx0VismCnfEntry | CISCO-VISM-DSX0-MIB |
| 1.3.6.1.4.1.351.110.4.7.1.1.25 | ds0CasMinDelayDialTime | CISCO-VISM-DSX0-MIB |