savoirfairelinux issueshttps://git.jami.net/groups/savoirfairelinux/-/issues2022-01-05T18:21:56Zhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/666Call re-invite - restart media only after successful ICE negotiation2022-01-05T18:21:56ZSébastien BlinCall re-invite - restart media only after successful ICE negotiationIf media transport uses ICE, and when a new media session is negotiated (incoming or outgoing re-invite) the current ICE session must be kept until the new ICE session is successfully negotiated, and the media is stopped and restarted us...If media transport uses ICE, and when a new media session is negotiated (incoming or outgoing re-invite) the current ICE session must be kept until the new ICE session is successfully negotiated, and the media is stopped and restarted using the new ICE session.
If the new session fails, the media transport must continue using the current ICE session.
# Scenario
+ In a call cut video
# Expected
+ the remote video should not be cut and retrieved a few secs after
# Current
During the negotiation remote video/audio is stopped and a glitch is seenMohamed ChibaniMohamed Chibanihttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/638Conference - Handle media change request (for host and remote participants)2022-01-05T18:21:51ZSébastien BlinConference - Handle media change request (for host and remote participants)# Scenario 0 - Bob account is in RDV mode
+ Alice calls rdv-bob
+ Carla calls rdv-bob
- Expected result:\
Bob is in detached mode, and local audio/video is in muted state
# Scenario 1 - Bob account is in RDV mode
+ Alice calls rdv-bob ...# Scenario 0 - Bob account is in RDV mode
+ Alice calls rdv-bob
+ Carla calls rdv-bob
- Expected result:\
Bob is in detached mode, and local audio/video is in muted state
# Scenario 1 - Bob account is in RDV mode
+ Alice calls rdv-bob in audio only
+ Alice upgrades to video
- Expected result:\
Alice should receives her video along with the other videos (from participants)
# Scenario 2 - Bob account is in RDV mode
+ Alice and Carl call rdv-bob
+ Bob joins the conference
- Expected result:\
Bob local audio should be added\
Bob local video (camera) should be added (and un-muted) if enabled in the account
# Scenario 3 - Bob account is in RDV mode
+ Alice and Carl call rdv-bob in audio only
+ Bob joins the conference
- Expected result:\
Bob local audio should be added\
Bob local video (camera) should be added (and un-muted) if enabled in the account
Alice and Carla should not receive video from conference unless they join with their video
# Scenario 4 - Bob account is in RDV mode
+ Alice call rdv-bob
+ Carla call rdv-bob in audio only
- Expected result:\
Carla should not receive video from conference unless she join with her video
# Scenario 5
+ Bob is on a call with Alice
+ Carla calls Bob (or the opposite). Alice's is put on-hold.
+ Bob joins Alice's call to create a conference
- Expected result:\
Bob local audio should be un-muted unless both calls where muted\
Bob local video should be un-muted unless both calls where muted. Does not apply if the video is disabled.Mohamed ChibaniMohamed Chibanihttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1377Photo is not uploaded2022-01-05T17:05:08ZAmer Cristian MikkiPhoto is not uploadedJami on IOS, I try to attached a photo to send it but is not working! I have iphone 13pro and is has last ios update!Jami on IOS, I try to attached a photo to send it but is not working! I have iphone 13pro and is has last ios update!https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1046Overview: LocationSharing2022-01-04T16:05:28ZMaxime CalletOverview: LocationSharing## Android location sharing
This issue wants to regroup in one all the known bugs and features request available. This is done to give a general overview on how the sharing location feature must be improved and give a better global visi...## Android location sharing
This issue wants to regroup in one all the known bugs and features request available. This is done to give a general overview on how the sharing location feature must be improved and give a better global visibility to team members and users.
## Current bugs
- [ ] Fix cross platform location sharing (ios/android)
- [ ] Location sharing does not always show when you open the conversation and you have to click on the notification¨
- [ ] ...
- [ ] ...
## Features request pool
- [ ] the Map should be contained in a card like a message or a link [#960](https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/960)
- [ ] ...
- [ ] ...Maxime CalletMehdi GhayourKateryna KostiukAdrien BéraudAmirhossein NaghshzanMaxime Callethttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/621Provide parameters for pulseaudio's echo-cancel-module2022-01-04T16:03:10ZAmin BandaliProvide parameters for pulseaudio's echo-cancel-moduleWe currently don't set any additional arguments for pulseaudio's echo canceller module:
https://git.jami.net/savoirfairelinux/ring-daemon/-/blob/504e54608267a257e14acc84daea236b1fd4f85a/src/media/audio/pulseaudio/audiostream.cpp#L59
V...We currently don't set any additional arguments for pulseaudio's echo canceller module:
https://git.jami.net/savoirfairelinux/ring-daemon/-/blob/504e54608267a257e14acc84daea236b1fd4f85a/src/media/audio/pulseaudio/audiostream.cpp#L59
Various GNU/Linux distributions such as Debian and its derivatives don't load the echo canceller module in `/etc/pulseaudio/default.pa` at all or with any additional parameters, so we can't rely on that.
We should look into providing additional arguments -- like the ones below -- ourselves when creating the pulseaudio stream.
For reference: example of loading the echo canceller module with additional arguments in a pulseaudio config file (thanks @atraczyk):
```
load-module module-echo-cancel use_volume_sharing=1 use_master_format=1 aec_method=webrtc aec_args="digital_gain_control=1 experimental_agc=1 analog_gain_control=0 noise_suppression=1 voice_detection=1 extended_filter=1" source_name=echoCancel_source sink_name=echoCancel_sink
```https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/413jami-qt --minimized not working2022-01-04T14:50:56Zalzxjami-qt --minimized not workingI've just updated Jami, now in KDE there is `jami-qt`! Nice.
At login, I need to start Jami after some pulseaudio tweaks. `jami-qt --minimized` should hide it, but it doesn't, the program window is still showing.
I'm using Debian Buste...I've just updated Jami, now in KDE there is `jami-qt`! Nice.
At login, I need to start Jami after some pulseaudio tweaks. `jami-qt --minimized` should hide it, but it doesn't, the program window is still showing.
I'm using Debian Buster with KDE.
some debug info:
```
$ jami-qt --debug --minimized
"notify server name: Plasma, vendor: KDE, version: 2.0, spec: 1.1"
No migration required
Screen saver dbus interface: "org.freedesktop.ScreenSaver"
NetworkManager client initialized, version: 1.14.6 , daemon running: yes , networking enabled: yes
primary network connection: 3e262bf9-4060-3d12-a2a6-0200e14a4ba7 default: yes
QDBusMarshaller: type `VectorString' attempts to redefine basic D-BUS type 'as' (QStringList) (Did you forget to call beginStructure() ?)
QDBusMarshaller: type `MapStringVectorString' produces invalid D-BUS signature `a{s}' (Did you forget to call beginStructure() ?)
QDBusMarshaller: type `QMap<QString,MapStringVectorString>' produces invalid D-BUS signature `a{s}' (Did you forget to call beginStructure() ?)
```
```
$ gdb --args jami-qt --minimized
GNU gdb (Debian 8.2.1-2+b3) 8.2.1
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from jami-qt...(no debugging symbols found)...done.
(gdb) r
Starting program: /usr/bin/jami-qt --minimized
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffe6964700 (LWP 23013)]
[New Thread 0x7fffdc4a7700 (LWP 23014)]
[New Thread 0x7fffdbca6700 (LWP 23015)]
[New Thread 0x7fffdb4a5700 (LWP 23016)]
[New Thread 0x7fffdac63700 (LWP 23017)]
[New Thread 0x7fffd9a22700 (LWP 23018)]
[New Thread 0x7fffd9221700 (LWP 23019)]
"notify server name: Plasma, vendor: KDE, version: 2.0, spec: 1.1"
[New Thread 0x7fffd8a20700 (LWP 23020)]
[New Thread 0x7fffc3fff700 (LWP 23021)]
No migration required
[New Thread 0x7fffc3342700 (LWP 23022)]
Screen saver dbus interface: "org.freedesktop.ScreenSaver"
[New Thread 0x7fffc0e82700 (LWP 23023)]
[Detaching after fork from child process 23024]
[Detaching after fork from child process 23025]
[New Thread 0x7fffaffff700 (LWP 23026)]
[New Thread 0x7fffaf7fe700 (LWP 23027)]
[New Thread 0x7fffaeffd700 (LWP 23028)]
[New Thread 0x7fffae7fc700 (LWP 23029)]
[New Thread 0x7fffadffb700 (LWP 23030)]
[New Thread 0x7fffacff9700 (LWP 23032)]
[New Thread 0x7fffad7fa700 (LWP 23031)]
[New Thread 0x7fff9bfff700 (LWP 23033)]
[New Thread 0x7fff9b7fe700 (LWP 23034)]
[New Thread 0x7fff9affd700 (LWP 23035)]
NetworkManager client initialized, version: 1.14.6 , daemon running: yes , networking enabled: yes
primary network connection: 3e262bf9-4060-3d12-a2a6-0200e14a4ba7 default: yes
[New Thread 0x7fff9a7fc700 (LWP 23036)]
[New Thread 0x7fff99ffb700 (LWP 23037)]
[New Thread 0x7fff997fa700 (LWP 23038)]
QDBusMarshaller: type `VectorString' attempts to redefine basic D-BUS type 'as' (QStringList) (Did you forget to call beginStructure() ?)
QDBusMarshaller: type `MapStringVectorString' produces invalid D-BUS signature `a{s}' (Did you forget to call beginStructure() ?)
QDBusMarshaller: type `QMap<QString,MapStringVectorString>' produces invalid D-BUS signature `a{s}' (Did you forget to call beginStructure() ?)
[New Thread 0x7fff98ff9700 (LWP 23039)]
[Detaching after fork from child process 23040]
[New Thread 0x7fff6bfff700 (LWP 23057)]
[New Thread 0x7fff6b7fe700 (LWP 23064)]
[Thread 0x7fffd9a22700 (LWP 23018) exited]
```Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1373A typo in Jami Privacy Policy2022-01-03T15:43:01ZA typo in Jami Privacy PolicyIn the Jami privacy policy shown on `jami.net`
A sentence reads "We use TSL/SRTP to secure connection and communications over the network."
It should be "We use **TLS**/SRTP to secure connection and communications over the network."
Than...In the Jami privacy policy shown on `jami.net`
A sentence reads "We use TSL/SRTP to secure connection and communications over the network."
It should be "We use **TLS**/SRTP to secure connection and communications over the network."
Thank you!https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/637Chat History No Longer Visible2021-12-30T23:28:08ZvindicatorrChat History No Longer VisibleBug report form
---------------
## Describe your environment
Please specify the following:
- OS: Arch linux
- Jami version: 202112271445
- What build you are using: [your own (daemon:02c5cecd363a1ee25a914d72e243d7903e44969b; lrc:48db6...Bug report form
---------------
## Describe your environment
Please specify the following:
- OS: Arch linux
- Jami version: 202112271445
- What build you are using: [your own (daemon:02c5cecd363a1ee25a914d72e243d7903e44969b; lrc:48db64cbcd3a8d7a12cad940694ce9239b8db576; client-qt:83f68573324a453a6d26e025fd6439f175a79d1b]
## Steps to reproduce
Note: Better the scenario is, better we will be able to reproduce and debug.
- Can you reproduce the bug: [at will]
- Steps:
1. Send messages between clients
- Actual result: Android device sees all messages while client-qt doesn't see any, including what client-qt sent, including emojis.
- Expected result: Show the history
## Additional information
This is a continuation of my testing and it began with chat history showing for the previous contacts I paired with.
I deleted those old contact histories and removed the accounts, then paired the latest created android contact.
I sent that android contact a message. The message was received and also showed in client-qt.
Then I think I was about to send a message from android, but from the side of my eye, I noticed my qt history went blank.
Heh, I see the messages DO exist in `/home/username/.local/share/jami/<id>/conversations/<id>/.git/`. Interesting way to go about it, but something I like if a contact edits or deletes their message, it will (ideally) still exist in the log.
Screenshots/videos/logs/etc
![Screenshot_20211227_224126](/uploads/cd8b4e4bb7e964bb5786816ccf8fba8f/Screenshot_20211227_224126.png)
Sample from the conversation git log:
```
commit <id>
Author: <name> <<id>>
Date: Tue Dec 28 04:22:46 2021 +0000
{"body":"Where did my message go?","type":"text/plain"}
```
`$ jami-qt -d`:
```
"notify server name: Plasma, vendor: KDE, version: 5.23.4, spec: 1.2"
qt.webenginecontext:
GLImplementation: desktop
Surface Type: OpenGL
Surface Profile: NoProfile
Surface Version: 3.0
Using Default SG Backend: yes
Using Software Dynamic GL: no
Using Angle: no
Init Parameters:
* application-name Jami
* browser-subprocess-path /usr/lib/qt6/QtWebEngineProcess
* d
* disable-features DnsOverHttpsUpgrade,ConsolidatedMovementXY,InstalledApp,BackgroundFetch,WebOTP,WebPayments,WebUSB,PictureInPicture
* disable-setuid-sandbox
* disable-speech-api
* disable-web-security
* enable-features NetworkServiceInProcess,TracingServiceInProcess
* enable-main-frame-before-activation
* enable-threaded-compositing
* gpu-preferences UAAAAAAAAAAoAAAQAAAAAAAAAAAAAAAAAABgAAAAAAAwAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAgAAAAAAAAACAAAAAAAAAAAAAAAAAAAAAIAAAAAAAAAAgAAAAAAAAACAAAAAAAAAA=
* in-process-gpu
* lang en
* no-sandbox
* num-raster-threads 2
* single-process
* use-gl desktop
No migration required
Can't open file: "/home/username/.local/share/jami/<id>/profile.vcf"
Screen saver dbus interface: "org.freedesktop.ScreenSaver"
Syncing lrc accounts list with the daemon
lookup name NOT FOUND: "" "<id>"
NetworkManager client initialized, version: , daemon running: no , networking enabled: no
no primary network connection detected, check network settings
NewAccountModel::getAccountInfo, can't find dummy ; Using default avatar
NewAccountModel::getAccountInfo, can't find dummy ; Using default avatar
qrc:/src/mainview/MainView.qml:372:5: QML WelcomePage: StackView has detected conflicting anchors. Transitions may not execute properly.
```
The last line came about when I clicked on my contact.
For retrieving logs, cf [this page](https://git.jami.net/savoirfairelinux/ring-project/wikis/tutorials/Bug-report-guide#logs).
EDIT0: Actually, while I'm here and mentioning the git conversations, why isn't all of that ~/.local stuff also encrypted? Is the password only used to encrypt the backup? If so, why is it even asked on account creation and not just at backup? I'd think the password would have everything encrypted in the respective ~/.local/... path.https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/640`End call` shows after the call has ended2021-12-30T10:16:18Zovari`End call` shows after the call has ended1. Right-click on a contact and the following shows<br>
![image](/uploads/4e61b1240bb1cdabbe58dc9a09053b38/image.png)
1. Call a contact
1. End the call
1. Right-click on the contact and the options shown in dot point 1 should show; howev...1. Right-click on a contact and the following shows<br>
![image](/uploads/4e61b1240bb1cdabbe58dc9a09053b38/image.png)
1. Call a contact
1. End the call
1. Right-click on the contact and the options shown in dot point 1 should show; however, the following 2 options show (yet there is no call)<br>
![image](/uploads/783778ab96388ced6a4d489a37c6f846/image.png)
Are you able to reproduce? and please fix?
Thank you
Linux Mint 20.3 Cinnamon beta<br>
jami-client-qt deb edition from jami.net Version: 202112221430https://git.jami.net/savoirfairelinux/jami-project/-/issues/855Confused audio in multiparty video conference - please add control/audio allo...2021-12-30T09:05:51ZCosmic37Confused audio in multiparty video conference - please add control/audio allocation/handsup flagHi, many of us are loving jami and thanks for your fantastic work! I would observe that a possible improvement which may help attract and retain users is if the video conference audio control could work better because with three or more ...Hi, many of us are loving jami and thanks for your fantastic work! I would observe that a possible improvement which may help attract and retain users is if the video conference audio control could work better because with three or more parties it can sometimes get garbled. If I understand correctly it seems that audio streams are all merged. This is problematic for many parties. I think it would be better if central audio allocation were controlled by the video conference initiator or host. Other parties could raise a flag/ hands up icon to signify they have something to say and then the controlling party could switch audio accordingly. This could be better for multiparty comms. If not the default then maybe this functionality could be an option "Start video call with audio allocation"Jami for educationAline Gondim SantosMaxime CalletKateryna KostiukAline Gondim Santoshttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/613Wrong microphone used for audio and video call2021-12-29T21:27:04Zring userWrong microphone used for audio and video call- Jami Version: Live Free or Die 20190602-01 (from F-Droid)
- Android Version: LineageOS 16 (Android 9), no GApps
- Smartphone: Samsung Galaxy S5 (klte)
If I make or receive an audio or video call, I have to talk loud and close to the m...- Jami Version: Live Free or Die 20190602-01 (from F-Droid)
- Android Version: LineageOS 16 (Android 9), no GApps
- Smartphone: Samsung Galaxy S5 (klte)
If I make or receive an audio or video call, I have to talk loud and close to the microphone at the top of my smartphone. I didn't even notice there is a second microphone at that place before.
I would expect to be able to use the mike at the button of my phone.
In a normal call without Jami I can use the "normal" microphone at the button.
Another problem is, that during an video call I have to speak directly into that micro. If I'm looking at the video stream, I'm too far away from the mike so the other user can't hear me.
Settings:
- Mobile Data: enabled (but not used for the tests)
- HD-Video: enabled
- Hardware-Acceleration: enabled
- Use system contacts: disabled
- Normal phone calls via Jami: disabled
- Start Jami while booting: enabled
- Run Jami in background: enabledBackloghttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/201ffmpeg: add G711, G729 codecs (SIP)2021-12-29T21:26:12Zovariffmpeg: add G711, G729 codecs (SIP)Please add the following codecs to Jami:
* [G.711a](https://en.wikipedia.org/wiki/G.711)
* [G.711u](https://en.wikipedia.org/wiki/G.711)
* [G.729a](https://en.wikipedia.org/wiki/G.729)
What do you think?
Thank you
> MyNetFone uses th...Please add the following codecs to Jami:
* [G.711a](https://en.wikipedia.org/wiki/G.711)
* [G.711u](https://en.wikipedia.org/wiki/G.711)
* [G.729a](https://en.wikipedia.org/wiki/G.729)
What do you think?
Thank you
> MyNetFone uses the **G.711a** codec, it is the standard codec used in Australia and Europe. The **G.711u** codec is used within the US, and may be present in PBXs or UC platforms from US vendors. The **G.729a** codec is often used for conference calling services.<br>
> https://www.mynetfone.com.au/support/faq/question/477
> The patents for G.711, released in 1972, have expired, so it may be used without the need for a licence
> https://en.wikipedia.org/wiki/G.711#Licensing
> As of January 1, 2017, the patent terms of most licensed patents under the G.729 Consortium have expired, the remaining unexpired patents are usable on a royalty-free basis.<br>
> https://en.wikipedia.org/wiki/G.729.1
https://git.jami.net/savoirfairelinux/ring-daemon/issues/200Backloghttps://git.jami.net/savoirfairelinux/jami-project/-/issues/822Feature Request: Push To Talk Key & Open Mic Options2021-12-29T21:25:39ZtrymeoutFeature Request: Push To Talk Key & Open Mic OptionsA cool thing to add for voice and video calls would be the ability to set a push-to-talk key for desktop (Windows, Mac, Linux) and to allow an open mic option and to add settings to configure your mic. Similar to gaming VOIP apps like Te...A cool thing to add for voice and video calls would be the ability to set a push-to-talk key for desktop (Windows, Mac, Linux) and to allow an open mic option and to add settings to configure your mic. Similar to gaming VOIP apps like TeamSpeak and Mumble.
This will allow less noise during calls and will allow users to have more privacy features on their audio during a call.Backloghttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/288Connectivity: be more resilient if a TURN server is not available2021-12-29T21:18:42ZSébastien BlinConnectivity: be more resilient if a TURN server is not available# Reproduce steps
+ In the settings change the turn address to something that will not work but resolvable (ex: enconn.fr)
+ Try to do a call
# Expected results
+ The call should work as soon as possible with the TURN ignored
# Curre...# Reproduce steps
+ In the settings change the turn address to something that will not work but resolvable (ex: enconn.fr)
+ Try to do a call
# Expected results
+ The call should work as soon as possible with the TURN ignored
# Current result
+ The client try to connect to the TURN server for each ICE and result with a timeout of several seconds (~20 on linux) for each ICE negotiations making the call just unusable
# Why?
When making a call, the first step is to gather all candidates and send this message through the DHT (or direct p2p connection if available). But to gather the TURN candidate, pjsip needs to connect to it and ask for a new session. For TCP connections, the connect() will take a lot of time to timeout (depending on /proc/sys/net/ipv4/tcp_syn_retries), for UDP I didn't dig enough to fully understand what pjsip is waiting, but I think it's something related to that candidate allocation.
# Solutions
Several solutions can be created:
1. (pjsip specific) A new timer for TURN candidate creation can be created inside pjsip, to be able to ignore TURN candidates if it's taking too long. Because Jami is a real time communication app, if the allocation is taking more than 3 seconds, this means that we are taking too much time and it's not acceptable.
2. (system + pjsip specific) Manually set the connection timeout on the sockets. For TCP, we need to do a setsockopt on TCP_SYNCNT. 2 SYN retries is acceptable imho (that's about 3 seconds. First packet + 1 retry). A solution need to be created for platforms not supporting this op. For UDP as I didn't dig enough, I don't really know what's really blocking so this will need further investigation
3. (best solution imho) Support the RFC for Trickle ICE. I don't really like 1 or 2 because sometimes TURN can work and we will ignore that fact if it's taking too long. Trickle ICE will allow us to send candidates as soon as it's gathered. This means we will be able to send separately host candidates, UPnP, relays like TURN. This is clearly the solution that will take the more time to implement, but the best solution imho.
Note for 3: the drawback I see is that, because we will send candidates separately, this will generate multiple values on the DHT instead of one. Which is a bit bad.Backloghttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/796Android - Audio is not automatically routed to headsets when plugged2021-12-29T21:11:09ZMohamed ChibaniAndroid - Audio is not automatically routed to headsets when pluggedOn Android, if a call is started on loudspeakers, the audio is not automatically routed to the headset if it's plugged. The user has to tap on the speaker icon on the UI, to manually route the audio to the headset.On Android, if a call is started on loudspeakers, the audio is not automatically routed to the headset if it's plugged. The user has to tap on the speaker icon on the UI, to manually route the audio to the headset.Backloghttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1122Audio issue using specifically one output device2021-12-29T20:38:01ZElysAudio issue using specifically one output deviceI've updated all Jami apps to the latest version (Windows 10, Android).
If you make a video call between android smartphone and android tablet the audio always works fine.
However if you make a video call between pc and any android dev...I've updated all Jami apps to the latest version (Windows 10, Android).
If you make a video call between android smartphone and android tablet the audio always works fine.
However if you make a video call between pc and any android device (tablet or smartphone) the voice input from pc has 2-3 second delay before you can hear the sound on the android device. This does not affect the sound quality. (Just audio and video are out of sync)
BUT: On the other side: The sound of the android device can be heard immediately without any delay but you can't recognize the input sound - it sounds complete different and you mainly hear noise.
This always happens and there is no way I found out to fix this issue.
I tried to change all (audio) settings but it didn't help.Backloghttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/417UPNP - Change port allocation/mapping policy for media (RTP/RTCP ports)2021-12-29T20:36:35ZMohamed ChibaniUPNP - Change port allocation/mapping policy for media (RTP/RTCP ports)RTP and RTCP port numbers are determined using port ranges from user configuration. The ranges are configured per media type (audio and video). The current behavior has few issues such:
- The configuration is limited to 2 streams: one au...RTP and RTCP port numbers are determined using port ranges from user configuration. The ranges are configured per media type (audio and video). The current behavior has few issues such:
- The configuration is limited to 2 streams: one audio stream and one video stream.
- Pre-defined port numbers will conflict with UPNP port mappings.
The required changes are as follows:
- Remove the restriction of media stream count to 2 streams.
- Do not use pre-defined port when requesting UPNP ports.
- Configuration of media port ranges should not be necessary anymore.Backloghttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/424ICE/PJNATH - Use a single STUN config to add multiple SRFLX candidates2021-12-29T20:35:28ZMohamed ChibaniICE/PJNATH - Use a single STUN config to add multiple SRFLX candidatesBackloghttps://git.jami.net/savoirfairelinux/jami-client-ios/-/issues/114Custom OpenDHT bootstrap server2021-12-29T20:34:51ZArtemy GavrelyukCustom OpenDHT bootstrap serverI haven't find an option to use a custom OpenDHT bootstrap server. Seems like it's absent like a custom TURN-server (#60). It could be great to have both of them. In my case it could help to investigate huge lags in message delivery.I haven't find an option to use a custom OpenDHT bootstrap server. Seems like it's absent like a custom TURN-server (#60). It could be great to have both of them. In my case it could help to investigate huge lags in message delivery.Backloghttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/430macOs/Daemon - Account can not re-register to DHT using the same port2021-12-29T20:34:12ZSébastien BlinmacOs/Daemon - Account can not re-register to DHT using the same portOn macOs, registering the account to the DHT sometimes fail with "Address already in use".
The client/system seems to fail to close the DHT socket, or does not close it fast enough.On macOs, registering the account to the DHT sometimes fail with "Address already in use".
The client/system seems to fail to close the DHT socket, or does not close it fast enough.Backlog