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

feat: Fast Reconnection #1212

Merged
merged 10 commits into from
Dec 15, 2023
Merged

feat: Fast Reconnection #1212

merged 10 commits into from
Dec 15, 2023

Conversation

oliverlaz
Copy link
Member

Overview

Implements Fast Reconnection flow. This should significantly speed-up the call drop recovery caused by a network switch.

Implementation notes

In case the WebSocket connection interrupts (due to a network switch WiFi -> 5G, or anything else), we'll attempt to re-establish a connection to the existing SFU by reusing the existing credentials and configuration. When this fails, we will attempt a Full Reconnect, and involve the Coordinator in the picture, as we do it today.

@oliverlaz oliverlaz merged commit 88a45e9 into feature/WD-1079 Dec 15, 2023
18 of 21 checks passed
@oliverlaz oliverlaz deleted the fast-reconnects branch December 15, 2023 12:26
oliverlaz added a commit that referenced this pull request Dec 15, 2023
Implements Fast Reconnection flow. This should significantly speed up the call drop recovery caused by a network switch.

### Implementation notes
In case the WebSocket connection interrupts (due to a network switch
WiFi -> 5G, or anything else), we'll attempt to re-establish a
connection to the existing SFU by reusing the existing credentials and
configuration. When this fails, we will attempt a Full Reconnect, and
involve the Coordinator in the picture, as we do it today.
oliverlaz added a commit that referenced this pull request Dec 22, 2023
Implements Fast Reconnection flow. This should significantly speed up
the call drop recovery caused by a network switch.

### Implementation notes
In case the WebSocket connection interrupts (due to a network switch
WiFi -> 5G, or anything else), we'll attempt to re-establish a
connection to the existing SFU by reusing the existing credentials and
configuration. When this fails, we will attempt a Full Reconnect, and
involve the Coordinator in the picture, as we do it today.

### Notes
This PR is a rebase of #1212 against `main`.
oliverlaz added a commit that referenced this pull request Jan 16, 2024
Fixes a regression introduced with #1212 where the status of the
underlying SFU WebSocket was incorrectly checked.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants