List of SIP request methods

From Wikipedia, the free encyclopedia

Jump to navigationJump to search

This article needs attention from an expert in Computing. Please add

a reason or a talk parameter to this template to explain the issue with the
article. WikiProject Computing may be able to help recruit an expert. (January
2018)

This article does not cite any sources. Please help improve this

article by adding citations to reliable sources. Unsourced material may be
challenged and removed. (January 2018)  (Learn how and when to remove this
template message)

SIP requests are the messages in the Session Initiation Protocol that initiate a functionality of the
protocol. They are sent by a user agent client to the server, and are answered with one or more SIP
responses, which return a result code of the transaction, and generally indicate the success, failure,
or other state of the transaction.

SIP requests

Request RFC
Description Notes
name references

The invite message initiates a SIP

dialog with the intent to When sent during an established dialog
INVITE establish a call. It is sent by a (reinvite) it modifies the sessions, for RFC 3261
user agent client to a user agent example placing a call on hold.
server.

Confirm that an entity has

ACK received a final response to an RFC 3261
INVITE request.

This method signals termination This message may be sent by either

BYE RFC 3261
of a dialog and ends a call. endpoint of a dialog.

Usually means terminating a SIP call while it

CANCEL Cancel any pending request. RFC 3261
is still ringing, before answer.
 Query the capabilities of an It is often used[how?] for keepalive purposes.
OPTIONS [citation needed]
RFC 3261
endpoint.

Register the SIP URI listed in the

To header field with a location
REGISTER server and associates it with the It implements a location service.[how?] RFC 3261
network address given in
a Contact header field.

PRACK is sent in response to provisional

PRACK Provisional acknowledgement. RFC 3262
response (1xx).

Initiates a subscription for

SUBSCRIBE notification of events from a RFC 6665
notifier.

Inform a subscriber of
NOTIFY RFC 6665
notifications of a new event.

Publish an event to a notification

PUBLISH RFC 3903
server.

Send mid-session information

INFO that does not modify the session This method is often used for DTMF relay. RFC 6086
state.

Ask recipient to issue SIP request

REFER RFC 3515
for the purpose of call transfer.

MESSAGE Transport text messages. RFC 3428

Modifies the state of a session

UPDATE without changing the state of RFC 3311
the dialog.
 List of SIP response codes
From Wikipedia, the free encyclopedia

Jump to navigationJump to search

The Session Initiation Protocol (SIP) is a signalling protocol used for controlling communication

sessions such as Voice over IP telephone calls. SIP is based around request/response transactions,
in a similar manner to the Hypertext Transfer Protocol (HTTP). Each transaction consists of a SIP
request (which will be one of several request methods), and at least one response.[1]:p11
SIP requests and responses may be generated by any SIP user agent; user agents are divided into
clients (UACs), which initiate requests, and servers (UASes), which respond to them. [1]:§8 A single
user agent may act as both UAC and UAS for different transactions: [1]:p26 for example, a SIP phone is
a user agent that will be a UAC when making a call, and a UAS when receiving one. Additionally,
some devices will act as both UAC and UAS for a single transaction; these are called Back-to-Back
User Agents (B2BUAs).[1]:p20
SIP responses specify a three-digit integer response code, which is one of a number of defined
codes that detail the status of the request. These codes are grouped according to their first digit as
"provisional", "success", "redirection", "client error", "server error" or "global failure" codes,
corresponding to a first digit of 1–6; these are expressed as, for example, "1xx" for provisional
responses with a code of 100–199.[1]:§7.2 The SIP response codes are consistent with the HTTP
response codes, although not all HTTP response codes are valid in SIP.[1]:§21
SIP responses also specify a "reason phrase", and a default reason phrase is defined with each
response code.[1]:§7.2 These reason phrases can be varied, however, such as to provide additional
information[1]:§21.4.18 or to provide the text in a different language. [1]:§20.3
The SIP response codes and corresponding reason phrases were initially defined in RFC 3261.
[1]
 That RFC also defines a SIP Parameters Internet Assigned Numbers Authority (IANA) registry to
allow other RFC to provide more response codes.[1]:§27[2]
This list includes all the SIP response codes defined in IETF RFCs and registered in the SIP
Parameters IANA registry as of 14 July 2017. This list also includes SIP response codes defined in
obsolete SIP RFCs (specifically, RFC 2543), which are therefore not registered with the IANA; these
are explicitly noted as such.

