Test voice quality from E1 to E2, with G711, G729, AMR codecs.

Voice Media stream is generated in one direction and key transport metrics are validated. At the same time a Mean Opinion Score is computed to validate the transport quality.

• One way delay (ms)
• jitter (ms)
• jitter max (ms)
• packet loss (%)
• voice MOS score on path
• packet loss burst

If test result pair cannot be collected: Check that your E2 endpoint can open 10115 port toward E1 for management (this is needed for stream pairs). Check that synchronization port between pairs is opened (management UDP 10115). Check that port in use is in range (see "preferences/Test Controller/Destination Port Conf Option" and "preferences/Test Controller/First Destination Port" so that correct destination port for test traffic is used.

If results cannot be collected (some pairs failures complete error): Check that your E2 endpoint can open 10115 port toward E1 for management (this is needed for stream pairs).

Check that port for traffic is opened (no firewall).

Check that synchronization port between pairs is opened (management UDP 10115). Check that port in use is in range (see "preferences/Test Controller/Destination Port Conf Option" and "preferences/Test Controller/First Destination Port" so that correct destination port for test traffic is used.

Test voice quality from E1 to E2 AND E2 to E1, with G711, G729, AMR codecs.

Metrics are gathered by direction.

This reproduces a realistic voice media call.

See Voice from-> to.

Test voice quality from E1 to E2, with G711, G729, AMR codecs, with N calls simultaneously.

Voice Media stream is generated in one direction and key transport metrics are validated. At the same time a Mean Opinion Score is computed to validate the transport quality.

This test is performed for N calls.

Aggregated over the N pairs:

• One way delay (ms)
• jitter (ms)
• jitter max (ms)
• packet loss (%)
• voice MOS score on path
• packet loss burst

Total Voice traffic throughput (layer 4)

If the number of pairs selected is greater than available licenses the test can be stuck in queue. Note the number of pairs is N (one pair per voice direction).

The maximum number of simultaneous pairs (N value) each individual test can perform is also controlled from an advanced setting. Only Administrator can modify this setting:

In Main Section, Max Concurrent Tests in GUI

See voice from->to for other potential issues.

Test voice quality from E1 to E2 AND E2 to E1, with G711, G729, AMR codecs.

Metrics are gathered by direction.

This reproduces a realistic voice media call.

This test does N calls.

See Voice N pairs unidirectional.

Generate a unidirectional video flow from E1 to E2. This can simulate video based on RTP/UDP flows going through the network.

• Generated bitrate
• DSCP setting

• One way delay (ms)
• jitter (ms)
• jitter max (ms)
• packet loss (%)
• max loss burst
• video MDI scores (Media Delivery Index, Delay Factor)

Multicast Flow. Emulates the standard streaming video codec. Measures video metrics. The client is the “From” endpoint and the server is the “To” endpoint.

Generate a multicast video flows from E1 to (E2…..EN). Where N the number of endpoints supported in the Mesh. This can simulate video based on RTP/UDP flows going through the network.

Test duration , Test bit rate (Mbps), DSCP Setting, Multicast Address: Port Video from->to.

• Datagrams Out of Order
• Delay (ms)
• Jitter (ms)
• Jitter Max (ms)
• Loss
• Max loss burst
• Source and destination ports
• Throughput Video (Mbps)
• Total Bytes Lost Video
• MDI Delay Factor (Media Delivery Index, Factor)
• Video MDI Media Loss Rate (Media Delivery Index, Loss Rate)

This test allows generating video rtp streams - bitrate will define corresponding codec (HD or SD).

This test generate Video stream on the selected path. It can be optimized with setting up send low jitter in the preferences to be 1 if the endpoints support it.

If test result pair cannot be collected:

• Ensure that your E2 endpoint can open 10115 port toward E1 for management (this is needed for stream pairs).
• Ensure that synchronization port between pairs is opened (management UDP 10115).
• Ensure that the port in use is in range. See "preferences/Test Controller/Destination Port Conf Option" and "preferences/Test Controller/First Destination Port" so that correct destination port for test traffic is used.

In the case of this video streaming technique, the video is encoded on a server at several bitrates and divided into video segments of 2 to 10 seconds.

The client first learns the available bitrates by downloading a video manifest, then starts requesting video segments from the server at a specific bitrate. The client starts requesting video segments at a medium bitrate, but this can be changed by altering the Starting Bitrate parameter of any Adaptive Video over HTTP flows.

Depending on the network bandwidth and the local speed of video decoding and rendering, the client can decide to increase (upshift) or decrease (downshift) the requested bitrate for future video segments as compared to that requested for the previous video segments.

• Avg Video Playback Rate (bps)
• Avg Video Pre-buffering duration (ms)
• Jitter Buffer Full Count
• Jitter Buffer Full Duration (ms)
• Throughput from->to (Mbps)
• Video Playback Downshifts
• Video Playback Upshifts
• Video Quality Segments - Very High
• Video Quality Segments - High
• Video Quality Segments – Medium
• Video Quality Segments - Low
• Video Quality Segments - Very Low
• Video Stopped Count
• Video Stopped Duration (ms)

Upshifting provides better video quality, but at a greater risk of playback interruptions, while downshifting increases playback smoothness at the expense of video quality.

Through its adapting capability, this video streaming technique provides the best trade-off between video quality and smooth video streaming.

Where no jitter buffer is used (there are no video download limitations), the video is downloaded at the maximum speed allowed by network conditions. This means that there are no pauses between GET requests.

One in which the jitter buffer is used and as such, the download of the video segments is paused when the buffer becomes full. On average, the throughput will not exceed the maximum video bitrate.

Video Playback Downshift is a decrease in the requested bit rate for future video segments as compared to that requested for the previous video segments. Video Playback Upshift is an increase in the requested bit rate for future video segments as compared to that requested for the previous video segments.

Video quality segments indicate the distribution of video playback quality Video stopped count and duration indicate the video playback interruptions and its duration.

If test result pair cannot be collected:

• Ensure that your E2 endpoint can open 10115 port toward E1 for management (this is needed for stream pairs).
• Ensure that synchronization port between pairs is opened (management UDP 10115).
• Ensure that port in use is in range. See "preferences/Test Controller/Destination Port Conf Option" and "preferences/Test Controller/First Destination Port" so that correct destination port for test traffic is used.

In the case of this video streaming technique, the video is encoded on a server at several bitrates and divided into video segments of 2 to 10 seconds. The client first learns the available bitrates by downloading a video manifest, then starts requesting video segments from the server at a specific bitrate.

The client starts requesting video segments at a medium bitrate, but this can be changed by altering the Starting Bitrate parameter of any Adaptive Video over HTTP flows. Depending on the network bandwidth and the local speed of video decoding and rendering, the client can decide to increase (upshift) or decrease (downshift) the requested bitrate for future video segments as compared to that requested for the previous video segments.

Additionally this also tests the Network KPI along with video streaming on both directions : it adds a bidirectional very low footprint packet heartbeat to measure the network kpis (loss/delay/jitter) on the segment.

• Avg Video Playback Rate (bps)
• Avg Video Pre-buffering duration (ms)
• Jitter Buffer Full Count
• Jitter Buffer Full Duration (ms)
• Throughput from->to (Mbps)
• Video Playback Downshifts
• Video Playback Upshifts
• Video Stopped Count
• Video Stopped Duration (ms)

Network KPI Metric:

• Delay (Ms):
• Jitter (Ms):
• Jitter Max (Ms):
• Loss:

Upshifting provides better video quality, but at a greater risk of playback interruptions, while downshifting increases playback smoothness at the expense of video quality.

Through its adapting capability, this video streaming technique provides the best trade-off between video quality and smooth video streaming.

This test is realistic and since jitter buffer is used and as such, the download of the video segments is paused when the buffer becomes full. On average, the throughput will not exceed the maximum video bitrate.

Video Playback Downshift is a decrease in the requested bit rate for future video segments as compared to that requested for the previous video segments. Video Playback Upshift is an increase in the requested bit rate for future video segments as compared to that requested for the previous video segments.

Video quality segments indicate the distribution of video playback quality Video stopped count and duration indicate the video playback interruptions and its duration.

Video Stopped Count Video Stopped Duration will tell for any user experience having video stalling during the watch.

The number of Downshift and Upshifts indicate how often the adaptive rate needed to change: lots of changes indicate an instable network condition.

The Avg Playback rate will indicate the overall video quality experience: high rate will mean the high quality segments could be transported, lower rates mean the video had to adapt to lower quality segments.

This test can only work from public->public, private->private and private->public. It is NOT supported for public->private direction.

If test result pair cannot be collected:

• Ensure that port in use is in range. See "preferences/Test Controller/Destination Port Conf Option" and "preferences/Test Controller/First Destination Port" so that correct destination port for test traffic is used.

In the case of this video streaming technique, the video is encoded on a server at several bitrates and divided into video segments of 2 to 10 seconds.

The client first learns the available bitrates by downloading a video manifest, then starts requesting video segments from the server at a specific bitrate.

The client starts requesting video segments at a medium bitrate, but this can be changed by altering the Starting Bitrate parameter of any Adaptive Video over HTTP flows.

Depending on the network bandwidth and the local speed of video decoding and rendering, the client can decide to increase (upshift) or decrease (downshift) the requested bitrate for future video segments as compared to that requested for the previous video segments.

Additionally this also tests the Network KPI along with video streaming.

• Avg Video Playback Rate (bps)
• Avg Video Pre-buffering duration (ms)
• Jitter Buffer Full Count
• Jitter Buffer Full Duration (ms)
• Throughput from->to (Mbps)
• Video Playback Downshifts
• Video Playback Upshifts
• Video Stopped Count
• Video Stopped Duration (ms)

Upshifting provides better video quality, but at a greater risk of playback interruptions, while downshifting increases playback smoothness at the expense of video quality.

Through its adapting capability, this video streaming technique provides the best trade-off between video quality and smooth video streaming.

The download of the video segments is paused when the buffer becomes full. On average, the throughput will not exceed the maximum video bitrate.

Video Playback Downshift is a decrease in the requested bit rate for future video segments as compared to that requested for the previous video segments. Video Playback Upshift is an increase in the requested bit rate for future video segments as compared to that requested for the previous video segments.

Video quality segments indicate the distribution of video playback quality Video stopped count and duration indicate the video playback interruptions and its duration.

Video Stopped Count Video Stopped Duration will tell for any user experience having video stalling during the watch.

The number of Downshift and Upshifts indicate how often the adaptive rate needed to change: lots of changes indicate an instable network condition.

The Avg Playback rate will indicate the overall video quality experience: high rate will mean the high quality segments could be transported, lower rates mean the video had to adapt to lower quality segments.

This test can only work from public->public, private->private and private->public. It is NOT supported for public->private direction

If test result pair cannot be collected:

• Ensure that port in use is in range. See "preferences/Test Controller/Destination Port Conf Option" and "preferences/Test Controller/First Destination Port" so that correct destination port for test traffic is used.

In the case of this video streaming technique, the video is encoded on a server at several bitrates and divided into video segments of 2 to 10 seconds.

The client first learns the available bitrates by downloading a video manifest, then starts requesting video segments from the server at a specific bitrate.

The client starts requesting video segments at a medium bitrate, but this can be changed by altering the Starting Bitrate parameter of any Adaptive Video over HTTP flows.

Depending on the network bandwidth and the local speed of video decoding and rendering, the client can decide to increase (upshift) or decrease (downshift) the requested bitrate for future video segments as compared to that requested for the previous video segments. Additionally this also tests the Network KPI along with video streaming.

• Avg Video Playback Rate (bps)
• Avg Video Pre-buffering duration (ms)
• Jitter Buffer Full Count
• Jitter Buffer Full Duration (ms)
• Throughput from->to (Mbps)
• Video Playback Downshifts
• Video Playback Upshifts
• Video Stopped Count
• Video Stopped Duration (ms)

Upshifting provides better video quality, but at a greater risk of playback interruptions, while downshifting increases playback smoothness at the expense of video quality.

Through its adapting capability, this video streaming technique provides the best trade-off between video quality and smooth video streaming.

Where no jitter buffer is used (there are no video download limitations), the video is downloaded at the maximum speed allowed by network conditions. This means that there are no pauses between GET requests.

One in which the jitter buffer is used and as such, the download of the video segments is paused when the buffer becomes full. On average, the throughput will not exceed the maximum video bitrate. Video Playback Downshift is a decrease in the requested bit rate for future video segments as compared to that requested for the previous video segments.

Video Playback Upshift is an increase in the requested bit rate for future video segments as compared to that requested for the previous video segments. Video quality segments indicate the distribution of video playback quality Video stopped count and duration indicate the video playback interruptions and its duration.

Video Stopped Count Video Stopped Duration will tell for any user experience having video stalling during the watch. The number of Downshift and Upshifts indicate how often the adaptive rate needed to change: lots of changes indicate an instable network condition. The Avg Playback rate will indicate the overall video quality experience: high rate will mean the high quality segments could be transported, lower rates mean the video had to adapt to lower quality segments.

This test can only work from public->public, private->private and private->public. It is NOT supported for public->private direction.

If test result pair cannot be collected:

• Ensure that port in use is in range. See "preferences/Test Controller/Destination Port Conf Option" and "preferences/Test Controller/First Destination Port" so that correct destination port for test traffic is used.

In the case of this video streaming technique, the video is encoded on a server at several bitrates and divided into video segments of 2 to 10 seconds. The client first learns the available bitrates by downloading a video manifest, then starts requesting video segments from the server at a specific bitrate.

The client starts requesting video segments at a medium bitrate, but this can be changed by altering the Starting Bitrate parameter of any Adaptive Video over HTTP flows.

Depending on the network bandwidth and the local speed of video decoding and rendering, the client can decide to increase (upshift) or decrease (downshift) the requested bitrate for future video segments as compared to that requested for the previous video segments. Additionally this also tests the Network KPI along with video streaming.

• Avg Video Playback Rate (bps)
• Avg Video Pre-buffering duration (ms)
• Jitter Buffer Full Count
• Jitter Buffer Full Duration (ms)
• Throughput from->to (Mbps)
• Video Playback Downshifts
• Video Playback Upshifts
• Video Stopped Count
• Video Stopped Duration (ms)

Upshifting provides better video quality, but at a greater risk of playback interruptions, while downshifting increases playback smoothness at the expense of video quality.

Through its adapting capability, this video streaming technique provides the best trade-off between video quality and smooth video streaming.

Where no jitter buffer is used (there are no video download limitations), the video is downloaded at the maximum speed allowed by network conditions. This means that there are no pauses between GET requests. One in which the jitter buffer is used and as such, the download of the video segments is paused when the buffer becomes full. On average, the throughput will not exceed the maximum video bitrate.

Video Playback Downshift is a decrease in the requested bit rate for future video segments as compared to that requested for the previous video segments. Video Playback Upshift is an increase in the requested bit rate for future video segments as compared to that requested for the previous video segments.

Video quality segments indicate the distribution of video playback quality Video stopped count and duration indicate the video playback interruptions and its duration.

Video Stopped Count Video Stopped Duration will tell for any user experience having video stalling during the watch.

The number of Downshift and Upshifts indicate how often the adaptive rate needed to change: lots of changes indicate an instable network condition.

The Avg Playback rate will indicate the overall video quality experience: high rate will mean the high quality segments could be transported, lower rates mean the video had to adapt to lower quality segments.

This test can only work from public->public, private->private and private->public. It is NOT supported for public->private direction.

If test result pair cannot be collected:

• Ensure that port in use is in range. See "preferences/Test Controller/Destination Port Conf Option" and "preferences/Test Controller/First Destination Port" so that correct destination port for test traffic is used.