OID reference

mpsSysChargeProtocol

1.3.6.1.4.1.272.4.53.1.3.1

Description

This value determine the charging protocol on the internal isdn ports. You have three options here: KEYPAD protocol - Charge data is transferred such that it can be displayed directly by the terminal device. Functional protocol - Charge data is transferred with binary encoding and must be decoded by the terminal devic…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.272.4.53.1.3 (mpsSysCharge)
Node code
1
Node name
mpsSysChargeProtocol
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.272.4.53.1.3.1
URN notation
urn:oid:1.3.6.1.4.1.272.4.53.1.3.1
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 272 4 53 1 3 1}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) bintec(272) bibo(4) mpsMIB(53) mpsSetup(1) mpsSysCharge(3) mpsSysChargeProtocol(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) bintec(272) bibo(4) mpsMIB(53) mpsSetup(1) mpsSysCharge(3) mpsSysChargeProtocol(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) bintec(272) bibo(4) mpsMIB(53) mpsSetup(1) mpsSysCharge(3) mpsSysChargeProtocol(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) bintec(272) bibo(4) mpsMIB(53) mpsSetup(1) mpsSysCharge(3) mpsSysChargeProtocol(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) bintec(272) bibo(4) mpsMIB(53) mpsSetup(1) mpsSysCharge(3) mpsSysChargeProtocol(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) bintec(272) bibo(4) mpsMIB(53) mpsSetup(1) mpsSysCharge(3) mpsSysChargeProtocol(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) bintec(272) bibo(4) mpsMIB(53) mpsSetup(1) mpsSysCharge(3) mpsSysChargeProtocol(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) bintec(272) bibo(4) mpsMIB(53) mpsSetup(1) mpsSysCharge(3) mpsSysChargeProtocol(1)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) bintec(272) bibo(4) mpsMIB(53) mpsSetup(1) mpsSysCharge(3) mpsSysChargeProtocol(1)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) bintec(272) bibo(4) mpsMIB(53) mpsSetup(1) mpsSysCharge(3) mpsSysChargeProtocol(1)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) bintec(272) bibo(4) mpsMIB(53) mpsSetup(1) mpsSysCharge(3) mpsSysChargeProtocol(1)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) bintec(272) bibo(4) mpsMIB(53) mpsSetup(1) mpsSysCharge(3) mpsSysChargeProtocol(1)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) bintec(272) bibo(4) mpsMIB(53) mpsSetup(1) mpsSysCharge(3) mpsSysChargeProtocol(1)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) bintec(272) bibo(4) mpsMIB(53) mpsSetup(1) mpsSysCharge(3) mpsSysChargeProtocol(1)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) bintec(272) bibo(4) mpsMIB(53) mpsSetup(1) mpsSysCharge(3) mpsSysChargeProtocol(1)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) bintec(272) bibo(4) mpsMIB(53) mpsSetup(1) mpsSysCharge(3) mpsSysChargeProtocol(1)}
OID-IRI notation
  • /1/3/6/1/4/1/272/4/53/1/3/1
  • /ISO/Identified-Organization/6/1/4/1/272/4/53/1/3/1
  • /ISO/3/6/1/4/1/272/4/53/1/3/1
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/bintec/bibo/mpsMIB/mpsSetup/mpsSysCharge/mpsSysChargeProtocol
  • /iso/identified-organization/dod/internet/private/enterprises/bintec/bibo/mpsMIB/mpsSetup/mpsSysCharge/mpsSysChargeProtocol
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/bintec/bibo/mpsMIB/mpsSetup/mpsSysCharge/mpsSysChargeProtocol
  • /iso/identified-organization/dod/internet/private/vendor-objects/bintec/bibo/mpsMIB/mpsSetup/mpsSysCharge/mpsSysChargeProtocol
  • /iso/org/dod/internet/private/enterprise/bintec/bibo/mpsMIB/mpsSetup/mpsSysCharge/mpsSysChargeProtocol
  • /iso/org/dod/internet/private/enterprises/bintec/bibo/mpsMIB/mpsSetup/mpsSysCharge/mpsSysChargeProtocol
  • /iso/org/dod/internet/private/ldap-enterprise/bintec/bibo/mpsMIB/mpsSetup/mpsSysCharge/mpsSysChargeProtocol
  • /iso/org/dod/internet/private/vendor-objects/bintec/bibo/mpsMIB/mpsSetup/mpsSysCharge/mpsSysChargeProtocol
  • /iso/iso-identified-organization/dod/internet/private/enterprise/bintec/bibo/mpsMIB/mpsSetup/mpsSysCharge/mpsSysChargeProtocol
  • /iso/iso-identified-organization/dod/internet/private/enterprises/bintec/bibo/mpsMIB/mpsSetup/mpsSysCharge/mpsSysChargeProtocol
  • /iso/iso-identified-organization/dod/internet/private/ldap-enterprise/bintec/bibo/mpsMIB/mpsSetup/mpsSysCharge/mpsSysChargeProtocol
  • /iso/iso-identified-organization/dod/internet/private/vendor-objects/bintec/bibo/mpsMIB/mpsSetup/mpsSysCharge/mpsSysChargeProtocol
  • /iso/iso-organization/dod/internet/private/enterprise/bintec/bibo/mpsMIB/mpsSetup/mpsSysCharge/mpsSysChargeProtocol
  • /iso/iso-organization/dod/internet/private/enterprises/bintec/bibo/mpsMIB/mpsSetup/mpsSysCharge/mpsSysChargeProtocol
  • /iso/iso-organization/dod/internet/private/ldap-enterprise/bintec/bibo/mpsMIB/mpsSetup/mpsSysCharge/mpsSysChargeProtocol
  • /iso/iso-organization/dod/internet/private/vendor-objects/bintec/bibo/mpsMIB/mpsSetup/mpsSysCharge/mpsSysChargeProtocol