Contents

 11xx—Provisional Responses
 22xx—Successful Responses
 33xx—Redirection Responses
 44xx—Client Failure Responses
 55xx—Server Failure Responses
 66xx—Global Failure Responses
 7References
 8External links

1xx—Provisional Responses[edit]
100 Trying
 Extended search being performed may take a significant time so a forking proxy must send a
100 Trying response.[1]:§21.1.1
180 Ringing
Destination user agent received INVITE, and is alerting user of call. [1]:§21.1.2
181 Call is Being Forwarded
Servers can optionally send this response to indicate a call is being forwarded. [1]:§21.1.3
182 Queued
Indicates that the destination was temporarily unavailable, so the server has queued the call
until the destination is available. A server may send multiple 182 responses to update
progress of the queue.[1]:§21.1.4
183 Session Progress
This response may be used to send extra information for a call which is still being set up.
[1]:§21.1.5

199 Early Dialog Terminated

Can be used by User Agent Server to indicate to upstream SIP entities (including the User
Agent Client (UAC)) that an early dialog has been terminated. [3]

2xx—Successful Responses[edit]
200 OK
Indicates the request was successful.[1]:§21.2.1
202 Accepted
Indicates that the request has been accepted for processing, but the processing has not
been completed.[4]:§7.3.1[5] Deprecated.[6]:§8.3.1[2]
204 No Notification
Indicates the request was successful, but the corresponding response will not be received. [7]

3xx—Redirection Responses[edit]
300 Multiple Choices
The address resolved to one of several options for the user or client to choose between,
which are listed in the message body or the message's Contact fields. [1]:§21.3.1
301 Moved Permanently
The original Request-URI is no longer valid, the new address is given in the Contact header
field, and the client should update any records of the original Request-URI with the new
value.[1]:§21.3.2
302 Moved Temporarily
The client should try at the address in the Contact field. If an Expires field is present, the
client may cache the result for that period of time.[1]:§21.3.3
305 Use Proxy
The Contact field details a proxy that must be used to access the requested destination. [1]:§21.3.4
380 Alternative Service
The call failed, but alternatives are detailed in the message body.[1]:§21.3.5

4xx—Client Failure
Responses[edit]
400 Bad Request
The request could not be understood due to malformed syntax.[1]:§21.4.1
401 Unauthorized
The request requires user authentication. This response is issued by UASs and registrars.
[1]:§21.4.2

402 Payment Required

Reserved for future use. [1]:§21.4.3

403 Forbidden
The server understood the request, but is refusing to fulfill it.  Sometimes (but not
[1]:§21.4.4

always) this means the call has been rejected by the receiver.
404 Not Found
The server has definitive information that the user does not exist at the domain specified in
the Request-URI. This status is also returned if the domain in the Request-URI does not
match any of the domains handled by the recipient of the request. [1]:§21.4.5
405 Method Not
Allowed
The method specified in the Request-Line is understood, but not allowed for the address
identified by the Request-URI.[1]:§21.4.6
406 Not
Acceptable
The resource identified by the request is only capable of generating response entities that
have content characteristics but not acceptable according to the Accept header field sent in
the request.[1]:§21.4.7
407 Proxy
Authenticati
on Required
The request requires user authentication. This response is issued by proxys. [1]:§21.4.8
408
Request
Timeout
Couldn't find the user in time. The server could not produce a response within a suitable
amount of time, for example, if it could not determine the location of the user in time. The
client MAY repeat the request without modifications at any later time. [1]:§21.4.9
409
Conf
lict
User already registered. [8]:§7.4.10
 Deprecated by omission from later RFCs  and by non-
[1]

registration with the IANA.[2]

4
1
0
G
o
n
e
The user existed once, but is not available here any more. [1]:§21.4.10

41
1
Le
 ng
th
Re
qu
ire
d
The server will not accept the request without a valid Content-Length. [8]:§7.4.12 Deprecated by
omission from later RFCs[1] and by non-registration with the IANA.[2]
412
Condit
ional
Reque
st
Failed
The given precondition has not been met.[9]
413
Request
Entity Too
Large
Request body too large.[1]:§21.4.11
414 Request-
URI Too Long
The server is refusing to service the request because the Request-URI is longer than the
server is willing to interpret.[1]:§21.4.12
415 Unsupport
Media Type
Request body in a format not supported.[1]:§21.4.13
416 Unsupport
Scheme
Request-URI is unknown to the server.[1]:§21.4.14
417 Unknown R
Priority
There was a resource-priority option tag, but no Resource-Priority header. [10]
420 Bad Extens
Bad SIP Protocol Extension used, not understood by the server. [1]:§21.4.15
421 Extension
The server needs a specific extension not listed in the Supported header. [1]:§21.4.16

