Spreed standalone signaling server

It is composed from following services:

• Spreed backend (it is REST api service) which control everything
• NATS (Messaging server)
• Janus WebRTC server
  • github
  • Janus as a WebRTC “enabler”
• CoTURN server (act as STUN/TURN)

Notes for dockerized solution:

• It is using direct host network because large ranges of ports are needed (RTP/TURN) and Docker port forwarding proxy performance is poor.
• Using one shared host network let detect already used ports when 2 services can opens ports with overlaping ranges:
  • Janus WebRTC opens listening ports on any range (it can be limited in janus.jcfg or cmd line argument)
  • TURN also opens listening ports 49152-65535 (range required by RFC)

Port forwarding is needed:

• Spreed backend HTTP port 3080 (set in server.conf) neeeds to be rev proxied with SSL to external IP with attached domain
• STUN/TURN UDP/TCP port 3478
• CoTURN UDP/TCP ports 49152-65535 (range required by RFC)
• Janus WebRTC ports 20000-40000 (set by cmd line argument -r 20000-40000)

• Settigns –> Talk
  • STUN servers
    • signaling.example.com:3478
  • TURN servers
    • signaling.example.com:3478
    • set [Turn API KEY] (set in server.conf in section [turn] secret=
  • Signaling servers
    • https://signaling.grinn-global.com/standalone-signaling/
    • check Validate SSL certificate
    • Shared secret: [Nextcloud-Secret-Key] (set in server.conf in section [backend] secret=