FM.IceLink.Stun.Turn Namespace

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

A generic STUN allocate message.

A STUN allocate request.

A STUN allocate response.

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.

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.

A generic STUN channel-bind message.

A STUN channel-bind request.

A STUN channel-bind response.

The CHANNEL-NUMBER attribute contains the number of the channel.

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

A STUN connection-attempt indication.

A generic STUN connection-attempt message.

A generic STUN connection-bind message.

A STUN connection-bind request.

A STUN connection-bind response.

The CONNECTION-ID attribute uniquely identifies a peer data connection.

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.

A generic STUN connect message.

A STUN connect request.

A STUN connect response.

A generic STUN create-permission message.

A STUN create-permission request.

A STUN create-permission response.

The DATA attribute is present in all Send and Data indications. The value portion of this attribute is variable length and consists of the application data.

A STUN data indication.

A generic STUN data message.

This attribute is used by the client to request that the server set the DF (Don't Fragment) bit in the IP header when relaying the application data onward to the peer.

This attribute allows the client to request that the port in the relayed transport address be even, and (optionally) that the server reserve the next-higher port number.

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.

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.

The LIFETIME attribute represents the duration for which the server will maintain an allocation in the absence of a refresh (in seconds).

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.

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

A generic STUN refresh message.

A STUN refresh request.

A STUN refresh response.

The REQUESTED-ADDRESS-FAMILY attribute is used by clients to request the allocation of a specific address type from a server.

This attribute is used by the client to request a specific transport protocol for the allocated transport address.

The RESERVATION-TOKEN attribute contains a token that uniquely identifies a relayed transport address being held in reserve by the server.

A STUN send indication.

A generic STUN send message.

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.

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.

The XOR-PEER-ADDRESS specifies the address and port of the peer as seen from the TURN server.

The XOR-RELAYED-ADDRESS is present in Allocate responses. It specifies the address and port that the server allocated to the client.