Re: Should pc.getRemoteStreams() include all remote tracks after pcsetRemoteDescription() ?

2015-03-06 11:02 GMT+01:00 Harald Alvestrand <harald@alvestrand.no>:
> I think we have agreement that calling track.stop() on an incoming track
> causes the next createOffer or createAnswer to put zero in that port number
> or putting "a=recvonly" in for that m-line.

Yep, and that's crazy. Basically you call stop() on a remote/receiving
track and what it happens is that you won't send "similar" media to
the peer, but will still receive that track from the peer! yes, that
track in which you called stop().

This is crazy, this is SDP (where a sending track must match a receiving track).

I would not like to be the guy responsible of documenting that.


-- 
Iñaki Baz Castillo
<ibc@aliax.net>

Received on Friday, 6 March 2015 10:53:42 UTC