Skip to content
Snippets Groups Projects
New look: Off

Can't receive a call & text after being on the same LAN for about a day.

    • Closed Issue created by rtwin_x @rtwin_x

    Bug report form

    Describe your environment

    Caller side:

    • OS: Windows 10, Version 10.0.19042.928
    • Jami version: Windows QT Beta 202104292750 (Desktop client)
    • On windows with Wired LAN (1000mb/s); i have UPnP On, LocalPeerDiscovery On, DHT-Proxy On, TURN On, STUN On.(default servers settings)

    Receiver side:

    • Android 11, version One UI 3.1, KernelVersion 4.14.190, Galaxy A71, SM-A715F/DS
    • Android Jami (BETA) together 20210421-01
    • On Android phone on LAN via 'Wi-Fi 5G'; i have UPnP Off, LocalPeerDiscovery On, DHT-Proxy On, TURN On, STUN On.(default servers settings)

    Other:

    • Both clients are in the same LAN behind a firewall/router.
    • The Android Phone has been connected to the LAN for 2+ days.

    Steps to reproduce

    • Can you reproduce the bug: often
      3 or 4 times a week, but it takes a while to come into that state again.

    (on windows, the caller) i restarted Jami and started with -D option to catch debug output.
    (on windows) i went to settings and disabled and re-enabled the account, hoping it would refresh and work.
    (on android) i did not change account to off/on, else it re-initializes and the problem is gone.(but bug still there ;)

    • Steps:
    1. On windows, Open Jami.
    2. On android, have the phone connected to LAN for days. Don't switch profile off and on.
    3. On windows, Call a contact which runs on Android.
    • Actual result:
    1. Windows app shows 'calling' and immediately stops with the message "Missed outgoing call"
    2. Android app only sees the message "Missed call"
    • Expected result:
    1. Android app shows incoming call, and user has time to pick up.

    Additional information

    • Calling from Android to Windows can keep ringing and looks Ok.
    • While calling from Windows to Android, the ringing immediately breaks off without doing anything on android. It does ring once on android, and also shows 'missed incoming call'.
    • (on the Android Phone) When i set the profile to off and on, then the Windows client immediately is able to communicate, and also the text messages which didn't come through(sent from that windows client) arrive.
    • This happened in older versions too, where i had to Off/On the profile on Android to get Android client working again. But it seems this problem is there already long, so i file a report.

    Attached is the logs from the Windows client only. it shows calls going both ways. only the calls from windows to android failed immediately. The log contains all info printed from starting to call up-to failing. it fitted in one screen. Sadly i can't perform any debugging on my android company phone.

    Jami_WindowsQT_Beta-202104291750-cant_call_out_Android_receiver_issue_

    In case you need additional info, or need me to try out some things, my jami ID is 'rtwin_x'

    Edited

    Designs

      Child items ...

      2. Activity

      • rtwin_x changed the description

        changed the description

      • rtwin_x changed the description

        changed the description

      • rtwin_x changed the description

        changed the description

      • Elys mentioned in issue jami-project#1395 (closed)

        mentioned in issue jami-project#1395 (closed)

      • rtwin_x
        rtwin_x @rtwin_x ·
        Author

        Hi, I still see the same issue with newer versions.

        i'm using Windows 10 [Version 10.0.19044.1586] Jami QT desktop client - version (BETA) 202203151416 Taranis Settings: localdiscovery=On, Proxy=On(Addr=default),Upnp=On,TURN=On(deafult addr)

        I sent a message from both an

        • FairPhone 3+, e/OS/, Android 10, Jami Taranis 20220121-01,(using WIFI in same lan) and
        • Samsung(Galaxy A71), Android 11, Jami Taranis 20220311-01,(using cellular 4G)

        but the windows client doesnt' receive it.(this happens after a while, maybe an hour or so..) When i turn the Jami account Off and On in Windows/QT client, suddenly it starts receiving the messages which were sent by both Android clients. (i've also seen it the other way around, where my Android phone doesn't receive, and its account needs to be switched off and on again)

        i have this problem for much longer (even before the GIT thing got incorporated). i'll try to get a minimalistic debug-log from the QT client.

        Edited by rtwin_x
      • Elys
        Elys @El4 ·

        To avoid misunderstandings: Your contact details are "Is Swarm: True <-> Is Swarm: True"?

      • rtwin_x
        rtwin_x @rtwin_x ·
        Author

        Good question. i forgot all about that.

        i don't know how to check in Android App. It does nt say in the profile details of the contact in the chat.

        But in the QT Client, it show for the contact in the chat as is Swarm: False :disappointed: (for both android contacts..)

        i thought i attended it a long time ago, by deleting the contacts, and finding them again. I will do that again.

        --

        Just now, i deleted the contact on both Qt-client(Win10) and Android-client(FP3 phone). Searched the contact on Qt-client, and sent a text.

        Then on Android-client i got a connection request, to which i pressed "accept". And now it keeps saying "downloading conversation from peer". After minutes nothing has changed.

        Then on the Android-client, i switched of WIFI so it only had 4G, and nothing changed. So, seconds after that, i went into my profile settings to set my profile offline and online again. That's when the "downloading conversation from peer" went away, and my message i sent from Qt-client appeared.

        Now, in my Android-client, in the chat, on the profile-details i see a message "(i) Private swarm". As well as on the chat-profile details on the Qt-client it says 'is Swarm: True'

        (Again that off/online toggle on the receiver end was required :/ ) I will check if anything changed:thumbsup:

        Edited by rtwin_x
      • Elys
        Elys @El4 ·

        Just wanted to add the following topic: jami-project#1389 (closed)

      • rtwin_x
        rtwin_x @rtwin_x ·
        Author

        @El4 i have a fresh log of the timespan in which it went from receiving to not being able to receive a text message. Maybe it is helpful?

        i'm using the following setup:

        1. Windows 10 [Version 10.0.19044.1586]
        • Jami QT dekstop client - version (BETA) 202203171723 Taranis
        • Settings: localdiscovery=On, Proxy=On(Addr=default),Upnp=On,TURN=On(deafult addr)
        • Connected via LAN and WIFI
        1. Samsung A71, Android 11,
        • Jami Taranis 2022-0311-01(Beta tester via GooglePlayStore)
        • Settings same as windows.
        • Connected via cellular 4G.
        1. Router has UPnP enabled. Version Ziggo "Connect Box"
        • Conform standaard specificaties : DOCSIS 3.0
        • Hardware versie : 5.01
        • Software versie : CH7465LG-NCIP-6.15.31p1-NOSH

        I have multiple identities setup in the windows Qt client(5 in total. None are used) For the sake the next test, i removed all conversations for all identities. I confirmed for the below conversation, swarm:true.

        In the logs just before this point, Android sent "17:00" to QT, and Qt received.

        [1647619337.796|13832|jamiaccount.cpp   :2036 ] [Account 01ff----------f05b3] Dht status: IPv4 connecting; IPv6 connected
