All MIBs › CISCO-VISM-DSX0-MIB › ds0CasDirectionality
ds0CasDirectionality
Module: CISCO-VISM-DSX0-MIB
OID (symbolic): CISCO-VISM-DSX0-MIB::ds0CasDirectionality
OID (numeric): 1.3.6.1.4.1.351.110.4.7.1.1.29
Node type: OBJECT-TYPE
Type: INTEGER
Access: read-write
Description: This object specifies the direction in which CAS calls will be accepted on this endpoint. If this object is set to
bidirectional(1): VISM can send and receive calls on this endpoint incoming(2) : calls from the connected PBX will be accepted by VISM on this endpoint. outgoing(3) : VISM will send calls towards the connected PBX and not accept calls from the PBX.
The main difference between bidirectional and one-way trunks is the occurrence of glare. On bidirectional trunks, since both VISM and the connected PBX can seize the endpoint at approximately the same time, glare (dual seizure) is likely to occur. The protocol assigned to a bidirectional endpoint should be capable of detecting and resolving glare. Wink-start and delay-dial are examples of protocols capable of glare handling and immediate-start, ground-start and loop-start, of those that cannot.
This object cannot be configured if the signaling type for the DS1 line to which this ds0 belongs is non-CAS.
For a CAS line, this object can only be configured after associating this ds0 with an endpoint. This means that if no endpoint was added for this Ds0, any configuration set attempt will be rejected, but any get will be allowed.
What is ds0CasDirectionality?
This read-write INTEGER specifies which direction CAS calls are accepted on this endpoint: bidirectional (both send and receive), incoming (only accepts calls from the PBX), or outgoing (only sends calls toward the PBX). Restricting directionality lets an admin enforce trunk usage policy, such as reserving certain DS0s strictly for outbound traffic to avoid contention with inbound call handling. For example, setting ds0CasDirectionality to outgoing on a subset of DS0s would ensure those channels are never seized by inbound PBX-originated calls.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.351.110.4.7.1.1.29 snmpwalk -v2c -c public <target> CISCO-VISM-DSX0-MIB::ds0CasDirectionality
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.351.110.4.7.1.1.29.1 snmpget -v2c -c public <target> CISCO-VISM-DSX0-MIB::ds0CasDirectionality.1
Set instance 1 (SNMPv2c):
snmpset -v2c -c private <target> 1.3.6.1.4.1.351.110.4.7.1.1.29.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-DSX0-MIB::ds0CasDirectionality 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.29 | ds0CasDirectionality | CISCO-VISM-DSX0-MIB |