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 revision Previous revision
Next revision 		Previous revision
Next revision Both sides next revision
digital:server:matrixsynapsemisc [2018/12/07 10:29]
natrius 		digital:server:matrixsynapsemisc [2019/01/28 17:32]
natrius
Line 2: Line 2:
  
 Different things, sometimes advanced and some things that just did not fit in the regular guide.  Different things, sometimes advanced and some things that just did not fit in the regular guide. 
- 
-## .well-known section 
-Mathijs   
-it's a little early, but you could also add a section about .well-known 
-which just means you have nginx serve a json file on example.com/.well-known/matrix/client 
-I did it for apache, but it's probably fairly easy for nginx as well 
- 
-Mathijs   
-https://matrix.org/docs/spec/client_server/r0.4.0.html#server-discovery 
-if you like reading spec :) 
- 
-## Coturn 
- 
-Coturn is a turn server and it is used for 1:1 voip calls through the client (example: riot). 
- 
-<code>apt install coturn</code> 
- 
-Edit Config files 
- 
-opening ports 
- 
  
 ## Add an SRV Record ## Add an SRV Record
Line 53: Line 32:
  
 It's so your server_name (what's in MXIDs) doesn't have to be the hostname of the machine synapse is running on. It's so your server_name (what's in MXIDs) doesn't have to be the hostname of the machine synapse is running on.
 +
 +### Example 1
 +
 +''example.com'' points to the physical machine where synapse is installed and Port 8448 is used. 
 +
 +### Example 2
 +
 +''example.com'' points to the phsycial machine where synapse is installes and port 8448 can not be used. 
 +
 +SRV needed. 
 +
 +### Example 3
 +
 +FIXME ''example.com'' point to the physical machine with the URL ''example1.com''
 +
 +SRV needed?
 +
 +
 +## .well-known section
 +Mathijs  
 +it's a little early, but you could also add a section about .well-known
 +which just means you have nginx serve a json file on example.com/.well-known/matrix/client
 +I did it for apache, but it's probably fairly easy for nginx as well
 +
 +Mathijs  
 +https://matrix.org/docs/spec/client_server/r0.4.0.html#server-discovery
 +if you like reading spec :)
 +
 +## Coturn
 +
 +Coturn is a turn server and it is used for 1:1 voip calls through the client (example: riot).
 +
 +<code>apt install coturn</code>
 +
 +Edit Config files
 +
 +opening ports
  
 ## Optional Adminshell ## Optional Adminshell
Line 83: Line 99:
  
 <code>python3 pollbot.py</code> <code>python3 pollbot.py</code>
- 
-## deactivate presence 
- 
-  * https://github.com/matrix-org/synapse/issues/3971 
- 
-put ''use_presence: false'' in your synapse config (''homeserver.yaml'' ) 
  
 ## How calls work ## How calls work
Line 105: Line 115:
  
 everybody assumes it works like this, but it doesn't: assuming both HSs have turn, you actually want red lines via homeserver 1, homeserver 2 and then one going through both ie. the media may go through one or both turn servers (or none, as in your green line) everybody assumes it works like this, but it doesn't: assuming both HSs have turn, you actually want red lines via homeserver 1, homeserver 2 and then one going through both ie. the media may go through one or both turn servers (or none, as in your green line)
 +
 +@dave:matrix.org
 +not sure I quite understand the second diagram
 +in the first. media won't always go through both turn servers
 +the key to thinking about turn, I find, is that the TURN server is a thing that essentially pretends to be your client, but somewhere else on the internet
 +and it tunnels the traffic back to you
 +so you have a point of presence with your own internet connection, and then a second point of presence in your turn server once its opened a channel for you
 +and you then present both of those options to ther other side as ways to talk to you
 +equally you can also use your turn server as a route to send packets out to the internet to talk to the other party