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

Aline Gondim Santos authored 3 years ago and Kateryna Kostiuk committed 3 years ago

GitLab: jami-client-ios#145
Change-Id: Ic4ae63ce2f1df1176c4a74339d1c3d82a9570ad5

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

Change-Id: I2bcbbf872b54262f8e4406fb01921a1ec07be3b3

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

Change-Id: I09876059293d18e25c34e755deafba8d224dc740

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

Change-Id: Ib5194ef6ca475df5be621c923d7660266cf7256e

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

Change-Id: I0c44b1a5fdd9727a8acf3d9deb88f9c2b5f71dd8

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

Change-Id: I1b21d80b7ea24bfc9334f2f63f3a57f0d4a57522

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

Change-Id: I59d9d812b6b5a2c66e2832328fbfdf663d9019af

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

Change-Id: I42fe3a4682bb9468ecf5417d6d9823e151e10bec

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

The agent will be written in Guile Scheme instead of C++ in
order to give maximum flexibility to developers of scenarios.
Thus, bindings will be added for the public Jami interface.

In other words, the agent will be a client of yet another
Jami's bindings.

Change-Id: Ic2cd333007d0b1aad56c02b116ea708b56e96cc5

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