Multiplexing RTP Data and Control Packets on a Single Port

Publisher

IETF / RFC Editor

URL

https://www.rfc-editor.org/rfc/rfc5761.html

Published

2010-04-01

Updated

unknown

Accessed

2026-09-24

HTTP status

200

License

IETF Trust Legal Provisions; no-redistribution; short excerpts and locators only

Source notes citing this source

• When RTP and RTCP are multiplexed, RTP payload types 64 to 95 must be avoided so RTCP packets can be distinguished, and dynamic payload types should come from 96 to 127. in context
• RTP and RTCP multiplexing on a single port is negotiated with the SDP attribute a=rtcp-mux, which the initial offer must include at media level. in context

Cite this source record

APA

WarmTransfer. (2010, April 1). Multiplexing RTP Data and Control Packets on a Single Port. WarmTransfer. https://warmtransfer.net/knowledge/sources/rfc-5761-rtcp-mux

BibTeX

@misc{warmtransfer-rfc-5761-rtcp-mux,
  title  = {Multiplexing RTP Data and Control Packets on a Single Port},
  author = {{WarmTransfer}},
  year   = {2010},
  url    = {https://warmtransfer.net/knowledge/sources/rfc-5761-rtcp-mux},
  note   = {IETF / RFC Editor, accessed 2026-09-24}
}