OID reference

mediaTerminalType

1.3.6.1.4.1.272.4.50.2.1.8

Description

Full description and source information

Identification

Identifier and names

Parent: 1.3.6.1.4.1.272.4.50.2.1 (mediaTerminalEntry)
Node code: 8
Node name: mediaTerminalType
Category: SNMP management object
Numeric OID: 1.3.6.1.4.1.272.4.50.2.1.8
URN notation: urn:oid:1.3.6.1.4.1.272.4.50.2.1.8

ASN.1, OID-IRI and named path variants

ASN.1 notation

{1 3 6 1 4 1 272 4 50 2 1 8}

{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) bintec(272) bibo(4) media(50) mediaTerminalTable(2) mediaTerminalEntry(1) mediaTerminalType(8)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) bintec(272) bibo(4) media(50) mediaTerminalTable(2) mediaTerminalEntry(1) mediaTerminalType(8)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) bintec(272) bibo(4) media(50) mediaTerminalTable(2) mediaTerminalEntry(1) mediaTerminalType(8)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) bintec(272) bibo(4) media(50) mediaTerminalTable(2) mediaTerminalEntry(1) mediaTerminalType(8)}
{iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) bintec(272) bibo(4) media(50) mediaTerminalTable(2) mediaTerminalEntry(1) mediaTerminalType(8)}
{iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) bintec(272) bibo(4) media(50) mediaTerminalTable(2) mediaTerminalEntry(1) mediaTerminalType(8)}
{iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) bintec(272) bibo(4) media(50) mediaTerminalTable(2) mediaTerminalEntry(1) mediaTerminalType(8)}
{iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) bintec(272) bibo(4) media(50) mediaTerminalTable(2) mediaTerminalEntry(1) mediaTerminalType(8)}
{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) bintec(272) bibo(4) media(50) mediaTerminalTable(2) mediaTerminalEntry(1) mediaTerminalType(8)}
{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) bintec(272) bibo(4) media(50) mediaTerminalTable(2) mediaTerminalEntry(1) mediaTerminalType(8)}
{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) bintec(272) bibo(4) media(50) mediaTerminalTable(2) mediaTerminalEntry(1) mediaTerminalType(8)}
{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) bintec(272) bibo(4) media(50) mediaTerminalTable(2) mediaTerminalEntry(1) mediaTerminalType(8)}
{iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) bintec(272) bibo(4) media(50) mediaTerminalTable(2) mediaTerminalEntry(1) mediaTerminalType(8)}
{iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) bintec(272) bibo(4) media(50) mediaTerminalTable(2) mediaTerminalEntry(1) mediaTerminalType(8)}
{iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) bintec(272) bibo(4) media(50) mediaTerminalTable(2) mediaTerminalEntry(1) mediaTerminalType(8)}
{iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) bintec(272) bibo(4) media(50) mediaTerminalTable(2) mediaTerminalEntry(1) mediaTerminalType(8)}

OID-IRI notation

/1/3/6/1/4/1/272/4/50/2/1/8
/ISO/Identified-Organization/6/1/4/1/272/4/50/2/1/8
/ISO/3/6/1/4/1/272/4/50/2/1/8

Named path variants

/iso/identified-organization/dod/internet/private/enterprise/bintec/bibo/media/mediaTerminalTable/mediaTerminalEntry/mediaTerminalType
/iso/identified-organization/dod/internet/private/enterprises/bintec/bibo/media/mediaTerminalTable/mediaTerminalEntry/mediaTerminalType
/iso/identified-organization/dod/internet/private/ldap-enterprise/bintec/bibo/media/mediaTerminalTable/mediaTerminalEntry/mediaTerminalType
/iso/identified-organization/dod/internet/private/vendor-objects/bintec/bibo/media/mediaTerminalTable/mediaTerminalEntry/mediaTerminalType
/iso/org/dod/internet/private/enterprise/bintec/bibo/media/mediaTerminalTable/mediaTerminalEntry/mediaTerminalType
/iso/org/dod/internet/private/enterprises/bintec/bibo/media/mediaTerminalTable/mediaTerminalEntry/mediaTerminalType
/iso/org/dod/internet/private/ldap-enterprise/bintec/bibo/media/mediaTerminalTable/mediaTerminalEntry/mediaTerminalType
/iso/org/dod/internet/private/vendor-objects/bintec/bibo/media/mediaTerminalTable/mediaTerminalEntry/mediaTerminalType
/iso/iso-identified-organization/dod/internet/private/enterprise/bintec/bibo/media/mediaTerminalTable/mediaTerminalEntry/mediaTerminalType
/iso/iso-identified-organization/dod/internet/private/enterprises/bintec/bibo/media/mediaTerminalTable/mediaTerminalEntry/mediaTerminalType
/iso/iso-identified-organization/dod/internet/private/ldap-enterprise/bintec/bibo/media/mediaTerminalTable/mediaTerminalEntry/mediaTerminalType
/iso/iso-identified-organization/dod/internet/private/vendor-objects/bintec/bibo/media/mediaTerminalTable/mediaTerminalEntry/mediaTerminalType
/iso/iso-organization/dod/internet/private/enterprise/bintec/bibo/media/mediaTerminalTable/mediaTerminalEntry/mediaTerminalType
/iso/iso-organization/dod/internet/private/enterprises/bintec/bibo/media/mediaTerminalTable/mediaTerminalEntry/mediaTerminalType
/iso/iso-organization/dod/internet/private/ldap-enterprise/bintec/bibo/media/mediaTerminalTable/mediaTerminalEntry/mediaTerminalType
/iso/iso-organization/dod/internet/private/vendor-objects/bintec/bibo/media/mediaTerminalTable/mediaTerminalEntry/mediaTerminalType

