How can we return turn1.example.com in the relay candidate response #1028
-
We use below sample configuration to make RTC Connection
From the coturn config, we use external-ip e.g. XX.XXX.XXX.XXX configuration to return the relay candidate
The problem that I am facing is of whitelisting. For example, As per my understanding, After gathering the candidates via My question is that is my understanding of the problem correct and if yes, then how can we solve this ? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
Hi @navinkumarr I cannot think of an easy solution - here are a few things that come to mind
Hope that helps |
Beta Was this translation helpful? Give feedback.
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 qualityHope that helps