Jitter Buffer Duplicates
Understand jitter buffer duplicate packets — what causes them, when they matter, and how they relate to retransmission and network behavior.
Jitter buffer duplicates is a cumulative count of packets that arrived at the jitter buffer more than once. The buffer identifies duplicates by their RTP sequence number — if a packet with the same sequence number has already been received and buffered, the second copy is discarded.
Think of it as receiving the same letter twice in the mail. You read the first one and throw the second one away. It is not harmful, but it does tell you something about how the mail system is working.
How It Works
Each RTP packet carries a unique sequence number. The jitter buffer tracks which sequence numbers it has already received. When a packet arrives with a sequence number the buffer has already seen, it is immediately identified as a duplicate and discarded without affecting playback.
Duplicates can arrive for several legitimate reasons:
- RTX retransmission — The receiver requested retransmission of a packet it thought was lost, but the original arrived late. Now both the original and the retransmitted copy arrive, producing a duplicate.
- Network-level duplication — Routing loops, link-layer retransmissions, or misconfigured load balancers can cause the network itself to deliver multiple copies of the same packet.
- Multipath routing — When packets take multiple paths through the network, a single packet may arrive via both paths.
The duplicate counter is cumulative and increases throughout the stream lifetime.
Usually harmless
Duplicate packets are detected and discarded before they reach the decoder. They do not cause audio distortion, video artifacts, or any playback issues. A moderate duplicate count is normal, especially when retransmission (RTX) is active. Only investigate if the count is unusually high relative to total packets.
Why It Matters
While duplicates themselves do not degrade quality, they provide diagnostic insight into your network and media path:
- Retransmission overlap — A moderate duplicate count when RTX is active is expected. It means some packets arrived just after the retransmission was requested — the originals were late, not lost.
- Network anomalies — A high duplicate count without corresponding RTX activity suggests the network is duplicating packets. This wastes bandwidth and may indicate routing problems.
- Bandwidth overhead — Each duplicate consumes bandwidth. If your link is constrained, significant duplication can crowd out legitimate traffic.
For SIP load testing, comparing duplicates with RTX Requests helps you understand retransmission efficiency. If duplicates are close to RTX requests in count, many retransmission requests were unnecessary — the originals just arrived late.
Common Causes
| Cause | Explanation |
|---|---|
| RTX retransmission | Original packet arrived late after retransmission was already requested |
| Routing loops | Network misconfiguration causing packets to traverse the same path twice |
| Link-layer retransmission | WiFi or other link layers retransmitting frames that were already received |
| Load balancer mirroring | Misconfigured network equipment duplicating traffic |
| SBC/B2BUA behavior | Some session border controllers may inadvertently duplicate media |
How to Interpret It
- Low count with active RTX — Normal. Some overlap between late originals and retransmissions is expected.
- High count with active RTX — Retransmission may be too aggressive. The buffer is requesting retransmissions before giving originals enough time to arrive.
- Any count with zero RTX — Network-level duplication. Investigate the media path for routing anomalies or misconfigured equipment.
- Compare with total packets — Calculate the duplication ratio. Below 1% is typical. Above 5% warrants investigation.
Related Metrics
- RTX Requests — Retransmission requests that may cause expected duplicates
- RTX Success — Successfully retransmitted packets
- Packets Pushed — Total packets delivered to the decoder (excludes duplicates)
- Late Packets — Late arrivals that may overlap with retransmissions to produce duplicates
Jitter Buffer Packet Losses
Understand jitter buffer packet losses — packets declared lost by the buffer after waiting past their deadline, and how they differ from network-level loss.
Jitter Buffer Packets Pushed
Understand jitter buffer packets pushed — the count of packets successfully delivered from the buffer to the decoder for playback.