Guidelines for End-to-End Support of the RTP Control Protocol (RTCP) in Back-to-Back User Agents (B2BUAs), February 2017
- Canonical URL:
- File formats:
- PROPOSED STANDARD
- L. Miniero
S. Garcia Murillo
- straw (art)
Discuss this RFC: Send questions or comments to firstname.lastname@example.org
SIP Back-to-Back User Agents (B2BUAs) are often designed to also be on the media path, rather than just to intercept signalling. This means that B2BUAs often implement an RTP or RTP Control Protocol (RTCP) stack as well, thus leading to separate multimedia sessions that the B2BUA correlates and bridges together. If not disciplined, this behaviour can severely impact the communication experience, especially when statistics and feedback information contained in RTCP messages get lost because of mismatches in the reported data.
This document defines the proper behaviour B2BUAs should follow when acting on both the signalling plane and media plane in order to preserve the end-to-end functionality of RTCP.
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 4844.