RTP payload formats: Difference between revisions

Content deleted Content added
Audio and video payload types: Move {{Sum RFC}} to top.
Line 23:
* {{Sum RFC|4629|ref=yes}}
* {{Sum RFC|4749|ref=yes}}
* {{Sum RFC|4867|ref=yes}}
* {{Sum RFC|5391|ref=yes}}
* {{Sum RFC|5404|ref=yes}}
* {{Sum RFC|5577|ref=yes}}
* {{Sum RFC|5993|ref=yes}}
* {{Sum RFC|6184|ref=yes}}
* {{Sum RFC|6190|ref=yes}}
Line 33 ⟶ 35:
* {{Sum RFC|9134|ref=yes}}
* {{Sum RFC|9607|ref=yes}}
* {{Sum RFC|9628|ref=yes}}
 
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.
Line 597 ⟶ 600:
|
|ITU-T [[Half Rate|GSM-HR]] (GSM 06.20)
|RFC{{IETF RFC|5993|link=no}}
|-
 
Line 608 ⟶ 611:
|
|[[Adaptive Multi-Rate]] audio
|RFC{{IETF RFC|4867|link=no}}
|-
 
Line 619 ⟶ 622:
|
|[[AMR-WB|Adaptive Multi-Rate Wideband]] audio (ITU-T G.722.2)
|RFC{{IETF RFC|4867|link=no}}
|-
 
Line 729 ⟶ 732:
|
|[[VP9]] video
|{{IETF RFC|9628|link=no}}
|[https://tools.ietf.org/html/draft-ietf-payload-vp9 draft-ietf-payload-vp9]
|-