SDP Media Sections and Codec Inspector
Inspect SDP media sections, inherited connection and ICE fields, ordered codecs, fmtp parameters and parsed ICE candidates locally.
About this sdp media sections and codec inspector
Inspect SDP media sections, inherited connection and ICE fields, ordered codecs, fmtp parameters and parsed ICE candidates locally Performs protocol inspection, IP calculation, and network analysis client-side without sending probes or exposing network topology.
Protocol mechanics & network logic
Paste a complete SDP with v=0, o=, s= and t= lines, then analyze. Each m= section has its own ordered payloads, rtpmap/fmtp and candidates. Session connection, direction, ICE credentials and DTLS setup are inherited unless overridden. The original line-summary tool remains below.
Worked network diagnostic scenario
Scenario: Extract selected SDP lines without creating a connection.
Sample input:
Processing: Split trimmed lines and collect media, rtpmap, candidate, fingerprint and ice ufrag prefixes. The sample has audio payloads 111 then 0 (Opus 48000/2 then PCMU 8000/1); video uses its own IPv6 connection, recvonly direction and H264 fmtp parameters.
Illustrative output:
Addressing limits & protocol boundaries
Input must be below 100000 UTF-8 bytes. This bounded parser checks supported fields and scope, not all RFC 8866 grammar or offer/answer negotiation. Unknown fields/attributes remain raw. Missing rtpmap is not guessed from static payload numbers. ICE lite/full and DTLS setup are displayed; controlling/controlled ICE role cannot be determined from one SDP. Credentials appear in local JSON. No WebRTC, Socket, STUN/TURN or network request runs. Real peer/browser interoperability remains unverified.
Addressing calculations and subnet models in SDP Media Sections and Codec Inspector follow IETF RFC definitions. Ensure subnet masks and CIDR prefixes match your network topology.
Offline network inspection boundary
Address parsing and CIDR calculations in SDP Media Sections and Codec Inspector run entirely client-side without probing external IP networks or transmitting routing data.
IETF RFC specifications & IANA registries
IETF Request for Comments (RFC) standards and IANA registry references:
- RFC 8866 (Session Description Protocol)
- W3C WebRTC 1.0
SDP Media Sections and Codec Inspector verification · Audit standards
How to use it
- Enter, paste, or select your input data into the SDP Media Sections and Codec Inspector workspace controls.
- Review parameter fields, units, or options configured for SDP Media Sections and Codec Inspector.
- Click the action button or observe immediate live calculations rendered by SDP Media Sections and Codec Inspector.
Frequently asked questions
What SDP lines does the analyzer extract?+
It splits nonempty trimmed SDP lines and extracts only m= media lines, a=rtpmap codec lines, a=candidate lines, a=fingerprint values and the first a=ice-ufrag value. It does not negotiate or validate WebRTC.
Which controls and result fields exist?+
The page has a text input, Run locally and Load sample. JSON returns version, media sections, parsed media, codecs, candidates, fingerprints and iceUfrag. It does not create peer connections, send media, contact STUN/TURN, test reachability or inspect certificates.
Which parsing limits apply?+
A media line is split on whitespace; a malformed rtpmap becomes a raw line. Candidate lines are retained verbatim, and fingerprint text is copied after its prefix. The parser does not check SDP grammar, candidate priority, codec compatibility, DTLS validity, ICE state or session success.
What result does the worked example produce?+
Load the sample SDP to obtain one audio section, Opus 48000/2, one candidate, one fingerprint, and iceUfrag czoa. These are parsed line fields only; they do not establish connection, reachability, or session success.