Incremental QoS Updates
The Interim Quality of Service (QoS) Update setting provides a more granular view of voice quality for troubleshooting by providing updates in 10 second increments. Without the Interim QoS Update setting selected, the Oracle® Enterprise Session Border Controller (ESBC) probe provides an average Mean Opinion Score (MOS) only at the end of the call. A troubleshooter cannot see what occurred in other parts of the call. For example, suppose your employee or agent complains of poor voice quality that occurred in the middle of the call, but the average MOS score at the end of the call is 4.40. The troubleshooter might determine that the quality is acceptable, without knowing that the score in the middle of the call is 2.50. The Interim QoS Update setting provides MOS scores every 10 seconds, and with more granular data to help troubleshooting efforts.
Standalone Oracle Communications Operations Monitor (OCOM) probes, such as those that run OCOM software on Linux COTS servers, provide MOS scores in 10 second time chunks. With the Interim QoS Update parameter enabled, the data presented in OCOM looks similar whether coming from an ESBC probe, OCOM probe, or both. To set voice quality sampling in 10 second increments, go to system-config, comm-monitor and enable interim-qos-update.
The ESBC provides the following data, per ten second interval.
- start + end time of the stream
- IP 5-tuple information to correlate to SIP sessions
- correlation information if available
- SSRC of the RTP stream (to be checked)
- Codec type
- Codec change information (if codecs changed)
The ESBC provides the following data, per ten second chunk.
- jitter
- min/avg/max
- packet loss
- # of packets received
- # of packets lost
- Per RTP stream.
- In 10 second increments, where the increment starts on a full minute based on the NTP clock (not the start time of the stream).
- Intervals not covering the full 10 seconds do not return a MOS value.
Note:
The comm-monitor VQ reports do not support disabling latching for a stream because the SBC does not have access to the stream source IP address. Latching may be globally disabled via the media-manager object or, dynamically disabled even when globally enabled in media-manager, for example, when a media for a session has been successfully negotiated but the source of the media flow changes.