Yes, it is feasible to circumvent VOIP blocks in the UAE by employing WebRTC clients.
Yes, it is feasible to circumvent VOIP blocks in the UAE by employing WebRTC clients.
My sister resides in the UAE while I am in India, making it impossible to use free video chat tools like Skype or WhatsApp there. Services such as those on Skype and WhatsApp are restricted from offering VoIP services in the region. I’m curious if a WebRTC client running on Heroku or AWS could bypass these rules. Although WebRTC uses TLS, it might still work. What are your opinions? Are there any other self-hosted solutions that could meet my needs?
EDIT: They also prohibit VPN usage, as reported by ZDNet.
Not necessarily. You could connect both devices via a VPN, either directly or through an intermediary, and then use standard VoIP software through that connection (such as SRTP). If generic VoIP services are blocked but not VPN, this might work. WebRTC isn’t built for this scenario either; a VPN tunnel would still be required to secure the setup.
Previously, I needed to make a video call with someone across the border using Google Duo. It functioned well without requiring a VPN, unlike other applications.
can you please explain this ? am not an expert in protocols and all.
There isn't a viable option that doesn't run into legal issues. I'd suggest focusing on platforms you're already using—like Twitch, Mixer, YouTube, etc.—and view the situation as a small group chat rather than a VoIP call. This way, you can avoid high fees without crossing any boundaries.
The issue isn't just HTTP traffic—it depends on how the connection is set up. WebRTC operates over peer-to-peer or STUN/TURN servers, not standard HTTP. If your server is handling the traffic, it might intercept or block WebRTC signals. Check your server configuration and ensure it supports WebRTC protocols.
WebRTC aims to transmit VoIP using standard TLS on port 443, yet the entire process lacks strong protection. If intercepted, it would reveal connection details and could be blocked. I wouldn’t depend on web-based tools for this since most rely on Chromium and Google often removes experimental features. The current WebRTC implementation is still incomplete.
On a side note, setting up a third-party server to run an RTMP stream and use OBS to broadcast is straightforward, allowing one-way or two-way communication. Running it in both directions creates a basic VoIP setup suitable for simple group chats.
Services like Kast enable participants to form virtual meetings similar to Teams or YouTube hangouts. Since the legal requirements in places like the UAE are unclear, these approaches help bypass potential risks rather than ensuring robust security. The only real way to secure the connection is mutual trust, which isn’t feasible if authorities demand access to intermediaries.
It relies on how the system is built. The most reliable way is to experiment with it. What counts as the full connection setup is unclear to you, and where did you learn this? I'm reaching out because this doesn't align with my knowledge of WebRTC. What aspects feel missing in its implementation? Also, why is it tied to Chromium? Since it's a web standard, many different versions exist, so you shouldn't rely solely on any single provider. You need to understand how encryption functions properly. The only trust required for security is between the two parties involved—no need to rely on intermediaries like ISPs.
It's the same issue with torrents too. ISPs are smart, then encrypting torrent traffic so it mimics VPN data, which makes them severely slow down all encrypted streams. Users end up routing through VPN services, but ISPs still block the traffic. The fastest way to damage new tech is to force it to use old methods, which explains why everything now relies heavily on HTTPS and the web is becoming very sensitive. You'd better not be joking if a country that bans VPNs and some VoIP apps just completely stops peer-to-peer connections.
🔗 https://torrentfreak.com/huge-security-f...es-150130/