idnits 2.17.1 draft-ietf-avt-rtcp-xr-mib-05.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 16. -- Found old boilerplate from RFC 3978, Section 5.5 on line 2038. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 1945. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 1952. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 1958. ** This document has an original RFC 3978 Section 5.4 Copyright Line, instead of the newer IETF Trust Copyright according to RFC 4748. ** This document has an original RFC 3978 Section 5.5 Disclaimer, instead of the newer disclaimer which includes the IETF Trust according to RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == The document seems to use 'NOT RECOMMENDED' as an RFC 2119 keyword, but does not include the phrase in its RFC 2119 key words list. -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (June 2006) is 6517 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Unexpected draft version: The latest known version of draft-ietf-rmonmib-framework is -05, but you're referring to -16. Summary: 3 errors (**), 0 flaws (~~), 3 warnings (==), 8 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Audio/Video Working Group Alan Clark 2 Internet-Draft Telchemy 3 Expires: December 22, 2006 Amy Pendleton 4 Nortel 5 June 2006 7 RTP Control Protocol Extended Reports (RTCP XR) 8 VoIP Metrics Management Information Base 9 draft-ietf-avt-rtcp-xr-mib-05.txt 11 Status of this Memo 13 By submitting this Internet-Draft, each author represents that any 14 applicable patent or other IPR claims of which he or she is aware 15 have been or will be disclosed, and any of which he or she becomes 16 aware will be disclosed, in accordance with Section 6 of BCP 79. 18 Internet-Drafts are working documents of the Internet Engineering 19 Task Force (IETF), its areas, and its working groups. Note that 20 other groups may also distribute working documents as 21 Internet-Drafts. 23 Internet-Drafts are draft documents valid for a maximum of six months 24 and may be updated, replaced, or obsoleted by other documents at any 25 time. It is inappropriate to use Internet-Drafts as reference 26 material or to cite them other than as "work in progress." 28 The list of current Internet-Drafts can be accessed at 29 http://www.ietf.org/ietf/1id-abstracts.txt. 31 The list of Internet-Draft Shadow Directories can be accessed at 32 http://www.ietf.org/shadow.html. 34 This Internet-Draft will expire on December 22, 2006. 36 This document is a product of the Audio-Visual Transport (AVT) 37 working group of the Internet Engineering Task Force. Comments are 38 solicited and should be addressed to the working group's mailing 39 list at avt@ietf.org and/or the authors. 41 Abstract 43 This memo defines a portion of the Management Information Base (MIB) 44 for use with network management protocols in the Internet community. 45 In particular, it defines objects for managing Real-Time Transport 46 Control Protocol Extended Reports (RTCP XR) VoIP Metrics (RFC3611). 48 Table of Contents 50 1. The Network Management Framework ............................. 2 51 2. Overview ..................................................... 3 52 2.1 Components .................................................. 3 53 2.2 Applicability of the MIB to RTP System Implementations ...... 3 54 2.3 Relationship to the RTP MIB....................................3 55 2.4 Relationship to the RAQMON Architecture...................... 3 56 2.5 The Structure of the RTCP XR MIB ............................ 4 57 2.6 Application to multi-party and multicast calls .............. 4 58 3 Definitions ................................................... 5 59 4. Security Considerations ...................................... 38 60 5. IANA Considerations .......................................... 38 61 5. Acknowledgements ............................................. 38 62 6. Intellectual Property ........................................ 39 63 7. Normative References ......................................... 39 64 9. Informative References ....................................... 39 65 8. Authors' Addresses ........................................... 40 66 9. Full Copyright Statement ..................................... 40 68 1. The Internet-Standard Management Framework 70 For a detailed overview of the documents that describe the current 71 Internet-Standard Management Framework, please refer to section 7 of 72 RFC 3410 [RFC3410]. 74 Managed objects are accessed via a virtual information store, termed 75 the Management Information Base or MIB. MIB objects are generally 76 accessed through the Simple Network Management Protocol (SNMP). 77 Objects in the MIB are defined using the mechanisms defined in the 78 Structure of Management Information (SMI). This memo specifies a MIB 79 module that is compliant to the SMIv2, which is described in STD 58, 80 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 81 [RFC2580]. 83 2. Overview 84 An "RTP System" may be a host end-system that runs an application 85 program that sends or receives RTP data packets, or it may be an 86 intermediate-system that forwards RTP packets. RTP Control Protocol 87 (RTCP) packets are sent by senders and receivers to convey 88 information about RTP packet transmission and reception [RFC3550]. 89 RTCP Extended Report (XR) [RFC3611] packets are sent by receivers 90 to convey additional information about certain types of RTP packet 91 reception. 93 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 94 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 95 document are to be interpreted as described in RFC 2119. 97 2.1 Components 98 The RTCP XR MIB is structured around "Session", "Source", 99 "Destination" and "Receiver" conceptual abstractions. 101 2.1.1 An RTP Session is an association of two or more participants 102 communicating with RTP. For each participant, the session is defined 103 by a particular pair of destination transport addresses (one network 104 address plus a port pair for RTP and RTCP). The destination 105 transport addresses may be common for all participants, as in the 106 case of IP multicast, or may be different for each, as in the case of 107 individual unicast addresses plus a common port pair," as defined in 108 section 3 of [RFC3550]. 110 2.1.2 A "Sender" is identified within an RTP session by a 32-bit 111 numeric "Synchronization Source," or "SSRC", value and is "...the 112 source of a stream of RTP packets" as defined in section 3 of 113 [RFC3550]. The sender is also a source of RTCP Sender Report packets 114 as specified in section 6 of [RFC3550]. 116 2.1.3 A "Receiver" of a "stream of RTP packets" can be a unicast or 117 multicast Receiver as described in 2.1.1, above. An RTP Receiver has 118 an SSRC value that is unique to the session. An RTP Receiver is a 119 source of RTCP Receiver Reports as specified in section 6 of 120 [RFC3550] and RTCP XR VoIP Metrics Reports as specified in section 121 4.7 of [RFC3611]. 123 2.2 Applicability of the MIB to RTP System Implementations 124 The RTCP XR MIB may be used in RTP Host Systems (end systems), see 125 section 3 of [RFC3550], that are supporting Voice over IP (VoIP host 126 systems) or in intermediate systems. 128 2.2.1 VoIP host Systems are end-systems that may use the RTCP XR MIB 129 to collect RTP Voice over IP session data that the host is sending or 130 receiving; these data may be used by a network manager to detect and 131 diagnose faults that occur over the lifetime of a VoIP session as in 132 a "help-desk" scenario. 134 2.2.2 Monitors of RTP Voice over IP sessions may be third-party or 135 may be located in the RTP host. Monitors may use the RTCP XR MIB to 136 collect Voice over IP session statistical data; these data may be 137 used by a network manager for planning and other network-management 138 purposes. A Monitor may use the RTCP XR MIB to collect data to 139 permit a network manager to diagnose faults in VoIP sessions. 141 2.3 Relationship to the RTP MIB V2 142 The RTP MIB V2 [draft-ietf-avt-mib-rtp-bis-00.txt] defines a table 143 of session identifying information. The tables in the RTCP XR MIB 144 augment the session data from the RTP MIB V2, providing detailed 145 performance information for RTP sessions transporting Voice over 146 IP. The RTP MIB V2 session table MUST be implemented if the RTCP 147 XR MIB Basic Parameter and Call Quality tables are implemented. 148 The history table in this MIB contains aggregate information and 149 does not have any relationship to the RTP MIB V2 session table. 150 In implementations that use only the RTCP XR history table to 151 report aggregate data, the RTP MIB V2 session table MUST NOT be 152 implemented. 154 2.4 Relationship to the RAQMON Architecture 156 The Real-time Application QoS monitoring (RAQMON) Framework [RAQMON] 157 defines an architecture that extends the Remote Monitoring (RMON) 158 family of applications for monitoring of application QoS in real 159 time, and an extensible data model with objects carried between 160 RAQMON data sources and RAQMON collectors. The RAQMON work is 161 more generic, and complementary in concept to RTCP-XR, covering a 162 wider range of applications running concurrently, while RTCP-XR 163 focuses on in-depth QoS monitoring of media traffic in VoIP. 165 The Real-time Application QoS Monitoring (RAQMON) MIB is defined 166 by [xxx] and runs on RAQMON collectors. A performance monitoring 167 application may query (i) RAQMON collectors for RAQMON MIB 168 information about the QoS parameters of multiple concurrent 169 applications (ii) end-points and gateways for in-depth RTCP-XR 170 information about the media QoS of VoIP or (iii) both. 172 2.5 The Structure of the RTCP XR MIB 174 There are three tables in the RTCP XR MIB 176 The rtcpXrBasicParametersTable contains basic packet loss, discard 177 and delay related parameters about a session. 179 The rtcpXrVoiceQualityMetricsTable contains information about the 180 call quality of a session 182 The rtcpXrHistoryTable contains aggregate information about a group 183 of sessions. 185 2.6 Application to multi-party and multicast calls 187 The RTCP XR MIB may be applied to multi-party calls. The RTP MIB 188 Session table is defined in terms of uni-directional RTP streams 189 from a source to a destination. 191 For a multi-party IP-IP conference call in which parties are 192 directly interconnected in a mesh network, a row should be created 193 in the session table for each such interconnection. 195 For a multi-party call in which parties are interconnected via 196 a bridge function and RTP streams are literally or logically 197 terminated at the bridge, a row should be created in the session 198 table for the RTP sessions established to and from each endpoint 199 and the bridge. 201 For a multicast call in which RTP sessions are terminated in 202 logical IP addresses from they are redistributed, a row in the 203 session table should be created for the source to multicast 204 address RTP session. 206 RTCPXR-MIB DEFINITIONS ::= BEGIN 207 IMPORTS 208 mib-2, MODULE-IDENTITY, NOTIFICATION-TYPE, 209 OBJECT-TYPE, Unsigned32, Integer32, 210 Gauge32, Counter32 FROM SNMPv2-SMI 211 OBJECT-GROUP, MODULE-COMPLIANCE, 212 NOTIFICATION-GROUP FROM SNMPv2-CONF 213 TEXTUAL-CONVENTION, RowPointer, DateAndTime 214 FROM SNMPv2-TC 215 SnmpAdminString FROM SNMP-FRAMEWORK-MIB 216 ItuPerceivedSeverity FROM ITU-ALARM-TC-MIB 217 rtpSessionIndex, rtpSessionCallStatus 218 FROM RTP-MIBV2; 220 rtcpXrMIB MODULE-IDENTITY 221 LAST-UPDATED "200603040000Z" 222 ORGANIZATION 223 "IETF AVT Working Group" 224 CONTACT-INFO 225 "IETF AVT Working Group 226 Chairs: Colin Perkins, Magnus Westerlund 227 Working Group Email: avt@ietf.org 229 Editors: Alan Clark 230 Telchemy 231 Email: alan@telchemy.com 233 Amy Pendleton 234 Nortel 235 Email: aspen@nortel.com" 236 DESCRIPTION 237 "RTCP Extended Reports MIB 238 Copyright (c) The Internet Society (2005) 239 This version of the MIB module is part of 240 RFC nnnn and is based on RFC3611." 242 REVISION "200603040000Z" 243 DESCRIPTION 244 "Published as draft-ietf-avt-rtcp-xr-mib-05.txt" 246 -- RFC Ed: replace above draft with RFC number and remove this note 248 ::= { mib-2 nnn } 250 -- IANA: need assignment of a mib-2 OID for this MIB 251 -- RFC Ed: replace mmm with assigned OID number and remove this note 252 -- RTCP Extended Reports - Voice over IP Metrics 253 -- 254 -- Description 255 -- This MIB module provides basic voice quality monitoring 256 -- capabilities for Voice-over-packet systems. The MIB contains 257 -- 3 tables of information that augment the data available in 258 -- the RTP MIB V2. 259 -- a table of basic parameters for each Stream 260 -- a table of call quality metrics for each Stream 261 -- a table of aggregate statistics for groups of calls 262 -- the indexes to these tables are imported from the RTP MIB V2 263 -- and hence this MIB MUST be used in conjunction with at least 264 -- the RTP session table from that MIB 266 -- TEXTUAL CONVENTIONS 268 LeveldB ::= TEXTUAL-CONVENTION 269 DISPLAY-HINT "d" 270 STATUS current 271 DESCRIPTION 272 "Represents a signal level in decibels (dB)." 273 SYNTAX Integer32 (-120..120|127) 275 Rfactor ::= TEXTUAL-CONVENTION 276 DISPLAY-HINT "d" 277 STATUS current 278 DESCRIPTION 279 "Call or transmission quality expressed as an 280 R factor in the range 0 to 120. A value of 281 127 shall be interpreted as NULL or unsupported." 282 REFERENCE 283 "ITU-T G.107" 284 SYNTAX Unsigned32 (0..120|127) 286 ScaledMOSscore ::= TEXTUAL-CONVENTION 287 DISPLAY-HINT "d" 288 STATUS current 289 DESCRIPTION 290 "Call or transmission quality expressed as a 291 MOS score scaled by 10. MOS is typically represented 292 as a 1.0 to 5.0 score with a single decimal place and 293 hence in this representation as 10 to 50. A value of 294 127 shall be interpreted as NULL or unsupported." 295 REFERENCE 296 "ITU-T P.800" 297 SYNTAX Integer32 (10..50|127) 299 Percentage ::= TEXTUAL-CONVENTION 300 DISPLAY-HINT "d" 301 STATUS current 302 DESCRIPTION 303 "Percentage expressed as a rounded integer." 304 SYNTAX Unsigned32 (0..100) 305 -- 306 -- OBJECTS 308 rtcpXrEvents OBJECT IDENTIFIER ::= { rtcpXrMIB 0 } 309 rtcpXrMIBObjects OBJECT IDENTIFIER ::= { rtcpXrMIB 1 } 310 rtcpXrConformance OBJECT IDENTIFIER ::= { rtcpXrMIB 2 } 312 -- Table of basic RTP stream parameters 313 -- 315 rtcpXrBaseParamTable OBJECT-TYPE 316 SYNTAX SEQUENCE OF RtcpXrBaseParamEntry 317 MAX-ACCESS not-accessible 318 STATUS current 319 DESCRIPTION 320 "Table of basic parameters related to RTP sessions in 321 the Session table. " 322 ::= { rtcpXrMIBObjects 2 } 324 rtcpXrBaseParamEntry OBJECT-TYPE 325 SYNTAX RtcpXrBaseParamEntry 326 MAX-ACCESS not-accessible 327 STATUS current 328 DESCRIPTION 329 "An entry in the table of basic parameters. A row in this table 330 is created for each RTP session endpoint participating." 331 INDEX { rtpSessionCallStatus, rtpSessionIndex } 332 ::= { rtcpXrBaseParamTable 1 } 334 RtcpXrBaseParamEntry ::= SEQUENCE { 335 rtcpXrBaseParamCodecType OCTET STRING, 336 rtcpXrBaseParamCodecBitRate Unsigned32, 337 rtcpXrBaseParamFrameDuration Unsigned32, 338 rtcpXrBaseParamFramesPerPacket Unsigned32, 339 rtcpXrBaseParamSampleRate Unsigned32, 340 rtcpXrBaseParamDurationMs Counter32, 341 rtcpXrBaseParamNetworkLossRate Percentage, 342 rtcpXrBaseParamAvgDiscardRate Percentage, 343 rtcpXrBaseParamBurstLossDensity Percentage, 344 rtcpXrBaseParamBurstLenMs Gauge32, 345 rtcpXrBaseParamGapLossDensity Percentage, 346 rtcpXrBaseParamGapLenMs Gauge32, 347 rtcpXrBaseParamAvgOWDelay Gauge32, 348 rtcpXrBaseParamAvgEndSysDelay Gauge32, 349 rtcpXrBaseParamNoiseLeveldBm LeveldB, 350 rtcpXrBaseParamSignalLeveldBm LeveldB, 351 rtcpXrBaseParamLocalRERLdB LeveldB, 352 rtcpXrBaseParamRemoteRERLdB LeveldB, 353 rtcpXrBaseParamPlcType INTEGER, 354 rtcpXrBaseParamJBuffAdaptMode INTEGER, 355 rtcpXrBaseParamJBuffAdaptRate Unsigned32, 356 rtcpXrBaseParamJBuffAverageDelay Gauge32, 357 rtcpXrBaseParamJBuffMaximumDelay Gauge32, 358 rtcpXrBaseParamJBuffAbsMaxDelay Gauge32, 359 rtcpXrBaseParamJitterLevel Gauge32 360 } 362 rtcpXrBaseParamCodecType OBJECT-TYPE 363 SYNTAX OCTET STRING (SIZE(0..32)) 364 MAX-ACCESS read-only 365 STATUS current 366 DESCRIPTION 367 "Codec type used on this call. The format used shall be 368 ITU-T G.7xx, GSM FR, GSM EFR, GSM HR, AMR, AMR WB, iLBC 369 or similar. For example 'ITU G.729A'. It is recommended 370 that Codecs are described in consistently with SDP." 371 ::= { rtcpXrBaseParamEntry 1 } 373 rtcpXrBaseParamCodecBitRate OBJECT-TYPE 374 SYNTAX Unsigned32 375 MAX-ACCESS read-only 376 STATUS current 377 DESCRIPTION 378 "Codec rate in use at the time this data was captured 379 expressed in bits per second. For example G.711 would 380 have the rate 64000 and G.729 would have the rate 8000." 381 ::= { rtcpXrBaseParamEntry 2 } 383 rtcpXrBaseParamFrameDuration OBJECT-TYPE 384 SYNTAX Unsigned32 (0..16384) 385 UNITS "sample clock ticks" 386 MAX-ACCESS read-only 387 STATUS current 388 DESCRIPTION 389 "Companion information to Codec type. This represents the 390 duration of the time interval represented by a frame, which 391 is generally equivalent to the nominal spacing of frames. 392 This is expressed in sample clock ticks as defined under 393 rtxpXrSampleRate. 394 This parameter may be equated to the SDP ptime parameter 395 which is expressed in milliseconds (however which cannot 396 represent certain Codec types, e.g. those with 2.5mS 397 frames)." 398 ::= { rtcpXrBaseParamEntry 3 } 400 rtcpXrBaseParamFramesPerPacket OBJECT-TYPE 401 SYNTAX Unsigned32 (0..65535) 402 UNITS "frames per packet" 403 MAX-ACCESS read-only 404 STATUS current 405 DESCRIPTION 406 "Number of Codec frames contained in a single IP packet in 407 this RTP stream at the time of sampling. The duration of 408 speech per IP packet is the product of Frame Duration and 409 Frames Per Packet. This may vary during a call." 410 ::= {rtcpXrBaseParamEntry 4 } 412 rtcpXrBaseParamSampleRate OBJECT-TYPE 413 SYNTAX Unsigned32 (0..16777215) 414 UNITS "samples per second" 415 MAX-ACCESS read-only 416 STATUS current 417 DESCRIPTION 418 "Companion information to Codec type. This represents the 419 rate at which media was sampled (e.g. 8000 for narrowband 420 voice, 16000 for wideband voice)." 421 ::= { rtcpXrBaseParamEntry 5 } 423 rtcpXrBaseParamDurationMs OBJECT-TYPE 424 SYNTAX Counter32 425 UNITS "milliseconds" 426 MAX-ACCESS read-only 427 STATUS current 428 DESCRIPTION 429 "Current duration of call in milliseconds if still active, 430 duration of call in milliseconds if complete." 431 ::= { rtcpXrBaseParamEntry 6 } 433 rtcpXrBaseParamNetworkLossRate OBJECT-TYPE 434 SYNTAX Percentage 435 UNITS "percent" 436 MAX-ACCESS read-only 437 STATUS current 438 DESCRIPTION 439 "Average rate of network packet loss." 440 REFERENCE 441 "See RFC3611 Section 4.7." 442 ::= { rtcpXrBaseParamEntry 7 } 444 rtcpXrBaseParamAvgDiscardRate OBJECT-TYPE 445 SYNTAX Percentage 446 UNITS "percent" 447 MAX-ACCESS read-only 448 STATUS current 449 DESCRIPTION 450 "Average rate of discards due to jitter." 451 REFERENCE 452 "See RFC3611 Section 4.7." 453 ::= { rtcpXrBaseParamEntry 8 } 455 rtcpXrBaseParamBurstLossDensity OBJECT-TYPE 456 SYNTAX Percentage 457 UNITS "percent" 458 MAX-ACCESS read-only 459 STATUS current 460 DESCRIPTION 461 "Density of loss and discarded packets during burst periods." 462 REFERENCE 463 "See RFC3611 Section 4.7." 464 ::= { rtcpXrBaseParamEntry 9 } 466 rtcpXrBaseParamBurstLenMs OBJECT-TYPE 467 SYNTAX Gauge32 468 UNITS "milliseconds" 469 MAX-ACCESS read-only 470 STATUS current 471 DESCRIPTION 472 "Average length of bursts in milliseconds." 473 REFERENCE 474 "See RFC3611 Section 4.7." 475 ::= { rtcpXrBaseParamEntry 10 } 477 rtcpXrBaseParamGapLossDensity OBJECT-TYPE 478 SYNTAX Percentage 479 UNITS "percent" 480 MAX-ACCESS read-only 481 STATUS current 482 DESCRIPTION 483 "Density of loss and discarded packets during gap periods." 484 REFERENCE 485 "See RFC3611 Section 4.7." 486 ::= { rtcpXrBaseParamEntry 11 } 488 rtcpXrBaseParamGapLenMs OBJECT-TYPE 489 SYNTAX Gauge32 490 UNITS "milliseconds" 491 MAX-ACCESS read-only 492 STATUS current 493 DESCRIPTION 494 "Average length of gaps in milliseconds." 495 REFERENCE 496 "See RFC3611 Section 4.7." 497 ::= { rtcpXrBaseParamEntry 12 } 499 rtcpXrBaseParamAvgOWDelay OBJECT-TYPE 500 SYNTAX Gauge32 501 UNITS "milliseconds" 502 MAX-ACCESS read-only 503 STATUS current 504 DESCRIPTION 505 "Average (symmetric) one way RTCP delay on call. A value of 506 zero indicates that this value has not yet been determined." 507 REFERENCE 508 "See RFC3611 Section 4.7." 509 ::= { rtcpXrBaseParamEntry 13 } 511 rtcpXrBaseParamAvgEndSysDelay OBJECT-TYPE 512 SYNTAX Gauge32 513 UNITS "milliseconds" 514 MAX-ACCESS read-only 515 STATUS current 516 DESCRIPTION 517 "Average end system delay on call. A value of zero may 518 indicate that this value has not yet been determined." 520 REFERENCE 521 "See RFC3611 Section 4.7." 522 ::= { rtcpXrBaseParamEntry 14 } 524 rtcpXrBaseParamNoiseLeveldBm OBJECT-TYPE 525 SYNTAX LeveldB 526 UNITS "dBm0" 527 MAX-ACCESS read-only 528 STATUS current 529 DESCRIPTION 530 "Measured received silent period noise level in dBm. 531 A value of 127 indicates that this parameter is not 532 available. 533 In midpoint applications this parameter may not be 534 available. If this is a midstream device and call 535 quality metrics were calculated using the value of 536 this parameter reported from the endpoint in an 537 RTCP XR payload then the value used in this 538 calculation MAY be reported." 539 REFERENCE 540 "See RFC3611 Section 4.7." 541 ::= { rtcpXrBaseParamEntry 15 } 543 rtcpXrBaseParamSignalLeveldBm OBJECT-TYPE 544 SYNTAX LeveldB 545 UNITS "dBm0" 546 MAX-ACCESS read-only 547 STATUS current 548 DESCRIPTION 549 "Measured received signal level during talkspurts in dBm. 550 A value of 127 indicates that this parameter is not 551 available. 552 In midpoint applications this parameter may not be 553 available. If this is a midstream device and call 554 quality metrics were calculated using the value of 555 this parameter reported from the endpoint in an 556 RTCP XR payload then the value used in this 557 calculation MAY be reported." 558 REFERENCE 559 "See RFC3611 Section 4.7." 560 ::= { rtcpXrBaseParamEntry 16 } 562 rtcpXrBaseParamLocalRERLdB OBJECT-TYPE 563 SYNTAX LeveldB 564 UNITS "dBm" 565 MAX-ACCESS read-only 566 STATUS current 567 DESCRIPTION 568 "Residual Echo Return Loss measured at this endpoint, 569 or at the terminating endpoint of this RTP session. 570 This relates to the echo level from the network beyond 571 the terminating endpoint and may be interpreted as either 572 line echo in the case of a gateway or acoustic echo in the 573 case of a handset. 574 Note that this echo affects conversational quality as 575 perceived by the user at the originating end of this 576 RTP session. 577 A value of 127 indicates that this parameter is not 578 available. 579 In midpoint applications this parameter may not be 580 available. If this is a midstream device and call 581 quality metrics were calculated using the value of 582 this parameter reported from the endpoint in an 583 RTCP XR payload then the value used in this 584 calculation MAY be reported." 585 REFERENCE 586 "See RFC3611 Section 4.7." 587 ::= { rtcpXrBaseParamEntry 17 } 589 rtcpXrBaseParamRemoteRERLdB OBJECT-TYPE 590 SYNTAX LeveldB 591 UNITS "dBm" 592 MAX-ACCESS read-only 593 STATUS current 594 DESCRIPTION 595 "Residual Echo Return Loss measured at originating endpoint 596 of this RTP session (i.e. the remote endpoint if this MIB 597 is implemented in an endpoint). 598 Note that this affects the conversational quality 599 metrics reported by the terminating (this) endpoint, hence 600 is useful in understanding what has affected the reported 601 call quality metrics 602 A value of 127 indicates that this parameter is not 603 available. 604 In midpoint applications this parameter may not be 605 available. If this is a midstream device and call 606 quality metrics were calculated using the value of 607 this parameter reported from the endpoint in an 608 RTCP XR payload then the value used in this 609 calculation MAY be reported." 610 REFERENCE 611 "See RFC3611 Section 4.7." 612 ::= { rtcpXrBaseParamEntry 18 } 614 rtcpXrBaseParamPlcType OBJECT-TYPE 615 SYNTAX INTEGER { disabled(1), 616 enhanced(2), 617 standard(3), 618 unspecified (4)} 619 MAX-ACCESS read-only 620 STATUS current 621 DESCRIPTION 622 "Defines type of packet loss concealment used on this call." 623 REFERENCE 624 "See RFC3611 Section 4.7." 625 ::= { rtcpXrBaseParamEntry 19 } 627 rtcpXrBaseParamJBuffAdaptMode OBJECT-TYPE 628 SYNTAX INTEGER { reserved (1), 629 nonAdaptive (2), 630 adaptive (3), 631 unknown (4) } 632 MAX-ACCESS read-only 633 STATUS current 634 DESCRIPTION 635 "Defines if jitter buffer is in fixed or adaptive mode." 636 REFERENCE 637 "See RFC3611 Section 4.7." 638 ::= { rtcpXrBaseParamEntry 20 } 640 rtcpXrBaseParamJBuffAdaptRate OBJECT-TYPE 641 SYNTAX Unsigned32 (0..15) 642 MAX-ACCESS read-only 643 STATUS current 644 DESCRIPTION 645 "Estimated adaptation rate of jitter buffer." 646 REFERENCE 647 "See RFC3611 Section 4.7." 648 ::= { rtcpXrBaseParamEntry 21 } 650 rtcpXrBaseParamJBuffAverageDelay OBJECT-TYPE 651 SYNTAX Gauge32 652 UNITS "milliseconds" 653 MAX-ACCESS read-only 654 STATUS current 655 DESCRIPTION 656 "Average size of jitter buffer in mS." 657 REFERENCE 658 "See RFC3611 Section 4.7." 659 ::= { rtcpXrBaseParamEntry 22 } 661 rtcpXrBaseParamJBuffMaximumDelay OBJECT-TYPE 662 SYNTAX Gauge32 663 UNITS "milliseconds" 664 MAX-ACCESS read-only 665 STATUS current 666 DESCRIPTION 667 "Maximum delay through jitter buffer at current size in mS." 668 REFERENCE 669 "See RFC3611 Section 4.7." 670 ::= { rtcpXrBaseParamEntry 23 } 672 rtcpXrBaseParamJBuffAbsMaxDelay OBJECT-TYPE 673 SYNTAX Gauge32 674 UNITS "milliseconds" 675 MAX-ACCESS read-only 676 STATUS current 677 DESCRIPTION 678 "Absolute maximum size jitter buffer can reach in mS." 680 REFERENCE 681 "See RFC3611 Section 4.7." 682 ::= { rtcpXrBaseParamEntry 24 } 684 rtcpXrBaseParamJitterLevel OBJECT-TYPE 685 SYNTAX Gauge32 686 UNITS "milliseconds" 687 MAX-ACCESS read-only 688 STATUS current 689 DESCRIPTION 690 "Average jitter level measured according to RFC3550 and 691 represented in terms of milliseconds." 692 REFERENCE 693 "See RFC3550 Section 6.4." 694 ::= { rtcpXrBaseParamEntry 25 } 696 -- 697 -- Table of Call Quality Metrics 698 -- 700 rtcpXrCallQualityTable OBJECT-TYPE 701 SYNTAX SEQUENCE OF RtcpXrCallQualityEntry 702 MAX-ACCESS not-accessible 703 STATUS current 704 DESCRIPTION 705 "Table of voice quality metrics. A row is created 706 in this table for each row in the Session table." 707 ::= { rtcpXrMIBObjects 3 } 709 rtcpXrCallQualityEntry OBJECT-TYPE 710 SYNTAX RtcpXrCallQualityEntry 711 MAX-ACCESS not-accessible 712 STATUS current 713 DESCRIPTION 714 "An entry in the table of voice quality metrics. A row in 715 this table is created for each row in the Session 716 table." 717 INDEX { rtpSessionCallStatus, rtpSessionIndex } 718 ::= { rtcpXrCallQualityTable 1 } 720 RtcpXrCallQualityEntry ::= SEQUENCE { 721 rtcpXrCallQualityRCQ Rfactor, 722 rtcpXrCallQualityRLQ Rfactor, 723 rtcpXrCallQualityExternalRCQ Rfactor, 724 rtcpXrCallQualityMOSCQ ScaledMOSscore, 725 rtcpXrCallQualityMOSLQ ScaledMOSscore, 726 rtcpXrCallQualityRLQestAlgorithm OCTET STRING, 727 rtcpXrCallQualityRCQestAlgorithm OCTET STRING, 728 rtcpXrCallQualityMOSLQEstAlgorithm OCTET STRING, 729 rtcpXrCallQualityMOSCQEstAlgorithm OCTET STRING 730 } 731 rtcpXrCallQualityRCQ OBJECT-TYPE 732 SYNTAX Rfactor 733 UNITS "R factor" 734 MAX-ACCESS read-only 735 STATUS current 736 DESCRIPTION 737 "Conversational quality R factor for this call. This value 738 SHOULD be calculated using ITU G.107 (The E Model) or 739 extended versions thereof." 740 REFERENCE 741 "See RFC3611 Section 4.7." 742 ::= { rtcpXrCallQualityEntry 1 } 744 rtcpXrCallQualityRLQ OBJECT-TYPE 745 SYNTAX Rfactor 746 UNITS "R factor" 747 MAX-ACCESS read-only 748 STATUS current 749 DESCRIPTION 750 "Listening quality R factor for this call. This value 751 SHOULD be calculated using ITU G.107 (The E Model) or 752 extended versions thereof." 753 ::= { rtcpXrCallQualityEntry 2 } 755 rtcpXrCallQualityExternalRCQ OBJECT-TYPE 756 SYNTAX Rfactor 757 UNITS "R factor" 758 MAX-ACCESS read-only 759 STATUS current 760 DESCRIPTION 761 "External R factor for this call. This value 762 SHOULD be calculated using ITU G.107 (The E Model) or 763 extended versions thereof. 764 The External R factor relates to the quality of an 765 incoming voice from another network segment. For example 766 if a conference bridge terminates and re-creates voice 767 streams then an R factor would be calculated at the bridge 768 for the endpoint A to bridge segment and relayed to the 769 subsequent bridge to endpoint B as an External R factor. 770 This allows endpoint B to estimate the end-to-end call 771 quality." 772 ::= { rtcpXrCallQualityEntry 3 } 774 rtcpXrCallQualityMOSCQ OBJECT-TYPE 775 SYNTAX ScaledMOSscore 776 UNITS "MOS x 10" 777 MAX-ACCESS read-only 778 STATUS current 779 DESCRIPTION 780 "Estimated conversational quality MOS for this call 781 expressed in MOS x 10 (e.g. 41 = MOS of 4.1). This value 782 MAY be calculated by converting the R-CQ value to a MOS." 784 REFERENCE 785 "See RFC3611 Section 4.7." 786 ::= { rtcpXrCallQualityEntry 4 } 788 rtcpXrCallQualityMOSLQ OBJECT-TYPE 789 SYNTAX ScaledMOSscore 790 UNITS "MOS x 10" 791 MAX-ACCESS read-only 792 STATUS current 793 DESCRIPTION 794 "Estimated listening quality MOS for this call 795 expressed in MOS x 10 (e.g. 41 = MOS of 4.1). This value 796 MAY be calculated by converting the R-CQ value to a MOS." 797 REFERENCE 798 "See RFC3611 Section 4.7." 799 ::= { rtcpXrCallQualityEntry 5 } 801 rtcpXrCallQualityRLQestAlgorithm OBJECT-TYPE 802 SYNTAX OCTET STRING (SIZE(0..128)) 803 MAX-ACCESS read-only 804 STATUS current 805 DESCRIPTION 806 "Call quality algorithm used to determine R-LQ factors. 807 For example, 'ITU-T G.107' for the ITU G.107 808 E model or 'ETSI TS101329-5E' for ETSI 809 TS 101 329-5 Annex E." 810 ::= { rtcpXrCallQualityEntry 6 } 812 rtcpXrCallQualityRCQestAlgorithm OBJECT-TYPE 813 SYNTAX OCTET STRING (SIZE(0..128)) 814 MAX-ACCESS read-only 815 STATUS current 816 DESCRIPTION 817 "Call quality algorithm used to determine R-CQ factors. 818 For example, 'ITU-T G.107' for the ITU G.107 819 E model or 'ETSI TS101329-5E' for ETSI 820 TS 101 329-5 Annex E." 821 ::= { rtcpXrCallQualityEntry 7 } 823 rtcpXrCallQualityMOSLQEstAlgorithm OBJECT-TYPE 824 SYNTAX OCTET STRING (SIZE(0..128)) 825 MAX-ACCESS read-only 826 STATUS current 827 DESCRIPTION 828 "Call quality algorithm used to determine MOS-LQ scores. 829 If any localized parameter scaling is used 830 (for example Japan's TTC MOS scaling) then this 831 MUST also be reported." 832 ::= { rtcpXrCallQualityEntry 8 } 834 rtcpXrCallQualityMOSCQEstAlgorithm OBJECT-TYPE 835 SYNTAX OCTET STRING (SIZE(0..128)) 836 MAX-ACCESS read-only 837 STATUS current 838 DESCRIPTION 839 "Call quality algorithm used to determine MOS-CQ scores. 840 If any localized parameter scaling is used 841 (for example Japan's TTC MOS scaling) then this 842 MUST also be reported." 843 ::= { rtcpXrCallQualityEntry 9 } 845 -- History Table 846 -- 848 rtcpXrHistoryTable OBJECT-TYPE 849 SYNTAX SEQUENCE OF RtcpXrHistoryEntry 850 MAX-ACCESS not-accessible 851 STATUS current 852 DESCRIPTION 853 "Table of aggregate measurement data for groups 854 of RTP sessions. A group may be a flow or any 855 other logical association of streams." 856 ::= { rtcpXrMIBObjects 4 } 858 rtcpXrHistoryEntry OBJECT-TYPE 859 SYNTAX RtcpXrHistoryEntry 860 MAX-ACCESS not-accessible 861 STATUS current 862 DESCRIPTION 863 "An entry in the table of call history records." 864 INDEX { rtcpXrHistoryIndex } 865 ::= { rtcpXrHistoryTable 1 } 867 RtcpXrHistoryEntry ::= SEQUENCE { 868 rtcpXrHistoryIndex Unsigned32, 869 rtcpXrHistoryGroupName OCTET STRING, 870 rtcpXrHistoryStartTime DateAndTime, 871 rtcpXrHistoryStopTime DateAndTime, 872 rtcpXrHistoryNumOfSessions Counter32, 873 rtcpXrHistoryMinDurationMs Gauge32, 874 rtcpXrHistoryMaxDurationMs Gauge32, 875 rtcpXrHistoryAvgDurationMs Gauge32, 876 rtcpXrHistoryMaxNetworkLossRate Percentage, 877 rtcpXrHistoryAvgNetworkLossRate Percentage, 878 rtcpXrHistoryMaxDiscardRate Percentage, 879 rtcpXrHistoryAvgDiscardRate Percentage, 880 rtcpXrHistoryMaxBurstLossDensity Percentage, 881 rtcpXrHistoryAvgBurstLossDensity Percentage, 882 rtcpXrHistoryMinBurstLenMs Gauge32, 883 rtcpXrHistoryMaxBurstLenMs Gauge32, 884 rtcpXrHistoryAvgBurstLenMs Gauge32, 885 rtcpXrHistoryMaxGapLossDensity Percentage, 886 rtcpXrHistoryAvgGapLossDensity Percentage, 887 rtcpXrHistoryMinGapLenMs Gauge32, 888 rtcpXrHistoryMaxGapLenMs Gauge32, 889 rtcpXrHistoryAvgGapLenMs Gauge32, 890 rtcpXrHistoryMinOneWayDelay Gauge32, 891 rtcpXrHistoryMaxOneWayDelay Gauge32, 892 rtcpXrHistoryAvgOneWayDelay Gauge32, 893 rtcpXrHistoryOneWayDelayCount Counter32, 894 rtcpXrHistoryMinEndSystemDelay Gauge32, 895 rtcpXrHistoryMaxEndSystemDelay Gauge32, 896 rtcpXrHistoryAvgEndSystemDelay Gauge32, 897 rtcpXrHistoryEndSystemDelayCount Counter32, 898 rtcpXrHistoryMinJitterLevel Gauge32, 899 rtcpXrHistoryMaxJitterLevel Gauge32, 900 rtcpXrHistoryAvgJitterLevel Gauge32, 901 rtcpXrHistoryMinNoiseLeveldBm LeveldB, 902 rtcpXrHistoryMaxNoiseLeveldBm LeveldB, 903 rtcpXrHistoryAvgNoiseLeveldBm LeveldB, 904 rtcpXrHistoryNoiseLevelCount Counter32, 905 rtcpXrHistoryMinSignalLeveldBm LeveldB, 906 rtcpXrHistoryMaxSignalLeveldBm LeveldB, 907 rtcpXrHistoryAvgSignalLeveldBm LeveldB, 908 rtcpXrHistorySignalLevelCount Counter32, 909 rtcpXrHistoryMinLocalRERLdB LeveldB, 910 rtcpXrHistoryMaxLocalRERLdB LeveldB, 911 rtcpXrHistoryAvgLocalRERLdB LeveldB, 912 rtcpXrHistoryLocalRERLCount Counter32, 913 rtcpXrHistoryMinRemoteRERLdB LeveldB, 914 rtcpXrHistoryMaxRemoteRERLdB LeveldB, 915 rtcpXrHistoryAvgRemoteRERLdB LeveldB, 916 rtcpXrHistoryRemoteRERLCount Counter32, 917 rtcpXrHistoryMinRCQ Rfactor, 918 rtcpXrHistoryMaxRCQ Rfactor, 919 rtcpXrHistoryAvgRCQ Rfactor, 920 rtcpXrHistoryRCQCount Counter32, 921 rtcpXrHistoryMinRLQ Rfactor, 922 rtcpXrHistoryMaxRLQ Rfactor, 923 rtcpXrHistoryAvgRLQ Rfactor, 924 rtcpXrHistoryRLQCount Counter32, 925 rtcpXrHistoryMinMOSCQ ScaledMOSscore, 926 rtcpXrHistoryMaxMOSCQ ScaledMOSscore, 927 rtcpXrHistoryAvgMOSCQ ScaledMOSscore, 928 rtcpXrHistoryMOSCQCount Counter32, 929 rtcpXrHistoryMinMOSLQ ScaledMOSscore, 930 rtcpXrHistoryMaxMOSLQ ScaledMOSscore, 931 rtcpXrHistoryAvgMOSLQ ScaledMOSscore, 932 rtcpXrHistoryMOSLQCount Counter32, 933 rtcpXrHistoryCQAlgorithm OCTET STRING, 934 rtcpXrHistoryReset INTEGER 935 } 936 rtcpXrHistoryIndex OBJECT-TYPE 937 SYNTAX Unsigned32 (0..4294967295) 938 MAX-ACCESS not-accessible 939 STATUS current 940 DESCRIPTION 941 "Index for this set of aggregate data." 942 ::= { rtcpXrHistoryEntry 1 } 944 rtcpXrHistoryGroupName OBJECT-TYPE 945 SYNTAX OCTET STRING (SIZE(0..128)) 946 MAX-ACCESS read-write 947 STATUS current 948 DESCRIPTION 949 "Name of this set of aggregate data. Examples may include 950 a flow, an interface or some other logical grouping of 951 RTP sessions." 952 ::= { rtcpXrHistoryEntry 2 } 954 rtcpXrHistoryStartTime OBJECT-TYPE 955 SYNTAX DateAndTime 956 MAX-ACCESS read-only 957 STATUS current 958 DESCRIPTION 959 "Time at which this history was reset or started." 960 ::= {rtcpXrHistoryEntry 3 } 962 rtcpXrHistoryStopTime OBJECT-TYPE 963 SYNTAX DateAndTime 964 MAX-ACCESS read-only 965 STATUS current 966 DESCRIPTION 967 "Time at which this history was stopped." 968 ::= {rtcpXrHistoryEntry 4 } 970 rtcpXrHistoryNumOfSessions OBJECT-TYPE 971 SYNTAX Counter32 972 MAX-ACCESS read-only 973 STATUS current 974 DESCRIPTION 975 "Number of calls included in this history." 976 ::= {rtcpXrHistoryEntry 5 } 978 rtcpXrHistoryMinDurationMs OBJECT-TYPE 979 SYNTAX Gauge32 980 UNITS "milliseconds" 981 MAX-ACCESS read-only 982 STATUS current 983 DESCRIPTION 984 "Minimum duration of calls." 985 ::= {rtcpXrHistoryEntry 6 } 987 rtcpXrHistoryMaxDurationMs OBJECT-TYPE 988 SYNTAX Gauge32 989 UNITS "milliseconds" 990 MAX-ACCESS read-only 991 STATUS current 992 DESCRIPTION 993 "Maximum duration of calls." 994 ::= {rtcpXrHistoryEntry 7 } 996 rtcpXrHistoryAvgDurationMs OBJECT-TYPE 997 SYNTAX Gauge32 998 UNITS "milliseconds" 999 MAX-ACCESS read-only 1000 STATUS current 1001 DESCRIPTION 1002 "Average duration of calls within this history." 1003 ::= {rtcpXrHistoryEntry 8 } 1005 rtcpXrHistoryMaxNetworkLossRate OBJECT-TYPE 1006 SYNTAX Percentage 1007 UNITS "percent" 1008 MAX-ACCESS read-only 1009 STATUS current 1010 DESCRIPTION 1011 "Maximum loss rate occurring on any call in this history." 1012 ::= {rtcpXrHistoryEntry 9 } 1014 rtcpXrHistoryAvgNetworkLossRate OBJECT-TYPE 1015 SYNTAX Percentage 1016 UNITS "percent" 1017 MAX-ACCESS read-only 1018 STATUS current 1019 DESCRIPTION 1020 "Mean for all calls in this history of the individual 1021 per call packet loss rate." 1022 ::= {rtcpXrHistoryEntry 10 } 1024 rtcpXrHistoryMaxDiscardRate OBJECT-TYPE 1025 SYNTAX Percentage 1026 UNITS "percent" 1027 MAX-ACCESS read-only 1028 STATUS current 1029 DESCRIPTION 1030 "Maximum discard rate occurring on any call in this history." 1031 ::= {rtcpXrHistoryEntry 11 } 1033 rtcpXrHistoryAvgDiscardRate OBJECT-TYPE 1034 SYNTAX Percentage 1035 UNITS "percent" 1036 MAX-ACCESS read-only 1037 STATUS current 1038 DESCRIPTION 1039 "Mean for all calls in this history of the individual 1040 per call packet discard rate." 1041 ::= {rtcpXrHistoryEntry 12 } 1043 rtcpXrHistoryMaxBurstLossDensity OBJECT-TYPE 1044 SYNTAX Percentage 1045 UNITS "percent" 1046 MAX-ACCESS read-only 1047 STATUS current 1048 DESCRIPTION 1049 "Maximum of the per-call average burst densities for any 1050 call in this history. A value of 0 shall be reported if 1051 no bursts were reported." 1052 ::= {rtcpXrHistoryEntry 13 } 1054 rtcpXrHistoryAvgBurstLossDensity OBJECT-TYPE 1055 SYNTAX Percentage 1056 UNITS "percent" 1057 MAX-ACCESS read-only 1058 STATUS current 1059 DESCRIPTION 1060 "Mean for all calls in this history of the individual 1061 per call burst density. A value of 0 shall be reported if 1062 no bursts were reported." 1063 ::= {rtcpXrHistoryEntry 14 } 1065 rtcpXrHistoryMinBurstLenMs OBJECT-TYPE 1066 SYNTAX Gauge32 1067 UNITS "milliseconds" 1068 MAX-ACCESS read-only 1069 STATUS current 1070 DESCRIPTION 1071 "Minimum of the per-call burst length for all calls in this 1072 history for which a burst length was reported. A value of 1073 0 shall be reported if no bursts were present." 1074 ::= {rtcpXrHistoryEntry 15 } 1076 rtcpXrHistoryMaxBurstLenMs OBJECT-TYPE 1077 SYNTAX Gauge32 1078 UNITS "milliseconds" 1079 MAX-ACCESS read-only 1080 STATUS current 1081 DESCRIPTION 1082 "Maximum of the per-call burst length for all calls in this 1083 history for which a burst length was reported. A value of 1084 0 shall be reported if no bursts were present." 1085 ::= {rtcpXrHistoryEntry 16 } 1087 rtcpXrHistoryAvgBurstLenMs OBJECT-TYPE 1088 SYNTAX Gauge32 1089 UNITS "milliseconds" 1090 MAX-ACCESS read-only 1091 STATUS current 1092 DESCRIPTION 1093 "Mean of the per-call burst length for all calls in this 1094 history for which a burst length was reported. A value of 1095 0 shall be reported if no bursts were present." 1096 ::= {rtcpXrHistoryEntry 17 } 1098 rtcpXrHistoryMaxGapLossDensity OBJECT-TYPE 1099 SYNTAX Percentage 1100 UNITS "percent" 1101 MAX-ACCESS read-only 1102 STATUS current 1103 DESCRIPTION 1104 "Maximum of the per-call gap density for all calls in this 1105 history for which a gap density was reported. A value of 1106 0 shall be reported if no gaps were present." 1107 ::= {rtcpXrHistoryEntry 18 } 1109 rtcpXrHistoryAvgGapLossDensity OBJECT-TYPE 1110 SYNTAX Percentage 1111 UNITS "percent" 1112 MAX-ACCESS read-only 1113 STATUS current 1114 DESCRIPTION 1115 "Mean of the per-call gap density for all calls in this 1116 history for which a gap density was reported. A value of 1117 0 shall be reported if no gaps were present." 1118 ::= {rtcpXrHistoryEntry 19 } 1120 rtcpXrHistoryMinGapLenMs OBJECT-TYPE 1121 SYNTAX Gauge32 1122 UNITS "milliseconds" 1123 MAX-ACCESS read-only 1124 STATUS current 1125 DESCRIPTION 1126 "Minimum of the per-call gap length for all calls in this 1127 history for which a gap length was reported. A value of 1128 0 shall be reported if no gaps were present." 1129 ::= {rtcpXrHistoryEntry 20 } 1131 rtcpXrHistoryMaxGapLenMs OBJECT-TYPE 1132 SYNTAX Gauge32 1133 UNITS "milliseconds" 1134 MAX-ACCESS read-only 1135 STATUS current 1136 DESCRIPTION 1137 "Maximum of the per-call gap length for all calls in this 1138 history for which a gap length was reported. A value of 1139 0 shall be reported if no gaps were present." 1140 ::= {rtcpXrHistoryEntry 21 } 1142 rtcpXrHistoryAvgGapLenMs OBJECT-TYPE 1143 SYNTAX Gauge32 1144 UNITS "milliseconds" 1145 MAX-ACCESS read-only 1146 STATUS current 1147 DESCRIPTION 1148 "Mean of the per-call gap length for all calls in this 1149 history for which a gap length was reported. A value of 1150 0 shall be reported if no gaps were present." 1151 ::= {rtcpXrHistoryEntry 22 } 1153 rtcpXrHistoryMinOneWayDelay OBJECT-TYPE 1154 SYNTAX Gauge32 1155 UNITS "milliseconds" 1156 MAX-ACCESS read-only 1157 STATUS current 1158 DESCRIPTION 1159 "Minimum of the per-call OW Delays for all calls in this 1160 history for which a Delay was reported. A value of 1161 0 shall be reported if no Delay values were reported." 1162 ::= {rtcpXrHistoryEntry 23 } 1164 rtcpXrHistoryMaxOneWayDelay OBJECT-TYPE 1165 SYNTAX Gauge32 1166 UNITS "milliseconds" 1167 MAX-ACCESS read-only 1168 STATUS current 1169 DESCRIPTION 1170 "Maximum of the per-call OW Delays for all calls in this 1171 history for which a Delay was reported. A value of 1172 0 shall be reported if no Delay values were reported." 1173 ::= {rtcpXrHistoryEntry 24 } 1175 rtcpXrHistoryAvgOneWayDelay OBJECT-TYPE 1176 SYNTAX Gauge32 1177 UNITS "milliseconds" 1178 MAX-ACCESS read-only 1179 STATUS current 1180 DESCRIPTION 1181 "Mean of the per-call OW Delays for all calls in this 1182 history for which a Delay was reported. A value of 1183 0 shall be reported if no Delay values were reported." 1184 ::= {rtcpXrHistoryEntry 25 } 1186 rtcpXrHistoryOneWayDelayCount OBJECT-TYPE 1187 SYNTAX Counter32 1188 MAX-ACCESS read-only 1189 STATUS current 1190 DESCRIPTION 1191 "Number of sessions included in the One Way Delay 1192 history values (as Delay may not be available on 1193 all calls." 1194 ::= {rtcpXrHistoryEntry 26 } 1196 rtcpXrHistoryMinEndSystemDelay OBJECT-TYPE 1197 SYNTAX Gauge32 1198 UNITS "milliseconds" 1199 MAX-ACCESS read-only 1200 STATUS current 1201 DESCRIPTION 1202 "Minimum of the per-call ES Delays for all calls in this 1203 history for which an ES Delay was reported." 1204 ::= {rtcpXrHistoryEntry 27 } 1206 rtcpXrHistoryMaxEndSystemDelay OBJECT-TYPE 1207 SYNTAX Gauge32 1208 UNITS "milliseconds" 1209 MAX-ACCESS read-only 1210 STATUS current 1211 DESCRIPTION 1212 "Maximum of the per-call ES Delays for all calls in this 1213 history for which an ES Delay was reported." 1214 ::= {rtcpXrHistoryEntry 28 } 1216 rtcpXrHistoryAvgEndSystemDelay OBJECT-TYPE 1217 SYNTAX Gauge32 1218 UNITS "milliseconds" 1219 MAX-ACCESS read-only 1220 STATUS current 1221 DESCRIPTION 1222 "Mean of the per-call ES Delays for all calls in this 1223 history for which an ES Delay was reported." 1224 ::= {rtcpXrHistoryEntry 29 } 1226 rtcpXrHistoryEndSystemDelayCount OBJECT-TYPE 1227 SYNTAX Counter32 1228 MAX-ACCESS read-only 1229 STATUS current 1230 DESCRIPTION 1231 "Number of sessions included in the End System 1232 Delay history values (as End System Delay 1233 may not be available on all calls." 1234 ::= {rtcpXrHistoryEntry 30 } 1236 rtcpXrHistoryMinJitterLevel OBJECT-TYPE 1237 SYNTAX Gauge32 1238 UNITS "milliseconds" 1239 MAX-ACCESS read-only 1240 STATUS current 1241 DESCRIPTION 1242 "Minimum of the per-call jitter for all calls in this 1243 history for which a jitter value was reported." 1244 ::= {rtcpXrHistoryEntry 31 } 1246 rtcpXrHistoryMaxJitterLevel OBJECT-TYPE 1247 SYNTAX Gauge32 1248 UNITS "milliseconds" 1249 MAX-ACCESS read-only 1250 STATUS current 1251 DESCRIPTION 1252 "Maximum of the per-call jitter for all calls in this 1253 history for which a jitter value was reported." 1254 ::= {rtcpXrHistoryEntry 32 } 1256 rtcpXrHistoryAvgJitterLevel OBJECT-TYPE 1257 SYNTAX Gauge32 1258 UNITS "milliseconds" 1259 MAX-ACCESS read-only 1260 STATUS current 1261 DESCRIPTION 1262 "Mean of the per-call jitter for all calls in this 1263 history for which a jitter value was reported." 1264 ::= {rtcpXrHistoryEntry 33 } 1266 rtcpXrHistoryMinNoiseLeveldBm OBJECT-TYPE 1267 SYNTAX LeveldB 1268 UNITS "dBm0" 1269 MAX-ACCESS read-only 1270 STATUS current 1271 DESCRIPTION 1272 "Minimum of the per-call Noise Level for all calls in this 1273 history for which a Noise Level value was reported." 1274 ::= {rtcpXrHistoryEntry 34 } 1276 rtcpXrHistoryMaxNoiseLeveldBm OBJECT-TYPE 1277 SYNTAX LeveldB 1278 UNITS "dBm0" 1279 MAX-ACCESS read-only 1280 STATUS current 1281 DESCRIPTION 1282 "Maximum of the per-call Noise Level for all calls in this 1283 history for which a Noise Level value was reported." 1284 ::= {rtcpXrHistoryEntry 35 } 1286 rtcpXrHistoryAvgNoiseLeveldBm OBJECT-TYPE 1287 SYNTAX LeveldB 1288 UNITS "dBm0" 1289 MAX-ACCESS read-only 1290 STATUS current 1291 DESCRIPTION 1292 "Mean of the per-call Noise Level for all calls in this 1293 history for which a Noise Level value was reported." 1294 ::= {rtcpXrHistoryEntry 36 } 1296 rtcpXrHistoryNoiseLevelCount OBJECT-TYPE 1297 SYNTAX Counter32 1298 MAX-ACCESS read-only 1299 STATUS current 1300 DESCRIPTION 1301 "Number of sessions included in the Noise Level 1302 history values (as Noise Level is an optional 1303 parameter and may not be present on all calls." 1304 ::= {rtcpXrHistoryEntry 37 } 1306 rtcpXrHistoryMinSignalLeveldBm OBJECT-TYPE 1307 SYNTAX LeveldB 1308 UNITS "dBm0" 1309 MAX-ACCESS read-only 1310 STATUS current 1311 DESCRIPTION 1312 "Minimum of the per-call Signal Level for all calls in this 1313 history for which a Signal Level value was reported." 1314 ::= {rtcpXrHistoryEntry 38 } 1316 rtcpXrHistoryMaxSignalLeveldBm OBJECT-TYPE 1317 SYNTAX LeveldB 1318 UNITS "dBm0" 1319 MAX-ACCESS read-only 1320 STATUS current 1321 DESCRIPTION 1322 "Maximum of the per-call Signal Level for all calls in this 1323 history for which a Signal Level value was reported." 1324 ::= {rtcpXrHistoryEntry 39 } 1326 rtcpXrHistoryAvgSignalLeveldBm OBJECT-TYPE 1327 SYNTAX LeveldB 1328 UNITS "dBm0" 1329 MAX-ACCESS read-only 1330 STATUS current 1331 DESCRIPTION 1332 "Mean of the per-call Signal Level for all calls in this 1333 history for which a Signal Level value was reported." 1334 ::= {rtcpXrHistoryEntry 40 } 1336 rtcpXrHistorySignalLevelCount OBJECT-TYPE 1337 SYNTAX Counter32 1338 MAX-ACCESS read-only 1339 STATUS current 1340 DESCRIPTION 1341 "Number of sessions included in the Signal Level 1342 history values (as Signal Level is an optional 1343 parameter and may not be present on all calls." 1344 ::= {rtcpXrHistoryEntry 41 } 1346 rtcpXrHistoryMinLocalRERLdB OBJECT-TYPE 1347 SYNTAX LeveldB 1348 UNITS "dBm" 1349 MAX-ACCESS read-only 1350 STATUS current 1351 DESCRIPTION 1352 "Minimum of the per-call local RERL for all calls in this 1353 history for which a local RERL value was reported." 1354 ::= {rtcpXrHistoryEntry 42 } 1356 rtcpXrHistoryMaxLocalRERLdB OBJECT-TYPE 1357 SYNTAX LeveldB 1358 UNITS "dBm" 1359 MAX-ACCESS read-only 1360 STATUS current 1361 DESCRIPTION 1362 "Maximum of the per-call local RERL for all calls in this 1363 history for which a local RERL value was reported." 1364 ::= {rtcpXrHistoryEntry 43 } 1366 rtcpXrHistoryAvgLocalRERLdB OBJECT-TYPE 1367 SYNTAX LeveldB 1368 UNITS "dBm" 1369 MAX-ACCESS read-only 1370 STATUS current 1371 DESCRIPTION 1372 "Mean of the per-call local RERL for all calls in this 1373 history for which a local RERL value was reported." 1374 ::= {rtcpXrHistoryEntry 44 } 1376 rtcpXrHistoryLocalRERLCount OBJECT-TYPE 1377 SYNTAX Counter32 1378 MAX-ACCESS read-only 1379 STATUS current 1380 DESCRIPTION 1381 "Number of sessions included in the Local RERL 1382 history values (as Local RERL is an optional 1383 parameter and may not be present on all calls." 1384 ::= {rtcpXrHistoryEntry 45 } 1386 rtcpXrHistoryMinRemoteRERLdB OBJECT-TYPE 1387 SYNTAX LeveldB 1388 UNITS "dBm" 1389 MAX-ACCESS read-only 1390 STATUS current 1391 DESCRIPTION 1392 "Minimum of the per-call remote RERL for all calls in this 1393 history for which a remote RERL value was reported." 1394 ::= {rtcpXrHistoryEntry 46 } 1396 rtcpXrHistoryMaxRemoteRERLdB OBJECT-TYPE 1397 SYNTAX LeveldB 1398 UNITS "dBm" 1399 MAX-ACCESS read-only 1400 STATUS current 1401 DESCRIPTION 1402 "Maximum of the per-call remote RERL for all calls in this 1403 history for which a remote RERL value was reported." 1404 ::= {rtcpXrHistoryEntry 47 } 1406 rtcpXrHistoryAvgRemoteRERLdB OBJECT-TYPE 1407 SYNTAX LeveldB 1408 UNITS "dBm" 1409 MAX-ACCESS read-only 1410 STATUS current 1411 DESCRIPTION 1412 "Mean of the per-call remote RERL for all calls in this 1413 history for which a remote RERL value was reported." 1414 ::= {rtcpXrHistoryEntry 48 } 1416 rtcpXrHistoryRemoteRERLCount OBJECT-TYPE 1417 SYNTAX Counter32 1418 MAX-ACCESS read-only 1419 STATUS current 1420 DESCRIPTION 1421 "Number of sessions included in the Remote RERL 1422 history values (as Remote RERL is an optional 1423 parameter and may not be present on all calls." 1424 ::= {rtcpXrHistoryEntry 49 } 1426 rtcpXrHistoryMinRCQ OBJECT-TYPE 1427 SYNTAX Rfactor 1428 UNITS "R factor" 1429 MAX-ACCESS read-only 1430 STATUS current 1431 DESCRIPTION 1432 "Minimum of the per-call R-CQ for all calls in this 1433 history for which an R-CQ value was reported." 1434 ::= {rtcpXrHistoryEntry 50 } 1436 rtcpXrHistoryMaxRCQ OBJECT-TYPE 1437 SYNTAX Rfactor 1438 UNITS "R factor" 1439 MAX-ACCESS read-only 1440 STATUS current 1441 DESCRIPTION 1442 "Maximum of the per-call R-CQ for all calls in this 1443 history for which an R-CQ value was reported." 1444 ::= {rtcpXrHistoryEntry 51 } 1446 rtcpXrHistoryAvgRCQ OBJECT-TYPE 1447 SYNTAX Rfactor 1448 UNITS "R factor" 1449 MAX-ACCESS read-only 1450 STATUS current 1451 DESCRIPTION 1452 "Mean of the per-call R-CQ for all calls in this 1453 history for which an R-CQ value was reported." 1454 ::= {rtcpXrHistoryEntry 52 } 1456 rtcpXrHistoryRCQCount OBJECT-TYPE 1457 SYNTAX Counter32 1458 MAX-ACCESS read-only 1459 STATUS current 1460 DESCRIPTION 1461 "Number of sessions included in the R CQ 1462 history values (as R CQ is an optional 1463 parameter and may not be present on all calls." 1464 ::= {rtcpXrHistoryEntry 53 } 1466 rtcpXrHistoryMinRLQ OBJECT-TYPE 1467 SYNTAX Rfactor 1468 UNITS "R factor" 1469 MAX-ACCESS read-only 1470 STATUS current 1471 DESCRIPTION 1472 "Minimum of the per-call R-LQ for all calls in this 1473 history for which an R-LQ value was reported." 1474 ::= {rtcpXrHistoryEntry 54 } 1476 rtcpXrHistoryMaxRLQ OBJECT-TYPE 1477 SYNTAX Rfactor 1478 UNITS "R factor" 1479 MAX-ACCESS read-only 1480 STATUS current 1481 DESCRIPTION 1482 "Maximum of the per-call R-LQ for all calls in this 1483 history for which an R-LQ value was reported." 1484 ::= {rtcpXrHistoryEntry 55 } 1486 rtcpXrHistoryAvgRLQ OBJECT-TYPE 1487 SYNTAX Rfactor 1488 UNITS "R factor" 1489 MAX-ACCESS read-only 1490 STATUS current 1491 DESCRIPTION 1492 "Mean of the per-call R-LQ for all calls in this 1493 history for which an R-LQ value was reported." 1494 ::= {rtcpXrHistoryEntry 56 } 1496 rtcpXrHistoryRLQCount OBJECT-TYPE 1497 SYNTAX Counter32 1498 MAX-ACCESS read-only 1499 STATUS current 1500 DESCRIPTION 1501 "Number of sessions included in the R LQ 1502 history values (as R LQ is an optional 1503 parameter and may not be present on all calls." 1504 ::= {rtcpXrHistoryEntry 57 } 1506 rtcpXrHistoryMinMOSCQ OBJECT-TYPE 1507 SYNTAX ScaledMOSscore 1508 UNITS "MOS x 10" 1509 MAX-ACCESS read-only 1510 STATUS current 1511 DESCRIPTION 1512 "Minimum of the per-call MOS-CQ for all calls in this 1513 history for which a MOS-CQ value was reported." 1514 ::= {rtcpXrHistoryEntry 58 } 1516 rtcpXrHistoryMaxMOSCQ OBJECT-TYPE 1517 SYNTAX ScaledMOSscore 1518 UNITS "MOS x 10" 1519 MAX-ACCESS read-only 1520 STATUS current 1521 DESCRIPTION 1522 "Maximum of the per-call MOS-CQ for all calls in this 1523 history for which a MOS-CQ value was reported." 1524 ::= {rtcpXrHistoryEntry 59 } 1526 rtcpXrHistoryAvgMOSCQ OBJECT-TYPE 1527 SYNTAX ScaledMOSscore 1528 UNITS "MOS x 10" 1529 MAX-ACCESS read-only 1530 STATUS current 1531 DESCRIPTION 1532 "Mean of the per-call MOS-CQ for all calls in this 1533 history for which a MOS-CQ value was reported." 1534 ::= {rtcpXrHistoryEntry 60 } 1536 rtcpXrHistoryMOSCQCount OBJECT-TYPE 1537 SYNTAX Counter32 1538 MAX-ACCESS read-only 1539 STATUS current 1540 DESCRIPTION 1541 "Number of sessions included in the MOS CQ 1542 history values (as MOS CQ is an optional 1543 parameter and may not be present on all calls." 1544 ::= {rtcpXrHistoryEntry 61 } 1546 rtcpXrHistoryMinMOSLQ OBJECT-TYPE 1547 SYNTAX ScaledMOSscore 1548 UNITS "MOS x 10" 1549 MAX-ACCESS read-only 1550 STATUS current 1551 DESCRIPTION 1552 "Minimum of the per-call MOS-LQ for all calls in this 1553 history for which a MOS-LQ value was reported." 1554 ::= {rtcpXrHistoryEntry 62 } 1556 rtcpXrHistoryMaxMOSLQ OBJECT-TYPE 1557 SYNTAX ScaledMOSscore 1558 UNITS "MOS x 10" 1559 MAX-ACCESS read-only 1560 STATUS current 1561 DESCRIPTION 1562 "Maximum of the per-call MOS-LQ for all calls in this 1563 history for which a MOS-LQ value was reported." 1564 ::= {rtcpXrHistoryEntry 63 } 1566 rtcpXrHistoryAvgMOSLQ OBJECT-TYPE 1567 SYNTAX ScaledMOSscore 1568 UNITS "MOS x 10" 1569 MAX-ACCESS read-only 1570 STATUS current 1571 DESCRIPTION 1572 "Mean of the per-call MOS-LQ for all calls in this 1573 history for which a MOS-LQ value was reported." 1574 ::= {rtcpXrHistoryEntry 64 } 1576 rtcpXrHistoryMOSLQCount OBJECT-TYPE 1577 SYNTAX Counter32 1578 MAX-ACCESS read-only 1579 STATUS current 1580 DESCRIPTION 1581 "Number of sessions included in the MOS LQ 1582 history values (as MOS LQ is an optional 1583 parameter and may not be present on all calls." 1584 ::= {rtcpXrHistoryEntry 65 } 1586 rtcpXrHistoryCQAlgorithm OBJECT-TYPE 1587 SYNTAX OCTET STRING (SIZE(0..32)) 1588 MAX-ACCESS read-only 1589 STATUS current 1590 DESCRIPTION 1591 "Call quality algorithm used - if consistent 1592 for all calls in this history." 1593 ::= {rtcpXrHistoryEntry 66 } 1595 rtcpXrHistoryReset OBJECT-TYPE 1596 SYNTAX INTEGER { running (1), 1597 stop (2), 1598 reset (3) 1599 } 1600 MAX-ACCESS read-write 1601 STATUS current 1602 DESCRIPTION 1603 "Status of this row in the history table. 1604 Writing a value of 2 to this object MUST cause 1605 history updates to be stopped for this row. Writing 1606 a value of 3 to this object MUST cause the history 1607 row to be reset. 1608 Reads MUST return a value of 1 if the row is still 1609 being updated or 2 if the row update has stopped." 1610 ::= {rtcpXrHistoryEntry 67 } 1612 -- 1613 -- Notifications 1614 -- 1616 rtcpXrVoipThresholdViolation NOTIFICATION-TYPE 1617 OBJECTS { rtcpXrVoipAlertSeverity, rtcpXrVoipAlertType, 1618 rtcpXrVoipAlertInfoType, rtcpXrVoipAlertPointer } 1619 STATUS current 1620 DESCRIPTION 1621 "Notification that voice quality has changed 1622 Sent immediately when the condition is detected." 1623 ::= { rtcpXrEvents 1} 1625 rtcpXrEventParam OBJECT IDENTIFIER ::= { rtcpXrEvents 2 } 1627 rtcpXrVoipAlertType OBJECT-TYPE 1628 SYNTAX SnmpAdminString 1629 MAX-ACCESS read-only 1630 STATUS current 1631 DESCRIPTION 1632 "Text description of the type of alert. Where possible, 1633 this parameter should be populated with the correct 1634 rtcpXrVoipEntry or rtcpXrVoipHistory description." 1635 ::= { rtcpXrEventParam 1 } 1637 rtcpXrVoipAlertInfoType OBJECT-TYPE 1638 SYNTAX INTEGER { adminStringOnly (1), 1639 sessionPointer (2), 1640 historyPointer (3) 1641 } 1642 MAX-ACCESS read-only 1643 STATUS current 1644 DESCRIPTION 1645 "Indicates the type of information returned in the 1646 rtcpXrVoipAlertInfo parameter." 1647 ::= { rtcpXrEventParam 2 } 1649 rtcpXrVoipAlertPointer OBJECT-TYPE 1650 SYNTAX RowPointer 1651 MAX-ACCESS read-only 1652 STATUS current 1653 DESCRIPTION 1654 "Pointer to the table of call session information to 1655 identify the specific call that triggered the alert." 1656 ::= { rtcpXrEventParam 3 } 1658 rtcpXrVoipAlertSeverity OBJECT-TYPE 1659 SYNTAX ItuPerceivedSeverity 1660 MAX-ACCESS read-only 1661 STATUS current 1662 DESCRIPTION 1663 "The severity of the alert as defined in ITU-T X.733 and 1664 RFC3877." 1665 REFERENCE 1666 "See Alarm MIB - RFC3877." 1667 ::= { rtcpXrEventParam 4 } 1669 -- MODULE GROUPS 1670 -- 1671 -- There are four types of RTCP XR VoIP Metrics System. 1672 -- 1673 -- RTCP XR VOIP Metrics Systems MUST implement one of the four 1674 -- identified types of system and SHOULD NOT implement the 1675 -- rtcpXrMinimalCompliance system, which is included only 1676 -- for reasons of compatibility with RFC3611's minimal 1677 -- requirements. 1679 rtcpXrCompliances OBJECT IDENTIFIER ::= { rtcpXrConformance 1 } 1680 rtcpXrGroups OBJECT IDENTIFIER ::= { rtcpXrConformance 2 } 1682 rtcpXrFullMetricsCompliance MODULE-COMPLIANCE 1683 STATUS current 1684 DESCRIPTION 1685 "Describes the requirements for conformance to the 1686 rtcpXr MIB for VoIP devices that support basic 1687 reporting." 1689 MODULE -- this module 1690 MANDATORY-GROUPS { 1691 rtcpXrBaseParamGroup, 1692 rtcpXrCallQualityGroup 1693 } 1694 ::= { rtcpXrCompliances 1 } 1696 rtcpXrMetricsAlertsCompliance MODULE-COMPLIANCE 1697 STATUS current 1698 DESCRIPTION 1699 "Describes the requirements for conformance to the 1700 rtcpXr MIB for VoIP devices that support reporting 1701 and alerts." 1702 MODULE -- this module 1703 MANDATORY-GROUPS { 1704 rtcpXrBaseParamGroup, 1705 rtcpXrCallQualityGroup, 1706 rtcpXrNotificationParmsGroup, 1707 rtcpXrNotificationsGroup 1708 } 1709 ::= { rtcpXrCompliances 2 } 1711 rtcpXrMetricsHistoryCompliance MODULE-COMPLIANCE 1712 STATUS current 1713 DESCRIPTION 1714 "Describes the requirements for conformance to the 1715 rtcpXr MIB for VoIP devices that support reporting, 1716 call history and alerts." 1717 MODULE -- this module 1718 MANDATORY-GROUPS { 1719 rtcpXrBaseParamGroup, 1720 rtcpXrCallQualityGroup, 1721 rtcpXrMIBHistoryGroup, 1722 rtcpXrNotificationParmsGroup, 1723 rtcpXrNotificationsGroup } 1724 ::= { rtcpXrCompliances 3 } 1726 rtcpXrHistoryCompliance MODULE-COMPLIANCE 1727 STATUS current 1728 DESCRIPTION 1729 "Describes the requirements for conformance to the 1730 rtcpXr MIB for VoIP devices that support only 1731 call history." 1732 MODULE -- this module 1733 MANDATORY-GROUPS { rtcpXrMIBHistoryGroup 1734 } 1735 ::= { rtcpXrCompliances 4 } 1737 rtcpXrMinimalCompliance MODULE-COMPLIANCE 1738 STATUS current 1739 DESCRIPTION 1740 "Describes the minimal requirements for conformance to 1741 the rtcpXr MIB - NOT RECOMMENDED." 1743 MODULE -- this module 1744 MANDATORY-GROUPS { 1745 rtcpXrBaseParamGroup 1746 } 1747 ::= { rtcpXrCompliances 5 } 1749 rtcpXrBaseParamGroup OBJECT-GROUP 1750 OBJECTS { 1751 rtcpXrBaseParamCodecType, 1752 rtcpXrBaseParamCodecBitRate, 1753 rtcpXrBaseParamFrameDuration, 1754 rtcpXrBaseParamFramesPerPacket, 1755 rtcpXrBaseParamSampleRate, 1756 rtcpXrBaseParamDurationMs, 1757 rtcpXrBaseParamNetworkLossRate, 1758 rtcpXrBaseParamAvgDiscardRate, 1759 rtcpXrBaseParamBurstLossDensity, 1760 rtcpXrBaseParamBurstLenMs, 1761 rtcpXrBaseParamGapLossDensity, 1762 rtcpXrBaseParamGapLenMs, 1763 rtcpXrBaseParamAvgOWDelay, 1764 rtcpXrBaseParamAvgEndSysDelay, 1765 rtcpXrBaseParamNoiseLeveldBm, 1766 rtcpXrBaseParamSignalLeveldBm, 1767 rtcpXrBaseParamLocalRERLdB, 1768 rtcpXrBaseParamRemoteRERLdB, 1769 rtcpXrBaseParamPlcType, 1770 rtcpXrBaseParamJBuffAdaptMode, 1771 rtcpXrBaseParamJBuffAdaptRate, 1772 rtcpXrBaseParamJBuffAverageDelay, 1773 rtcpXrBaseParamJBuffMaximumDelay, 1774 rtcpXrBaseParamJBuffAbsMaxDelay, 1775 rtcpXrBaseParamJitterLevel 1776 } 1777 STATUS current 1778 DESCRIPTION 1779 "Objects used in rtcpXr VoIP Metrics MIB" 1780 ::= { rtcpXrGroups 1 } 1782 rtcpXrCallQualityGroup OBJECT-GROUP 1783 OBJECTS { 1784 rtcpXrCallQualityRCQ, 1785 rtcpXrCallQualityRLQ, 1786 rtcpXrCallQualityExternalRCQ, 1787 rtcpXrCallQualityMOSCQ, 1788 rtcpXrCallQualityMOSLQ, 1789 rtcpXrCallQualityRLQestAlgorithm, 1790 rtcpXrCallQualityRCQestAlgorithm, 1791 rtcpXrCallQualityMOSLQEstAlgorithm, 1792 rtcpXrCallQualityMOSCQEstAlgorithm 1793 } 1794 STATUS current 1795 DESCRIPTION 1796 "Call quality objects used in rtcpXr VoIP Metrics MIB" 1797 ::= { rtcpXrGroups 2 } 1799 rtcpXrMIBHistoryGroup OBJECT-GROUP 1800 OBJECTS { 1801 rtcpXrHistoryGroupName, 1802 rtcpXrHistoryStartTime, 1803 rtcpXrHistoryStopTime, 1804 rtcpXrHistoryNumOfSessions, 1805 rtcpXrHistoryMinDurationMs, 1806 rtcpXrHistoryMaxDurationMs, 1807 rtcpXrHistoryAvgDurationMs, 1808 rtcpXrHistoryMaxNetworkLossRate, 1809 rtcpXrHistoryAvgNetworkLossRate, 1810 rtcpXrHistoryMaxDiscardRate, 1811 rtcpXrHistoryAvgDiscardRate, 1812 rtcpXrHistoryMaxBurstLossDensity, 1813 rtcpXrHistoryAvgBurstLossDensity, 1814 rtcpXrHistoryMinBurstLenMs, 1815 rtcpXrHistoryMaxBurstLenMs, 1816 rtcpXrHistoryAvgBurstLenMs, 1817 rtcpXrHistoryMaxGapLossDensity, 1818 rtcpXrHistoryAvgGapLossDensity, 1819 rtcpXrHistoryMinGapLenMs, 1820 rtcpXrHistoryMaxGapLenMs, 1821 rtcpXrHistoryAvgGapLenMs, 1822 rtcpXrHistoryMinOneWayDelay, 1823 rtcpXrHistoryMaxOneWayDelay, 1824 rtcpXrHistoryAvgOneWayDelay, 1825 rtcpXrHistoryOneWayDelayCount, 1826 rtcpXrHistoryMinEndSystemDelay, 1827 rtcpXrHistoryMaxEndSystemDelay, 1828 rtcpXrHistoryAvgEndSystemDelay, 1829 rtcpXrHistoryEndSystemDelayCount, 1830 rtcpXrHistoryAvgJitterLevel, 1831 rtcpXrHistoryMinJitterLevel, 1832 rtcpXrHistoryMaxJitterLevel, 1833 rtcpXrHistoryMinNoiseLeveldBm, 1834 rtcpXrHistoryMaxNoiseLeveldBm, 1835 rtcpXrHistoryAvgNoiseLeveldBm, 1836 rtcpXrHistoryNoiseLevelCount, 1837 rtcpXrHistoryMinSignalLeveldBm, 1838 rtcpXrHistoryMaxSignalLeveldBm, 1839 rtcpXrHistoryAvgSignalLeveldBm, 1840 rtcpXrHistorySignalLevelCount, 1841 rtcpXrHistoryMinLocalRERLdB, 1842 rtcpXrHistoryMaxLocalRERLdB, 1843 rtcpXrHistoryAvgLocalRERLdB, 1844 rtcpXrHistoryLocalRERLCount, 1845 rtcpXrHistoryMinRemoteRERLdB, 1846 rtcpXrHistoryMaxRemoteRERLdB, 1847 rtcpXrHistoryAvgRemoteRERLdB, 1848 rtcpXrHistoryRemoteRERLCount, 1849 rtcpXrHistoryMinRCQ, 1850 rtcpXrHistoryMaxRCQ, 1851 rtcpXrHistoryAvgRCQ, 1852 rtcpXrHistoryRCQCount, 1853 rtcpXrHistoryMinRLQ, 1854 rtcpXrHistoryMaxRLQ, 1855 rtcpXrHistoryAvgRLQ, 1856 rtcpXrHistoryRLQCount, 1857 rtcpXrHistoryMinMOSCQ, 1858 rtcpXrHistoryMaxMOSCQ, 1859 rtcpXrHistoryAvgMOSCQ, 1860 rtcpXrHistoryMOSCQCount, 1861 rtcpXrHistoryMinMOSLQ, 1862 rtcpXrHistoryMaxMOSLQ, 1863 rtcpXrHistoryAvgMOSLQ, 1864 rtcpXrHistoryMOSLQCount, 1865 rtcpXrHistoryCQAlgorithm, 1866 rtcpXrHistoryReset 1867 } 1868 STATUS current 1869 DESCRIPTION 1870 "Objects used in rtcpXr VoIP History MIB" 1871 ::= { rtcpXrGroups 3 } 1873 rtcpXrNotificationParmsGroup OBJECT-GROUP 1874 OBJECTS { 1875 rtcpXrVoipAlertSeverity, 1876 rtcpXrVoipAlertType, 1877 rtcpXrVoipAlertInfoType, 1878 rtcpXrVoipAlertPointer 1879 } 1880 STATUS current 1881 DESCRIPTION 1882 "Notification parameters emitted by a rtcpXr endpoint." 1883 ::= { rtcpXrGroups 4 } 1885 rtcpXrNotificationsGroup NOTIFICATION-GROUP 1886 NOTIFICATIONS { 1887 rtcpXrVoipThresholdViolation 1888 } 1889 STATUS current 1890 DESCRIPTION 1891 "Notifications emitted by a rtcpXr endpoint." 1892 ::= { rtcpXrGroups 5 } 1894 END 1896 4. Security Considerations 1898 Access to rtcpXrHistoryReset can result in resetting the table of 1899 aggregate call quality information, which results in the loss of 1900 useful management data. 1902 It is thus important to control even GET and/or NOTIFY access to 1903 these objects and possibly to even encrypt their values when sending 1904 them over the network via SNMP. 1906 SNMP versions prior to SNMPv3 did not include adequate security. 1907 Even if the network itself is secure (for example by using IPSec), 1908 even then, there is no control as to who on the secure network is 1909 allowed to access and GET/SET (read/change/create/delete) the objects 1910 in this MIB module. 1912 It is RECOMMENDED that implementers consider the security features as 1913 provided by the SNMPv3 framework (see [RFC3410], section 8), 1914 including full support for the SNMPv3 cryptographic mechanisms (for 1915 authentication and privacy). 1917 Further, deployment of SNMP versions prior to SNMPv3 is NOT 1918 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 1919 enable cryptographic security. It is then a customer/operator 1920 responsibility to ensure that the SNMP entity giving access to an 1921 instance of this MIB module is properly configured to give access to 1922 the objects only to those principals (users) that have legitimate 1923 rights to indeed GET or SET (change/create/delete) them. 1925 5. IANA Considerations 1927 An OID within the mib-2 tree is requested, following which this note 1928 may be deleted. 1930 6. Acknowledgements 1932 The authors would like to acknowledge the input and advice provided 1933 by Dan Romascanu, Rajesh Kumar Kim Curran, Shane Holthaus and Brian 1934 Park. 1936 7. Intellectual Property 1938 The IETF takes no position regarding the validity or scope of any 1939 Intellectual Property Rights or other rights that might be claimed to 1940 pertain to the implementation or use of the technology described in 1941 this document or the extent to which any license under such rights 1942 might or might not be available; nor does it represent that it has 1943 made any independent effort to identify any such rights. Information 1944 on the procedures with respect to rights in RFC documents can be 1945 found in BCP 78 and BCP 79. 1947 Copies of IPR disclosures made to the IETF Secretariat and any 1948 assurances of licenses to be made available, or the result of an 1949 attempt made to obtain a general license or permission for the use of 1950 such proprietary rights by implementers or users of this 1951 specification can be obtained from the IETF on-line IPR repository at 1952 http://www.ietf.org/ipr. 1954 The IETF invites any interested party to bring to its attention any 1955 copyrights, patents or patent applications, or other proprietary 1956 rights that may cover technology that may be required to implement 1957 this standard. Please address the information to the IETF at 1958 ietf-ipr@ietf.org. 1960 8. Normative References 1962 [RFC3550] Shulzrinne, H., Casner, S., Frederick, R. and V. 1963 Jacobson, "RTP: A Transport Protocol for real-time 1964 applications," RFC 3550, July 2003. 1966 [RFC3611] Friedman, T., Caceres, R., Clark, A., "RTP Control 1967 Protocol Reporting Extensions (RTCP XR)," RFC 3611, 1968 [October/November] 2003 1970 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1971 Rose, M. and S. Waldbusser, "Structure of Management 1972 Information Version 2", STD 58, RFC 2578, December 1999. 1974 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1975 Rose, M. and S. Waldbusser, "Textual Conventions for 1976 SMIv2", STD 58, RFC 2579, December 1999. 1978 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1979 Rose, M. and S. Waldbusser, "Conformance Statements for 1980 SMIv2", STD 58, RFC 2580, December 1999. 1982 9. Informative References 1984 [RFC3410] Case, J., Mundy, R., Partain, D. and Stewart, B., 1985 "Introduction and Applicability Statements for Internet 1986 Standard Management Framework", RFC 3410, December 2002 1988 [RAQMON] Siddiqui, A., Romascanu, D., 1989 draft-ietf-rmonmib-framework-16.txt 1991 8. Authors' Addresses 1993 Alan Clark 1994 Telchemy Incorporated 1995 2905 Premiere Parkway, Suite 280 1996 Duluth, Georgia 30097 1997 U.S.A. 1999 Email: alan@telchemy.com 2001 Amy Pendleton 2002 Nortel 2003 2380 Performance Drive 2004 Richardson, Texas 75081 2005 U.S.A. 2007 Email: aspen@nortel.com 2009 9. Full Copyright Statement 2011 Copyright (C) The Internet Society (2006). This document is subject 2012 to the rights, licenses and restrictions contained in BCP 78, and 2013 except as set forth therein, the authors retain all their rights. 2015 This document and translations of it may be copied and furnished to 2016 others, and derivative works that comment on or otherwise explain it 2017 or assist in its implementation may be prepared, copied, published 2018 and distributed, in whole or in part, without restriction of any 2019 kind, provided that the above copyright notice and this paragraph are 2020 included on all such copies and derivative works. However, this 2021 document itself may not be modified in any way, such as by removing 2022 the copyright notice or references to the Internet Society or other 2023 Internet organizations, except as needed for the purpose of 2024 developing Internet standards in which case the procedures for 2025 copyrights defined in the Internet Standards process must be 2026 followed, or as required to translate it into languages other than 2027 English. 2029 The limited permissions granted above are perpetual and will not be 2030 revoked by the Internet Society or its successors or assigns. 2032 This document and the information contained herein are provided on 2033 an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE 2034 REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE 2035 INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR 2036 IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 2037 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 2038 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.