Indicates that the socket encountered an error while sending.
Indicates that the socket encountered an error while receiving.
Indicates that the socket is closed.
Indicates that the socket's send buffer is full.
Indicates the local relayed candidate could not be processed.
Indicates the local server reflexive could not be processed.
Indicates that the ICE gatherer could not be started.
Indicates that RTCP datagram sockets were assigned incorrectly after the gatherer was started.
Indicates that all ports are in use.
Indicates that no local addresses were found.
Indicates that the relayed candidate refresh request timed out.
Indicates that the relayed candidate refresh request failed.
Indicates that the candidate pair create-permission request timed out.
Indicates that the candidate pair create-permission request failed.
Indicates that the ICE transport encountered an error while sending.
Indicates that the ICE transport encountered a problem creating a peer reflexive candidate
Indicates that an internal DTLS error occurred.
Indicates that the DTLS key exchange failed.
Indicates that a DTLS message was received before the DTLS endpoint was ready.
Indicates that an SCTP message had no payload data.
Indicates that an attempt was made to send data on an unsupported stream.
Indicates that an operation was attempted while in a state that doesn't allow it.
Indicates that an internal SCTP error occurred.
Indicates the media transport failed.
Indicates that the reliable data channel encountered an error while opening.
Indicates that the reliable data channel encountered an error while sending.
Indicates that the connection architecture is invalid.
Indicates that an internal connection error occurred.
Indicates that the connection's inner transport could not be started.
Indicates that the connection's inner transport is closed.
Indicates that a connection has failed connectivity checks for an extended period.
Indicates that a connection has not been established within allocated timeframe.
Indicates that the stream was disabled.
Indicates that the local and remote stream encryption modes are not compatible.
Indicates that the local and remote stream directions are not compatible.
Indicates that an error was encountered while processing the local description.
Indicates that an error was encountered while processing the remote description.
Indicates the local relayed candidate could not be processed.
Indicates the supplied Turn relay server is invalid or not resolved
300 Try Alternate. RFC5389. Indicates that a server using this extension redirects a client to another server by
replying to a request message with an error response message with an error code of 300 (Try Alternate).
The server MUST include an ALTERNATE-SERVER attribute in the error response. The error response
message MAY be authenticated; however, there are uses cases for
ALTERNATE-SERVER where authentication of the response is not possible
400 Bad Request. RFC5389. Idicates that the original request was malformed. The client SHOULD NOT retry the
request without modification from the previous attempt. The server may not be able
to generate a valid MESSAGE-INTEGRITY for this error, so the client MUST NOT expect
a valid MESSAGE-INTEGRITY attribute on this response.
401 Unauthorized. RFC5389. Indicates that the request did not contain the correct
credentials to proceed. The client should retry the request with proper credentials.
403 Forbidden. RFC 5766. Indicates that the request is valid, but the server is refusing
to perform it, likely due to administrative restrictions. The client considers the current
transaction as having failed. The client MAY notify the user or operator and SHOULD NOT retry the
same request with this server until it believes the problem has been fixed.
405 Mobility Forbidden. RFC 8016. Indicates that the request is valid, but the server is refusing to perform it,
likely due to administrative restrictions. The client considers the current transaction as having failed.
The client can notify the user or operator. The client SHOULD NOT retry sending the Allocate request
containing the MOBILITY-TICKET with this server until it believes the problem has been fixed.
420 Unknown Attribute. RFC5389. Indicates that the server received a STUN packet containing a comprehension-required
attribute that it did not understand. The server MUST put this unknown attribute in the UNKNOWN-ATTRIBUTE
attribute of its error response.
430 Stale credentials; the shared secret sent in the request is expired; the client should obtain a new shared secret.
431 Integrity Check Failure.
432 Missing Username; the username attribute is not present in the request.
437 Allocation Mismatch. RFC 5766. This indicates that the client has picked a 5-tuple that the server sees as already in use.
One way this could happen is if an intervening NAT assigned a mapped transport address that was used by another client that recently
crashed. The client considers the current transaction as having failed. The client SHOULD pick another client transport address
and retry the Allocate request (using a different transaction id).
The client SHOULD try three different client transport addresses before giving up on this server.Once the client gives up on the
server, it SHOULD NOT try to create another allocation on the server for 2 minutes.
438 Stale Nonce. RFC5389. Indicates that the NONCE used by the client was no longer valid. The client should retry, using the
NONCE provided in the response.
440 Address Family Not Supported. RFC 6156. Indicates that the server does not support the address family requested by the client.
441 Wrong Credentials. RFC 5766. Indicates that wrong credential were used by the client. The client should not receive this error
in response to an Allocate request. The client MAY notify the user or operator and SHOULD NOT retry the same request with this server
until it believes the problem has been fixed.
442 Unsupported Transport Protocol. The client should not receive this error in response to a request for a UDP allocation. The
client MAY notify the user or operator and SHOULD NOT reattempt the request with this server until it believes the problem has
443 Peer Address Family Mismatch. A peer address was of a different address family than that of the relayed transport address of the allocation.
446 Connection Already exists. This indicates that either 1) the server is currently processing a Connect request for this allocation with
the same XOR-PEER-ADDRESS; OR 2) the server has already successfully processed a Connect request for this allocation with the same XOR-PEER-ADDRESS,
and the resulting client and peer data connections are either pending or active
447 Connection Timeout or Failure. This indicates that the TURN server was unable to connect to the peer. The client MAY retry with the same
XOR-PEER-ADDRESS attribute, but MUST wait at least 10 seconds.
486 Allocation Quota Reached. The server is currently unable to create any more allocations with this username. The client considers the current
transaction as having failed. The client SHOULD wait at least 1 minute before trying to create any more allocations on the server.
487 Role Conflict. The Binding request contained either the ICE-CONTROLLING or ICE-CONTROLLED attribute, indicating a role that conflicted with the server.
The server ran a tie-breaker based on the tie-breaker value in the request and determined that the client needs to switch roles.
500 Server Error. RFC5389. Indicates that the server has suffered a temporary error. The client should try again.
508 Insufficient Capacity. The server has no more relayed transport addresses available, or has none with the requested properties, or the one that was
reserved is no longer available. The client considers the current operation as having failed. If the client is using either the EVEN-PORT or the
RESERVATION-TOKEN attribute, then the client MAY choose to remove or modify this attribute and try again immediately. Otherwise, the client SHOULD
wait at least 1 minute before trying to create any more allocations on this server.
Indicates Invalid Response Type, where message type obtained in reponse to a request is of unexpected type.
Indicates that a failed response does not contain an error code or when the error code is inconsistent with
the contents of the response.
Indicates Invalid Stun Transaction Id
Indicates Unknown Stun Error Code
Indicates Invalid Stun Message Integrity