jami-project issueshttps://git.jami.net/savoirfairelinux/jami-project/-/issues2022-12-21T17:42:04Zhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1425Multi-Swarm (Jami-Beta; Windows 10 ) -> Swarm (Android) does not work2022-12-21T17:42:04ZElysMulti-Swarm (Jami-Beta; Windows 10 ) -> Swarm (Android) does not workNot sure if this is an issue or not:
using Jami beta version (Windows 10)
Jami beta version (Android)
But sending text messages Multi-Swarm -> Swarm does not work
I created a group (user 1(me),user 2 (second Jami account).
If I use t...Not sure if this is an issue or not:
using Jami beta version (Windows 10)
Jami beta version (Android)
But sending text messages Multi-Swarm -> Swarm does not work
I created a group (user 1(me),user 2 (second Jami account).
If I use the group to send text messages the android user never receives the text message.
However no issues if I don't use the "group chat" function and just send a message to the same user in the contact listhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/919i can't register on a sip server with TCP2022-11-11T16:54:22ZTolminoi can't register on a sip server with TCPi'm on OSX and on IOS and there isn't any way to define to use TCP Sip transporti'm on OSX and on IOS and there isn't any way to define to use TCP Sip transporthttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1389(Swarm <-> Non-Swarm?) Sending text messages and/or attachments never works2022-08-09T15:01:21ZElys(Swarm <-> Non-Swarm?) Sending text messages and/or attachments never worksIt does not only involve attachments but also simple text messages (See: https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1053 )
> does **NEVER** work (even if you add the Non-Swarm Contact (Version 20210521-01; your s...It does not only involve attachments but also simple text messages (See: https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1053 )
> does **NEVER** work (even if you add the Non-Swarm Contact (Version 20210521-01; your same user account) again):
> Jami Android Version 20220121-01 <-> Jami Android Version 20210521-01
> Jami Windows 10 Version 202112221635 <-> Jami Android Version 20210521-01
(Android:) Sometimes you receive an invite to add the same contact (that should receive the text message) again.
But you never get any text message.
EDIT: However, you can make voice and/ or video calls without any problems.https://git.jami.net/savoirfairelinux/jami-project/-/issues/1283Do not add [nightly] repos to sources.list.d2021-08-03T15:22:22ZIaroslav GridinDo not add [nightly] repos to sources.list.dCurrently, jami-all package from https://dl.jami.net/ adds jami's key and repo to sources.list.d. Moreover, if package is installed from "internal" repo, it adds "nightly" still and overwrites the internal sources list. This seems likely...Currently, jami-all package from https://dl.jami.net/ adds jami's key and repo to sources.list.d. Moreover, if package is installed from "internal" repo, it adds "nightly" still and overwrites the internal sources list. This seems likely to cause issues to me and adding repo and key is not necessarily wanted by repository uses.https://git.jami.net/savoirfairelinux/jami-project/-/issues/10013 persons conference call screen disapearing after one participant disconnected2020-06-23T20:50:09ZLarbi Gharib3 persons conference call screen disapearing after one participant disconnected**Environment:**
* **Host participant:** Ubuntu 18.04
* **Invited participant 1:** iOS
* **Invited participant 2:** Android
**Issue steps to reproduce:**
1. Call participant 1 with video
2. Participant 1 accepts call
3. Add participan...**Environment:**
* **Host participant:** Ubuntu 18.04
* **Invited participant 1:** iOS
* **Invited participant 2:** Android
**Issue steps to reproduce:**
1. Call participant 1 with video
2. Participant 1 accepts call
3. Add participant 2 with video
4. Participant 2 accepts call
5. Call begins (15 minutes)
6. Participant 1 leave call
**Expected behavior:**
Conference call falls back to 1 to 1 video call and we can still see each other
**Actual behavior:**
Host participant cannot see the participant 2 and only sees the chat (Tried to click on the conference call [participant 1 contact name] and the participant 2 contact name in the left column call history, same result).
However participant 2 can see host participant as if the call fell back to a 1 to 1 video call.Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/836Debian to Android2020-03-23T20:46:39ZKitchMDebian to AndroidCall from Android on cellular network to Debian on fiber network allows a text message. However, there is no audio or video available.Call from Android on cellular network to Debian on fiber network allows a text message. However, there is no audio or video available.https://git.jami.net/savoirfairelinux/jami-project/-/issues/276Create browser plugin for Ring2020-02-27T13:17:59ZJami BotCreate browser plugin for RingIssue generated from Tuleap's migration script.
**Originally submitted by: Alexandre Lision (alision)**
<p>For now Ring can work with native clients on different platforms (OSX, Windows, Linux, Android...)</p>
<p>We would like to m...Issue generated from Tuleap's migration script.
**Originally submitted by: Alexandre Lision (alision)**
<p>For now Ring can work with native clients on different platforms (OSX, Windows, Linux, Android...)</p>
<p>We would like to make a web plugin that allows Ring to run in Chromium.</p>
<p>If it is possible, make it work in Firefox as well.</p>https://git.jami.net/savoirfairelinux/jami-project/-/issues/474gitlab setup (missing email notifications)2019-03-02T19:32:00ZRing Thinggitlab setup (missing email notifications)I don't get email notifications about the responses to the issue I had created, so maybe something needs to be fixed in the configuration.
Also, apologies for not having filled the bug template, but it is easy to overlook, it's not sele...I don't get email notifications about the responses to the issue I had created, so maybe something needs to be fixed in the configuration.
Also, apologies for not having filled the bug template, but it is easy to overlook, it's not selected by default for ring-client-android. It has to be chosen manually.Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/68lrc: heap-use-after-free detected by ASAN when deleting an account2018-05-25T13:36:42ZJami Botlrc: heap-use-after-free detected by ASAN when deleting an accountIssue generated from Tuleap's migration script.
**Originally submitted by: Stepan Salenikovich (ssalenik)**
systematic
Removing "Test" "a8d2da906eae7749"
=================================================================
==30971...Issue generated from Tuleap's migration script.
**Originally submitted by: Stepan Salenikovich (ssalenik)**
systematic
Removing "Test" "a8d2da906eae7749"
=================================================================
==30971==ERROR: AddressSanitizer: heap-use-after-free on address 0x60400031df90 at pc 0x4ebfa9 bp 0x7fffffffc150 sp 0x7fffffffc140
READ of size 4 at 0x60400031df90 thread T0
\#0 0x4ebfa8 in QModelIndex::isValid() const /usr/include/x86\_64-linux-gnu/qt5/QtCore/qabstractitemmodel.h:64
\#1 0x4ebfa8 in operator() /home/ssalenikovich/projects/ring-client-gnome/src/accountview.cpp:461
\#2 0x4ebfa8 in call /usr/include/x86\_64-linux-gnu/qt5/QtCore/qobjectdefs\_impl.h:494
\#3 0x4ebfa8 in call<QtPrivate::List<const QModelIndex&, const QModelIndex&>, void> /usr/include/x86\_64-linux-gnu/qt5/QtCore/qobjectdefs\_impl.h:551
\#4 0x4ebfa8 in impl /usr/include/x86\_64-linux-gnu/qt5/QtCore/qobject\_impl.h:192
\#5 0x7ffff50db359 in QMetaObject::activate(QObject\*, int, int, void\*\*) (/usr/lib/x86\_64-linux-gnu/libQt5Core.so.5+0x312359)
\#6 0x7ffff505b099 in QItemSelectionModel::currentChanged(QModelIndex const&, QModelIndex const&) (/usr/lib/x86\_64-linux-gnu/libQt5Core.so.5+0x292099)
\#7 0x7ffff50637a9 (/usr/lib/x86\_64-linux-gnu/libQt5Core.so.5+0x29a7a9)
\#8 0x7ffff50652e8 (/usr/lib/x86\_64-linux-gnu/libQt5Core.so.5+0x29c2e8)
\#9 0x7ffff50db9c8 in QMetaObject::activate(QObject\*, int, int, void\*\*) (/usr/lib/x86\_64-linux-gnu/libQt5Core.so.5+0x3129c8)
\#10 0x7ffff51593d3 in QAbstractItemModel::rowsAboutToBeRemoved(QModelIndex const&, int, int, QAbstractItemModel::QPrivateSignal) (/usr/lib/x86\_64-linux-gnu/libQt5Core.so.5+0x3903d3)
\#11 0x7ffff5053589 in QAbstractItemModel::beginRemoveRows(QModelIndex const&, int, int) (/usr/lib/x86\_64-linux-gnu/libQt5Core.so.5+0x28a589)
\#12 0x6023db in AccountModel::remove(Account\*) /home/ssalenikovich/projects/ring-lrc/src/accountmodel.cpp:904
\#13 0x4edb43 in remove\_account /home/ssalenikovich/projects/ring-client-gnome/src/accountview.cpp:282
\#14 0x7ffff562b503 (/usr/lib/x86\_64-linux-gnu/libgobject-2.0.so.0+0x10503)
\#15 0x7ffff5644fa6 in g\_signal\_emit\_valist (/usr/lib/x86\_64-linux-gnu/libgobject-2.0.so.0+0x29fa6)
\#16 0x7ffff56458fe in g\_signal\_emit (/usr/lib/x86\_64-linux-gnu/libgobject-2.0.so.0+0x2a8fe)
\#17 0x7ffff674121c (/usr/lib/x86\_64-linux-gnu/libgtk-3.so.0+0x10821c)
\#18 0x7ffff6741274 (/usr/lib/x86\_64-linux-gnu/libgtk-3.so.0+0x108274)
\#19 0x7ffff562b503 (/usr/lib/x86\_64-linux-gnu/libgobject-2.0.so.0+0x10503)
\#20 0x7ffff5644fa6 in g\_signal\_emit\_valist (/usr/lib/x86\_64-linux-gnu/libgobject-2.0.so.0+0x29fa6)
\#21 0x7ffff56458fe in g\_signal\_emit (/usr/lib/x86\_64-linux-gnu/libgobject-2.0.so.0+0x2a8fe)
\#22 0x7ffff673f1ff (/usr/lib/x86\_64-linux-gnu/libgtk-3.so.0+0x1061ff)
\#23 0x7fffee813d8f in ffi\_call\_unix64 (/usr/lib/x86\_64-linux-gnu/libffi.so.6+0x5d8f)
\#24 0x7fffee8137f7 in ffi\_call (/usr/lib/x86\_64-linux-gnu/libffi.so.6+0x57f7)
\#25 0x7ffff562bf3b in g\_cclosure\_marshal\_generic\_va (/usr/lib/x86\_64-linux-gnu/libgobject-2.0.so.0+0x10f3b)
\#26 0x7ffff562b503 (/usr/lib/x86\_64-linux-gnu/libgobject-2.0.so.0+0x10503)
\#27 0x7ffff5644fa6 in g\_signal\_emit\_valist (/usr/lib/x86\_64-linux-gnu/libgobject-2.0.so.0+0x29fa6)
\#28 0x7ffff56458fe in g\_signal\_emit (/usr/lib/x86\_64-linux-gnu/libgobject-2.0.so.0+0x2a8fe)
\#29 0x7ffff67e4290 (/usr/lib/x86\_64-linux-gnu/libgtk-3.so.0+0x1ab290)
\#30 0x7ffff562e29d in g\_cclosure\_marshal\_VOID\_\_BOXEDv (/usr/lib/x86\_64-linux-gnu/libgobject-2.0.so.0+0x1329d)
\#31 0x7ffff562b503 (/usr/lib/x86\_64-linux-gnu/libgobject-2.0.so.0+0x10503)
\#32 0x7ffff5644fa6 in g\_signal\_emit\_valist (/usr/lib/x86\_64-linux-gnu/libgobject-2.0.so.0+0x29fa6)
\#33 0x7ffff56458fe in g\_signal\_emit (/usr/lib/x86\_64-linux-gnu/libgobject-2.0.so.0+0x2a8fe)
\#34 0x7ffff67e187d (/usr/lib/x86\_64-linux-gnu/libgtk-3.so.0+0x1a887d)
\#35 0x7ffff67e2cca (/usr/lib/x86\_64-linux-gnu/libgtk-3.so.0+0x1a9cca)
\#36 0x7ffff67e5704 (/usr/lib/x86\_64-linux-gnu/libgtk-3.so.0+0x1ac704)
\#37 0x7ffff67b8daa in gtk\_event\_controller\_handle\_event (/usr/lib/x86\_64-linux-gnu/libgtk-3.so.0+0x17fdaa)
\#38 0x7ffff6954fdc (/usr/lib/x86\_64-linux-gnu/libgtk-3.so.0+0x31bfdc)
\#39 0x7ffff6827608 (/usr/lib/x86\_64-linux-gnu/libgtk-3.so.0+0x1ee608)
\#40 0x7ffff562b503 (/usr/lib/x86\_64-linux-gnu/libgobject-2.0.so.0+0x10503)
\#41 0x7ffff5644a4f in g\_signal\_emit\_valist (/usr/lib/x86\_64-linux-gnu/libgobject-2.0.so.0+0x29a4f)
\#42 0x7ffff56458fe in g\_signal\_emit (/usr/lib/x86\_64-linux-gnu/libgobject-2.0.so.0+0x2a8fe)
\#43 0x7ffff69588c3 (/usr/lib/x86\_64-linux-gnu/libgtk-3.so.0+0x31f8c3)
\#44 0x7ffff6824f1d (/usr/lib/x86\_64-linux-gnu/libgtk-3.so.0+0x1ebf1d)
\#45 0x7ffff6826b2d in gtk\_main\_do\_event (/usr/lib/x86\_64-linux-gnu/libgtk-3.so.0+0x1edb2d)
\#46 0x7ffff63c3b41 (/usr/lib/x86\_64-linux-gnu/libgdk-3.so.0+0x50b41)
\#47 0x7ffff5355c3c in g\_main\_context\_dispatch (/lib/x86\_64-linux-gnu/libglib-2.0.so.0+0x49c3c)
\#48 0x7ffff5355f1f (/lib/x86\_64-linux-gnu/libglib-2.0.so.0+0x49f1f)
\#49 0x7ffff5355fcb in g\_main\_context\_iteration (/lib/x86\_64-linux-gnu/libglib-2.0.so.0+0x49fcb)
\#50 0x7ffff591667b in g\_application\_run (/usr/lib/x86\_64-linux-gnu/libgio-2.0.so.0+0xa967b)
\#51 0x4b957f in main /home/ssalenikovich/projects/ring-client-gnome/src/main.cpp:45
\#52 0x7ffff2c14a3f in \_\_libc\_start\_main (/lib/x86\_64-linux-gnu/libc.so.6+0x20a3f)
\#53 0x4b93d8 in \_start (/home/ssalenikovich/projects/ring-client-gnome/build/gnome-ring+0x4b93d8)
0x60400031df90 is located 0 bytes inside of 40-byte region [0x60400031df90,0x60400031dfb8)
freed by thread T0 here:
\#0 0x7ffff6f556af in operator delete(void\*) (/usr/lib/x86\_64-linux-gnu/libasan.so.1+0x586af)
\#1 0x7ffff505094e in QPersistentModelIndex::operator=(QModelIndex const&) (/usr/lib/x86\_64-linux-gnu/libQt5Core.so.5+0x28794e)
previously allocated by thread T0 here:
\#0 0x7ffff6f551af in operator new(unsigned long) (/usr/lib/x86\_64-linux-gnu/libasan.so.1+0x581af)
\#1 0x7ffff504d485 (/usr/lib/x86\_64-linux-gnu/libQt5Core.so.5+0x284485)
SUMMARY: AddressSanitizer: heap-use-after-free /usr/include/x86\_64-linux-gnu/qt5/QtCore/qabstractitemmodel.h:64 QModelIndex::isValid() const
Shadow bytes around the buggy address:
0x0c088005bba0: fa fa fd fd fd fd fd fa fa fa fd fd fd fd fd fa
0x0c088005bbb0: fa fa fd fd fd fd fd fa fa fa 00 00 00 00 04 fa
0x0c088005bbc0: fa fa fd fd fd fd fd fd fa fa 00 00 00 00 00 fa
0x0c088005bbd0: fa fa fd fd fd fd fd fa fa fa 00 00 00 00 02 fa
0x0c088005bbe0: fa fa fd fd fd fd fd fa fa fa fd fd fd fd fd fd
=>0x0c088005bbf0: fa fa[fd]fd fd fd fd fa fa fa fd fd fd fd fd fd
0x0c088005bc00: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c088005bc10: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c088005bc20: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c088005bc30: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x0c088005bc40: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
Shadow byte legend (one shadow byte represents 8 application bytes):
Addressable: 00
Partially addressable: 01 02 03 04 05 06 07
Heap left redzone: fa
Heap right redzone: fb
Freed heap region: fd
Stack left redzone: f1
Stack mid redzone: f2
Stack right redzone: f3
Stack partial redzone: f4
Stack after return: f5
Stack use after scope: f8
Global redzone: f9
Global init order: f6
Poisoned by user: f7
Contiguous container OOB:fc
ASan internal: fe
==30971==ABORTING
[Thread 0x7fffdba76700 (LWP 30978) exited]
[Thread 0x7ffff7f15a40 (LWP 30971) exited]
[Inferior 1 (process 30971) exited with code 01]https://git.jami.net/savoirfairelinux/jami-project/-/issues/72New year crash in LRC2018-05-25T13:36:24ZJami BotNew year crash in LRCIssue generated from Tuleap's migration script.
**Originally submitted by: Emmanuel Lepage Vallee (elv13)**
The new time calculation code is broken as each values can be negative and this isn't taken into account.
I will revert to ...Issue generated from Tuleap's migration script.
**Originally submitted by: Emmanuel Lepage Vallee (elv13)**
The new time calculation code is broken as each values can be negative and this isn't taken into account.
I will revert to a version based on my old code but including the changes introduced by the rewrite.
It is faster anyway. In my opinion, it is also clear and simple and don't depend on 3rd party APIs at all, just plain C and decimal logichttps://git.jami.net/savoirfairelinux/jami-project/-/issues/77daemon/lrc: bizzare call state transitions when call fails immediately2018-05-25T13:36:07ZJami Botdaemon/lrc: bizzare call state transitions when call fails immediatelyIssue generated from Tuleap's migration script.
**Originally submitted by: Stepan Salenikovich (ssalenik)**
It seems like when a call fails, lrc puts in Failed -> Over state, but then a new call object is created in the Failed state.
...Issue generated from Tuleap's migration script.
**Originally submitted by: Stepan Salenikovich (ssalenik)**
It seems like when a call fails, lrc puts in Failed -> Over state, but then a new call object is created in the Failed state.
lrc log:
Creating the call to "ring" failed
Calling action ACCEPT (0) on Call(0x603000b18aa0) with state "Dialing" . Become "Failed"
Call State Changed for call "15222503668050492823" . New state : "FAILURE"
Call not found "15222503668050492823" new state "FAILURE"
New foreign call: "15222503668050492823"
Building call "15222503668050492823" failed, it may already have been destroyed by the daemon
Call State Changed for call "15222503668050492823" . New state : "OVER"
Call not found "15222503668050492823" new state "OVER"
New foreign call: "15222503668050492823"
Building call "15222503668050492823" failed, it may already have been destroyed by the daemon
State changing from "Failed" to "Over" on Call(0x603000b18aa0)
Cannot remove Call(0x603000b18aa0) : call not found in tree
Calling action REFUSE (1) on Call(0x603000b18aa0) with state "Failed" . Become "Over"https://git.jami.net/savoirfairelinux/jami-project/-/issues/82IM history not loading for some Persons2018-05-25T13:35:56ZJami BotIM history not loading for some PersonsIssue generated from Tuleap's migration script.
**Originally submitted by: Alexandre Lision (alision)**
There is an issue with the way text messaging is read/save.
Text messages are stored in a file named after the associated Conta...Issue generated from Tuleap's migration script.
**Originally submitted by: Alexandre Lision (alision)**
There is an issue with the way text messaging is read/save.
Text messages are stored in a file named after the associated ContactMethod's sha1.
When starting Ring, some ContactMethods are loaded WITHOUT an account.
It was preventing the user from sending a text message to some ContactMethods (see c20da91 in ring-lrc)
We now set an account if none is provided, and this cause the sha1 to be regenerated, and so the text messages are saved under a different sha1.
Problem is when you reopen Ring, the ContactMethod is still not associated with an account, so the sha1 is back to its first value. No file is located under this sha1, so im history appears empty.https://git.jami.net/savoirfairelinux/jami-project/-/issues/257What is the use of ring-daemon/src/dring/videomanager\_interface.h FrameBuffe...2018-05-25T13:33:55ZJami BotWhat is the use of ring-daemon/src/dring/videomanager\_interface.h FrameBuffer::storage ?Issue generated from Tuleap's migration script.
**Originally submitted by: Ciro Santilli (cirosantilli)**
https://github.com/savoirfairelinux/ring-daemon/blob/b1120dc145a911304389b50417aa5b0978e6fb92/src/dring/videomanager\_interface.h\...Issue generated from Tuleap's migration script.
**Originally submitted by: Ciro Santilli (cirosantilli)**
https://github.com/savoirfairelinux/ring-daemon/blob/b1120dc145a911304389b50417aa5b0978e6fb92/src/dring/videomanager\_interface.h\#L43
Does not seem used anywhere, Android and GNOME build fine without it.
Somewhat equivalent to the two other fields: `ptr {nullptr}; std::size\_t ptrSize`
There is a similar construct at: https://github.com/savoirfairelinux/ring-lrc/blob/cab4e0244b2804ee5da0a069016cff720eddc280/src/video/renderer.h\#L54https://git.jami.net/savoirfairelinux/jami-project/-/issues/181LRC - UserActionModel state is not properly updated for new outgoing call2018-05-25T12:53:26ZJami BotLRC - UserActionModel state is not properly updated for new outgoing callIssue generated from Tuleap's migration script.
**Originally submitted by: Stepan Salenikovich (ssalenik)**
<p>When creating a new call in a client and selecting that call immediately, the UserActionModel (UAM) does not properly update ...Issue generated from Tuleap's migration script.
**Originally submitted by: Stepan Salenikovich (ssalenik)**
<p>When creating a new call in a client and selecting that call immediately, the UserActionModel (UAM) does not properly update the states of the actions. It seems this is because doing CallModel::getIndex() immediately after creating a new call results in an invalid index, thus the selectionModel can't be updated and the UAM relies on the selectionModel.<br />
</p>https://git.jami.net/savoirfairelinux/jami-project/-/issues/306LRC: call changes state in an unexpected way2018-05-25T12:51:44ZJami BotLRC: call changes state in an unexpected wayIssue generated from Tuleap's migration script.
**Originally submitted by: Stepan Salenikovich (ssalenik)**
<p>I made a call to a machine with auto answer on, the call started (camera and audio), but dissapeared from the client complete...Issue generated from Tuleap's migration script.
**Originally submitted by: Stepan Salenikovich (ssalenik)**
<p>I made a call to a machine with auto answer on, the call started (camera and audio), but dissapeared from the client completely.</p>
<p>The client log only had this:<br />
Warning : call Call(0x9e2290) had an unexpected transition of state.( "Talking" )</p>
<p>Possibly changes in the daemon now allow state transitions which are not expected by lrc.</p>https://git.jami.net/savoirfairelinux/jami-project/-/issues/462Outgoing call - not displaying recipient video2018-05-23T01:30:47ZJami BotOutgoing call - not displaying recipient videoIssue generated from Tuleap's migration script.
**Originally submitted by: Loïc Siret (lsiret)**
On multidevice branch.
I have 2 clients GNOME and OSX.
When I start a call from OSX to GNOME, I expect to see the GNOME client video...Issue generated from Tuleap's migration script.
**Originally submitted by: Loïc Siret (lsiret)**
On multidevice branch.
I have 2 clients GNOME and OSX.
When I start a call from OSX to GNOME, I expect to see the GNOME client video on the OSX. But I see a black screen.
When I start a call from GNOME to OSX, I expect to see the OSX client video on GNOME. But I see a black screen.
Running a wireshark on Caller machine show udp packet from other client.
Daemon log of Caller machine attached.
Working nice on master
[error.log](/uploads/a9e99578a97dc623e7c96ebbde00f14c/error.log)https://git.jami.net/savoirfairelinux/jami-project/-/issues/424ring-daemon breaks: no member named 'raw\_chain' in 'pj\_ssl\_cert\_info'2018-05-22T00:46:43ZJami Botring-daemon breaks: no member named 'raw\_chain' in 'pj\_ssl\_cert\_info'Issue generated from Tuleap's migration script.
**Originally submitted by: Yuri (yurivict)**
Getting this in the FreeBSD port.
It also expects a missing symbol PJSIP\_TRANSPORT\_DTLS6.
You provide patches for pjsip. However, it isn'...Issue generated from Tuleap's migration script.
**Originally submitted by: Yuri (yurivict)**
Getting this in the FreeBSD port.
It also expects a missing symbol PJSIP\_TRANSPORT\_DTLS6.
You provide patches for pjsip. However, it isn't easy to build pjsip. This is done by its own port. Ring port can't just easily repeat what the other port is doing.
Please merge your patches into the pjsip upstream, so that there will be no need to keep any patches.https://git.jami.net/savoirfairelinux/jami-project/-/issues/387Easier bug reports2018-05-22T00:39:04ZJami BotEasier bug reportsIssue generated from Tuleap's migration script.
**Originally submitted by: Olafur Egilsson (olafure)**
Please consider moving bug reports to github, where all the cool kids are.Issue generated from Tuleap's migration script.
**Originally submitted by: Olafur Egilsson (olafure)**
Please consider moving bug reports to github, where all the cool kids are.https://git.jami.net/savoirfairelinux/jami-project/-/issues/377ring-daemon build fails: can't find PIX\_FMT\_PLANAR and PIX\_FMT\_RGB2018-05-22T00:38:40ZJami Botring-daemon build fails: can't find PIX\_FMT\_PLANAR and PIX\_FMT\_RGBIssue generated from Tuleap's migration script.
**Originally submitted by: Yuri (yurivict)**
Build of ring-daemon-2.2.0 on FreeBSD 11 fails:
video\_scaler.cpp:95:28: error: use of undeclared identifier 'PIX\_FMT\_PLANAR'
if (...Issue generated from Tuleap's migration script.
**Originally submitted by: Yuri (yurivict)**
Build of ring-daemon-2.2.0 on FreeBSD 11 fails:
video\_scaler.cpp:95:28: error: use of undeclared identifier 'PIX\_FMT\_PLANAR'
if (not (desc->flags & PIX\_FMT\_PLANAR)
\^
video\_scaler.cpp:96:26: error: use of undeclared identifier 'PIX\_FMT\_RGB'
or desc->flags & PIX\_FMT\_RGB)
\^
These values originate from libav. libav-11.8\_2 has them, but some other version is bundled with the latest ffmpeg-3.3.2 that doesn't have them.
You need to make sure libav version is picked up first.
On my system libav instals this header as
/usr/local/include/libav/libavutil/pixdesc.h
and ffmpeg installs it as /usr/local/include/libav/libavutil/pixdesc.hPhilippe GorleyPhilippe Gorleyhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/378daemon: integrate multidevice2018-05-22T00:38:40ZJami Botdaemon: integrate multideviceIssue generated from Tuleap's migration script.
**Originally submitted by: Andreas Traczyk (andreas.traczyk)**
<p>- &nbsp;Integrate multidevice and patch for UWP</p>Issue generated from Tuleap's migration script.
**Originally submitted by: Andreas Traczyk (andreas.traczyk)**
<p>- Integrate multidevice and patch for UWP</p>Andreas TraczykAndreas Traczyk