…ation can specify its preferred policy regarding use of RTP/RTCP multiplexing [ RFC5761 ] using one of the following policies: negotiate: The JSEP implementation will gather both RTP and RTCP candidates but also will offer "a=rtcp-mux", thus allowing for compatibility with either…

…ng RTP data packets and RTCP control packets on a single transport-layer flow [ RFC5761 ] . Such RTP and RTCP multiplexing MUST be negotiated in the signaling channel before it is used. If SDP is used for signaling, this negotiation MUST use the mechanism defined in [ RFC5761 ] .…

…ng RTP data packets and RTCP control packets on a single transport-layer flow [ RFC5761 ] . Such RTP and RTCP multiplexing MUST be negotiated in the signaling channel before it is used. If SDP is used for signaling, this negotiation MUST use the mechanism defined in [ RFC5761 ] .…

…same port and signals that it can do that in the SDP through an SDP attribute [ RFC5761 ]. However, since the offerer doesn't know if the answerer can perform Rosenberg Standards Track [Page 31] RFC 5245 ICE April 2010 such multiplexing, the offerer includes candidates for RTP an…

…same port and signals that it can do that in the SDP through an SDP attribute [ RFC5761 ]. However, since the offerer doesn't know if the answerer can perform Rosenberg Standards Track [Page 31] RFC 5245 ICE April 2010 such multiplexing, the offerer includes candidates for RTP an…

…her example, the initiating agent can multiplex RTP and RTCP on the same port [ RFC5761 ]. However, since the initiating agent doesn't know if the peer agent can perform such multiplexing, it includes candidates for RTP and RTCP on separate ports. If the peer agent can perform su…

…same port and signals that it can do that in the SDP through an SDP attribute [ RFC5761 ]. However, since the offerer doesn't know if the answerer can perform Rosenberg Standards Track [Page 31] RFC 5245 ICE April 2010 such multiplexing, the offerer includes candidates for RTP an…

…same port and signals that it can do that in the SDP through an SDP attribute [ RFC5761 ]. However, since the offerer doesn't know if the answerer can perform Rosenberg Standards Track [Page 31] RFC 5245 ICE April 2010 such multiplexing, the offerer includes candidates for RTP an…

…her example, the initiating agent can multiplex RTP and RTCP on the same port [ RFC5761 ]. However, since the initiating agent doesn't know if the peer agent can perform such multiplexing, it includes candidates for RTP and RTCP on separate ports. If the peer agent can perform su…

…ying RTCIceTransport . Though if RTCP multiplexing is negotiated according to [ RFC5761 ], or if connection 's RTCRtcpMuxPolicy is require , do not create any RTCP-specific transport objects, and instead let rtcpTransport equal transport Set transceiver [[Sender]] [[SenderTranspo…

… are mandatory to implement in [[!RTP-USAGE]], such as RTP/RTCP multiplexing [[!RFC5761]], audio/video multiplexing [[!RTP-MULTI-STREAM]] and reduced size RTCP [[!RFC5506]] are assumed to be available and are therefore not included in RTCRtpCapabilities although these features ca…

… are mandatory to implement in [[!RTP-USAGE]], such as RTP/RTCP multiplexing [[!RFC5761]] and reduced size RTCP [[!RFC5506]] are assumed to be available and are therefore not included in RTCRtpCapabilities although these features can be set via RTCRtpParameters sequence<RTCRtpCod…

… are mandatory to implement in [[!RTP-USAGE]], such as RTP/RTCP multiplexing [[!RFC5761]], audio/video multiplexing [[!RTP-MULTI-STREAM]] and reduced size RTCP [[!RFC5506]] are assumed to be available and are therefore not included in RTCRtpCapabilities , although these parameter…

… are mandatory to implement in [[!RTP-USAGE]], such as RTP/RTCP multiplexing [[!RFC5761]] and reduced-size RTCP [[!RFC5506]] are assumed to be available and are therefore not included in RTCRtpCapabilities although these features can be set via RTCRtpParameters sequence<RTCRtpCod…

… are mandatory to implement in [[!RTP-USAGE]], such as RTP/RTCP multiplexing [[!RFC5761]], audio/video multiplexing [[!RTP-MULTI-STREAM]] and reduced size RTCP [[!RFC5506]] are assumed to be available and are therefore not included in RTCRtpCapabilities although these features ca…