savoirfairelinux issueshttps://git.jami.net/groups/savoirfairelinux/-/issues2024-01-30T14:52:35Zhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/813Unable to acces the dial pad in a call using a Sip account2024-01-30T14:52:35Zdenn0nUnable to acces the dial pad in a call using a Sip accountHi sorry i don't know if should be like that but i think it is very necessary access the dial pad ones you are in the call maybe this is more a request then a bug I'm using the version 20200913-01 cr.ring installed from googleplay
if ...Hi sorry i don't know if should be like that but i think it is very necessary access the dial pad ones you are in the call maybe this is more a request then a bug I'm using the version 20200913-01 cr.ring installed from googleplay
if i dial from other devices to the android account in this case 6016 I'm unavailable to access the dial pad like i show next
![Screenshot_20201017-144045_Jami](/uploads/ae19ec1a23b34cbc2fab6bf3fdb62f85/Screenshot_20201017-144045_Jami.png)
and if i dial out to that othe devices or anyone else it can be accesses
![Screenshot_20201017-130232_Jami](/uploads/238ac9c9d748a9a56cb8a7502c60af97/Screenshot_20201017-130232_Jami.png)
it should be accessible at any time on the call right ?
plus in the pc version there is a transfer button, if it just could be accessible from the android version to , sorry tank you for all of your work !Iteration 24Amirhossein NaghshzanAmirhossein Naghshzanhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/688jami-daemon: add OCSP verification, store & trust2020-11-27T05:01:40ZVsevolod Ivanovjami-daemon: add OCSP verification, store & trust- :ballot_box_with_check: revoke jams device
https://review.jami.net/c/ring-daemon/+/12742
- :ballot_box_with_check: openssl OCSP server setup
https://github.com/binarytrails/notes/blob/master/software/ssl.md#setup-server
- :...- :ballot_box_with_check: revoke jams device
https://review.jami.net/c/ring-daemon/+/12742
- :ballot_box_with_check: openssl OCSP server setup
https://github.com/binarytrails/notes/blob/master/software/ssl.md#setup-server
- :ballot_box_with_check: proof-of-concept with opendht http library
https://github.com/binarytrails/various/blob/master/cpp/gnutls/ocsp.cpp
- :ballot_box_with_check: generating / sending OCSP request
- :ballot_box_with_check: receiving / processing OCSP request
- Jami-daemon integration: https://review.jami.net/c/ring-daemon/+/12792
- :ballot_box_with_check: Verify certificate with OCSP if present with a TLS session wrapper
- :ballot_box_with_check: Test/Debug/Validate JAMS for OCSP feature
- :ballot_box_with_check: Save OCSP responses into Certificate Store
```
ocsp/
└── <Certificate UID>
└── <OCSP Response Serial Number>
```
- :ballot_box_with_check: Load OCSP responses into Certificate Store
- :ballot_box_with_check: OpenDHT: Use OCSP requests store/trust implementation in Crypto
- :ballot_box_with_check: IM: Validate peers with OCSP responses prior to communication
https://github.com/savoirfairelinux/opendht/pull/464
- Implement OCSP periodic request sending/caching (IM are not automatic)
(ensures no revoked user can send messages even if the tls wrapper is not called as in sip calls)
Iteration 24Adrien BéraudVsevolod IvanovAdrien Béraudhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/847Account automatically disabled on connectivityChanged()2020-12-15T17:08:54ZSébastien BlinAccount automatically disabled on connectivityChanged()# Scenario
+ Open account settings
+ Cut the wifi
+ Enable 4g
# Expected result
+ The account must go online
# Current result
+ The account stay offline, like it was disabled, but the user didn't disabled the account# Scenario
+ Open account settings
+ Cut the wifi
+ Enable 4g
# Expected result
+ The account must go online
# Current result
+ The account stay offline, like it was disabled, but the user didn't disabled the accountIteration 23Amirhossein NaghshzanAmirhossein Naghshzanhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/352camera stays open after a call disconnects2020-11-23T22:14:20ZAdrien Béraudcamera stays open after a call disconnectsIteration 23Kateryna KostiukKateryna Kostiukhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/347Use keep alive mechanism to auto re-register sip account2020-11-19T16:31:25ZMing Rui ZhangUse keep alive mechanism to auto re-register sip accountIteration 23Ming Rui ZhangMing Rui Zhanghttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/346Use outbound proxy server address when it is specified2021-02-22T21:57:03ZMing Rui ZhangUse outbound proxy server address when it is specifiedCurrently, the proxy address in the SIP client does not have an impact,
when the user specifies that, it should use that address as the destination addressCurrently, the proxy address in the SIP client does not have an impact,
when the user specifies that, it should use that address as the destination addressIteration 23Ming Rui ZhangMing Rui Zhanghttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/339When the Jami android app uses a "DHT proxy" host-name different than the def...2020-11-25T15:59:10ZCarloWhen the Jami android app uses a "DHT proxy" host-name different than the default one it does not connect.Bug report
---------------
## Test environment
Android mobile setup:
- Ring version: 20190706-01
- Device model:
- Android version: 7.0
- What build you are using: Play Store
## Steps to reproduce
- Can you reproduce the...Bug report
---------------
## Test environment
Android mobile setup:
- Ring version: 20190706-01
- Device model:
- Android version: 7.0
- What build you are using: Play Store
## Steps to reproduce
- Can you reproduce the bug: yes at will.
The Jami app default/preset proxy server connection string is "dhtproxy.jami.net:[80-100]", with [80-100] being a range of possible service ports .
- Steps:
1. The current IP address of of dhtproxy.jami.net resolved with nslookup is 54.36.178.20 .
2. Enabling the use of "dhtproxy.jami.net:[80-100]" the jami account goes online correctly.
3. Making a traceroute --resolve-hostnames dhtproxy.jami.net, on a Linux host, I get at the end of the trace list a name alias of the same ip (54.36.178.20) "ns3102173.ip-54-36-178.eu". I can make the same using an app ("Ping & Net") directly on the mobile and I obtain the same results.
4. Using nslookup I verify that the two host names dhtproxy.jami.net and ns3102173.ip-54-36-178.eu resolve to the same ip : 54.36.178.20 . Also on the Android mobile I obtain the same results using the app "Ping & Net".
5. If on the android mobile I point Firefox to the url http://dhtproxy.jami.net or to http://ns3102173.ip-54-36-178.eu I get the same dhtproxy report JSON text: this means that the two host names can be used to open at least the same port 80 \`web page\`.
6. In the Jami application I substituted the dafault/preset host namedhtproxy.jami.net with it's alias ns3102173.ip-54-36-178.eu, I obtain the connection string "ns3102173.ip-54-36-178.eu:[80-100]"; doing so the Jami account no more connects. It seems quite that "the application" is not resolving the IP address for the new host name or it cuts out any other server name to use/resolve different than dhtproxy.jami.net.
7. Using directly the ip address in the connection string makes Jami to connect : "54.36.178.20:[80-100]" .
- Actual result: the Jami Android OS app does not connect to a "DHT proxy" string that has a literal hostname different than "dhtproxy.jami.net". It does connect if the "DHT proxy" is identified using its IP address .
- Expected result: the the Jami Android OS app should connect with any "DHT proxy" using in the connection string its DNS name to be resolved.
## Additional information
I encountered this bug verifying the connection to an OpenDHT (dhtnode) instance I setup; using this setup the Jami app connects to the "DHT proxy" from the Internet only when using the the IP host number in the connection string.
OpenDHT instance, compiled from source baseline version 1.10.0 (https://github.com/savoirfairelinux/opendht.git), running on Linux OS.Iteration 23Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/343multi device & file transfer.2020-11-10T20:48:59ZSébastien Blinmulti device & file transfer.# Scenario
+ A got 2 devices
+ B sends a file to A
# Expected
A should receives the file on both devices
# Current
One device is cut when the other one received the whole file# Scenario
+ A got 2 devices
+ B sends a file to A
# Expected
A should receives the file on both devices
# Current
One device is cut when the other one received the whole fileIteration 22Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/189rendezvous: client crashes when receiving a call2020-11-10T16:03:37ZGuillaume Hellerrendezvous: client crashes when receiving a callScenario:
* create a rendezvous on Windows Qt client
* call rendezvous from another account (not on the same device)
* Jami crashes
Note: crash does not occur if another account is selected
Version: 202010271743Scenario:
* create a rendezvous on Windows Qt client
* call rendezvous from another account (not on the same device)
* Jami crashes
Note: crash does not occur if another account is selected
Version: 202010271743Iteration 22Andreas TraczykMing Rui ZhangAndreas Traczykhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/341Still some ice nego failures2020-11-09T17:10:15ZSébastien BlinStill some ice nego failuresIteration 22Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/837Feature request add option to see entered password when backing up2020-10-29T21:05:50ZFeature request add option to see entered password when backing upMany of android power users and those who want an open source keyboard (that works without 10mb upload speed) use "Hacker's Keyboard" which can use qwerty which is very small for touch devices. I succeded in making a mistake twice, but w...Many of android power users and those who want an open source keyboard (that works without 10mb upload speed) use "Hacker's Keyboard" which can use qwerty which is very small for touch devices. I succeded in making a mistake twice, but wanted to review entered text when finishedIteration 22Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/338Add DRing API to control conference moderators2020-11-12T15:45:46ZAdrien BéraudAdd DRing API to control conference moderatorsIteration 22Pierre LespagnolPierre Lespagnolhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/155Remove the changelog2020-11-06T20:58:52ZAndreas TraczykRemove the changelogIteration 22Ming Rui ZhangMing Rui Zhanghttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/153Jami account register username in settings not functioning2020-11-05T15:30:53ZMing Rui ZhangJami account register username in settings not functioningIteration 22Ming Rui ZhangMing Rui Zhanghttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/829Account that sent the contact request doesn't see shown-names of those contac...2020-11-12T15:46:32ZAccount that sent the contact request doesn't see shown-names of those contacts even if messages were exchanged and even if contact initiator calls contactFrom one account i chatted with several people, with one that just accepted, with few that accepted and sent mesaages, with few that i exchanged mesages with. But only thing that brings them together is that i sent the contact request. S...From one account i chatted with several people, with one that just accepted, with few that accepted and sent mesaages, with few that i exchanged mesages with. But only thing that brings them together is that i sent the contact request. Several days passed and several messages were exchanged, maybe i didint try calls. I tested that again, and it turns out that
android to android contact initiator never gets to see contact shown-names (haven't checked after calls)
Update:
Shown-name updates only if account that recieved contact request calls the initialiserIteration 22Amirhossein NaghshzanAmirhossein Naghshzanhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/152Banned contact list model refresh issue2020-11-05T15:31:33ZMing Rui ZhangBanned contact list model refresh issueif banned contacts are more than 3, and user is trying to recover these middle ones,
list does not refreshif banned contacts are more than 3, and user is trying to recover these middle ones,
list does not refreshIteration 22Ming Rui ZhangMing Rui Zhanghttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/265video_mixer: do not use camera resolution as width/height2020-11-03T23:46:21ZSébastien Blinvideo_mixer: do not use camera resolution as width/height# Reproduce steps
1. Set camera to low resolution (160x120)
2. Create a conference with high res medias
# Expected result
The conference should get a correct video
# Actual result
The whole grid is 160x120, resulting in hideous videos# Reproduce steps
1. Set camera to low resolution (160x120)
2. Create a conference with high res medias
# Expected result
The conference should get a correct video
# Actual result
The whole grid is 160x120, resulting in hideous videosIteration 22Sébastien BlinPierre LespagnolSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/661Wrong Status in Contact List after Failed File Transmission2020-10-29T21:05:59ZWrong Status in Contact List after Failed File Transmission- Ring version: 2019-08-24-01
- Device model: Samsung Tablet S2
- Android version: 8.1 / LineageOS 15.1-20190228
- Jami-Version from F-droid
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. Have file...- Ring version: 2019-08-24-01
- Device model: Samsung Tablet S2
- Android version: 8.1 / LineageOS 15.1-20190228
- Jami-Version from F-droid
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. Have file transmission fail (e.g. error "... not reachable") after init).
2. Return to contact list from text chat view.
- Actual result: Contact list shows "file sent" status even though file was not sent.
- Expected result: Contact list shall show file transmission state correctly. Even after failures.Iteration 22Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/523Typing backspace in a message while in video call hides the message editing ...2020-11-03T16:33:05ZMaxim CournoyerTyping backspace in a message while in video call hides the message editing screen## Describe your environment
- Ring version: 20180712
- Device model: HTC U-Play
- Android version: 6.0
- What build you are using: F-droid
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. Initiate a...## Describe your environment
- Ring version: 20180712
- Device model: HTC U-Play
- Android version: 6.0
- What build you are using: F-droid
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. Initiate a video call.
2. Click the burger menu, select 'Text messaging'
3. Type some text, then backspace
- Actual result: Screens goes back to video (or crash, or Play Store release)
- Expected result: Text is deleted if any; message editing screen doesn't vanish.Iteration 22https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/273Sound & Conference: If one member is in hold, the sound is cut for the others...2020-08-12T14:53:30ZSébastien BlinSound & Conference: If one member is in hold, the sound is cut for the others participants# Reproduce Steps
Do a conference between 3 devices
A participant switch the conference in hold
# Expected result
The others should be able to speak together
# Current result
No sound for the other participant# Reproduce Steps
Do a conference between 3 devices
A participant switch the conference in hold
# Expected result
The others should be able to speak together
# Current result
No sound for the other participantItération 20Sébastien BlinSébastien Blin