Aline Gondim Santos authored 2 years ago and Sébastien Blin committed 2 years ago

To apply translations, first try to read if the JAMI_LANG variable is
set, if not, try to get the system language.

GitLab: #747

Change-Id: Ie458abcc07c0d0fd151172e172fe1418e5f06e7f

This gives to clients the ability to perform search for messages
with several parameters (account's id, conversation's id, author,
period, max number).
(To discuss) This patch introduces the search API, and a signal
(MessagesFound) to return a result.

GitLab: jami-project#1382
Change-Id: Ibc4665449fa0da71a015d1d18d6d0d3209331d43

Create a minimal test for the plugins system.

GitLab: #745

Change-Id: I17d48860ce24cfdc5423d4dcc3cb44bb4d4531f6

+ Some code were unused
+ Ask for profiles in one to one after a clone, this
allow to get the profile after adding/removing/re-adding
the contact as the peer will not know and got a cache
where they sent the avatar before.
+ Update unit-test

Change-Id: Ide1df647dbec63f343b60c1c622d1a214f4c3016

Several improvements are included with this patch:

1. confirmed is resetted when account is removed, this allow to
send a request when conversation is added back and reset the
whole matrix, avoiding duplicates
2. Banned can be due to harrasement. In this case, keeping the
conversation like the old behavior (pre-swarm) is better, to keep
proofs. Also re-adding back a contact is immediate if it was a
mistake as the conversation is kept back.

jami-project#1449

Change-Id: I13da8ce9bd431b91ce7b7d455dae561358c62f10

Removing a contact was not actually closing all connections, causing
the remote contact to be able to call even if it was banned if there
was more than two channels opened.
Rewrite closeConnectionsWith as it was unused to use it to close
connections with the banned contact.

jami-project#1449

Change-Id: I147f437370a553f0682b0cea060720a6c473f8a2

Change-Id: I3eaa39c81fe816e3149ae8599fb8e95f84e18bc0

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

Change-Id: Iafc78c75cc935bd7b91f39cbd43159f1a7eeaa02

This is useful for the conversation_module if any channel is pending
while shutting down, as the previous fetch status was not updated.
More generally, every connectDevice() should call the associated
callback.

Add a unit test to replicate this scenario.

Change-Id: I72f2975dc15dd4bac3f55c2f899ebb1ae5a7a7f3

bad CPPUNIT_ASSERT and timing issue

Change-Id: I16267d00325ebc1875cb4a92f73eaefb50614f99

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

Now that it's been months since all clients supports swarm, we
can assume that everybody is using a version compatible with
swarm now.
So, downgrading conversations to a non swarm if a DHT message
comes is not necessary and it's just unwanted code.

Change-Id: I83b83d592ea43219cbdecb31fa8b5a71b897e487
GitLab: #312

GitLab: #318
Change-Id: I12c04096a91c40b5e6c9c435373cce23b4065d7e

After a re-add of an invited contact, the validation was bugguy causing
the conversation to be invalidated and erased due to malformed commits

Change-Id: Ib500ae117f0c53774cfb1eec23aa160ba2f86420

A contact can be banned from another device. In this case,
JamiAccount::removeContact is not called and the daemon only call the
dedicated callback.
So, remove the conversation requests and connections to the banned
contact (and avoid future incoming calls if connected) when the
callback is called instead in JamiAccount::removeContact() as it
will be called in a multi-device context.

Change-Id: I1ac8b441268d7bfc9bb6627fbbbc7b83e2e75052

Change-Id: Ibfa6759b19ba240115ef36412cc8a1ed7bd6cd41

sipTransport was only true on destroy, causing tlsInfos_ to be
always incorrect.
Moreover, if the SIPTransport is generated from a channeled socket,
we do not need to copy the peerCertificate.
Finally, update conference to use the tlsInfos_ to get the URI
instead of playing with peerNumber's

Change-Id: If8b93a4614e790e6ffbfd1bcc0aa68f6407344ce

Sébastien Blin authored 2 years ago and Amin Bandali committed 2 years ago

In the contact list, receiving a confirmed request for a non-active
contact would re-add the contact.  If the contact was removed then
re-added, the conversation would be badly updated & removed, instead
of replacing the conversation by the old one.

Finally, remove the replaced conversation after the clone of the
new one, to avoid making the contact disappear while cloning.

Add some tests to validate the scenarios.

Change-Id: I67a94604c5869804ed66b390aa26cca9420fbc28

+ Bump deamon version to enable multistream
+ use signal for recorder to check if file stopped
+ answerMediaChangeRequest pass isRemote for tests

Change-Id: I396b8246264cb7826350f75e74f20f05b864f384

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

If a conversation was previously removed, it couldn't be re-cloned
due to the fact that the sync value can come from a previously
offline device.
Like updateContact in contact_list, use created/removed to determine
if it's a re-added contact to be able to re-sync again.

Change-Id: Ibe16d2bda02cbbe41b16d8b365d9c8ef02b36140

As unused and duplicates informations

Change-Id: I4c98328339bd4149206ac88d9af456418960838f

+ Fix recording in an audio only call
+ Fix crash if deinit the recorder without remote video
+ Add some tests

Change-Id: Ie78a632f6a2ecb3eae4f53ae8f25c8ecbf5c5091
GitLab: #719

