W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > January 2018

Re: [webrtc-pc] addTransceiver woes

From: stefan hakansson via GitHub <sysbot+gh@w3.org>
Date: Tue, 02 Jan 2018 19:07:11 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-354849370-1514920030-sysbot+gh@w3.org>
I don't care that much what the default is, perhaps "inactive"? Or we let it be "sendrecv".

>My interpretation is ontrack only fires in association with receivers being created with a track. That means at SRD() or if you addTransceiver() then no event should fire because you created it yourself.
When I read 4.4.1.6, "Set the RTCSessionDescription", sub bullets 2.8.2.5 and 2.8.2.6 I come to the conclusion:
- On the answerer side, `ontrack` will fire (as result of SRD) if the offerer side created the transceiver with `sendonly` or `sendrecv`
- On the offerer side, `ontrack` will fire (as result of SRD) if the answerer side created the transceiver (selected for this media description) with `sendonly` or `sendrecv`

So it seems possible to get `ontrack` - even if no tracks are attached - on both ends if the offerer app creates a `sendonly` transceiver and the answerer creates a `sendrecv` transceiver (that is picked for the media description).



-- 
GitHub Notification of comment by stefhak
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1662#issuecomment-354849370 using your GitHub account
Received on Tuesday, 2 January 2018 19:07:15 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:21:58 UTC