Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[stable16] Fix status not kept after forced reconnections #1827

Merged
merged 2 commits into from
May 16, 2019

Conversation

backportbot-nextcloud[bot]
Copy link

backport of #1824

danxuliu added 2 commits May 16, 2019 08:03
When a reconnection is forced the call is left and then joined again. In
that case the initial adjustments done when joining a call should not be
done again.

Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
When joining a call again due to a forced reconnection the same flags
used when originally joining the call should be provided again;
otherwise, if no flags are provided, the default flags would be used by
the server, which may not match the real call flags.

Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
@backportbot-nextcloud backportbot-nextcloud bot added bug feature: frontend 🖌️ "Web UI" client feature: signaling 📶 Internal and external signaling backends labels May 16, 2019
@backportbot-nextcloud backportbot-nextcloud bot added this to the 💙 Next Minor (16) milestone May 16, 2019
@nickvergessen nickvergessen merged commit 81f7d89 into stable16 May 16, 2019
@nickvergessen nickvergessen deleted the backport/1824/stable16 branch May 16, 2019 09:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug feature: frontend 🖌️ "Web UI" client feature: signaling 📶 Internal and external signaling backends
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants