jami-project issueshttps://git.jami.net/savoirfairelinux/jami-project/-/issues2018-05-22T00:37:35Zhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/356Documentation website yields 4042018-05-22T00:37:35ZJami BotDocumentation website yields 404Issue generated from Tuleap's migration script.
**Originally submitted by: Kevin Cole (ubuntourist)**
<p>The FAQ <a href="https://ring.cx/en/documentation/faq\#node-62">Ring just does not work. What should I do?</a> offers</p>
<blo...Issue generated from Tuleap's migration script.
**Originally submitted by: Kevin Cole (ubuntourist)**
<p>The FAQ <a href="https://ring.cx/en/documentation/faq\#node-62">Ring just does not work. What should I do?</a> offers</p>
<blockquote>
<p>(Linux only: use the <a href="https://ring.cx/en/documentation/advanced">advanced method</a> applying to your operating system.)</p>
</blockquote>
<p>which leads nowhere.</p>https://git.jami.net/savoirfairelinux/jami-project/-/issues/353daemon : two call id received for same call2018-05-22T00:37:22ZJami Botdaemon : two call id received for same callIssue generated from Tuleap's migration script.
**Originally submitted by: Hadrien De Sousa (hdesousa)**
\* Environment:
Test on Android version 69
\* Reproduce steps:
Make a call on Android and use daemon to get call id (getCa...Issue generated from Tuleap's migration script.
**Originally submitted by: Hadrien De Sousa (hdesousa)**
\* Environment:
Test on Android version 69
\* Reproduce steps:
Make a call on Android and use daemon to get call id (getCallList)
\* Expected result:
The daemon should return one call id bound to the contact ring id
\* Actual result:
The daemon returns two call ids for the same call ;
- one bound to the contact device id, e.g. <sips:1baa0e29e8d36e3dff05038dbe6ced5e57bc3dda@192.168.49.104:35422;transport=dtls>
- the other bound to the contact actual ring id
The id bound to the device id is unnecessary and should not be returned as its confusing for clients to receive two different call ids for the same call.https://git.jami.net/savoirfairelinux/jami-project/-/issues/346Patches for pjproject missing upstream submission2018-05-22T00:37:10ZJami BotPatches for pjproject missing upstream submissionIssue generated from Tuleap's migration script.
**Originally submitted by: Andrey Gursky (agur)**
Hi,
I'd like to ask you to open a ticket on pjproject's trac for every patch or add a comment like "doesn't need forwarding because ....Issue generated from Tuleap's migration script.
**Originally submitted by: Andrey Gursky (agur)**
Hi,
I'd like to ask you to open a ticket on pjproject's trac for every patch or add a comment like "doesn't need forwarding because ..." This will make it easier to manage them.
Ideally, you could add the following fields on the top of each patch (similar to Debian policy):
Description: why it is needed and what it does
Author:
Bug: https://tuleap.ring.cx/...
Forwarded: https:// (or not needed because ...)
Last-Update:
BTW, feel free to apply this not only for pjproject but all patches used by Ring.
Thanks,
Andrey
P.S. While it is, you know, possible to patch every open source project in use, it is not a common practice (for upstream). And you could imagine, what would happen if this would be widely practiced - distribution packaging would become useless, security audit become harder, more disk space / RAM consumption and so on.Guillaume RoguezGuillaume Roguezhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/325Migrated Ring account certificate have no CA flag2018-05-22T00:36:17ZJami BotMigrated Ring account certificate have no CA flagIssue generated from Tuleap's migration script.
**Originally submitted by: Adrien Béraud (adrienberaud)**
During migration of Ring accounts for multi-device, a new certificate was signed by a certificate without the CA flag.
This is b...Issue generated from Tuleap's migration script.
**Originally submitted by: Adrien Béraud (adrienberaud)**
During migration of Ring accounts for multi-device, a new certificate was signed by a certificate without the CA flag.
This is because the Ring account certificate didn't used to be a CA and was not regenerated during migration.Adrien BéraudAdrien Béraudhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/310Ring does not have a 'update' button2018-05-22T00:35:43ZJami BotRing does not have a 'update' buttonIssue generated from Tuleap's migration script.
**Originally submitted by: Svetlana Tkachenko (gryllida)**
We could have a 'nightly' and 'beta' and 'stable' (one day) release channels, and Ring could have an update button so that I don'...Issue generated from Tuleap's migration script.
**Originally submitted by: Svetlana Tkachenko (gryllida)**
We could have a 'nightly' and 'beta' and 'stable' (one day) release channels, and Ring could have an update button so that I don't have to manually download a new version.
Some details about how Firefox does updates:
https://wiki.mozilla.org/Releases/Update\_Channels
http://www.askvg.com/mozilla-updates-firefox-update-channels-nightly-aurora-beta-and-release/https://git.jami.net/savoirfairelinux/jami-project/-/issues/302daemon: crash during ip2ip call to localhost2018-05-22T00:35:22ZJami Botdaemon: crash during ip2ip call to localhostIssue generated from Tuleap's migration script.
**Originally submitted by: Stepan Salenikovich (ssalenik)**
<p>making an ip2ip call to localhost (127.0.0.1) the daemon systematically segfaults... the issue seems to be that rdata-&gt;msg...Issue generated from Tuleap's migration script.
**Originally submitted by: Stepan Salenikovich (ssalenik)**
<p>making an ip2ip call to localhost (127.0.0.1) the daemon systematically segfaults... the issue seems to be that rdata->msg\_info->msg = 0x0, but this check is not performed by the code... however, the function itself and the whole presence SIP module isn't in use anyways...</p>
<p> </p>
<pre>
[1479148412.111| 6697|manager.cpp:434 ] ----- Switch current call id to '7971077113848492381' -----
[1479148412.132| 6697|sipaccount.cpp:340 ] contact header: / ->
[1479148412.132| 6697|sipvoiplink.cpp:814 ] [call:7971077113848492381] INVITE@0x5555569237f8 state changed to 1 (CALLING): cause=0, tsx@0x55555692b4d8 status 0 (Default status message)
[1479148412.132| 6697|sipvoiplink.cpp:1117 ] [INVITE:0x5555569237f8] tsx\_role=0, tsx\_state=1, ev\_type=5, tsx\_state\_type=2
[1479148412.132| 6697|call.cpp:145 ] [call:7971077113848492381] state change 0/1, cnx 0/2, code 0
[1479148412.132| 6697|call.cpp:183 ] [call:7971077113848492381] emit client call state change CONNECTING, code 0
Thread 1 "dring" received signal SIGSEGV, Segmentation fault.
ring::PresSubServer::pres\_on\_rx\_subscribe\_request (rdata=0x5555568dbb88) at pres\_sub\_server.cpp:95
95 std::string request(str->ptr, str->slen);
(gdb) bt
\#0 ring::PresSubServer::pres\_on\_rx\_subscribe\_request (rdata=0x5555568dbb88) at pres\_sub\_server.cpp:95
\#1 0x0000555555841ac6 in pjsip\_endpt\_process\_rx\_data ()
\#2 0x0000555555841e22 in endpt\_on\_rx\_msg ()
\#3 0x000055555584bc96 in pjsip\_tpmgr\_receive\_packet ()
\#4 0x000055555584cc6f in udp\_on\_read\_complete ()
\#5 0x000055555589c624 in ioqueue\_dispatch\_read\_event ()
\#6 0x000055555589ea1c in pj\_ioqueue\_poll ()
\#7 0x0000555555841774 in pjsip\_endpt\_handle\_events2 ()
\#8 0x0000555555841835 in pjsip\_endpt\_handle\_events ()
\#9 0x0000555555787255 in ring::SIPVoIPLink::handleEvents (this=0x5555565a7a00) at sipvoiplink.cpp:689
\#10 0x000055555571a721 in std::function::operator()() const (this=0x5555565725a8) at /usr/include/c++/6/functional:2136
\#11 ring::Manager::pollEvents (this=0x5555563d5980 ) at manager.cpp:1454
\#12 0x00007ffff7bbdae3 in DBus::DefaultMainLoop::dispatch() () from /usr/lib/x86\_64-linux-gnu/libdbus-c++-1.so.0
\#13 0x00007ffff7bbe78c in DBus::BusDispatcher::enter() () from /usr/lib/x86\_64-linux-gnu/libdbus-c++-1.so.0
\#14 0x000055555563492f in DBusClient::event\_loop (this=) at dbusclient.cpp:237
\#15 0x000055555562d4ed in main (argc=2, argv=0x7fffffffddc8) at main.cpp:235
(gdb) bt full
\#0 ring::PresSubServer::pres\_on\_rx\_subscribe\_request (rdata=0x5555568dbb88) at pres\_sub\_server.cpp:95
method = 0x6e6f74676e697228
str = 0x6e6f74676e697230
request = "\\000\_=VUU\\000\\000\\306\\032\\204UUU\\000\\000\\244\\311\\377\\377\\377\\177\\000\\000\\260\\311\\377\\377\\377\\177\\000\\000\\210\\273\\215VUU\\000\\000؎ZVUU\\000\\000@\\311\\377\\377\\000\\000\\000\\000\\000\\000\\000\\000UU\\000\\000`3;VUU\\000\\000\\200\\316\\215VUU\\000\\000p\\311\\377\\377\\377\\177\\000\\000\\313\\030\\204UUU\\000\\000p\\311\\377\\377\\377\\177\\000\\000\\000\\214oFΛrO`\\312\\377\\377\\377\\177\\000\\000\\"\\036\\204UUU\\000\\000 \\312\\377\\377\\377\\177\\000\\000\\210\\273\\215VUU\\000\\000\\320\\311\\377\\377\\000\\000\\000\\000؎ZVUU\\000\\000\\300\\311\\377\\377\\000\\000\\000\\000\\200\\316\\215VUU", '\\000' , "\\001\\000\\000\\000"...
\#1 0x0000555555841ac6 in pjsip\_endpt\_process\_rx\_data ()
No symbol table info available.
\#2 0x0000555555841e22 in endpt\_on\_rx\_msg ()
No symbol table info available.
\#3 0x000055555584bc96 in pjsip\_tpmgr\_receive\_packet ()
No symbol table info available.
\#4 0x000055555584cc6f in udp\_on\_read\_complete ()
No symbol table info available.
\#5 0x000055555589c624 in ioqueue\_dispatch\_read\_event ()
No symbol table info available.
\#6 0x000055555589ea1c in pj\_ioqueue\_poll ()
No symbol table info available.
\#7 0x0000555555841774 in pjsip\_endpt\_handle\_events2 ()
No symbol table info available.
\#8 0x0000555555841835 in pjsip\_endpt\_handle\_events ()
No symbol table info available.
\#9 0x0000555555787255 in ring::SIPVoIPLink::handleEvents (this=0x5555565a7a00) at sipvoiplink.cpp:689
timeout = {sec = 0, msec = 0}
ret =
\#10 0x000055555571a721 in std::function::operator()() const (this=0x5555565725a8) at /usr/include/c++/6/functional:2136
No locals.
\#11 ring::Manager::pollEvents (this=0x5555563d5980 ) at manager.cpp:1454
iter = {first = 93825009351168, second = {> = {}, = {static \_M\_max\_size = 16, static \_M\_max\_align = 8, \_M\_functor = {
\_M\_unused = {\_M\_object = , \_M\_const\_object = , \_M\_function\_pointer = ,
\_M\_member\_pointer = (void (std::\_Undefined\_class::\*)(std::\_Undefined\_class \* const)) 0x5555565a7a00, this adjustment 93825009356336}, \_M\_pod\_data = "\\000zZVUU\\000\\000\\060\\216ZVUU\\000"},
\_M\_manager = >::\_M\_manager(std::\_Any\_data &, const std::\_Any\_data &, std::\_Manager\_operation)>},
\_M\_invoker = >::\_M\_invoke(const std::\_Any\_data &)>}}
\#12 0x00007ffff7bbdae3 in DBus::DefaultMainLoop::dispatch() () from /usr/lib/x86\_64-linux-gnu/libdbus-c++-1.so.0
No symbol table info available.
\#13 0x00007ffff7bbe78c in DBus::BusDispatcher::enter() () from /usr/lib/x86\_64-linux-gnu/libdbus-c++-1.so.0
No symbol table info available.
\#14 0x000055555563492f in DBusClient::event\_loop (this=) at dbusclient.cpp:237
No locals.
\#15 0x000055555562d4ed in main (argc=2, argv=0x7fffffffddc8) at main.cpp:235
programName = "/home/ssalenikovich/projects/ring-daemon/bin/dring"
persistent = true
</pre>
<p> </p>https://git.jami.net/savoirfairelinux/jami-project/-/issues/291Name lookup can take too long with a bad server2018-05-22T00:34:58ZJami BotName lookup can take too long with a bad serverIssue generated from Tuleap's migration script.
**Originally submitted by: Stepan Salenikovich (ssalenik)**
<p>If a bad server is specified, the name lookup takes too long / never ends.</p>
<p>eg: I made a lookup with a non existin...Issue generated from Tuleap's migration script.
**Originally submitted by: Stepan Salenikovich (ssalenik)**
<p>If a bad server is specified, the name lookup takes too long / never ends.</p>
<p>eg: I made a lookup with a non existing server:</p>
<p>[1478803235.690|25072|namedirectory.cpp:181 ] Name lookup for ssalenikovich1: http://bleepbloop/name/ssalenikovich1</p>
<p>And never seemed to get a response from the daemon after several minutes of waiting.</p>
<p>The problem is twofold:</p>
<p>1. the daemon should timeout (sooner)</p>
<p>2. the UI should probably have a way of cancelling the lookup if it is taking too long.</p>https://git.jami.net/savoirfairelinux/jami-project/-/issues/277ui: show username instead of RingID everywhere2018-05-22T00:34:39ZJami Botui: show username instead of RingID everywhereIssue generated from Tuleap's migration script.
**Originally submitted by: Adrien Béraud (adrienberaud)**
On every client:
\* If there is an account registered username, it should be shown/shared instead of the RingID on front page/sh...Issue generated from Tuleap's migration script.
**Originally submitted by: Adrien Béraud (adrienberaud)**
On every client:
\* If there is an account registered username, it should be shown/shared instead of the RingID on front page/share link etc. (except QR code).
\* A username lookup should always be performed on every RingID in the conversation history,
if a name is found it should be shown instead of the RingID.
\* In a call/conversation, the contact registered name should be shown instead of the RingID. An advanced menu option (not shown by default) should still allow to copy the RingID.https://git.jami.net/savoirfairelinux/jami-project/-/issues/265Incoming text messages are received without ringID2018-05-22T00:34:18ZJami BotIncoming text messages are received without ringIDIssue generated from Tuleap's migration script.
**Originally submitted by: Aline Bonnet (abonnet)**
When you receive a text message during a hold call, the "from" variable is empty.
In merge function, peerNumber variable is not retri...Issue generated from Tuleap's migration script.
**Originally submitted by: Aline Bonnet (abonnet)**
When you receive a text message during a hold call, the "from" variable is empty.
In merge function, peerNumber variable is not retrieved. Before this call, peerNumber variable contains the device ID and not the ring ID.
On Android, vcard is not saved during a outgoing call because you are not the ringID.Adrien BéraudAdrien Béraudhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/260daemon: putting in a "random" string for the nameserver makes the account inv...2018-05-22T00:34:11ZJami Botdaemon: putting in a "random" string for the nameserver makes the account invalidIssue generated from Tuleap's migration script.
**Originally submitted by: Stepan Salenikovich (ssalenik)**
<p>using eg: &quot;asdfadfafd&quot; as the name server url invalidates the ring account... the ring account should work whether ...Issue generated from Tuleap's migration script.
**Originally submitted by: Stepan Salenikovich (ssalenik)**
<p>using eg: "asdfadfafd" as the name server url invalidates the ring account... the ring account should work whether the name server is valid or not</p>https://git.jami.net/savoirfairelinux/jami-project/-/issues/255Account backup and restore do not work2018-05-22T00:34:03ZJami BotAccount backup and restore do not workIssue generated from Tuleap's migration script.
**Originally submitted by: Alexandre Lision (alision)**
The ability to export a local copy of an account and restore it later has been broken by the multidevice implementation.
Here's...Issue generated from Tuleap's migration script.
**Originally submitted by: Alexandre Lision (alision)**
The ability to export a local copy of an account and restore it later has been broken by the multidevice implementation.
Here's what happen when we try to restore a multidevice Ring account:
\u001b[0mAdding account d696e12f9f520144
\u001b[0m\u001b[22;36m[1477410239.282|0x101a173c0|account.cpp:409 ] \u001b[0m\u001b[22;31mCouldn't find key "Account.archivePassword"
\u001b[0m\u001b[22;36m[1477410239.282|0x101a173c0|account.cpp:409 ] \u001b[0m\u001b[22;31mCouldn't find key "Account.archivePIN"
\u001b[0m\u001b[22;36m[1477410239.282|0x101a173c0|account.cpp:409 ] \u001b[0m\u001b[22;31mCouldn't find key "Account.archivePath"
\u001b[0m\u001b[22;36m[1477410239.282|0x101a173c0|ringaccount.cpp:1066 ] \u001b[0m\u001b[01;33mRingAccount::loadAccount
\u001b[0m\u001b[22;36m[1477410239.282|0x101a173c0|ringaccount.cpp:667 ] \u001b[0m\u001b[01;33mloadIdentity()
\u001b[0m\u001b[22;36m[1477410239.282|0x101a173c0|ringaccount.cpp:689 ] \u001b[0m\u001b[22;31mError loading identity: Can't read file:
\u001b[0m\u001b[22;36m[1477410239.282|0x101a173c0|ringaccount.cpp:1080 ] \u001b[0m\u001b[01;33mPassword needed to create archive
\u001bhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/250default ringtone is too big2018-05-22T00:33:57ZJami Botdefault ringtone is too bigIssue generated from Tuleap's migration script.
**Originally submitted by: Alexandre Lision (alision)**
The new default.wav ringtone weights 2.4Mb. It is way too big for a ringtone.
Previous one we used was konga.ul, 28Kb.
The H...Issue generated from Tuleap's migration script.
**Originally submitted by: Alexandre Lision (alision)**
The new default.wav ringtone weights 2.4Mb. It is way too big for a ringtone.
Previous one we used was konga.ul, 28Kb.
The Hangout ringtone weights 64kb.
Having such a large file causes performance issues (buffering), especially on Android.https://git.jami.net/savoirfairelinux/jami-project/-/issues/243enableAccel setting does not work2018-05-22T00:33:47ZJami BotenableAccel setting does not workIssue generated from Tuleap's migration script.
**Originally submitted by: Philippe Gorley (pgorley)**
Changing the enableAccel setting in dring.yml to 0 does not deactivate hardware accelerationIssue generated from Tuleap's migration script.
**Originally submitted by: Philippe Gorley (pgorley)**
Changing the enableAccel setting in dring.yml to 0 does not deactivate hardware accelerationPhilippe GorleyPhilippe Gorleyhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/237multidevice: client not acknowledged when ICE nego timeout2018-05-22T00:33:37ZJami Botmultidevice: client not acknowledged when ICE nego timeoutIssue generated from Tuleap's migration script.
**Originally submitted by: Guillaume Roguez (guillaume)**
<p>The caller's client continue to display &quot;searching for&quot; status after the daemon has deleted a terminated call due to ...Issue generated from Tuleap's migration script.
**Originally submitted by: Guillaume Roguez (guillaume)**
<p>The caller's client continue to display "searching for" status after the daemon has deleted a terminated call due to ICE timeout (negotiation timeout of 60s).</p>
<p><strong>Steps to reproduce the bug</strong></p>
<ul>
<li>call a valid Ring device but do not answer on it</li>
<li>wait 1 minute</li>
<li>the caller log shows the ICE negotiation timeout and the "subcall" destruction the client continue in "searching for" state</li>
</ul>
<p><strong>Result (vs. expected result)</strong></p>
<ul>
<li>the client loops in "searching for" state indefinetly</li>
</ul>Adrien BéraudAdrien Béraudhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/235It is allowed to import the same account multiple times2018-05-22T00:33:35ZJami BotIt is allowed to import the same account multiple timesIssue generated from Tuleap's migration script.
**Originally submitted by: Thibault Wittemberg (twittemberg)**
It is possible to add the same "multidevice" account multiple times on the same deviceIssue generated from Tuleap's migration script.
**Originally submitted by: Thibault Wittemberg (twittemberg)**
It is possible to add the same "multidevice" account multiple times on the same devicehttps://git.jami.net/savoirfairelinux/jami-project/-/issues/197daemon: message fails to send but status is IDLE2018-05-22T00:32:38ZJami Botdaemon: message fails to send but status is IDLEIssue generated from Tuleap's migration script.
**Originally submitted by: Stepan Salenikovich (ssalenik)**
<p>If you create a new Ring account with a bad (or non working) bootstrap, the account never connects to the dht. If you then tr...Issue generated from Tuleap's migration script.
**Originally submitted by: Stepan Salenikovich (ssalenik)**
<p>If you create a new Ring account with a bad (or non working) bootstrap, the account never connects to the dht. If you then try to send a text message, it will of course fail, however, the status of the messges seems to stay on IDLE, see log:</p>
<p>[1473257868.497|13729|message\_engine.cpp:239 ] Could not save messages to /home/ssalenikovich/.cache/ring/92994cf5413c8fb7/messages: basic\_ios::clear: iostream error<br />
[1473257868.516|13729|sipaccount.cpp:2067 ] Unable to create request: Invalid Request URI (PJSIP\_EINVALIDREQURI)<br />
[1473257868.516|13729|message\_engine.cpp:137 ] Message 16160251769922510613: failure<br />
[1473257868.516|13729|message\_engine.cpp:158 ] Status IDLE for message 16160251769922510613<br />
[1473257882.640|13729|message\_engine.cpp:239 ] Could not save messages to /home/ssalenikovich/.cache/ring/92994cf5413c8fb7/messages: basic\_ios::clear: iostream error<br />
[1473257882.651|13729|sipaccount.cpp:2067 ] Unable to create request: Invalid Request URI (PJSIP\_EINVALIDREQURI)<br />
[1473257882.651|13729|message\_engine.cpp:137 ] Message 17238945268893409279: failure<br />
[1473257882.651|13729|message\_engine.cpp:158 ] Status IDLE for message 17238945268893409279</p>
<p> </p>
<p>The status should be FAILURE</p>https://git.jami.net/savoirfairelinux/jami-project/-/issues/190Incorrect finishing call2018-05-22T00:32:24ZJami BotIncorrect finishing callIssue generated from Tuleap's migration script.
**Originally submitted by: Alexandr Sergheev (asergheev)**
<p>Some times when call finished by first user , second could receive &quot;Failure&quot; status</p>
<p>Steps:</p>
<p>I...Issue generated from Tuleap's migration script.
**Originally submitted by: Alexandr Sergheev (asergheev)**
<p>Some times when call finished by first user , second could receive "Failure" status</p>
<p>Steps:</p>
<p>Initiate call -> press "finish Call" button >>> as result on other end call status became "Failure"</p>
<p> </p>Guillaume RoguezGuillaume Roguezhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/185daemon: keys and cert are not deleted on account removal2018-05-22T00:32:20ZJami Botdaemon: keys and cert are not deleted on account removalIssue generated from Tuleap's migration script.
**Originally submitted by: Stepan Salenikovich (ssalenik)**
<p>When an account is deleted in the daemon, the account's keys and cert and the dir containing them should also be deleted in \...Issue generated from Tuleap's migration script.
**Originally submitted by: Stepan Salenikovich (ssalenik)**
<p>When an account is deleted in the daemon, the account's keys and cert and the dir containing them should also be deleted in \~/.local/share/ring<br />
<br />
The user likely expects that this info is deleted... otherwise the account can be recreated..</p>Guillaume RoguezGuillaume Roguezhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/174daemon: fix coverity.com minor issues2018-05-22T00:23:27ZJami Botdaemon: fix coverity.com minor issuesIssue generated from Tuleap's migration script.
**Originally submitted by: Guillaume Roguez (guillaume)**
Our coverity scan has found many minor issues, mostly fixable by very few changes.
https://scan.coverity.com/projects/ring?ta...Issue generated from Tuleap's migration script.
**Originally submitted by: Guillaume Roguez (guillaume)**
Our coverity scan has found many minor issues, mostly fixable by very few changes.
https://scan.coverity.com/projects/ring?tab=overview
This tickets follows them.Guillaume RoguezGuillaume Roguezhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/173Missing ring.cx script in debian packages2018-05-22T00:22:43ZJami BotMissing ring.cx script in debian packagesIssue generated from Tuleap's migration script.
**Originally submitted by: Alexandre Viau (aviau)**
Missing ring.cx script in debian packagesIssue generated from Tuleap's migration script.
**Originally submitted by: Alexandre Viau (aviau)**
Missing ring.cx script in debian packages