Nortel-MsCarrier-MscPassport-TdmaIwfMIB :: mscTdmaCsV42BisP0CompressionDirection

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › Nortel-MsCarrier-MscPassport-TdmaIwfMIB › mscTdmaCsV42BisP0CompressionDirection

mscTdmaCsV42BisP0CompressionDirection

Module: Nortel-MsCarrier-MscPassport-TdmaIwfMIB

OID (symbolic): Nortel-MsCarrier-MscPassport-TdmaIwfMIB::mscTdmaCsV42BisP0CompressionDirection

OID (numeric): 1.3.6.1.4.1.562.36.2.1.135.8.10.1.1

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-write

Description: This attribute specifies the V.42bis data compression direction to be supported. The value for compression direction is negotiated at link setup by the data link protocol by way of the Exchange Identification (XID) negotiation of parameter P0 (compression direction). During XID negotiation of parameter P0, both sides (IWF and mobile or IWF and PSTN) agree on the compression direction. This attribute has one of the following values: noCompression: No compression is present. compInitrResp: The data sent by the IWF to the other entity is compressed. compRespInitr: The data received by the IWF from the other entity is compressed. compBoth: The data sent and received by the IWF is compressed. Changes to this attribute do not affect existing calls.

What is mscTdmaCsV42BisP0CompressionDirection?

A read-write setting (default compBoth) choosing which direction(s) of V.42bis data compression the IWF supports: none, IWF-to-remote only (compInitrResp), remote-to-IWF only (compRespInitr), or both (compBoth); the actual direction used is negotiated at link setup via the XID parameter P0. Admins would set this to something other than compBoth if compressing only one direction is preferred, e.g. to reduce CPU load when traffic is predominantly one-way; changes only affect new calls, not calls already in progress.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.562.36.2.1.135.8.10.1.1
snmpwalk -v2c -c public <target> Nortel-MsCarrier-MscPassport-TdmaIwfMIB::mscTdmaCsV42BisP0CompressionDirection

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.562.36.2.1.135.8.10.1.1.1
snmpget -v2c -c public <target> Nortel-MsCarrier-MscPassport-TdmaIwfMIB::mscTdmaCsV42BisP0CompressionDirection.1

Set instance 1 (SNMPv2c):

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

Start monitoring Nortel MsCarrier MscPassport switch (TDMA mobile interworking function) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the Nortel-MsCarrier-MscPassport-TdmaIwfMIB::mscTdmaCsV42BisP0CompressionDirection OID value, configure state conditions and alerts, and monitor any Nortel MsCarrier MscPassport switch (TDMA mobile interworking function) 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.562nortelCPM-NORTEL-MIB
1.3.6.1.4.1.562.36msCarrierNortel-MsCarrier-MscPassport-UsefulDefinitionsMIB
1.3.6.1.4.1.562.36.2mscPassportNortel-MsCarrier-MscPassport-UsefulDefinitionsMIB
1.3.6.1.4.1.562.36.2.1mscComponentsNortel-MsCarrier-MscPassport-UsefulDefinitionsMIB
Numeric OIDNameModule
1.3.6.1.4.1.562.36.2.1.135mscTdmaCsNortel-MsCarrier-MscPassport-TdmaIwfMIB
1.3.6.1.4.1.562.36.2.1.135.8mscTdmaCsV42BisNortel-MsCarrier-MscPassport-TdmaIwfMIB
1.3.6.1.4.1.562.36.2.1.135.8.10mscTdmaCsV42BisProvTableNortel-MsCarrier-MscPassport-TdmaIwfMIB
1.3.6.1.4.1.562.36.2.1.135.8.10.1mscTdmaCsV42BisProvEntryNortel-MsCarrier-MscPassport-TdmaIwfMIB
1.3.6.1.4.1.562.36.2.1.135.8.10.1.1mscTdmaCsV42BisP0CompressionDirectionNortel-MsCarrier-MscPassport-TdmaIwfMIB