422 Session Int

The received request contains a Session-Expires header field with a duration below the
minimum timer.[11]
423 Interval To
Expiration time of the resource is too short. [1]:§21.4.17

424 Bad Locati

The request's location content was malformed or otherwise unsatisfactory. [12]
428 Use Identit
The server policy requires an Identity header, and one has not been provided. [13]:p11
429 Provide Re
The server did not receive a valid Referred-By token on the request. [14]
A specific flow to a user agent has failed, although other flows may succeed. This response
is intended for use between proxy devices, and should not be seen by an endpoint (and if it
is seen by one, should be treated as a 400 Bad Request response).[15]:§11.5
433 Anonymity
The request has been rejected because it was anonymous. [16]
436 Bad Identit
The request has an Identity-Info header, and the URI scheme in that header cannot be
dereferenced.[13]:p11
437 Unsupport
The server was unable to validate a certificate for the domain that signed the request. [13]:p11

438 Invalid Iden

The server obtained a valid certificate that the request claimed was used to sign the request,
but was unable to verify that signature.[13]:p12
439 First Hop L
The first outbound proxy the user is attempting to register through does not support the
"outbound" feature of RFC 5626, although the registrar does.[15]:§11.6
440 Max-Bread
If a SIP proxy determines a response context has insufficient Incoming Max-Breadth to carry
out a desired parallel fork, and the proxy is unwilling/unable to compensate by forking serially
or sending a redirect, that proxy MUST return a 440 response. A client receiving a 440
response can infer that its request did not reach all possible destinations. [17]
469 Bad Info Pa
If a SIP UA receives an INFO request associated with an Info Package that the UA has not
indicated willingness to receive, the UA MUST send a 469 response, which contains a Recv-
Info header field with Info Packages for which the UA is willing to receive INFO requests. [18]
470 Consent Ne
The source of the request did not have the permission of the recipient to make such a
request.[19]
480 Temporaril
Callee currently unavailable. [1]:§21.4.18

481 Call/Transa
Server received a request that does not match any dialog or transaction. [1]:§21.4.19

482 Loop Detec

Server has detected a loop. [1]:§21.4.20

483 Too Many H

Max-Forwards header has reached the value '0'. [1]:§21.4.21

484 Address In
Request-URI incomplete. [1]:§21.4.22

485 Ambiguous
Request-URI is ambiguous.[1]:§21.4.23
486 Busy Here
Callee is busy.[1]:§21.4.24
487 Request Te
Request has terminated by bye or cancel.[1]:§21.4.25
488 Not Accept
Some aspect of the session description or the Request-URI is not acceptable, or Codec
issue.[1]:§21.4.26
489 Bad Event
The server did not understand an event package specified in an Event header field. [4]:§7.3.2[6]:§8.3.2
491 Request Pe
Server has some pending request from the same dialog. [1]:§21.4.27
493 Undeciphe
Request contains an encrypted MIME body, which recipient can not decrypt. [1]:§21.4.28

494 Security Ag
The server has received a request that requires a negotiated security mechanism, and the
response contains a list of suitable security mechanisms for the requester to choose
between,[20]:§§2.3.1–2.3.2 or a digest authentication challenge.[20]:§2.4

5xx—Serve
500 Server Inte
The server could not fulfill the request due to some unexpected condition. [1]:§21.5.1

501 Not Implem

The server does not have the ability to fulfill the request, such as because it does not
recognize the request method. (Compare with 405 Method Not Allowed, where the server
recognizes the method but does not allow or support it.) [1]:§21.5.2
502 Bad Gatew
The server is acting as a gateway or proxy, and received an invalid response from a
downstream server while attempting to fulfill the request. [1]:§21.5.3
503 Service Un
The server is undergoing maintenance or is temporarily overloaded and so cannot process
the request. A "Retry-After" header field may specify when the client may reattempt its
request.[1]:§21.5.4
504 Server Tim
The server attempted to access another server in attempting to process the request, and did
not receive a prompt response.[1]:§21.5.5
505 Version No
The SIP protocol version in the request is not supported by the server. [1]:§21.5.6

513 Message T
The request message length is longer than the server can process. [1]:§21.5.7

580 Preconditio
The server is unable or unwilling to meet some constraints specified in the offer. [21]

6xx—Globa
600 Busy Every
All possible destinations are busy. Unlike the 486 response, this response indicates the
destination knows there are no alternative destinations (such as a voicemail server) able to
accept the call.[1]:§21.6.1
603 Decline
The destination does not wish to participate in the call, or cannot do so, and additionally the
destination knows there are no alternative destinations (such as a voicemail server) willing to
accept the call.[1]:§21.6.2
 604 Does Not E
The server has authoritative information that the requested user does not exist anywhere.
[1]:§21.6.3

606 Not Accept

The user's agent was contacted successfully but some aspects of the session description
such as the requested media, bandwidth, or addressing style were not acceptable. [1]:§21.6.4
607 Unwanted
The called party did not want this call from the calling party. Future attempts from the calling
party are likely to be similarly rejected. [22]
 RTP audio video profile
From Wikipedia, the free encyclopedia
Jump to navigationJump to search
The RTP audio/video profile (RTP/AVP) is a profile for Real-time Transport Protocol (RTP) that
specifies the technical parameters of audio and video streams. RTP specifies a general-purpose
data format, but doesn't specify how encoded data should utilize the features of RTP (what payload
type value to put in the RTP header, what sampling rate and clock rate [the rate at which the RTP
timestamp increments] to use, etc.). An RTP profile specifies these details. The RTP audio/video
profile specifies a mapping of specific audio and video codecs and their sampling rates to RTP
payload types and clock rates, and how to encode each data format as an RTP data payload, as
well as specifying how to describe these mappings using Session Description Protocol (SDP).

Contents

 1RTP/AVP audio and video payload types

 2See also
 3References
 4External links

RTP/AVP audio and video payload types[edit]

Def
Pay Fr aul
loa No. Cloc am t
d of k e pac
Typ Referen
typ Name cha rate siz ket Description
e ces
e nne (Hz) e siz
(PT ls [note 1]
(m e
) s) (m
s)

ITU-T G.711 PCM µ-Law 
0 PCMU audio 1 8000 any 20 RFC 3551
audio 64 kbit/s

reserved
(previou RFC 3551,
reserved, previously FS-
1 sly FS- audio 1 8000 previously 
1016 CELP audio 4.8 kbit/s
1016CE RFC 1890
LP)

2 reserved audio 1 8000 reserved, previously ITU- RFC 3551,

(previou T G.721 ADPCM audio previously 
sly 32 kbit/s or ITU-
 Def
Pay Fr aul
loa No. Cloc am t
d of k e pac
Typ Referen
typ Name cha rate siz ket Description
e ces
e nne (Hz) e siz
(PT ls [note 1]
(m e
) s) (m
s)

G721 or
G726- T G.726 audio 32 kbit/s RFC 1890
32)

European GSM Full
3 GSM audio 1 8000 20 20 Rate audio 13 kbit/s (GSM RFC 3551
06.10)

4 G723 audio 1 8000 30 30 ITU-T G.723.1 audio RFC 3551

IMA ADPCM audio
5 DVI4 audio 1 8000 any 20 RFC 3551
32 kbit/s

IMA ADPCM audio
6 DVI4 audio 1 16000 any 20 RFC 3551
64 kbit/s

Experimental Linear
7 LPC audio 1 8000 any 20 Predictive Coding audio RFC 3551
5.6 kbit/s

ITU-T G.711 PCM A-

8 PCMA audio 1 8000 any 20 RFC 3551
Law audio 64 kbit/s

8000[note ITU-T G.722 audio RFC 3551 -

9 G722 audio 1 any 20
2]
64 kbit/s Page 14
 Def
Pay Fr aul
loa No. Cloc am t
d of k e pac
Typ Referen
typ Name cha rate siz ket Description
e ces
e nne (Hz) e siz
(PT ls [note 1]
(m e
) s) (m
s)

Linear PCM 16-bit Stereo

RFC 3551,
10 L16 audio 2 44100 any 20 audio 1411.2 kbit/s,[2][3]
Page 27
[4]
uncompressed

Linear PCM 16-bit audio RFC 3551,

11 L16 audio 1 44100 any 20
705.6 kbit/s, uncompressed Page 27

RFC
Qualcomm Code Excited
12 QCELP audio 1 8000 20 20 2658, RFC
Linear Prediction
3551

Comfort noise. Payload

type used with audio
codecs that do not support
comfort noise as part of the
13 CN audio 1 8000 RFC 3389
codec itself such
as G.711, G.722.1, G.722, 
G.726, G.727, G.728, GSM
06.10, Siren, and RTAudio.

RFC
MPEG-1 or MPEG-2 audio
14 MPA audio 1, 2 90000 8–72 3551, RFC
only
2250

ITU-T G.728 audio
15 G728 audio 1 8000 2.5 20 RFC 3551
16 kbit/s

IMA ADPCM audio
16 DVI4 audio 1 11025 any 20 RFC 3551
44.1 kbit/s
 Def
Pay Fr aul
loa No. Cloc am t
d of k e pac
Typ Referen
typ Name cha rate siz ket Description
e ces
e nne (Hz) e siz
(PT ls [note 1]
(m e
) s) (m
s)

IMA ADPCM audio

17 DVI4 audio 1 22050 any 20 RFC 3551
88.2 kbit/s

ITU-T G.729 and G.729a RFC 3551,

audio 8 kbit/s; Annex B is Page
18 G729 audio 1 8000 10 20 implied unless 20, RFC
the  annexb=no  parameter 3555, Page
is used 15

reserved
reserved,
19 (previou audio RFC 3551
previously comfort noise
sly CN)

25 CELB video 90000 Sun CellB video[5] RFC 2029

26 JPEG video 90000 JPEG video RFC 2435

Xerox PARC's Network RFC 3551,

28 nv video 90000
Video (nv)[6] Page 32

31 H261 video 90000 ITU-T H.261 video RFC 4587

MPEG-1 and MPEG-2

32 MPV video 90000 RFC 2250
video

audio/
33 MP2T 90000 MPEG-2 transport stream RFC 2250
video
 Def
Pay Fr aul
loa No. Cloc am t
d of k e pac
Typ Referen
typ Name cha rate siz ket Description
e ces
e nne (Hz) e siz
(PT ls [note 1]
(m e
) s) (m
s)

RFC
H.263 video, first version
34 H263 video 90000 3551, RFC
(1996)
2190

reserved because RTCP

packet types 200–204
RFC
would otherwise be
72–76 reserved 3550, RFC
indistinguishable from RTP
3551
payload types 72–76 with
the marker bit set

RFC
dynam H263- H.263 video, second 3551, RFC
video 90000
ic 1998 version (1998) 4629, RFC
2190

dynam H263- H.263 video, third version

video 90000 RFC 4629
ic 2000 (2000)

dynam
RFC 6184,
ic (or H264 H.264 video (MPEG-4 Part
video 90000 previously 
profile AVC 10)
RFC 3984
)

dynam
ic (or H264
video 90000 H.264 video RFC 6190
profile SVC
)

dynam H265 video 90000 H.265 video (HEVC) RFC 7798

ic (or
 Def
Pay Fr aul
loa No. Cloc am t
d of k e pac
Typ Referen
typ Name cha rate siz ket Description
e ces
e nne (Hz) e siz
(PT ls [note 1]
(m e
) s) (m
s)

profile
)

dynam draft-
ic (or barbato-
theora video 90000 Theora video
profile avt-rtp-
) theora

dynam 20, Internet low Bitrate

iLBC audio 1 8000 20, 30 RFC 3952
ic 30 Codec 13.33 or 15.2 kbit/s

dynam PCMA-
audio 1 16000 5 ITU-T G.711.1 A-law RFC 5391
ic WB

dynam PCMU-
audio 1 16000 5 ITU-T G.711.1 µ-law RFC 5391
ic WB

32000 draft-ietf-
dynam
G718 audio (placeh 20 ITU-T G.718 payload-
ic
older) rtp-g718

dynam (vario
G719 audio 48000 20 ITU-T G.719 RFC 5404
ic us)

dynam 16000, ITU-T G.722.1 and

G7221 audio 20 RFC 5577
ic 32000 G.722.1 Annex C
 Def
Pay Fr aul
loa No. Cloc am t
d of k e pac
Typ Referen
typ Name cha rate siz ket Description
e ces
e nne (Hz) e siz
(PT ls [note 1]
(m e
) s) (m
s)

