Change-Id: Ic3c0a52dce9ace78f8c3288c8326cc41da809fad

Change-Id: Ic5597f0713b9abbc6cfa903f13f9811b9a6f03b4

Sébastien Blin authored 2 years ago and Adrien Béraud committed 2 years ago

This fixes testProfileReceivedMultiDevice

Change-Id: I9fadebe2f353cdacd5a06fd860195ba7a50813dd

Ezra Pierce authored 2 years ago and Sébastien Blin committed 2 years ago

Change-Id: Ic8c46108f8cb25a148f1d90a9537602653e432c5

Ezra Pierce authored 2 years ago and Sébastien Blin committed 2 years ago

With the media player paused, calling seekToTime(startTime+100) results in getPlayerPosition() returning a negative value.
This patch adds a check in seekToTime to update the pauseInterval before updating the new startTime to fix this issue.
See MediaPlayerTest::testSeekWhilePaused() for the specific unit test that was failing.

Change-Id: Ib91c2998199728af532ba9dc83ea6ab830852b69

add build folders to docker ignore to fix problems when building the
image when the daemon has already been built locally

Change-Id: Ie24039ee5fbbf8944a008b6d0deac61a8400d00b

This causes a regression where we see both Incoming and Outgoing
missed call

Change-Id: Ic3d2ed2f4ca1018907619da33485af22f82da850

This allow the search request to be case insensitive by default

Change-Id: I97d0e9c01a2ca311faba7136cfda460ce7ad9957

This is a pretty trivial patch as all the necessary logics are
already supported by the deamon.
A client can use sendMessage with flag = 2 to add a reaction.
This only adds a "react-to" in the body of the message that the
client can interpret.
To remove a reaction, the client can use editMessage (and set the
body to "" for the id of the reaction), also there is no limit
on the content of the reaction and multiple reactions can be added
to the same message.
For non compatible clients, it will be shown as a simple text message
as it's the same type.

Change-Id: I7b13d32771109118b94ed17d0b918e66487e94bb

Reason for revert: crash

Change-Id: Ibc97ff3edeb40a1bf49df38be35de268da10399b

Sébastien Blin authored 2 years ago and Adrien Béraud committed 2 years ago

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

Sébastien Blin authored 2 years ago and Adrien Béraud committed 2 years ago

Change-Id: I6dc0b22f4336dde4db1d6a869e4447ad51d809ff

Sébastien Blin authored 3 years ago and Adrien Béraud committed 2 years ago

The new logic is there! Swarm is working since some time now, so we can
remove previous logic.

GitLab: #524
Change-Id: I5ca172e9349694d944c9561d97fe8a63d190ebf3

Sébastien Blin authored 2 years ago and Adrien Béraud committed 2 years ago

This causes new accounts to not sync with invalid certificates

This reverts commit 2db218b5.

Change-Id: I5bc98d9463f6ebe5331f908165e06ac5ac1e432a

Change-Id: Ie2746e3e01c8ebb12c3fd2ec9a08ec8b6b32a55f

Change-Id: I6e5b31c27f3c8bd22a6d6178bf3225f0b7ebde49

Change-Id: I9aa531e26c3ddcae81472b8ba55fbfe004e21001

Change-Id: Iabc70759c470a74b877e93ef794ed9ca51681d8d

Antoine Noreau authored 2 years ago and Sébastien Blin committed 2 years ago

Ensure SIP connections are gracefully terminated:
Removed duplicated register calls to SIP server

Change-Id: I330e67cf9534504f92517996eb7b693b43d359d3
Gitlab: #786

getAudioRTP() is not in use anywhere.

Change-Id: Ie88c2f80b1fd7d30f6c4fa586fbf7eaaa3c340ba

Detected by sonarqube

Change-Id: I606f9cf2458dda07471d0a67af8915c7ca13d410

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

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

Change-Id: I099d185f1a68470274012d3a597ff0b4a9f589d5

Change-Id: Ia7dc5c12c91c0b9ea07c41b2de3ac58df7d1239f

Change-Id: I94fa4962d90e697c283f5e3a2ff2a709f37fc599

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

Change-Id: I1ca05176ca1b2927bb2a44346d1e26b3d6261e77

Change-Id: I9b2b5ad339407cf80f8839eb2c897fd1a1a2c113

Ezra Pierce authored 2 years ago and Sébastien Blin committed 2 years ago

Adding option to configure noise suppression to use either native noise suppression (where supported), or noise suppression from the audio processor.

Change-Id: Iecc7f7e7997d0b75a88bcbadf0f1be9f1710676e

Change-Id: I879224318b47c151db91a12c0260dea25e33553d

Nicolas Vengeon authored 2 years ago and Sébastien Blin committed 2 years ago

jami-client-qt#510

Change-Id: Ie09ebd95ba161559c5c08b7e0618d6e87ecca1ee

Ezra Pierce authored 2 years ago and Sébastien Blin committed 2 years ago

Noise suppression results in higher quality audio with negligible additional latency.

Change-Id: I1aad3963bed045ed10631e897dda54b6cccd8632

Change-Id: I6fd5f5fa5c7f6f23555b40540a2eda37bd78165c

Change-Id: Ib939740608d112626ccce0228726e758b07d22a3

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

Change-Id: I6d0d909224cecb82883f805f60100e7c2e8d01f6

Olivier Dion authored 2 years ago and Sébastien Blin committed 2 years ago

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

Authentication realm kept as wildcard * to accept all challenges

Gitlab: #680

Change-Id: Ie75243466f683d939e27a94f5a9a16652e4a38de

Thomas Ballasi authored 2 years ago and Sébastien Blin committed 2 years ago

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