SNMP properties

Value type
INTEGER
Maximum access defined by MIB
read-write
Status in MIB
current
Default value
keypad-and-functional

Enumerated values

ValueName
1keypad-and-functional
2no-keypad
3no-functional

Using this OID with SNMP

At least one MIB declaration places this object in a scalar group. A scalar instance uses the suffix .0.

snmpget [connection options] DEVICE .1.3.6.1.4.1.272.4.53.1.3.1.0

Replace the placeholders with your connection and authentication options. Available permissions and device support can differ from the MIB.

Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.

The displayed source records contain one distinct definition. Compare its source records.

mpsSysChargeProtocol OBJECT-TYPE
        SYNTAX          INTEGER {
                            keypad-and-functional(1),
                            no-keypad(2),
                            no-functional(3)
                        }
        MAX-ACCESS      read-write
        STATUS          current
        DESCRIPTION
            "This value determine the charging protocol on the internal isdn 
             ports. You have three options here: KEYPAD protocol - Charge data 
             is transferred such that it can be displayed directly by the 
             terminal device.
             Functional protocol - Charge data is transferred with binary 
             encoding and must be decoded by the terminal device. 
             Both - Both of these protocols are recognized (default settings 
             for the PBX system."
        DEFVAL { keypad-and-functional }
        ::= { mpsSysCharge 1 }

Meaning

Descriptions

1 unique

Identical descriptions are grouped. Different wording and device-specific notes are retained.

This value determine the charging protocol on the internal isdn ports. You have three options here: KEYPAD protocol - Charge data is transferred such that it can be displayed directly by the terminal device. Functional protocol - Charge data is transferred with binary encoding and must be decoded by the terminal device. Both - Both of these protocols are recognized (default settings for the PBX system.

Sources for this description

Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)

See 1 matching source record

Evidence

Source records

1 records

Matching descriptions are grouped; open a group to compare definitions and supporting files.

Records for description 1Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)1 record · 1 source

Description 1

mpsSysChargeProtocol · currentMultiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)1 source

Status in source: current.

Names: mpsSysChargeProtocol

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "mpsSysChargeProtocol",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "keypad-and-functional",
    "(",
    "1",
    ")",
    ",",
    "no-keypad",
    "(",
    "2",
    ")",
    ",",
    "no-functional",
    "(",
    "3",
    ")",
    "}",
    "MAX-ACCESS",
    "read-write",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"This value determine the charging protocol on the internal isdn ports. You have three options here: KEYPAD protocol - Charge data is transferred such that it can be displayed directly by the terminal device. Functional protocol - Charge data is transferred with binary encoding and must be decoded by the terminal device. Both - Both of these protocols are recognized (default settings for the PBX system.\"",
    "DEFVAL",
    "{",
    "keypad-and-functional",
    "}",
    "::=",
    "{",
    "mpsSysCharge",
    "1",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "keypad-and-functional",
            1
          ],
          [
            "no-keypad",
            2
          ],
          [
            "no-functional",
            3
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "This value determine the charging protocol on the internal isdn ports. You have three options here: KEYPAD protocol - Charge data is transferred such that it can be displayed directly by the terminal device. Functional protocol - Charge data is transferred with binary encoding and must be decoded by the terminal device. Both - Both of these protocols are recognized (default settings for the PBX system."
    ],
    null,
    null,
    null,
    [
      "DEFVAL",
      "keypad-and-functional"
    ]
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.272)

Hertlein Elisabeth

Siblings (12)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.272.4.53.1.3.2 mpsSysChargeFrequency00
1.3.6.1.4.1.272.4.53.1.3.3 mpsSysChargeIncomingCall00
1.3.6.1.4.1.272.4.53.1.3.4 mpsSysChargeMultiplier00
1.3.6.1.4.1.272.4.53.1.3.5 mpsSysChargeExponent00
1.3.6.1.4.1.272.4.53.1.3.6 mpsSysChargeCurrencyName00
1.3.6.1.4.1.272.4.53.1.3.7 mpsSysChargeExtensionIndex00
1.3.6.1.4.1.272.4.53.1.3.8 mpsSysChargeHiddenDigitsCountA00
1.3.6.1.4.1.272.4.53.1.3.9 mpsSysChargeHiddenDigitsCountB00
1.3.6.1.4.1.272.4.53.1.3.10 mpsSysChargeSaveOutgoingCall00
1.3.6.1.4.1.272.4.53.1.3.11 mpsSysChargeSaveIncomingCall00
1.3.6.1.4.1.272.4.53.1.3.12 mpsSysChargePrintingHost00
1.3.6.1.4.1.272.4.53.1.3.13 mpsSysChargePrintingTcpPort00