Home / RTP, codecs, and DTMF / Static and dynamic payload types
Static and dynamic payload types
RFC 3551 assigns static payload types. Dynamic types are named by rtpmap, and G.722 stays at clock 8000.
Learn in 5 minutes
- List static types 0, 8, 9, and 18 with their clocks
- Require rtpmap for payload types 96 through 127
- Refuse a G.722 clock of 16000
Visual
Dynamic types 96 through 127 take their meaning from rtpmap on that m-line only.
Worked example
Read static types The offer lists PCMU and PCMA on separate m-lines. Confirm the clocks are 8000.
- Press Negotiate.
- Read payload 0.
- Read payload 8 and its clock.
Fault
Both sides use payload type 96 and there is no audio. The rtpmap lines name different encodings.
Dynamic types match on the rtpmap encoding name, not on the number.
Quiz
Ecosystem
Glossary, sister systems, and the integration seam for this room.
Quality management and recording QM scores interactions. The standardized way an SBC forks a session to a recorder is SIPREC.
Sources and go deeper
- RFC 3551 — last checked 2026-10
- ITU-T G.711 — last checked 2026-10
- RFC 3264 — last checked 2026-10