- From: Taylor Brandstetter via GitHub <sysbot+gh@w3.org>
- Date: Wed, 12 Jul 2017 16:30:31 +0000
- To: public-webrtc-logs@w3.org
That's correct. So if a JSEP endpoint gets a "recvonly" offer, it will send an "inactive" answer. But `transceiver.direction` (the "desired" direction) will still be `recvonly`, so if a re-offer changes the m= section to "sendrecv" or "sendonly", the re-answer will be "recvonly". So this is all intentional, and carries over the behavior from before things got rewritten in terms of transceivers. And yes, the step that says "Create an RTCRtpTransceiver with sender, receiver and direction" is incorrect; it should be "Create an RTCRtpTransceiver with sender, receiver and a `recvonly` direction". -- GitHub Notification of comment by taylor-b Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1473#issuecomment-314824112 using your GitHub account
Received on Wednesday, 12 July 2017 16:30:37 UTC