TURN over TLS on corporate networks that intercept TLS

For Workers & Pages, what is the name of the domain?

N/A

What is the issue or error you’re encountering

On corporate networks with a transparent proxy that intercepts TLS traffic (using a custom root certificate), our application can’t connect to the Cloudflare TURN service, even using TURN over TLS on port 443.

In my experience if TURN over TLS on 443 gets passed through or not depends a lot on the settings of the transparent proxy, firewall or what ever is intercepting the traffic on port 443. Because in the end the TURN traffic doesn’t look like HTTP at all. So if the intercepting device blocks non-HTTP traffic it will always block TURN over TLS.

Does the same transparent proxy allow other TURN over TLS on port 443 with other TURN service providers?