The API doesn't provide any signal to detect when a device
discards a conversation's request. So, there is no way to correctly
update the UI when needed. This patch introduces a signal for this.

Change-Id: I78e39c65ff1ed037ff38b92368c770f73f3e5006
GitLab: #600

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

Change-Id: I545bbce8fdfa742dba61d613993e27e944b42af1
GitLab: https://git.jami.net/savoirfairelinux/ring-project/-/issues/1282

Change-Id: I0343a54c197a654b6f455dc9ee56b4e9ff98b421

Change-Id: I156894d5a9bb8acb19e9f334272b639d299ba4b7

https://github.com/pjsip/pjproject/issues/2787
https://github.com/pjsip/pjproject/pull/2788

Change-Id: I3c20c11a2a6f726dda6789fab2f12df2fcb23463

This reverts commit fa6fc142.

Reason for revert: Big delays added, resulting in unusable conference

Change-Id: Icdc87f5880f28db41165bda9d8e4f90189f420cd

This causes the client to show a lot of removed contacts to be
shown after syncing.

Change-Id: I66f0c343ad89812196222f29b23e7c6b5dbb8954
GitLab: https://git.jami.net/savoirfairelinux/ring-project/-/issues/1282

Change-Id: I9af1b95b07217c8abe4887586000fae9990963ca
GitLab: #604

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

This avoids to duplicate logic for all clients and fix the behavior
for swarm. setMessageDisplayed should be called everytime by the
client. Then the daemon will refresh the lastDisplayed for account
and will or not send the notification to other peers.
Note: if notifications are not sent, incoming displayed notifications
are also ignored. If we don't send we don't receive too.

Change-Id: If0f462ac4670d50a114c4a54bd90d76d83084bd9
GitLab: #599

onChange should not be moved if used

Change-Id: Id76b7b12502179308e5230e5382eb2f73945c43e

RTCP default address might not be provided by peer in the
received SDP, leading to misconfiguration of RTCP ICE
socket. Now, when the RTCP default address is not present,
the RTP address will be used instead.
Note when ICE is used, the RTP/RTCP default addresses are
only needed to identify the underlying ICE socket.

Gitlab: #587

Change-Id: Ia16eb7d25407e67b6ab5a29c18fc3c56e6fc15aa

Change-Id: Ie8528b466dac36f4f9658672d10ba09b7b895909

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

add test to ut_conference

GitLab: #562
Change-Id: I6b1a4882d42c57fd56429ed6d3e607a3b3192369

Change-Id: If133b3ccb576a3def747c6175dce201b589de35a

We need to wait that all devices are found before stopping
forEachDevices. This fix ut_call.

Change-Id: Ic695869957fbd1a6f28e11fa6ffb59d6447841e7
GitLab: https://git.jami.net/savoirfairelinux/ring-project/-/issues/1282

ubuntu 20.04 uses msgpack 3.0.1-3, however daemon doesn't seems
to build (msgpack_pack not found). This fix the build for ubuntu 20.04

Change-Id: I84d50b94b2e7b40d9cd8a599dd5d7da8c2ac4194

To send git notifications when sending messages.

Change-Id: Idb1d68dddccfaec4517e8b29fbbcf2f971566c59

Olivier Dion authored 3 years ago and Adrien Béraud committed 3 years ago

Gitlab: #590

Change-Id: Ie05da9f7fdad57c86da97fc7e3a2f8235100fc2c

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

rfc6544 rebase introduced an error where no_pending_check was
wrong causing the on_ice_complete to never be called if all
candidates failed.

GitLab: #597
Change-Id: Idca5f9bb2b03d9ae4687cef64df96cef6509b15d

Change-Id: Icc2baab0a6a52cbfee9b975187294c70477b5de0
GitLab: #579

95280b19 caused a regression where
certificates from contacts with the same patch weren't pinned
cause the public key is used. This cause bugs after the restart
where all connections where declined.

GitLab: #579
Change-Id: I6aea0d45f5f6084e59f23f497506349f17f9dafa

Change-Id: If02e9f70726e9506b54d69048a4996f3c1bd3f8f

In a one to one swarm, the invited file is not always the account.
Fix regression from 588890f9

Change-Id: I11581f37e2b7829bf05a42cfd48ab146bbb735f3

Change-Id: Ia052e6a86c3cb68c9895b0ee87e96391990b1d72

Change-Id: Ic8264b3b2b6f9cc3c4f92274830c49ed7fe3f87c

Change-Id: I1eba92ae040feafacad7c282c785f890704fc6b0

parseAnnounce doesn't use the longId. This fix authentification
to JAMS accounts.

Change-Id: I87a6b3d5893bb3aae6c814b086f50cd023d8a85c
GitLab: #579

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

Change-Id: Ic1f59314e62690cd7976095a8ec2e0cad49ccfc6

This fix ut_compability and a regression from
95280b19

Change-Id: I4a41e3c383fd8c8d31e844d2cd58fa82ef04fd00
GitLab: #579

Change-Id: Ie9f478783af7275eb360e3098d0e0d4bae7018e8

A user can remove a contact while a conversation is syncing with
this contact. In this case, the conversation was not deleted
properly. Causing some UI bug when re-adding the contact.

GitLab: #596
Change-Id: I88f2549a02ba67e9030cdadfdfb45f34a0ee06b9

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

Change-Id: I5e135b9ef4365acf87e6de4a8b1af9d19ef34ca3

Olivier Dion authored 3 years ago and Adrien Béraud committed 3 years ago

By removing the YAML configuration, the agent is now configured via a Scheme
file interpreted by Guile.

There's no need for behavior trees now since it can be reproduced naturally in
the Scheme language.

See README.md for how to compile and run.

Change-Id: Ibbf9ed0f965cee71bce63c0f8e8c12862f37176d

This breaks one to one swarm. Now, invited/ is added to detect
contacts that joins and left a conversation. This is wanted
to show read-only conversations.

Change-Id: I519094e75872062538fe56dd3a32378da814005b
GitLab: #595

With this patch, the daemon is now storing informations based
on setMessageDisplayed/onMessageDisplayed to follow the read
status per participant.

This avoid to creates a logic in all clients and allow the client
to have a correct read status even if the daemon was launched
separately.
Clients can now:

+ Retrieve last displayed interactions by retrieving members infos
(via getConversationMembers() and the key "lastDisplayed")
+ Know how many messages there between the head and a commit. This
is useful to count unread messages for a peer.

GitLab: #592
Change-Id: I0b5bc7adb5cda48754f33a362a40ce10ee345e3c

This changes tends to simplify the client code to
detect syncing conversations. Note, this patch
introduces some breaking changes for the stored
convInfos, but this will be fixed when all devices
are up-to-date.

Changes:

+ getConversations() now returns conversations as soon
as the request is accepted.
+ getConversationMembers() return members for syncing
conversation (current account and the sender of the
request)
+ "convInfo" now stores a map<string, ConvInfo> to
avoid iterating over all conversations. This changes
the structure stored on the disk and sent during the sync.

GitLab: #591
Change-Id: I365875cda89c483bcf9c6ea3bd8222e6253773b1

Change-Id: Icb4266aeb1274c02d8fc7e60dabfc7a7bec7a17e

Change-Id: I74f8b2cdb8cdf258022f32478dba8dad9e54353c

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

Change-Id: I8c834ea5abefc1f61996ab5098f1d7caf74e36dc

Change-Id: I512c6a5f2fe905d0857a5f22488cf01596a983b5