.... assuming cloud server is not behind a NAT firewall, which most are... you can find a lot of info in the user groups regarding this between March and August.
Sent from my iPhone > On Dec 15, 2020, at 11:49 PM, K. Kamhamea <kamha...@googlemail.com> wrote: > > In summary two conclusions can be drawn, right? > 1. There is no need to use courn if your server uses a unique public IP. > 2. You can run a OM Server in a private network with only one public IP using > coturn. > --- That's cool !!! > And probably it is even necessary to use coturn if your OM server resides on > a cloud that doesn't provide such a service. > > Thank You so much for the link. > K > >> Am Di., 15. Dez. 2020 um 22:43 Uhr schrieb Ali Alhaidary >> <ali.alhaid...@the5stars.org>: >> https://www.callstats.io/blog/2017/10/26/webrtc-product-turn-server >> >> >> On 12/15/20 5:05 PM, K. Kamhamea wrote: >> > I wonder why we need a coturn anyway? >> > >> > 1. SSL certificates can be installed without it >> > 2. The server URL can be written without port number (meaning it can >> > be accessed by the default 433 port) without turn server installed >> > the simple iptables command does the trick >> > >> > iptables -t nat -A PREROUTING -p tcp --dport 443 -j REDIRECT --to-port >> > 5443 >> > >> > and changing server.xml to the default port doesn't work anyway (with >> > or without turn server) >> > >> > It think better avoid turn server as it may slow down the >> > communication further.
