jami-daemon issueshttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues2021-02-19T23:09:25Zhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/236Recorder stop during a switch of Input2021-02-19T23:09:25ZPierre LespagnolRecorder stop during a switch of InputPierre LespagnolPierre Lespagnolhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/235Black screen when call Android devices2020-10-05T18:34:16ZPierre LespagnolBlack screen when call Android devicesIf the daemon fail to receive the first packet sent by MediaCodec (Android with hardware acceleration), the decoding session fail to be initialised.If the daemon fail to receive the first packet sent by MediaCodec (Android with hardware acceleration), the decoding session fail to be initialised.https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/232Black screen with Mediacodec H2642020-09-09T13:11:11ZCyrille BéraudBlack screen with Mediacodec H264If the first packet sent by a stream using Mediacodec H264 (Acceleration Android) is not received, the stream is corrupted
[log](/uploads/1a28454268b3c80ecff5a74d0f6ab750/log)If the first packet sent by a stream using Mediacodec H264 (Acceleration Android) is not received, the stream is corrupted
[log](/uploads/1a28454268b3c80ecff5a74d0f6ab750/log)Itération 21Mohamed ChibaniPierre LespagnolMohamed Chibanihttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/231HW nvidia - Rotation is not handled properly during a call when switching camera2021-01-28T15:48:49ZCyrille BéraudHW nvidia - Rotation is not handled properly during a call when switching camera- Activate HW acceleration on Linux/Jami
- Make a call (phone vertically) (android)
- switch camera- Activate HW acceleration on Linux/Jami
- Make a call (phone vertically) (android)
- switch cameraIteration 18Adrien BéraudPierre LespagnolAdrien Béraudhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/229EPIC - Improve video quality for weak connections2020-06-29T14:11:47ZGuillaume HellerEPIC - Improve video quality for weak connectionsThe video quality should be good (ideally without any visible glitch) even on weak ADSL connexions (800 kbps upload or less).
We first need to analyze and characterize the quality issues experienced by users on these types of connections...The video quality should be good (ideally without any visible glitch) even on weak ADSL connexions (800 kbps upload or less).
We first need to analyze and characterize the quality issues experienced by users on these types of connections. Then suggest and implement solutions adapted to the context.Iteration 18Pierre LespagnolMohamed ChibaniPierre Lespagnolhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/223Audio lost after 5min2020-08-14T17:10:41ZGuillaume HellerAudio lost after 5minIn some cases (not identified yet), the audio is lost exactly after 5min.
It can also happens that the video freezes, but the audio remains.In some cases (not identified yet), the audio is lost exactly after 5min.
It can also happens that the video freezes, but the audio remains.Iteration 18Mohamed ChibaniMohamed Chibanihttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/222Recording video calls crash after some time2020-07-07T20:06:36ZAdrien BéraudRecording video calls crash after some timeIteration 18Pierre LespagnolPierre Lespagnolhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/221Video rotation not considered in recorded video2020-06-20T17:34:20ZAdrien BéraudVideo rotation not considered in recorded videoIteration 18Pierre LespagnolPierre Lespagnolhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/220Explore WebRTC support2023-11-20T14:19:22ZAdrien BéraudExplore WebRTC supportBacklogLarbi GharibLarbi Gharibhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/214dring hogs cpu when viewing Settings->Media page in jami-gnome2021-07-14T19:27:41ZArvid Brodindring hogs cpu when viewing Settings->Media page in jami-gnomeHow to reproduce:
* Start dring and jami-gnome.
* Select Settings->Media page.
* dring cpu usage goes to 100 % according to top (i.e. one core fully used), and stays there until I leave the Media settings page. This happens also with no...How to reproduce:
* Start dring and jami-gnome.
* Select Settings->Media page.
* dring cpu usage goes to 100 % according to top (i.e. one core fully used), and stays there until I leave the Media settings page. This happens also with no webcam/video device attached to the computer.
System info:
$ /usr/lib/ring/dring --version
Jami Daemon 9.1.0, by Savoir-faire Linux 2004-2019
https://jami.net/
[Video support enabled]
$ jami-gnome --version
74ef874ea412985a5cfb49e3e162d20b5707733b - unknown
(About page says "Free as in Freedom" built on 2020-04-14 20:24:50 UTC)
OS: Xubuntu 18.04 with kernel 5.5.17
This is NOT repeatable on Xubuntu 20.04 beta with Jami Daemon 7.4.0/jami-gnome "Live Free or Die" built on 2020-03-23 06:24:58.Pierre LespagnolPierre Lespagnolhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/212Video conferencing - known issues2020-06-19T17:26:28ZSébastien BlinVideo conferencing - known issues+ [x] Picture size 0x0
+ [x] Audio sometimes master receives sound, but peers not after adding someone
+ [x] Grey screen sometimes for peers (decrypt error resulting in a gray or black screen for non master)
+ [x] Lot of HOLD/Preview is...+ [x] Picture size 0x0
+ [x] Audio sometimes master receives sound, but peers not after adding someone
+ [x] Grey screen sometimes for peers (decrypt error resulting in a gray or black screen for non master)
+ [x] Lot of HOLD/Preview issues
+ [x] Add a participant is slow
+ [x] Crash when removing/adding someone to the confSébastien BlinPierre LespagnolSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/200ffmpeg: add G726, iLBC codecs (SIP: no audio in call)2023-12-27T18:07:22ZLinus G.ffmpeg: add G726, iLBC codecs (SIP: no audio in call)I made an internal call via fritz.box and I called myself via the telephone by **600. I heared the ringtone but when I accepted the call, neither of us did hear anything. I'm using Kubuntu 18.04. I guess, these are the important lines in...I made an internal call via fritz.box and I called myself via the telephone by **600. I heared the ringtone but when I accepted the call, neither of us did hear anything. I'm using Kubuntu 18.04. I guess, these are the important lines in the log:
```
[1577674451.545|19511|sipcall.cpp :906 ] [call:3558973192781136] startAllMedia()
[1577674451.545|19511|sip_utils.cpp :203 ] Registered thread 0x7ff0bdff6dd0 (0x4C36)
[1577674451.546|19511|sdp.cpp :599 ] Could not find rtpmap attribute
[1577674451.546|19511|sdp.cpp :599 ] Could not find rtpmap attribute
[1577674451.546|19511|sdp.cpp :616 ] Could not find codec G726-32
[1577674451.546|19511|sdp.cpp :616 ] Could not find codec G726-32
[1577674451.546|19511|sdp.cpp :616 ] Could not find codec G726-40
[1577674451.546|19511|sdp.cpp :616 ] Could not find codec G726-24
[1577674451.546|19511|sdp.cpp :616 ] Could not find codec iLBC
[1577674451.546|19511|sdp.cpp :616 ] Could not find codec telephone-event
[1577674451.546|19511|sipcall.cpp :956 ] [call:3558973192781136] [SDP:slot#0] Missing remote codec
[1577674451.546|19511|video_rtp_session.cpp:91 ] No socket pair, keyframe request callback not possible
```
Full log: https://pastebin.com/RtTvcmBY
Kind regardsPierre LespagnolPierre Lespagnolhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/184add support for jack audio connection kit2021-07-16T18:10:57Zjoinlawadd support for jack audio connection kitadding support for jack audio connection kit
a low-latency audio server
http://www.jackaudio.org/adding support for jack audio connection kit
a low-latency audio server
http://www.jackaudio.org/https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/183[FR] Stop trying to auto-manage volume or add option to disable2020-12-29T16:04:42ZIT wrx[FR] Stop trying to auto-manage volume or add option to disableRight now, at least in gnu+linux distributions, it seems jami tries to auto-manage the volume of inputs and outputs. While in theory this would be nice, in practice, it can make a call untenable. Having two people trying to set their vol...Right now, at least in gnu+linux distributions, it seems jami tries to auto-manage the volume of inputs and outputs. While in theory this would be nice, in practice, it can make a call untenable. Having two people trying to set their volume with jami also changing it, is chaos. Please consider either just stop auto-managing audio levels, or at least allow users to disable this feature.
thankshttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/182Be able to start video call with no camera, a file or a screen share.2019-11-21T20:25:13ZSébastien BlinBe able to start video call with no camera, a file or a screen share.All is in the title. Actually, a video call is only startable via a camera, then we can share a fileAll is in the title. Actually, a video call is only startable via a camera, then we can share a filehttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/178Conferences: record doesn't work (no file created)2020-09-08T15:31:08ZSébastien BlinConferences: record doesn't work (no file created)Pierre LespagnolPierre Lespagnolhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/177Video Call immediately stop sending video (dmesg: general protection fault)2020-04-16T16:30:34ZTim RühsenVideo Call immediately stop sending video (dmesg: general protection fault)With an old LogiTech HD 720p camera on Debian unstable: on video call connect my picture freezes and the other side gets no video.
`dmesg` shows
```
traps: dring[2098] general protection fault ip:5647869f6dd9 sp:7f6423023d40 error:0 in ...With an old LogiTech HD 720p camera on Debian unstable: on video call connect my picture freezes and the other side gets no video.
`dmesg` shows
```
traps: dring[2098] general protection fault ip:5647869f6dd9 sp:7f6423023d40 error:0 in dring[5647863d9000+df4000]
```
Linux ryzen 5.3.0-2-amd64 #1 SMP Debian 5.3.9-1 (2019-11-09) x86_64 GNU/Linux
jami 20191113.4.31768e1~dfsg1-1
Any idea what to try or how to debug ?Pierre LespagnolPierre Lespagnolhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/13Add PipeWire support on Linux2024-03-22T15:44:49ZannaAdd PipeWire support on LinuxTo quote the PipeWire website (https://pipewire.org/#about):
"PipeWire is a project that aims to greatly improve handling of audio and video under Linux. It aims to support the usecases currently handled by both PulseAudio and Jack and ...To quote the PipeWire website (https://pipewire.org/#about):
"PipeWire is a project that aims to greatly improve handling of audio and video under Linux. It aims to support the usecases currently handled by both PulseAudio and Jack and at the same time provide same level of powerful handling of Video input and output. It also introduces a security model that makes interacting with audio and video devices from containerized applications easy, with supporting Flatpak applications being the primary goal. Alongside Wayland and Flatpak we expect PipeWire to provide a core building block for the future of Linux application development.
Features include:
* Capture and playback of audio and video with minimal latency.
* Real-time Multimedia processing on audio and video.
* Multiprocess architecture to let applications share multimedia content.
* GStreamer plugins for easy use and integration in current applications.
* Sandboxed applications support.
See Flatpak for more info."
@pgorley What do you think?François-Simon Fauteux-ChapleauFrançois-Simon Fauteux-Chapleauhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/975Link voice setup callback to host (without rtp session)2024-03-25T18:36:16ZSébastien BlinLink voice setup callback to host (without rtp session)https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/974Various asserts and crashes with TURN / PJNATH2024-03-25T18:29:13ZAdrien BéraudVarious asserts and crashes with TURN / PJNATHTypical assertion when PJSIP built with asserts:
```
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
2024-03-22 14:13:31.793 9191-9191 D...Typical assertion when PJSIP built with asserts:
```
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A Build fingerprint: 'google/cheetah/cheetah:14/AP1A.240305.019.A1/11445699:user/release-keys'
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A Revision: 'MP1.0'
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A ABI: 'arm64'
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A Timestamp: 2024-03-22 14:13:31.550572829-0400
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A Process uptime: 2s
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A Cmdline: cx.ring
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A pid: 8414, tid: 9172, name: Thread-64 >>> cx.ring <<<
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A uid: 10352
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A tagged_addr_ctrl: 0000000000000001 (PR_TAGGED_ADDR_ENABLE)
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A signal 6 (SIGABRT), code -1 (SI_QUEUE), fault addr --------
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A Abort message: '../src/pjnath/turn_session.c:740: pj_status_t pj_turn_session_alloc(pj_turn_session *, const pj_turn_alloc_param *): assertion "sess->state>PJ_TURN_STATE_NULL && sess->state<=PJ_TURN_STATE_RESOLVED" failed'
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A x0 0000000000000000 x1 00000000000023d4 x2 0000000000000006 x3 000000795e531320
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A x4 2f333639622d6d6e x5 2f333639622d6d6e x6 2f333639622d6d6e x7 7f7f7f7f7f7f7f7f
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A x8 00000000000000f0 x9 0000007d40c87200 x10 0000000000000001 x11 0000007d40cd1ba0
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A x12 0000007d5ac86020 x13 000000007fffffff x14 00000000009ffbec x15 00000247cba606d0
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A x16 0000007d40d3cfc8 x17 0000007d40d1a160 x18 000000795b0d8000 x19 00000000000020de
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A x20 00000000000023d4 x21 00000000ffffffff x22 0000000000002374 x23 00000000000020de
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A x24 000000795e5318b0 x25 000000795e5318b0 x26 000000795e531bf0 x27 00000000000fc000
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A x28 00000000000fe000 x29 000000795e5313a0
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A lr 0000007d40cc2e48 sp 000000795e531300 pc 0000007d40cc2e74 pst 0000000000001000
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A 11 total frames
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A backtrace:
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A #00 pc 000000000005ee74 /apex/com.android.runtime/lib64/bionic/libc.so (abort+164) (BuildId: 33ad5959e2b38fc822cda3c642e16c94)
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A #01 pc 000000000005f284 /apex/com.android.runtime/lib64/bionic/libc.so (__assert2+36) (BuildId: 33ad5959e2b38fc822cda3c642e16c94)
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A #02 pc 0000000001922e2c /data/app/~~VtmIPQIw72akn02OjhBU0g==/cx.ring-aDZMbBTi4zOBSAIxpYGD2w==/base.apk!libjami-core-jni.so (offset 0xd64000) (pj_turn_session_alloc+284) (BuildId: f128353698d79bade99658daa4d09034a3aee20e)
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A #03 pc 000000000192a61c /data/app/~~VtmIPQIw72akn02OjhBU0g==/cx.ring-aDZMbBTi4zOBSAIxpYGD2w==/base.apk!libjami-core-jni.so (offset 0xd64000) (BuildId: f128353698d79bade99658daa4d09034a3aee20e)
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A #04 pc 000000000192a258 /data/app/~~VtmIPQIw72akn02OjhBU0g==/cx.ring-aDZMbBTi4zOBSAIxpYGD2w==/base.apk!libjami-core-jni.so (offset 0xd64000) (BuildId: f128353698d79bade99658daa4d09034a3aee20e)
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A #05 pc 000000000194d5f4 /data/app/~~VtmIPQIw72akn02OjhBU0g==/cx.ring-aDZMbBTi4zOBSAIxpYGD2w==/base.apk!libjami-core-jni.so (offset 0xd64000) (BuildId: f128353698d79bade99658daa4d09034a3aee20e)
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A #06 pc 00000000019414bc /data/app/~~VtmIPQIw72akn02OjhBU0g==/cx.ring-aDZMbBTi4zOBSAIxpYGD2w==/base.apk!libjami-core-jni.so (offset 0xd64000) (ioqueue_dispatch_write_event+416) (BuildId: f128353698d79bade99658daa4d09034a3aee20e)
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A #07 pc 0000000001945428 /data/app/~~VtmIPQIw72akn02OjhBU0g==/cx.ring-aDZMbBTi4zOBSAIxpYGD2w==/base.apk!libjami-core-jni.so (offset 0xd64000) (pj_ioqueue_poll+1476) (BuildId: f128353698d79bade99658daa4d09034a3aee20e)
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A #08 pc 0000000001739b98 /data/app/~~VtmIPQIw72akn02OjhBU0g==/cx.ring-aDZMbBTi4zOBSAIxpYGD2w==/base.apk!libjami-core-jni.so (offset 0xd64000) (BuildId: f128353698d79bade99658daa4d09034a3aee20e)
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A #09 pc 00000000000ca7cc /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*)+204) (BuildId: 33ad5959e2b38fc822cda3c642e16c94)
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A #10 pc 00000000000607b0 /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+64) (BuildId: 33ad5959e2b38fc822cda3c642e16c94)
```Sébastien BlinFrançois-Simon Fauteux-ChapleauSébastien Blin