OID reference

mobileSmsSendMsgStatus

1.3.6.1.4.1.272.4.41.4.1.24.1.5

Description

The Status of the SMS. To start transmission of the SMS set Status to `transmit(1)'. On successful transmission the Status is set to `success(2)'. Afterwards the SMS is moved to the 'mobileSmsTable'. When transmission fails the Status changes to `error(3)'. The SMS stays in 'mobileSmsSendTable' for retransmissions. If…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.272.4.41.4.1.24.1 (mobileSmsSendEntry)
Node code
5
Node name
mobileSmsSendMsgStatus
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.272.4.41.4.1.24.1.5
URN notation
urn:oid:1.3.6.1.4.1.272.4.41.4.1.24.1.5
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 272 4 41 4 1 24 1 5}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) bintec(272) bibo(4) tty(41) mobileMIB(4) mobile(1) mobileSmsSendTable(24) mobileSmsSendEntry(1) mobileSmsSendMsgStatus(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) bintec(272) bibo(4) tty(41) mobileMIB(4) mobile(1) mobileSmsSendTable(24) mobileSmsSendEntry(1) mobileSmsSendMsgStatus(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) bintec(272) bibo(4) tty(41) mobileMIB(4) mobile(1) mobileSmsSendTable(24) mobileSmsSendEntry(1) mobileSmsSendMsgStatus(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) bintec(272) bibo(4) tty(41) mobileMIB(4) mobile(1) mobileSmsSendTable(24) mobileSmsSendEntry(1) mobileSmsSendMsgStatus(5)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) bintec(272) bibo(4) tty(41) mobileMIB(4) mobile(1) mobileSmsSendTable(24) mobileSmsSendEntry(1) mobileSmsSendMsgStatus(5)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) bintec(272) bibo(4) tty(41) mobileMIB(4) mobile(1) mobileSmsSendTable(24) mobileSmsSendEntry(1) mobileSmsSendMsgStatus(5)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) bintec(272) bibo(4) tty(41) mobileMIB(4) mobile(1) mobileSmsSendTable(24) mobileSmsSendEntry(1) mobileSmsSendMsgStatus(5)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) bintec(272) bibo(4) tty(41) mobileMIB(4) mobile(1) mobileSmsSendTable(24) mobileSmsSendEntry(1) mobileSmsSendMsgStatus(5)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) bintec(272) bibo(4) tty(41) mobileMIB(4) mobile(1) mobileSmsSendTable(24) mobileSmsSendEntry(1) mobileSmsSendMsgStatus(5)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) bintec(272) bibo(4) tty(41) mobileMIB(4) mobile(1) mobileSmsSendTable(24) mobileSmsSendEntry(1) mobileSmsSendMsgStatus(5)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) bintec(272) bibo(4) tty(41) mobileMIB(4) mobile(1) mobileSmsSendTable(24) mobileSmsSendEntry(1) mobileSmsSendMsgStatus(5)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) bintec(272) bibo(4) tty(41) mobileMIB(4) mobile(1) mobileSmsSendTable(24) mobileSmsSendEntry(1) mobileSmsSendMsgStatus(5)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) bintec(272) bibo(4) tty(41) mobileMIB(4) mobile(1) mobileSmsSendTable(24) mobileSmsSendEntry(1) mobileSmsSendMsgStatus(5)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) bintec(272) bibo(4) tty(41) mobileMIB(4) mobile(1) mobileSmsSendTable(24) mobileSmsSendEntry(1) mobileSmsSendMsgStatus(5)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) bintec(272) bibo(4) tty(41) mobileMIB(4) mobile(1) mobileSmsSendTable(24) mobileSmsSendEntry(1) mobileSmsSendMsgStatus(5)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) bintec(272) bibo(4) tty(41) mobileMIB(4) mobile(1) mobileSmsSendTable(24) mobileSmsSendEntry(1) mobileSmsSendMsgStatus(5)}
OID-IRI notation
  • /1/3/6/1/4/1/272/4/41/4/1/24/1/5
  • /ISO/Identified-Organization/6/1/4/1/272/4/41/4/1/24/1/5
  • /ISO/3/6/1/4/1/272/4/41/4/1/24/1/5
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/bintec/bibo/tty/mobileMIB/mobile/mobileSmsSendTable/mobileSmsSendEntry/mobileSmsSendMsgStatus
  • /iso/identified-organization/dod/internet/private/enterprises/bintec/bibo/tty/mobileMIB/mobile/mobileSmsSendTable/mobileSmsSendEntry/mobileSmsSendMsgStatus
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/bintec/bibo/tty/mobileMIB/mobile/mobileSmsSendTable/mobileSmsSendEntry/mobileSmsSendMsgStatus
  • /iso/identified-organization/dod/internet/private/vendor-objects/bintec/bibo/tty/mobileMIB/mobile/mobileSmsSendTable/mobileSmsSendEntry/mobileSmsSendMsgStatus
  • /iso/org/dod/internet/private/enterprise/bintec/bibo/tty/mobileMIB/mobile/mobileSmsSendTable/mobileSmsSendEntry/mobileSmsSendMsgStatus
  • /iso/org/dod/internet/private/enterprises/bintec/bibo/tty/mobileMIB/mobile/mobileSmsSendTable/mobileSmsSendEntry/mobileSmsSendMsgStatus
  • /iso/org/dod/internet/private/ldap-enterprise/bintec/bibo/tty/mobileMIB/mobile/mobileSmsSendTable/mobileSmsSendEntry/mobileSmsSendMsgStatus
  • /iso/org/dod/internet/private/vendor-objects/bintec/bibo/tty/mobileMIB/mobile/mobileSmsSendTable/mobileSmsSendEntry/mobileSmsSendMsgStatus
  • /iso/iso-identified-organization/dod/internet/private/enterprise/bintec/bibo/tty/mobileMIB/mobile/mobileSmsSendTable/mobileSmsSendEntry/mobileSmsSendMsgStatus
  • /iso/iso-identified-organization/dod/internet/private/enterprises/bintec/bibo/tty/mobileMIB/mobile/mobileSmsSendTable/mobileSmsSendEntry/mobileSmsSendMsgStatus
  • /iso/iso-identified-organization/dod/internet/private/ldap-enterprise/bintec/bibo/tty/mobileMIB/mobile/mobileSmsSendTable/mobileSmsSendEntry/mobileSmsSendMsgStatus
  • /iso/iso-identified-organization/dod/internet/private/vendor-objects/bintec/bibo/tty/mobileMIB/mobile/mobileSmsSendTable/mobileSmsSendEntry/mobileSmsSendMsgStatus
  • /iso/iso-organization/dod/internet/private/enterprise/bintec/bibo/tty/mobileMIB/mobile/mobileSmsSendTable/mobileSmsSendEntry/mobileSmsSendMsgStatus
  • /iso/iso-organization/dod/internet/private/enterprises/bintec/bibo/tty/mobileMIB/mobile/mobileSmsSendTable/mobileSmsSendEntry/mobileSmsSendMsgStatus
  • /iso/iso-organization/dod/internet/private/ldap-enterprise/bintec/bibo/tty/mobileMIB/mobile/mobileSmsSendTable/mobileSmsSendEntry/mobileSmsSendMsgStatus
  • /iso/iso-organization/dod/internet/private/vendor-objects/bintec/bibo/tty/mobileMIB/mobile/mobileSmsSendTable/mobileSmsSendEntry/mobileSmsSendMsgStatus

