Fix Discord calls that hang forever on “RTC Connecting”, “No Route”, or “DTLS Connecting”.
Some ISPs don’t block Discord — they block the handshake. Text works, servers load, media would flow fine… but the handful of packets that set up a call get silently dropped, so voice never connects.
Unmute finds those packets and reshapes just enough of them to get past the filter. Only handshake packets are touched. Voice and video data are never inspected or modified, so there is no effect on latency, bandwidth, or call quality.
$ unmute status
Unmute
✔ service: active
• at boot: enabled
• ports: 19294-19344 queue: 201
handshakes
native Discord → udplen +8
WebRTC / DTLS → ipfrag2 pos8
Discord has two different voice handshakes, and an ISP can block them by two different mechanisms:
| Client | Handshake | Signature | Commonly blocked by |
|---|---|---|---|
| Native Discord desktop | IP discovery | starts 0x0001 0x0046, always 74 bytes |
packet size |
| Vesktop / browser / any WebRTC | DTLS ClientHello | starts 0x16 0xfe |
payload signature |
A strategy that beats one often does nothing for the other. Padding defeats a size filter but leaves a signature untouched; fragmenting hides a signature but doesn’t change the size a size filter keys on. That’s why “it fixed Vesktop but broke native Discord” is such a common dead end.
Unmute measures each handshake separately and applies a strategy per client.
- Linux with systemd and nftables
- Root access
The installer handles dependencies on apt, dnf/yum, pacman, zypper, apk, xbps and
eopkg. It reuses an existing nfqws if you
already have zapret installed, and otherwise builds it from source.
git clone https://github.com/vsoultann/unmute
cd unmute
sudo ./install.shOptions:
| Flag | Effect |
|---|---|
| (none) | CLI + GUI |
--no-gui |
CLI only — no GTK dependencies |
--uninstall |
Remove everything (config is left behind) |
The installer will:
- detect your distro and install dependencies
- obtain
nfqws(reuse or build) - create an
unmutesystem user - install the CLI, GUI, systemd unit, polkit rule and desktop entry
- warn you if another bypass tool is already queueing the same ports
- enable and start the service
sudo unmute autotuneThis is the important step. The right strategy is ISP-specific, so Unmute measures it rather than guessing: it sends probes through each candidate strategy against a live Discord voice server and keeps the one that actually gets answered.
testing strategies against 104.29.148.37:19318
udplen +8 ████ 4/4 external=203.0.113.9:52780
udplen +64 ████ 4/4
ipfrag2 pos8 ░░░░ 0/4
fake ttl6 ████ 4/4
result
✔ native IP discovery : udplen +8
That’s it. If something still doesn’t work, see Troubleshooting.
unmute status # service state, active strategies, live packet counters
unmute probe # is the handshake getting through right now?
sudo unmute autotune # measure and apply the best strategy for this network
sudo unmute doctor # verify the install, detect conflicting tools
sudo unmute stop # disable without uninstalling
sudo unmute start
sudo unmute enable # / disable — control start-at-bootLaunch Unmute from your application menu, or run unmute-gui. It offers the same
capabilities: a service toggle, start-at-boot switch, one-click auto-tune, a
reachability test, and live packet counters. Privileged actions prompt through polkit.
Discord’s voice servers answer an IP-discovery request carrying an arbitrary SSRC.
That means unmute probe can test reachability honestly without joining a call, and
autotune can score strategies in seconds instead of by trial and error on a live
conversation.
A crafted STUN packet is not a valid test — Discord requires ICE credentials and ignores unauthenticated ones, so STUN returns zero even on a perfectly healthy endpoint. Don’t use it as a control.
Matching happens on handshake bytes in nftables, not on protocol guessing:
udp dport 19294-19344 @th,64,16 0x16fe → queue (DTLS ClientHello)
udp dport 19294-19344 @th,64,32 0x00010046 … → queue (IP discovery)
Everything else — all media, every other application — never leaves the kernel. Matched
packets go to a single nfqws instance carrying one profile per handshake.
Matching on bytes rather than L7 classification is deliberate: nfqws makes a STUN
classification stick to a flow, so any L7 filter mentioning stun also swallows the
DTLS ClientHello that arrives later on the same 5-tuple — silently shielding the very
packet you’re trying to fix.
Full write-up, including the measurements and the debugging pitfalls: docs/how-it-works.md.
| Steam | UDP 3478/4379/4380 and 27000-27100 — outside the matched range |
| Games (Roblox etc.) | UDP 49152-65535 — outside the matched range |
| All media | RTP/SRTP/RTCP never matches a handshake signature |
| TCP | not matched at all |
sudo unmute doctor also checks whether another bypass tool (e.g. zapret) is queueing
the same ports — two tools fighting over one packet is a common cause of “it worked
yesterday”.
| Symptom | What to do |
|---|---|
| Auto-tune finds nothing | Your ISP may use a mechanism not yet in the strategy list. Please open an issue with your country and ISP — that’s how the list grows. |
| One client works, the other doesn’t | Expected if only one handshake is blocked. unmute status shows the strategy applied to each. |
| Worked on wifi, not on mobile data | Different networks, different filters. Re-run sudo unmute autotune on each. |
probe reports 0/4 everywhere |
Endpoints are read from Discord’s WebRTC logs and may be stale. Join a call once to refresh them, or pass --endpoint IP:PORT. |
| Service won’t start | journalctl -u unmute -n 30, then sudo unmute doctor. |
sudo ./install.sh --uninstallConfiguration is left at /etc/unmute/ so a reinstall keeps your tuned strategy; delete
that directory to remove every trace.
Packet rewriting is done by nfqws from bol-van’s
zapret. Unmute adds the byte-level matching, the per-handshake strategy split, the
measurement harness, and the packaging.
MIT — see LICENSE.