Skip to content

Commit fcdcee4

Browse files
committed
Update delay-issue.md
1 parent 2c85973 commit fcdcee4

File tree

1 file changed

+1
-1
lines changed
  • articles/communication-services/resources/troubleshooting/voice-video-calling/audio-issues

1 file changed

+1
-1
lines changed

articles/communication-services/resources/troubleshooting/voice-video-calling/audio-issues/delay-issue.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ For the network quality of the receiving end, check UFD events with the values o
3636
In addition, you can use the [Media Stats API](../../../../concepts/voice-video-calling/media-quality-sdk.md) to monitor and track real-time network performance from the Web client.
3737
There are two metrics related to the audio delay: `rttInMs` and `jitterBufferDelayInMs`.
3838

39-
The [rttInMs](../../../../concepts/voice-video-calling/media-quality-sdk.md?pivots=platform-web#audio-send-metrics) has a direct impact on audio delay, as the metric indicates the round trip time of packets. High latency can result in perceptible delays in audio.
39+
The [rttInMs](../../../../concepts/voice-video-calling/media-quality-sdk.md?pivots=platform-web#audio-send-metrics) has a direct impact on the audio delay, as the metric indicates the round trip time of packets. High latency can result in perceptible delays in audio.
4040
We recommend a round-trip time of 200 ms or less.
4141
If the round-trip time is larger than 500 ms, users may experience significant delays that can lead to frustration and hinder effective communication. In such cases, the conversation flow can be disrupted, making it difficult to have a smooth and natural interaction
4242

0 commit comments

Comments
 (0)