Skip to content
Glossary November 2026 6 min read

What Is RTP (Real-time Transport Protocol)?

RTP carries the actual voice in a VoIP call, while SIP only sets it up. See what RTP does, how RTCP reports loss and jitter, and why one-way audio happens.

D
November 2026
Last updated

Quick answer

RTP, the Real-time Transport Protocol, is the protocol that carries the actual audio of a VoIP call. RFC 3550 describes it as end-to-end delivery for real-time data such as interactive audio. SIP sets up the call; RTP carries the voice, and its companion RTCP reports packet loss and jitter.

When a VoIP call is connected, two people hear each other because small packets of encoded audio are flowing in both directions. RTP is the protocol that wraps and numbers those packets. SIP arranges the call; RTP carries the sound.

The Definition

RFC 3550 describes RTP as providing end-to-end delivery services for data with real-time characteristics, such as interactive audio and video. Those services include payload type identification, sequence numbering, timestamping and delivery monitoring. The RFC is clear about the limits: applications typically run RTP on top of UDP, though it may be used with other suitable protocols, and RTP itself does not guarantee timely delivery or quality of service. It relies on lower-layer services for that.

Sequence numbers let a receiver spot missing or out-of-order packets, and timestamps let it play the audio back at the right pace. Those two fields are the raw material for the measurements covered below.

SIP Sets Up the Call, RTP Carries the Audio

The easiest way to think about it: SIP is the conversation about the call, RTP is the call. During setup the two ends agree on compatible media types, as RFC 3261 describes. After the ACK, audio is exchanged as an RTP stream in each direction. If SIP signalling succeeds but the RTP path is blocked or misrouted, the call still shows as connected, because signalling and media take different paths.

For port numbering, RFC 3550 says RTP should use an even destination port and the corresponding RTCP stream the next higher, odd port, and that the RTP and RTCP port numbers must not be the same. Firewalls and session border controllers therefore need to allow a range of media ports, not only the signalling port. See the SBC page for the device that often sits in that path.

RTCP: How Each Side Reports Loss and Jitter

RTP has a companion, the RTP Control Protocol. RFC 3550 says RTCP is based on the periodic transmission of control packets to all participants, and that its primary function is to provide feedback on the quality of the data distribution. In the sender and receiver reports (sections 6.4.1 and 6.4.2) three fields matter for call quality:

  • Fraction lost: the fraction of RTP data packets from a source that were lost since the previous report was sent.
  • Cumulative number of packets lost: the total number of RTP data packets from that source lost since the beginning of reception.
  • Interarrival jitter: an estimate of the statistical variance of the RTP data packet interarrival time, measured in timestamp units.

These are the same measurements discussed on the jitter and packet loss pages. They are also the inputs to a MOS estimate, together with latency and the codec.

RTP and Codecs

RTP does not decide how voice is compressed. The voice codec does, and RTP labels each packet with the payload type so the receiver knows which codec to decode it with. If the two ends cannot agree on a codec during SIP setup, there is nothing for RTP to carry, which is why codec mismatches show up as failed calls or silence rather than as poor quality.

When RTP Goes Wrong: One-Way and No Audio

Because media is a separate stream, RTP problems have a recognisable pattern. A call that rings, is answered, and then has silence in one direction, or both, usually means RTP packets are not reaching the far end or are being dropped on the way. Common places to look are firewalls, NAT handling and the media ports allowed through. The one-way audio troubleshooting guide takes you through it step by step. Choppy or robotic audio is a different pattern: packets arrive, but late or incompletely.

How to Use It

  • Ask which half is failing. No ring or a rejected call is a SIP question. Silence after answer is an RTP question.
  • Use the RTCP numbers. Fraction lost and jitter tell you whether the problem is the stream or something else.
  • Allow the media ports. Opening only the signalling port is the classic cause of one-way audio.

Frequently Asked Questions

What is RTP used for in VoIP?

RTP carries the actual audio of a call as a stream of numbered, timestamped packets. SIP sets up the call; RTP delivers the voice.

What is the difference between RTP and SIP?

SIP is signalling: it creates, modifies and ends the session. RTP is media: it carries the audio itself. They run as separate streams.

What is RTCP?

The RTP Control Protocol. It sends periodic reports between participants, including fraction lost, cumulative packets lost and interarrival jitter.

Which ports does RTP use?

RFC 3550 says RTP should use an even destination port and RTCP the next higher odd port. The actual range is set by your platform, carrier or SBC, so ask which range to allow.

Does RTP guarantee call quality?

No. RFC 3550 states that RTP itself does not guarantee timely delivery or quality of service. It relies on the underlying network.

Related terms and guides: SIP, SRTP, jitter, packet loss, voice codec, MOS, one-way audio troubleshooting.

Sources

Related terms

Ready to see DialerBee in action?

Request a 15-minute live demo, or start a 14-day free trial — no slides, no commitment. Calling starts once your own SIP trunk or PBX is connected and approved.

14-day free trial · free AI credit · no card · 11 languages · BYOC · compliance-supporting controls