savoirfairelinux issueshttps://git.jami.net/groups/savoirfairelinux/-/issues2021-03-15T14:53:10Zhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/476No SIP registration due to bad network detection2021-03-15T14:53:10ZEnrico ScholzNo SIP registration due to bad network detectionjami 20210308.1.7cc33bd does not do any SIP registration here. E.g. with tcpdump I see DNS queries (and responses) for the SIP server but no further communication to the SIP server itself.
Running the daemon with `--debug` shows
```
*...jami 20210308.1.7cc33bd does not do any SIP registration here. E.g. with tcpdump I see DNS queries (and responses) for the SIP server but no further communication to the SIP server itself.
Running the daemon with `--debug` shows
```
** (jami-gnome:822803): DEBUG: 14:24:26.718: NetworkManager client initialized, version: (null)
daemon running: no
nnetworking enabled: no
```
<details>
<summary>Full Log</summary>
<pre>
$ ring.cx --debug
(jami-gnome:822803): GLib-DEBUG: 14:24:25.931: setenv()/putenv() are not thread-safe and should not be used after threads are created
** (jami-gnome:822803): DEBUG: 14:24:25.931: debug enabled
** Message: 14:24:25.933: Jami GNOME client version: development
** Message: 14:24:25.933: git ref: unknown
** (jami-gnome:822803): DEBUG: 14:24:25.933: enabling autostart
** (jami-gnome:822803): DEBUG: 14:24:25.933: checking /usr/share/jami-gnome/jami-gnome.desktop
(jami-gnome:822803): dconf-DEBUG: 14:24:25.933: watch_established: "/net/jami/JamiGnome/" (establishing: 1)
** (jami-gnome:822803): DEBUG: 14:24:25.934: '/home/ensc/.config/autostart/jami-gnome.desktop' is already a symlink to '/usr/share/jami-gnome/jami-gnome.desktop'
(jami-gnome:822803): dbind-WARNING **: 14:24:25.945: AT-SPI: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.NameHasNoOwner: Could not activate remote peer.
** (jami-gnome:822803): DEBUG: 14:24:26.098: installed translations for de
** (jami-gnome:822803): DEBUG: 14:24:26.098: installed translations for de_DE
(jami-gnome:822803): GLib-GIO-DEBUG: 14:24:26.106: _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ‘gio-vfs’
(jami-gnome:822803): GLib-DEBUG: 14:24:26.178: unsetenv() is not thread-safe and should not be used after threads are created
(jami-gnome:822803): Gtk-DEBUG: 14:24:26.178: Connecting to session manager
(jami-gnome:822803): Gtk-DEBUG: 14:24:26.178: Failed to get the GNOME session proxy: The name org.gnome.SessionManager is not owned
Can't open file: "/home/ensc/.local/share/jami/606bab6fe62f6e4c/profile.vcf"
** (jami-gnome:822803): DEBUG: 14:24:26.254: notify server name: naughty, vendor: awesome, version: 3.5, spec: 1.0
(jami-gnome:822803): Gtk-WARNING **: 14:24:26.255: Child name 'calls' not found in GtkStack
(jami-gnome:822803): Gtk-CRITICAL **: 14:24:26.256: gtk_container_remove: assertion 'GTK_IS_WIDGET (widget)' failed
(jami-gnome:822803): Gtk-CRITICAL **: 14:24:26.256: gtk_container_add: assertion 'GTK_IS_WIDGET (widget)' failed
(jami-gnome:822803): Gtk-CRITICAL **: 14:24:26.256: gtk_widget_show: assertion 'GTK_IS_WIDGET (widget)' failed
(jami-gnome:822803): Gtk-CRITICAL **: 14:24:26.256: gtk_container_remove: assertion 'GTK_IS_WIDGET (widget)' failed
(jami-gnome:822803): Gtk-CRITICAL **: 14:24:26.257: gtk_container_add: assertion 'GTK_IS_WIDGET (widget)' failed
(jami-gnome:822803): Gtk-CRITICAL **: 14:24:26.257: gtk_widget_show: assertion 'GTK_IS_WIDGET (widget)' failed
(jami-gnome:822803): dconf-DEBUG: 14:24:26.257: watch_fast: "/net/jami/JamiGnome/" (establishing: 0, active: 1)
invoking IsSupported() failed for remote volume monitor with dbus name org.gtk.vfs.GoaVolumeMonitor:: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not activate remote peer. (g-dbus-error-quark, 3)
(jami-gnome:822803): dconf-DEBUG: 14:24:26.413: watch_fast: "/org/gtk/settings/file-chooser/" (establishing: 0, active: 0)
(jami-gnome:822803): dconf-DEBUG: 14:24:26.414: watch_established: "/org/gtk/settings/file-chooser/" (establishing: 1)
(jami-gnome:822803): dconf-DEBUG: 14:24:26.565: watch_fast: "/net/jami/JamiGnome/" (establishing: 0, active: 2)
(jami-gnome:822803): Gtk-CRITICAL **: 14:24:26.585: gtk_scrolled_window_add: assertion 'child_widget == NULL' failed
(jami-gnome:822803): dconf-DEBUG: 14:24:26.623: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.623: change_notify: /net/jami/JamiGnome/show-main-window
(process:822825): GLib-GIO-DEBUG: 14:24:26.661: Failed to initialize portal (GNetworkMonitorPortal) for gio-network-monitor: Not using portals
(process:822825): GLib-GIO-DEBUG: 14:24:26.663: Failed to initialize networkmanager (GNetworkMonitorNM) for gio-network-monitor: NetworkManager not running
(process:822825): GLib-GIO-DEBUG: 14:24:26.663: _g_io_module_get_default: Found default implementation netlink (GNetworkMonitorNetlink) for ?gio-network-monitor?
(WebKitWebProcess:822824): dbind-WARNING **: 14:24:26.672: AT-SPI: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.NameHasNoOwner: Could not activate remote peer.
(jami-gnome:822803): dconf-DEBUG: 14:24:26.701: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.702: change_notify: /net/jami/JamiGnome/window-width
(jami-gnome:822803): dconf-DEBUG: 14:24:26.702: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.702: change_notify: /net/jami/JamiGnome/window-height
(jami-gnome:822803): dconf-DEBUG: 14:24:26.708: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.708: change_notify: /net/jami/JamiGnome/window-width
(jami-gnome:822803): dconf-DEBUG: 14:24:26.708: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.708: change_notify: /net/jami/JamiGnome/window-height
(jami-gnome:822803): dconf-DEBUG: 14:24:26.718: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.718: change_notify: /net/jami/JamiGnome/window-maximized
** (jami-gnome:822803): DEBUG: 14:24:26.718: NetworkManager client initialized, version: (null)
daemon running: no
nnetworking enabled: no
** (jami-gnome:822803): WARNING **: 14:24:26.718: no primary network connection detected, check network settings
(process:822825): GLib-GIO-DEBUG: 14:24:26.740: _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ?gio-vfs?
(jami-gnome:822803): dconf-DEBUG: 14:24:26.756: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.756: change_notify: /net/jami/JamiGnome/window-width
(jami-gnome:822803): dconf-DEBUG: 14:24:26.756: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.756: change_notify: /net/jami/JamiGnome/window-height
(jami-gnome:822803): dconf-DEBUG: 14:24:26.776: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.776: change_notify: /net/jami/JamiGnome/window-width
(jami-gnome:822803): dconf-DEBUG: 14:24:26.776: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.776: change_notify: /net/jami/JamiGnome/window-height
(jami-gnome:822803): dconf-DEBUG: 14:24:26.792: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.792: change_notify: /net/jami/JamiGnome/window-width
(jami-gnome:822803): dconf-DEBUG: 14:24:26.792: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.792: change_notify: /net/jami/JamiGnome/window-height
(WebKitWebProcess:822824): GLib-GIO-DEBUG: 14:24:26.796: _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ‘gio-vfs’
(jami-gnome:822803): dconf-DEBUG: 14:24:26.810: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.810: change_notify: /net/jami/JamiGnome/window-width
(jami-gnome:822803): dconf-DEBUG: 14:24:26.810: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.810: change_notify: /net/jami/JamiGnome/window-height
(jami-gnome:822803): dconf-DEBUG: 14:24:26.828: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.828: change_notify: /net/jami/JamiGnome/window-width
(jami-gnome:822803): dconf-DEBUG: 14:24:26.828: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.828: change_notify: /net/jami/JamiGnome/window-height
(jami-gnome:822803): dconf-DEBUG: 14:24:26.847: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.847: change_notify: /net/jami/JamiGnome/window-width
(jami-gnome:822803): dconf-DEBUG: 14:24:26.848: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.848: change_notify: /net/jami/JamiGnome/window-height
(jami-gnome:822803): dconf-DEBUG: 14:24:26.865: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.865: change_notify: /net/jami/JamiGnome/window-width
(jami-gnome:822803): dconf-DEBUG: 14:24:26.865: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.865: change_notify: /net/jami/JamiGnome/window-height
(jami-gnome:822803): Gdk-CRITICAL **: 14:24:26.880: gdk_window_thaw_toplevel_updates: assertion 'window->update_and_descendants_freeze_count > 0' failed
(jami-gnome:822803): dconf-DEBUG: 14:24:26.882: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.882: change_notify: /net/jami/JamiGnome/window-width
(jami-gnome:822803): dconf-DEBUG: 14:24:26.882: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.882: change_notify: /net/jami/JamiGnome/window-height
(jami-gnome:822803): dconf-DEBUG: 14:24:26.899: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.899: change_notify: /net/jami/JamiGnome/window-width
(jami-gnome:822803): dconf-DEBUG: 14:24:26.899: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.899: change_notify: /net/jami/JamiGnome/window-height
(jami-gnome:822803): dconf-DEBUG: 14:24:26.917: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.917: change_notify: /net/jami/JamiGnome/window-width
(jami-gnome:822803): dconf-DEBUG: 14:24:26.917: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.917: change_notify: /net/jami/JamiGnome/window-height
</pre>
</details>
I am not using Gnome and network is managed manually (no NetworkManager)https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/477[To confirm] multidevice issue2021-03-15T16:32:53ZSébastien Blin[To confirm] multidevice issueAlice (2 devices A1, A0), Bob, Carla
+ A0 et Bob in call
+ Carla sends a message to Alice (or call), A1 will receives but not A0Alice (2 devices A1, A0), Bob, Carla
+ A0 et Bob in call
+ Carla sends a message to Alice (or call), A1 will receives but not A0Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/906Android - Video out not showing2021-05-28T21:08:30ZXesús GonzálezAndroid - Video out not showing- Jami version: Together - 20210226-01
- Device model: Sony Xperia XZ1 (G8341)
- Android version: 9
- What build you are using: Play Store
- Can you reproduce the bug: at will
- Steps:
1. Starting video call between Android ...- Jami version: Together - 20210226-01
- Device model: Sony Xperia XZ1 (G8341)
- Android version: 9
- What build you are using: Play Store
- Can you reproduce the bug: at will
- Steps:
1. Starting video call between Android and Linux client.
2. Both devices successfully connected.
- Actual result: **Android video out NOT showing** (neither on Android screen nor on computer screen).
- Expected result: Android video out showing.https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/662Support DTMF2021-12-29T17:07:16ZSébastien BlinSupport DTMFTo be definedTo be definedBackloghttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1257Outgoing SIP calls drop after 32s2021-06-25T19:17:17ZDavid LecompteOutgoing SIP calls drop after 32sI am using an OVH SIP account. Outgoing calls to a landline or to another OVH SIP account drop after 32s, this is 100% reproducible.
I am using Trisquel 9 on a desktop PC and added Jami repository, the version of jami is 2021-03-08 21:4...I am using an OVH SIP account. Outgoing calls to a landline or to another OVH SIP account drop after 32s, this is 100% reproducible.
I am using Trisquel 9 on a desktop PC and added Jami repository, the version of jami is 2021-03-08 21:43:25 UTC . The network connection is via ethernet, my ISP is SFR in Paris France, fiber connection.
The attached log was obtained with
/usr/lib/ring/dring -d -c 2>&1 | tee dring5.log
The image is a screen capture taken immediately after the call drop (less than 1s after) in order to show what was visible in the log. The big seqence of consecutive "underrun occured" was during the call but it paused more than 10s before the call drop.
[dring5.log](/uploads/13531e3ba91c41ce9edd1c87531a616b/dring5.log)
![right_after_drop](/uploads/32eccf95fdc4c7191b6c18ae7bab4d45/right_after_drop.png)Ming Rui ZhangMing Rui Zhanghttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/907MIUI/Android's dark theme inverts my qr code image2021-03-15T17:55:08ZMIUI/Android's dark theme inverts my qr code imageWhen system option "dark mode" is enabled jami qr code becomes inverted no matter what theme is active as jami's option.
All dark theme's differences are:
1. three button backgrounds "QR code" "Share" "Link a new device" in "Account...When system option "dark mode" is enabled jami qr code becomes inverted no matter what theme is active as jami's option.
All dark theme's differences are:
1. three button backgrounds "QR code" "Share" "Link a new device" in "Account" tab,
2. in qr section there are qr image and "Share my QR" button,
3. in "conversations" tab in "About jami" the "credits" button background,
4. In account choosing menu, default profile pictures (only the "human" part), and in profile picture choosing dialog. The human part changes its color to black, while in chats those stay white
(Button backgrounds in 1, 2, 3 are white in jami's dark theme, and android's dark mode turns them to very dark color. But button text is still kind of readable because of blueish text color)
MIUI 12.0.1 Android 10https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/908Shortcut must have a non-empty label2021-03-23T21:13:00ZAmirhossein NaghshzanShortcut must have a non-empty labelApplication crashes after hanging up a conferance and go to HomeActivity with below log:
Caused by: java.lang.IllegalArgumentException: Shortcut must have a non-empty label
at androidx.core.content.pm.ShortcutInfoCompat$a.a(Sour...Application crashes after hanging up a conferance and go to HomeActivity with below log:
Caused by: java.lang.IllegalArgumentException: Shortcut must have a non-empty label
at androidx.core.content.pm.ShortcutInfoCompat$a.a(SourceFile:536)
at cx.ring.client.HomeActivity.setShareShortcuts(SourceFile:806)
at cx.ring.client.HomeActivity.a(Unknown Source:0)Amirhossein NaghshzanAmirhossein Naghshzanhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/298Cannot hangup when switching from conference to normal call2021-03-29T12:47:18ZMing Rui ZhangCannot hangup when switching from conference to normal callAlice call Bob
Alice adds John to call with Bob
Bob hangup
Alice cannot end call with JohnAlice call Bob
Alice adds John to call with Bob
Bob hangup
Alice cannot end call with JohnMing Rui ZhangMing Rui Zhanghttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/909Disable acceleration in conferences - AndroidTV2021-05-10T13:19:56ZAmirhossein NaghshzanDisable acceleration in conferences - AndroidTVAccelerated encoding should be disabled in conferencesAccelerated encoding should be disabled in conferenceshttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/910Hangup button does not hang up a conference - AndroidTV2021-05-10T13:23:33ZAmirhossein NaghshzanHangup button does not hang up a conference - AndroidTVOn TV when we are in a conference and hangup button pushed, the call does not hang up on other devicesOn TV when we are in a conference and hangup button pushed, the call does not hang up on other deviceshttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/339Call: client closes when hangup fullscreen call2021-08-18T10:21:58ZAline Gondim SantosCall: client closes when hangup fullscreen callAlice calls Bob
Alice puts call in full screen
Alice hangup call
Client closesAlice calls Bob
Alice puts call in full screen
Alice hangup call
Client closeshttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1207Linked devices bug(i hope)2023-02-06T00:23:23ZTonyStone31Linked devices bug(i hope)So about 2 weeks ago I started having connection issues and unable to send and receive from my mobile phone to my wife while connected to our Mobile carrier only. Seemed to not be an issue if we were on wifi with our android devices... ...So about 2 weeks ago I started having connection issues and unable to send and receive from my mobile phone to my wife while connected to our Mobile carrier only. Seemed to not be an issue if we were on wifi with our android devices... even when on separate networks. Anyway what I happened to find is on my desktop client at one point i set it up as a device linked to my account. There appears to be several linked devices that I NEVER ADDED. When I revoke a device, enter password, click ok, then go offline and back online I get several additional devices that are suposedly linked.
Is it possible that when we were having issues it is because some how it was sending all of my messages to other linked accounts... possibly someone spying???
Anyway here is some info I was able to gather from the daemon when i started and performed above actions. I hope it is helpful. In the meantime I backed up this account on my desktop for troubleshooting and investigating but in order to reliably communicate with others again I had to create a new account for my mobile. In the future I would like to link my desktop to my new account but for now I will wait and see if something can be found out here.
```
/usr/lib/ring $ ./dring -cd
Jami Daemon 9.9.0, by Savoir-faire Linux 2004-2019
https://jami.net/
[Video support enabled]
[Plugins support enabled]
[1615852620.876| 5590|ringbuffer.cpp :55 ] Create new RingBuffer audiolayer_id
[1615852620.877| 5590|video_device_monitor_impl.cpp:150 ] udev: adding device with id 046d_HD_Webcam_C615_0B888740
[1615852620.945| 5590|video_device.h :133 ] Default video settings: 800x600, 30 FPS
[1615852620.945| 5590|video_device_monitor_impl.cpp:150 ] udev: adding device with id 046d_HD_Webcam_C615_0B888740
[1615852620.946| 5590|manager.cpp :708 ] Not initialized
[1615852620.946| 5590|manager.cpp :708 ] Not initialized
19:57:00.946 os_core_unix.c !pjlib 2.10 for POSIX initialized
[1615852620.946| 5590|manager.cpp :773 ] Using PJSIP version 2.10 for x86_64-pc-linux-gnu
[1615852620.946| 5590|manager.cpp :774 ] Using GnuTLS version 3.6.15
[1615852620.946| 5590|manager.cpp :775 ] Using OpenDHT version 2.1.9
[1615852620.946| 5590|manager.cpp :776 ] Using FFmpeg version 4.3.git
[1615852620.946| 5590|sipvoiplink.cpp :615 ] Using SIP nameserver: 127.0.0.53
[1615852620.946| 5590|sipvoiplink.cpp :714 ] SIPVoIPLink@0x55cebe2cabf0
[1615852620.946| 5594|sip_utils.cpp :252 ] Registered thread 0x7fc4258a74f0 (0xB15D6)
[1615852620.946| 5590|manager.cpp :791 ] Configuration file path: /home/tony/.config/jami/dring.yml
[1615852620.948| 5599|system_codec_container.cpp:197 ] Can't find a usable accelerated H265/HEVC codec, disabling.
[1615852620.948| 5599|system_codec_container.cpp:232 ] Encoders found: H264 VP8 MP4V-ES H263-1998 opus G722 speex speex speex PCMA PCMU
[1615852620.948| 5599|system_codec_container.cpp:233 ] Decoders found: H264 VP8 MP4V-ES H263-1998 opus G722 speex speex speex PCMA PCMU
[1615852620.948| 5599|jamiaccount.cpp :316 ] [Account ae7f47077fe61458] Can't load proxy URL from cache: Can't check write time for: /home/tony/.cache/jami/ae7f47077fe61458/dhtproxy
[1615852620.949| 5599|jamiaccount.cpp :1914 ] [Account ae7f47077fe61458] Creating a new upnp controller instance
[1615852620.949| 5599|upnp_context.cpp :48 ] Creating UPnPContext instance [0x7fc418006db0]
[1615852620.949| 5599|upnp_control.cpp :38 ] Controller@0x7fc4180047e0: Created UPnP Controller session
[1615852620.949| 5591|nat_pmp.cpp :119 ] NAT-PMP: Setting observer to 0x7fc418006db0
[1615852620.950| 5599|jamiaccount.cpp :1066 ] [Account ae7f47077fe61458] loading account
[1615852620.950| 5599|namedirectory.cpp :493 ] Loaded 19 name-address mappings
[1615852620.950| 5599|account_manager.cpp:57 ] Loading certificate from 'ring_device.crt' and key from 'ring_device.key' at /home/tony/.local/share/jami/ae7f47077fe61458
[1615852620.957| 5591|pupnp.cpp :213 ] PUPnP: Initialized on 192.168.1.177:49152 | fe80:0000:0000:0000:840a:4ae9:1961:aa5f:49152
[1615852620.957| 5591|pupnp.cpp :234 ] PUPnP: Successfully registered client
[1615852620.957| 5591|upnp_context.cpp :334 ] Successfully registered controller 0x7fc418006db0
[1615852620.957| 5591|upnp_context.cpp :98 ] Starting UPNP context
[1615852620.957| 5591|pupnp.cpp :300 ] PUPnP: Start search for IGD: attempt 1
[1615852620.958| 5610|pupnp.cpp :252 ] PUPnP: Send IGD search request
[1615852620.958| 5600|nat_pmp.cpp :70 ] NAT-PMP: Trying to initialize IGD
[1615852620.958| 5600|nat_pmp.cpp :98 ] NAT-PMP: Initialized on gateway 192.168.1.1
[1615852620.958| 5600|nat_pmp.cpp :478 ] NAT-PMP: Setting IGD 192.168.1.1 public address to 74.76.58.56
[1615852620.958| 5600|nat_pmp.cpp :488 ] NAT-PMP: Send request to close all existing mappings to IGD 192.168.1.1
[1615852620.958| 5591|upnp_context.cpp :848 ] New event for IGD [NAT-PMP Gateway] [NAT-PMP]: [ADDED]
[1615852620.958| 5591|upnp_context.cpp :889 ] IGD [NAT-PMP] on address 192.168.1.1:0 was added. Will process any pending requests
[1615852620.958| 5591|upnp_context.cpp :541 ] Current preferred protocol [NAT-PMP] IGD [NAT-PMP Gateway 192.168.1.1]
[1615852620.958| 5591|upnp_context.cpp :561 ] Mapping status [TCP] - overall 0: 0 open (0 ready + 0 in use), 0 pending, 0 in-progress, 0 failed
[1615852620.959| 5591|upnp_context.cpp :425 ] Provision 4 new mappings of type [TCP]
[1615852620.959| 5591|upnp_context.cpp :402 ] Request mapping JAMI-TCP:13662 using protocol [NAT-PMP] IGD [NAT-PMP Gateway 192.168.1.1]
[1615852620.959| 5591|mapping.cpp :104 ] Changed mapping JAMI-TCP:13662 state from PENDING to IN_PROGRESS
[1615852620.959| 5591|upnp_context.cpp :402 ] Request mapping JAMI-TCP:12317 using protocol [NAT-PMP] IGD [NAT-PMP Gateway 192.168.1.1]
[1615852620.959| 5600|nat_pmp.cpp :216 ] NAT-PMP: Request mapping JAMI-TCP:13662 on 192.168.1.1
[1615852620.959| 5591|mapping.cpp :104 ] Changed mapping JAMI-TCP:12317 state from PENDING to IN_PROGRESS
[1615852620.960| 5600|mapping.cpp :104 ] Changed mapping JAMI-TCP:13662 state from IN_PROGRESS to OPEN
[1615852620.960| 5591|upnp_context.cpp :402 ] Request mapping JAMI-TCP:13439 using protocol [NAT-PMP] IGD [NAT-PMP Gateway 192.168.1.1]
[1615852620.960| 5600|nat_pmp.cpp :367 ] NAT-PMP: Allocated mapping JAMI-TCP:13662 on 192.168.1.1
[1615852620.960| 5600|nat_pmp.cpp :216 ] NAT-PMP: Request mapping JAMI-TCP:12317 on 192.168.1.1
[1615852620.960| 5600|mapping.cpp :104 ] Changed mapping JAMI-TCP:12317 state from IN_PROGRESS to OPEN
[1615852620.960| 5591|mapping.cpp :104 ] Changed mapping JAMI-TCP:13439 state from PENDING to IN_PROGRESS
[1615852620.960| 5600|nat_pmp.cpp :367 ] NAT-PMP: Allocated mapping JAMI-TCP:12317 on 192.168.1.1
[1615852620.960| 5591|upnp_context.cpp :402 ] Request mapping JAMI-TCP:14386 using protocol [NAT-PMP] IGD [NAT-PMP Gateway 192.168.1.1]
[1615852620.960| 5600|nat_pmp.cpp :216 ] NAT-PMP: Request mapping JAMI-TCP:13439 on 192.168.1.1
[1615852620.960| 5591|mapping.cpp :104 ] Changed mapping JAMI-TCP:14386 state from PENDING to IN_PROGRESS
[1615852620.960| 5591|upnp_context.cpp :561 ] Mapping status [UDP] - overall 0: 0 open (0 ready + 0 in use), 0 pending, 0 in-progress, 0 failed
[1615852620.960| 5591|upnp_context.cpp :425 ] Provision 8 new mappings of type [UDP]
[1615852620.960| 5591|upnp_context.cpp :402 ] Request mapping JAMI-UDP:22676 using protocol [NAT-PMP] IGD [NAT-PMP Gateway 192.168.1.1]
[1615852620.960| 5591|mapping.cpp :104 ] Changed mapping JAMI-UDP:22676 state from PENDING to IN_PROGRESS
[1615852620.960| 5591|upnp_context.cpp :402 ] Request mapping JAMI-UDP:21975 using protocol [NAT-PMP] IGD [NAT-PMP Gateway 192.168.1.1]
[1615852620.960| 5591|mapping.cpp :104 ] Changed mapping JAMI-UDP:21975 state from PENDING to IN_PROGRESS
[1615852620.960| 5591|upnp_context.cpp :402 ] Request mapping JAMI-UDP:20766 using protocol [NAT-PMP] IGD [NAT-PMP Gateway 192.168.1.1]
[1615852620.960| 5591|mapping.cpp :104 ] Changed mapping JAMI-UDP:20766 state from PENDING to IN_PROGRESS
[1615852620.960| 5591|upnp_context.cpp :402 ] Request mapping JAMI-UDP:22504 using protocol [NAT-PMP] IGD [NAT-PMP Gateway 192.168.1.1]
[1615852620.960| 5591|mapping.cpp :104 ] Changed mapping JAMI-UDP:22504 state from PENDING to IN_PROGRESS
[1615852620.960| 5591|upnp_context.cpp :402 ] Request mapping JAMI-UDP:24788 using protocol [NAT-PMP] IGD [NAT-PMP Gateway 192.168.1.1]
[1615852620.960| 5591|mapping.cpp :104 ] Changed mapping JAMI-UDP:24788 state from PENDING to IN_PROGRESS
[1615852620.960| 5591|upnp_context.cpp :402 ] Request mapping JAMI-UDP:20460 using protocol [NAT-PMP] IGD [NAT-PMP Gateway 192.168.1.1]
[1615852620.960| 5600|mapping.cpp :104 ] Changed mapping JAMI-TCP:13439 state from IN_PROGRESS to OPEN
[1615852620.960| 5591|mapping.cpp :104 ] Changed mapping JAMI-UDP:20460 state from PENDING to IN_PROGRESS
[1615852620.960| 5600|nat_pmp.cpp :367 ] NAT-PMP: Allocated mapping JAMI-TCP:13439 on 192.168.1.1
[1615852620.960| 5591|upnp_context.cpp :402 ] Request mapping JAMI-UDP:22273 using protocol [NAT-PMP] IGD [NAT-PMP Gateway 192.168.1.1]
[1615852620.960| 5600|nat_pmp.cpp :216 ] NAT-PMP: Request mapping JAMI-TCP:14386 on 192.168.1.1
[1615852620.960| 5591|mapping.cpp :104 ] Changed mapping JAMI-UDP:22273 state from PENDING to IN_PROGRESS
[1615852620.960| 5591|upnp_context.cpp :402 ] Request mapping JAMI-UDP:24969 using protocol [NAT-PMP] IGD [NAT-PMP Gateway 192.168.1.1]
[1615852620.960| 5591|mapping.cpp :104 ] Changed mapping JAMI-UDP:24969 state from PENDING to IN_PROGRESS
[1615852620.960| 5591|mapping.cpp :104 ] Changed mapping JAMI-TCP:13662 state from IN_PROGRESS to OPEN
[1615852620.961| 5600|mapping.cpp :104 ] Changed mapping JAMI-TCP:14386 state from IN_PROGRESS to OPEN
[1615852620.961| 5591|upnp_context.cpp :947 ] Mapping JAMI-TCP:13662 is already open on IGD 192.168.1.1 [NAT-PMP]
[1615852620.961| 5600|nat_pmp.cpp :367 ] NAT-PMP: Allocated mapping JAMI-TCP:14386 on 192.168.1.1
[1615852620.961| 5591|mapping.cpp :104 ] Changed mapping JAMI-TCP:12317 state from IN_PROGRESS to OPEN
[1615852620.961| 5600|nat_pmp.cpp :216 ] NAT-PMP: Request mapping JAMI-UDP:22676 on 192.168.1.1
[1615852620.961| 5591|upnp_context.cpp :947 ] Mapping JAMI-TCP:12317 is already open on IGD 192.168.1.1 [NAT-PMP]
[1615852620.961| 5591|mapping.cpp :104 ] Changed mapping JAMI-TCP:13439 state from IN_PROGRESS to OPEN
[1615852620.961| 5591|upnp_context.cpp :947 ] Mapping JAMI-TCP:13439 is already open on IGD 192.168.1.1 [NAT-PMP]
[1615852620.961| 5591|mapping.cpp :104 ] Changed mapping JAMI-TCP:14386 state from IN_PROGRESS to OPEN
[1615852620.961| 5591|upnp_context.cpp :947 ] Mapping JAMI-TCP:14386 is already open on IGD 192.168.1.1 [NAT-PMP]
[1615852620.961| 5600|mapping.cpp :104 ] Changed mapping JAMI-UDP:22676 state from IN_PROGRESS to OPEN
[1615852620.961| 5600|nat_pmp.cpp :367 ] NAT-PMP: Allocated mapping JAMI-UDP:22676 on 192.168.1.1
[1615852620.961| 5600|nat_pmp.cpp :216 ] NAT-PMP: Request mapping JAMI-UDP:21975 on 192.168.1.1
[1615852620.961| 5591|mapping.cpp :104 ] Changed mapping JAMI-UDP:22676 state from IN_PROGRESS to OPEN
[1615852620.961| 5591|upnp_context.cpp :947 ] Mapping JAMI-UDP:22676 is already open on IGD 192.168.1.1 [NAT-PMP]
[1615852620.961| 5600|mapping.cpp :104 ] Changed mapping JAMI-UDP:21975 state from IN_PROGRESS to OPEN
[1615852620.961| 5600|nat_pmp.cpp :367 ] NAT-PMP: Allocated mapping JAMI-UDP:21975 on 192.168.1.1
[1615852620.961| 5600|nat_pmp.cpp :216 ] NAT-PMP: Request mapping JAMI-UDP:20766 on 192.168.1.1
[1615852620.961| 5591|mapping.cpp :104 ] Changed mapping JAMI-UDP:21975 state from IN_PROGRESS to OPEN
[1615852620.961| 5591|upnp_context.cpp :947 ] Mapping JAMI-UDP:21975 is already open on IGD 192.168.1.1 [NAT-PMP]
[1615852620.961| 5600|mapping.cpp :104 ] Changed mapping JAMI-UDP:20766 state from IN_PROGRESS to OPEN
[1615852620.961| 5600|nat_pmp.cpp :367 ] NAT-PMP: Allocated mapping JAMI-UDP:20766 on 192.168.1.1
[1615852620.961| 5600|nat_pmp.cpp :216 ] NAT-PMP: Request mapping JAMI-UDP:22504 on 192.168.1.1
[1615852620.961| 5591|mapping.cpp :104 ] Changed mapping JAMI-UDP:20766 state from IN_PROGRESS to OPEN
[1615852620.961| 5591|upnp_context.cpp :947 ] Mapping JAMI-UDP:20766 is already open on IGD 192.168.1.1 [NAT-PMP]
[1615852620.962| 5600|mapping.cpp :104 ] Changed mapping JAMI-UDP:22504 state from IN_PROGRESS to OPEN
[1615852620.962| 5600|nat_pmp.cpp :367 ] NAT-PMP: Allocated mapping JAMI-UDP:22504 on 192.168.1.1
[1615852620.962| 5600|nat_pmp.cpp :216 ] NAT-PMP: Request mapping JAMI-UDP:24788 on 192.168.1.1
[1615852620.962| 5591|mapping.cpp :104 ] Changed mapping JAMI-UDP:22504 state from IN_PROGRESS to OPEN
[1615852620.962| 5591|upnp_context.cpp :947 ] Mapping JAMI-UDP:22504 is already open on IGD 192.168.1.1 [NAT-PMP]
[1615852620.962| 5600|mapping.cpp :104 ] Changed mapping JAMI-UDP:24788 state from IN_PROGRESS to OPEN
[1615852620.962| 5600|nat_pmp.cpp :367 ] NAT-PMP: Allocated mapping JAMI-UDP:24788 on 192.168.1.1
[1615852620.962| 5600|nat_pmp.cpp :216 ] NAT-PMP: Request mapping JAMI-UDP:20460 on 192.168.1.1
[1615852620.962| 5591|mapping.cpp :104 ] Changed mapping JAMI-UDP:24788 state from IN_PROGRESS to OPEN
[1615852620.962| 5591|upnp_context.cpp :947 ] Mapping JAMI-UDP:24788 is already open on IGD 192.168.1.1 [NAT-PMP]
[1615852620.962| 5600|mapping.cpp :104 ] Changed mapping JAMI-UDP:20460 state from IN_PROGRESS to OPEN
[1615852620.962| 5600|nat_pmp.cpp :367 ] NAT-PMP: Allocated mapping JAMI-UDP:20460 on 192.168.1.1
[1615852620.962| 5600|nat_pmp.cpp :216 ] NAT-PMP: Request mapping JAMI-UDP:22273 on 192.168.1.1
[1615852620.962| 5591|mapping.cpp :104 ] Changed mapping JAMI-UDP:20460 state from IN_PROGRESS to OPEN
[1615852620.962| 5591|upnp_context.cpp :947 ] Mapping JAMI-UDP:20460 is already open on IGD 192.168.1.1 [NAT-PMP]
[1615852620.962| 5600|mapping.cpp :104 ] Changed mapping JAMI-UDP:22273 state from IN_PROGRESS to OPEN
[1615852620.962| 5600|nat_pmp.cpp :367 ] NAT-PMP: Allocated mapping JAMI-UDP:22273 on 192.168.1.1
[1615852620.962| 5600|nat_pmp.cpp :216 ] NAT-PMP: Request mapping JAMI-UDP:24969 on 192.168.1.1
[1615852620.962| 5591|mapping.cpp :104 ] Changed mapping JAMI-UDP:22273 state from IN_PROGRESS to OPEN
[1615852620.962| 5591|upnp_context.cpp :947 ] Mapping JAMI-UDP:22273 is already open on IGD 192.168.1.1 [NAT-PMP]
[1615852620.962| 5600|mapping.cpp :104 ] Changed mapping JAMI-UDP:24969 state from IN_PROGRESS to OPEN
[1615852620.962| 5600|nat_pmp.cpp :367 ] NAT-PMP: Allocated mapping JAMI-UDP:24969 on 192.168.1.1
[1615852620.962| 5591|mapping.cpp :104 ] Changed mapping JAMI-UDP:24969 state from IN_PROGRESS to OPEN
[1615852620.962| 5591|upnp_context.cpp :947 ] Mapping JAMI-UDP:24969 is already open on IGD 192.168.1.1 [NAT-PMP]
[1615852620.973| 5599|certstore.cpp :85 ] CertificateStore: loaded 36 local certificates.
[1615852620.980| 5599|account_manager.cpp:143 ] [Auth] checking device receipt for f89e17b207a981e8963bb3ca480220bb988055ac
[1615852620.984| 5599|contact_list.cpp :231 ] [Contacts] error loading trust requests: Can't read file: incomingTrustRequests
[1615852620.986| 5599|contact_list.cpp :430 ] [Contacts] Found account device: 4b81c337b3f90b2c2474d4ef5e428fcc06a7146f
[1615852620.992| 5599|contact_list.cpp :430 ] [Contacts] Found account device: 68e9e8f189d77a22194bea5e596e152838239b8e
[1615852620.994| 5599|contact_list.cpp :430 ] [Contacts] Found account device: IrontTowel-Tower11 fdb7adf0273e3f29595ab7279c81286d1ff004db
[1615852620.996| 5599|account_manager.cpp:186 ] [Auth] Device fdb7adf0273e3f29595ab7279c81286d1ff004db receipt checked successfully for account f89e17b207a981e8963bb3ca480220bb988055ac
[1615852620.996| 5599|jamiaccount.cpp :1127 ] [Account ae7f47077fe61458] loaded account identity
[1615852620.996| 5590|ringbuffer.cpp :55 ] Create new RingBuffer urgentRingBuffer_id
[1615852620.997| 5590|pulselayer.cpp :141 ] Waiting....
[1615852620.997| 5611|pulselayer.cpp :141 ] Waiting....
[1615852620.997| 5611|pulselayer.cpp :141 ] Waiting....
[1615852620.998| 5611|pulselayer.cpp :145 ] Connection to PulseAudio server established
[1615852620.998| 5611|pulselayer.cpp :175 ] Updating PulseAudio sink list
[1615852620.998| 5611|pulselayer.cpp :192 ] Updating PulseAudio source list
[1615852620.998| 5611|pulselayer.cpp :209 ] Updating PulseAudio server infos
[1615852620.998| 5611|pulselayer.cpp :645 ] PulseAudio server info:
Server name: pulseaudio
Server version: 13.99.1
Default Sink alsa_output.pci-0000_00_1b.0.hdmi-stereo
Default Source alsa_input.usb-046d_HD_Webcam_C615_0B888740-00.mono-fallback
Default Sample Specification: s16le 2ch 44100Hz
Default Channel Map: front-left,front-right
[1615852620.998| 5611|audiolayer.cpp :132 ] Hardware audio format available : {s16, 2 channels, 44100Hz} 0
[1615852620.998| 5611|manager.cpp :2635 ] Audio format changed: {s16, 1 channels, 16000Hz} -> {s16, 2 channels, 44100Hz}
[1615852621.050| 5590|jamiaccount.cpp :1874 ] [Account ae7f47077fe61458] Starting account..
[1615852621.050| 5595|jamiaccount.cpp :2751 ] Loading DhParams from file '/home/tony/.cache/jami/ae7f47077fe61458/dhParams'
[1615852621.050| 5590|jamiaccount.cpp :1782 ] UPnP: Attempting to map ports for Jami account
[1615852621.050| 5590|upnp_context.cpp :238 ] Desired port is not set, will provide the first available port for [UDP]
[1615852621.050| 5590|mapping.cpp :86 ] Changing mapping JAMI-UDP:20460 state from AVAILABLE to UNAVAILABLE
[1615852621.050| 5590|jamiaccount.cpp :1800 ] [Account ae7f47077fe61458] DHT UPNP mapping changed to JAMI-UDP:20460 (state=OPEN, auto-update=YES)
[1615852621.051| 5590|jamiaccount.cpp :1834 ] [Account ae7f47077fe61458] Mapping JAMI-UDP:20460 successfully allocated: starting the DHT
[1615852621.051| 5591|jamiaccount.cpp :2069 ] [Account ae7f47077fe61458] Starting account...
[1615852621.051| 5591|jamiaccount.cpp :2646 ] Could not load /home/tony/.cache/jami/ae7f47077fe61458/treatedCalls
[1615852621.051| 5613|jamiaccount.cpp :3548 ] [Account ae7f47077fe61458] Refresh cache for TURN server resolution
[1615852621.054| 5591|jamiaccount.cpp :1937 ] [Account ae7f47077fe61458] Bootstrap node: bootstrap.jami.net
[1615852621.054| 5591|account_manager.cpp:198 ] announcing device at f89e17b207a981e8963bb3ca480220bb988055ac
[1615852621.055| 5613|jamiaccount.cpp :3598 ] [Account ae7f47077fe61458] Cache refreshed for TURN resolution
[1615852621.055| 5591|archive_account_manager.cpp:436 ] Building device sync from fdb7adf0273e3f29595ab7279c81286d1ff004db
[1615852621.055| 5591|archive_account_manager.cpp:443 ] sending device sync to 4b81c337b3f90b2c2474d4ef5e428fcc06a7146f
[1615852621.055| 5591|archive_account_manager.cpp:443 ] sending device sync to 68e9e8f189d77a22194bea5e596e152838239b8e
[1615852621.055| 5591|jamiaccount.cpp :2321 ] [Account ae7f47077fe61458] Listening on callto:fdb7adf0273e3f29595ab7279c81286d1ff004db : 6d3e7fd4c9eff75bf3b010370924135619ca3a73
[1615852621.055| 5591|upnp_context.cpp :541 ] Current preferred protocol [NAT-PMP] IGD [NAT-PMP Gateway 192.168.1.1]
[1615852621.055| 5591|upnp_context.cpp :561 ] Mapping status [TCP] - overall 4: 4 open (4 ready + 0 in use), 0 pending, 0 in-progress, 0 failed
[1615852621.056| 5591|upnp_context.cpp :561 ] Mapping status [UDP] - overall 8: 8 open (7 ready + 1 in use), 0 pending, 0 in-progress, 0 failed
[1615852621.056| 5591|upnp_context.cpp :425 ] Provision 1 new mappings of type [UDP]
[1615852621.056| 5591|upnp_context.cpp :402 ] Request mapping JAMI-UDP:24076 using protocol [NAT-PMP] IGD [NAT-PMP Gateway 192.168.1.1]
[1615852621.056| 5591|mapping.cpp :104 ] Changed mapping JAMI-UDP:24076 state from PENDING to IN_PROGRESS
[1615852621.056| 5600|nat_pmp.cpp :216 ] NAT-PMP: Request mapping JAMI-UDP:24076 on 192.168.1.1
[1615852621.056| 5600|mapping.cpp :104 ] Changed mapping JAMI-UDP:24076 state from IN_PROGRESS to OPEN
[1615852621.056| 5600|nat_pmp.cpp :367 ] NAT-PMP: Allocated mapping JAMI-UDP:24076 on 192.168.1.1
[1615852621.056| 5600|nat_pmp.cpp :236 ] NAT-PMP: Renew mapping JAMI-TCP:12317 on 192.168.1.1
[1615852621.056| 5591|mapping.cpp :104 ] Changed mapping JAMI-UDP:24076 state from IN_PROGRESS to OPEN
[1615852621.056| 5600|nat_pmp.cpp :373 ] NAT-PMP: Renewed mapping JAMI-TCP:12317 on 192.168.1.1
[1615852621.056| 5591|upnp_context.cpp :947 ] Mapping JAMI-UDP:24076 is already open on IGD 192.168.1.1 [NAT-PMP]
[1615852621.056| 5600|nat_pmp.cpp :236 ] NAT-PMP: Renew mapping JAMI-TCP:13439 on 192.168.1.1
[1615852621.056| 5600|nat_pmp.cpp :373 ] NAT-PMP: Renewed mapping JAMI-TCP:13439 on 192.168.1.1
[1615852621.057| 5615|jamiaccount.cpp :2194 ] [Account ae7f47077fe61458] Dht status : IPv4 connecting; IPv6 connecting
[1615852621.057| 5615|jamiaccount.cpp :2204 ] [Account ae7f47077fe61458] connecting to the DHT network...
[1615852621.057| 5600|nat_pmp.cpp :236 ] NAT-PMP: Renew mapping JAMI-TCP:13662 on 192.168.1.1
[1615852621.057| 5600|nat_pmp.cpp :373 ] NAT-PMP: Renewed mapping JAMI-TCP:13662 on 192.168.1.1
[1615852621.057| 5600|nat_pmp.cpp :236 ] NAT-PMP: Renew mapping JAMI-TCP:14386 on 192.168.1.1
[1615852621.057| 5600|nat_pmp.cpp :373 ] NAT-PMP: Renewed mapping JAMI-TCP:14386 on 192.168.1.1
[1615852621.057| 5600|nat_pmp.cpp :236 ] NAT-PMP: Renew mapping JAMI-UDP:20460 on 192.168.1.1
[1615852621.058| 5600|nat_pmp.cpp :373 ] NAT-PMP: Renewed mapping JAMI-UDP:20460 on 192.168.1.1
[1615852621.058| 5600|nat_pmp.cpp :236 ] NAT-PMP: Renew mapping JAMI-UDP:20766 on 192.168.1.1
[1615852621.058| 5600|nat_pmp.cpp :373 ] NAT-PMP: Renewed mapping JAMI-UDP:20766 on 192.168.1.1
[1615852621.058| 5600|nat_pmp.cpp :236 ] NAT-PMP: Renew mapping JAMI-UDP:21975 on 192.168.1.1
[1615852621.059| 5600|nat_pmp.cpp :373 ] NAT-PMP: Renewed mapping JAMI-UDP:21975 on 192.168.1.1
[1615852621.059| 5600|nat_pmp.cpp :236 ] NAT-PMP: Renew mapping JAMI-UDP:22273 on 192.168.1.1
[1615852621.059| 5600|nat_pmp.cpp :373 ] NAT-PMP: Renewed mapping JAMI-UDP:22273 on 192.168.1.1
[1615852621.059| 5600|nat_pmp.cpp :236 ] NAT-PMP: Renew mapping JAMI-UDP:22504 on 192.168.1.1
[1615852621.059| 5600|nat_pmp.cpp :373 ] NAT-PMP: Renewed mapping JAMI-UDP:22504 on 192.168.1.1
[1615852621.060| 5600|nat_pmp.cpp :236 ] NAT-PMP: Renew mapping JAMI-UDP:22676 on 192.168.1.1
[1615852621.060| 5600|nat_pmp.cpp :373 ] NAT-PMP: Renewed mapping JAMI-UDP:22676 on 192.168.1.1
[1615852621.060| 5600|nat_pmp.cpp :236 ] NAT-PMP: Renew mapping JAMI-UDP:24788 on 192.168.1.1
[1615852621.060| 5600|nat_pmp.cpp :373 ] NAT-PMP: Renewed mapping JAMI-UDP:24788 on 192.168.1.1
[1615852621.060| 5600|nat_pmp.cpp :236 ] NAT-PMP: Renew mapping JAMI-UDP:24969 on 192.168.1.1
[1615852621.061| 5600|nat_pmp.cpp :373 ] NAT-PMP: Renewed mapping JAMI-UDP:24969 on 192.168.1.1
[1615852621.082| 5615|jamiaccount.cpp :2194 ] [Account ae7f47077fe61458] Dht status : IPv4 connected; IPv6 connecting
[1615852621.083| 5615|jamiaccount.cpp :2208 ] [Account ae7f47077fe61458] connected to the DHT network
[1615852621.083| 5615|message_engine.cpp:231 ] [Account ae7f47077fe61458] loaded 4 messages from /home/tony/.cache/jami/ae7f47077fe61458/messages
[1615852621.086| 5615|account_manager.cpp:210 ] found CRL for account.
[1615852621.088| 5615|account_manager.cpp:210 ] found CRL for account.
[1615852621.089| 5615|account_manager.cpp:210 ] found CRL for account.
[1615852621.091| 5615|account_manager.cpp:210 ] found CRL for account.
[1615852621.092| 5615|account_manager.cpp:210 ] found CRL for account.
[1615852621.094| 5615|account_manager.cpp:210 ] found CRL for account.
[1615852621.095| 5615|jamiaccount.cpp :2185 ] Query for local certificate store: 4b81c337b3f90b2c2474d4ef5e428fcc06a7146f: 1 found.
[1615852621.116| 5615|jamiaccount.cpp :2185 ] Query for local certificate store: 68e9e8f189d77a22194bea5e596e152838239b8e: 1 found.
[1615852621.139| 5591|jamiaccount.cpp :3350 ] [Account ae7f47077fe61458] Store DHT public IPv4 address : 74.76.58.56
[1615852623.362| 5591|pupnp.cpp :748 ] PUPnP: Discovered a new IGD [uuid:069ecdfc-8e05-985d-9e12-ec2781eb8ce url: http://192.168.1.1:2189/rootDesc.xml]
[1615852623.362| 5591|pupnp.cpp :748 ] PUPnP: Discovered a new IGD [uuid:b1baf23d-7db3-dae8-a622-99728df94fb9 url: http://192.168.1.27:8008/ssdp/device-desc.xml]
[1615852623.362| 5591|pupnp.cpp :748 ] PUPnP: Discovered a new IGD [uuid:Socket-1_0-22A9B1K0105A43 url: http://192.168.1.169:49153/setup.xml]
[1615852623.362| 5591|pupnp.cpp :748 ] PUPnP: Discovered a new IGD [uuid:069ecdfc-8e05-985d-9e12-ec2781eb8c0 url: http://192.168.1.1:2189/rootDesc.xml]
[1615852623.363| 5613|pupnp.cpp :778 ] PUPnP: Succeeded to download device XML document from http://192.168.1.1:2189/rootDesc.xml
[1615852623.363| 5629|pupnp.cpp :778 ] PUPnP: Succeeded to download device XML document from http://192.168.1.1:2189/rootDesc.xml
[1615852623.368| 5627|pupnp.cpp :778 ] PUPnP: Succeeded to download device XML document from http://192.168.1.27:8008/ssdp/device-desc.xml
[1615852623.369| 5628|pupnp.cpp :778 ] PUPnP: Succeeded to download device XML document from http://192.168.1.169:49153/setup.xml
[1615852623.369| 5610|pupnp.cpp :1039 ] PUPnP: Found new device [uuid:069ecdfc-8e05-985d-9e12-ec2781eb8ce]
[1615852623.370| 5610|pupnp.cpp :398 ] PUPnP: Validating the IGD candidate [UDN: uuid:069ecdfc-8e05-985d-9e12-ec2781eb8ce]
Name : FreeBSD router
Service Type : urn:schemas-upnp-org:service:WANIPConnection:1
Service ID : urn:upnp-org:serviceId:WANIPConn1
Base URL : http://192.168.1.1:2189/rootDesc.xml
Location URL : http://192.168.1.1:2189/rootDesc.xml
control URL : http://192.168.1.1:2189/ctl/IPConn
Event URL : http://192.168.1.1:2189/evt/IPConn
[1615852623.371| 5610|pupnp.cpp :470 ] PUPnP: Added a new IGD [uuid:069ecdfc-8e05-985d-9e12-ec2781eb8ce] to the list of valid IGDs
[1615852623.371| 5610|pupnp.cpp :473 ] PUPnP: New IGD addresses [int: 192.168.1.1 - ext: 74.76.58.56]
[1615852623.371| 5610|pupnp.cpp :1350 ] PUPnP: Remove all mappings (if any) on IGD 192.168.1.1 matching descr prefix JAMI
[1615852623.403| 5610|pupnp.cpp :1337 ] PUPnP: Found 0 allocated mappings on IGD 192.168.1.1
[1615852623.403| 5591|upnp_context.cpp :848 ] New event for IGD [uuid:069ecdfc-8e05-985d-9e12-ec2781eb8ce] [UPNP]: [ADDED]
[1615852623.403| 5591|upnp_context.cpp :889 ] IGD [UPNP] on address 192.168.1.1:0 was added. Will process any pending requests
[1615852623.403| 5591|upnp_context.cpp :541 ] Current preferred protocol [NAT-PMP] IGD [NAT-PMP Gateway 192.168.1.1]
[1615852623.403| 5591|upnp_context.cpp :561 ] Mapping status [TCP] - overall 4: 4 open (4 ready + 0 in use), 0 pending, 0 in-progress, 0 failed
[1615852623.403| 5591|upnp_context.cpp :561 ] Mapping status [UDP] - overall 9: 9 open (8 ready + 1 in use), 0 pending, 0 in-progress, 0 failed
[1615852623.403| 5600|nat_pmp.cpp :236 ] NAT-PMP: Renew mapping JAMI-UDP:24076 on 192.168.1.1
[1615852623.403| 5600|nat_pmp.cpp :373 ] NAT-PMP: Renewed mapping JAMI-UDP:24076 on 192.168.1.1
[1615852625.731| 5615|contact_list.cpp :421 ] [Contacts] Found invalid account device: a09e1f0730f5d2ab8a747bc9075d426f6d171574: Certificate check failed with code: 34
* Certificate is revoked
[1615852625.735| 5615|account_manager.cpp:210 ] found CRL for account.
[1615852625.736| 5615|account_manager.cpp:210 ] found CRL for account.
[1615852625.738| 5615|account_manager.cpp:210 ] found CRL for account.
[1615852625.739| 5615|account_manager.cpp:210 ] found CRL for account.
[1615852625.740| 5615|account_manager.cpp:210 ] found CRL for account.
[1615852625.742| 5615|account_manager.cpp:210 ] found CRL for account.
[1615852625.743| 5615|account_manager.cpp:210 ] found CRL for account.
[1615852625.744| 5615|account_manager.cpp:210 ] found CRL for account.
[1615852625.745| 5615|account_manager.cpp:210 ] found CRL for account.
[1615852625.746| 5615|account_manager.cpp:210 ] found CRL for account.
[1615852625.747| 5615|account_manager.cpp:210 ] found CRL for account.
[1615852625.748| 5615|account_manager.cpp:210 ] found CRL for account.
[1615852625.749| 5615|account_manager.cpp:210 ] found CRL for account.
[1615852625.750| 5615|account_manager.cpp:210 ] found CRL for account.
[1615852625.751| 5615|account_manager.cpp:210 ] found CRL for account.
[1615852625.752| 5615|account_manager.cpp:210 ] found CRL for account.
[1615852625.754| 5615|account_manager.cpp:210 ] found CRL for account.
[1615852625.755| 5615|account_manager.cpp:210 ] found CRL for account.
[1615852625.756| 5615|account_manager.cpp:210 ] found CRL for account.
[1615852625.757| 5615|account_manager.cpp:210 ] found CRL for account.
[1615852625.758| 5615|account_manager.cpp:210 ] found CRL for account.
[1615852625.759| 5615|account_manager.cpp:210 ] found CRL for account.
[1615852625.760| 5615|account_manager.cpp:210 ] found CRL for account.
[1615852625.762| 5615|account_manager.cpp:210 ] found CRL for account.
[1615852625.763| 5615|account_manager.cpp:210 ] found CRL for account.
[1615852625.764| 5615|account_manager.cpp:210 ] found CRL for account.
[1615852627.446| 5591|pupnp.cpp :748 ] PUPnP: Discovered a new IGD [uuid:23456789-1234-1010-8000-104FA8A7617A url: http://192.168.1.27:52323/MediaRenderer.xml]
[1615852627.448| 5613|pupnp.cpp :778 ] PUPnP: Succeeded to download device XML document from http://192.168.1.27:52323/MediaRenderer.xml
[1615852638.004| 5591|pupnp.cpp :748 ] PUPnP: Discovered a new IGD [uuid:069ecdfc-8e05-985d-9e12-ec2781eb8cf url: http://192.168.1.1:2189/rootDesc.xml]
[1615852638.005| 5629|pupnp.cpp :778 ] PUPnP: Succeeded to download device XML document from http://192.168.1.1:2189/rootDesc.xml
[1615852643.481| 5615|jamiaccount.cpp :2194 ] [Account ae7f47077fe61458] Dht status : IPv4 connected; IPv6 disconnected
[1615852647.945| 5615|jamiaccount.cpp :2194 ] [Account ae7f47077fe61458] Dht status : IPv4 connected; IPv6 connecting
[1615852651.021| 5591|pupnp.cpp :748 ] PUPnP: Discovered a new IGD [uuid:8f50ef5f-d371-4b7a-bcba-f091522b1468 url: http://192.168.1.27:36768/sony/webapi/ssdp/dd.xml]
[1615852651.025| 5627|pupnp.cpp :778 ] PUPnP: Succeeded to download device XML document from http://192.168.1.27:36768/sony/webapi/ssdp/dd.xml
[1615852653.403| 5591|upnp_context.cpp :541 ] Current preferred protocol [NAT-PMP] IGD [NAT-PMP Gateway 192.168.1.1]
[1615852653.403| 5591|upnp_context.cpp :561 ] Mapping status [TCP] - overall 4: 4 open (4 ready + 0 in use), 0 pending, 0 in-progress, 0 failed
[1615852653.403| 5591|upnp_context.cpp :561 ] Mapping status [UDP] - overall 9: 9 open (8 ready + 1 in use), 0 pending, 0 in-progress, 0 failed
[1615852663.144| 5591|pupnp.cpp :748 ] PUPnP: Discovered a new IGD [uuid:a619c611-6951-40c5-9075-144ae1108938 url: http://192.168.1.27:22422/dd.xml]
[1615852663.146| 5628|pupnp.cpp :778 ] PUPnP: Succeeded to download device XML document from http://192.168.1.27:22422/dd.xml
[1615852680.004| 5602|pupnp.cpp :898 ] PUPnP: Received discovery search time-out
[1615852681.004| 5602|pupnp.cpp :898 ] PUPnP: Received discovery search time-out
[1615852681.551| 5615|jamiaccount.cpp :2194 ] [Account ae7f47077fe61458] Dht status : IPv4 connected; IPv6 disconnected
[1615852682.004| 5602|pupnp.cpp :898 ] PUPnP: Received discovery search time-out
[1615852682.004| 5602|pupnp.cpp :898 ] PUPnP: Received discovery search time-out
[1615852682.028| 5615|jamiaccount.cpp :2194 ] [Account ae7f47077fe61458] Dht status : IPv4 connected; IPv6 connecting
[1615852683.403| 5591|upnp_context.cpp :541 ] Current preferred protocol [NAT-PMP] IGD [NAT-PMP Gateway 192.168.1.1]
[1615852683.404| 5591|upnp_context.cpp :561 ] Mapping status [TCP] - overall 4: 4 open (4 ready + 0 in use), 0 pending, 0 in-progress, 0 failed
[1615852683.404| 5591|upnp_context.cpp :561 ] Mapping status [UDP] - overall 9: 9 open (8 ready + 1 in use), 0 pending, 0 in-progress, 0 failed
[1615852700.258| 5615|jamiaccount.cpp :2194 ] [Account ae7f47077fe61458] Dht status : IPv4 connected; IPv6 disconnected
[1615852700.548| 5615|jamiaccount.cpp :2194 ] [Account ae7f47077fe61458] Dht status : IPv4 connected; IPv6 connecting
[1615852713.403| 5591|upnp_context.cpp :541 ] Current preferred protocol [NAT-PMP] IGD [NAT-PMP Gateway 192.168.1.1]
[1615852713.403| 5591|upnp_context.cpp :561 ] Mapping status [TCP] - overall 4: 4 open (4 ready + 0 in use), 0 pending, 0 in-progress, 0 failed
[1615852713.403| 5591|upnp_context.cpp :561 ] Mapping status [UDP] - overall 9: 9 open (8 ready + 1 in use), 0 pending, 0 in-progress, 0 failed
[1615852743.404| 5591|upnp_context.cpp :541 ] Current preferred protocol [NAT-PMP] IGD [NAT-PMP Gateway 192.168.1.1]
[1615852743.404| 5591|upnp_context.cpp :561 ] Mapping status [TCP] - overall 4: 4 open (4 ready + 0 in use), 0 pending, 0 in-progress, 0 failed
[1615852743.404| 5591|upnp_context.cpp :561 ] Mapping status [UDP] - overall 9: 9 open (8 ready + 1 in use), 0 pending, 0 in-progress, 0 failed
[1615852773.404| 5591|upnp_context.cpp :541 ] Current preferred protocol [NAT-PMP] IGD [NAT-PMP Gateway 192.168.1.1]
[1615852773.404| 5591|upnp_context.cpp :561 ] Mapping status [TCP] - overall 4: 4 open (4 ready + 0 in use), 0 pending, 0 in-progress, 0 failed
[1615852773.404| 5591|upnp_context.cpp :561 ] Mapping status [UDP] - overall 9: 9 open (8 ready + 1 in use), 0 pending, 0 in-progress, 0 failed
[1615852803.404| 5591|upnp_context.cpp :541 ] Current preferred protocol [NAT-PMP] IGD [NAT-PMP Gateway 192.168.1.1]
[1615852803.404| 5591|upnp_context.cpp :561 ] Mapping status [TCP] - overall 4: 4 open (4 ready + 0 in use), 0 pending, 0 in-progress, 0 failed
[1615852803.404| 5591|upnp_context.cpp :561 ] Mapping status [UDP] - overall 9: 9 open (8 ready + 1 in use), 0 pending, 0 in-progress, 0 failed
[1615852833.404| 5591|upnp_context.cpp :541 ] Current preferred protocol [NAT-PMP] IGD [NAT-PMP Gateway 192.168.1.1]
[1615852833.404| 5591|upnp_context.cpp :561 ] Mapping status [TCP] - overall 4: 4 open (4 ready + 0 in use), 0 pending, 0 in-progress, 0 failed
[1615852833.404| 5591|upnp_context.cpp :561 ] Mapping status [UDP] - overall 9: 9 open (8 ready + 1 in use), 0 pending, 0 in-progress, 0 failed
[1615852863.051| 5590|jamiaccount.cpp :2030 ] [Account ae7f47077fe61458] tracking buddy 5d151c7d1fce0df006b8d939ee048f9cfe4eb737
[1615852863.052| 5590|jamiaccount.cpp :2030 ] [Account ae7f47077fe61458] tracking buddy 8c8d66be0f3feb65fd3edcd86712bad14146917d
[1615852863.052| 5590|jamiaccount.cpp :2030 ] [Account ae7f47077fe61458] tracking buddy c56f255b8ff1346fb046cd7236f1a91a4c2b623e
[1615852863.053| 5590|jamiaccount.cpp :2030 ] [Account ae7f47077fe61458] tracking buddy e74b5e63c32716b446c01f94c4db4b0a92173313
[1615852863.072| 5590|jamiaccount.cpp :2030 ] [Account ae7f47077fe61458] tracking buddy fd061306a2de34e3c65aa247d526f079d5b09204
[1615852863.404| 5591|upnp_context.cpp :541 ] Current preferred protocol [NAT-PMP] IGD [NAT-PMP Gateway 192.168.1.1]
[1615852863.404| 5591|upnp_context.cpp :561 ] Mapping status [TCP] - overall 4: 4 open (4 ready + 0 in use), 0 pending, 0 in-progress, 0 failed
[1615852863.404| 5591|upnp_context.cpp :561 ] Mapping status [UDP] - overall 9: 9 open (8 ready + 1 in use), 0 pending, 0 in-progress, 0 failed
[1615852893.404| 5591|upnp_context.cpp :541 ] Current preferred protocol [NAT-PMP] IGD [NAT-PMP Gateway 192.168.1.1]
[1615852893.404| 5591|upnp_context.cpp :561 ] Mapping status [TCP] - overall 4: 4 open (4 ready + 0 in use), 0 pending, 0 in-progress, 0 failed
[1615852893.404| 5591|upnp_context.cpp :561 ] Mapping status [UDP] - overall 9: 9 open (8 ready + 1 in use), 0 pending, 0 in-progress, 0 failed
[1615852895.116| 5596|archive_account_manager.cpp:511 ] [Auth] reading account archive
[1615852895.116| 5596|fileutils.cpp :460 ] Reading archive from /home/tony/.local/share/jami/ae7f47077fe61458/archive.gz
[1615852896.520| 5596|accountarchive.cpp:32 ] Loading account archive (16444 bytes)
[1615852896.548| 5590|archive_account_manager.cpp:537 ] [Auth] building account archive
[1615852896.560| 5590|fileutils.cpp :487 ] Writing archive to /home/tony/.local/share/jami/ae7f47077fe61458/archive.gz
[1615852897.867| 5590|archive_account_manager.cpp:436 ] Building device sync from fdb7adf0273e3f29595ab7279c81286d1ff004db
[1615852897.867| 5590|archive_account_manager.cpp:443 ] sending device sync to 4b81c337b3f90b2c2474d4ef5e428fcc06a7146f
[1615852923.404| 5591|upnp_context.cpp :541 ] Current preferred protocol [NAT-PMP] IGD [NAT-PMP Gateway 192.168.1.1]
[1615852923.404| 5591|upnp_context.cpp :561 ] Mapping status [TCP] - overall 4: 4 open (4 ready + 0 in use), 0 pending, 0 in-progress, 0 failed
[1615852923.404| 5591|upnp_context.cpp :561 ] Mapping status [UDP] - overall 9: 9 open (8 ready + 1 in use), 0 pending, 0 in-progress, 0 failed
[1615852937.934| 5598|archive_account_manager.cpp:511 ] [Auth] reading account archive
[1615852937.934| 5598|fileutils.cpp :460 ] Reading archive from /home/tony/.local/share/jami/ae7f47077fe61458/archive.gz
[1615852939.283| 5598|accountarchive.cpp:32 ] Loading account archive (29381 bytes)
[1615852939.312| 5590|archive_account_manager.cpp:537 ] [Auth] building account archive
[1615852939.313| 5590|fileutils.cpp :487 ] Writing archive to /home/tony/.local/share/jami/ae7f47077fe61458/archive.gz
[1615852940.626| 5590|archive_account_manager.cpp:436 ] Building device sync from fdb7adf0273e3f29595ab7279c81286d1ff004db
[1615852953.178| 5590|manager.cpp :2269 ] Audio device already selected ; doing nothing.
[1615852953.178| 5590|manager.cpp :2269 ] Audio device already selected ; doing nothing.
[1615852953.181| 5590|manager.cpp :2269 ] Audio device already selected ; doing nothing.
[1615852953.404| 5591|upnp_context.cpp :541 ] Current preferred protocol [NAT-PMP] IGD [NAT-PMP Gateway 192.168.1.1]
[1615852953.404| 5591|upnp_context.cpp :561 ] Mapping status [TCP] - overall 4: 4 open (4 ready + 0 in use), 0 pending, 0 in-progress, 0 failed
[1615852953.404| 5591|upnp_context.cpp :561 ] Mapping status [UDP] - overall 9: 9 open (8 ready + 1 in use), 0 pending, 0 in-progress, 0 failed
[1615852963.322| 5590|jamiaccount.cpp :810 ] Exported account to /home/tony/.local/share/jami/ae7f47077fe61458/config.yml
[1615852963.322| 5590|jamiaccount.cpp :2543 ] [Account ae7f47077fe61458] unregistering account 0x7fc418000b70
[1615852963.324| 5600|mapping.cpp :104 ] Changed mapping JAMI-UDP:20460 state from OPEN to FAILED
[1615852963.324| 5597|message_engine.cpp:303 ] [Account ae7f47077fe61458] saved 2 messages to /home/tony/.cache/jami/ae7f47077fe61458/messages
[1615852963.385| 5590|manager.cpp :2649 ] Set accounts order : ae7f47077fe61458/
[1615852963.385| 5590|manager.cpp :1736 ] Saving Configuration to XDG directory /home/tony/.config/jami/dring.yml
[1615852963.388| 5590|manager.cpp :2649 ] Set accounts order : ae7f47077fe61458/
[1615852963.388| 5590|manager.cpp :1736 ] Saving Configuration to XDG directory /home/tony/.config/jami/dring.yml
[1615852967.968| 5590|jamiaccount.cpp :810 ] Exported account to /home/tony/.local/share/jami/ae7f47077fe61458/config.yml
[1615852967.968| 5590|jamiaccount.cpp :1874 ] [Account ae7f47077fe61458] Starting account..
[1615852967.968| 5590|jamiaccount.cpp :1782 ] UPnP: Attempting to map ports for Jami account
[1615852967.968| 5590|upnp_control.cpp :135 ] Failed to remove mapping UDP from local list
[1615852967.968| 5590|upnp_context.cpp :241 ] Try to find mapping for port 20460 [UDP]
[1615852967.968| 5590|upnp_context.cpp :272 ] Did not find any available mapping. Will request one now
[1615852967.968| 5590|mapping.cpp :104 ] Changed mapping JAMI-UDP:20460 state from OPEN to PENDING
[1615852967.968| 5590|upnp_context.cpp :1076 ] Mapping request for JAMI-UDP:20460 already added!
[1615852967.968| 5629|jamiaccount.cpp :3548 ] [Account ae7f47077fe61458] Refresh cache for TURN server resolution
[1615852967.969| 5591|upnp_context.cpp :541 ] Current preferred protocol [NAT-PMP] IGD [NAT-PMP Gateway 192.168.1.1]
[1615852967.969| 5600|mapping.cpp :104 ] Changed mapping JAMI-UDP:20460 state from OPEN to FAILED
[1615852967.969| 5591|upnp_context.cpp :561 ] Mapping status [TCP] - overall 4: 4 open (4 ready + 0 in use), 0 pending, 0 in-progress, 0 failed
[1615852967.969| 5591|upnp_context.cpp :561 ] Mapping status [UDP] - overall 9: 9 open (8 ready + 1 in use), 0 pending, 0 in-progress, 0 failed
[1615852967.969| 5591|jamiaccount.cpp :2069 ] [Account ae7f47077fe61458] Starting account...
[1615852967.969| 5591|jamiaccount.cpp :2646 ] Could not load /home/tony/.cache/jami/ae7f47077fe61458/treatedCalls
[1615852967.971| 5591|jamiaccount.cpp :1937 ] [Account ae7f47077fe61458] Bootstrap node: bootstrap.jami.net
[1615852967.971| 5591|account_manager.cpp:198 ] announcing device at f89e17b207a981e8963bb3ca480220bb988055ac
[1615852967.972| 5591|archive_account_manager.cpp:436 ] Building device sync from fdb7adf0273e3f29595ab7279c81286d1ff004db
[1615852967.972| 5591|jamiaccount.cpp :2321 ] [Account ae7f47077fe61458] Listening on callto:fdb7adf0273e3f29595ab7279c81286d1ff004db : 6d3e7fd4c9eff75bf3b010370924135619ca3a73
[1615852967.972| 5591|jamiaccount.cpp :2030 ] [Account ae7f47077fe61458] tracking buddy 5d151c7d1fce0df006b8d939ee048f9cfe4eb737
[1615852967.972| 5591|jamiaccount.cpp :2030 ] [Account ae7f47077fe61458] tracking buddy 8c8d66be0f3feb65fd3edcd86712bad14146917d
[1615852967.972| 5591|jamiaccount.cpp :2030 ] [Account ae7f47077fe61458] tracking buddy c56f255b8ff1346fb046cd7236f1a91a4c2b623e
[1615852967.972| 5591|jamiaccount.cpp :2030 ] [Account ae7f47077fe61458] tracking buddy e74b5e63c32716b446c01f94c4db4b0a92173313
[1615852967.972| 5591|jamiaccount.cpp :2030 ] [Account ae7f47077fe61458] tracking buddy fd061306a2de34e3c65aa247d526f079d5b09204
[1615852967.995| 5590|manager.cpp :2649 ] Set accounts order : ae7f47077fe61458/
[1615852967.995| 5590|manager.cpp :1736 ] Saving Configuration to XDG directory /home/tony/.config/jami/dring.yml
[1615852967.997| 5590|manager.cpp :2649 ] Set accounts order : ae7f47077fe61458/
[1615852967.997| 5590|manager.cpp :1736 ] Saving Configuration to XDG directory /home/tony/.config/jami/dring.yml
[1615852968.111| 5851|jamiaccount.cpp :2194 ] [Account ae7f47077fe61458] Dht status : IPv4 connecting; IPv6 connecting
[1615852968.111| 5851|jamiaccount.cpp :2204 ] [Account ae7f47077fe61458] connecting to the DHT network...
[1615852968.135| 5851|jamiaccount.cpp :2194 ] [Account ae7f47077fe61458] Dht status : IPv4 connected; IPv6 connecting
[1615852968.135| 5851|jamiaccount.cpp :2208 ] [Account ae7f47077fe61458] connected to the DHT network
[1615852968.135| 5851|message_engine.cpp:231 ] [Account ae7f47077fe61458] loaded 4 messages from /home/tony/.cache/jami/ae7f47077fe61458/messages
[1615852968.136| 5851|account_manager.cpp:210 ] found CRL for account.
[1615852968.137| 5851|account_manager.cpp:210 ] found CRL for account.
[1615852968.137| 5851|account_manager.cpp:210 ] found CRL for account.
[1615852968.138| 5851|account_manager.cpp:210 ] found CRL for account.
[1615852968.138| 5851|account_manager.cpp:210 ] found CRL for account.
[1615852968.138| 5851|account_manager.cpp:210 ] found CRL for account.
[1615852968.139| 5591|jamiaccount.cpp :3350 ] [Account ae7f47077fe61458] Store DHT public IPv4 address : 74.76.58.56
[1615852968.150| 5629|jamiaccount.cpp :3598 ] [Account ae7f47077fe61458] Cache refreshed for TURN resolution
[1615852968.162| 5590|manager.cpp :2649 ] Set accounts order : ae7f47077fe61458/
[1615852968.162| 5590|manager.cpp :1736 ] Saving Configuration to XDG directory /home/tony/.config/jami/dring.yml
[1615852968.164| 5590|manager.cpp :2649 ] Set accounts order : ae7f47077fe61458/
[1615852968.164| 5590|manager.cpp :1736 ] Saving Configuration to XDG directory /home/tony/.config/jami/dring.yml
[1615852971.821| 5851|contact_list.cpp :430 ] [Contacts] Found account device: 4b81c337b3f90b2c2474d4ef5e428fcc06a7146f
[1615852971.822| 5851|contact_list.cpp :430 ] [Contacts] Found account device: 68e9e8f189d77a22194bea5e596e152838239b8e
[1615852971.824| 5851|contact_list.cpp :421 ] [Contacts] Found invalid account device: a09e1f0730f5d2ab8a747bc9075d426f6d171574: Certificate check failed with code: 34
* Certificate is revoked
[1615852971.826| 5851|account_manager.cpp:210 ] found CRL for account.
[1615852971.827| 5851|account_manager.cpp:210 ] found CRL for account.
[1615852971.827| 5851|account_manager.cpp:210 ] found CRL for account.
[1615852971.828| 5851|account_manager.cpp:210 ] found CRL for account.
[1615852971.828| 5851|account_manager.cpp:210 ] found CRL for account.
[1615852971.829| 5851|account_manager.cpp:210 ] found CRL for account.
[1615852971.829| 5851|account_manager.cpp:210 ] found CRL for account.
[1615852971.830| 5851|account_manager.cpp:210 ] found CRL for account.
[1615852971.830| 5851|account_manager.cpp:210 ] found CRL for account.
[1615852971.830| 5851|account_manager.cpp:210 ] found CRL for account.
[1615852971.831| 5851|account_manager.cpp:210 ] found CRL for account.
[1615852971.831| 5851|account_manager.cpp:210 ] found CRL for account.
[1615852971.832| 5851|account_manager.cpp:210 ] found CRL for account.
[1615852971.832| 5851|account_manager.cpp:210 ] found CRL for account.
[1615852971.833| 5851|account_manager.cpp:210 ] found CRL for account.
[1615852971.833| 5851|account_manager.cpp:210 ] found CRL for account.
[1615852971.834| 5851|account_manager.cpp:210 ] found CRL for account.
[1615852971.834| 5851|account_manager.cpp:210 ] found CRL for account.
[1615852971.834| 5851|account_manager.cpp:210 ] found CRL for account.
[1615852971.835| 5851|account_manager.cpp:210 ] found CRL for account.
[1615852971.835| 5851|account_manager.cpp:210 ] found CRL for account.
[1615852971.836| 5851|account_manager.cpp:210 ] found CRL for account.
[1615852971.836| 5851|account_manager.cpp:210 ] found CRL for account.
[1615852971.837| 5851|account_manager.cpp:210 ] found CRL for account.
[1615852971.837| 5851|account_manager.cpp:210 ] found CRL for account.
[1615852971.837| 5851|account_manager.cpp:210 ] found CRL for account.
[1615852973.104| 5851|account_manager.cpp:210 ] found CRL for account.
[1615852973.105| 5851|account_manager.cpp:210 ] found CRL for account.
[1615852973.105| 5851|account_manager.cpp:210 ] found CRL for account.
[1615852973.106| 5851|account_manager.cpp:210 ] found CRL for account.
[1615852973.106| 5851|account_manager.cpp:210 ] found CRL for account.
[1615852973.106| 5851|account_manager.cpp:210 ] found CRL for account.
[1615852980.589| 5851|jamiaccount.cpp :2194 ] [Account ae7f47077fe61458] Dht status : IPv4 connected; IPv6 disconnected
[1615852982.596| 5851|jamiaccount.cpp :2194 ] [Account ae7f47077fe61458] Dht status : IPv4 connected; IPv6 connecting
[1615852997.969| 5591|upnp_context.cpp :541 ] Current preferred protocol [NAT-PMP] IGD [NAT-PMP Gateway 192.168.1.1]
[1615852997.969| 5591|upnp_context.cpp :561 ] Mapping status [TCP] - overall 4: 4 open (4 ready + 0 in use), 0 pending, 0 in-progress, 0 failed
[1615852997.969| 5591|upnp_context.cpp :561 ] Mapping status [UDP] - overall 9: 9 open (8 ready + 1 in use), 0 pending, 0 in-progress, 0 failed
[1615853007.909| 5851|jamiaccount.cpp :2194 ] [Account ae7f47077fe61458] Dht status : IPv4 connected; IPv6 disconnected
[1615853008.259| 5851|jamiaccount.cpp :2194 ] [Account ae7f47077fe61458] Dht status : IPv4 connected; IPv6 connecting
[1615853027.969| 5591|upnp_context.cpp :541 ] Current preferred protocol [NAT-PMP] IGD [NAT-PMP Gateway 192.168.1.1]
[1615853027.969| 5591|upnp_context.cpp :561 ] Mapping status [TCP] - overall 4: 4 open (4 ready + 0 in use), 0 pending, 0 in-progress, 0 failed
[1615853027.969| 5591|upnp_context.cpp :561 ] Mapping status [UDP] - overall 9: 9 open (8 ready + 1 in use), 0 pending, 0 in-progress, 0 failed
[1615853042.959| 5851|jamiaccount.cpp :2194 ] [Account ae7f47077fe61458] Dht status : IPv4 connected; IPv6 disconnected
[1615853043.726| 5851|jamiaccount.cpp :2194 ] [Account ae7f47077fe61458] Dht status : IPv4 connected; IPv6 connecting
[1615853055.085| 5851|jamiaccount.cpp :2194 ] [Account ae7f47077fe61458] Dht status : IPv4 connected; IPv6 disconnected
[1615853057.385| 5851|jamiaccount.cpp :2194 ] [Account ae7f47077fe61458] Dht status : IPv4 connected; IPv6 connecting
[1615853057.969| 5591|upnp_context.cpp :541 ] Current preferred protocol [NAT-PMP] IGD [NAT-PMP Gateway 192.168.1.1]
[1615853057.969| 5591|upnp_context.cpp :561 ] Mapping status [TCP] - overall 4: 4 open (4 ready + 0 in use), 0 pending, 0 in-progress, 0 failed
[1615853057.969| 5591|upnp_context.cpp :561 ] Mapping status [UDP] - overall 9: 9 open (8 ready + 1 in use), 0 pending, 0 in-progress, 0 failed
[1615853069.830| 5851|jamiaccount.cpp :2194 ] [Account ae7f47077fe61458] Dht status : IPv4 connected; IPv6 disconnected
[1615853071.888| 5851|jamiaccount.cpp :2194 ] [Account ae7f47077fe61458] Dht status : IPv4 connected; IPv6 connecting
[1615853087.969| 5591|upnp_context.cpp :541 ] Current preferred protocol [NAT-PMP] IGD [NAT-PMP Gateway 192.168.1.1]
[1615853087.969| 5591|upnp_context.cpp :561 ] Mapping status [TCP] - overall 4: 4 open (4 ready + 0 in use), 0 pending, 0 in-progress, 0 failed
[1615853087.969| 5591|upnp_context.cpp :561 ] Mapping status [UDP] - overall 9: 9 open (8 ready + 1 in use), 0 pending, 0 in-progress, 0 failed
[1615853117.969| 5591|upnp_context.cpp :541 ] Current preferred protocol [NAT-PMP] IGD [NAT-PMP Gateway 192.168.1.1]
[1615853117.970| 5591|upnp_context.cpp :561 ] Mapping status [TCP] - overall 4: 4 open (4 ready + 0 in use), 0 pending, 0 in-progress, 0 failed
[1615853117.970| 5591|upnp_context.cpp :561 ] Mapping status [UDP] - overall 9: 9 open (8 ready + 1 in use), 0 pending, 0 in-progress, 0 failed
[1615853147.970| 5591|upnp_context.cpp :541 ] Current preferred protocol [NAT-PMP] IGD [NAT-PMP Gateway 192.168.1.1]
[1615853147.970| 5591|upnp_context.cpp :561 ] Mapping status [TCP] - overall 4: 4 open (4 ready + 0 in use), 0 pending, 0 in-progress, 0 failed
[1615853147.970| 5591|upnp_context.cpp :561 ] Mapping status [UDP] - overall 9: 9 open (8 ready + 1 in use), 0 pending, 0 in-progress, 0 failed
[1615853177.970| 5591|upnp_context.cpp :541 ] Current preferred protocol [NAT-PMP] IGD [NAT-PMP Gateway 192.168.1.1]
[1615853177.970| 5591|upnp_context.cpp :561 ] Mapping status [TCP] - overall 4: 4 open (4 ready + 0 in use), 0 pending, 0 in-progress, 0 failed
[1615853177.970| 5591|upnp_context.cpp :561 ] Mapping status [UDP] - overall 9: 9 open (8 ready + 1 in use), 0 pending, 0 in-progress, 0 failed
[1615853207.970| 5591|upnp_context.cpp :541 ] Current preferred protocol [NAT-PMP] IGD [NAT-PMP Gateway 192.168.1.1]
[1615853207.970| 5591|upnp_context.cpp :561 ] Mapping status [TCP] - overall 4: 4 open (4 ready + 0 in use), 0 pending, 0 in-progress, 0 failed
[1615853207.970| 5591|upnp_context.cpp :561 ] Mapping status [UDP] - overall 9: 9 open (8 ready + 1 in use), 0 pending, 0 in-progress, 0 failed
[1615853237.970| 5591|upnp_context.cpp :541 ] Current preferred protocol [NAT-PMP] IGD [NAT-PMP Gateway 192.168.1.1]
[1615853237.970| 5591|upnp_context.cpp :561 ] Mapping status [TCP] - overall 4: 4 open (4 ready + 0 in use), 0 pending, 0 in-progress, 0 failed
[1615853237.970| 5591|upnp_context.cpp :561 ] Mapping status [UDP] - overall 9: 9 open (8 ready + 1 in use), 0 pending, 0 in-progress, 0 failed
[1615853267.970| 5591|upnp_context.cpp :541 ] Current preferred protocol [NAT-PMP] IGD [NAT-PMP Gateway 192.168.1.1]
[1615853267.970| 5591|upnp_context.cpp :561 ] Mapping status [TCP] - overall 4: 4 open (4 ready + 0 in use), 0 pending, 0 in-progress, 0 failed
[1615853267.970| 5591|upnp_context.cpp :561 ] Mapping status [UDP] - overall 9: 9 open (8 ready + 1 in use), 0 pending, 0 in-progress, 0 failed
[1615853297.970| 5591|upnp_context.cpp :541 ] Current preferred protocol [NAT-PMP] IGD [NAT-PMP Gateway 192.168.1.1]
[1615853297.970| 5591|upnp_context.cpp :561 ] Mapping status [TCP] - overall 4: 4 open (4 ready + 0 in use), 0 pending, 0 in-progress, 0 failed
[1615853297.970| 5591|upnp_context.cpp :561 ] Mapping status [UDP] - overall 9: 9 open (8 ready + 1 in use), 0 pending, 0 in-progress, 0 failed
[1615853327.970| 5591|upnp_context.cpp :541 ] Current preferred protocol [NAT-PMP] IGD [NAT-PMP Gateway 192.168.1.1]
[1615853327.970| 5591|upnp_context.cpp :561 ] Mapping status [TCP] - overall 4: 4 open (4 ready + 0 in use), 0 pending, 0 in-progress, 0 failed
[1615853327.970| 5591|upnp_context.cpp :561 ] Mapping status [UDP] - overall 9: 9 open (8 ready + 1 in use), 0 pending, 0 in-progress, 0 failed
[1615853357.970| 5591|upnp_context.cpp :541 ] Current preferred protocol [NAT-PMP] IGD [NAT-PMP Gateway 192.168.1.1]
[1615853357.970| 5591|upnp_context.cpp :561 ] Mapping status [TCP] - overall 4: 4 open (4 ready + 0 in use), 0 pending, 0 in-progress, 0 failed
[1615853357.970| 5591|upnp_context.cpp :561 ] Mapping status [UDP] - overall 9: 9 open (8 ready + 1 in use), 0 pending, 0 in-progress, 0 failed
[1615853387.970| 5591|upnp_context.cpp :541 ] Current preferred protocol [NAT-PMP] IGD [NAT-PMP Gateway 192.168.1.1]
[1615853387.970| 5591|upnp_context.cpp :561 ] Mapping status [TCP] - overall 4: 4 open (4 ready + 0 in use), 0 pending, 0 in-progress, 0 failed
[1615853387.970| 5591|upnp_context.cpp :561 ] Mapping status [UDP] - overall 9: 9 open (8 ready + 1 in use), 0 pending, 0 in-progress, 0 failed
[1615853417.970| 5591|upnp_context.cpp :541 ] Current preferred protocol [NAT-PMP] IGD [NAT-PMP Gateway 192.168.1.1]
[1615853417.970| 5591|upnp_context.cpp :561 ] Mapping status [TCP] - overall 4: 4 open (4 ready + 0 in use), 0 pending, 0 in-progress, 0 failed
[1615853417.970| 5591|upnp_context.cpp :561 ] Mapping status [UDP] - overall 9: 9 open (8 ready + 1 in use), 0 pending, 0 in-progress, 0 failed
[1615853447.970| 5591|upnp_context.cpp :541 ] Current preferred protocol [NAT-PMP] IGD [NAT-PMP Gateway 192.168.1.1]
[1615853447.970| 5591|upnp_context.cpp :561 ] Mapping status [TCP] - overall 4: 4 open (4 ready + 0 in use), 0 pending, 0 in-progress, 0 failed
[1615853447.970| 5591|upnp_context.cpp :561 ] Mapping status [UDP] - overall 9: 9 open (8 ready + 1 in use), 0 pending, 0 in-progress, 0 failed
[1615853477.970| 5591|upnp_context.cpp :541 ] Current preferred protocol [NAT-PMP] IGD [NAT-PMP Gateway 192.168.1.1]
[1615853477.971| 5591|upnp_context.cpp :561 ] Mapping status [TCP] - overall 4: 4 open (4 ready + 0 in use), 0 pending, 0 in-progress, 0 failed
[1615853477.971| 5591|upnp_context.cpp :561 ] Mapping status [UDP] - overall 9: 9 open (8 ready + 1 in use), 0 pending, 0 in-progress, 0 failed
[1615853507.971| 5591|upnp_context.cpp :541 ] Current preferred protocol [NAT-PMP] IGD [NAT-PMP Gateway 192.168.1.1]
[1615853507.971| 5591|upnp_context.cpp :561 ] Mapping status [TCP] - overall 4: 4 open (4 ready + 0 in use), 0 pending, 0 in-progress, 0 failed
[1615853507.971| 5591|upnp_context.cpp :561 ] Mapping status [UDP] - overall 9: 9 open (8 ready + 1 in use), 0 pending, 0 in-progress, 0 failed
[1615853537.971| 5591|upnp_context.cpp :541 ] Current preferred protocol [NAT-PMP] IGD [NAT-PMP Gateway 192.168.1.1]
[1615853537.971| 5591|upnp_context.cpp :561 ] Mapping status [TCP] - overall 4: 4 open (4 ready + 0 in use), 0 pending, 0 in-progress, 0 failed
[1615853537.971| 5591|upnp_context.cpp :561 ] Mapping status [UDP] - overall 9: 9 open (8 ready + 1 in use), 0 pending, 0 in-progress, 0 failed
[1615853567.971| 5591|upnp_context.cpp :541 ] Current preferred protocol [NAT-PMP] IGD [NAT-PMP Gateway 192.168.1.1]
[1615853567.971| 5591|upnp_context.cpp :561 ] Mapping status [TCP] - overall 4: 4 open (4 ready + 0 in use), 0 pending, 0 in-progress, 0 failed
[1615853567.971| 5591|upnp_context.cpp :561 ] Mapping status [UDP] - overall 9: 9 open (8 ready + 1 in use), 0 pending, 0 in-progress, 0 failed
[1615853597.971| 5591|upnp_context.cpp :541 ] Current preferred protocol [NAT-PMP] IGD [NAT-PMP Gateway 192.168.1.1]
[1615853597.971| 5591|upnp_context.cpp :561 ] Mapping status [TCP] - overall 4: 4 open (4 ready + 0 in use), 0 pending, 0 in-progress, 0 failed
[1615853597.971| 5591|upnp_context.cpp :561 ] Mapping status [UDP] - overall 9: 9 open (8 ready + 1 in use), 0 pending, 0 in-progress, 0 failed
[1615853605.478| 5851|jamiaccount.cpp :2194 ] [Account ae7f47077fe61458] Dht status : IPv4 connected; IPv6 disconnected
[1615853605.955| 5851|jamiaccount.cpp :2194 ] [Account ae7f47077fe61458] Dht status : IPv4 connected; IPv6 connecting
[1615853627.971| 5591|upnp_context.cpp :541 ] Current preferred protocol [NAT-PMP] IGD [NAT-PMP Gateway 192.168.1.1]
[1615853627.971| 5591|upnp_context.cpp :561 ] Mapping status [TCP] - overall 4: 4 open (4 ready + 0 in use), 0 pending, 0 in-progress, 0 failed
[1615853627.971| 5591|upnp_context.cpp :561 ] Mapping status [UDP] - overall 9: 9 open (8 ready + 1 in use), 0 pending, 0 in-progress, 0 failed
[1615853635.264| 5851|jamiaccount.cpp :2194 ] [Account ae7f47077fe61458] Dht status : IPv4 connected; IPv6 disconnected
[1615853636.511| 5851|jamiaccount.cpp :2194 ] [Account ae7f47077fe61458] Dht status : IPv4 connected; IPv6 connecting
```https://git.jami.net/savoirfairelinux/jami-plugins/-/issues/14Fancy hat plugin2021-04-14T15:08:13ZSébastien BlinFancy hat pluginCreate plugin to add accessories like hats, tiaras, glasses, wigs...Create plugin to add accessories like hats, tiaras, glasses, wigs...Aline Gondim SantosAline Gondim Santoshttps://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-client-ios/-/issues/126SIP account: could not detect audio only call2021-03-17T20:10:56ZKateryna KostiukSIP account: could not detect audio only callA video preview is showing for an incoming audio-only callA video preview is showing for an incoming audio-only callhttps://git.jami.net/savoirfairelinux/jami-client-macos/-/issues/276SIP account: sometimes app crash or locked when finishing call2021-03-19T15:21:16ZKateryna KostiukSIP account: sometimes app crash or locked when finishing callhttps://git.jami.net/savoirfairelinux/jami-jams/-/issues/70Replace Statement database management with ORM such as Hibernate2021-03-17T20:17:11ZLarbi GharibReplace Statement database management with ORM such as HibernateAdrien BéraudGuillaume HellerLarbi GharibAdrien Béraudhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/343Conference: dual layout change behaviour with double click2021-04-14T14:27:01ZAline Gondim SantosConference: dual layout change behaviour with double clickWhile we are in conference and double click on a participant video it may change the layout and/or change jami fullscreen status.While we are in conference and double click on a participant video it may change the layout and/or change jami fullscreen status.Ming Rui ZhangMing Rui Zhanghttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1209[FeatureRequest] Communicate between my devices.2021-08-17T20:21:56Zxialvjun[FeatureRequest] Communicate between my devices.It's like https://git.jami.net/savoirfairelinux/ring-project/-/issues/786 , but focus on different things.
I just want my devices of one account can communicate with each other. Just like a device is a contact. Even though device and co...It's like https://git.jami.net/savoirfairelinux/ring-project/-/issues/786 , but focus on different things.
I just want my devices of one account can communicate with each other. Just like a device is a contact. Even though device and contact are different, they can share the same UI.https://git.jami.net/savoirfairelinux/jami-project/-/issues/1210share screen and webcam at the same time2021-07-08T16:36:14ZElysshare screen and webcam at the same timeIt is possible to share your screen during a video call (Android, Windows etc.).
But is it possible to share your screen AND webcam at the same time (without using external software- for example OBS Studio)?
So you can drag the the webc...It is possible to share your screen during a video call (Android, Windows etc.).
But is it possible to share your screen AND webcam at the same time (without using external software- for example OBS Studio)?
So you can drag the the webcam anywhere you want on the shared screen and/or resize the webcam?
Example (found on YouTube): https://youtu.be/4j1KkIcSwX0?t=332
If it is not possible: I submit a feature request.