savoirfairelinux issueshttps://git.jami.net/groups/savoirfairelinux/-/issues2021-06-12T11:37:52Zhttps://git.jami.net/savoirfairelinux/jami-libclient/-/issues/463Swarm: add support for re-asking file transfer2021-06-12T11:37:52ZSébastien BlinSwarm: add support for re-asking file transferSwarm-chathttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1217Please support push notifications for calls2021-03-31T13:09:42ZreubenfirminPlease support push notifications for callsThe Android app seems to work reasonably well, but eats battery. Please support push notifications to circumvent this - for me, I can't use Jami as a daily driver to receive calls on my cellphone if battery only lasts 1/3rd of the day wi...The Android app seems to work reasonably well, but eats battery. Please support push notifications to circumvent this - for me, I can't use Jami as a daily driver to receive calls on my cellphone if battery only lasts 1/3rd of the day without a charge.https://git.jami.net/savoirfairelinux/jami-project/-/issues/1216Please retry connection every minute if de-registered2021-08-20T21:11:20ZreubenfirminPlease retry connection every minute if de-registeredI'm on a flakey internet connection (data SIM hotspot). Periodically the network provider will have a hiccup. Jami will become deregistered, and then won't be able to reconnect until I go in and toggle the switch.
Please add an auto-rec...I'm on a flakey internet connection (data SIM hotspot). Periodically the network provider will have a hiccup. Jami will become deregistered, and then won't be able to reconnect until I go in and toggle the switch.
Please add an auto-reconnect feature so that it more aggressively tries to reconnect if it becomes de-registered.https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/499SIP Call Tranfer & Hold Issues2021-04-08T20:41:12ZMing Rui ZhangSIP Call Tranfer & Hold IssuesThe main reason for these issues are related to re-INVITE message handling
Originally, we rely on the auto-response from pjsip.
But their response contains an invalid Contact header
Changes are required to be madeThe main reason for these issues are related to re-INVITE message handling
Originally, we rely on the auto-response from pjsip.
But their response contains an invalid Contact header
Changes are required to be madeMing Rui ZhangMing Rui Zhanghttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/356First hangup crash2021-04-07T19:48:27ZSébastien BlinFirst hangup crash# Reproduce steps
+ With a clean env, create the first account
+ During the profile creation, set an avatar via the webcam
+ Then call a contact
+ hangup
# Expected result
It should be fine
# Current result
Crash
```
Thread 109 "QT...# Reproduce steps
+ With a clean env, create the first account
+ During the profile creation, set an avatar via the webcam
+ Then call a contact
+ hangup
# Expected result
It should be fine
# Current result
Crash
```
Thread 109 "QThread" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7ffeff7fe640 (LWP 2786264)]
0x00007fffed529546 in QQmlData::isSignalConnected(QAbstractDeclarativeData*, QObject const*, int) () from /lib64/libQt5Qml.so.5
(gdb) bt
#0 0x00007fffed529546 in QQmlData::isSignalConnected(QAbstractDeclarativeData*, QObject const*, int) () at /lib64/libQt5Qml.so.5
#1 0x00007fffece28efa in void doActivate<false>(QObject*, int, void**) () at /lib64/libQt5Core.so.5
#2 0x0000000000431c05 in PhotoboothPreviewRender::hideBooth() ()
#3 0x000000000048fe29 in PhotoboothPreviewRender::PhotoboothPreviewRender(QQuickItem*)::{lambda()#1}::operator()() const::{lambda()#1}::operator()() const ()
#4 0x0000000000491894 in QtPrivate::FunctorCall<QtPrivate::IndexesList<>, QtPrivate::List<>, void, PhotoboothPreviewRender::PhotoboothPreviewRender(QQuickItem*)::{lambda()#1}::operator()() const::{lambda()#1}>::call(PhotoboothPreviewRender::PhotoboothPreviewRender(QQuickItem*)::{lambda()#1}::operator()() const::{lambda()#1}&, void**) ()
#5 0x00000000004917c7 in void QtPrivate::Functor<PhotoboothPreviewRender::PhotoboothPreviewRender(QQuickItem*)::{lambda()#1}::operator()() const::{lambda()#1}, 0>::call<QtPrivate::List<>, void>(PhotoboothPreviewRender::PhotoboothPreviewRender(QQuickItem*)::{lambda()#1}::operator()() const::{lambda()#1}&, void*, void**) ()
#6 0x00000000004915a0 in QtPrivate::QFunctorSlotObject<PhotoboothPreviewRender::PhotoboothPreviewRender(QQuickItem*)::{lambda()#1}::operator()() const::{lambda()#1}, 0, QtPrivate::List<>, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) ()
#7 0x00007fffece29386 in void doActivate<false>(QObject*, int, void**) () at /lib64/libQt5Core.so.5
#8 0x0000000000432731 in RenderManager::previewRenderingStopped() ()
#9 0x000000000045f007 in RenderManager::RenderManager(lrc::api::AVModel&)::{lambda(QString const&)#2}::operator()(QString const&) const ()
#10 0x000000000045ffe7 in QtPrivate::FunctorCall<QtPrivate::IndexesList<0>, QtPrivate::List<QString const&>, void, RenderManager::RenderManager(lrc::api::AVModel&)::{lambda(QString const&)#2}>::call(RenderManager::RenderManager(lrc::api::AVModel&)::{lambda(QString const&)#2}&, void**) ()
#11 0x000000000045ff4d in void QtPrivate::Functor<RenderManager::RenderManager(lrc::api::AVModel&)::{lambda(QString const&)#2}, 1>::call<QtPrivate::List<QString const&>, void>(RenderManager::RenderManager(lrc::api::AVModel&)::{lambda(QString const&)#2}&, void*, void**)
()
#12 0x000000000045fe68 in QtPrivate::QFunctorSlotObject<RenderManager::RenderManager(lrc::api::AVModel&)::{lambda(QString const&)#2}, 1, QtPrivate::List<QString const&>, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) ()
#13 0x00007fffece29386 in void doActivate<false>(QObject*, int, void**) () at /lib64/libQt5Core.so.5
#14 0x0000000000432351 in FrameWrapper::renderingStopped(QString const&) ()
#15 0x000000000045efc1 in FrameWrapper::slotRenderingStopped(QString const&) ()
#16 0x0000000000463d01 in QtPrivate::FunctorCall<QtPrivate::IndexesList<0>, QtPrivate::List<QString const&>, void, void (FrameWrapper::*)(QString const&)>::call(void (FrameWrapper::*)(QString const&), FrameWrapper*, void**) ()
#17 0x0000000000463309 in void QtPrivate::FunctionPointer<void (FrameWrapper::*)(QString const&)>::call<QtPrivate::List<QString const&>, void>(void (FrameWrapper::*)(QString const&), FrameWrapper*, void**) ()
#18 0x0000000000462205 in QtPrivate::QSlotObject<void (FrameWrapper::*)(QString const&), QtPrivate::List<QString const&>, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) ()
#19 0x00007fffece29386 in void doActivate<false>(QObject*, int, void**) () at /lib64/libQt5Core.so.5
#20 0x00007ffff6960e25 in lrc::api::AVModel::rendererStopped(QString const&) (this=<optimized out>, _t1=<optimized out>) at /home/amarok/Projects/jami/lrc/build-local/ringclient_autogen/include/api/moc_avmodel.cpp:316
#21 0x00007fffece29386 in void doActivate<false>(QObject*, int, void**) () at /lib64/libQt5Core.so.5
#22 0x00007ffff6951375 in lrc::api::video::Renderer::stopped(QString const&) (this=<optimized out>, _t1=<optimized out>) at /home/amarok/Projects/jami/lrc/build-local/ringclient_autogen/include/api/moc_newvideo.cpp:192
#23 0x00007fffece29386 in void doActivate<false>(QObject*, int, void**) () at /lib64/libQt5Core.so.5
#24 0x00007ffff6952669 in Video::ShmRenderer::stopShm() (this=0x36157d0) at /home/amarok/Projects/jami/lrc/src/shmrenderer.cpp:282
#25 Video::ShmRenderer::stopShm() (this=0x36157d0) at /home/amarok/Projects/jami/lrc/src/shmrenderer.cpp:268
#26 0x00007ffff695279d in Video::ShmRenderer::~ShmRenderer() (this=0x36157d0, __in_chrg=<optimized out>) at /home/amarok/Projects/jami/lrc/src/shmrenderer.cpp:138
#27 0x00007ffff69527f9 in Video::ShmRenderer::~ShmRenderer() (this=0x36157d0, __in_chrg=<optimized out>) at /home/amarok/Projects/jami/lrc/src/shmrenderer.cpp:139
#28 0x00007fffece29386 in void doActivate<false>(QObject*, int, void**) () at /lib64/libQt5Core.so.5
#29 0x00007fffecc5cc91 in QThread::finished(QThread::QPrivateSignal) () at /lib64/libQt5Core.so.5
#30 0x00007fffecc5e2c2 in QThreadPrivate::finish(void*) () at /lib64/libQt5Core.so.5
#31 0x00007fffecc5ef28 in __pthread_cleanup_class::~__pthread_cleanup_class() () at /lib64/libQt5Core.so.5
#32 0x00007fffecc5ee02 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5
#33 0x00007fffec47f3f9 in start_thread () at /lib64/libpthread.so.0
#34 0x00007fffec763903 in clone () at /lib64/libc.so.6
```https://git.jami.net/savoirfairelinux/jami-project/-/issues/1215Please detect status 488 from SIP server and offer suggestions to change codec2023-05-29T13:37:07ZreubenfirminPlease detect status 488 from SIP server and offer suggestions to change codecWhen a SIP server returns 488, it can mean a codec incompatibility. Your UI buries that 488 is returned. Please detect the status and pop up the settings asking the user to check the codecs vs what the voip provider allows.When a SIP server returns 488, it can mean a codec incompatibility. Your UI buries that 488 is returned. Please detect the status and pop up the settings asking the user to check the codecs vs what the voip provider allows.https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/498Plugins(Windows): uninstalling plugins may fail if in use2023-09-29T09:59:53ZAndreas TraczykPlugins(Windows): uninstalling plugins may fail if in useThe Windows API FreeLibrary used in dlclose reports success but the module is sometimes not actually unloaded.
This results in the removal of the plugin's files to fail.The Windows API FreeLibrary used in dlclose reports success but the module is sometimes not actually unloaded.
This results in the removal of the plugin's files to fail.https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/497Plugins: don't use plugins in call if not enabled2021-05-12T14:47:20ZAndreas TraczykPlugins: don't use plugins in call if not enabledEven if the plugins are disabled in the configuration, they are still activated during a call.Even if the plugins are disabled in the configuration, they are still activated during a call.Aline Gondim SantosAline Gondim Santoshttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/496ICE do not add ips with interfaces in a down state2021-04-12T14:43:30ZSébastien BlinICE do not add ips with interfaces in a down stateIn https://git.jami.net/savoirfairelinux/ring-daemon/-/issues/495, all the candidates (like `172.27.0.1`) come from a bad interface like:
```
9: br-b8251442502e: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN grou...In https://git.jami.net/savoirfairelinux/ring-daemon/-/issues/495, all the candidates (like `172.27.0.1`) come from a bad interface like:
```
9: br-b8251442502e: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
link/ether 02:42:4b:3f:9b:89 brd ff:ff:ff:ff:ff:ff
inet 172.27.0.1/16 brd 172.27.255.255 scope global br-b8251442502e
valid_lft forever preferred_lft forever
inet6 fe80::42:4bff:fe3f:9b89/64 scope link
valid_lft forever preferred_lft forever
```
Because state is down, it should be removedSébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/495ICE: Avoid too many objects.2021-04-08T18:54:54ZSébastien BlinICE: Avoid too many objects.```
[1617036479.318|14109|account_manager.cpp:572 ] Found 1 devices for YYYYYYYYYYYYYYYY
[1617036480.850|14109|connectionmanager.cpp:572 ] [Account 3275d56919ba0019] New response received from XXXXXXXXXX
[1617036480.850|14618|ice_tran...```
[1617036479.318|14109|account_manager.cpp:572 ] Found 1 devices for YYYYYYYYYYYYYYYY
[1617036480.850|14109|connectionmanager.cpp:572 ] [Account 3275d56919ba0019] New response received from XXXXXXXXXX
[1617036480.850|14618|ice_transport.cpp :1572 ] Add remote ICE candidate: Hac101532 1 TCP 2130706431 172.16.21.50 43855 typ host tcptype passive
[1617036480.850|14618|ice_transport.cpp :1572 ] Add remote ICE candidate: Hac101532 1 TCP 2130706175 172.16.21.50 9 typ host tcptype active
[1617036480.850|14618|ice_transport.cpp :1572 ] Add remote ICE candidate: Hac1c0001 1 TCP 2130705919 172.28.0.1 43855 typ host tcptype passive
[1617036480.850|14618|ice_transport.cpp :1572 ] Add remote ICE candidate: Hac1c0001 1 TCP 2130705663 172.28.0.1 9 typ host tcptype active
[1617036480.850|14618|ice_transport.cpp :1572 ] Add remote ICE candidate: Hc0a81001 1 TCP 2130705407 192.168.16.1 43855 typ host tcptype passive
[1617036480.850|14618|ice_transport.cpp :1572 ] Add remote ICE candidate: Hc0a81001 1 TCP 2130705151 192.168.16.1 9 typ host tcptype active
[1617036480.850|14618|ice_transport.cpp :1572 ] Add remote ICE candidate: Hac180001 1 TCP 2130704895 172.24.0.1 43855 typ host tcptype passive
[1617036480.850|14618|ice_transport.cpp :1572 ] Add remote ICE candidate: Hac180001 1 TCP 2130704639 172.24.0.1 9 typ host tcptype active
[1617036480.850|14618|ice_transport.cpp :1572 ] Add remote ICE candidate: Hac190001 1 TCP 2130704383 172.25.0.1 43855 typ host tcptype passive
[1617036480.850|14618|ice_transport.cpp :1572 ] Add remote ICE candidate: Hac190001 1 TCP 2130704127 172.25.0.1 9 typ host tcptype active
[1617036480.850|14618|ice_transport.cpp :1572 ] Add remote ICE candidate: Hac110001 1 TCP 2130703871 172.17.0.1 43855 typ host tcptype passive
[1617036480.850|14618|ice_transport.cpp :1572 ] Add remote ICE candidate: Hac110001 1 TCP 2130703615 172.17.0.1 9 typ host tcptype active
[1617036480.850|14618|ice_transport.cpp :1572 ] Add remote ICE candidate: Hac1b0001 1 TCP 2130703359 172.27.0.1 43855 typ host tcptype passive
[1617036480.850|14618|ice_transport.cpp :1572 ] Add remote ICE candidate: Hac1b0001 1 TCP 2130703103 172.27.0.1 9 typ host tcptype active
[1617036480.850|14618|ice_transport.cpp :1572 ] Add remote ICE candidate: Hac1a0001 1 TCP 2130702847 172.26.0.1 43855 typ host tcptype passive
[1617036480.850|14618|ice_transport.cpp :1572 ] Add remote ICE candidate: Hac1a0001 1 TCP 2130702591 172.26.0.1 9 typ host tcptype active
[1617036480.850|14618|ice_transport.cpp :1572 ] Add remote ICE candidate: Hac140001 1 TCP 2130702335 172.20.0.1 43855 typ host tcptype passive
[1617036480.850|14618|ice_transport.cpp :1572 ] Add remote ICE candidate: Hac140001 1 TCP 2130702079 172.20.0.1 9 typ host tcptype active
[1617036480.850|14618|ice_transport.cpp :1572 ] Add remote ICE candidate: Hac160001 1 TCP 2130701823 172.22.0.1 43855 typ host tcptype passive
[1617036480.850|14618|ice_transport.cpp :1572 ] Add remote ICE candidate: Hac160001 1 TCP 2130701567 172.22.0.1 9 typ host tcptype active
[1617036480.850|14618|ice_transport.cpp :1572 ] Add remote ICE candidate: Hac1e0001 1 TCP 2130701311 172.30.0.1 43855 typ host tcptype passive
[1617036480.850|14618|ice_transport.cpp :1572 ] Add remote ICE candidate: Hac1e0001 1 TCP 2130701055 172.30.0.1 9 typ host tcptype active
[1617036480.850|14618|ice_transport.cpp :1572 ] Add remote ICE candidate: Hc0a82001 1 TCP 2130700799 192.168.32.1 43855 typ host tcptype passive
[1617036480.851|14618|ice_transport.cpp :1572 ] Add remote ICE candidate: Hc0a82001 1 TCP 2130700543 192.168.32.1 9 typ host tcptype active
[1617036480.851|14618|ice_transport.cpp :1572 ] Add remote ICE candidate: Hac170001 1 TCP 2130700287 172.23.0.1 43855 typ host tcptype passive
[1617036480.851|14618|ice_transport.cpp :1572 ] Add remote ICE candidate: Hac170001 1 TCP 2130700031 172.23.0.1 9 typ host tcptype active
[1617036480.851|14618|ice_transport.cpp :1572 ] Add remote ICE candidate: Hac1d0001 1 TCP 2130699775 172.29.0.1 43855 typ host tcptype passive
[1617036480.851|14618|ice_transport.cpp :1572 ] Add remote ICE candidate: Hac1d0001 1 TCP 2130699519 172.29.0.1 9 typ host tcptype active
[1617036480.851|14618|ice_transport.cpp :1572 ] Add remote ICE candidate: Hac150001 1 TCP 2130699263 172.21.0.1 43855 typ host tcptype passive
[1617036480.851|14618|ice_transport.cpp :1572 ] Add remote ICE candidate: Hac150001 1 TCP 2130699007 172.21.0.1 9 typ host tcptype active
[1617036480.851|14618|ice_transport.cpp :1572 ] Add remote ICE candidate: Hac1f0001 1 TCP 2130698751 172.31.0.1 43855 typ host tcptype passive
[1617036480.851|14618|ice_transport.cpp :1572 ] Add remote ICE candidate: Rc0fc8ceb 1 TCP 16777215 192.252.140.235 15571 typ relay tcptype passive
[1617036480.851|14618|ice_transport.cpp :1076 ] [ice:0x627000011900] negotiation starting (32 remote candidates)
[1617036480.851|14618|ice_transport.cpp :1090 ] [ice:0x627000011900] start failed: Too many objects of the specified type (PJ_ETOOMANY)
```Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/494Recheck all APIs2021-12-29T19:03:54ZSé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-client-ios/-/issues/129bluetooth headset not working on iOS2023-05-17T17:49:09ZKateryna Kostiukbluetooth headset not working on iOSDuring the call, audio routed to the speaker when Cisco Bluetooth connected.During the call, audio routed to the speaker when Cisco Bluetooth connected.https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/493account loading failed when build with clang 122021-04-01T14:53:49ZKateryna Kostiukaccount loading failed when build with clang 12Certificate parsing broken. Error: "Can't export CRL: ASN1 parser: Value is not valid." Happens when gnutls use libtasn1 build with clang 12.Certificate parsing broken. Error: "Can't export CRL: ASN1 parser: Value is not valid." Happens when gnutls use libtasn1 build with clang 12.Kateryna KostiukKateryna Kostiukhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/916samsung galaxy j3 prime: Video and sound become choppy and call drops2022-01-03T02:01:58ZMaxim Cournoyersamsung galaxy j3 prime: Video and sound become choppy and call dropsBug report form
---------------
## Describe your environment
Please specify the following:
- Ring version: 20210315-01
- Device model: Samsung Galaxy J3 (SM-J327W)
- Android version: 8.1.0
- On the Samsung Galaxy J3: Play Stor...Bug report form
---------------
## Describe your environment
Please specify the following:
- Ring version: 20210315-01
- Device model: Samsung Galaxy J3 (SM-J327W)
- Android version: 8.1.0
- On the Samsung Galaxy J3: Play Store; on the other device: Tried with Play store (20210315-01) or jami-gnome built from the latest sources on GNU/Linux
## Steps to reproduce
- Can you reproduce the bug: With one of my contacts though which is using a SM-J327W device, it always occur on her side (their Jami app crashes after a while). I couldn't reproduce using a SM-J320W8 (a different, but close model).
- Steps:
1. Call Jami on a Samsung Galaxy J3 SM-J327W
1. The call originally proceeds normally, with good video and audio and a decent framerate (~15 fps on both ends).
1. After 2-5 minutes of call, the video and audio sent from the Galaxy J3 device becomes choppy, with the framerate dropping to near zero (0.09 fps) and eventually the call dropping.
- Actual result: The call drops after a while.
- Expected result: The video and audio should remain fluid, and the call should not drop even after a prolonged period of time.
## Additional information
The phone specs are available from https://www.phonearena.com/phones/Samsung-Galaxy-J3-Prime_id10506. It has the following processor and GPU:
- CPU: Quad-core, 1400 MHz, ARM Cortex-A53, 64-bit, 28 nm
- GPU: Adreno 308
- RAM: 1.5 GiBhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/355feature request: store an editable style.css in the user's config folder2023-05-12T15:23:56ZNick Econopoulyfeature request: store an editable style.css in the user's config folderIt would be great if there was a simplified `style.css` (like Firefox's `userChrome.css`) in `~/.config/jami`.
I think it'd be good to export a much simpler CSS file than the current `chatview.css` file for this. Both files would exist,...It would be great if there was a simplified `style.css` (like Firefox's `userChrome.css`) in `~/.config/jami`.
I think it'd be good to export a much simpler CSS file than the current `chatview.css` file for this. Both files would exist, but users get a simpler CSS file where they can change the fonts and color scheme without accidentally messing up some other crucial CSS.https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/492libnatpmp is always used from contribs2023-05-05T19:02:06ZMaxim Cournoyerlibnatpmp is always used from contribsThe contrib build system relies on pkg-config to detect system libraries, as done here:
```
ifeq ($(call need_pkg,'libnatpmp'),)
PKGS_FOUND += natpmp
endif
```
This never marks natpmp as found, because libnatpmp doesn't install any pkg...The contrib build system relies on pkg-config to detect system libraries, as done here:
```
ifeq ($(call need_pkg,'libnatpmp'),)
PKGS_FOUND += natpmp
endif
```
This never marks natpmp as found, because libnatpmp doesn't install any pkg-config file (.pc), thus cannot be found via pkg-config.
Possible solution: Rather than reinvent the wheel in this contrib build system, perhaps we could use Autoconf as the configuration driver of the contribs build system, which is quite capable in this regard. It could return a list of targets needed from the contribs build system to be built, and add them as dependencies.https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/491Layout update missing for rendezvous2021-04-13T13:37:59ZPierre LespagnolLayout update missing for rendezvous# Scenario
- Bob call rendezvous-bob
- Alice call rendezvous-bob
- Bob create conf with rendezvous-bob and Roger
- Alice quit rendezvous-bob
- Alice call rendezvous-bob
# Current Result
- Bob don't have the new layout with Alice# Scenario
- Bob call rendezvous-bob
- Alice call rendezvous-bob
- Bob create conf with rendezvous-bob and Roger
- Alice quit rendezvous-bob
- Alice call rendezvous-bob
# Current Result
- Bob don't have the new layout with AlicePierre LespagnolPierre Lespagnolhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/490Plugin: load status is not saved when installed2021-03-31T19:50:42ZAline Gondim SantosPlugin: load status is not saved when installedWhen a plugin is installed, jami is not saving it's load status.
Hence, in the next time we open jami, plugin may not be loaded.When a plugin is installed, jami is not saving it's load status.
Hence, in the next time we open jami, plugin may not be loaded.Aline Gondim SantosAline Gondim Santoshttps://git.jami.net/savoirfairelinux/jami-client-macos/-/issues/279account creation: update fields title for jams connection2021-04-27T18:13:22ZGuillaume Helleraccount creation: update fields title for jams connectionRename followig fields to:
MacOS
- Connect to account manager --> Connect to a JAMS server
- Account manager --> JAMS URL
iOS
- Connect to account manager --> Connect to a JAMS server
- Enter account manager URI --> Enter JAMS URL
- Ac...Rename followig fields to:
MacOS
- Connect to account manager --> Connect to a JAMS server
- Account manager --> JAMS URL
iOS
- Connect to account manager --> Connect to a JAMS server
- Enter account manager URI --> Enter JAMS URL
- Account manager --> JAMS URLKateryna KostiukKateryna Kostiukhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/915Cannot set a local port other than 5060 on Android2022-08-31T15:28:51Zalex-kruppCannot set a local port other than 5060 on Android- Ring version: Together - 20210226-01
- Android version: 8.1.0
- What build you are using: Play Store
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. Change Account/Advanced/LocalPort to e.g. 5061...- Ring version: Together - 20210226-01
- Android version: 8.1.0
- What build you are using: Play Store
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. Change Account/Advanced/LocalPort to e.g. 5061
2. Switch away from Account
3. Switch to Account and check Account/Advanced/LocalPort
- Actual result: 5060
- Expected result: 5061