FFmpeg  4.3
Macros | Enumerations | Functions | Variables
rtspcodes.h File Reference
#include "libavutil/common.h"
#include "libavformat/http.h"

Go to the source code of this file.

Macros

#define RTSP_STATUS_CODE2STRING(x)
 

Enumerations

enum  RTSPStatusCode {
  RTSP_STATUS_CONTINUE =100, RTSP_STATUS_OK =200, RTSP_STATUS_CREATED =201, RTSP_STATUS_LOW_ON_STORAGE_SPACE =250,
  RTSP_STATUS_MULTIPLE_CHOICES =300, RTSP_STATUS_MOVED_PERMANENTLY =301, RTSP_STATUS_MOVED_TEMPORARILY =302, RTSP_STATUS_SEE_OTHER =303,
  RTSP_STATUS_NOT_MODIFIED =304, RTSP_STATUS_USE_PROXY =305, RTSP_STATUS_BAD_REQUEST =400, RTSP_STATUS_UNAUTHORIZED =401,
  RTSP_STATUS_PAYMENT_REQUIRED =402, RTSP_STATUS_FORBIDDEN =403, RTSP_STATUS_NOT_FOUND =404, RTSP_STATUS_METHOD =405,
  RTSP_STATUS_NOT_ACCEPTABLE =406, RTSP_STATUS_PROXY_AUTH_REQUIRED =407, RTSP_STATUS_REQ_TIME_OUT =408, RTSP_STATUS_GONE =410,
  RTSP_STATUS_LENGTH_REQUIRED =411, RTSP_STATUS_PRECONDITION_FAILED =412, RTSP_STATUS_REQ_ENTITY_2LARGE =413, RTSP_STATUS_REQ_URI_2LARGE =414,
  RTSP_STATUS_UNSUPPORTED_MTYPE =415, RTSP_STATUS_PARAM_NOT_UNDERSTOOD =451, RTSP_STATUS_CONFERENCE_NOT_FOUND =452, RTSP_STATUS_BANDWIDTH =453,
  RTSP_STATUS_SESSION =454, RTSP_STATUS_STATE =455, RTSP_STATUS_INVALID_HEADER_FIELD =456, RTSP_STATUS_INVALID_RANGE =457,
  RTSP_STATUS_RONLY_PARAMETER =458, RTSP_STATUS_AGGREGATE =459, RTSP_STATUS_ONLY_AGGREGATE =460, RTSP_STATUS_TRANSPORT =461,
  RTSP_STATUS_UNREACHABLE =462, RTSP_STATUS_INTERNAL =500, RTSP_STATUS_NOT_IMPLEMENTED =501, RTSP_STATUS_BAD_GATEWAY =502,
  RTSP_STATUS_SERVICE =503, RTSP_STATUS_GATEWAY_TIME_OUT =504, RTSP_STATUS_VERSION =505, RTSP_STATUS_UNSUPPORTED_OPTION =551
}
 RTSP handling. More...
 
enum  RTSPMethod {
  DESCRIBE, ANNOUNCE, OPTIONS, SETUP,
  PLAY, PAUSE, TEARDOWN, GET_PARAMETER,
  SET_PARAMETER, REDIRECT, RECORD, UNKNOWN = -1
}
 

Functions

static int ff_rtsp_averror (enum RTSPStatusCode status_code, int default_averror)
 

Variables

static const av_unused char *const rtsp_status_strings []
 

Macro Definition Documentation

◆ RTSP_STATUS_CODE2STRING

#define RTSP_STATUS_CODE2STRING (   x)
Value:

Definition at line 125 of file rtspcodes.h.

Enumeration Type Documentation

◆ RTSPStatusCode

RTSP handling.

Enumerator
RTSP_STATUS_CONTINUE 
RTSP_STATUS_OK 
RTSP_STATUS_CREATED 
RTSP_STATUS_LOW_ON_STORAGE_SPACE 
RTSP_STATUS_MULTIPLE_CHOICES 
RTSP_STATUS_MOVED_PERMANENTLY 
RTSP_STATUS_MOVED_TEMPORARILY 
RTSP_STATUS_SEE_OTHER 
RTSP_STATUS_NOT_MODIFIED 
RTSP_STATUS_USE_PROXY 
RTSP_STATUS_BAD_REQUEST 
RTSP_STATUS_UNAUTHORIZED 
RTSP_STATUS_PAYMENT_REQUIRED 
RTSP_STATUS_FORBIDDEN 
RTSP_STATUS_NOT_FOUND 
RTSP_STATUS_METHOD 
RTSP_STATUS_NOT_ACCEPTABLE 
RTSP_STATUS_PROXY_AUTH_REQUIRED 
RTSP_STATUS_REQ_TIME_OUT 
RTSP_STATUS_GONE 
RTSP_STATUS_LENGTH_REQUIRED 
RTSP_STATUS_PRECONDITION_FAILED 
RTSP_STATUS_REQ_ENTITY_2LARGE 
RTSP_STATUS_REQ_URI_2LARGE 
RTSP_STATUS_UNSUPPORTED_MTYPE 
RTSP_STATUS_PARAM_NOT_UNDERSTOOD 
RTSP_STATUS_CONFERENCE_NOT_FOUND 
RTSP_STATUS_BANDWIDTH 
RTSP_STATUS_SESSION 
RTSP_STATUS_STATE 
RTSP_STATUS_INVALID_HEADER_FIELD 
RTSP_STATUS_INVALID_RANGE 
RTSP_STATUS_RONLY_PARAMETER 
RTSP_STATUS_AGGREGATE 
RTSP_STATUS_ONLY_AGGREGATE 
RTSP_STATUS_TRANSPORT 
RTSP_STATUS_UNREACHABLE 
RTSP_STATUS_INTERNAL 
RTSP_STATUS_NOT_IMPLEMENTED 
RTSP_STATUS_BAD_GATEWAY 
RTSP_STATUS_SERVICE 
RTSP_STATUS_GATEWAY_TIME_OUT 
RTSP_STATUS_VERSION 
RTSP_STATUS_UNSUPPORTED_OPTION 

Definition at line 31 of file rtspcodes.h.

◆ RTSPMethod

enum RTSPMethod
Enumerator
DESCRIBE 
ANNOUNCE 
OPTIONS 
SETUP 
PLAY 
PAUSE 
TEARDOWN 
GET_PARAMETER 
SET_PARAMETER 
REDIRECT 
RECORD 
UNKNOWN 

Definition at line 129 of file rtspcodes.h.

Function Documentation

◆ ff_rtsp_averror()

static int ff_rtsp_averror ( enum RTSPStatusCode  status_code,
int  default_averror 
)
inlinestatic

Variable Documentation

◆ rtsp_status_strings

const av_unused char* const rtsp_status_strings[]
static

Definition at line 78 of file rtspcodes.h.

x
FFmpeg Automated Testing Environment ************************************Introduction Using FATE from your FFmpeg source directory Submitting the results to the FFmpeg result aggregation server Uploading new samples to the fate suite FATE makefile targets and variables Makefile targets Makefile variables Examples Introduction **************FATE is an extended regression suite on the client side and a means for results aggregation and presentation on the server side The first part of this document explains how you can use FATE from your FFmpeg source directory to test your ffmpeg binary The second part describes how you can run FATE to submit the results to FFmpeg’s FATE server In any way you can have a look at the publicly viewable FATE results by visiting this as it can be seen if some test on some platform broke with their recent contribution This usually happens on the platforms the developers could not test on The second part of this document describes how you can run FATE to submit your results to FFmpeg’s FATE server If you want to submit your results be sure to check that your combination of OS and compiler is not already listed on the above mentioned website In the third part you can find a comprehensive listing of FATE makefile targets and variables Using FATE from your FFmpeg source directory **********************************************If you want to run FATE on your machine you need to have the samples in place You can get the samples via the build target fate rsync Use this command from the top level source this will cause FATE to fail NOTE To use a custom wrapper to run the pass ‘ target exec’ to ‘configure’ or set the TARGET_EXEC Make variable Submitting the results to the FFmpeg result aggregation server ****************************************************************To submit your results to the server you should run fate through the shell script ‘tests fate sh’ from the FFmpeg sources This script needs to be invoked with a configuration file as its first argument tests fate sh path to fate_config A configuration file template with comments describing the individual configuration variables can be found at ‘doc fate_config sh template’ Create a configuration that suits your based on the configuration template The ‘slot’ configuration variable can be any string that is not yet but it is suggested that you name it adhering to the following pattern ‘ARCH OS COMPILER COMPILER VERSION’ The configuration file itself will be sourced in a shell therefore all shell features may be used This enables you to setup the environment as you need it for your build For your first test runs the ‘fate_recv’ variable should be empty or commented out This will run everything as normal except that it will omit the submission of the results to the server The following files should be present in $workdir as specified in the configuration it may help to try out the ‘ssh’ command with one or more ‘ v’ options You should get detailed output concerning your SSH configuration and the authentication process The only thing left is to automate the execution of the fate sh script and the synchronisation of the samples directory Uploading new samples to the fate suite *****************************************If you need a sample uploaded send a mail to samples request This is for developers who have an account on the fate suite server If you upload new please make sure they are as small as space on each network bandwidth and so on benefit from smaller test cases Also keep in mind older checkouts use existing sample that means in practice generally do not remove or overwrite files as it likely would break older checkouts or releases Also all needed samples for a commit should be ideally before the push If you need an account for frequently uploading samples or you wish to help others by doing that send a mail to ffmpeg devel rsync vauL Duo x
Definition: fate.txt:150
NULL
#define NULL
Definition: coverity.c:32
rtsp_status_strings
static const av_unused char *const rtsp_status_strings[]
Definition: rtspcodes.h:78
FF_ARRAY_ELEMS
#define FF_ARRAY_ELEMS(a)
Definition: sinewin_tablegen_template.c:38