jami-daemon issueshttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues2021-12-23T21:46:55Zhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/530Medias: Big lag when a lot of person leave the conference2021-12-23T21:46:55ZSébastien BlinMedias: Big lag when a lot of person leave the conference# Scenario
+ Be in a rdv with 10 people
+ Every body leave except 2 people
# Current result
+ Big lag on video
# Expected
+ No lag# Scenario
+ Be in a rdv with 10 people
+ Every body leave except 2 people
# Current result
+ Big lag on video
# Expected
+ No lagBackloghttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/487libnatpmp is not detected in configure step on linux2021-03-31T13:57:08ZMohamed Chibanilibnatpmp is not detected in configure step on linuxMaxim CournoyerMaxim Cournoyerhttps://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-daemon/-/issues/327remote management2023-05-05T19:06:30Zevkogan1remote managementClient1-GTK. Client2-Android.
Video call, turn off the microphone on Client1. Switch the camera to client2. The microphone is turned on on Client1, and without indication.
Turn off the camera on client2 and turn off/on the microphone ...Client1-GTK. Client2-Android.
Video call, turn off the microphone on Client1. Switch the camera to client2. The microphone is turned on on Client1, and without indication.
Turn off the camera on client2 and turn off/on the microphone on Client1. The camera on client2 turns on.
Is this covert espionage SOFTWARE? :)https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/256Stuck in Connecting: Some negotiations are blocked2020-07-16T18:48:37ZSébastien BlinStuck in Connecting: Some negotiations are blockedRelated to https://git.jami.net/savoirfairelinux/ring-daemon/issues/227
# Observation
The ice become complete too soon with no valid pairs:
@@@ Updating States
@@@ on_ice_complete
[1593797289.007|37053|manager.cpp :243 ] 13:28...Related to https://git.jami.net/savoirfairelinux/ring-daemon/issues/227
# Observation
The ice become complete too soon with no valid pairs:
@@@ Updating States
@@@ on_ice_complete
[1593797289.007|37053|manager.cpp :243 ] 13:28:09.007 sip:1018943881119817 ...ICE process complete, status=Success
[1593797289.007|37053|manager.cpp :243 ] 13:28:09.007 sip:1018943881119817 ...Valid list
(called a second time after that when negotiation is done
# Reproduce steps
still unknownIteration 19Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/243Stuck in Connecting: Closed sockets are not detected all the time2020-07-02T20:06:36ZSébastien BlinStuck in Connecting: Closed sockets are not detected all the timeRelated to https://git.jami.net/savoirfairelinux/ring-daemon/issues/227
# Reproduce Steps
1. device A calls device B
2. Call is working
3. device B cut its connectivity
4. device A calls device B
5. device A is blocked in "Connecting"
...Related to https://git.jami.net/savoirfairelinux/ring-daemon/issues/227
# Reproduce Steps
1. device A calls device B
2. Call is working
3. device B cut its connectivity
4. device A calls device B
5. device A is blocked in "Connecting"
# Expected result
Jami should detect that the socket is unusable and stop the call if fallback fails
+ icecb.on_destroy should be calledIteration 19Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/230Contacts are not displayed after account creation from the DHT2020-06-18T19:54:46ZCyrille BéraudContacts are not displayed after account creation from the DHTIteration 18Sébastien BlinAdrien BéraudKateryna KostiukMing Rui ZhangSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/201ffmpeg: add G711, G729 codecs (SIP)2021-12-29T21:26:12Zovariffmpeg: add G711, G729 codecs (SIP)Please add the following codecs to Jami:
* [G.711a](https://en.wikipedia.org/wiki/G.711)
* [G.711u](https://en.wikipedia.org/wiki/G.711)
* [G.729a](https://en.wikipedia.org/wiki/G.729)
What do you think?
Thank you
> MyNetFone uses th...Please add the following codecs to Jami:
* [G.711a](https://en.wikipedia.org/wiki/G.711)
* [G.711u](https://en.wikipedia.org/wiki/G.711)
* [G.729a](https://en.wikipedia.org/wiki/G.729)
What do you think?
Thank you
> MyNetFone uses the **G.711a** codec, it is the standard codec used in Australia and Europe. The **G.711u** codec is used within the US, and may be present in PBXs or UC platforms from US vendors. The **G.729a** codec is often used for conference calling services.<br>
> https://www.mynetfone.com.au/support/faq/question/477
> The patents for G.711, released in 1972, have expired, so it may be used without the need for a licence
> https://en.wikipedia.org/wiki/G.711#Licensing
> As of January 1, 2017, the patent terms of most licensed patents under the G.729 Consortium have expired, the remaining unexpired patents are usable on a royalty-free basis.<br>
> https://en.wikipedia.org/wiki/G.729.1
https://git.jami.net/savoirfairelinux/ring-daemon/issues/200Backloghttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/186SIP proxy field is not used correctly2020-12-13T23:57:25ZJami BotSIP proxy field is not used correctlyIssue generated from Tuleap's migration script.
**Originally submitted by: Raman Gupta (rocketraman)**
A detailed description of the bug. Use following fields for description field:
\* Environment:
Ring v1.0.0 on Linux Fedora 25 ...Issue generated from Tuleap's migration script.
**Originally submitted by: Raman Gupta (rocketraman)**
A detailed description of the bug. Use following fields for description field:
\* Environment:
Ring v1.0.0 on Linux Fedora 25
\* Reproduce steps:
Using the hostname and proxy fields to connect to a domain mydomain.com and proxy server proxy.versature.com. The configuration should set up Ring to connect to proxy.versature.com, passing the mydomain.com in the subsequent SIP request(s).
\* Expected result:
I would expect ring to connect successfully using this configuration. As a point of comparison, Zoiper will connect successfully.
\* Actual result:
The actual result is that Ring attempts to make a SIP connection to the hostname, ignoring the proxy field. The debug logs at SIPLOGLEVEL=4 are:
```
[1496261573.159|18869|sipaccount.cpp:698 ] doRegister mydomain.com
[1496261573.159|18869|sipvoiplink.cpp:1220 ] try to resolve 'mydomain.com' (port: 0)
16:12:53.159 resolver.c Transmitting 38 bytes to NS 0 (127.0.0.1:53): DNS SRV query for \_sip.\_udp.mydomain.com: Success
16:12:53.190 \_sip.\_udp.redo DNS SRV resolution failed for \_sip.\_udp.mydomain.com: DNS "Name Error" (PJLIB\_UTIL\_EDNS\_NXDOMAIN)
16:12:53.190 \_sip.\_udp.redo DNS SRV resolution failed for \_sip.\_udp.mydomain.com, trying resolving A/AAAA record for mydomain.com
16:12:53.190 resolver.c Transmitting 28 bytes to NS 0 (127.0.0.1:53): DNS A query for mydomain.com: Success
16:12:53.190 resolver.c Transmitting 28 bytes to NS 0 (127.0.0.1:53): DNS AAAA query for mydomain.com: Success
[1496261573.220|18869|sipaccount.cpp:815 ] Creating transport
16:12:53.220 udp0x18cc530 SIP UDP transport started, published address is 192.168.1.6:5062
[1496261573.220|18869|siptransport.cpp:357 ] Created UDP transport on default : 0.0.0.0:5062
[1496261573.221|18869|siptransport.cpp:82 ] SipTransport@0x190acc0 {tr=0x1919ec8 {rc=2}}
[1496261573.221|18869|sip\_utils.cpp:87 ] Adding route proxy.versature.com
[1496261605.223|18869|sipaccount.cpp:1033 ] SIP registration failed, status=408 (Request Timeout)
[1496261605.223|18869|sipaccount.cpp:2018 ] Scheduling re-registration retry in 53 seconds..
[1496261658.316|18869|sip\_utils.cpp:87 ] Adding route proxy.versature.com
[1496261690.321|18869|sipaccount.cpp:1033 ] SIP registration failed, status=408 (Request Timeout)
[1496261690.321|18869|sipaccount.cpp:2018 ] Scheduling re-registration retry in 302 seconds..
```
IF the system is configured with \_sip.\_udp SRV records on the domain provided in the hostname to point to the proxy, and the proxy field is left blank, then Ring successfully looks up the SRV record and connects to the proxy given there. Explicitly providing the proxy does not work as shown above.
The way I think it should work (and the way I think Zoiper works) is that you have a "domain/hostname" [1] setting and a "proxy" setting. The logic would be:
1) If proxy is set, Ring connects to the proxy and then passes username@domain in the SIP header.
2) If proxy is not set, then Ring looks for the proxy in the DNS SRV records for domain and if it exists, Ring connects to it and then passes username@domain to it.
3) Lastly, if the DNS SRV record does not exist, Ring attempts to connect to the A record of the domain/hostname setting, and again passes username@domain to it.
That way the auth information is completely configurable (username + domain) and the server that handles the request is completely configurable (proxy). The server to physically connect to is configurable either by DNS record on the domain, OR by explicit configuration in the proxy field.
[1] The "domain/hostname" config value would replace the current "hostname" config value.
The codepath to make the SIP connection as described above already exists -- its just that its impossible to configure the UI currently to trigger it. Given an SRV record of \_sip.\_udp.mydomain.com pointing to proxy.versature.com port 5060, Ring makes a connection to proxy.versature.com and passes all information with domain @mydomain.com. Here is a trace https://pastebin.com/raw/5z39MRu8.Ming Rui ZhangMing Rui Zhanghttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/180Missed call after one call2020-12-15T21:14:36ZMuhammad FattahiMissed call after one callUsing freepbx 15(using Asterisk 16)
After one call i must kill process jami then try to call.
Otherwise after one call any calls are missed call and nothing happened.
Other client like linphone work currectly.
OS: Ubuntu 18.04Using freepbx 15(using Asterisk 16)
After one call i must kill process jami then try to call.
Otherwise after one call any calls are missed call and nothing happened.
Other client like linphone work currectly.
OS: Ubuntu 18.04Ming Rui ZhangMing Rui Zhanghttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/164joinConferences() doesn't work2019-09-28T15:12:32ZSébastien BlinjoinConferences() doesn't workIteration 17 (Video conferences stabilization)Pierre LespagnolPierre Lespagnolhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/163Can't search amarok@ns.jami.net2019-09-28T15:10:48ZSébastien BlinCan't search amarok@ns.jami.netIteration 16 (POC prep)Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/160Seems like hardware acceleration is actived even if it's not and bug when dri...2021-02-04T13:56:04ZSébastien BlinSeems like hardware acceleration is actived even if it's not and bug when drivers are not herePierre LespagnolPierre Lespagnolhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/158Android: video frozen in conference, or black screen2019-11-21T15:01:34ZSébastien BlinAndroid: video frozen in conference, or black screenIteration 17 (Video conferences stabilization)Pierre LespagnolPierre Lespagnolhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/156[Split account]Backup account with password is broken2019-09-28T15:11:02ZSébastien Blin[Split account]Backup account with password is brokenIteration 16 (POC prep)Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/155Jams: Auth error should stop account creation2019-09-28T15:11:04ZSébastien BlinJams: Auth error should stop account creationAnd a deadlock occursAnd a deadlock occursIteration 16 (POC prep)Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/150[JAMS] Revoke device doesn't work2021-04-19T14:29:51ZSébastien Blin[JAMS] Revoke device doesn't workNew release 1Adrien BéraudAdrien Béraudhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/147[Split account]Import from device crash on multiple platforms2019-09-28T15:10:58ZSébastien Blin[Split account]Import from device crash on multiple platformsIteration 16 (POC prep)Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/141file transfer: cancel is broken2019-09-12T13:34:58ZSébastien Blinfile transfer: cancel is brokenIteration 15Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/140ios (lte) -> android, sometimes there is a 30 seconds delay during media nego...2019-08-29T14:44:21ZSébastien Blinios (lte) -> android, sometimes there is a 30 seconds delay during media negotiationMakes the call unusable.Makes the call unusable.Iteration 14Sébastien BlinSébastien Blin