Prompt
How do I find out why call quality is bad for certain users
Latest observation
To find out why call quality is bad for certain users, the fastest approach is to isolate whether the problem is user-specific, device-specific, network-specific, or service-wide.
1) Identify the pattern
Check whether the bad quality happens:
- Only for specific users
- Only on certain devices (desk phone, softphone, mobile)
- Only in certain locations or networks (office, home, VPN, Wi‑Fi)
- Only during certain times
- Only with certain call directions (internal, external, inbound, outbound)
If it’s only a few users, that usually points to their network, device, headset, Wi‑Fi, or local endpoint settings.
2) Check the user’s endpoint
For affected users, verify:
- Headset / speaker / microphone quality
- Firmware and software version
- Whether the user is on Wi‑Fi vs wired Ethernet
- CPU usage and system performance
- Whether the app/phone is up to date
- Audio enhancement or Bluetooth issues
Common signs:
- Choppy audio → packet loss, jitter, poor Wi‑Fi
- Delayed audio → latency, VPN, routing issues
- Echo → speaker volume, mic/speaker placement, headset problems
- Robot voice / metallic sound → packet loss/jitter/codec issues
3) Check network quality
Look at:
- Latency
- Jitter
- Packet loss
- Bandwidth
- Wi‑Fi signal strength
- VPN usage
- Firewall or ISP issues
Typical acceptable values:
- Latency: under 150 ms one-way is ideal; under 300 ms round-trip is usually acceptable
- Jitter: under 30 ms
- Packet loss: below 1% is best; above 3% can cause noticeable issues
If users are remote, their home internet or ISP is often the culprit.
4) Review call analytics / QoS data
If your phone system or UC platform provides call records, check metrics for affected calls:
- Packet loss
- Jitter
- RTT/latency
- MOS score
- Codec used
- Call path / media relay path
- Device type and client version
Compare a bad call vs a good call from the same user to spot differences.
5) Check infrastructure
If multiple users are affected in one place, inspect:
- Switch ports
- VLAN configuration
- QoS markings/prioritization
- Wireless access points
- Internet gateway
- SBC / SBC logs
- SIP trunk or provider issues
6) Correlate with known changes
Ask whether anything changed recently:
- New headset
- Software update
- Firewall change
- Network reconfiguration
- VPN policy change
- ISP changes
- Office move or new Wi‑Fi APs
7) Reproduce the issue
If possible:
- Make a test call from the affected user’s device
- Compare on:
- same user on a different network
- different user on same device/network
- same user on a different device
This helps separate:
- user account issues
- device issues
- network issues
8) Gather exact symptoms
Ask the user:
- Is the problem on both send and receive audio?
- Is it worse on Wi‑Fi, VPN, or mobile data?
- Does it happen with all callers or specific numbers?
- Does it happen only in long calls?
- Does it occur in headset mode, speakerphone, or Bluetooth?
9) What to look for in logs/tools
Depending on your platform, check:
- Call detail records (CDRs)
- Media quality reports
- SIP logs
- Client diagnostics
- Wireshark captures if needed
- Endpoint logs
- Network monitoring tools
Quick triage checklist
For a bad-quality user, check:
- Device/headset
- Wired vs Wi‑Fi
- VPN on/off
- Packet loss/jitter/latency
- Client version and firmware
- Whether the issue reproduces on another network/device
If you want, I can help you build a step-by-step troubleshooting flow for your specific environment, like Microsoft Teams, Zoom, Cisco, Avaya, or VoIP/SIP.