SNMP properties

Value type: INTEGER
Maximum access defined by MIB: read-write
Status in MIB: mandatory
Default value: client

Enumerated values

Value	Name
1	client
2	server
8	delete

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 BIANCA-BRICK-PROXY-MIB, the row index consists of these components in order:

mediaTerminalIntAddr (IpAddress): four numeric subidentifiers, one per IPv4 address octet.
mediaTerminalIntPort (INTEGER): one numeric subidentifier for the non-negative value.

An instance has the form .1.3.6.1.4.1.272.4.50.2.1.8.<mediaTerminalIntAddr: four octets>.<mediaTerminalIntPort>. Use values 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.50.2.1.8

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.

Published definition

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

mediaTerminalType  OBJECT-TYPE
	    SYNTAX  INTEGER {
		client(1),
		server(2),
		delete(8)
	    }
	    ACCESS  read-write
	    STATUS  mandatory
	    DESCRIPTION
		"The type of the terminal entry:

		  'client' -> autodetected (and thus listed here automatically)
			      or manually added IP phone or softclient;
		  'server' -> manually added internal rerouted SIP server;
		  'delete' -> delete flag.

		 Manually added clients are usually obsolete as they are
		 autodetected by the Application Level Gateway anyways (see
		 ipProxyTable for definition of dynamic NAT rules). 'Type' =
		 'server' is used in order to enable access from WAN to a SIP
		 registrar or SIP proxy located in LAN."
	    DEFVAL { client }
	::= { mediaTerminalEntry 8 }

Meaning

Descriptions

1 unique

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

The type of the terminal entry: 'client' -> autodetected (and thus listed here automatically) or manually added IP phone or softclient; 'server' -> manually added internal rerouted SIP server; 'delete' -> delete flag. Manually added clients are usually obsolete as they are autodetected by the Application Level Gateway anyways (see ipProxyTable for definition of dynamic NAT rules). 'Type' = 'server' is used in order to enable access from WAN to a SIP registrar or SIP proxy located in LAN.

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

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

Status in source: mandatory.

Names: mediaTerminalType

Technical details

{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "mediaTerminalType",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "client",
    "(",
    "1",
    ")",
    ",",
    "server",
    "(",
    "2",
    ")",
    ",",
    "delete",
    "(",
    "8",
    ")",
    "}",
    "ACCESS",
    "read-write",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\"The type of the terminal entry: 'client' -> autodetected (and thus listed here automatically) or manually added IP phone or softclient; 'server' -> manually added internal rerouted SIP server; 'delete' -> delete flag. Manually added clients are usually obsolete as they are autodetected by the Application Level Gateway anyways (see ipProxyTable for definition of dynamic NAT rules). 'Type' = 'server' is used in order to enable access from WAN to a SIP registrar or SIP proxy located in LAN.\"",
    "DEFVAL",
    "{",
    "client",
    "}",
    "::=",
    "{",
    "mediaTerminalEntry",
    "8",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "client",
            1
          ],
          [
            "server",
            2
          ],
          [
            "delete",
            8
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "The type of the terminal entry: 'client' -> autodetected (and thus listed here automatically) or manually added IP phone or softclient; 'server' -> manually added internal rerouted SIP server; 'delete' -> delete flag. Manually added clients are usually obsolete as they are autodetected by the Application Level Gateway anyways (see ipProxyTable for definition of dynamic NAT rules). 'Type' = 'server' is used in order to enable access from WAN to a SIP registrar or SIP proxy located in LAN."
    ],
    null,
    null,
    null,
    [
      "DEFVAL",
      "client"
    ]
  ]
}

Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community) · Publisher's source file: Source package: observium-community-latest.tar.gz
Vendor MIB copy from the Observium Community archive.

Module: BIANCA-BRICK-PROXY-MIB

See published definition above
Module imports
```
{'RFC-1212': ['OBJECT-TYPE'], 'RFC1155-SMI': ['IpAddress', 'Counter', 'enterprises', 'TimeTicks'], 'RFC1158-MIB': ['DisplayString']}
```
· Download BIANCA-BRICK-PROXY-MIB
Related source files and packages:
- Observium Community original distribution archive

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.272)

Hertlein Elisabeth

Siblings (8)

OID	Name	Direct children	Descendants	Description
1.3.6.1.4.1.272.4.50.2.1.1	mediaTerminalIntAddr	0	0
1.3.6.1.4.1.272.4.50.2.1.2	mediaTerminalIntPort	0	0
1.3.6.1.4.1.272.4.50.2.1.3	mediaTerminalExtPort	0	0
1.3.6.1.4.1.272.4.50.2.1.4	mediaTerminalRemotePort	0	0
1.3.6.1.4.1.272.4.50.2.1.5	mediaTerminalLifetime	0	0
1.3.6.1.4.1.272.4.50.2.1.6	mediaTerminalAge	0	0
1.3.6.1.4.1.272.4.50.2.1.7	mediaTerminalProto	0	0
1.3.6.1.4.1.272.4.50.2.1.10	mediaTerminalSessions	0	0