Voice calls are not being routed to the proxy server

[roman90sv]

Describe the bug
Voice calls are not being routed to the proxy server address specified in the messenger's settings. The "Use proxy for calls" option is currently active.
However, the rest of the messenger's traffic is routed through the proxy (all connections to TG servers, messages, file downloads, etc.).

When voice calls are not routed through the proxy, it is impossible to use them. This is because Telegram calls are blocked in my country at the DPI level. The voice data transfer protocol itself is blocked, both over UDP and TCP. The DPI drops most of the packets, so even with a successful connection, you can only hear choppy sound with a very low bitrate.

To Reproduce

1. Settings → Data and Storage → Proxy Settings.
2. I activate the options "Use proxy" and "Use proxy for calls."
3. I specify a Socks5 proxy address in the following format: 127.0.0.1:2080.
4. Nekobox proxy client is listening on the port I specified and routes the traffic to my proxy server using the Trojan protocol.

! If I disconnect from the proxy server in Nekobox, then exteraGram cannot connect to the TG servers. This confirms that the main traffic is indeed being routed to the specified Socks5 proxy address.

Expected behavior
If exteraGram adhered to the "use proxy for calls" option, then voice calls would be just as high-quality as they are when routing is configured at the Nekobox client level. This is because if I disable the proxy in exteraGram's settings and instead select exteraGram in Nekobox's settings for routing through my proxy server, then voice calls work perfectly.

Smartphone (please complete the following information):

• Device: Matepad BTK-W09
• OS: Android 12, HarmonyOS 3.1.0.188, Kernel version 5.10.136
• Version exteraGram: 12.0.1 (61669)

[damnurmum]

The error lies in the implementation of the "Use proxy for calls" function in Exteragram. The application cannot correctly bind voice call data streams (probably using the MTProto mobile protocol) to the interface of the configured proxy, which leads to direct connections that are immediately detected and blocked by filtering systems at the national level. All you have to do is wait for a response from the developers.