Enum ErrorCode

Error codes are six digit values, where the first three digits indicate component, while the remaining three digits particular problem with the component.

Namespace: FM.LiveSwitch
Assembly: FM.LiveSwitch.dll
Syntax
public enum ErrorCode : int

Fields

Name Description
ConnectionDeadStream

Indicates that a connection has failed connectivity checks for an extended period.
ConnectionInternalError

Indicates that an internal connection error occurred.
ConnectionInvalidArchitecture

Indicates that the connection architecture is invalid.
ConnectionNotEstablished

Indicates that a connection has not been established within allocated timeframe.
ConnectionRemoteFailure

Indicates that the remote end of the connection signalled failure.
ConnectionSimulcastNotSupported

Indicates that simulcast is not supported.
ConnectionTransportClosed

Indicates that the connection's inner transport is closed.
ConnectionTransportStartError

Indicates that the connection's inner transport could not be started.
DataStreamDirectionCannotBeChanged

Indicates that an attempt was made to modify Data Stream direction; however, this is not allowed.
DtlsInternalError

Indicates that an internal DTLS error occurred.
DtlsKeyExchangeFailed

Indicates that the DTLS key exchange failed.
DtlsNotReady

Indicates that a DTLS message was received before the DTLS endpoint was ready.
IceAllPortsInUse

Indicates that all ports are in use.
IceConnectivityCheckFailed

Indicates that connectivity checks failed on the candidate pair.
IceCreatePermissionError

Indicates that the candidate pair create-permission request failed.
IceCreatePermissionTimeout

Indicates that the candidate pair create-permission request timed out.
IceGenericGathererError

Indicates that an Ice Gatherer error occurred.
IceInvalidServerAssignmentError

Indicates the supplied Turn relay server is invalid or not resolved
IceLocalAddressUnavailable

Indicates that no local addresses were found.
IceLocalRelayedDatagramCandidateError

Indicates the local relayed candidate could not be processed.
IceLocalRelayedStreamCandidateError

Indicates the local relayed candidate could not be processed.
IceLocalServerReflexiveCandidateError

Indicates the local server reflexive could not be processed.
IcePeerReflexiveError

Indicates that the ICE transport encountered a problem creating a peer reflexive candidate.
IceRefreshError

Indicates that the relayed candidate refresh request failed.
IceRefreshTimeout

Indicates that the relayed candidate refresh request timed out.
IceSendError

Indicates that the ICE transport encountered an error while sending.
IceStartError

Indicates that the ICE gatherer could not be started.
IceUnsuitableSocketAssignment

Indicates that RTCP datagram sockets were assigned incorrectly after the gatherer was started.
IncompatibleIceSetup

Indicates that the IcePolicy requirements are not supported by the remote client.
InvalidStreamDirectionChange

Indicates that a Media Stream direction change attempt was made; however, new direction setting is not supported by the existing stream capabilities (inputs or outpus are missing).
IPProtocolMismatch

Indicates the IP Protocol mismatch has occurred.
LocalDescriptionError

Indicates that an error was encountered while processing the local description.
MediaTransportFailed

Indicates the media transport failed.
NetworkUnreachable

Indicates the network is unreachable.
PacketTooLarge

Indicates the supplied Turn relay server is invalid or not resolved.
ReliableDataChannelOpenError

Indicates that the reliable data channel encountered an error while opening.
ReliableDataChannelSendError

Indicates that the reliable data channel encountered an error while sending.
RemoteDescriptionError

Indicates that an error was encountered while processing the remote description.
SctpInternalError

Indicates that an internal SCTP error occurred.
SctpInvalidState

Indicates that an operation was attempted while in a state that doesn't allow it.
SctpNoPayloadData

Indicates that an SCTP message had no payload data.
SctpUnsupportedStream

Indicates that an attempt was made to send data on an unsupported stream.
SocketClosed

Indicates that the socket is closed.
SocketIPError

Indicates that the stream socket ip is invalid, remote server ip is invalid or there is a mimatch in the the ip of the socket and the remote server ip version
SocketManagerInvalidState

Indicates that an operation was attempted in an invalid state.
SocketReceiveError

Indicates that the socket encountered an error while receiving.
SocketSendBufferFull

Indicates that the socket's send buffer is full.
SocketSendError

Indicates that the socket encountered an error while sending.
StreamDirectionMismatch

Indicates that the local and remote stream directions are not compatible.
StreamDisabled

Indicates that the stream was disabled.
StreamEncryptionMismatch

Indicates that the local and remote stream encryption modes are not compatible.
StunAddressFamilyNotSupported

440 Address Family Not Supported. RFC 6156. Indicates that the server does not support the address family requested by the client.
StunBadRequest

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.
StunIceRoleConflict

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.
StunIntegrityCheckFailure

431 Integrity Check Failure.
StunInvalidErrorCode

Indicates that a failed response does not contain an error code or when the error code is inconsistent with the contents of the response.
StunInvalidMessageIntegrity

Indicates Invalid Stun Message Integrity
StunInvalidResponseType

Indicates Invalid Response Type, where message type obtained in reponse to a request is of unexpected type.
StunInvalidTransactionId

Indicates Invalid Stun Transaction Id
StunMissingUsername

432 Missing Username; the username attribute is not present in the request.
StunServerError

500 Server Error. RFC5389. Indicates that the server has suffered a temporary error. The client should try again.
StunStaleCredentials

430 Stale credentials; the shared secret sent in the request is expired; the client should obtain a new shared secret.
StunStaleNonce

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.
StunTryAlternate

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 or practical.
StunTurnAllocationMismatch

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.
StunTurnAllocationQuotaReached

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.
StunTurnConnectionAlreadyExists

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
StunTurnConnectionTimeoutOrFailure

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.
StunTurnForbidden

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.
StunTurnInsufficientCapacity

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.
StunTurnMobilityForbidden

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.
StunTurnPeerAddressFamilyMismatch

443 Peer Address Family Mismatch. A peer address was of a different address family than that of the relayed transport address of the allocation.
StunTurnUnsupportedTransportProtocol

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 been fixed.
StunTurnWrongCredentials

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.
StunUnauthorized

401 Unauthorized. RFC5389. Indicates that the request did not contain the correct credentials to proceed. The client should retry the request with proper credentials.
StunUnknownAttribute

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.
StunUnknownStunErrorCode

Indicates Unknown Stun Error Code