Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

sdpFmtpLine prose is vague about which SDP to use #2710

Closed
jan-ivar opened this issue Jan 20, 2022 · 0 comments · Fixed by #2711
Closed

sdpFmtpLine prose is vague about which SDP to use #2710

jan-ivar opened this issue Jan 20, 2022 · 0 comments · Fixed by #2711
Assignees

Comments

@jan-ivar
Copy link
Member

webrtc-pc sdpFmtpLine parameter says: "... For an RTCRtpSender, these parameters come from the remote description, and for an RTCRtpReceiver, they come from the local description."

This is vague. We should update this to say: "For an RTCRtpSender, these parameters come from the current remote description, and for an RTCRtpReceiver, they come from the (potentially pending) local description."

This is because:

  • sender getParameters gets it from [[SendCodecs]] which is set in the answer or pranswer.
  • receiver getParameters gets it from [[ReceiveCodecs]] which is set in SLD.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant