Tunneling and proxy support is a built-in feature in Glue. Basically, it means that Glue can be used behind a proxy server. (https://en.wikipedia.org/wiki/Proxy_server). This feature is automatically used if Glue detects that direct connections will not work. Glue proxy support is based on system proxy settings. At the moment, Glue does not support overriding system proxy settings at the application level.
Glue utilizes real-time session connection tunneling through standard WebRTC data channels to bypass proxy servers. This method is similar to how popular browser-based communication platforms like Google Meet, Microsoft Teams, and Zoom operate. Since WebRTC is a widely accepted protocol for transmitting real-time data traffic, it is automatically permitted to pass through most corporate proxy servers.
Glue users have the option to manually enable WebRTC connection tunneling through the Glue settings. However, if a direct connection is not feasible due to the current network configuration, the Glue client will automatically switch to WebRTC connection tunneling.
Direct session connections are still recommended whenever possible because they offer better session overall performance. When WebRTC connection tunneling is used, it may result in reduced performance in sessions with more than 15-20 participants. For that kind of session and requirements, there are specific Glue session hosts available for separate requests.
Required firewall configuration can be found here.
For session connections to work, WebSocket and WebRTC connections must be allowed through a firewall and proxy a server if that exists. Note that WebRTC tunneling does not require any non-standard TCP/UDP connections or firewall rules due to it being standard WebRTC traffic.