- Joined
- Nov 16, 2022
- Messages
- 191
- Reaction score
- 8
I am running a 3CX V20 hosted by 3CX. Users complain that, from time to time, incoming calls sound like an echo, or they have an issue hearing the other side
I downloaded the log and uploaded it to ChatGPT to see what I am missing
The results are according to ChatGPT:
1.9 GB RAM is not enough → leads to:
Why it matters:
If you want stable audio:
Go 4 GB RAM + 4 CPU — no compromise
Step 2 — Fix NTP immediately
I downloaded the log and uploaded it to ChatGPT to see what I am missing
The results are according to ChatGPT:
- CPU: 2 cores
- RAM: 1.9 GB total (only ~700 MB free)
- Hosting: KVM VM (likely low-tier VPS)
- 3CX Version: 20.0.8
- Firewall Check: Passed

- NTP:
Not configured / missing
1. Server is underpowered (BIGGEST ISSUE)
3CX v20 + multiple concurrent calls + transcoding = your specs are too low.1.9 GB RAM is not enough → leads to:
- RTP packet delay
- Jitter → echo / robotic sound
- One-way audio intermittently
- Audio clipping
“sometimes echo”
“sometimes can’t hear other side”
2. No NTP (Time Sync) — VERY IMPORTANT
Your log shows:This is a major VoIP issue.ntpstat: The system cannot find the file specified.
Why it matters:
- RTP streams rely on timing
- Without sync → jitter buffers break
- Causes:
- Echo
- Delay
- Audio overlap
3. Likely RTP / network jitter (cloud VPS factor)
You’re on a virtualized host (KVM), which introduces:
- Variable latency
- CPU steal time
- Packet jitter
4. Client-side causes (secondary)
Some users may also:
- Use WiFi (big contributor to echo)
- Have double NAT / ISP modem issues
- Use browser/PWA instead of desktop app
What to do (in order — do NOT skip)
Step 1 — Upgrade Server (CRITICAL)
Minimum for your setup:| Component | Recommended |
|---|---|
| CPU | 4 vCPU |
| RAM | 4 GB (minimum) |
| Disk | OK |
Go 4 GB RAM + 4 CPU — no compromise