[1647619346.124|13832|jamiaccount.cpp   :2036 ] [Account 01ff----------f05b3] Dht status: IPv4 disconnected; IPv6 connected
[1647619354.772|13832|jamiaccount.cpp   :2036 ] [Account 01ff----------f05b3] Dht status: IPv4 connecting; IPv6 connected
[1647619364.825|13832|jamiaccount.cpp   :2036 ] [Account 01ff----------f05b3] Dht status: IPv4 disconnected; IPv6 connected
[1647619369.357|13832|jamiaccount.cpp   :2036 ] [Account 01ff----------f05b3] Dht status: IPv4 connecting; IPv6 connected
[1647619386.302|13832|jamiaccount.cpp   :2036 ] [Account 01ff----------f05b3] Dht status: IPv4 disconnected; IPv6 connected
[1647619386.413|13832|jamiaccount.cpp   :2036 ] [Account 01ff----------f05b3] Dht status: IPv4 connecting; IPv6 connected
[1647619394.949|13832|jamiaccount.cpp   :2036 ] [Account 01ff----------f05b3] Dht status: IPv4 disconnected; IPv6 connected
[1647619395.578|13832|jamiaccount.cpp   :2036 ] [Account 01ff----------f05b3] Dht status: IPv4 connecting; IPv6 connected
[1647619413.166|13832|jamiaccount.cpp   :2036 ] [Account 01ff----------f05b3] Dht status: IPv4 disconnected; IPv6 connected
[1647619414.649|13832|jamiaccount.cpp   :2036 ] [Account 01ff----------f05b3] Dht status: IPv4 connecting; IPv6 connected
[1647619431.855|13832|jamiaccount.cpp   :2036 ] [Account 01ff----------f05b3] Dht status: IPv4 disconnected; IPv6 connected
[1647619432.159|13832|jamiaccount.cpp   :2036 ] [Account 01ff----------f05b3] Dht status: IPv4 connecting; IPv6 connected
[1647619492.433|13832|jamiaccount.cpp   :2036 ] [Account 01ff----------f05b3] Dht status: IPv4 disconnected; IPv6 connected
[1647619492.857|13832|jamiaccount.cpp   :2036 ] [Account 01ff----------f05b3] Dht status: IPv4 connecting; IPv6 connected
[1647619524.500|13832|jamiaccount.cpp   :2036 ] [Account 01ff----------f05b3] Dht status: IPv4 disconnected; IPv6 connected
[1647619524.505|13832|jamiaccount.cpp   :2036 ] [Account 01ff----------f05b3] Dht status: IPv4 connecting; IPv6 connected
[1647619585.770|13832|jamiaccount.cpp   :2036 ] [Account 01ff----------f05b3] Dht status: IPv4 disconnected; IPv6 connected
[1647619938.694|13832|jamiaccount.cpp   :2036 ] [Account 01ff----------f05b3] Dht status: IPv4 connecting; IPv6 connected
[1647619947.427|13832|jamiaccount.cpp   :2036 ] [Account 01ff----------f05b3] Dht status: IPv4 disconnected; IPv6 connected
[1647619949.627|13832|jamiaccount.cpp   :2036 ] [Account 01ff----------f05b3] Dht status: IPv4 connecting; IPv6 connected
[1647619972.673|13832|jamiaccount.cpp   :2036 ] [Account 01ff----------f05b3] Dht status: IPv4 disconnected; IPv6 connected
[1647619973.003|13832|jamiaccount.cpp   :2036 ] [Account 01ff----------f05b3] Dht status: IPv4 connecting; IPv6 connected
[1647620052.670|13832|jamiaccount.cpp   :2036 ] [Account 01ff----------f05b3] Dht status: IPv4 disconnected; IPv6 connected
[1647620052.722|13832|jamiaccount.cpp   :2036 ] [Account 01ff----------f05b3] Dht status: IPv4 connecting; IPv6 connected
[1647620062.480|13832|jamiaccount.cpp   :2036 ] [Account 01ff----------f05b3] Dht status: IPv4 disconnected; IPv6 connected
[1647620062.871|13832|jamiaccount.cpp   :2036 ] [Account 01ff----------f05b3] Dht status: IPv4 connecting; IPv6 connected
[1647620174.098|13832|jamiaccount.cpp   :2036 ] [Account 01ff----------f05b3] Dht status: IPv4 disconnected; IPv6 connected
[1647620537.921|13832|jamiaccount.cpp   :2036 ] [Account 01ff----------f05b3] Dht status: IPv4 connecting; IPv6 connected
[1647620556.260|13832|jamiaccount.cpp   :2036 ] [Account 01ff----------f05b3] Dht status: IPv4 disconnected; IPv6 connected
[1647620556.512|13832|jamiaccount.cpp   :2036 ] [Account 01ff----------f05b3] Dht status: IPv4 connecting; IPv6 connected
[1647620625.303|13832|jamiaccount.cpp   :2036 ] [Account 01ff----------f05b3] Dht status: IPv4 disconnected; IPv6 connected
[1647620628.285|13832|jamiaccount.cpp   :2036 ] [Account 01ff----------f05b3] Dht status: IPv4 connecting; IPv6 connected
[1647620755.197|13832|jamiaccount.cpp   :2036 ] [Account 01ff----------f05b3] Dht status: IPv4 disconnected; IPv6 connected
[1647622946.067|13832|jamiaccount.cpp   :2036 ] [Account 01ff----------f05b3] Dht status: IPv4 connecting; IPv6 connected
[1647622955.843|13832|jamiaccount.cpp   :2036 ] [Account 01ff----------f05b3] Dht status: IPv4 disconnected; IPv6 connected
[1647622956.585|13832|jamiaccount.cpp   :2036 ] [Account 01ff----------f05b3] Dht status: IPv4 connecting; IPv6 connected
[1647622965.856|13832|jamiaccount.cpp   :2036 ] [Account 01ff----------f05b3] Dht status: IPv4 disconnected; IPv6 connected
[1647622966.458|13832|jamiaccount.cpp   :2036 ] [Account 01ff----------f05b3] Dht status: IPv4 connecting; IPv6 connected
[1647622975.146|13832|jamiaccount.cpp   :2036 ] [Account 01ff----------f05b3] Dht status: IPv4 disconnected; IPv6 connected
[1647622975.851|13832|jamiaccount.cpp   :2036 ] [Account 01ff----------f05b3] Dht status: IPv4 connecting; IPv6 connected
[1647622985.089|13832|jamiaccount.cpp   :2036 ] [Account 01ff----------f05b3] Dht status: IPv4 disconnected; IPv6 connected
[1647622985.766|13832|jamiaccount.cpp   :2036 ] [Account 01ff----------f05b3] Dht status: IPv4 connecting; IPv6 connected
[1647623002.611|13832|jamiaccount.cpp   :2036 ] [Account 01ff----------f05b3] Dht status: IPv4 disconnected; IPv6 connected
[1647623003.038|13832|jamiaccount.cpp   :2036 ] [Account 01ff----------f05b3] Dht status: IPv4 connecting; IPv6 connected
[1647623032.832|13832|jamiaccount.cpp   :2036 ] [Account 01ff----------f05b3] Dht status: IPv4 disconnected; IPv6 connected
[1647623033.760|13832|jamiaccount.cpp   :2036 ] [Account 01ff----------f05b3] Dht status: IPv4 connecting; IPv6 connected
[1647623057.328|13832|jamiaccount.cpp   :2036 ] [Account 01ff----------f05b3] Dht status: IPv4 disconnected; IPv6 connected
[1647623060.287|13832|jamiaccount.cpp   :2036 ] [Account 01ff----------f05b3] Dht status: IPv4 connecting; IPv6 connected
[1647623112.826|13832|jamiaccount.cpp   :2036 ] [Account 01ff----------f05b3] Dht status: IPv4 disconnected; IPv6 connected
[1647623114.402|13832|jamiaccount.cpp   :2036 ] [Account 01ff----------f05b3] Dht status: IPv4 connecting; IPv6 connected
[1647623150.931|13832|jamiaccount.cpp   :2036 ] [Account 01ff----------f05b3] Dht status: IPv4 disconnected; IPv6 connected
[1647624245.067|13832|jamiaccount.cpp   :2036 ] [Account 01ff----------f05b3] Dht status: IPv4 connecting; IPv6 connected
[1647624262.912|13832|jamiaccount.cpp   :2036 ] [Account 01ff----------f05b3] Dht status: IPv4 disconnected; IPv6 connected
[1647624266.157|13832|jamiaccount.cpp   :2036 ] [Account 01ff----------f05b3] Dht status: IPv4 connecting; IPv6 connected
[1647624275.024|13832|jamiaccount.cpp   :2036 ] [Account 01ff----------f05b3] Dht status: IPv4 disconnected; IPv6 connected
[1647624275.496|13832|jamiaccount.cpp   :2036 ] [Account 01ff----------f05b3] Dht status: IPv4 connecting; IPv6 connected
[1647624286.749|13832|jamiaccount.cpp   :2036 ] [Account 01ff----------f05b3] Dht status: IPv4 disconnected; IPv6 connected
[1647624289.244|13832|jamiaccount.cpp   :2036 ] [Account 01ff----------f05b3] Dht status: IPv4 connecting; IPv6 connected
[1647624306.044|13832|jamiaccount.cpp   :2036 ] [Account 01ff----------f05b3] Dht status: IPv4 disconnected; IPv6 connected
[1647624307.205|13832|jamiaccount.cpp   :2036 ] [Account 01ff----------f05b3] Dht status: IPv4 connecting; IPv6 connected
[1647624379.186|13832|jamiaccount.cpp   :2036 ] [Account 01ff----------f05b3] Dht status: IPv4 disconnected; IPv6 connected
[1647624380.484|13832|jamiaccount.cpp   :2036 ] [Account 01ff----------f05b3] Dht status: IPv4 connecting; IPv6 connected
[1647624399.171|13832|jamiaccount.cpp   :2036 ] [Account 01ff----------f05b3] Dht status: IPv4 disconnected; IPv6 connected
[1647624399.340|13832|jamiaccount.cpp   :2036 ] [Account 01ff----------f05b3] Dht status: IPv4 connecting; IPv6 connected
[1647624474.094|13832|jamiaccount.cpp   :2036 ] [Account 01ff----------f05b3] Dht status: IPv4 disconnected; IPv6 connected
[1647624485.097|13832|jamiaccount.cpp   :2036 ] [Account 01ff----------f05b3] Dht status: IPv4 connecting; IPv6 connected
[1647624502.079|13832|jamiaccount.cpp   :2036 ] [Account 01ff----------f05b3] Dht status: IPv4 disconnected; IPv6 connected
[1647624503.606|13832|jamiaccount.cpp   :2036 ] [Account 01ff----------f05b3] Dht status: IPv4 connecting; IPv6 connected
[1647624530.320|13832|jamiaccount.cpp   :2036 ] [Account 01ff----------f05b3] Dht status: IPv4 disconnected; IPv6 connected
[1647624531.059|13832|jamiaccount.cpp   :2036 ] [Account 01ff----------f05b3] Dht status: IPv4 connecting; IPv6 connected
[1647624539.886|13832|jamiaccount.cpp   :2036 ] [Account 01ff----------f05b3] Dht status: IPv4 disconnected; IPv6 connected
[1647624546.826|13832|jamiaccount.cpp   :2036 ] [Account 01ff----------f05b3] Dht status: IPv4 connecting; IPv6 connected
[1647624591.264| 9348|multiplexed_socket.cpp:210  ] Tls endpoint is down, shutdown multiplexed socket
[1647624591.269| 9348|tls_session.cpp   :1543 ] [TLS] shutdown
[1647624591.279| 9348|ice_transport.cpp :1716 ] [ice:0000017BA626FA90] ice send failed: Not found (PJ_ENOTFOUND)
[1647624591.287| 9348|tls_session.cpp   :897  ] [1647624591.287|14836|ice_transport.cpp :316  ] [TLS] transport failure on tx: errno = 5
[ice:0000017BA626FA90] destroying 0000017B9F2000A8
[1647624591.777|14836|ice_transport.cpp :331  ] [ice:0000017BA626FA90] Destroying ice_strans 0000017B9F2000A8
[1647624592.288|14836|ice_transport.cpp :649  ] [ice:0000017BA626FA90] Timer heap flushed after 503 ms
[1647624592.290|14836|ice_transport.cpp :363  ] [ice:0000017BA626FA90] done destroying
[1647624593.093| 6868|multiplexed_socket.cpp:210  ] Tls endpoint is down, shutdown multiplexed socket
[1647624593.099| 6868|channeled_transport.cpp:187  ] [SIPS] process disconnect event
[1647624593.104| 6868|siptransport.cpp  :201  ] pjsip transport@0000017BA66D7100 TLS to 109.37.136.14 -> DISCONNECTED
[1647624593.108| 6868|siptransport.cpp  :97   ] ~SipTransport@0000017BA81011B0 {tr=0000017BA66D7100 {rc=1}}
[1647624593.116| 6868|tls_session.cpp   :1543 ] [TLS] shutdown
[1647624593.128| 6868|ice_transport.cpp :1716 ] [ice:0000017BABEE1BF0] ice send failed: Not found (PJ_ENOTFOUND)
[1647624593.130| 6868|tls_session.cpp   :897  ] [1647624593.130|16556|ice_transport.cpp :316  ] [TLS] transport failure on tx: errno = 5
[ice:0000017BABEE1BF0] destroying 0000017BA9D308F8
[1647624593.594|16556|ice_transport.cpp :331  ] [ice:0000017BABEE1BF0] Destroying ice_strans 0000017BA9D308F8
[1647624593.608| 7896|multiplexed_socket.cpp:210  ] Tls endpoint is down, shutdown multiplexed socket
[1647624593.616| 7896|tls_session.cpp   :1543 ] [TLS] shutdown[1647624593.616|15584|gitserver.cpp     :478  ]
GitServer destroyed
[1647624593.619| 7896|ice_transport.cpp :1716 ] [ice:0000017B9238D400] ice send failed: Not found (PJ_ENOTFOUND)
[1647624593.622| 7896|tls_session.cpp   :897  ] [1647624593.622|14836|ice_transport.cpp :316  ] [TLS] transport failure on tx: errno = 5
[ice:0000017B9238D400] destroying 0000017BAB9B8258
[1647624594.107|16556|ice_transport.cpp :649  ] [ice:0000017BABEE1BF0] Timer heap flushed after 506 ms
[1647624594.113|16556|ice_transport.cpp :363  ] [ice:0000017BABEE1BF0] done destroying
[1647624594.123|14836|ice_transport.cpp :331  ] [ice:0000017B9238D400] Destroying ice_strans 0000017BAB9B8258
[1647624594.632|14836|ice_transport.cpp :649  ] [ice:0000017B9238D400] Timer heap flushed after 501 ms
[1647624594.634|14836|ice_transport.cpp :363  ] [ice:0000017B9238D400] done destroying
[1647624596.120| 9120|siptransport.cpp  :201  ] pjsip transport@0000017BA66D7100 TLS to 109.37.136.14 -> DESTROY
[1647624596.126| 9120|siptransport.cpp  :220  ] unmap pjsip transport@0000017BA66D7100 {SipTransport@0000000000000000}
[1647624596.132| 9120|channeled_transport.cpp:129  ] ChanneledSIPTransport@0000017BA66D7070: destroying
[1647624596.143| 9120|channeled_transport.cpp:199  ] ~ChanneledSIPTransport@0000017BA66D7070 {tr=0000017BA66D7100}
[1647624596.150| 9120|channeled_transport.cpp:216  ] ~ChanneledSIPTransport@0000017BA66D7070 {tr=0000017BA66D7100} bye
[1647624642.819|13832|jamiaccount.cpp   :2036 ] [Account 01ff----------f05b3] Dht status: IPv4 disconnected; IPv6 connected
[1647624643.857|13832|jamiaccount.cpp   :2036 ] [Account 01ff----------f05b3] Dht status: IPv4 connecting; IPv6 connected
[1647624700.243|13832|jamiaccount.cpp   :2036 ] [Account 01ff----------f05b3] Dht status: IPv4 disconnected; IPv6 connected

        Above, i did do nothing just waited.(but there it went into non-receptive state..)

        <nothing in the log>

        Above, sent message "21:20" from Android to Qt, but nothing happens on Qt side

        Then i switched off WIFI at Qt-side. now only wired LAN exists.

        Then a lot happened in the log, but Qt client didn't receive the message

        Then i switched Off wired LAN at Qt-side

        Then i switched On wired LAN at Qt-side. And i did receive the message of "21:20" at Qt-side

      • Sébastien Blin
        Sébastien Blin @sblin ·
        Owner

        There was changes for connectivity changes, so it should be fixed.

      • Sébastien Blin closed

        closed

      Please register or sign in to reply