savoirfairelinux issueshttps://git.jami.net/groups/savoirfairelinux/-/issues2022-12-06T05:34:21Zhttps://git.jami.net/savoirfairelinux/jami-client-ios/-/issues/147SIP Account Registered, but No Audio.2022-12-06T05:34:21ZDiagonSIP Account Registered, but No Audio. iOS v.14.7.1
Jami v.3.20
iPhone SE (Gen.1)
SIP account:
<uname>
<password>
SIP Server: callcentric.com
Port: 5060
Proxy: callcentric.com
Account Status:
Enable Account (enabled)
Auto Registe... iOS v.14.7.1
Jami v.3.20
iPhone SE (Gen.1)
SIP account:
<uname>
<password>
SIP Server: callcentric.com
Port: 5060
Proxy: callcentric.com
Account Status:
Enable Account (enabled)
Auto Register After Expiration. (enabled)
My account is listed as "registered" when I check via callcentric's web interface, but when I call *123 or *86 for voicemail, there is no sound. The seconds timer is running. The speaker icon and the microphone icons do not respond. The only thing I can do is get the keypad or hang up.https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/999Incoming call is displayed to user after it has immediately failed (for a few...2023-10-29T19:53:06ZElysIncoming call is displayed to user after it has immediately failed (for a few times) / or you hear the call ringing without viewing any notificationUpdate: You can get the call without any noticiation but you'll hear the ringing forever: https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/999#note_45879
Update: https://git.jami.net/savoirfairelinux/jami-client-androi...Update: You can get the call without any noticiation but you'll hear the ringing forever: https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/999#note_45879
Update: https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/999#note_44908
Always reproduced!
---
using newest version of Jami Android 20221107-01 and Jami 202211101600 Windows 10
I was able to reproduce again (sameuseraccount (Android) -\> sameuseraccount (Windows 10)).
Reproduced if two devices use **different networks AND** if two devices use the **same WLAN**
I think if you make a call useraccount 1 -\> useraccount 2 even if the green dot of your own contact in the contact list on Windows 10 is not visible the Android version will still "remember" the call and as soon as the green dot is visible (on Windows 10) the call will succeed.
EDIT: **Maybe you have to make a call successfully before (Android -\> Windows 10) and then JUST exit Windows 10 to reproduce.**
EDIT: I think I now know why and how it fails?
1. Make a call before you can view the green dot of your contact (?)
2. Make a call shortly before you can view the green dot of your contact (?) / or as soon as you would see the green dot
3. The other peer should receive the call after ten seconds (but you'll never know)?
Sometimes you have to exit Jami (just) on the smartphone a couple of times (over 20 times?) to reproduce?
Just reproduced a couple of times again:
**DISABLE "run in background"**
Steps to reproduce (You actually just have to exit ONE device; NOT BOTH, but I think you have to enable TURN, even if you use the same network) (See: https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/999#note_38603)
---
EDIT: I was also able to reproduce **Android -\> Windows 10** (**sameuseraccount -\> sameuseraccount**); different network
(The Windows 10 user and the Android user have themselves already in the contact list)
Steps to reproduce:
1. Android: Open Jami and keep Jami running (more than 30 seconds)
2. Now the Windows 10 user opens Jami
3. As soon as the Windows 10 user opens Jami, (BEFORE the green dot of the Android user is visible on Windows 10) the Android user makes one call (Android -\> Windows 10), quickly a second call and maybe you also need a third call - they will all immediately fail
4. Now wait for a few seconds or even longer (nobody does anything; meanwhile the Windows 10 views the green dot of the Android user)
5. The Windows 10 user will receive a call (but the Android user will never notice)
I think you can't reproduce if the green dot is not gone- for example if just the Windows 10 user exits Jami but as soon as he opens Jami again the green dot is already there? In that case I wasn't able to reproduce I think ...
---
**Android \<-\> Android**
1. Open Jami and quickly make a first call (maybe even before I can see the green dot ?? (Can't tell because of issue https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/994) - it will immediately fail
2. Now after a few seconds (or even just one second) make the second call - it will immediately fail
3. Now wait
4. Now the Android tablet will receive a call after 10 seconds or more (but the smartphone user will never be able to view the call)
I had a few possibilities:
- Sometimes you don't reproduce?
- Sometimes the other device just gets one call (2 calls failed)
- Sometimes the other device gets both two calls (2 calls failed)
- Sometimes you need to make a third call (after a few seconds) and the other device will receive the third call AND the second call
---
Option B:
Another option how to reproduce this issue:
EDIT: I think I was even able to reproduce even if you make a call after you can view the green dot of the Android contact but BEFORE the green dot of your own account refreshes again.
1. Just open Jami on Android (never exit; keep Jami running at least 30 seconds; Maybe you've already closed Jami on Windows 10)
2. Now the Windows 10 user opens Jami
3. Make a call Android -\> Windows 10 (before the Windows 10 user can view the green dot of the Android contact): It will immediately fail
4. Make a second call Android -\> Windows 10 (before the Windows 10 user can view the green dot of the Android contact): It will try to connect; However (just) the Android user now stops the call ("connecting" \[although this time it might would work\])
5. Now the Android user makes another call - it will immediately fail (again)
6. Maybe the Android user makes again another call - immediately fail (Sometimes it it will show "connecting" again and the call might successfully work)
7. Maybe all peers need to wait a few seconds
8. Now just the Windows 10 user will receive a call - the Android user will never noticehttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/998"Start Jami on startup" and "Run in background" do not work like expected2021-09-29T18:45:50Zvstoykovbg"Start Jami on startup" and "Run in background" do not work like expected## Steps to reproduce
- Steps:
1. Turn off "Start Jami on startup" and "Run in background"
2. Reboot phone
3. Do not open Jami manually
4. Send message from another device
- Actual result: The message is received.
- Expected re...## Steps to reproduce
- Steps:
1. Turn off "Start Jami on startup" and "Run in background"
2. Reboot phone
3. Do not open Jami manually
4. Send message from another device
- Actual result: The message is received.
- Expected result: The message is not received.
I am expecting Jami to listen for messages only when it's running in the background or it's open.
Also the existence of the two options is confusing:
1. Does Jami listen to messages when "Start Jami on startup" is off and "Run in background" is on (and the app is not manually started)?
2. Does Jami listen to messages when "Start Jami on startup" is on and "Run in background" is off (and the app is not manually started)?
Jami version: Maloya - 20210924-01
Android version: 9
![Screenshot_20210929-203330](/uploads/99cbc71559a584906ec28a35d984ded1/Screenshot_20210929-203330.jpg)https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/543Windows beta installer needs user to click Ignore to finish2022-09-07T14:35:20ZovariWindows beta installer needs user to click Ignore to finishWhen installing Jami beta for Windows, the person said that Windows had a dialog which stated something like "Can't update file as it is in use." with the options `Retry`, `Ignore` and `Cancel`.
`Retry` didn't work so they pressed `Igno...When installing Jami beta for Windows, the person said that Windows had a dialog which stated something like "Can't update file as it is in use." with the options `Retry`, `Ignore` and `Cancel`.
`Retry` didn't work so they pressed `Ignore`. Once `Ignore` was pressed, Jami installed; however, this doesn't seem very wise.
We don't have any devices with Windows operating systems; hence, we couldn't reproduce their situation.
1. Are you aware of any programs that should be disabled closed when installing Jami? For example, Windows Defender?
When Jami was installed on there computer Windows Defender caused some problems, and the stated that they allowed the Jami program.
When we made a call, they couldn't hear us and we couldn't hear them.
In their Jami program, they clicked `Open settings`, `Audio/Video` tab, and they said the volume meter for the microphone didn't move and there was no option in the `Microphone` drop-down.
2. Is there a setting in Windows to allow microphones and speakers for programs?
Thank you for your assistance.
Windows 10<br>
[Download Jami beta](https://dl.jami.net/windows/beta/jami.beta.x64.msi) from [Download Jami for Windows](https://jami.net/download-jami-windows/)Andreas TraczykAndreas Traczykhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/996Revoking Device: Password Field Does Not Accept Numbers2022-02-11T09:20:42ZMartin MayerRevoking Device: Password Field Does Not Accept NumbersHi all,
I just tried to revoke devices from my Android. However, when asked for the password,
I can only enter letters, not numbers. This silently fails.
----
To reproduce
* Try to revoke a secondary account
* Enter numbers, when ...Hi all,
I just tried to revoke devices from my Android. However, when asked for the password,
I can only enter letters, not numbers. This silently fails.
----
To reproduce
* Try to revoke a secondary account
* Enter numbers, when asked for the password
* Without hitting enter, dismiss the dialpad (back button)
* Check what you've entered. Numbers are mission
---
Version : 2021_05_21 from F-Droid.
----
Additional observations:
* Entering the required password pops up the dialpad
* The dialpad hides the password entry field
* Hence it is not obvious that I could not enter numerbs, just letters.
* Only dismissing the dialpad revealed the issue.https://git.jami.net/savoirfairelinux/jami-project/-/issues/1307Option to use the Curve448 identity key pair and 224 bits encryption, or NIST...2023-11-20T14:26:02ZMarek ĽachOption to use the Curve448 identity key pair and 224 bits encryption, or NIST P-384 encryption in Jami's spec/clientsCurrently, Jami only officially supports _RSA encryption. To future prove-it, since RSA is already quite old, an update to the Jami specs (and then the clients) allowing also for the use of `elliptic Curve448 at 224 bits` encryption (for...Currently, Jami only officially supports _RSA encryption. To future prove-it, since RSA is already quite old, an update to the Jami specs (and then the clients) allowing also for the use of `elliptic Curve448 at 224 bits` encryption (for Python available through [eccsnacks](https://github.com/nnathan/eccsnacks)), would be welcome to future-proof its security.
Another potentially viable option for an update of the encryption standard, could be the `Riandael NIST P-384` encryption, which's usually 192bit (available for Python through https://pycryptodome.readthedocs.io/en/latest/index.html).
Thank you for considering,https://git.jami.net/savoirfairelinux/jami-project/-/issues/1305Update version of installed git (on Windows)2021-09-17T17:22:56ZAmin BandaliUpdate version of installed git (on Windows)Per https://git.jami.net/savoirfairelinux/jami-project/-/issues/1290#note_30286, the version of git currently installed (presumably by `scripts/install-deps-windows.ps1`) on Windows is too old (2.10.2), and should be bumped up (e.g. to 2...Per https://git.jami.net/savoirfairelinux/jami-project/-/issues/1290#note_30286, the version of git currently installed (presumably by `scripts/install-deps-windows.ps1`) on Windows is too old (2.10.2), and should be bumped up (e.g. to 2.33.0, the current latest release) if there are no blockers.Andreas TraczykMing Rui ZhangAndreas Traczykhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/620MediaDemuxer: can lock on disconnect2023-04-17T14:09:50ZSébastien BlinMediaDemuxer: can lock on disconnect# Scenario
+ Plug a camera
+ Show it in media settings
+ Unplug
# Expected scenario
+ The UI should not freeze
# Current result
sometimes, the UI is freezing, blocking on destroying the video input.
# Backtrace
```
Thread 1 (Threa...# Scenario
+ Plug a camera
+ Show it in media settings
+ Unplug
# Expected scenario
+ The UI should not freeze
# Current result
sometimes, the UI is freezing, blocking on destroying the video input.
# Backtrace
```
Thread 1 (Thread 0x7fffe2a99d40 (LWP 2929030) "jami-qt"):
#0 0x00007fffeda179d7 in __pthread_clockjoin_ex () at /lib64/libpthread.so.0
#1 0x00007fffedffd687 in std::thread::join() () at /lib64/libstdc++.so.6
#2 0x00007fffec773cbb in jami::video::VideoInput::~VideoInput() () at /home/amarok/Projects/jami/daemon/src/.libs/libring.so.0
#3 0x00007fffec4cae2a in DRing::stopCamera() () at /home/amarok/Projects/jami/daemon/src/.libs/libring.so.0
#4 0x00007ffff7d17752 in VideoManagerInterface::stopCamera() (this=<optimized out>) at /home/amarok/Projects/jami/lrc/src/qtwrapper/videomanager_wrap.h:184
#5 0x00007ffff7d1cad0 in lrc::api::AVModel::setDeviceSettings(lrc::api::video::Settings&) (this=0x1496890, settings=...) at /home/amarok/Projects/jami/lrc/src/avmodel.cpp:293
#6 0x000000000049d42d in SettingsAdapter::set_Video_Settings_Rate_And_Resolution(QString const&, double, QString const&) (this=0xffb380, deviceId=..., rate=30, resolution=...) at /home/amarok/Projects/jami/client-qt/src/settingsadapter.cpp:193
#7 0x0000000000434c41 in SettingsAdapter::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (_o=_o@entry=0xffb380, _c=_c@entry=QMetaObject::InvokeMetaMethod, _id=_id@entry=17, _a=_a@entry=0x7fffffff2710) at /home/amarok/Projects/jami/client-qt/build-local/jami-qt_autogen/UVLADIE3JM/moc_settingsadapter.cpp:708
#8 0x00000000004385ee in SettingsAdapter::qt_metacall(QMetaObject::Call, int, void**) (this=0xffb380, _c=QMetaObject::InvokeMetaMethod, _id=17, _a=0x7fffffff2710) at /home/amarok/Projects/jami/client-qt/build-local/jami-qt_autogen/UVLADIE3JM/moc_settingsadapter.cpp:969
#9 0x00007fffeeb08cf5 in QQmlObjectOrGadget::metacall(QMetaObject::Call, int, void**) const () at /lib64/libQt5Qml.so.5
#10 0x00007fffeea11149 in CallPrecise(QQmlObjectOrGadget const&, QQmlPropertyData const&, QV4::ExecutionEngine*, QV4::CallData*, QMetaObject::Call) () at /lib64/libQt5Qml.so.5
#11 0x00007fffeea123f7 in QV4::QObjectMethod::callInternal(QV4::Value const*, QV4::Value const*, int) const () at /lib64/libQt5Qml.so.5
#12 0x00007fffeea38cce in QV4::Runtime::CallPropertyLookup::call(QV4::ExecutionEngine*, QV4::Value const&, unsigned int, QV4::Value*, int) () at /lib64/libQt5Qml.so.5
#13 0x00007fff4014bb4e in ()
#14 0x00007fffffff2d40 in ()
#15 0x0000000000000010 in ()
#16 0x00007fff4014b000 in ()
#17 0x00007fff4014bb8b in ()
#18 0x000000000088d800 in ()
#19 0x00007fffeea2ceba in QV4::Moth::VME::exec(QV4::CppStackFrame*, QV4::ExecutionEngine*) [clone .part.0] () at /lib64/libQt5Qml.so.5
#20 0x00007fffee9d7d48 in QV4::ArrowFunction::virtualCall(QV4::FunctionObject const*, QV4::Value const*, QV4::Value const*, int) () at /lib64/libQt5Qml.so.5
#21 0x00007fffeea3cc46 in QV4::Runtime::CallQmlContextPropertyLookup::call(QV4::ExecutionEngine*, unsigned int, QV4::Value*, int) () at /lib64/libQt5Qml.so.5
#22 0x00007fff40148084 in ()
#23 0x00007fffffff3010 in ()
#24 0x0000000000000000 in ()
Thread 224 (Thread 0x7ffcceffd640 (LWP 2929321) "jami-qt"):
#0 0x00007fffedcf35db in ioctl () at /lib64/libc.so.6
#1 0x00007fffec9c4759 in mmap_read_frame (pkt=0x7ffc6401f2c0, ctx=0x7ffc64002200) at libavdevice/v4l2.c:505
#2 v4l2_read_packet (ctx=0x7ffc64002200, pkt=0x7ffc6401f2c0) at libavdevice/v4l2.c:992
#3 0x00007fffeca222c2 in ff_read_packet (s=s@entry=0x7ffc64002200, pkt=pkt@entry=0x7ffc6401f2c0) at libavformat/utils.c:843
#4 0x00007fffeca22c3b in read_frame_internal (s=s@entry=0x7ffc64002200, pkt=0x7ffc6401f2c0) at libavformat/utils.c:1546
#5 0x00007fffeca23938 in av_read_frame (s=0x7ffc64002200, pkt=0x7ffc6401f2c0) at libavformat/utils.c:1750
#6 0x00007fffec413fa7 in jami::MediaDemuxer::decode() () at /home/amarok/Projects/jami/daemon/src/.libs/libring.so.0
#7 0x00007fffec76f6a9 in jami::video::VideoInput::captureFrame() () at /home/amarok/Projects/jami/daemon/src/.libs/libring.so.0
#8 0x00007fffec774bcb in jami::video::VideoInput::process() () at /home/amarok/Projects/jami/daemon/src/.libs/libring.so.0
#9 0x00007fffec32602d in jami::ThreadLoop::mainloop(std::thread::id&, std::function<bool ()>, std::function<void ()>, std::function<void ()>) () at /home/amarok/Projects/jami/daemon/src/.libs/libring.so.0
#10 0x00007fffec326758 in std::thread::_State_impl<std::thread::_Invoker<std::tuple<void (jami::ThreadLoop::*)(std::thread::id&, std::function<bool ()>, std::function<void ()>, std::function<void ()>), jami::ThreadLoop*, std::reference_wrapper<std::thread::id>, std::function<bool ()>, std::function<void ()>, std::function<void ()> > > >::_M_run() () at /home/amarok/Projects/jami/daemon/src/.libs/libring.so.0
#11 0x00007fffedffd444 in execute_native_thread_routine () at /lib64/libstdc++.so.6
#12 0x00007fffeda163f9 in start_thread () at /lib64/libpthread.so.0
#13 0x00007fffedcfcb53 in clone () at /lib64/libc.so.6
```
av_read_frame can block forever, causing the VideoInput to wait.Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-plugins/-/issues/20Voice changer2021-08-28T12:58:05ZDavid HedlundVoice changerWho wouldn't like to have voice changer option?Who wouldn't like to have voice changer option?https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/988Push notification will not show at the beginning when the device is restarted2021-08-24T07:19:05ZMing Rui ZhangPush notification will not show at the beginning when the device is restartedWhen the device is restarted, there will be for sure no Jami running in the background.
At this time, when a push notification is received, Jami will wake up from the debugging log and
messages, calls will be received and handled correc...When the device is restarted, there will be for sure no Jami running in the background.
At this time, when a push notification is received, Jami will wake up from the debugging log and
messages, calls will be received and handled correctly.
But, there will be no system notification being showed unless the contact keeps sending or calling (until ```bootstrapDaemon``` is called again).
Current speculations:
1. When the client is started normally, the ```ConversationFacade``` instance will be created which is in charge of
notifications' build.
```
2021-08-23 12:22:52.434 17572-17572/cx.ring D/DERP: init conv facade
java.lang.RuntimeException
at net.jami.services.ConversationFacade.<init>(ConversationFacade.kt:631)
at cx.ring.dependencyinjection.ServiceInjectionModule.provideConversationFacade(ServiceInjectionModule.kt:140)
at cx.ring.dependencyinjection.ServiceInjectionModule_ProvideConversationFacadeFactory.provideConversationFacade(ServiceInjectionModule_ProvideConversationFacadeFactory.java:78)
at cx.ring.application.DaggerJamiApplicationFirebase_HiltComponents_SingletonC.conversationFacade(DaggerJamiApplicationFirebase_HiltComponents_SingletonC.java:285)
at cx.ring.application.DaggerJamiApplicationFirebase_HiltComponents_SingletonC.access$3800(DaggerJamiApplicationFirebase_HiltComponents_SingletonC.java:200)
at cx.ring.application.DaggerJamiApplicationFirebase_HiltComponents_SingletonC$SwitchingProvider.get(DaggerJamiApplicationFirebase_HiltComponents_SingletonC.java:1569)
at dagger.internal.DoubleCheck.get(DoubleCheck.java:47)
at cx.ring.application.DaggerJamiApplicationFirebase_HiltComponents_SingletonC$ActivityCImpl.injectHomeActivity2(DaggerJamiApplicationFirebase_HiltComponents_SingletonC.java:1339)
at cx.ring.application.DaggerJamiApplicationFirebase_HiltComponents_SingletonC$ActivityCImpl.injectHomeActivity(DaggerJamiApplicationFirebase_HiltComponents_SingletonC.java:1242)
at cx.ring.client.Hilt_HomeActivity.inject(Hilt_HomeActivity.java:67)
at cx.ring.client.Hilt_HomeActivity$1.onContextAvailable(Hilt_HomeActivity.java:38)
at androidx.activity.contextaware.ContextAwareHelper.dispatchOnContextAvailable(ContextAwareHelper.java:99)
at androidx.activity.ComponentActivity.onCreate(ComponentActivity.java:322)
at androidx.fragment.app.FragmentActivity.onCreate(FragmentActivity.java:273)
at cx.ring.client.HomeActivity.onCreate(HomeActivity.kt:132)
at android.app.Activity.performCreate(Activity.java:7183)
at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1220)
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2910)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3032)
at android.app.ActivityThread.-wrap11(Unknown Source:0)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1696)
at android.os.Handler.dispatchMessage(Handler.java:105)
at android.os.Looper.loop(Looper.java:164)
at android.app.ActivityThread.main(ActivityThread.java:6944)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.Zygote$MethodAndArgsCaller.run(Zygote.java:327)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1374)
```
2. When the application wakes up by push notification, no instance of ```ConversationFacade``` will be created. Therefore,
there will be no subscription to create notifications on the representation level.https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/987SIP configuration options need explanation2022-11-11T16:33:23ZWarthog-CapitalSIP configuration options need explanationTo an SIP newcomer like me, the configuration options in the Jami app are very unclear. Specifically, entries that leave me wondering are:
- Advanced / Enable UPnP. I thought SIP is a client-server protocol, why would it need to open po...To an SIP newcomer like me, the configuration options in the Jami app are very unclear. Specifically, entries that leave me wondering are:
- Advanced / Enable UPnP. I thought SIP is a client-server protocol, why would it need to open ports?
- Advanced / Use DHT proxy. Similar question. In which way is DHT involved in SIP?
- Advanced / Use Stun/TURN. What is the effect of enabling these options?
- Security / Add credentials. Currently contains my password, and "*". What does the * mean? How can a SIP account possibly have multiple credentials?
- Security / Encrypt media streams (SRTP). Encryption sounds good, why is it disabled by default? Does it require server support, or client support on the other end (end-to-end)? What happens if my server or a caller do not support SRTP?
- Security / Enable SDES as key exchange protocol. What are the pros and cons of setting this option?
- Security / Use TLS Transport. Transport encryption should be standard on any protocol nowadays, why is this disabled by default?
- Security / Certification authorities, certificate file and private key file have a red exclamation mark, indicating that some action must be taken. But they are greyed out. What is the issue here? If this is related to TLS, why can it not use the system-wide certificate store for authentication?
- Security / TLS method: TLSv1. TLS version 1 is deprecated and should not be used. Why is this the default? TLSv1.3 is not even an option here, apparently?
- Security / TLS ciphers. Just opens a text field. What is the user supposed to put in here?
- Server name. I would assume that this is the domain name configured for the SIP account (user@domain). What does this option mean?
- Security / Verify server/client. What is the effect of these options?
- Security / TLS require client certificate. (default: on) What is the effect of this option?
My main reason for using SIP is having encrypted telephony. Based on these presented options, I have no idea whether my settings are secure and whether my voice calls are encrypted or not.
In particular, my provider Sipgate.de apparently does not support SRTP (https://basicsupport.sipgate.de/hc/de/articles/207246495-Ist-eine-SRTP-TLS-Sprachverschl%C3%BCsselung-m%C3%B6glich-), so does this mean that SRTP is involved in client-to-server communication, not end-to-end? Confusingly, if I enable SRTP in the options above, my connection is still shown as "online", so something seems to work.
Configuration options that I am missing are:
- ZRTP. Is ZRTP supported? Based on my research, this one is definitely end-to-end.
- Configuring a display name. Other SIP clients offered me to set up a display name, but this does not seem to be an option for SIP accounts in Jami.
Clarification would be appreciated! :)Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1289Bundle same contacts with different spelling2021-08-19T19:54:53ZmokkinBundle same contacts with different spellingThe following examples shows three different spellings of the same contact:
![image](/uploads/564ff72a0adad7f06a3055ba20dd53f6/image.png)
1. International format with country code and city code
2. National format with city code
3. Local...The following examples shows three different spellings of the same contact:
![image](/uploads/564ff72a0adad7f06a3055ba20dd53f6/image.png)
1. International format with country code and city code
2. National format with city code
3. Local format without any prefix
All of them are successful for calling, because the pbx/sip knows its region. For a better overview these contacts should be recognized as the same and bundled.https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/500Reorder video tiles via drag and drop2023-05-12T13:18:34ZovariReorder video tiles via drag and dropReorder video tiles via drag and drop.
https://jitsi-hacks.cketti.eu/hacks/reorder/
![image](/uploads/7f397eaa57545732b65bbd2c6352ddfb/image.png)
# Installation
Drag the following link into your browser’s bookmark bar: [Reorder video...Reorder video tiles via drag and drop.
https://jitsi-hacks.cketti.eu/hacks/reorder/
![image](/uploads/7f397eaa57545732b65bbd2c6352ddfb/image.png)
# Installation
Drag the following link into your browser’s bookmark bar: [Reorder video tiles](javascript:(function()%7Bfunction%20callback()%7B%7Dvar%20s%3Ddocument.createElement(%22script%22)%3Bs.src%3D%22https%3A%2F%2Fjitsi-hacks.cketti.eu%2Freorder.js%22%3Bif(s.addEventListener)%7Bs.addEventListener(%22load%22%2Ccallback%2Cfalse)%7Delse%20if(s.readyState)%7Bs.onreadystatechange%3Dcallback%7Ddocument.body.appendChild(s)%3B%7D)())
If the link doesn't work, here is the code:<br>
`javascript:(function()%7Bfunction%20callback()%7B%7Dvar%20s%3Ddocument.createElement(%22script%22)%3Bs.src%3D%22https%3A%2F%2Fjitsi-hacks.cketti.eu%2Freorder.js%22%3Bif(s.addEventListener)%7Bs.addEventListener(%22load%22%2Ccallback%2Cfalse)%7Delse%20if(s.readyState)%7Bs.onreadystatechange%3Dcallback%7Ddocument.body.appendChild(s)%3B%7D)()`
To inject the script click the link in the bookmark bar while the Jitsi Meet tab is active. The effects only last until the next page reload.
# Usage
Once the hack is loaded you can reorder videos in tile view via drag and drop.
How does it work?
The script utilizes the [Dragula](https://bevacqua.github.io/dragula/) library to allow reordering video tiles via drag and drop.
# Source Code
Find [reorder.js](https://github.com/cketti/jitsi-hacks/blob/main/docs/reorder.js) on GitHub.https://git.jami.net/savoirfairelinux/jami-packaging/-/issues/105Guix packaging: allow jami-qt to run on non-Mesa systems2024-01-10T22:53:46ZMaxim CournoyerGuix packaging: allow jami-qt to run on non-Mesa systemsGuix applications cannot currently run on drivers not part of Mesa, such as the nvidia proprietary drivers or AMD ones.
To be truly universal, Guix applications should be able to run on such systems as well.
This basically requires fix...Guix applications cannot currently run on drivers not part of Mesa, such as the nvidia proprietary drivers or AMD ones.
To be truly universal, Guix applications should be able to run on such systems as well.
This basically requires fixing Mesa in Guix to use glvnd (see the upstream issue here: https://issues.guix.gnu.org/49847).https://git.jami.net/savoirfairelinux/jami-packaging/-/issues/104Guix packaging: fix fonts issue2021-08-13T17:48:50ZMaxim CournoyerGuix packaging: fix fonts issueExplore if something can be done to improve the look and feel of jami-qt when packaged as a Guix pack (software bundle). Perhaps adding a font to the pack could be enough.Explore if something can be done to improve the look and feel of jami-qt when packaged as a Guix pack (software bundle). Perhaps adding a font to the pack could be enough.https://git.jami.net/savoirfairelinux/jami-project/-/issues/1285No option to share computer audio with screen share?2023-01-25T17:04:49ZCross NastasiNo option to share computer audio with screen share?Not sure if this is intentional or not, but there doesn't seem to be a way to share the computer output along with a screen share. This is important for sharing videos and other things that require audio.Not sure if this is intentional or not, but there doesn't seem to be a way to share the computer output along with a screen share. This is important for sharing videos and other things that require audio.https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/485Drag and drop files from chatview and send to other contacts2023-05-19T14:50:07ZAndreas TraczykDrag and drop files from chatview and send to other contacts1. Direct send
2. No conversation selection1. Direct send
2. No conversation selectionhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/480Conference call view: confirm before kicking participant2021-07-27T21:23:48ZAndreas TraczykConference call view: confirm before kicking participantProvide a confirmation dialog after proposing to remove a participant from the call.Provide a confirmation dialog after proposing to remove a participant from the call.https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/985Question / feature request: Android Video call with internal audio (and micro...2023-11-14T19:56:18ZElysQuestion / feature request: Android Video call with internal audio (and microphone)It is possible to live-stream internal audio on Android (at least Android 10 etc.)
There are also apps that were able to record internal audio on Android 6 (in the past; for example older versions of Mobizen screen recorder. Example: ht...It is possible to live-stream internal audio on Android (at least Android 10 etc.)
There are also apps that were able to record internal audio on Android 6 (in the past; for example older versions of Mobizen screen recorder. Example: https://www.youtube.com/watch?v=s18FeVOI8i8 ).
And you can record or even live-stream internal Audio and the sound of an external microphone.
Example: https://youtu.be/1JY4_8l6Xco?t=980
As far as I know also Telegram is able to stream internal audio: https://www.youtube.com/watch?v=rJOd42kfhuU
Would it be possible to stream internal audio on Android AND the sound / your voice of an internal or external microphone of your phone AT THE SAME TIME during a Jami video call ?https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/477Project image resource cleanup2023-04-28T19:34:44ZAndreas TraczykProject image resource cleanupMany image resources are unused, duplicates, not in the correct image format, etc.
- [x] homogenize type
- [ ] homogenize naming
- [x] prune unused
- [x] prune duplicates
- [x] alias icons as Qml singleton propertiesMany image resources are unused, duplicates, not in the correct image format, etc.
- [x] homogenize type
- [ ] homogenize naming
- [x] prune unused
- [x] prune duplicates
- [x] alias icons as Qml singleton propertiesAndreas TraczykAndreas Traczyk