SNMP properties

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

Enumerated values

Notes below names come from selected MIB definitions.

ValueName and source notes
1transmit
start transmission
2success
transmission successful
3error
transmission failed
5delete

Using this OID with SNMP

At least one MIB declaration places this object in a table row. A value belongs to a row instance; its suffix depends on the row's INDEX or AUGMENTS definition.

In BINTEC-MOBILE-MIB, the row index mobileSmsSendId is declared as INTEGER. A non-negative index value is encoded as one numeric subidentifier. An instance has the form .1.3.6.1.4.1.272.4.41.4.1.24.1.5.<mobileSmsSendId>. Use an index value actually present on the device and permitted by its MIB. Other definitions can differ.

snmpwalk [connection options] DEVICE .1.3.6.1.4.1.272.4.41.4.1.24.1.5

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.

mobileSmsSendMsgStatus OBJECT-TYPE
        SYNTAX      INTEGER {
            transmit(1),   -- start transmission
            success(2),    -- transmission successful
            error(3),      -- transmission failed
            delete(5)
        }
        MAX-ACCESS  read-write
        STATUS      current
        DESCRIPTION
            "The Status of the SMS.
             To start transmission of the SMS set Status to `transmit(1)'.

             On successful transmission the Status is set to `success(2)'.
             Afterwards the SMS is moved to the 'mobileSmsTable'.

             When transmission fails the Status changes to     `error(3)'.
             The SMS stays in 'mobileSmsSendTable' for retransmissions.

             If the SMS should be deleted from the 'mobileSmsSendTable'
             and the mobile device storage specified in
             'mobileSmsSendMsgStorage' the Status should be set to `delete(5)'.
            "
        DEFVAL { transmit }
    ::= { mobileSmsSendEntry 5 }

