Documentation forVoIP & Network Quality Manager
Monitoring VoIP and network quality is a key capability of Hybrid Cloud Observability and is also available in a standalone module, VoIP & Network Quality Manager (VNQM). Hybrid Cloud Observability and VNQM are built on the self-hosted SolarWinds Platform.

Jitter in SolarWinds VNQM

Jitter is a measure of the variation in network latency that results in a loss of synchronization over time. In VoIP phone calls, users experience jitter as distracting noise, clicks, and pops. To ensure acceptable quality of service, network jitter should be located, isolated, and addressed. By using SolarWinds VoIP and Network Quality Manager you can identify areas of your network that may be experiencing synchronization difficulties, and then you can take the necessary action to ensure maximum quality of service on your VoIP network.

SolarWinds VoIP and Network Quality Manager requires you to select a jitter codec to properly configure Network Service Assurance for your VoIP network. Codecs compute jitter by specifying that Network Service Assurance operations send a number of packets (n), each with a specific size (s), at a set interval (i) between packets, at a determined frequency (f), as shown in the following table.

Codec

Network Service Assurance operation frequency (f)

Default number of packets (n)

Default packet size (s)

Default interval between packets (i)

G.711a

Set on each operation as the network test interval

1000

160 + 12 RTP bytes

20 ms

G.711u

1000

160 + 12 RTP bytes

20 ms

G.729a

1000

20 + 12 RTP bytes

20 ms

For more information about configurable settings within SolarWinds VoIP and Network Quality Manager, see Configure SolarWinds VNQM settings.

Based on the Network Service Assurance operations used by SolarWinds VoIP and Network Quality Manager, jitter codecs G.711a and G.711u can achieve a peak MOS of 4.34. On the same basis, jitter codec G.729a can achieve a peak MOS of 4.06. For information on configuring individual Network Service Assurance operations, see Add Network Service Assurance operations.

SolarWinds VoIP and Network Quality Manager calculates jitter in the following way:

MinJitterSD = milli/microseconds equivalent of Minimum(rttMonLatestJitterOperMinOfNegativesSD, rttMonLatestJitterOperMinOfPositivesSD)

MinJitterDS = milli/microseconds equivalent of Minimum(rttMonLatestJitterOperMinOfNegativesDS, rttMonLatestJitterOperMinOfPositivesDS)

AvgJitterSD = milli/microseconds equivalent of rttMonLatestJitterOperAvgSDJAvgJitterDS = milli/microseconds equivalent of rttMonLatestJitterOperAvgDSJ

AvgJitterDS = milli/microseconds equivalent of rttMonLatestJitterOperAvgDSJ

MaxJitterSD = milli/microseconds equivalent of Maximum(rttMonLatestJitterOperMaxOfNegativesSD, rttMonLatestJitterOperMaxOfPositivesSD)

MaxJitterDS = milli/microseconds equivalent of Maximum(rttMonLatestJitterOperMaxOfNegativesDS, rttMonLatestJitterOperMaxOfPositivesDS)

MinJitter = Minimum(MinJitterDS, MinJitterSD)

AvgJitter = milli/microseconds equivalent of rttMonLatestJitterOperAvgJitter

MaxJitter = Maximum(MaxJitterDS, MaxJitterSD)

rttMonLatestJitterOperMinOfNegativesSD 1.3.6.1.4.1.9.9.42.1.5.2.1.11
rttMonLatestJitterOperMinOfPositivesSD 1.3.6.1.4.1.9.9.42.1.5.2.1.6
rttMonLatestJitterOperMinOfNegativesDS 1.3.6.1.4.1.9.9.42.1.5.2.1.21
rttMonLatestJitterOperMinOfPositivesDS 1.3.6.1.4.1.9.9.42.1.5.2.1.16
rttMonLatestJitterOperAvgSDJ 1.3.6.1.4.1.9.9.42.1.5.2.1.47
rttMonLatestJitterOperAvgDSJ 1.3.6.1.4.1.9.9.42.1.5.2.1.48
rttMonLatestJitterOperMaxOfNegativesSD 1.3.6.1.4.1.9.9.42.1.5.2.1.12
rttMonLatestJitterOperMaxOfPositivesSD

1.3.6.1.4.1.9.9.42.1.5.2.1.7

rttMonLatestJitterOperMaxOfNegativesDS 1.3.6.1.4.1.9.9.42.1.5.2.1.22
rttMonLatestJitterOperMaxOfPositivesDS 1.3.6.1.4.1.9.9.42.1.5.2.1.17
rttMonLatestJitterOperAvgJitter 1.3.6.1.4.1.9.9.42.1.5.2.1.46

SolarWinds VoIP and Network Quality Manager reads one jitter value at a given time, which is calculated based on the SNMP poll. This is an average value. The CLI command is not necessarily executed at the same moment. For this reason, the output of the current CLI commands is not the same as the values displayed in the VNQM charts or in the historical data.