Make webrtcHandshakeTimeout and webrtcTrackGatherTimeout configurable #3404
Comments
jwalton
added a commit
to SolinkCorp/mediamtx
that referenced
this issue
May 28, 2024
jwalton
added a commit
to SolinkCorp/mediamtx
that referenced
this issue
May 28, 2024
jwalton
added a commit
to SolinkCorp/mediamtx
that referenced
this issue
May 28, 2024
jwalton
added a commit
to SolinkCorp/mediamtx
that referenced
this issue
May 29, 2024
webrtc: allow configuring timeouts (bluenviron#3404)
aler9
pushed a commit
that referenced
this issue
May 30, 2024
|
fixed by #3406 |
13 tasks
|
This issue is mentioned in release v1.8.3 🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the feature
I'm running into an issue where my WebRTC client is taking a little too long to complete the timeout. We end up hitting the
webrtcHandshakeTimeout, which kills the connection, then my client tries again, but fails again, and we end up in this loop of doom never playing video, but it could be solved if we could bump up the timeout a little.So I'd like to raise a PR to make this configurable, but I'm wondering if you would prefer to see these added to the
Pathstruct (so they could be configured per-path) or to the top levelConfstruct? I'm inclined towards theConfstruct, as it seems unlikely anyone would ever want to configure these path-by-path.The text was updated successfully, but these errors were encountered: