Media diagnostics · Primary-source explanation; examples are illustrative. Instructions are based on publisher guidance; a UK IPTV account was not tested on this platform.
Read the session description
RFC 8866 defines SDP descriptions of multimedia sessions and documents dynamic RTP payload assignments using rtpmap attributes. A dynamic number observed in an RTP header is not a globally fixed codec name. Two authorised sessions can assign their dynamic values differently. A diagnostic which labels every familiar dynamic number with one codec can therefore misclassify the payload and send a decoder investigation in the wrong direction.
Keep a conceptual mapping together
For an original example, one session description associates its chosen dynamic payload number with a particular audio encoding and clock rate. Another session uses that same number for a different format. The number alone cannot distinguish them; the matching session description supplies the context. Retain the media section, mapping and any format parameters which the actual payload specification requires. Do not merge mappings from unrelated sessions merely because their numbers look the same.
Protect the private session record
Use authorised diagnostic material and remove private addresses, account identifiers or credentials before sharing a minimal excerpt. A mapping tells a receiver how a described format is represented; it does not grant access, prove the source is trusted or guarantee every receiver supports it. This article explains a packet interpretation boundary and makes no claim about UK IPTV delivery protocols. The practical improvement is to preserve the necessary description before calling a packet type unsupported or corrupt.