savoirfairelinux issueshttps://git.jami.net/groups/savoirfairelinux/-/issues2023-06-16T18:56:18Zhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/720Support DTMF2023-06-16T18:56:18ZSébastien BlinSupport DTMFTo be definedTo be definedBackloghttps://git.jami.net/savoirfairelinux/jami-client-ios/-/issues/160Custom OpenDHT bootstrap server2022-02-03T21:48:10ZArtemy 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 (jami-client-ios#60). It could be great to have both of them. In my case it could help to investigate huge lags in messag...I haven't find an option to use a custom OpenDHT bootstrap server. Seems like it's absent like a custom TURN-server (jami-client-ios#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-client-qt/-/issues/670Swarm: Add swarm creation into the UI2022-05-13T14:55:46ZSébastien BlinSwarm: Add swarm creation into the UI![create-group0](/uploads/3a632484fbac3e6313dffa2a7605e1c9/create-group0.png)
![create-group1](/uploads/bb76dae1c886bc5cd83e6ce6cc840252/create-group1.png)![create-group0](/uploads/3a632484fbac3e6313dffa2a7605e1c9/create-group0.png)
![create-group1](/uploads/bb76dae1c886bc5cd83e6ce6cc840252/create-group1.png)Swarm-chathttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/713Conference layout seems broken after 25+ participants2024-02-14T14:07:15ZSébastien BlinConference layout seems broken after 25+ participants# Scenario
+ Start a conference with 25 participants
+ Another participant join
# Expected
+ The layout should be updated
# Current result
Seems blocked to the previous view# Scenario
+ Start a conference with 25 participants
+ Another participant join
# Expected
+ The layout should be updated
# Current result
Seems blocked to the previous viewBackloghttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/712Windows: Black screen of the interlocutor if he/she rotates the screen of the...2024-02-14T14:06:57ZElysWindows: Black screen of the interlocutor if he/she rotates the screen of the phonePerson A using Jami Windows 10, Person B using Jami Android 11 (Mate 20 Pro)
issue: especially if Person B rotates the screen to portrait
Steps: you get a video call (android, Person B):
persons A and B see each other
Person B rotates...Person A using Jami Windows 10, Person B using Jami Android 11 (Mate 20 Pro)
issue: especially if Person B rotates the screen to portrait
Steps: you get a video call (android, Person B):
persons A and B see each other
Person B rotates the screen to portrait, then rotates the screen to upside-down landscape. If person B rotates the screen to portrait again, Person A (using Windows 10) only sees a black screen (with a preview of Person A). Sometimes person B has to rotate the screen many times but after a random number of attempts this issue occurs.
same thing happens (sometimes) if Person A shares screen and wants to return to webcam - Person B is now absent - Person A only sees black screen (with a preview of Person A)
Example:
![fail2](/uploads/dd557fd8978885fb470b3116fa4bfed2/fail2.png)Backloghttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/711video rotation - handle multi-stream2022-07-05T18:02:18ZMohamed Chibanivideo rotation - handle multi-streamBackloghttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/710Hardware acceleration - Daemon must compile if RING_ACCEL is not defined2022-02-03T20:48:13ZMohamed ChibaniHardware acceleration - Daemon must compile if RING_ACCEL is not definedUndefining RING_ACCEL fails the compilation of the daemon in many places.
Also, compilation check must use #if RING_ACCEL instead of #ifdef, because in Daemon configuration, a feature is disabled by setting it's macro to 0 (so still defi...Undefining RING_ACCEL fails the compilation of the daemon in many places.
Also, compilation check must use #if RING_ACCEL instead of #ifdef, because in Daemon configuration, a feature is disabled by setting it's macro to 0 (so still defined).Backloghttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/706pjnath/turn_session: Bad TURN session state2024-02-14T14:06:29ZOlivier Dionpjnath/turn_session: Bad TURN session stateIn pjnath/turn_session.c:
```c
1192 PJ_ASSERT_RETURN(sess->state == PJ_TURN_STATE_READY, PJ_EINVALIDOP);
```
w...In pjnath/turn_session.c:
```c
1192 PJ_ASSERT_RETURN(sess->state == PJ_TURN_STATE_READY, PJ_EINVALIDOP);
```
where `sess->state` has the value `PJ_TURN_STATE_DESTROYING`.
Discovered by: agent's scenario `make-call`
Passive agent log: [passive.log.gz](/uploads/a6476e40a8be86c7059f9e22674d1b67/passive.log.gz)
Active agent log: [make-call.log.gz](/uploads/fc06004cdc28de838667332216a08c3a/make-call.log.gz)
Backtrace trace, see Thread 51: [gdb.txt](/uploads/7f47530f51acdd00aee0e527cf0e570f/gdb.txt)
Tested on jami-daemon@07804eb312350a1ec896c7f271464ca2b3475869Backloghttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/702UPNP-NATPMP - Add a unit test with minimal validation2022-11-26T22:41:53ZMohamed ChibaniUPNP-NATPMP - Add a unit test with minimal validationBackloghttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/701Recheck all APIs2022-02-03T20:34:22ZSébastien BlinRecheck all APIs+ Remove unnecessary APIs
+ Homogeneize file naming
+ definitions URI/ids
+ Split ConfigurationManager+ Remove unnecessary APIs
+ Homogeneize file naming
+ definitions URI/ids
+ Split ConfigurationManagerBackloghttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/700UPnP - Make port ranges configurable2022-02-03T20:29:33ZMohamed ChibaniUPnP - Make port ranges configurableThe port ranges (TCP and UDP) used by upnp to port mapping allocation must be configurable (currently they are hard-coded).
A new API must be added to allow a user to set the ranges for both UDP and TCP ports. If not set, default values ...The port ranges (TCP and UDP) used by upnp to port mapping allocation must be configurable (currently they are hard-coded).
A new API must be added to allow a user to set the ranges for both UDP and TCP ports. If not set, default values be used.
Might be related to https://git.jami.net/savoirfairelinux/ring-daemon/-/issues/417Backloghttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/698UPNP/ICE/TCP - ICE/TCP connection using relay should be reset if a UPNP/NAT-P...2024-02-14T14:07:50ZMohamed ChibaniUPNP/ICE/TCP - ICE/TCP connection using relay should be reset if a UPNP/NAT-PMP is availableBackloghttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/697macOs/Daemon - Account can not re-register to DHT using the same port2023-03-03T21:09:21ZSé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.Backloghttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/696ICE/PJNATH - Use a single STUN config to add multiple SRFLX candidates2024-02-14T14:07:53ZMohamed ChibaniICE/PJNATH - Use a single STUN config to add multiple SRFLX candidatesBackloghttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/694ffmpeg: add G711, G729 codecs (SIP)2022-07-06T00:18:18Zovariffmpeg: 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-client-android/-/issues/1074Android - Audio is not automatically routed to headsets when plugged2023-05-31T13:31:14ZMohamed 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-client-android/-/issues/1073Wrong microphone used for audio and video call2022-02-03T18:25:23Zring 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-client-android/-/issues/1070Plugins: add new UI for plugins with pref per account2022-05-04T19:09:20ZMaxime CalletPlugins: add new UI for plugins with pref per account- Add the new UI for the update plugins system inside the bottom control panel (bottom sheet)- Add the new UI for the update plugins system inside the bottom control panel (bottom sheet)Next major releaseAmirhossein NaghshzanAmirhossein Naghshzanhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/668Please add `Share window` option to the list in the panel2022-03-21T03:39:09ZovariPlease add `Share window` option to the list in the panelShould a `Share window` option be added to the list in the panel?
![image](https://git.jami.net/savoirfairelinux/jami-project/uploads/cb7546909b817b550441facaab06722c/image.png)
It might make a better UX.
There would be 4 options then...Should a `Share window` option be added to the list in the panel?
![image](https://git.jami.net/savoirfairelinux/jami-project/uploads/cb7546909b817b550441facaab06722c/image.png)
It might make a better UX.
There would be 4 options then in the image above, i.e.:
* Share screen
* Share screen area
* Share window
* Share file
What do you think?
Thank you
https://git.jami.net/savoirfairelinux/jami-project/-/issues/1294#note_32291
cc: @agsantosJami for education(2)Aline Gondim SantosAline Gondim Santoshttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/657Update chat layout in current call with the chat open if the setting is updated2022-08-24T21:43:39ZovariUpdate chat layout in current call with the chat open if the setting is updatedRelated to #571.
1. Make a call
2. Click on the `Chat` button to open the chatview
3. Click `Open Settings` > `General` > Change `Layout` (under the `Chatview` section) to the other option, i.e. `Horizontal view`/`Vertical view`
4. Clic...Related to #571.
1. Make a call
2. Click on the `Chat` button to open the chatview
3. Click `Open Settings` > `General` > Change `Layout` (under the `Chatview` section) to the other option, i.e. `Horizontal view`/`Vertical view`
4. Click `Close settings`
5. The call has not updated the chatview as the chatview is in the previous setting
6. Workaround: close and open the chatview but clicking on the `Chat` button twice
If there is a current call with the chatview open and the setting is updated, can the position of the chatview in the current call please be updated without the workaround?
What do you think?
Thank you
Linux Mint 20.3 Cinnamon<br>
client-qt Version: 202201251934 deb edition from jami.netJami for education(2)