No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

CloudEC V600R019C00 Troubleshooting (Enterprise On-premises, Convergent Conference)

Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Low Video Definition/Smoothness

Low Video Definition/Smoothness

Symptoms and Possible Causes

Symptoms: In a multi-party conference or P2P call, the definition or smoothness of other participants' video viewed by the local participant is low.

Exceptions of the endpoints, transmission network, or media processing devices may cause low video definition or smoothness. Common root causes are as follows:

[Endpoint problems]: The sending frame rate of the endpoint is low. The sending resolution of the endpoint is low. Bandwidth reduction of the recipient endpoint causes poor video quality.

[Transmission network faults]: I frames are frequently encoded due to bandwidth restrictions or packet loss on the transmission network, causing poor video quality.

[Media processing device faults]: Frequent I frame encoding or forcible adaptation of the MCU causes poor video quality of the recipient.

Processing Idea

The processing idea of low video definition or smoothness is as follows: Analyze the fault cause stage by stage from the pickup party's endpoint in the reverse direction of media processing based on the counter data collected in the SessionInsight until the fault cause is detected.

Diagnosis

Figure 1-46 Low Video Definition/Smoothness
P1, Definition or Smoothness of Other Participants' Video Viewed by the Local Participant Is Low

[Determination rule]

The definition or smoothness of other participants' video is low. The receiving frame rate, decoding frame rate, and decoding resolution in the receiving direction of the local participant are used for determination. If the video receiving resolution or frame rate of the recipient is low due to network, SBC, or MCU exceptions or the resolution or frame rate does not decrease obviously but the user feeds back that the video definition is low, you can determine that the definition or smoothness of other participants' video is low. The counter data indicates that the video decoding frame rate, video resolution, or video bit rate of the recipient is low.

For details about how to determine the fault cause, see P2, Improper Conference Template Settings Cause Poor Video Quality to P5, Bandwidth Reduction of the Recipient Endpoint Causes Poor Quality.

P2, Improper Conference Template Settings Cause Poor Video Quality

[Determination rule]

The definition or smoothness of other participants' video is low. The sending frame rate, encoding frame rate, and encoding resolution in the sending direction of the local participant are used for determination. When the conference template is improperly configured, the resolution or bit rate of the video encoded and sent by the endpoint may be too low.

[Example]

As shown in Figure 1-47, select Collection, Coding and Output Width(Collection), Output Height(Collection), Output Width(Coding), Output Height(Coding) for Counter sending settings to display statistics about the encoding resolution of the endpoint's video sending module. In the fault period, the resolution is less than VGA (640x480), indicating that the definition of the decoded image is low. In this case, if the network condition is good and no packet is lost, you need to check whether the poor video quality is caused by the low resolution or bit rate setting in the conference template.

Figure 1-47 Counters indicating the endpoint's video encoding resolution
P3, The MCU Frequently Sends I Frames, Causing Poor Video Quality

[Determination rule]

The definition or smoothness of other participants' video is low. The receiving frame rate, decoding frame rate, and number of decoded I frames in the receiving direction of the local participant are used for determination. When the MCU frequently sends I frames, the quality of the video received by the endpoint may be poor.

[Example]

As shown in Figure 1-48, select Network sending, Coding and I Frame Reqs(Coding) for Counter sending settings to display statistics about the number of I frame requests to the video encoding module of the MCU. Then, you can detect that the number of I frame requests increases continuously and the number of I frames of video encoded by the MCU increases continuously (not displayed in the figure) in the fault period. In addition, as shown in Figure 1-49, select Decoding, Network receiving and Decode Frame Rate(Decoding), Net Lost Packets(Network receiving), Receive Frame Rate(Decoding), Receive I Frames(Decoding) for Counter receiving settings to display statistics about the receiving frame rate and decoding frame rate of the endpoint. Then, you can detect that the decoding frame rate decreases and the number of lost packets and number of decoded I frames increase continuously, indicating that the MCU frequently sends I frames because of network packet loss.

Figure 1-48 Counter indicating the number of I frame requests to the video encoding module of the MCU
Figure 1-49 Counters indicating the video decoding frame rate & receiving frame rate of the endpoint
P4, Forcible Adaptation of the MCU Causes Poor Quality

[Determination rule]

The definition or smoothness of other participants' video is low. The receiving frame rate, decoding frame rate, and decoding resolution in the receiving direction of the local participant are used for determination. When the MCU performs forcible adaptation, the endpoint receiving resolution may be low, causing poor video quality.

[Example]

As shown in Figure 1-50, select Network sending, Coding and Output Width(Coding), Output Height(Coding), Set Bandwidth(Coding), Bytes(Network sending) for Counter sending settings to display statistics about the video encoding module's resolution of the MCU. Then, you can detect that the encoding resolution decreases from 1920x1080 to 1280x720 due to forcible adaptation of the MCU in the fault period. As shown in Figure 1-51, select Decoding, Network receiving and Width(Decoding), Height(Decoding), Bytes(Network receiving) for Counter receiving settings to display statistics about the decoding resolution and bit rate of the endpoint. Then, you can detect that the decoding resolution decreases from 1920x1080 to 1280x720 and the corresponding bit rate (Bytes(Network receiving)) increases slowly, indicating that the video quality in the period deteriorates.

