DescriptionFix RtpReceiver.GetParameters when SSRCs aren't signaled.
When SSRCs aren't signaled, an SSRC of 0 is used internally to mean
"the default receive stream". But this wasn't working with the
implementation of GetRtpReceiveParameters in the audio/video
engines. This was breaking RtpReceiver.GetParameters in this situation,
as well as the new getStats implementation (which relies on
GetParameters).
The new implementation will fail if *no* default receive stream is
configured (meaning no default sink is set), and otherwise will return
a default RtpEncodingParameters (later it will be filled with relevant
SDP parameters as they're implemented).
BUG=webrtc:6971
Review-Url: https://codereview.webrtc.org/2806173002
Cr-Commit-Position: refs/heads/master@{#17803}
Committed: https://chromium.googlesource.com/external/webrtc/+/3bc15103aea1dd2fdfc01b833b62f34171c82e81
Patch Set 1 #
Total comments: 2
Patch Set 2 : Changing behavior slightly in response to comment on https://github.com/w3c/webrtc-pc/issues/1116 #
Messages
Total messages: 12 (6 generated)
|