Update Frequently Asked Questions

This commit is contained in:
Sébastien Blin 2020-04-08 17:56:23 -04:00
parent 5408242dde
commit be9ff65fae
1 changed files with 18 additions and 3 deletions

View File

@ -39,6 +39,7 @@
- [How to back up and reimport conversations and accounts](#advanced-7) - [How to back up and reimport conversations and accounts](#advanced-7)
- [How secure are you?](#advanced-8) - [How secure are you?](#advanced-8)
- [When do public IPs get exposed?](#advanced-9) - [When do public IPs get exposed?](#advanced-9)
- [What port Jami uses?](#advanced-10)
This page aims to gather as many resources as possible (technical or not) and This page aims to gather as many resources as possible (technical or not) and
condense them to create concise documentation. Then, this can then be condense them to create concise documentation. Then, this can then be
@ -353,8 +354,22 @@ This will not work (actually, you can create the SIP control connection because
### <a name="advanced-10">What port Jami uses?</a> ### <a name="advanced-10">What port Jami uses?</a>
+ dhtproxy, nameserver: TCP [80-100], 443 Jami works as a server and get new ports for each connections (randomly binded). This is the ranges that can be usedd for each components:
+ dht: UDP [4000, 8888]
+ audio: UDP [16384-32766] + audio: UDP [16384-32766]
+ video: UDP [49152-65534] + video: UDP [49152-65534]
+ SIP Control: UDP/TCP randomly binded
So for ufw, we recommend to run:
`sudo ufw default allow outgoing`
For now, you can't specify a specific range to configure ports used by Jami. The inbound traffic can be controlled without issue, Jami should work and can use a TURN server if needed.
If you run your own proxy or nameserver:
+ dhtproxy, nameserver: TCP [80-100], 443
If you run your own TURN server:
+ TURN/STUN: TCP+UDP 3478, 5349 + TURN/STUN: TCP+UDP 3478, 5349
+ dht: UDP [4000, 8888]