Get desktop application:
View/edit binary Protocol Buffers messages
Reported connectivity of client network
(message has no fields)
Used in:
Connectivity status is unspecified.
Connectivity to ICE servers is unimpaired.
Connectivity to ICE servers is possibly blocked.
ICE server configuration. Each configuration is ephemeral and should not be shared across WebRTC peer connections or cached for later use.
Duration the config is valid for.
ICE servers to be used by the client to establish a connection. E.g.: [ { "urls": "stun:stun1.example.net" }, { "urls": "turn:turn.example.org", "username": "user", "credential": "myPassword" } ]
Corresponds to: https://www.w3.org/TR/webrtc/#rtcicetransportpolicy-enum The recommended ICE transport policy to use in the RTC configuration.
Possible detected network provider interference with ice_servers connectivity. This is an estimation which might be inaccurate.
Extra ice servers that can be present when block_status indicates POSSIBLY_BLOCKED and which might be able to provide better connectivity than ice_servers in that scenario. However the network quality is likely to be strictly worse. Applications are recommended to use these servers instead of ice_servers to be robust against blocking. However these ice servers also currently requires applications to disable TLS validation. This is because TURNS is used for obfuscation instead of security, and no valid certificate is returned since valid certificates can be blocked.
Extra optional configuration for unblocking purposes.
ICE Server configuration based on the RTCIceServer type in the WebRTC W3C specification: https://www.w3.org/TR/webrtc/#rtciceserver-dictionary.
Used in:
STUN or TURN URI(s) as defined in [rfc7064] and [rfc7065] or other URI types.
If this IceServer object represents a TURN server, then this attribute specifies the credential to use with that TURN server.
If this IceServer object represents a TURN server, then this attribute specifies the credential to use with that TURN server.
The TLS certificate policy to use for TLS urls.
If the URIs in urls only contain IP addresses, this field can be used to indicate the hostname. If specified, it should be used for TLS SNI and certificate validation for any applicable URLs. For urls that themselves contains the hostname, this can be ignored.
List of protocols to be used in the TLS ALPN extension.
List of elliptic curves to be used in the TLS elliptic curves extension. Only curves supported by OpenSSL should be used (e.g. "P-256", "X25519").
Setting for STUN alternative magic cookie.
Maximum rate in kilobits per second (kilo = 1000). Can be used as hint to the bandwidth estimator to improve media quality. If less than or equal to zero, the maximum send rate is not specified.
Setting for StunAltMagic.
(message has no fields)
Used in:
Use default.
Use normal stun magic.
Use stun alt magic.
TLS certificate policy.
(message has no fields)
Used in:
For TLS based protocols, ensure the connection is secure by not circumventing certificate validation. This is the default and should be used when unspecified.
For TLS based protocols, disregard security completely by skipping certificate validation. This is insecure and should never be used unless security is irrelevant in that particular context.
Extra unblocking configuration.
Used in:
Minimum length to pad STUN messages.
Maximum length to pad STUN messages.
The minimum payload size of channel data. Smaller messages should be sent as TURN send indications. Since channel data messages are not easily padded it is useful to avoid sending some smaller messages as channel data.
Pad ICE STUN ping requests and responses.
Enable padding.