The call ID. invalid(0), call ID(1~16776415,16777215). The callId should be exclusive in the group of same call type.
Sources for this description
Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)
OID reference
1.3.6.1.4.1.40297.1.2.5.5.12.1.4
The call ID. invalid(0), call ID(1~16776415,16777215). The callId should be exclusive in the group of same call type.
Identification
{1 3 6 1 4 1 40297 1 2 5 5 12 1 4}
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 HYTERA-REPEATER-MIB, the row index contactIndex 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.40297.1.2.5.5.12.1.4.<contactIndex>. 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.40297.1.2.5.5.12.1.4
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.
callId OBJECT-TYPE
SYNTAX INTEGER (0..16776415|16777215)
MAX-ACCESS read-write
STATUS mandatory
DESCRIPTION
"The call ID.
invalid(0), call ID(1~16776415,16777215).
The callId should be exclusive in the group of same call type."
-- 1.3.6.1.4.1.40297.1.2.5.5.12.1.4
::= { contactEntry 4 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
The call ID. invalid(0), call ID(1~16776415,16777215). The callId should be exclusive in the group of same call type.
Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)
Evidence
Matching descriptions are grouped; open a group to compare definitions and supporting files.
Status in source: mandatory.
Names: callId
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"callId",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"(",
"0",
".",
".",
"16776415",
"|",
"16777215",
")",
"MAX-ACCESS",
"read-write",
"STATUS",
"mandatory",
"DESCRIPTION",
"\"The call ID. invalid(0), call ID(1~16776415,16777215). The callId should be exclusive in the group of same call type.\"",
"::=",
"{",
"contactEntry",
"4",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"integerSubType",
[
[
0,
16776415
],
[
16777215
]
]
]
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"mandatory"
],
[
"DESCRIPTION",
"The call ID. invalid(0), call ID(1~16776415,16777215). The callId should be exclusive in the group of same call type."
],
null,
null,
null,
null
]
}Vendor MIB copy from the LibreNMS archive.
Module: HYTERA-REPEATER-MIB
See published definition above
{'RFC-1212': ['OBJECT-TYPE'], 'RFC1155-SMI': ['private', 'enterprises', 'IpAddress', 'Counter', 'Gauge', 'TimeTicks']}Related source files and packages:
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.40297.1.2.5.5.12.1.1 | contactIndex | 0 | 0 | |
| 1.3.6.1.4.1.40297.1.2.5.5.12.1.2 | callAlias | 0 | 0 | |
| 1.3.6.1.4.1.40297.1.2.5.5.12.1.3 | contactCallType | 0 | 0 |