Meaning

Descriptions

1 unique

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

The Status of the SMS. To start transmission of the SMS set Status to `transmit(1)'. On successful transmission the Status is set to `success(2)'. Afterwards the SMS is moved to the 'mobileSmsTable'. When transmission fails the Status changes to `error(3)'. The SMS stays in 'mobileSmsSendTable' for retransmissions. If the SMS should be deleted from the 'mobileSmsSendTable' and the mobile device storage specified in 'mobileSmsSendMsgStorage' the Status should be set to `delete(5)'.

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

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

Status in source: current.

Names: mobileSmsSendMsgStatus

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "mobileSmsSendMsgStatus",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "transmit",
    "(",
    "1",
    ")",
    ",",
    "success",
    "(",
    "2",
    ")",
    ",",
    "error",
    "(",
    "3",
    ")",
    ",",
    "delete",
    "(",
    "5",
    ")",
    "}",
    "MAX-ACCESS",
    "read-write",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"The Status of the SMS. To start transmission of the SMS set Status to `transmit(1)'. On successful transmission the Status is set to `success(2)'. Afterwards the SMS is moved to the 'mobileSmsTable'. When transmission fails the Status changes to `error(3)'. The SMS stays in 'mobileSmsSendTable' for retransmissions. If the SMS should be deleted from the 'mobileSmsSendTable' and the mobile device storage specified in 'mobileSmsSendMsgStorage' the Status should be set to `delete(5)'. \"",
    "DEFVAL",
    "{",
    "transmit",
    "}",
    "::=",
    "{",
    "mobileSmsSendEntry",
    "5",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "transmit",
            1
          ],
          [
            "success",
            2
          ],
          [
            "error",
            3
          ],
          [
            "delete",
            5
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "The Status of the SMS. To start transmission of the SMS set Status to `transmit(1)'. On successful transmission the Status is set to `success(2)'. Afterwards the SMS is moved to the 'mobileSmsTable'. When transmission fails the Status changes to `error(3)'. The SMS stays in 'mobileSmsSendTable' for retransmissions. If the SMS should be deleted from the 'mobileSmsSendTable' and the mobile device storage specified in 'mobileSmsSendMsgStorage' the Status should be set to `delete(5)'."
    ],
    null,
    null,
    null,
    [
      "DEFVAL",
      "transmit"
    ]
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.272)

Hertlein Elisabeth

Siblings (8)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.272.4.41.4.1.24.1.1 mobileSmsSendId00
1.3.6.1.4.1.272.4.41.4.1.24.1.2 mobileSmsSendIfIndex00
1.3.6.1.4.1.272.4.41.4.1.24.1.3 mobileSmsSendMsgStorage00
1.3.6.1.4.1.272.4.41.4.1.24.1.4 mobileSmsSendMsgSlot00
1.3.6.1.4.1.272.4.41.4.1.24.1.6 mobileSmsSendDestAddr00
1.3.6.1.4.1.272.4.41.4.1.24.1.7 mobileSmsSendMsgFormat00
1.3.6.1.4.1.272.4.41.4.1.24.1.8 mobileSmsSendMsgCoding00
1.3.6.1.4.1.272.4.41.4.1.24.1.9 mobileSmsSendMsgData00