What's the future of Talk and the HPB?

ā„¹ļø Support šŸ’¬ Talk (spreed)
3

nothing obvious, which is why its mentioned in the how to.

following the discussions on various GitHubs concernedā€¦ it turns out, that impression was not intended by the spreed folks. see Nextcloud Talk documentation and discussion

Talk:HPB remains optional! Talk is functional for personal use in a local network for ~3 participants. For multiple external participants (HPB=) STUN, TURN and a signalling service is required;

High Performance Backend for Talk on Nextcloud with Docker

Talk:HPB

A High Performance Backend (HPB) requires a signalling service and consists of three components working hand in hand;

  1. STUN service is part of TURN for discovering NATed/firewalled external IPā€™s. TURN is both a ā€˜Traversal Using Relays around NATā€™ (TURN) server and a ā€˜Session Traversal Utilities for NATā€™ (STUN) server. A STUN server is provided by default in Nextcloud, but you can replace it with your own.
    • Examples: stun.nextcloud.com:443 or stun.yourdomain.tld:3478 or both
  2. TURN service like ā€œcoturnā€ or ā€œeturnalā€ for connecting NATed/firewalled external IPā€™s and controlling WebRTC streams. Its main role is to help WebRTC clients behind routers to communicate and relays the audio and video data through firewalls and port restrictions.
    • Examples: turn.yourdomain.tld:3478 or yourdomain.tld:3478
    • Encryption is optional for TURN & STUN and will be handled by encrypted Nextcloud
  3. Signalling service like ā€œJanus: the general purpose WebRTC serverā€ is required for calls and conversations with multiple participants. The signaling server is used to establish a WebSocket connection between the participants in the call. Without it, all participants would have to upload their own audio/video individually for each other participant causing connectivity issues.
    • Example: https://signal.yourdomain.tld
1 Like