You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Subscribe to a single publisher's video and data channels.
Unsubscribe from data channel by sending: "body": { "streams": [ { "feed": 8532500667596649, "mid": "1" } ], "request": "unsubscribe"
we are not receiving data channel messages
subscribe to data channel again.
data channel messages start flowing.
Not working scenario:
1.subscribe to many publisher's video and data channels.
2. Unsubscribe from one of subscribed publishers by sending: "body": { "streams": [ { "feed": 8532500667596649, "mid": "1" } ], "request": "unsubscribe"
result:
3. We are not receiving any data channel messages from any publisher.
4. subscribe to data channel again not working, messages are not flowing.
expected:
3. We are not receiving data channel messages from this publisher, however, the rest of them are working
4. subscribe to data channel again enables messages from this publisher.
tested on latest multistream: f976215
Worth mentioning that after triggering any SDP change for the subscriber (even unsubscribe from video) datachannel is fixed.
The text was updated successfully, but these errors were encountered:
Yes, that line definitely needs to be removed: it's already in the code that handles the removal of the streams in the following lines, when a subscription becomes completely empty, which is the only place where it should be. In fact, ready is set back to 1 if subsequent renegotiations add media again.
I'll have to check if the ready=1 thing is done when re-subscribing to datachannels as well, though, as IIRC it currently checks the media direction, which doesn't change for datachannels.
Working scenario:
"body": { "streams": [ { "feed": 8532500667596649, "mid": "1" } ], "request": "unsubscribe"
Not working scenario:
1.subscribe to many publisher's video and data channels.
2. Unsubscribe from one of subscribed publishers by sending:
"body": { "streams": [ { "feed": 8532500667596649, "mid": "1" } ], "request": "unsubscribe"
result:
3. We are not receiving any data channel messages from any publisher.
4. subscribe to data channel again not working, messages are not flowing.
expected:
3. We are not receiving data channel messages from this publisher, however, the rest of them are working
4. subscribe to data channel again enables messages from this publisher.
tested on latest multistream: f976215
Worth mentioning that after triggering any SDP change for the subscriber (even unsubscribe from video) datachannel is fixed.
The text was updated successfully, but these errors were encountered: