Revision as of 19:09, 17 September 2024 edit 128.7.6.66 (talk) Added RFC 9607, RTP payload for SCIP ← Previous edit		Revision as of 07:53, 6 March 2025 edit undo Dandorid (talk \| contribs) Extended confirmed users 4,434 edits →Audio and video payload types: {{Ref RFC}} Next edit →
Line 3: ==Audio and video payload types== The technical parameters of payload formats for audio and video streams are standardised.{{Ref RFC\|3551}} ~~RFC 3551, entitled '''RTP Profile for Audio and Video''' ('''RTP/AVP'''), specifies the technical parameters of payload formats for audio and video streams.~~ The standard also describes the process of registering new payload types with IANA; additional payload formats and payload types are defined in the following specifications: * {{Sum RFC\|4856}} * {{IETF RFC\|3551}}, Standard 65, ''RTP Profile for Audio and Video Conferences with Minimal Control'' * {{IETF RFC\|4856}}, ''Media Type Registration of Payload Formats in the RTP Profile for Audio and Video Conferences'' * {{IETF RFC\|3190}}, ''RTP Payload Format for 12-bit [[Digital Audio Tape\|DAT Audio]] and 20- and 24-bit Linear Sampled Audio'' * {{IETF RFC\|6184}}, ''RTP Payload Format for [[H.264]] Video'' Line 25 ⟶ 22: Payload identifiers 96–127 are used for payloads defined dynamically during a session. It is recommended to dynamically assign port numbers, although port numbers 5004 and 5005 have been registered for use of the profile when a dynamically assigned port is not required. Applications should always support PCMU (payload type 0);. ~~previously~~Previously, DVI4 (payload type 5) was also recommended, but this was removed in 2013 by.{{Ref RFC \|7007.}} {\| class="wikitable sortable" Line 142 ⟶ 139: \|audio \|1 \|8000{{refn\|group=note\|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.~~<ref~~{{Ref ~~name="rfc3551">~~RFC \|3551~~, ''RTP Profile for Audio and Video Conferences with Minimal Control'', H. Schulzrinne, S. Casner, The Internet Society (July 2003).</ref>~~\|rp=14}} \|any \|20 \|ITU-T [[G.722]] audio 64 kbit/s \|RFC 3551 ~~\|[https://tools.ietf.org/html/rfc3551#page-14 RFC 3551 - Page 14]~~ \|- Line 156 ⟶ 153: \|any \|20 \|[[Linear PCM]] 16-bit Stereo audio 1411.2 kbit/s,{{Ref RFC\|2586}}{{Ref RFC\|3108\|rp=62}}{{Ref RFC\|4856\|rp=18}} uncompressed \|[[Linear PCM]] 16-bit Stereo audio 1411.2 kbit/s,<ref>{{cite web \|url=https://tools.ietf.org/html/rfc2586 \|title=RFC 2586 - The Audio/L16 MIME content type \|date=May 1999 \|accessdate=2010-03-16}}</ref><ref>{{cite web \|url=https://tools.ietf.org/html/rfc3108#page-62 \|title=RFC 3108 - Conventions for the use of the Session Description Protocol (SDP) for ATM Bearer Connections \|date=May 2001 \|accessdate=2010-03-16}}</ref><ref>{{cite web \|url=https://tools.ietf.org/html/rfc4856#page-18 \|title=RFC 4856 - Media Type Registration of Payload Formats in the RTP Profile for Audio and Video Conferences - Registration of Media Type audio/L16 \|date=March 2007 \|accessdate=2010-03-16}}</ref> uncompressed \|[https://tools.ietf.org/html/rfc3551#page-27 RFC 3551, Page 27] \|-

RTP payload formats: Difference between revisions