Test for sendonly or recvonly streams

RESOLVED WORKSFORME

Status

()

Core
WebRTC: Signaling
RESOLVED WORKSFORME
4 years ago
3 years ago

People

(Reporter: mt, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

4 years ago
It would appear that we have no tests that check that we do all the right things for sendonly and recvonly media sections.  :bwc suggested that there might be some code that makes assumptions about the relationship between send and receive streams that could be problematic.

<bwc> Because the code seems to be insisting that there be receive streams for every type we're sending before firing the [onaddstream] callback.

Perhaps if we had some basic tests that included sendonly and recvonly streams, we could be certain that this stuff actually worked.  (The existence of bug 935806 suggests that we might already have some support for sendonly/recvonly).

Comment 1

3 years ago
I am not sure if this is the right place to put my comment, so please let me know if I should move it to somewhere else. 
It appears that PeerConnection with sendonly video stream does not react on FIR packets sent to it. I do not know if this is a know issue, but it sound related tho this bug.

My test scenario is tree PeerConnections (A,B,C) connected via Video MCU (switching unit). A and B are sendonly and C is receiveonly. The MCU is using FIR to switch between A and B stream send to C. The same scenario works if A and B are in sendreceive mode.
I guess the received RTCP packets not processed in case of sendonly streams, or the RTCP receiver is inactive.
(In reply to todorst from comment #1)
> I am not sure if this is the right place to put my comment, so please let me
> know if I should move it to somewhere else. 

It would be great if you could open a new bug for your problem. As this bug is only talking about adding tests it is very unlikely that your problem would/will taken care of.

Comment 3

3 years ago
Thanks for your advice! I think that I finally found the right bug (859971) and if I understood its comments the RTCP packets are not processed/send for unidirectional streams.

Comment 4

3 years ago
This is pretty well-tested at this point. I think we're ok here.
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.