Enumeration ErrorCodes

Failed to apply constraints to a broadcast sender. Please check your broadcast configuration again. See the error message for more information.

Failed to create a broadcast offer. This can occur when the offer creation fails, the resulting SDP is empty, or the modification of the SDP fails.

Failed to add transceiver to the peer connection. See the error message for more information.

Peer connection has already been created. This may happen when trying to call 'startBroadcast' multiple times.

Peer connection has not been created yet. This may happen when trying to call 'dispose' or 'stopBroadcast' multiple times.

Failed to set a broadcast answer. This can occur if an answer already exists, the creation of an answer from SDP fails, or setting the remote description fails.

Client request failed. This may indicate a failure to reach the server or a response with 4XX HTTP status.

Client request is still pending. This may occur when trying to send multiple start/stop requests to the server simultaneously.

Client resource already exists. This may occur when a broadcast was not properly cleaned up after the termination of a previous broadcast.

Client resource does not exist. This may occur if 'startBroadcast' has not been called yet.

Unrecognized error that does not fit into other specific categories.

'startBroadcast' method has not been called yet.

Failed to set up logger. Logger configuration needs to be re-checked.

Recovery failed.

'setup' method has not been called yet.

Media device kind not supported. See the error message for more information.

A MediaDevices API method is not supported. This occurs when a requested MediaDevices method is not available in the current browser environment.

Permission query for media devices failed.

MediaStream already exists. This may happen when trying to call 'setup' multiple times.

Failed to create a MediaStream. See the error message for more information.

MediaStream has not been set yet. This may happen if 'setup' has not been called yet.

Failed to initiate the collection of RTC stats.

Failed to obtain stats as the sender's track kind is incorrect. It must be either "audio" or "video".

Failed to parse user agent for metrics gathering.

Failed to stop the collection of RTC stats.

Failed to create a resource on the server.

Malformed response from the server. This may occur when the response from the server is missing expected fields or contains empty SDP.

Server request failed. Corresponds to 5XX HTTP status. See the error's metadata and message for more information.

Failed to validate incoming configuration. This occurs when an object does not pass schema validation. See the error message for the exact location of issues.