Click or drag to resize
ErrorCode Enumeration
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.IceLink
Assembly: FM.IceLink (in FM.IceLink.dll) Version: 3.0.3.0 (3.0.3.0)
Members
  Member nameValueDescription
SocketSendError100000 Indicates that the socket encountered an error while sending.
SocketReceiveError100001 Indicates that the socket encountered an error while receiving.
SocketClosed100002 Indicates that the socket is closed.
SocketSendBufferFull100003 Indicates that the socket's send buffer is full.
IceLocalRelayedDatagramCandidateError101000 Indicates the local relayed candidate could not be processed.
IceLocalServerReflexiveCandidateError101001 Indicates the local server reflexive could not be processed.
IceStartError102000 Indicates that the ICE gatherer could not be started.
IceUnsuitableSocketAssignment102001 Indicates that RTCP datagram sockets were assigned incorrectly after the gatherer was started.
IceAllPortsInUse102002 Indicates that all ports are in use.
IceLocalAddressUnavailable102003 Indicates that no local addresses were found.
IceRefreshTimeout103000 Indicates that the relayed candidate refresh request timed out.
IceRefreshError103001 Indicates that the relayed candidate refresh request failed.
IceCreatePermissionTimeout104000 Indicates that the candidate pair create-permission request timed out.
IceCreatePermissionError104001 Indicates that the candidate pair create-permission request failed.
IceSendError105000 Indicates that the ICE transport encountered an error while sending.
IcePeerReflexiveError105001 Indicates that the ICE transport encountered a problem creating a peer reflexive candidate
DtlsInternalError106000 Indicates that an internal DTLS error occurred.
DtlsKeyExchangeFailed106001 Indicates that the DTLS key exchange failed.
DtlsNotReady106002 Indicates that a DTLS message was received before the DTLS endpoint was ready.
SctpNoPayloadData107000 Indicates that an SCTP message had no payload data.
SctpUnsupportedStream107001 Indicates that an attempt was made to send data on an unsupported stream.
SctpInvalidState107002 Indicates that an operation was attempted while in a state that doesn't allow it.
SctpInternalError107003 Indicates that an internal SCTP error occurred.
MediaTransportFailed108000 Indicates the media transport failed.
ReliableDataChannelOpenError109000 Indicates that the reliable data channel encountered an error while opening.
ReliableDataChannelSendError109001 Indicates that the reliable data channel encountered an error while sending.
ConnectionInvalidArchitecture110000 Indicates that the connection architecture is invalid.
ConnectionInternalError110001 Indicates that an internal connection error occurred.
ConnectionTransportStartError110002 Indicates that the connection's inner transport could not be started.
ConnectionTransportClosed110003 Indicates that the connection's inner transport is closed.
ConnectionDeadStream110004 Indicates that a connection has failed connectivity checks for an extended period.
ConnectionNotEstablished110005 Indicates that a connection has not been established within allocated timeframe.
StreamDisabled111000 Indicates that the stream was disabled.
StreamEncryptionMismatch111001 Indicates that the local and remote stream encryption modes are not compatible.
StreamDirectionMismatch111002 Indicates that the local and remote stream directions are not compatible.
LocalDescriptionError112000 Indicates that an error was encountered while processing the local description.
RemoteDescriptionError112001 Indicates that an error was encountered while processing the remote description.
IceLocalRelayedStreamCandidateError113000 Indicates the local relayed candidate could not be processed.
IceInvalidServerAssignmentError113001 Indicates the supplied Turn relay server is invalid or not resolved
StunTryAlternate114000 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.
StunBadRequest114001 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.
StunUnauthorized114002 401 Unauthorized. RFC5389. Indicates that the request did not contain the correct credentials to proceed. The client should retry the request with proper credentials.
StunTurnForbidden114003 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.
StunTurnMobilityForbidden114004 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.
StunUnknownAttribute114005 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.
StunStaleCredentials114006 430 Stale credentials; the shared secret sent in the request is expired; the client should obtain a new shared secret.
StunIntegrityCheckFailure114007 431 Integrity Check Failure.
StunMissingUsername114008 432 Missing Username; the username attribute is not present in the request.
StunTurnAllocationMismatch114009 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.
StunStaleNonce114010 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.
StunAddressFamilyNotSupported114011 440 Address Family Not Supported. RFC 6156. Indicates that the server does not support the address family requested by the client.
StunTurnWrongCredentials114012 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.
StunTurnUnsupportedTransportProtocol114013 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.
StunTurnPeerAddressFamilyMismatch114014 443 Peer Address Family Mismatch. A peer address was of a different address family than that of the relayed transport address of the allocation.
StunTurnConnectionAlreadyExists114015 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
StunTurnConnectionTimeoutOrFailure114016 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.
StunTurnAllocationQuotaReached114017 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.
StunIceRoleConflict114018 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.
StunServerError114019 500 Server Error. RFC5389. Indicates that the server has suffered a temporary error. The client should try again.
StunTurnInsufficientCapacity114020 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.
StunInvalidResponseType114021 Indicates Invalid Response Type, where message type obtained in reponse to a request is of unexpected type.
StunInvalidErrorCode114022 Indicates that a failed response does not contain an error code or when the error code is inconsistent with the contents of the response.
StunInvalidTransactionId114023 Indicates Invalid Stun Transaction Id
StunUnknownStunErrorCode114024 Indicates Unknown Stun Error Code
StunInvalidMessageIntegrity114025 Indicates Invalid Stun Message Integrity
See Also