1:1 calls should be completed automatically
How to use GitHub
- Please use the 👍 reaction to show that you are affected by the same issue.
- Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
- Subscribe to receive notifications on status change and new comments.
Steps to reproduce
- Use HPB
- Start a 1:1 conversation in Talk from any device (browser or smartphone).
- Accept the call in Nextcloud Talk on your Android device or iPhone.
- On the first device, end the call. (complete for everyone)
Expected behaviour
The call on the second device should end automatically.
Actual behaviour
The call does not end. After a while, an attempt is made to reconnect to the dialog. P.S.: This behavior is typical only when using HPB. Without HPB, the call ends automatically. If there are more than 2 subscribers in the room, then the call ends automatically for all (when using HPB).
English is not my native language, so please be kind to my mistakes.
Talk app
Talk app version: 17.0.3
Custom Signaling server configured: yes, v. 12de5a9b71afef06eaf171099712ef0a5f6ca0c4
Custom TURN server configured: yes
Custom STUN server configured: yes
Browser
Microphone available: yes
Camera available: yes
Operating system: Windows
Browser name: Chrome
Browser version: 116.0.5845.141
Android App:
Nexcloud Talk Version: v.17.0.2
Server configuration
Nextcloud AIO: 7.0.0 Nextcloud Version: 27.0.2
While I can see usecases for that, for me it also regularly happens with the other expected result regularly. e.g. I finally reach my PC, I hang up on the phone and then join the call on the Browser/Desktop client. It would be quite annoying for the other person if they would have to rejoin the call, just because I switched?
@nickvergessen I mean the situation when one of the users in the browser clicks "End call for everyone". Applies only to call 1:1. In a scenario without a high-performance server, the call ends for all users. If you use a high-performance server, the Android/iOS user will see a loading indicator. After about 7-10 seconds, the Android/IOS client will retry the call. This does not apply to the situation when the user clicks "Leave call" in the browser.
English is not my native language, so please be kind to my mistakes.
Couldn't reproduce with iOS, But reproduced with Android.
So moving there
Agree on proposal