GitLab: #743
Change-Id: I5a0313f21aa2044bf9e20c96ed4f597cc9ca2859

Change-Id: I3f8365b7d0631ba23bbd20ea5a8da4e847a1eec0

Change-Id: I728827c5515095f355c000d4a9a76f0a1a6eb78b

Change-Id: Ib565af26f01d08e994451a5bfb6413791e8037b3

Before 1360c775 interface contains
"default", not an empty string. This cause the UDP transport to not
be-ing recycled and changing settings cause the SIP account to not
be re-registered correctly.
Also handle the case of empty interface, anyway it can be considered
as default.

GitLab: #826
Change-Id: I77068e44b7ea93463be2d8dec00b0da87a56370d

Sébastien Blin authored 2 years ago and Andreas Traczyk committed 2 years ago

In some cases, the local address was set as public address, causing
the SDP to not contains the public address for the medias.

GitLab: #823
Change-Id: Iad2673170c8f9ef46e8e30b15aa638a1a0dd6e6e

Change-Id: I79219023e5cc694424a68ed9e078d94988acb9b1

Handle Apple Silicon arch

Change-Id: I95878dca3588776d7ef4bf676841278cc7353876

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

Change-Id: I28c6dc67ee49dd2f8aaae8a5da39496a676501ce

+ Forward the onFinished signal to jamiaccount to only mark a profile
as sent once finished.
+ For incoming transfer, only send to upper layer if file is complete.

Change-Id: If0160330c65720f235d0fabacaf124a4b52ec823

On the same model as conversation's preferences

GitLab: #815
Change-Id: I15461d40c5d9e83e39ef5f83b6b663d9427615f8

Change-Id: I5cd70f156b6c137b0fde174d8c742ca81564171f
GitLab: #704

Add preferences to original sync information sent and use it after
a clone.

GitLab: #814
Change-Id: I742ba8ff3ddf56d1f73658fffa0675ce481981e0

#704

Change-Id: I44a908e03e7a809e07e68906c0839fbc356e3346

Kateryna Kostiuk authored 2 years ago and Kateryna Kostiuk committed 2 years ago

On iOS, when the app is in the background, invitations are received
and saved by the notifications extension. When Jami becomes active in
the foreground, those invitations may not be visible. This
patch reload invitations from the file when registering an account.

jami-client-ios#250
Change-Id: I9ae3d8ec285c94081c5a6d1ceeb31f9058673dcf

Change-Id: I05ae748bc572f3a7e28fd040fefe047a5fc4ca3d

Fadi Shehadeh authored 2 years ago and Sébastien Blin committed 2 years ago

-changed config file for graph visualization
-increased fields limit

Change-Id: Ic2270930230e9eaa6272dbfec0ca0a9643bfa6d8

Aline Gondim Santos authored 2 years ago and Adrien Béraud committed 2 years ago

Change-Id: I2ee4f6642150c327921fabcac871434748835e8b

Change-Id: I5c9178e2fb3de42a61dcc60c98b6f60a81c8e7dc

Use the negotiated medias to start conference in a correct state
(e.g. if calling a swarm in audio-only we should only see
one audio only participant). The previous code was incorrectly
starting the conference and adding an extra partipant when
attaching the call.

Note: lot of code in conference is also currently re-factored for
homogeneizing 1:1 and video conferences. So I prefered to avoid
to change a lot of things there.

A test is also added to check that video or audio is correctly
attached in the participants information.

Change-Id: I074cc4eb41b21418a6d751e3395db93e8a4da7f5
GitLab: #803

Adrien Béraud authored 2 years ago and Adrien Béraud committed 2 years ago

Change-Id: Ibdb2592704bd36cb95d165237507fe1fd3e7d215

jami-client-android#990

Change-Id: Ia756c8b4a66f7e661f4ec72d2a1f46d4967f5593

Change-Id: Idfd2a086847f9665c57e83a8184c20957fec9664

Change-Id: Ia80fc12ba65b1abd516af205e6664261ae2e33fe

Change-Id: I0a72cd58d0c3822ecb99366f2e96c10eb81d7900

Change-Id: I8439fdb4ed070d8701976481b42ee3f50d57525a

This was a regression caused by 11c47a98
where the profile was not sent in multi-device mode.

Change-Id: Icb5b3d9e8fafef84374bb2253f67879286d3f893

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

This avoid to erase the content of a file if it's an hard link,
which was the case for file transfers.

Change-Id: I5ee2ace650de0ef12953e5643f014e62e2d3c04d

Change-Id: Ic96399c9d58b4abbd0bc9b3cbab9f27c8b479b04

Change-Id: I12fd7a335ce9075f65493ed0efe8b8dbc5c6ced4

Change-Id: Iccad0f6572783885f079424ba8ea37a24dbf4b46

Change-Id: I1c00901a92ba9821a14114809799285a10d6aaee

Change-Id: I61e8237f6994d024b48d1783e108b4d4a763b097

Change-Id: I1307012cc7b26c620b141deda0049bcea66860c3

Change-Id: Ia2154baaa51969fcbe4c906344aa8f5dfdf041ae

Change-Id: I00c0605a5f6c289a792bee5b8b36374d469da93b

Seems loadTextFile is failing for files written on GNU/Linux and
loaded on Windows.

Change-Id: Idca4fc87f0039df26f97e8627c444ad518fd8dc8
GitLab: #810

Change-Id: Ic3ffb3330cfc7d3a38763d294abf737e3b57e589

Change-Id: Ica456a0e2bee80848ce790665d066d245b0a62f3

If two users were starting a call at the same time, activeCalls
was filled with a duplicate active call. This was due because
the merge commit re-announce all commits where the linearized
parent potentially changed, causing a call to be added two times
in the vector.

Also add a fail-safe to avoid this in the future (will only print
a log in the back-end).

Change-Id: Ie419a419c13abcfb44e3c758fa40845f492504ae