Change-Id: I83eb58915afb2baef7dad17bec192129eb754bd3

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

This patch makes the daemon able to negotiate more than 2 medias
for a call. Basically, this patch includes some major changes:

1. reportMediaNegotiationStatus is also called for conference, so
the client is able to update the mediaList of the conference to
use it later if it needs to change the medias. And the medias
can be retrieven with currentMediaList
2. The conference object correctly updates the video mixer on
media changes, and video inputs are restarted if removed then
re-added.
3. Because previous versions of the daemon only supports two medias,
only negotiate more medias with compatible peers. If the daemon is
not compatible, the medias will not be negotiated anyway.

jami-project#1429

Change-Id: I55701d9e6e53b05c9a58adad4e8ea90303e6b9e7

Change-Id: Iad94763131b74d17ab5d7bf1090d30d533ae04a6

jami-project#1429

Change-Id: I23ef5a7ccedfd500aea3f9392c367a168eb391d1

This fix isConferenceParticipant after exitConference() (if going
from a conference to a 1:1 call) and avoid failed actions after.

jami-project#1429
Change-Id: I9ba5d687ac9d523a89503552c9951568f5986940

This fix testInviteFromMessageAfterRemoved (hasHandler was
not correct in checkConversationsEvents because the task was not
cancelled anymore).
Fix ut_scheduler's build

Change-Id: I4dbf3b31180c43fb7fa11061f3ffacb492d925c3

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

Change-Id: Icad35be50347b26fdb9470b3878c09a403cdbf93

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

Since we're not building Jami statically anymore, agent.exe is
generated under test/agent/.libs and the script `agent' is a wrapper
around it.  Thus, change agent.exe for `agent' for compilation of
scheme.

Change-Id: I8766ca6470ba1a9136d8eb6cb2d45b278fd85456

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

Change-Id: I06a7f8da672946b20c353e4b5d3a3aaa499203fb

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

The agent requires Jami's bindings to correctly run scenario.  This
can only be done if Guile can find the correct scripts.  Thus, the
pre-inst-env script can be used to setup the correct environment for
running the agent before its installation.

Change-Id: I474ef204bb33fd2098eee44b5b99c00f120c4536

if a shutdown is called while we are waiting for channel to be ready
we must remove the pending callback attached.

Change-Id: Ibe1d2a6517b5f1035d4031bf08bab294ce5111d7

The current design got some limitations. It's not possible to
control informations per shared media. This means that we can't
got several active sinks for example.
The goal of this patch here is to update the conferences orders
to be able to control the state of each sink individually and for
the client to be able to handle conferences with accounts connected
via several devices with several medias per devices.
So each orders is sent with a different level (account/device/media)

For example, we will be able to send a moderator order for an account,
to hangup a device or to set a media active.

To support those orders, both sides MUST be patched. Else, the old
protocol will be used. The version of the protocol supported is sent
in the conferences informations to notify the peer what version to use.

Finally, this patch changes some APIs to support multisteam:
+ Some APIs now takes the deviceId or the sinkId when necessary

jami-project#1429
Doc: https://git.jami.net/savoirfairelinux/jami-project/-/wikis/technical/6.1.-Conference-Protocol
Change-Id: Ieedd6055fd43b2a09b2cc8b253dcd6a3bf260a39

In some cases, the infos were not correctly refreshed, causing some
pending callbacks to never be called.
Also, split getInfo() in two methods to improve readability.

Change-Id: I1b60f2cf2ac5bf97c9a44a53794b56906d314e6a
GitLab: #TODO

Merge's commits were'nt checked, while comitting and while pulling.
This means that the author could be incorrect. Add a check before
doing a merge commit and when validating it.
This avoid incorrect repository in case a merge commit is generated
after a migration.

Misc: fix incorrect test

GitLab: #738

Change-Id: Id9748eb7d3dd5db023dd2ab4a30261c31af5d514

Aline Gondim Santos authored 3 years ago and Aline Gondim Santos committed 2 years ago

With video split we don't need dummy rtp session.

GitLab: #729
Change-Id: Ibf6bb303d1860a80549f6cfb2a06e36e51f48b70

This patch fixes several behaviours:

+ Banning a member now stores the previous state of the member
+ This allow to store empty .crt files for invited
+ Unbanning a member is now possible for an admin
+ This re-add the member in its previous state

https://git.jami.net/savoirfairelinux/jami-product-backlog/-/issues/51
Change-Id: I34d5913c023043e07544f1b8bb6211aea5db0065

Conversation's requests also have metadata attached which clients
must be able to access.

jami-client-qt#670

Change-Id: If02fffb5646074e993c090846ff998e83ab79d78

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

The agent and unit tests can now be compiled without requiring
`--disable-shared' at configuration time.

The agent requires the logger functions to have default visibility instead of
hidden.  Thus, `jami::logger::[v]log' can be considered part of the public API.

The unit tests however require hidden symbols.  Thus, we link the tests against
a static version of libjami instead.

Change-Id: I59d9e67679766e0310a19f9a879c06a31c5124c4

Mute/un-mute audio is done only locally, i.e. without requesting
a media change (re-invite) as done for the video, thus the media
direction in the SDP must not change for the audio stream.

Gitlab: #688

Change-Id: I3775a29f6c566a159d5b9269b4d9462ab4e3c36f