rzerres/element-call
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Experiment with different timeouts

Browse Source 
This lets you set the global variables peerConnectionTimeout and websocketTimeout to see what LiveKit does with different values.
This commit is contained in:
Robin
2024-04-09 10:06:34 -04:00
parent 03d2818c1f
commit 51cc406af7
1 changed files with 13 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
src/livekit/useECConnectionState.ts
View File

@@ -28,6 +28,13 @@ import * as Sentry from "@sentry/react";
import { SFUConfig, sfuConfigEquals } from "./openIDSFU"; import { SFUConfig, sfuConfigEquals } from "./openIDSFU";
declare global {
interface Window {
peerConnectionTimeout?: number;
websocketTimeout?: number;
}
}
/* /*
* Additional values for states that a call can be in, beyond what livekit * Additional values for states that a call can be in, beyond what livekit
* provides in ConnectionState. Also reconnects the call if the SFU Config * provides in ConnectionState. Also reconnects the call if the SFU Config
@@ -124,7 +131,12 @@ async function connectAndPublish(
micTrack: LocalTrack | undefined, micTrack: LocalTrack | undefined,
screenshareTracks: MediaStreamTrack[], screenshareTracks: MediaStreamTrack[],
): Promise<void> { ): Promise<void> {
await livekitRoom!.connect(sfuConfig!.url, sfuConfig!.jwt); await livekitRoom!.connect(sfuConfig!.url, sfuConfig!.jwt, {
// Due to stability issues on Firefox we are testing the effect of different
// timeouts, and allow these values to be set through the console
peerConnectionTimeout: window.peerConnectionTimeout ?? 45000,
websocketTimeout: window.websocketTimeout ?? 45000,
});
if (micTrack) { if (micTrack) {
logger.info(`Publishing precreated mic track`); logger.info(`Publishing precreated mic track`);