Change-Id: Iab2caaa3fb8377b7a42301c3635d70233f0cc623

Change-Id: I2c04e3831f68a55b7682c42eb93464e1fab78b1b

Change-Id: I4bdef901c2a2bc07dc1a9263eb0a9796655c051a

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

Change-Id: I55568eac3c95105131751d245224fbc3fd44a782

RingBuffer has its own mutex. This avoids potential deadlocks.

Change-Id: I93175aafe9fbb3f927da28124a7d42e61585523d

Change-Id: Idde24be13daf0fca55ce5a2607e6b9835c18f3c5

maxime authored 3 years ago and Aline Gondim Santos committed 3 years ago

Change-Id: Iaa356f723a34c67cfd66190c04a53aea88bbea07

Change-Id: I30b7d9db2cbac84c6ae15d15b0fe8a0f93e3a271

Change-Id: I3b0fd2a34289545dbf06b85c2e825fbf87bb42ad

Change-Id: Idbb8720de936661b01fcea97faeab92d0526b6c2

Philippe Gorley authored 6 years ago and Adrien Béraud committed 3 years ago

Hardware decoding will still be used even if the codec level is unknown
or higher than the hardware's reported supported level.

From FFmpeg: "It's generally a good idea to pass this flag unless you
have a specificreason not to, as hardware tends to under-report
supported levels."

Change-Id: I83614b0eab6166a42973f062e666783c2a8e7627

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

Change-Id: I19bc2fe4edef3c8dc7992473235f6ffd002c6e0b

Change-Id: I12148f354905cd888e284ab5583a80f9fe721248

Change-Id: Ieb61181e437278e1975fadfa9908c0bc413b1add

Change-Id: If641609b25cf6dad1a2c91fe534c2fa3a7119ad1

Change-Id: I5e328cc2d0e38aa26bf62cb3a5bd083d499b9a02

Change-Id: If509355da31d71e9301d463fbbd64c202530cdfc

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

If UPNP is enabled by the user, the UPNP controller must registered
only if the account is enabled.

Gitlab: #639

Change-Id: I993b50ea37fafa847460650d901ac3c3d5039718

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

Add logs to help debug ICE intialization issues

Gitlab: #619

Change-Id: If81067e2261cf7fbb054b4c9abe641e2ebc84a0a

After removing and re-adding a contact, the second conversation
will be deleted and the first conv will be recloned. However,
some text messages can be present. In this case, we can re-add
them.

Change-Id: I7cafcf76b5d36769ea939729a2fbf6730853cafb

cancel a file from the user should removes the file from the
waiting map to avoid to relaunch the download on the next sync.

Change-Id: I0696364d0131c8dde563b97b8b965e99d1f5686a

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

For now, the daemon doesn't handle the profile of the account nor
the compression. However, it does handle sendTrustRequest, which uses
the DHT to transmit requests. DHT values must be small, else it will
not be sent. So, this patch cache the compressed payload generated
by the client and removes it as soon as the confirmation is received.
This allow the daemon to retry to send request with the payload sent
originally.

Change-Id: I3fac542c6a53febdb7f1d0c516ec2d9ff5b317be

Change-Id: I14df750d459a0771f4e60923a1ecf3bfb938a78b

This is only to avoid to return weird states from the daemon to the
client. But if a conversation is added through addContact,
removeContact should be called to removes it. However, if
removeConversation() is called, the conversationId in contact's
details MUST be updated.
Same for acceptConversationRequest, this should removes related
trust requests

Change-Id: I4b273075862cdcdffc7f13c1b5e581a2eebc411d

Change-Id: I2af34ba8055903541d04d87c12082ffd03f47d8c

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

Change-Id: Ie12b5962f37f4e35aa3d2f71031bce605b24551a

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

Change-Id: Idda022b8085d15224fc41139fc5868eaf07900c0

Change-Id: I73484d9a5d060680c1b8f60121c3ae6021c5f6eb

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

While waiting for ICE initialization, the call state may change
and also the ICE instance. This patch handle a race between
ICE initiliazation and call removal

Gitlab: #619

Change-Id: I4a18a9901ddbd35969b85cf0b17213b1ac277b02

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

No need to start a thread pool for this.

Change-Id: Ifabb41549f6b0620f38cae4fd80af688bfc2e642

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

Instantiation and initialization of ICE are done in a single
stage (in the class constructor).
To initialize the ICE instance, connection information must
first be gathered asynchronously.
However, when sharing ICE media instance between subcalls,
it's better to have a valid ICE instance as soon as possible
(even if not fully initialized) to proceed with the call
initialization process, then wait for ICE initialization to start
the call.
Thus, the ICE instantiation will be performed synchronously as
soon as the parent (main) call is created, then it will be
initialized asynchronously when the connection info are ready.

Gitlab: #619

Change-Id: I9c97516238f1a690603975ec968c8c6733155d4a

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

Currently, when making an outgoing call to a Jami account with
multiple registered devices, a new ice media instance is created
for each subcall. This is not necessary, because all ice instances
will be similar until the peer answers (and provide its candidates)
But when the answer is received from the peer, all ice instances are
destroyed except the instance of the successful subcall, which will
be used to negotiate the media path.
Instead, only one instance will be created for the parent call, and
shared amongst the attached subcalls.

Gitlab: #619

Change-Id: I001c27f69d21b3ea640b189aea401e43c3f6bdef

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

This patch removes the temporary ICE shared pointer

Gitlab: #619

Change-Id: Icacac9df1102327d4d1a0f0d67dfa457016048cd

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

Make sure we unload plugin before trying to load it.

Change-Id: I87ac7b36378c0e70ecd101b68c8fcb8b7ea7fde8

Amin Bandali authored 3 years ago and Sébastien Blin committed 3 years ago

Change-Id: I8b64659932709aa5642ef88be4bd6707812f7148

When requesting destruction of ice session and stream
transport instances from PJNATH, some operation will be
done asynchronously through scheduled timers. If not
properly handled, the timer heap will still contain
timer entries when the timer heap and the IO queueu are
destroyed.
Now, the timer heap is given more time to flush the
remaining timer entries before the IO queue and the
timer heap are destructed.
The timer heap may still contain timer entries if
PJNATH does not process all the timers within the
givent max time (currently set to 3s).

Gitlab: #637

Change-Id: I5ef2fe9d824e8b57191a51fac8f9e53e0e626fcd

Change-Id: Id5bd0b744e5b6775dd08b31b39a1ddea01c2be0c

Pixel 4 XL, 720p:
before: 6.69 ms (14,9 fps)
after: 5.92 ms (16,9 fps)

Change-Id: I8a2bdbed7388efbf95b066ace2f8032684a87a2e

Change-Id: Iada2486cffef5be26eac5618b8e62349ca3b01cf

Change-Id: I1c3d2943f3347fa9214456a2e180b0836bd6420f