Use Proxy For Call doesn't seems to work

[ExPl0siF]

Hey everyone!

I have a Firewall which block every ports except my list. I've wanted to use Telegram on it but it seems that Telegram uses random ports. So I tried to use the proxy method with a SOCKS5 proxy on port 1080. I opened port 1080 (Both TCP/UDP) on the firewall. The proxy can be reached and is connected. But when I tried to make calls the same problem as if I didn't used the proxy happen -> the call cannot connect (stays on exchanging keys or connecting ... and quit call). So it seems that the Proxy For Call option doesn't work, isn't it? Something can escape my brain but I can't see what at the moment ...

Operating Systems: MacOS 12.1 | Windows 11
Telegram Version: 3.4.3

Thanks for reading and helping

P.S.: Doesn't know if it's an app issue or a something related on my part so can't tell if it's a question or a bug

[ilya-fedin]

Do you mean one-to-one calls or voice chats? If the second, this is a duplciate of #9984

[ExPl0siF]

Do you mean one-to-one calls or voice chats? If the second, this is a duplciate of #9984

I mean one to one call. Already see the other post. Thanks!

[ExPl0siF]

Hi @Aokromes, could you please tell me why this issue was closed? I said that the error was on one-to-one call. So this is not a duplicate of #9984

[PackElend]

@ilya-fedin one2one call

[Mandofskii]

When telegram support socks5 proxies for video chats?

[mostafaznv]

I have this problem too.

[CodingMoeButa]

I have this problem too.

[AqlaSolutions]

Same here

[Domest0s]

The same issue. Having it for a long time. Windows 10.

[aga-git]

Same issue with Telegram Desktop 4.8.1. Windows 7/8/10/11.
Socks 5 proxy not just being used for calls even so having 'Advanced' - 'connection type' - 'use custom proxy' - 'use proxy for calls' ticked AND in 'Privacy and security' - 'Calls' - 'Use peer-two-peer with' - 'Nobody' selected. Call JUST not goes through socks proxy server, it goes directly to one of telegram servers IPs. Confirmed via Microsoft Network Monitor. Conventional traffic (chats/etc) goes via proxy, calls - dropping after unsuccessful key exchange (explainable because no NAT is allowed in our network, only proxies are used). Advanced dante socks5 proxy setup was useless...

[alk3pInjection]

Same here on tdesktop 4.10.3 flatpak. Any updates?
I believe this is a severe security issue for users who intend to use (and probably rely on) this feature.

[tm4ig]

I bought telegram premium not for stupid emoji, but to support development. And I am very disappointed that this critical bug has not been fixed for two years.
Looks like telegram sucks

[mabt]

Same issue there

[AbdullahZubair]

Having the same issue. Not sure where is the problem lies.

[amir14a]

Same problem

[LionelHoudelier]

SOLVED FOR ME:
MY CONFIG: Desktop (debian flatpak flathug for me):
REASON of the bug: The option "use proxy for calls does NOT seem too work" because it STILL uses ports 596 597 598 599 and 1400 (opensnitch told me that) INSTEAD OF ONLY THE PROXY PORT when calling (text messages are working as expected).
I opened all these ports on my firewall (ufw) and it worked!