350-801 · Question #222
User A calls user B. The call gets connected, but the quality is bad. What are two reasons for this issue? (Choose two.)
The correct answer is C. Network congestion D. Incorrect QoS. When a call connects but experiences poor quality, common culprits are network issues such as congestion, which causes packet loss and delay, or improperly configured Quality of Service (QoS) that fails to prioritize voice traffic.
Question
User A calls user B. The call gets connected, but the quality is bad. What are two reasons for this issue? (Choose two.)
Options
- AIncorrect partition
- BNo region relationship
- CNetwork congestion
- DIncorrect QoS
- EIncompatible codec
How the community answered
(35 responses)- A6% (2)
- C91% (32)
- E3% (1)
Why each option
When a call connects but experiences poor quality, common culprits are network issues such as congestion, which causes packet loss and delay, or improperly configured Quality of Service (QoS) that fails to prioritize voice traffic.
An incorrect partition would prevent the call from connecting in the first place, rather than resulting in bad quality once connected.
A lack of region relationship would affect codec negotiation and bandwidth, potentially leading to no call or a different codec, but not directly causing 'bad quality' on an already connected call as definitively as congestion or incorrect QoS.
Network congestion leads to packet loss, jitter, and delay, which are primary causes of degraded voice and video call quality, manifesting as choppy audio, echoes, or dropped words.
Incorrect QoS configuration means that voice traffic is not prioritized over other network traffic. This can result in voice packets being dropped or delayed during periods of network stress, directly leading to poor call quality.
Incompatible codecs would prevent the call from connecting at all, as the endpoints would not be able to negotiate a common media format; if the call is connected, codecs are compatible.
Concept tested: Common causes of poor voice/video call quality
Source: https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/trouble/12_5_1/cucm_b_troubleshooting-guide-1251/cucm_b_troubleshooting-guide-1251_chapter_0100.html#concept_37EB0D421D835497B08034E262A86B91
Topics
Community Discussion
No community discussion yet for this question.