First call: "Searching" remains if the Android contact is called after JUST the Android contact disables and enables (again) his own account (only useraccount1 -> useraccount2?)

using Jami (Windows 10 -> Android; useraccount1 -> useraccount2), different network

EDIT: I think I didn't reproduce if I make a call sameuseraccount -> sameuseraccount if the Android user enables his account very quickly again - however if the Android user waits one minute or even longer and THEN enables his account again I get the "Connecting" issue jami-project#1513 (closed) (at least after I repeat these steps the second time: Open Jami (Windows 10 and Android); Wait a few seconds; Now just the Android user disables his own account and waits two minutes or even longer; Now the Android user enables his own account; Same steps: The Android user disables his own account and waits two minutes; Now the Android user enables his own account: This time a call sameuseraccount(windows 10) -> sameuseraccount(android) will stuck in "Connecting")

You have to make a call useraccount1 -> useraccount2 if the Android user immediately enables his account

Mixed:

• If I first make a call sameuseraccount(windows 10) -> sameuseraccount(android) everything works
• Now I disable (Windows 10) sameuseraccount(windows 10) and enable the other account (useraccount1 (windows 10)) so I can make a call useraccount1 (Windows 10) -> useraccount2 (Android)
• Still same issue (although sameuseraccount(windows 10) -> sameuseraccount(android) does not have any issues?)

Maybe also related: jami-project#1513 (closed)

ALWAYS DISABLE "run in background"

Steps to reproduce:

1. Windows 10: (=useraccount1) You've already opened Jami and keep Jami running
2. Android (=useraccount2) Open Jami
3. Now the Windows 10 user will view the green dot of the Android user in the contact list
4. Now just the Android user disables his own account
5. Now just the Android user enables his own account
6. BEFORE the Android user views the green dot of (all) his contacts in the contact list the Windows 10 user tries to make a call (Windows 10 -> Android)
7. Windows 10: The call will be stuck at "Searching" (it won't fail? - it won't work?; even after a minute; even if the Android user now views the green dot of all contacts)

Sometimes after some time you'll get missed outgoing call (in that case Windows 10).

Same issue if you immediately make a first call (Windows 10 -> Android) if the Android user views the green dot of the Windows 10 user in the contact list

However - the next calls will work?

EDIT: I think this is not (only) a timing issue but an issue because (just) the Android user disabled (and now enables) his own account.

No issues if you make a call Android -> Windows 10. (Remember you never disabled the Windows 10 Jami account)

EDIT 2: If the Windows 10 user also disables his own account and enables his account again I think this issue does NOT happen? (Not sure - I also had this issue if the Windows 10 user disables and enables his account?)

changed the description

changed title from "Searching" remains if the contact is called before the green dot is visible again to "Searching" remains if the contact is called before or shortly after the green dot is visible again

changed the description

changed title from "Searching" remains if the contact is called before or shortly after the green dot is visible again to First call: "Searching" remains if the Android contact is called after the Android contact reenables his own account

changed title from First call: "Searching" remains if the Android contact is called after the Android contact reenables his own account to First call: "Searching" remains if the Android contact is called after JUST the Android contact reenables his own account

changed the description

changed the description

changed title from First call: "Searching" remains if the Android contact is called after JUST the Android contact reenables his own account to First call: "Searching" remains if the Android contact is called after JUST the Android contact enables and disables his own account

added natureto determine label

assigned to @sblin

changed title from First call: "Searching" remains if the Android contact is called after JUST the Android contact enables and disables his own account to First call: "Searching" remains if the Android contact is called after JUST the Android contact disables and enables (again) his own account

mentioned in issue jami-project#1513 (closed)

changed the description

changed title from First call: "Searching" remains if the Android contact is called after JUST the Android contact disables and enables (again) his own account to First call: "Searching" remains if the Android contact is called after JUST the Android contact disables and enables (again) his own account (only useraccount1 -> useraccount2?)

changed the description

changed the description

changed the description

changed the description

removed natureto determine label

added typebug + 1 deleted label

So actually you should reproduce

useraccount 1 -> useraccount 2 even if you immediately enable/disable the account

sameuseraccount -> sameuseraccount if you wait ~2 minutes?

Can you also try to reproduce: jami-project#1513 (closed)

mentioned in issue jami-client-android#1150 (closed)

Steps to reproduce:


        
      Windows 10: (=useraccount1) You've already opened Jami and keep Jami running

        
      Android (=useraccount2) Open Jami

        
      Now the Windows 10 user will view the green dot of the Android user in the contact list

        
      Now just the Android user disables his own account

        
      Now just the Android user enables his own account

        
      BEFORE the Android user views the green dot of (all) his contacts in the contact list the Windows 10 user tries to make a call (Windows 10 -> Android)

        
      Windows 10: The call will be stuck at "Searching" (it won't fail? - it won't work?; even after a minute; even if the Android user now views the green dot of all contacts)

I tried 50 times without a single failure on several devices since last patches (both sides with version >= 20221220). If you can confirm. (else provide logs + 1 scenario (please not more, to reproduce it takes ~1h each time (setup/reproduce/confirm/get logs)))

Just reproduced the following issue (again?):

Windows 10: 202211101600

Android: 20221207-01

sameuseraccount (Windows 10) -> sameuseraccount (Android); different network,

