RTP sequence numbers help a receiver track packet order and estimate missing packets within a source. They are not programme frame numbers, and a visible gap is not automatically a permanent loss that the viewer noticed.
Use them when the session actually uses RTP and the evidence is collected appropriately. An unrelated HTTP media log should not be interpreted as an RTP sequence trace.
Keep the source identity attached
Sequence tracking belongs to the relevant RTP source, identified within the session. Mixing packets from different sources can create apparent gaps that do not describe one continuous sequence. A source restart or identifier change also needs interpretation.
The base RTP sequence field wraps around, so a smaller number after a larger one is not automatically a restart. Analysis tools may maintain an extended sequence value. Read the tool's method rather than counting simple numeric jumps by eye.
Allow for arrival order and observation limits
Packets can arrive out of order or later than an initial observation. A gap at one instant may be filled afterward, although late data can still miss an application's playback deadline. Network reception and useful on-time media are related but different measures.
A capture can also lose packets locally if its collection process cannot keep up. That makes capture quality part of the evidence. Do not accuse a network operator of dropping every packet absent from an overloaded monitoring file.
Relate the trace to actual playback
Record the relevant time window and application symptom. A receiver may conceal some loss, recover information through additional mechanisms or continue with a visible artifact. The sequence trace does not describe those outcomes by itself.
For a household investigation, a supported player statistic may be more practical than a raw capture. Note whether the statistic represents packets missing at reception, packets too late for use or another measure. Similar labels can conceal different calculations.
- Confirm that the observed session uses RTP.
- Keep packets separated by the appropriate source identity.
- Account for wraparound, reordering and source restarts.
- Check collection quality and the statistic’s definition.
- Align the result with the actual viewing symptom.
Report a bounded finding
A useful report says that a defined source showed a particular reception pattern during a documented interval. It does not convert the count directly into a universal picture-quality percentage or identify the precise network hop responsible.
Keep private session and account details out of public reports. If specialist support needs a trace, use an authorized channel and a limited capture scope. The sequence mechanism is a diagnostic aid, not a reason to collect unrelated household traffic.
Useful answers
Is an RTP sequence number the video frame number?
No. It tracks RTP packet sequence for a source. Frames and packets are different units, and one frame may involve multiple packets.
Does every sequence gap mean permanent network loss?
No. Reordering, late arrival, source changes and capture loss need consideration. The application’s actual outcome is another separate observation.