11 Status Code Definitions
11 Status Code Definitions
Where applicable, HTTP status [H10] codes are reused. Status codes that have the same meaning are not repeated here. See Table 1 for a listing of which status codes may be returned by which requests.
11.1 Success 2xx
11.1.1 250 Low on Storage Space
The server returns this warning after receiving a RECORD request that it may not be able to fulfill completely due to insufficient storage space. If possible, the server should use the Range header to indicate what time period it may still be able to record. Since other processes on the server may be consuming storage space simultaneously, a client should take this only as an estimate.
11.2 Redirection 3xx
See [H10.3].
Within RTSP, redirection may be used for load balancing or redirecting stream requests to a server topologically closer to the client. Mechanisms to determine topological proximity are beyond the scope of this specification.
11.3 Client Error 4xx
11.3.1 405 Method Not Allowed
The method specified in the request is not allowed for the resource identified by the request URI. The response MUST include an Allow header containing a list of valid methods for the requested resource. This status code is also to be used if a request attempts to use a method not indicated during SETUP, e.g., if a RECORD request is issued even though the mode parameter in the Transport header only specified PLAY.
11.3.2 451 Parameter Not Understood
The recipient of the request does not support one or more parameters contained in the request.
11.3.3 452 Conference Not Found
The conference indicated by a Conference header field is unknown to the media server.
11.3.4 453 Not Enough Bandwidth
The request was refused because there was insufficient bandwidth. This may, for example, be the result of a resource reservation failure.
11.3.5 454 Session Not Found
The RTSP session identifier in the Session header is missing, invalid, or has timed out.
11.3.6 455 Method Not Valid in This State
The client or server cannot process this request in its current state. The response SHOULD contain an Allow header to make error recovery easier.
11.3.7 456 Header Field Not Valid for Resource
The server could not act on a required request header. For example, if PLAY contains the Range header field but the stream does not allow seeking.
11.3.8 457 Invalid Range
The Range value given is out of bounds, e.g., beyond the end of the presentation.
11.3.9 458 Parameter Is Read-Only
The parameter to be set by SET_PARAMETER can be read but not modified.
11.3.10 459 Aggregate Operation Not Allowed
The requested method may not be applied on the URL in question since it is an aggregate (presentation) URL. The method may be applied on a stream URL.
11.3.11 460 Only Aggregate Operation Allowed
The requested method may not be applied on the URL in question since it is not an aggregate (presentation) URL. The method may be applied on the presentation URL.
11.3.12 461 Unsupported Transport
The Transport field did not contain a supported transport specification.
11.3.13 462 Destination Unreachable
The data transmission channel could not be established because the client address could not be reached. This error will most likely be the result of a client attempt to place an invalid Destination parameter in the Transport field.
11.3.14 551 Option not supported
An option given in the Require or the Proxy-Require fields was not supported. The Unsupported header should be returned stating the option for which there is no support.