1. Open Jami (Windows 10)
2. Now Open Jami (Android)
3. Now the Windows 10 user views the green dot of the Android user
4. Now make a call Windows 10 -> Android
5. Now exit the call
6. Now just the Android user disables his account (the Windows 10 user will still view a green dot of the contact)
7. Now just the Android user enables his account again

issue:

If the Windows user makes a call at the same time or shortly (less than 3 seconds) after the Android user enabled his account Jami will stuck "Searching" and this state will remain forever or sometimes it will disappear after one minute?

If just the Windows 10 user stops the "Searching" bar sometimes even the next calls Windows 10 -> Android will fail

version >= 20221220

You mean the Android version?

https://review.jami.net/c/jami-client-android/+/23464

Can you reproduce for example Windows 10 <-> Windows 10?

https://dl.jami.net/windows/

Otherwise I have to wait for new update...

I did some tests:

I could NEVER reproduce if the android phone uses the hotspot of Windows 10 (and the same network; TURN disabled, both devices "Enable local peer discovery")

EDIT: Now I use two different networks again (I exit both apps before).

I saw that I didn't enable TURN just on the android phone (generally: before (different network), after (same network) and now (different network). (If I used different networks Jami on Windows 10 always used the TURN server).

Maybe this is the issue? But at the moment I can't reproduce anymore...

But the first call (Windows 10 -> Android) always worked as long as I didn't disable (and enable again) the Android account?

without turn or upnp, there will be no connection or a lot of failures for sure

Upnp was never enabled (neither Jami on Windows 10 nor Android; but "Enable local peer discovery" (both devices); although I mostly used different networks - so it shouldn't be relevant?)

Although I still disabled turn (JUST ANDROID) but enabled turn on Jami Windows 10 I now can't reproduce at the moment

I can even make calls Android -> Windows 10

I was able to reproduce the same= issue?

sameuseraccount (Windows 10) -> sameuseraccount (Android); different network,

BOTH enabled turn:

Launch Jami (Android & Windows 10) Make a call Windows 10 -> Android Jami will stuck "Connecting" and will fail

Logs: Windows 10:

(I just replaced Account with 1234

[1671632524.839|20788|ringbuffer.cpp          :55  ] Create new RingBuffer 8322997200105101
[1671632524.892|20220|ringbuffer.cpp          :55  ] Create new RingBuffer 5222483135054545
[1671632524.892|20220|jamiaccount.cpp         :603 ] [call 8322997200105101] A channeled socket is detected with this peer.
[1671632524.893|20220|ringbuffer.cpp          :55  ] Create new RingBuffer 3729259888580096
[1671632524.899|20220|ringbuffer.cpp          :55  ] Create new RingBuffer 7690673354527590
[1671632524.899|20220|jamiaccount.cpp         :576 ] [call 8322997200105101] No channeled socket with this peer. Send request
[1671632524.899|20220|jamiaccount.cpp         :3930] [Account 1234 ] Ask a1b193d2098cae6ea30fe00c4a1921c11ce01a3b8ac791370749a9491743aef9 for a new SIP channel
[1671632524.899|2212|call.cpp                :523 ] [call:8322997200105101] subcall 7690673354527590 failed
[1671632524.900|2212|ringbufferpool.cpp      :262 ] Unbind call 7690673354527590 from all bound calls
[1671632524.900|2212|call.cpp                :523 ] [call:8322997200105101] subcall 5222483135054545 failed
[1671632524.900|2212|ringbufferpool.cpp      :262 ] Unbind call 5222483135054545 from all bound calls
[1671632526.800|11856|media_decoder.cpp       :563 ] Not using hardware decoding for rawvideo
[1671632527.897|2212|channeled_transport.cpp :186 ] [SIPS] process disconnect event
[1671632527.897|2212|sipcall.cpp             :494 ] [call:3729259888580096] Ending call because underlying SIP transport was closed
[1671632527.897|2212|gitserver.cpp           :478 ] GitServer destroyed
[1671632527.897|2212|gitserver.cpp           :478 ] GitServer destroyed
[1671632527.897|2212|gitserver.cpp           :478 ] GitServer destroyed
[1671632527.897|2212|gitserver.cpp           :478 ] GitServer destroyed
[1671632527.898|2212|gitserver.cpp           :478 ] GitServer destroyed
[1671632527.898|2212|gitserver.cpp           :478 ] GitServer destroyed
[1671632527.898|2212|call.cpp                :523 ] [call:8322997200105101] subcall 3729259888580096 failed
[1671632527.898|2212|ringbufferpool.cpp      :262 ] Unbind call 3729259888580096 from all bound calls
[1671632527.898|2212|ringbuffer.cpp          :60  ] Destroy RingBuffer 3729259888580096
[1671632527.927|18496|conversationrepository.cpp:1733] New message added with id: 9525fb34dd3e83c28c39fb4dc8f0eabb196780b6
[1671632528.264|20084|ice_transport.cpp       :352 ] [ice:0000019668305070] Destroying ice_strans 0000019676804CA8
[1671632528.311|10844|ice_transport.cpp       :352 ] [ice:000001967533C0E0] Destroying ice_strans 00000196756C6D88
[1671632542.172|2212|jamiaccount.cpp         :3404] Timeout when send a message, close current connection
 

mentioned in issue jami-project#1395 (closed)

unassigned @sblin

added severityhigh label

moved from jami-project#1512 (moved)