You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
webrtc transport produces lots of warning logs, that might indicate non-working transport:
2024-08-19T13:04:01.017+0200 INFO webrtc-transport-pion v3@v3.2.50/peerconnection.go:489 peer connection state changed: connected
2024-08-19T13:04:01.017+0200 INFO webrtc-transport-pion v3@v3.2.50/peerconnection.go:489 peer connection state changed: failed
2024-08-19T13:04:01.017+0200 WARN webrtc-transport-pion v3@v3.2.50/peerconnection.go:2320 Failed to start manager: remote certificate does not match any fingerprint
2024-08-19T13:04:01.017+0200 WARN webrtc-transport-pion v3@v3.2.50/peerconnection.go:1465 Failed to start SCTP: DTLS not established
2024-08-19T13:04:01.017+0200 WARN webrtc-transport-pion v3@v3.2.50/peerconnection.go:1734 undeclaredMediaProcessor failed to open SrtcpSession: the DTLS transport has not started yet
Need to investigate implication of failed DTLS transport.
The text was updated successfully, but these errors were encountered:
Implementation ideas
webrtc transport produces lots of warning logs, that might indicate non-working transport:
Need to investigate implication of failed DTLS transport.
The text was updated successfully, but these errors were encountered: