W3C home > Mailing lists > Public > public-webrtc@w3.org > November 2017

[webrtc-pc] addTransceiver woes

From: Philipp Hancke via GitHub <sysbot+gh@w3.org>
Date: Wed, 08 Nov 2017 06:44:43 +0000
To: public-webrtc@w3.org
Message-ID: <issues.opened-272090489-1510123481-sysbot+gh@w3.org>
fippo has just created a new issue for https://github.com/w3c/webrtc-pc:

== addTransceiver woes ==
given the following piece of code:
```
const pc = new RTCPeerConnection();
const transceiver = pc.addTransceiver('audio');
pc.createOffer()
.then(offer) => {
   console.log(offer.sdp);
   console.log(transceiver.mid);
})
```
1) what is the direction in the sdp? Given that the transceivers direction is sendrecv by default should it be sendrecv? But that results in an API which is sendrecv without any track information. I would expect recvonly here.

2) what is transceiver.mid insider the promise? http://w3c.github.io/webrtc-pc/#dom-rtcpeerconnection-addtransceiver says its null initially and that changes only by setting a description. However, that means the mid value in the sdp does not match the transceivers mid.

Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1662 using your GitHub account
Received on Wednesday, 8 November 2017 06:44:45 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 8 November 2017 06:44:45 UTC