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

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

logUntil should retrieve the commits with the commit passed.
Add a LogOptions parameter to avoid too much parameters.

Change-Id: I77a0150b135b14fe44577747d2b1a86cb2cf2509

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

Change-Id: I8c899f31e29bc7a50989afc69518accbf2935428

Change-Id: I738d5dd3ef7ad4787a950e172172c31949b77a74

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

Change-Id: I995b422ca3d078b02cf560056edeeacc35628a70

Change-Id: I55fae603c65350adfec658cf73768a9535d614d3

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

Change-Id: I834f27f66836be3ece3feac7ead662802d89da2d
Gitlab: jami-client-android#1111

Change-Id: Ie51f23d4c0547adc8542bb046d769f03a91d27c4
GitLab: #784

Change-Id: Ie035755eaa58621985b80612f25c2918891b00bc

This reverts commit 7bce5bb7.

Reason for revert: Break config

Change-Id: I7e21df8f0fc80ceea3088f891992b1ae19693e33

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

Gitlab: jami-client-android#1111
Change-Id: I3d0f5abcd4b1ca4d64fcc908c0823ad6961c872c

The sinks only should be created when there is a video device
available. If no video device is available, no sinks should be
created.

Change-Id: Iec35288bf9966eb664470b2f8c1e5738f6909893

For now, only be able to edit messages from our-self and with the
text/plain type

Change-Id: I20c6ed7dad3892f0fa655812242b9ca6e77e69b3
GitLab: #316

If iOS is in deep sleep mode, it will only wake up the daemon if
a new activity needs to be shown (call, message or contact).
If the peer accepts a trust request, it will clone and join the
conversation (so a new message will be shown). So, cloning
a conversation should notify the iOS device that the daemon MUST
be started.

GitLab: #776
Change-Id: I639a5f928fec2970909a29b9f3c33c165ac201c8

If initialization of natpmpHdl_ has failed, then closing it will result in closing
a random file descriptor, typically standard input.

Change-Id: Ifb1335a83b1900d4cf31c820bba090cb30b68d7a

In some cases the file "contacts" was badly synced. Also, if for any
reason "contacts" is not correctly formed, we may be able to fix it.

This patch handles two cases of failures:

1. If the contact details doesn't contain any conversationId BUT
a 1:1 conversation is found with this contact, we update the
conversationId in the details.

2. If, for some reason, multiple 1:1 conversations are detected
with the same contact, we only keep the one in the details, as
it should be the correct one.

This should fix the fact that for some conversation, calls are not
written in the history (cause getOneToOneConversation() returns
nothing).

Change-Id: I5dd9fc51999540d8a4230f8fdce828a461da752a

Change-Id: Ic01845c26653338719b76410878aece456ac93cc

Ezra Pierce authored 2 years ago and Adrien Béraud committed 2 years ago

Guile is no longer in contrib so this documentation is obsolete.

Change-Id: I884cf03b5d1fa677f6cf8036bd5b0dffec4dda88

Change-Id: I36869baf37ccd52d7204b6cd9f5a6c4e0c4a3a17

Aline Gondim Santos authored 2 years ago and Adrien Béraud committed 2 years ago

Change-Id: I2e8e7c6ff7da0cb71db135184522e92f25aca0f3
GitLab: #779

Change-Id: I7362b02cc1fd557cf454ccc29d60ff88a53f4afc

GitLab: #780

Change-Id: I50e5dff097c4573f24f9ba6c25fa38e2857479ae