If a contact is added, the first device will erase the trust request,
but the second device will update the contact but not the trust
request. Causing, the removeContact to generate a new request for
the previously created conversation.
Change-Id: I2f0a48b3c6b6b18ed6218e7a08c61de2beb08d3d
GitLab: #664
As libwrap is used by default, HAVE_SHM should only be true
if directrenderer is not used to avoid useless work
Change-Id: I9f819a7c06c667ccf08066f70104dcd3667f8546
Handle media change request in conference, specifically when adding
video to a an audio only call.
Gitlab: #638
Change-Id: I0eb892eb941d2a62b6046c7b2ac9d128f4bcbd12
When a call is held, the media direction in the SDP
for an active media must be set to sendonly.
Also add unit test for simple hold/resume operations
Gitlab: #644
Change-Id: Ib41434c55f9be1a6d34a7d51c9127af89081c8e8
Introduce 2 main changes to the TCP patch:
- limit the number of connection retries.
- use a higher Ta for TCP connection retry (500 ms)
Gitlab: #634
Change-Id: I2281addf072c6f0e9ff2fc0457e08a590af1e178
+ set initial rdv conference as muted (a/v)
+ update a/v mute state when joining or detaching host participant
Change-Id: I38d2dc219446ba526e6a3fc40e53ee73a2e87785
In a swarm, if something is wrong, the peer will retry the connection
but for the sender, they have the file so they should be able to see
it and should not see any "Cancelled" error here.
However, in the future, we will need to update the API to provide
status per users and what peers received the file.
Change-Id: Id02ea3f6552557bdc01d3f13504b5b81efb443e9
When hosting a conference a video session and video mixer are
created regardless if the video enabled state in account settings.
The video enable/disabled in the account settings must be applied
to the created conferences as well.
Gitlab: #646
Change-Id: Iddd72e9056974e50041e693dd964420557c6c331
- extend the scope of contact string
- protect with a mutex
- simplify contact address and header rewrite
in SIP account.
Gitlab: #633
Change-Id: I413261bb4e9cb80bf37b8c69d3a4cd7506b6a58b
Guile is confused by agent.scm and agent. It will try to load the ELF file
instead of the Scheme script when `(use-modules (agent))`.
Change-Id: Ieead4c384f10df9ead351a6ae66b21f708e97424
This work follow the JamiAccount split started before. This moves
the ConnectionManager's callbacks code related to data transfer into
transfer_channel_handler and improves syncing by sending contact's
avatars (where a swarm is present) to new devices.
Note: for now, contact's avatar are managed by the client. So, this
code will only transmit avatars if the profile is found. For now,
the only path tested is the one used by jami-libclient. To be able
to fully sync all avatars, the avatar management should be moved in
the daemon with future work.
Finally, in syncHistory a test is added to validate the behavior.
Doc: https://git.jami.net/savoirfairelinux/ring-project/-/wikis/technical/3.8-Sync-profiles
GitLab: https://git.jami.net/savoirfairelinux/ring-project/-/issues/1282
Change-Id: Ic98da34aabf1be070a57dcac55bba0a00c555445