dynam ITU-T G.726 audio
G726-16 audio 1 8000 any 20 RFC 3551
ic 16 kbit/s

dynam ITU-T G.726 audio

G726-24 audio 1 8000 any 20 RFC 3551
ic 24 kbit/s

dynam ITU-T G.726 audio

G726-32 audio 1 8000 any 20 RFC 3551
ic 32 kbit/s

dynam ITU-T G.726 audio

G726-40 audio 1 8000 any 20 RFC 3551
ic 40 kbit/s

dynam
G729D audio 1 8000 10 20 ITU-T G.729 Annex D RFC 3551
ic

dynam
G729E audio 1 8000 10 20 ITU-T G.729 Annex E RFC 3551
ic

dynam
G7291 audio 16000 20 ITU-T G.729.1 RFC 4749
ic

dynam GSM- ITU-T GSM-EFR (GSM

audio 1 8000 20 20 RFC 3551
ic EFR 06.60)

dynam GSM- ITU-T GSM-HR (GSM

audio 1 8000 20 RFC 5993
ic HR-08 06.20)
 Def
Pay Fr aul
loa No. Cloc am t
d of k e pac
Typ Referen
typ Name cha rate siz ket Description
e ces
e nne (Hz) e siz
(PT ls [note 1]
(m e
) s) (m
s)

dynam
ic (or (vario
AMR audio 8000 20 Adaptive Multi-Rate audio RFC 4867
profile us)
)

dynam
Adaptive Multi-Rate
ic (or AMR- (vario
audio 16000 20 Wideband audio (ITU-T RFC 4867
profile WB us)
G.722.2)
)

dynam
ic (or AMR- 1, 2 or 13.3– Extended Adaptive Multi
audio 72000 RFC 4352
profile WB+ omit 40 Rate – WideBand audio
)

dynam
ic (or (vario (variou
vorbis audio Vorbis audio RFC 5215
profile us) s)
)

dynam
ic (or 48000[no 2.5–
opus audio 1, 2 20 Opus audio RFC 7587
profile te 3]
60
)

dynam
8000,
ic (or
speex audio 1 16000, 20 Speex audio RFC 5574
profile
32000
)
 Def
Pay Fr aul
loa No. Cloc am t
d of k e pac
Typ Referen
typ Name cha rate siz ket Description
e ces
e nne (Hz) e siz
(PT ls [note 1]
(m e
) s) (m
s)

RFC
dynam mpa- 24– 5219(previ
audio 1, 2 90000 Loss-Tolerant MP3 audio
ic robust 72 ously RFC
3119)

dynam RFC
90000
ic (or MP4A- 6416(previ
audio or MPEG-4 Audio
profile LATM ously RFC
others
) 3016)

dynam RFC
90000
ic (or MP4V- 6416(previ
video or MPEG-4 Visual
profile ES ously RFC
others
) 3016)

dynam
ic (or mpeg4- audio/ 90000 MPEG-4 Elementary
RFC 3640
profile generic video or other Streams
)

dynam
VP8 video 90000 VP8 video RFC 7741
ic

draft-ietf-
dynam
VP9 video 90000 VP9 video payload-
ic
vp9

dynam L8 audio (vario (variou any 20 Linear PCM 8-bit audio RFC

ic us) s) with 128 offset 3551Sectio
n 4.5.10
 Def
Pay Fr aul
loa No. Cloc am t
d of k e pac
Typ Referen
typ Name cha rate siz ket Description
e ces
e nne (Hz) e siz
(PT ls [note 1]
(m e
) s) (m
s)

and Table 5

20 (by
analo RFC
dynam (vario (variou IEC 61119 12-bit nonlinear
DAT12 audio any gy 3190Sectio
ic us) s) audio
with n3
L16)

RFC
3551Sectio
dynam (vario (variou
L16 audio any 20 Linear PCM 16-bit audio n
ic us) s)
4.5.11, RF
C 2586

20 (by
analo RFC
dynam (vario (variou
L20 audio any gy Linear PCM 20-bit audio 3190Sectio
ic us) s)
with n4
L16)

20 (by
analo RFC
dynam (vario (variou
L24 audio any gy Linear PCM 24-bit audio 3190Sectio
ic us) s)
with n4
L16)

dynam
raw video 90000 Uncompressed Video RFC 4175
ic

dynam ac3 audio (vario 32000, Dolby AC-3 audio RFC 4184

ic us) 44100,
 Def
Pay Fr aul
loa No. Cloc am t
d of k e pac
Typ Referen
typ Name cha rate siz ket Description
e ces
e nne (Hz) e siz
(PT ls [note 1]
(m e
) s) (m
s)

48000

32000,
dynam (vario
eac3 audio 44100, Enhanced AC-3 audio RFC 4598
ic us)
48000

dynam
t140 text 1000 Text over IP RFC 4103
ic

EVRC
dynam
EVRC0 audio 8000 EVRC audio RFC 4788
ic
EVRC1

EVRCB
EVRCB
dynam
0 audio 8000 EVRC-B audio RFC 4788
ic
EVRCB
1

EVRC
WB
dynam EVRC
audio 16000 EVRC-WB audio RFC 5188
ic WB0
EVRC
WB1

dynam jpeg200
video 90000 JPEG 2000 video RFC 5371
ic 0
 Def
Pay Fr aul
loa No. Cloc am t
d of k e pac
Typ Referen
typ Name cha rate siz ket Description
e ces
e nne (Hz) e siz
(PT ls [note 1]
(m e
) s) (m
s)

dynam UEMCL 8000,

audio UEMCLIP audio RFC 5686
ic IP 16000

dynam ATRAC
audio 44100 ATRAC3 audio RFC 5584
ic 3

dynam ATRAC 44100,

audio ATRAC3+ audio RFC 5584
ic -X 48000

ATRAC
-
dynam ADVA (variou ATRAC Advanced
audio RFC 5584
ic NCED- s) Lossless audio
LOSSL
ESS

dynam
DV video 90000 DV video RFC 3189
ic

dynam
BT656 video ITU-R BT.656 video RFC 3555
ic

dynam
BMPEG video Bundled MPEG-2 video RFC 2343
ic

dynam SMPTE
video SMPTE 292M video RFC 3497
ic 292M
 Def
Pay Fr aul
loa No. Cloc am t
d of k e pac
Typ Referen
typ Name cha rate siz ket Description
e ces
e nne (Hz) e siz
(PT ls [note 1]
(m e
) s) (m
s)

dynam
RED audio Redundant Audio Data RFC 2198
ic

dynam
VDVI audio Variable-rate DVI4 audio RFC 3551
ic

dynam MPEG-1 Systems Streams

MP1S video RFC 2250
ic video

dynam MPEG-2 Program Streams

MP2P video RFC 2250
ic video

8000
dynam
tone audio (default tone RFC 4733
ic
)

8000
dynam telephon
audio (default DTMF tone RFC 4733
ic e-event
)

(equal 4000
dynam to ÷
aptx audio 2–6 4[note 4] aptX audio RFC 7310
ic sampli sampl
ng rate) e rate

1. ^ The "clock rate" is the rate at which the timestamp in the RTP header is incremented, which
need not be the same as the codec's sampling rate. For instance, video codecs typically use a clock
rate of 90000 so their frames can be more precisely aligned with the RTCP NTP timestamp, even
though video sampling rates are typically in the range of 1–60 samples per second.
 2. ^ Although the sampling rate for G.722 is 16000, its clock rate is 8000 to remain backwards
compatible with RFC 1890, which incorrectly used this value.[1]
3. ^ Because Opus can change sampling rates dynamically, its clock rate is fixed at 48000, even
when the codec will be operated at a lower sampling rate. The  maxplaybackrate and  sprop-
maxcapturerate  parameters in SDP can be used to indicate hints/preferences about the
maximum sampling rate to encode/decode.
4. ^ For aptX, the packetization interval must be rounded down to the nearest packet interval
that can contain an integer number of samples. So at sampling rates of 11025, 22050, or 44100, a
packetization rate of "4" is rounded down to 3.99.
RFC 3551 lists details of the payload format, or a reference for the details is provided. Payload
identifiers 96–127 are used for payloads defined dynamically during a session. The document
recommends dynamically assigned port numbers, although port numbers 5004 and 5005 have been
registered for use of the profile when a dynamically assigned port is not required. The standard also
describes the process of registering new payload types with IANA.
Applications operating under this profile should always support PCMU (payload type 0). Previously,
DVI4 (payload type 5) was also recommended, but this recommendation was removed in August
2013 by RFC 7007 because "many RTP deployments do not support DVI4, and there is little reason
to use it when much more modern codecs are available."