Modified behavior to support cases where a SIP account uploads a new profile. The main idea is to move the vCard management logic in the daemon.
Change-Id: I74dece22cd2917ad2f5ff2b37e2d413696cdcec3
PluginsTest::testTranslations assumes that at least one of the fields in
the TestSuite plugin's manifest has a French translation. Such a
translation was added in version 1.0.1 of TestSuite last year by commit
d0e0ef18395a07a1579b512c5d67bf61f7c3587a in the jami-plugins repo:
https://review.jami.net/c/jami-plugins/+/25667
However, the daemon plugin tests were still using version 1.0.0 of
TestSuite, which is why testTranslations was failing every day. This
patch fixes the issue by upgrading the TestSuite.jpl file used for the
tests to version 1.0.1.
GitLab: #1064
Change-Id: I7b851083bd8e1ac80d61f721baabbc092b46c56a
Added a flag (0 for avatar path, 1 for base64 image) to enhance API flexibility, allowing avatar support without local image storage. This change accommodates clients, such as iOS, that do not save images locally.
Change-Id: I914c14d9b38b97d1126bd2d1de4523d987e422ee
This new API integrates vCard logic within the daemon, allowing clients to only provide a path. It sends the updated data directly to other connected peers to synchronize information (cached connections). The API can also be used to remove a displayName or avatar, meaning you must always supply either a displayName or an avatar to use it.
Change-Id: I6d9bdb29ce86ce3721911cf5cf7eb836ef976110
The MessageChannel is used to exchange Jami protocol messages
between peers, similar to the SyncChannel but for communications
with contact devices instead of account devices.
It would ultimately be used instead of the SIP channel
for communication with peers, overcoming the pjsip message size limitation
and avoiding the overhead of the SIP message header.
The MessageChannel also allows transmission of raw binary data over the network,
which is not possible with a SIP transport.
Messages on the MessageChannel are serialized using msgpack.
It is used instead of the SIP transport when possible,
in a backward-compatible way, falling back to the SIP transport if a MessageChannel is not available, for instance when communicating with an
older Jami version.
Change-Id: I104c998486cbd5e520b1e3b92277613c84a3a305
This patch fixes a bug in the Conversation::Impl::loadMessages2 function
that caused it to incorrectly return an empty list when the nbOfCommits
option was set to 0.
GitLab: #1073
GitLab: #1074
GitLab: #1075
Change-Id: Ie0cc5ced49725f4996a6e4350619ac1717882168
The Daemon API now returns the correct number of messages requested. Previously, it could load the entire conversation.
Change-Id: I3204abc4c0f0dcc55dbc436e4c8740b3f886b8b8
to port libraries into plugins, they need to be PIC compiled.
docker default user is root, the flag --allow_running_as_root is needed for onnx
Change-Id: If9a3f70b8232b32ac005cdb7b22f011aef32c871
Previously when the default host device was
removed, trying to host a conference would still
attempt to connect to a device with empty Uri.
Change-Id: I8f33eba5a5b93e9d1bff2275667a885a3ebe22c5
When a device sync status between another device, it only exchange the last message viewed and the last message fetched. This patch is about correcting status after sync
Change-Id: Id9ac6b9e5cdce168b1df72904ad9619fa307be52
This patch fixes a bug that could cause the members in a swarm to
repeatedly fetch from each other, generating large amounts of
unnecessary network traffic in the process.
https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/1851
Change-Id: I3e4d2f2b3b9b659a9a51ad6fe00c4f08f4c923a6
These signals help the client know when a user updated his profile and are indeed needed in the expressJs server
Change-Id: Ib82d3bf477dbb77a3d86f79c6f9aa12a9b30dfd3
Fixes the issue where one of the daemon-tests would repeatedly
fail. Cause was an expired plugin certificate.
GitLab: #1015
Change-Id: Ib6059402569c9817514e3a80dad63b3c52c1e3c1
