- Nov 18, 2022
-
-
Initializing a ICE session will need to gather candidates. The TURN can be long to retrieve, and fails can be really long to detect. There is at least 3 cases of failures: + IPv6 badly configured, which can cause a DNS resolution timeout of several minutes (that's why the IP was cached) + Empty DNS entries, causing a resolution failure + A TURN server un-reachable or wrongly configured (e.g. 1.1.1.1) The idea here is to resolve the TURN and test the connection before caching it. And use it when cached. This avoid all resolutions steps and we're basically sure that it was working. Other approaches: + Add a new callback in pjsip to detect that the TURN is taking too long to remove it for next calls, but I prefer to not add another patch in pj and it's not an ideal solution + trickle ICE to not wait for all candidates, but this is a big changes and will generate more DHT messages + Do not retransmit messages, but this is against the RFC Change-Id: Iaec4308bca8cbbbfa4d6b1b6d7a7759b8062a67a GitLab: #781
-
Change-Id: I6dc0b22f4336dde4db1d6a869e4447ad51d809ff
-
The new logic is there! Swarm is working since some time now, so we can remove previous logic. GitLab: #524 Change-Id: I5ca172e9349694d944c9561d97fe8a63d190ebf3
-
This causes new accounts to not sync with invalid certificates This reverts commit 2db218b5. Change-Id: I5bc98d9463f6ebe5331f908165e06ac5ac1e432a
-
Adrien Béraud authored
Change-Id: Ie2746e3e01c8ebb12c3fd2ec9a08ec8b6b32a55f
-
Adrien Béraud authored
Change-Id: I6e5b31c27f3c8bd22a6d6178bf3225f0b7ebde49
-
Adrien Béraud authored
Change-Id: I9aa531e26c3ddcae81472b8ba55fbfe004e21001
-
Adrien Béraud authored
Change-Id: Iabc70759c470a74b877e93ef794ed9ca51681d8d
-
Ensure SIP connections are gracefully terminated: Removed duplicated register calls to SIP server Change-Id: I330e67cf9534504f92517996eb7b693b43d359d3 Gitlab: #786
-
Ezra Pierce authored
getAudioRTP() is not in use anywhere. Change-Id: Ie88c2f80b1fd7d30f6c4fa586fbf7eaaa3c340ba
-
- Nov 17, 2022
-
-
Sébastien Blin authored
Detected by sonarqube Change-Id: I606f9cf2458dda07471d0a67af8915c7ca13d410
-
Sébastien Blin authored
This avoid mobile phone to host conferences for others unless explicitly authorized by the user. Clients can show it via the "hostConference" conversation's preference. Documentation: https://docs.jami.net/technical/swarm.html#call-in-swarm GitLab: #312 Change-Id: I9bbd3e394cd1b3bcfd4a3120d9023a5ed686303d
-
Sébastien Blin authored
This patch introduces the ability to start calls and extends the usage of rendezvous points to swarm with multiple participants. When starting a call in a swarm with multiple participats, one device will work as the host of the conference, and the caller will immediately start the call alone. Other peers will receive a commit and a notification to be able to join the active call. To join a call, users needs to call rdv:uri/device/convId/confId to be added (if authorized) to the conf. There are some majors differences in the process. First, every conversation will be able to decide a default host for conferences. This still needs some design and will be introduced in another patch. For now, the caller is the host. Then, because all members of the call may not be interested to join a call, or they may want to get several calls at the same time, the system must be able to manage more than one active calls (e.g. a company with multiple projects can do several standups at the same time). Finally, in the conversation, two commits will be generated to be able to know what active calls are available. The first is announcing that a conference started, the second announces that the conference stopped (the host closed the call). However, this introduces a difficulty. The host may crash and not commit the end of the call in time. In this case, hostedCalls are stored in a file and the conversation is updated during the init of the daemon. Change-Id: I081a4920edb3773bbed884ae50f34e476ad42094 Documentation: https://docs.jami.net/technical/swarm.html#call-in-swarm GitLab: #312
-
- Nov 16, 2022
-
-
Adrien Béraud authored
Change-Id: I099d185f1a68470274012d3a597ff0b4a9f589d5
-
Adrien Béraud authored
Change-Id: Ia7dc5c12c91c0b9ea07c41b2de3ac58df7d1239f
-
- Nov 15, 2022
-
-
Adrien Béraud authored
Change-Id: I94fa4962d90e697c283f5e3a2ff2a709f37fc599
-
- Nov 04, 2022
-
-
Thomas Ballasi authored
As a measure of refactorization of the code and to prepare to the development of dhtnet, the following changes aims at seperating jami-specific code to connectivity-specific code. GitLab: #778 Change-Id: Iaa08100f7d61c80292f039a5aae66819cc85b0e9
-
Thomas Ballasi authored
Change-Id: I1ca05176ca1b2927bb2a44346d1e26b3d6261e77
-
- Nov 03, 2022
-
-
Adrien Béraud authored
Change-Id: I9b2b5ad339407cf80f8839eb2c897fd1a1a2c113
-
- Nov 02, 2022
-
-
Adding option to configure noise suppression to use either native noise suppression (where supported), or noise suppression from the audio processor. Change-Id: Iecc7f7e7997d0b75a88bcbadf0f1be9f1710676e
-
Adrien Béraud authored
Change-Id: I879224318b47c151db91a12c0260dea25e33553d
-
jami-client-qt#510 Change-Id: Ie09ebd95ba161559c5c08b7e0618d6e87ecca1ee
-
- Nov 01, 2022
-
-
Noise suppression results in higher quality audio with negligible additional latency. Change-Id: I1aad3963bed045ed10631e897dda54b6cccd8632
-
Adrien Béraud authored
Change-Id: I6fd5f5fa5c7f6f23555b40540a2eda37bd78165c
-
Adrien Béraud authored
Change-Id: Ib939740608d112626ccce0228726e758b07d22a3
-
- Oct 31, 2022
-
-
Sébastien Blin authored
If an error occurs during the execution of git_remote_fetch, there is no need to signal any error to the client as it's not a critical issue (no malformed conversation, mode is recognized, no unauthorized method) and the sync will be retried later. Change-Id: I2d875445e51aa6cd78eb2e7dbfe5efb8b2831860
-
Adrien Béraud authored
Change-Id: I6d0d909224cecb82883f805f60100e7c2e8d01f6
-
- Oct 29, 2022
-
-
It's not possible to replace the DRing namespace for jami because of conflicts with namespaces and classes defined under the jami namespace. Thus, use libjami as the namespace. Script to reproduce: rg -l DRing | sort | uniq | awk '$0 !~ /NEWS/' | xargs sed -i -e 's|DRing|libjami|g' rg -l DRING_ | sort | uniq | xargs sed -i -e 's|DRING_|LIBJAMI_|g' sed -i -e 's|dring|jami|g' src/jami/CMakeLists.txt sed -i -e 's|dring|jami|g' src/jami/def.h Change-Id: I80e8c8b58a7586527a016bbef850bab07869c473
-
- Oct 28, 2022
-
-
Antoine Noreau authored
Authentication realm kept as wildcard * to accept all challenges Gitlab: #680 Change-Id: Ie75243466f683d939e27a94f5a9a16652e4a38de
-
The usage of ChannelSocketTest helps avoiding unnecessary overhead when running unit tests (especially on creating a huge quantity of nodes and sockets). ChannelSocketTest implements a simplier form of ChannelSocket that directly communicates to a peer rather than through a socket. Change-Id: Id1c68aaa92f8f8cf8002c417f670254b0b851cfb
-
- Oct 27, 2022
-
-
logUntil should retrieve the commits with the commit passed. Add a LogOptions parameter to avoid too much parameters. Change-Id: I77a0150b135b14fe44577747d2b1a86cb2cf2509
-
Change-Id: I8c899f31e29bc7a50989afc69518accbf2935428
-
- Oct 26, 2022
-
-
Adrien Béraud authored
Change-Id: I738d5dd3ef7ad4787a950e172172c31949b77a74
-
Change-Id: I995b422ca3d078b02cf560056edeeacc35628a70
-
Sébastien Blin authored
Change-Id: I55fae603c65350adfec658cf73768a9535d614d3
-
Change-Id: I834f27f66836be3ece3feac7ead662802d89da2d Gitlab: jami-client-android#1111
-
Sébastien Blin authored
Change-Id: Ie51f23d4c0547adc8542bb046d769f03a91d27c4 GitLab: #784
-
- Oct 25, 2022
-
-
Adrien Béraud authored
Change-Id: Ie035755eaa58621985b80612f25c2918891b00bc
-
Sébastien Blin authored
This reverts commit 7bce5bb7. Reason for revert: Break config Change-Id: I7e21df8f0fc80ceea3088f891992b1ae19693e33
-
Gitlab: jami-client-android#1111 Change-Id: I3d0f5abcd4b1ca4d64fcc908c0823ad6961c872c
-