Figure 1-50 Counters indicating the MCU video encoding resolution
Figure 1-51 Counters indicating the endpoint's video decoding resolution
P5, Bandwidth Reduction of the Recipient Endpoint Causes Poor Quality

[Determination rule]

The definition or smoothness of other participants' video is low. The encoding bandwidth and encoding resolution in the sending direction of the local participant's MCU are used for determination. When the recipient endpoint sends bandwidth reduction feedback to the MCU due to network restrictions, the resolution or bit rate of video encoded and sent by the MCU may be too low.

[Example]

As shown in Figure 1-52, select Network sending, Coding and Output Width(Coding), Output Height(Coding), Set Bandwidth(Coding), Bytes(Network sending) for Counter sending settings to display statistics about the video module's encoding resolution and bandwidth of the MCU. Then, you can detect that the resolution in the fault period decreases from 1080p to 720p, indicating that the encoded video definition is low. However, the network condition is good and no packet is lost. In this case, when the MCU sending bandwidth reduces, you need to check the bandwidth feedback received by the MCU and determine whether bandwidth reduction of the recipient endpoint causes poor video quality.

Figure 1-52 Counters indicating the MCU video encoding resolution
P6, Definition or Smoothness of the Local Participant's Video Is Low

[Determination rule]

The definition or smoothness of the local participant's video is low. The receiving frame rate, decoding frame rate, and decoding resolution in the receiving direction of the local participant in the MCU are used for determination. If the resolution or frame rate of video received by the recipient is low due to endpoint or network exceptions or the resolution or frame rate does not decrease obviously but users feed back that the video definition is low, you can determine that the definition or smoothness of the local participant's video is low. The counter data indicates that the video decoding frame rate, video resolution, or video bit rate of the corresponding participant in the MCU is low.

For details about how to determine the fault cause, see P7, The Sending Frame Rate of the Endpoint Is Low to P9, The Endpoint Frequently Sends I Frames.

P7, The Sending Frame Rate of the Endpoint Is Low

[Determination rule]

The definition or smoothness of the local participant's video is low. The encoding and sending frame rates and resolutions of the local participant are used for determination. When the endpoint's sending frame rate is low, the counter data indicates that both the encoding frame rate of the endpoint and the decoding frame rate of the MCU are too low.

[Example]

As shown in Figure 1-53, select Collection, Coding and Send Frames(Coding) for Counter sending settings to display statistics about the number of video frames sent by the endpoint. Then, you can detect that the number of frames is 363 when the session lasts for 2 minutes in the fault period. The frame rate is calculated as follows: 363/(2 x 60) = 3 fps. That is, the sending frame rate is 3 fps. As shown in Figure 1-54, the receiving and decoding frame rates of the MCU are also low, indicating that the sending frame rate of the source end is low. Therefore, the smoothness of the local participant's video is low.

Figure 1-53 Counter indicating the number of frames of video encoded and sent by the endpoint
Figure 1-54 Counters indicating the video decoding frame rate & receiving frame rate of the MCU
P8, The Sending Resolution of the Endpoint Is Low

[Determination rule]

The definition or smoothness of the local participant's video is low. The encoding and sending frame rates and resolutions of the local participant are used for determination. When the endpoint's sending resolution is low, the counter data indicates that both the encoding resolution of the endpoint and decoding resolution of the MCU are too low.

[Example]

As shown in Figure 1-55, select Collection, Coding and Output Width(Collection), Output Height(Collection), Output Width(Coding), Output Height(Coding) for Counter sending settings to display statistics about the video collection and encoding resolutions of the endpoint. Then, you can detect that the endpoint's collection and encoding resolutions are 416x224 in the fault period, indicating that the sending resolution of the source end is low and the decoding resolution of the MCU decreases. Therefore, the definition of the local participant's video is low.

Figure 1-55 Counters indicating the endpoint's video encoding resolution
P9, The Endpoint Frequently Sends I Frames

[Determination rule]

The definition or smoothness of the local participant's video is low. The encoding and sending frame rates and resolutions and the number of sent I frames of the local participant are used for determination. When the endpoint frequently sends I frames, the definition or smoothness of the local participant's video may be low.

[Example]

As shown in Figure 1-56, select Coding and I Frames(Coding) for Counter sending settings to display statistics about the number of I frames of video encoded by the endpoint. Then, you can detect that the number of I frames increases continuously in the fault period. In addition, as shown in Figure 1-57, the number of I frames received and decoded by the MCU increases continuously and the decoding frame rate (Decode Frame Rate(Decoding)) decreases, indicating that video smoothness is low because the endpoint frequently sends I frames.

Figure 1-56 Counter indicating the number of I frames of video encoded by the endpoint
Figure 1-57 Counters indicating the MCU video receiving frame rate & the decoding frame rate
Translation
Download
Updated: 2019-08-07

Document ID: EDOC1100059098

Views: 22143

Downloads: 12

Average rating:
This Document Applies to these Products
Related Version
Related Documents
Share
Previous Next