- Jul 13, 2020
-
-
Change-Id: I321bdff614f1a90c5745cbedbebb89f0e0a1494f
-
Adrien Béraud authored
Change-Id: I94c88a504ae2a98043be8fd201f95227002d99c4
-
Adrien Béraud authored
Change-Id: Iffb7c8b4be4f084575e5e1a7bc6a02c86cb07fda
-
- Jul 09, 2020
-
-
Adrien Béraud authored
Change-Id: Iec1bb9a287d97dff8cc4342fe5ebf7d2238f10b4
-
Sébastien Blin authored
Change-Id: I67971c024245e95e870bfed320db160a9142ff39
-
Adrien Béraud authored
Change-Id: I990948900098449e37338bc6eed4ae4c4e110249
-
Adrien Béraud authored
Change-Id: Ic1f124297a2f5cc7f8409e3ff064a444ebe04a1a
-
Adrien Béraud authored
Change-Id: I5da233b3792215626fd82e827509ef95528e5be8
-
Sébastien Blin authored
Instead of letting the TURN session destroy itself when finished, the current code is overriding the user_data attached to the session. This is not needed because the turn session will be stopped when the timer will complete and this can cause some crashes in pj_turn_session_on_rx_pkt2 because the data is erased while not protected via turn_sock->grp_lock() (mostly in turn_sock.c, on_data_read) Change-Id: Ia4a12917711b5534b372cb3a26e9141e5393c569 Gitlab: #299
-
Sébastien Blin authored
The relay candidate was declared as suceeded even if not in the valid list. Because of this, some negotiations were successful but no valid candidates were given to the app. Moreover, the connection timeout checks were using the wrong timer. This avoids to cancel successful negotiations to check a connection timeout. Finally, some clean is done with this patch Change-Id: Iacfbf3b9f5faafe1bd05f66157485226761c30bf Gitlab: #256
-
- Jul 08, 2020
-
-
Sébastien Blin authored
if onTlsStateChange is called during destroy, callbacks can change between the check and the actual call. Change-Id: I8528205c25da76281e7e6bc9fdb3b9c0fbf596b2 Gitlab: #234
-
Albert Babí Oller authored
Change-Id: Ie24e29fc97f1f83cc0148c1c75788cef8f1008df
-
- Jul 07, 2020
-
-
Sébastien Blin authored
Change-Id: I936dc5577014ac551b5f8726a3d3b12be46c091f
-
Sébastien Blin authored
The same TID is used for all outgoing transfer (because it's the same file). So we should use a vector of transfer not a single outgoing transfer Change-Id: I3b492dc0198903672540a4365bfd32d6458970fd Gitlab: #259
-
Sébastien Blin authored
Change-Id: I4863d9d781634e3a15d75b030eaa8a0d08925f69 Gitlab: #246
-
Adrien Béraud authored
Change-Id: If047cc1e32a5cb04c5b6a5341c416be6db3ee7e4
-
Adrien Béraud authored
Gitlab: #225 Change-Id: I3874ba798ffa56c4f51b99048b9adb83f28bef16
-
Sébastien Blin authored
on iOS, the default value of an enum is not the first one, this means that requests for new channel are not working Change-Id: I190625bc34e94622c2e7d68d936818c204f96413
-
This patch prevent to filter a frame multiple time or a frame partially filtered. Change-Id: Ie120bc2a5a6d263fdc912cab365fc654dd71b0db Gitlab: #222
-
Change-Id: I0919a3a78f4066122773a2ee9ab85d8e406e7e8f
-
- Jul 06, 2020
-
-
Change-Id: If77d5cd33aae4607975caca46fd0a9f649975a54 Gitlab: #233
-
Adrien Béraud authored
Change-Id: Ib8b12f9f2133aa38ee3f48f805e8db78401faa9e
-
Avoid to be able to build if an old version of opendht is installed Change-Id: Iefcd2ba476ad3d7291a12bf112ab731c9962909a
-
This patch enables Jami to read the port of the turn server after the ':'. Change-Id: I045e3aa585b3d725445f666d2c9f8629501f124c Gitlab: #258
-
Adrien Béraud authored
Gitlab: #226 Change-Id: I058c851795f912f261f371afe3edc2f9f09a9ff5
-
Adrien Béraud authored
Change-Id: Ic61c5acaff60b015d1df92b5f1633a63f81bccd9
-
- Jul 03, 2020
-
-
Adrien Béraud authored
Change-Id: I4c6ea07a9d6734235e488a914bbaeeab01cee357
-
Pierre Duchemin authored
Change-Id: I72dcdecda2aab18c251f339d979bf72bda1af3e2
-
- Jul 02, 2020
-
-
Adrien Béraud authored
Change-Id: I1256fcb763bd4982714e9205078919d0d05a1e6b
-
Change-Id: Iceb7bb4ec8e710928b9399a75122db2f837d5491
-
Change-Id: I010069c97af03b8128c22765eb5814b2fb0a59c2 Gitlab: #254
-
Adrien Béraud authored
Change-Id: I6b97da0a32855dc8dc583a30883b31a647d20d15
-
Adrien Béraud authored
Change-Id: Iae41a073cfa5a1a842d8025477539db833f506b8
-
Adrien Béraud authored
Change-Id: Ibd8a93dceb1dc3fb959cdc6c874aae7da5514647
-
- Jul 01, 2020
-
-
Change-Id: I26660bccd3ab150687c118e22edc27d9e9f9e333
-
- Jun 30, 2020
-
-
Adrien Béraud authored
Change-Id: I0af605825cd6cc80bf6bb5cbc05fdb8e81185a39
-
Adrien Béraud authored
Change-Id: I0895410c9a3cb602e10ed8911545c3ad9e77b53f
-
- Jun 29, 2020
-
-
Sébastien Blin authored
TCP_KEEPALIVE are not enough to detect that TCP connections are dead or not. Some routers doesn't seems to support TCP_KEEPALIVE and moreover, sometimes the settings is just not enough as described in this article: https://blog.cloudflare.com/when-tcp-sockets-refuse-to-die/ RFC 5482 describe a new option for sockets: TCP_USER_TIMEOUT which must be used with keep alives to detect closed connection in a better way. In this patch we set TCP_USER_TIMEOUT to 30 seconds (like the keep alive). This is a TCP level socket option used to specify the max time in ms that transmitted data can be unacknowledged before a force close. Change-Id: I217616b9b9e08adfa5a044a451fbbc97faf1939e Gitlab: #243
-
Change-Id: I64783d990cf463a5a873314c978e42a7b19bb55b Gitlab: #228
-
- Jun 28, 2020
-
-
Change-Id: I9d1d1a53070228b93728655021cdf1764b5eb6b2 Gitlab: #238
-