coturn VS Remotely

Stars: 11875 Author: coturn Star the coturn repository⭐

Might work with coturn or turn-rs, others?

https://github.com/coturn/coturn

https://github.com/mycrl/turn-rs

Maybe there are some projects doing only stun - if that is enough?

Both TURN and STUN can be self hosted, the most popular project i have found is coturn

# TURN server name and realm realm=DOMAIN server-name=turnserver # Use fingerprint in TURN message fingerprint # IPs the TURN server listens to listening-ip=0.0.0.0 # External IP-Address of the TURN server external-ip=IP_ADDRESS # Main listening port listening-port=3478 # Further ports that are open for communication min-port=10000 max-port=20000 # Log file path log-file=/var/log/turnserver.log # Enable verbose logging verbose # Specify the user for the TURN authentification user=turnuser:turn456 # Enable long-term credential mechanism lt-cred-mech # If running coturn version older than 4.5.2, uncomment these rules and ensure # that you have listening-ip set to ipv4 addresses only. # Prevent Loopback bypass https://github.com/coturn/coturn/security/advisories/GHSA-6g6j-r9rf-cm7p #denied-peer-ip=0.0.0.0-0.255.255.255 #denied-peer-ip=127.0.0.0-127.255.255.255 #denied-peer-ip=::1

I am trying to deploy coturn server in the Kubernetes cluster.

That is an excellent use case for a webrtc server rather than an usual voice communication. If you decide to go that way, you don't need any sim card. You just need an internet access. You install a webrtc client (the usual one is coturn). I don't know if you also need to set up some kind of chat server in addition.

I've found this issue for you: https://github.com/coturn/coturn/issues/492

If you host yourself on a VPS you can hook in coturn (it's enabled by the linked playbook by default):

https://github.com/spantaleev/matrix-docker-ansible-deploy/b...

https://github.com/coturn/coturn

Consider the interfaces here. These are located in a base library that contains code that can run on any operating system. There's no platform-agnostic way to do things like capture the screen or send keyboard/mouse input, so we have interfaces for services that perform those functions. The base library uses the interfaces instead of classes (i.e. implementations), because it doesn't know how to implement those things.

You can look at the commit history for my project. https://github.com/lucent-sea/Remotely/graphs/contributors

Remotely is a nice solution.

$DownloadUri = "https://github.com/lucent-sea/Remotely/releases/download/v2021.05.19.1433/Remotely_Server_Installer.exe" $OutPath = "$env:USERPROFILE\Downloads\Remotely_Server_Installer.exe" $WebClient = [System.Net.WebClient]::new() $HttpClient = [System.Net.Http.HttpClient]::new()

You could try: https://github.com/lucent-sea/Remotely

Here's an example of a working Nginx config: https://github.com/lucent-sea/Remotely/blob/master/Utilities/Example_Nginx_Config.txt

I think here is the answer, kinda