What the sources actually say
"RTC Connecting" is the stage where Discord establishes the voice connection. The pinned Flowseal Discord thread, Discussion #252, lists being stuck on this message as a known symptom and gives two first responses: try other strategy BAT files, or change the voice channel region in the channel settings. The same thread links a separate issue about voice channels stopping work for AdGuard users.
The most detailed RTC case is Issue #13149, opened 2026-05-08 and now closed, titled "[Solution] 5000 ping and endless RTC connection when using Zapret and AdGuard". The reporter, using zapret version 1.9.7b with strategy ALT 11, described these symptoms starting around 2026-04-29: the Discord desktop app launched and text chats worked, but connecting to any voice channel never completed, and the reported ping climbed as high as 5000 ms. Critically, voice chat in the browser version of Discord worked normally on the same machine.
The reporter wrote that they had tried everything first: different zapret versions, every strategy, and a full reset of Windows network settings. The actual cause turned out to be AdGuard's traffic filtering — fully disabling AdGuard immediately restored voice chat in the desktop app. Their documented resolution: in AdGuard, open Settings → Network, open the list of filtered applications, add winws.exe from zapret's bin folder and Discord, and then uncheck both entries so AdGuard stops filtering them. The author notes the same treatment can be applied to Cloudflare WARP (listed as warp-svc or Cloudflare WARP) if it also broke.
Two details from that issue keep it honest: the author says AdGuard and zapret had coexisted on their machine for a long time without conflicts before the problem appeared, and they note that for part of the affected users the problem was fixed by newer zapret versions — the AdGuard conflict was what remained for those whom updates did not help.
Step-by-step diagnostic flow
- Confirm the shape of the failure: Discord opens and text chats work, but joining a voice channel sits on "RTC Connecting" indefinitely, possibly with extreme ping values.
- Test voice in the browser version of Discord. In Issue #13149 the browser worked while the desktop app did not — a useful split that points at something filtering the desktop app's traffic.
- If you run AdGuard or similar traffic-filtering software, fully disable it as a test. The issue author reports voice chat recovered immediately when AdGuard was off.
- If the conflict is confirmed, apply the reported exclusions: AdGuard → Settings → Network → filtered applications, add winws.exe and Discord, and uncheck both so they are not filtered.
- If AdGuard is not involved, follow the pinned discussion's advice: try other strategy BAT files and change the voice channel region.
- Re-test after each single change, otherwise you will not know which step mattered.
What is source-backed vs community-reported
- Community-reported (Discussion #252): "RTC Connecting" as a recognized symptom; strategy switching and voice region change as first responses; a linked AdGuard voice-outage issue.
- Current issue evidence (Issue #13149, opened 2026-05-08, closed): the 5000 ms ping symptom, browser-vs-desktop split, and the AdGuard exclusion procedure on zapret 1.9.7b / ALT 11.
- Source-backed by official documentation: none; the official zapret repository does not document Discord RTC behavior.
When the reported workaround may not apply
If you do not run AdGuard or any traffic-filtering software, the Issue #13149 resolution has nothing to attach to — the author themselves said newer zapret versions fixed the same symptom for other users. Voice connection failures can also be strategy- or ISP-specific, which is why the pinned discussion recommends strategy and region changes rather than any single fix. And if Discord fails entirely — not just voice — the general Discord troubleshooting flow is a better starting point than RTC-specific steps.