jami-daemon issueshttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues2020-06-29T14:11:47Zhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/229EPIC - Improve video quality for weak connections2020-06-29T14:11:47ZGuillaume HellerEPIC - Improve video quality for weak connectionsThe video quality should be good (ideally without any visible glitch) even on weak ADSL connexions (800 kbps upload or less).
We first need to analyze and characterize the quality issues experienced by users on these types of connections...The video quality should be good (ideally without any visible glitch) even on weak ADSL connexions (800 kbps upload or less).
We first need to analyze and characterize the quality issues experienced by users on these types of connections. Then suggest and implement solutions adapted to the context.Iteration 18Pierre LespagnolMohamed ChibaniPierre Lespagnolhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/228File transfer: multiple improvements2020-06-29T15:07:19ZSébastien BlinFile transfer: multiple improvements+ [ ] Remove eventloop from PeerConnection
+ [ ] Fix potential resources deadlocks
+ [ ] Fix mutex usage
+ [ ] Channeled File Transfer to avoid ICE negotiation when possible.+ [ ] Remove eventloop from PeerConnection
+ [ ] Fix potential resources deadlocks
+ [ ] Fix mutex usage
+ [ ] Channeled File Transfer to avoid ICE negotiation when possible.Iteration 18Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/226Support OAuth authentication with server account manager2020-07-07T20:07:05ZAdrien BéraudSupport OAuth authentication with server account managerIteration 18Adrien BéraudAdrien Béraudhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/224Random call drops2020-07-10T14:12:21ZAdrien BéraudRandom call dropsIn many cases the call drops (ends) unexpectedly without obvious reasons.In many cases the call drops (ends) unexpectedly without obvious reasons.Iteration 18Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/223Audio lost after 5min2020-08-14T17:10:41ZGuillaume HellerAudio lost after 5minIn some cases (not identified yet), the audio is lost exactly after 5min.
It can also happens that the video freezes, but the audio remains.In some cases (not identified yet), the audio is lost exactly after 5min.
It can also happens that the video freezes, but the audio remains.Iteration 18Mohamed ChibaniMohamed Chibanihttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/222Recording video calls crash after some time2020-07-07T20:06:36ZAdrien BéraudRecording video calls crash after some timeIteration 18Pierre LespagnolPierre Lespagnolhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/221Video rotation not considered in recorded video2020-06-20T17:34:20ZAdrien BéraudVideo rotation not considered in recorded videoIteration 18Pierre LespagnolPierre Lespagnolhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/262Received pictures are not displayed - Android Beta 20200703-012020-07-09T00:50:06ZCyrille BéraudReceived pictures are not displayed - Android Beta 20200703-01Iteration 19Adrien BéraudPierre DucheminAdrien Béraudhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/259File transfer and multi device, "already accepted" + cancelled2020-07-17T14:25:42ZSébastien BlinFile transfer and multi device, "already accepted" + cancelled# Reproduce step
+ Account B got 2 devices connected to account A
+ A sends a file
+ B receives the file request on both devices, but A cancels the transfer# Reproduce step
+ Account B got 2 devices connected to account A
+ A sends a file
+ B receives the file request on both devices, but A cancels the transferIteration 19Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/258No way to use a custom turn server port2020-07-16T18:48:33ZBrando TovarNo way to use a custom turn server port**Evironment details:**
* OS: Ubuntu 20.04
* Jami version: Jami from jami.net for ubuntu 20.04
**Steps to reproduce**
* Set your own turn server using these instructions: https://git.jami.net/savoirfairelinux/ring-project/wikis/technica...**Evironment details:**
* OS: Ubuntu 20.04
* Jami version: Jami from jami.net for ubuntu 20.04
**Steps to reproduce**
* Set your own turn server using these instructions: https://git.jami.net/savoirfairelinux/ring-project/wikis/technical/3.6-Setup-your-own-TURN-server
* Update turn configuration on Jami advance settings with: IPOfTurnServer:customPort
* Then trying to make a call using turn only will not work and the logs will show this line: `[ice] added turn server 'IPOfTurnServer', port 3478`
The solution is to use 3478 as the listening port on the turnserver.conf than everything will work as intended.Iteration 19Brando TovarBrando Tovarhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/256Stuck in Connecting: Some negotiations are blocked2020-07-16T18:48:37ZSébastien BlinStuck in Connecting: Some negotiations are blockedRelated to https://git.jami.net/savoirfairelinux/ring-daemon/issues/227
# Observation
The ice become complete too soon with no valid pairs:
@@@ Updating States
@@@ on_ice_complete
[1593797289.007|37053|manager.cpp :243 ] 13:28...Related to https://git.jami.net/savoirfairelinux/ring-daemon/issues/227
# Observation
The ice become complete too soon with no valid pairs:
@@@ Updating States
@@@ on_ice_complete
[1593797289.007|37053|manager.cpp :243 ] 13:28:09.007 sip:1018943881119817 ...ICE process complete, status=Success
[1593797289.007|37053|manager.cpp :243 ] 13:28:09.007 sip:1018943881119817 ...Valid list
(called a second time after that when negotiation is done
# Reproduce steps
still unknownIteration 19Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/249Stuck in Searching: Listen on Call ICE is not responding2020-07-09T20:19:50ZSébastien BlinStuck in Searching: Listen on Call ICE is not respondingRelated to https://git.jami.net/savoirfairelinux/ring-daemon/issues/227
# Reproduce steps
Unknown
# Observations
+ Device A calls device B with the bug
+ device B answer its ICE for the PeerConnection request, but not for the DHT ICE...Related to https://git.jami.net/savoirfairelinux/ring-daemon/issues/227
# Reproduce steps
Unknown
# Observations
+ Device A calls device B with the bug
+ device B answer its ICE for the PeerConnection request, but not for the DHT ICE candidates request
+ First call is failing. No fallback done because we are still in the SEARCHING state. Second call will succeed. Because the Peer negotiation is done without issue. However all first calls to device B will failIteration 19Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/248Stuck in Connecting/Searching: timeout duration2020-07-02T20:06:29ZSébastien BlinStuck in Connecting/Searching: timeout durationRelated to https://git.jami.net/savoirfairelinux/ring-daemon/issues/227
Actually ICE_NEGOTIATION_TIMEOUT is 60 seconds. This is pretty long and the user will close the window before thisRelated to https://git.jami.net/savoirfairelinux/ring-daemon/issues/227
Actually ICE_NEGOTIATION_TIMEOUT is 60 seconds. This is pretty long and the user will close the window before thisIteration 19Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/247Stuck in Searching/Connecting: Resolve the two requests mystery2020-07-02T20:06:32ZSébastien BlinStuck in Searching/Connecting: Resolve the two requests mysteryRelated to https://git.jami.net/savoirfairelinux/ring-daemon/issues/227
# Reproduce steps
1. device B cut its connectivity
2. device A calls device B (with the connecting lock, cf https://git.jami.net/savoirfairelinux/ring-daemon/issue...Related to https://git.jami.net/savoirfairelinux/ring-daemon/issues/227
# Reproduce steps
1. device B cut its connectivity
2. device A calls device B (with the connecting lock, cf https://git.jami.net/savoirfairelinux/ring-daemon/issues/243)
3. device A is blocked in "Searching"
4. after a while, device B is back online
5. device A receives 2 ICE response
# Expected results
Only one answer should be received (the one from the fallback request)Iteration 19Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/246Stuck in Searching/Connecting: Improve logs2020-07-07T17:49:52ZSébastien BlinStuck in Searching/Connecting: Improve logsEverything is in the title. The negotiation of a call can be quite complex to understand and logs should be understandable, moreover if the call fails.
Related to https://git.jami.net/savoirfairelinux/ring-daemon/issues/227Everything is in the title. The negotiation of a call can be quite complex to understand and logs should be understandable, moreover if the call fails.
Related to https://git.jami.net/savoirfairelinux/ring-daemon/issues/227Iteration 19Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/244Stuck in Connecting/Searching: Re-add timeouts2020-07-02T20:06:34ZSébastien BlinStuck in Connecting/Searching: Re-add timeoutsBecause we removed the eventloop to check pending calls, timeout are not checked and only done on successfully negotiated ICE. We should check re-add timeout to avoid any lock in SEARCHING or CONNECTING.
Related to https://git.jami.net/...Because we removed the eventloop to check pending calls, timeout are not checked and only done on successfully negotiated ICE. We should check re-add timeout to avoid any lock in SEARCHING or CONNECTING.
Related to https://git.jami.net/savoirfairelinux/ring-daemon/issues/227
# Reproduce Steps
1. device B cut its connectivity
2. device A calls device B
5. device A is blocked in "Searching"
# Expected result
When ICE_NEGOTIATION_TIMEOUT is reached, the searching window should be closedIteration 19Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/243Stuck in Connecting: Closed sockets are not detected all the time2020-07-02T20:06:36ZSébastien BlinStuck in Connecting: Closed sockets are not detected all the timeRelated to https://git.jami.net/savoirfairelinux/ring-daemon/issues/227
# Reproduce Steps
1. device A calls device B
2. Call is working
3. device B cut its connectivity
4. device A calls device B
5. device A is blocked in "Connecting"
...Related to https://git.jami.net/savoirfairelinux/ring-daemon/issues/227
# Reproduce Steps
1. device A calls device B
2. Call is working
3. device B cut its connectivity
4. device A calls device B
5. device A is blocked in "Connecting"
# Expected result
Jami should detect that the socket is unusable and stop the call if fallback fails
+ icecb.on_destroy should be calledIteration 19Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/225Add support for searching a JAMS user repository2020-07-13T14:11:56ZAdrien BéraudAdd support for searching a JAMS user repositoryShould be possible to search existing and new users by their first name, last name or username. Results should be returned in a predictive display (display up to 5 results to avoid having too many results)
The list of results should als...Should be possible to search existing and new users by their first name, last name or username. Results should be returned in a predictive display (display up to 5 results to avoid having too many results)
The list of results should also contains the avatar of the users (even for new users)
Example:
![contact_search](/uploads/09d4b6cbd56f62000422d7c925765438/contact_search.png)Iteration 19Adrien BéraudAdrien Béraudhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/273Sound & Conference: If one member is in hold, the sound is cut for the others...2020-08-12T14:53:30ZSébastien BlinSound & Conference: If one member is in hold, the sound is cut for the others participants# Reproduce Steps
Do a conference between 3 devices
A participant switch the conference in hold
# Expected result
The others should be able to speak together
# Current result
No sound for the other participant# Reproduce Steps
Do a conference between 3 devices
A participant switch the conference in hold
# Expected result
The others should be able to speak together
# Current result
No sound for the other participantItération 20Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/272Sound & Conference: Adding somebody cut the sound during 2/3 seconds2020-08-12T14:53:31ZSébastien BlinSound & Conference: Adding somebody cut the sound during 2/3 seconds# Reproduce steps
+ Add someone in the conference
# Expected result
The sound should continue
# Current result
Sometimes, during a few seconds the sound is cut# Reproduce steps
+ Add someone in the conference
# Expected result
The sound should continue
# Current result
Sometimes, during a few seconds the sound is cutItération 20Sébastien BlinMohamed ChibaniSébastien Blin