jami
/
jami-docs
mirror of https://git.jami.net/savoirfairelinux/jami-docs.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

user/faq.md: cleanup 

Change-Id: I12e074d22a53884667e23cf6b14536a041829938
This commit is contained in:
ovari123 2025-05-05 04:41:14 -04:00
parent 47b8241122
commit a4364130d7
1 changed files with 24 additions and 25 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

49
user/faq.md
View File

@ -497,27 +497,27 @@ For all three scenarios, there are three main actions:
##### Send a message
The Jami application is running a DHT (<https://opendht.net>) node on your device.
So every operations on the DHT will use your IP address.
This is why Jami has the option to use a DHTProxy (e.g., <http://dhtproxy.jami.net/>); this will avoid using your node and instead will use another node on the network (which will see your IP address).
So every operation on the DHT will use your IP address.
This is why Jami has the option to use a DHTProxy (for example, <http://dhtproxy.jami.net/>); this will avoid using your node and instead will use another node on the network (which will see your IP address).
Note that your message is not sent directly to the other device.
In fact your message is sent on some nodes of the DHT and your contact will retrieve the message on this node.
So, your contact don't see your IP address at this step, but the node who get the message will (or they will see the IP address of the proxy).
In fact, your message is sent on some nodes of the DHT, and your contact will retrieve the message on this node.
So, your contact does not see your IP address at this step, but the node that gets the message will (or they will see the IP address of the proxy).
##### Send a file
As described in the docs, you will send a message with all the IP address you know that your peer can contact in an encrypted packet.
So, if your peer send you a file or you send a file, your addresses will appear in the ICE message.
As described in the documentation, you will send a message with all the IP addresses you know that your peer can contact in an encrypted packet.
So, if your peer sends you a file or you send a file, your addresses will appear in the ICE message.
##### Calls
Same as above, the IP address is present in the ICE.
Same as above, the IP address is present in the ICE message.
#### (2) Behind a VPN
##### Send a message
The IP address of your VPN will be used by the DHT node.
If you want a proof, you can compile dhtnode and run the `la` command to get your public detected address.
If proof is required, compile dhtnode and run the `la` command to retrieve your public detected address.
This is what I got:
```none
@ -536,10 +536,10 @@ If you use a DHTProxy, the DHTProxy will see your VPN addresses.
##### Send a file
Same as above, the ICE contains:
+ addresses from your LAN
+ public address of your VPN
+ TURN address if TURN is enabled
Same as above, the ICE message contains:
+ addresses from your local area network (LAN)
+ public address of your virtual private network (VPN)
+ TURN server address if the TURN server is enabled
##### Do a call
@ -595,8 +595,8 @@ bound). These are the ranges that can be used for each component:
- SIP Control: UDP/TCP randomly bound
```{note}
If UDP is blocked, a DHTProxy can be used to use TCP instead.
However, media will not work because it only supports UDP.
If the UDP protocol is blocked, a DHTProxy can be used to use the TCP protocol instead.
However, media will not work because it only supports the UDP protocol.
```
So for UFW (Uncomplicated Firewall), it is recommended to open the Terminal and enter the command:
@ -619,21 +619,20 @@ If you run your own TURN server:
### Can I use Jami in a local network (LAN) without Internet access?
Yes!
Thanks to Jami's architecture, Jami users on a local/private network can communicate among themselves using Jami, without requiring any outside connectivity such as the Internet.
Thanks to Jami's architecture, Jami users on a local/private network can communicate among themselves using Jami without requiring any outside connectivity such as the Internet.
To do so, from Jami's `Account` settings open `Advanced account settings`.
There, enable the `Enable local peer discovery` setting.
Additionally, you may want to manually set the `bootstrap` node's address (default: `bootstrap.jami.net`) to the IP address of another device on your network that also runs Jami and/or an OpenDHT node.
To do so, with the selected Jami account, open the settings, select the `Account` tab, and open `Advanced settings`.
There, enable the `Local peer discovery` setting.
Additionally, you may want to set the `bootstrap` node address (default: `bootstrap.jami.net`) manually to the IP address of another device on your network that also runs Jami and/or an OpenDHT node.
```{note}
If you will use this Jami account for communicating only with only with other devices on the same local/private network, you can disable TURN if you wish.
If you do so, and later you decide to use this account also for communicating with other Jami devices outside your network, don't forget to enable TURN again, as it helps Jami work around issues with some overly restrictive firewalls.
If you will use this Jami account for communicating only with other devices on the same local/private network, you can disable the TURN server if you wish.
If you do so, and later you decide to use this account also for communicating with other Jami devices outside your network, don't forget to enable the TURN server again, as it helps Jami work around issues with some overly restrictive firewalls.
```
### How can I configure the codecs even more?
Codecs can be configured via a file. In the configurations files, you
can create a file called `encoder.json` like this:
Codecs can be configured via a file. In the configuration files, you can create a file called `encoder.json` like this:
```json
{
@ -679,9 +678,9 @@ The relevant preference keys are:
- `audioProcessor`, which configures which audio processor to use. The valid options are:
- `webrtc`: the `WebRTC Audio Processing library <https://www.freedesktop.org/software/pulseaudio/webrtc-audio-processing/>`_
- `speex`: the `Speex DSP library <https://gitlab.xiph.org/xiph/speexdsp>`_
- `null`: disables audio processing (though your system echo canceller may still be used, see below)
- `webrtc`: the [WebRTC Audio Processing library](https://www.freedesktop.org/software/pulseaudio/webrtc-audio-processing/)
- `speex`: the [Speex DSP (digital signal processing) library](https://gitlab.xiph.org/xiph/speexdsp)
- `null`: disables audio processing (though your system echo canceller may still be used; see below)
- `echoCancel`, which configures how echo cancelling should be done. The valid options are: