…ned long The SSRC to be used in the "SSRC of packet sender" field defined in [[!RFC3550]] Section 6.4.2 (Receiver Report) and [[!RFC4585]] Section 6.1 (Feedback Messages), as well as the "SSRC" field defined in [[!RFC3611]] Section 2 (Extended Reports). It can only be set for an …
…ong ssrc The SSRC to be used in the "SSRC of packet sender" field defined in [[!RFC3550]] Section 6.4.2 (Receiver Report) and [[!RFC4585]] Section 6.1 (Feedback Messages), as well as the "SSRC" field defined in [[!RFC3611]] Section 2 (Extended Reports). This is only set for an RT…
…ong ssrc The SSRC to be used in the "SSRC of packet sender" field defined in [[!RFC3550]] Section 6.4.2 (Receiver Report) and [[!RFC4585]] Section 6.1 (Feedback Messages), as well as the "SSRC" field defined in [[!RFC3611]] Section 2 (Extended Reports). It can only be set for an …
…ned long The SSRC to be used in the "SSRC of packet sender" field defined in [[!RFC3550]] Section 6.4.2 (Receiver Report) and [[!RFC4585]] Section 6.1 (Feedback Messages), as well as the "SSRC" field defined in [[!RFC3611]] Section 2 (Extended Reports). It can only be set for an …
…ong ssrc The SSRC to be used in the "SSRC of packet sender" field defined in [[!RFC3550]] Section 6.4.2 (Receiver Report) and [[!RFC4585]] Section 6.1 (Feedback Messages), as well as the "SSRC" field defined in [[!RFC3611]] Section 2 (Extended Reports). This is only set for an RT…
…ong ssrc The SSRC to be used in the "SSRC of packet sender" field defined in [[!RFC3550]] Section 6.4.2 (Receiver Report) and [[!RFC4585]] Section 6.1 (Feedback Messages), as well as the "SSRC" field defined in [[!RFC3611]] Section 2 (Extended Reports). This is only set for an RT…
… . RTP Speex Header Fields The RTP header is defined in the RTP specification [ RFC3550 ]. This section defines how fields in the RTP header are used. Payload Type (PT): The assignment of an RTP payload type for this packet format is outside the scope of this document; it is spec…
…nce number, SSRC and CSRC identifiers) are used as specified in Section 5.1 of [RFC3550] 4.2 . VP8 Payload Descriptor The first octets after the RTP header are the VP8 payload descriptor, with the following structure. The single-octet version of the PictureID is illustrated to th…
…hat the browser may change the SSRC in event of a collision, as described in [[!RFC3550]]. dictionary RTCRtpCodecParameters unsigned byte payloadType The value that goes in the RTP Payload Type Field [[!RFC3550]]. The payloadType must always be provided both within RTCRtpSender a…
…o be used in the Receiver Report "SSRC of packet sender" field as defined in [[!RFC3550]] Section 6.4.2. If unset, ssrc is chosen by the browser, and the chosen value is not reflected in RTCRtcpParameters.ssrc If the browser chooses the ssrc it may change it in event of a collisi…
…hat the browser may change the SSRC in event of a collision, as described in [[!RFC3550]]. boolean compound=true Whether compound RTCP is configured (if true) or reduced-size RTCP as specified in [[!RFC5506]], if false. boolean mux=true Whether RTP and RTCP are multiplexed, as sp…
…the Real-time Transport Protocol has SSRC collisions, which although very rare [RFC3550] are quite possible. During a collision, two or more SSRCs that share a master key will have identical keystreams for overlapping portions of the RTP sequence number space. SRTP Security Descr…
…...... 8 1 . Introduction In a centralized Real-time Transport Protocol (RTP) [ RFC3550 ] audio conference, an audio mixer or forwarder receives audio streams from many or all of the conference participants. It then selectively forwards some of them to other participants in the c…
…d is transported over the same port as the Real-time Transport Protocol (RTP) [ RFC3550 ] media stream which has been established using a signaling protocol such as Session Initiation Protocol (SIP) [ RFC3261 ]. This generates a shared secret, which is then used to generate keys …
…am maps into an RTP session. The RTP RFC [ RFC1889 ] (at present obsoleted by [ RFC3550 ]) used to define an RTP session as follows: "For each participant, the session is defined by a particular pair of destination transport addresses (one network address plus a port pair for RTP…