Indicates type of the active call violation
Sources for this description
Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)
OID reference
1.3.6.1.4.1.6486.801.1.2.1.76.1.1.8.1
Indicates type of the active call violation
Identification
{1 3 6 1 4 1 6486 801 1 2 1 76 1 1 8 1}
Notes below names come from selected MIB definitions.
| Value | Name and source notes |
|---|---|
| 1 | jitterViolation jitter violation |
| 2 | rtdViolation rtd violation |
| 3 | mosViolation mos violation |
| 4 | rFactorViolation Rfactor violation |
| 5 | pktLossViolation Packet loss violation |
At least one MIB declaration places this object in a scalar group. A scalar instance uses the suffix .0.
A query example is omitted because the source variants do not establish compatible read access.
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.
alaSIPSnoopingCallViolationType OBJECT-TYPE
SYNTAX INTEGER {
jitterViolation (1), --jitter violation
rtdViolation (2), --rtd violation
mosViolation (3), --mos violation
rFactorViolation (4), -- Rfactor violation
pktLossViolation (5) -- Packet loss violation
}
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION "Indicates type of the active call violation"
::= { aluSIPSnoopingNotificationObjects 1 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
Indicates type of the active call violation
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: current.
Names: alaSIPSnoopingCallViolationType
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"alaSIPSnoopingCallViolationType",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"{",
"jitterViolation",
"(",
"1",
")",
",",
"rtdViolation",
"(",
"2",
")",
",",
"mosViolation",
"(",
"3",
")",
",",
"rFactorViolation",
"(",
"4",
")",
",",
"pktLossViolation",
"(",
"5",
")",
"}",
"MAX-ACCESS",
"accessible-for-notify",
"STATUS",
"current",
"DESCRIPTION",
"\"Indicates type of the active call violation\"",
"::=",
"{",
"aluSIPSnoopingNotificationObjects",
"1",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"enumSpec",
[
[
"jitterViolation",
1
],
[
"rtdViolation",
2
],
[
"mosViolation",
3
],
[
"rFactorViolation",
4
],
[
"pktLossViolation",
5
]
]
]
],
null,
[
"MaxAccessPart",
"accessible-for-notify"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"Indicates type of the active call violation"
],
null,
null,
null,
null
]
}Vendor MIB copy from the Observium Community archive.
Module: ALCATEL-ENT1-SIP-SNOOPING-MIB
See published definition above
{'IF-MIB': ['InterfaceIndex'], 'SNMPv2-TC': ['RowStatus', 'DateAndTime'], 'SNMPv2-SMI': ['NOTIFICATION-TYPE', 'OBJECT-TYPE', 'OBJECT-IDENTITY', 'MODULE-IDENTITY', 'Counter64', 'Integer32', 'Counter32'], 'SNMPv2-CONF': ['OBJECT-GROUP', 'MODULE-COMPLIANCE', 'NOTIFICATION-GROUP'], 'INET-ADDRESS-MIB': ['InetAddress', 'InetAddressType'], 'ALCATEL-ENT1-BASE': ['softentIND1SIPSnooping'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString'], 'ALCATEL-ENT1-CHASSIS-MIB': ['physicalIndex']}Related source files and packages:
Registration