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

GitLab: jami-project#855
Change-Id: I425a4b0049f1ade8c8eeeb93fc79f8d36bd25585

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

+ set initial rdv conference as muted (a/v)
+ update a/v mute state when joining or detaching host participant

Change-Id: I38d2dc219446ba526e6a3fc40e53ee73a2e87785

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

Change-Id: Ifc363fee36bd10fba9211cddaa03d6fbd8e99d49

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

Change-Id: I00df0524c8b00ad55fffe1ab17e82ba8a8ee9c0a

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

wait for contactAdded before actually removing it.

Change-Id: I29a6a2220a2e77ca023abdccab44c1f6a65bd5e5

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

Change-Id: Ifb28f17a705a9c46185c96ff8c23d3283128a0bc

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

Change-Id: I40171f3c5872bd5bf5719fd22a6a2af20ce6263f

Maxime Callet authored 3 years ago and Sébastien Blin committed 3 years ago

Change-Id: I3dbed60d7b0d53e720a564f28a32b6e2fa73fcea

jami-client-ios#150

Change-Id: I4f6d1b5e8db5be8e1c31b1bb7534080a13766edc

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

Mohamed Chibani authored 3 years ago and Sébastien Blin committed 3 years ago

- extend the scope of contact string
- protect with a mutex
- simplify contact address and header rewrite
in SIP account.

Gitlab: #633

Change-Id: I413261bb4e9cb80bf37b8c69d3a4cd7506b6a58b

Change-Id: I7bfa72e8c4e370bcf40611151c28e46c79b3bafd

Change-Id: Idbe771a647bf16b45d88755d684623895e5a8e82

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

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

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

With the help of a macro, we also get the context where the casting failed.

Change-Id: I7be3d63de9dd07994fb5c8cad39d5a93eedb7e8f

Change-Id: Id9176818cdc0162e4ac689a34c8927aadba4fd7b

Change-Id: I1a9e5c02d5678c6c9057dbfd372c636406593f3f

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

Change-Id: Iba4b98a1b9dd58c24945ee752084697419173049

Change-Id: I373ddb0efdeca41bf54e80aec4b9d1db69f77300

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

Change-Id: I95edfc348e9ef431e4ad26827bdfdadbba0fc746

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

Change-Id: I39c2bca72f8b6feb1578aecf32f97738eadfd235

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

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

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

Change-Id: I1d39a963ef3efe64059da82d99e23589c4920a2d

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

Change-Id: Ib70fdc0739a0ab7216be851b35f55a1ecb72a9a2

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

Change-Id: I8c18baa7f42f06a99e56acba0ce7863f1db28938

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

Change-Id: I12a30be4d77574f66bd6fc207cfee501bdb41bfa

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

Change-Id: I1de543265671728148e02d5b4d7d1878e22d6e18

Vladimir Stoiakin authored 3 years ago and Adrien Béraud committed 3 years ago

Change-Id: Ic5862a3e7ce879d8015a50dd348489c81b893603

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

ASAN does not like this:
--------------------------------------------------------------------------------
runtime error: reference binding to null pointer of type 'const value_type'
--------------------------------------------------------------------------------

Change-Id: Idca4720dda401c756bd6ea5dc054dd9e63779153

If a conversation is not cloned, when detecting a new presence,
needsSyncingWith MUST return true if one conversation needs to be
cloned. Else, it will result in an infinite syncing.

Change-Id: I3a9bcab9f8a845161ceac7d75d8842f8b338ed57

Mohamed Chibani authored 3 years ago and Adrien Béraud committed 3 years ago

Changing the media source of a media stream (video in particular)
must trigger a reinvite.
Since currently we do not support changing video properties (resolution
in particular) in the same media session, any changes in the video
properties must trigger a re-invite to restart the media locally and on
the remote peer.

Gitlab: #653

Change-Id: Ibd6192135d272908963cfbc585bec95c66881a28

acceptTrustRequest will set the conversation as ready.
removeConversation should be done after

Change-Id: I966cc2142d00bda880d63f11c52c36faceb11aa7

A ChannelSocket can starts to receive datas while waiting acceptance
for the channel. In this case, received datas will be injected when
setOnRecv will be called on the channel.

However, in channeled_transport, setOnRecv injects data to pjsip and
is handled by the SIPVoIPLink where transaction_request_cb will retrieve
the infos via the transports_. This means, that, in order to successfully
handle data, we MUST inject data when transports_ is correct.

In this patch, SipTransportBroker::getChanneledTransport is modified
to connect the callbacks after adding the transport to the map and
inject data in the correct methods.

This fix sporadic failures for testInviteFromMessageAfterRemoved

Change-Id: I2767801a9dad77439fb2f2adedbc9b900add8cea

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

Change-Id: I724883bf523ce7670f87979c884d97a86688cc38

Change-Id: If306734d2c29c017115e829b3fb4811333cea1f4

* use fmt for better performances
* fix dtls
* remove double space after display name

Change-Id: I9daeb69c65838b130432dfee0b4a5f92d0e53ad9

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

Change-Id: I53308fca61c46551129320babc99915d927a81dd

The contact header field was stored in a member varialbe of Jami/SIP
accounts. There was a condition in which the contact header could
be concurrently accessed by multiple threads. This typically happens
when terminating calls in batch (when calling hangupCalls() for
instance).
Managment of SIP contact header in Jami and SIP accounts was
reworked to prevent such race.

Gitlab: #633

Change-Id: Ib9295070a5295969bf114ec29e66e36b1c5c5e03

Kateryna Kostiuk authored 3 years ago and Adrien Béraud committed 3 years ago

GitLab: #644
Change-Id: Ia2b8e05d6ffbb22336bb284ea9ac5fc292eacb85