Skip to content

How can we return turn1.example.com in the relay candidate response #1028

Answered by eakraly
navinkumarr asked this question in Q&A
Discussion options

You must be logged in to vote

Hi @navinkumarr
Right, firewalls are never easy.

I cannot think of an easy solution - here are a few things that come to mind

  • To have an additional mechanism that will update firewall config with IP addresses of TURN servers. For example a job that would run every X hours, resolve address of TURN server(s) and update firewall rules.

  • If your FW always allows HTTPS (TLS over 443) then you can force relay to use TURN over TLS (use following as iceCandidate: turns:turn1.example.com:443). This will enable relay over TLS to 443 which will look like HTTPS to most firewalls but may degrade connection quality

Hope that helps

Replies: 1 comment 2 replies

Comment options

You must be logged in to vote
2 replies
@navinkumarr
Comment options

@eakraly
Comment options

Answer selected by navinkumarr
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants