RTP Payload Format for EVS
5G VoNR voice debugging requires RFC 8130 — EVS RTP framing differs substantially from RFC 4867 AMR. TOC parsing is essential for packet capture analysis.
What It Defines
RTP carriage for Enhanced Voice Services (EVS) codec frames on 5G/IMS networks. Defines compact vs header-full payload formats, AMR-WB IO mode interworking, and TOC (Table of Contents) entries for multi-frame packets.
Canonical (Normative)
Convenient (Practical)
The canonical publication point for finalized RFCs. If a protocol is standardized as an RFC, the RFC Editor text is the normative final reference. Published by the IETF, IRTF, IAB, and independent stream.
Related Specs
EVS is the next-generation carrier voice codec after AMR-WB. Required for 5G voice debugging, operator IMS integrations, and understanding VoNR codec policies.
AMR-WB is mandatory for VoLTE — every LTE voice call uses it. Understanding rate adaptation and the AMR payload format (RFC 4867) is essential for mobile VoIP and operator codec policy.
VoLTE and IMS carry AMR over RTP per RFC 4867 — not as `.amr` files. CMR bits and octet-align vs bandwidth-efficient modes cause real interoperability bugs between carriers.
5G is the foundation for edge compute, private networks, URLLC industrial automation, and mmWave backhaul. Understanding network slicing, SA vs NSA deployment modes, and QoS flows is critical for 5G-connected application design.