meta data for this page
  •  

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
sw:nextcloud:talk:spreed [2020/11/18 21:45] – niziaksw:nextcloud:talk:spreed [2020/11/19 08:40] (current) – niziak
Line 7: Line 7:
   * Spreed backend (it is REST api service) which control everything   * Spreed backend (it is REST api service) which control everything
   * NATS (Messaging server)   * NATS (Messaging server)
 +    * can be message broker to connect cluster of signaling servers
   * [[https://janus.conf.meetecho.com/|Janus WebRTC server]]   * [[https://janus.conf.meetecho.com/|Janus WebRTC server]]
     * [[https://github.com/meetecho/janus-gateway|github]]     * [[https://github.com/meetecho/janus-gateway|github]]
Line 28: Line 29:
  
  
-===== Verify ======+===== Verify and debug ======
  
 +Check if web frontend for signaling server is working:
 <code bash> <code bash>
 curl -k -i https://signaling.example.com/standalone-signaling/api/v1/welcome curl -k -i https://signaling.example.com/standalone-signaling/api/v1/welcome
 </code> </code>
 +
 +During NC Talk call, open WebRTC diagnose page in browser:
 +    * Firefox [[about:webrtc]]
 +    * Chrome [[chrome://webrtc-internals]]
 +and check what is **Remote Candidate** column. It should be only external configured IP of signaling server.
 +If TURN or JANUS is incorrectly configured (especially if it is running behind NAT) it can offer some wrong local IPs collected from all interfaces of machine on which is running (it can be some local LAN addresses like 192.168.x.x or Docker virtual interfaces like 172.17.x.x).
 +
  
 ===== NextCloud setup ===== ===== NextCloud setup =====