Skip to content

RPC changes for ingress proxy WHIP#1194

Merged
cnderrauber merged 6 commits into
mainfrom
whip_notify
Sep 9, 2025
Merged

RPC changes for ingress proxy WHIP#1194
cnderrauber merged 6 commits into
mainfrom
whip_notify

Conversation

@cnderrauber
Copy link
Copy Markdown
Contributor

  • Sfu notify ingress about WHIP webrtc connection closed
  • Sweeper delete whip session on sfu
  • Add sub_skip_reference_ts in participant info if the publisher's rtcp sr is incomplete for simulcast (will be set for obs whip session)

@cnderrauber cnderrauber requested a review from a team September 8, 2025 05:37
@changeset-bot
Copy link
Copy Markdown

changeset-bot Bot commented Sep 8, 2025

⚠️ No Changeset found

Latest commit: 3021e65

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

💥 An error occurred when fetching the changed packages and changesets in this PR
Some errors occurred when validating the changesets config:
The package or glob expression "github.com/livekit/protocol" specified in the `fixed` option does not match any package in the project. You may have misspelled the package name or provided an invalid glob expression. Note that glob expressions must be defined according to https://www.npmjs.com/package/micromatch.

Comment thread protobufs/livekit_models.proto Outdated
map<string, string> attributes = 15;
DisconnectReason disconnect_reason = 16;
repeated KindDetail kind_details = 18;
// indicates that subscriber subscribes to track of the participant can skip reference timestamps
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this should not be in ParticipantInfo. This is sent as update. Other participants need not know this. Can we move this to the request where WHIP is created from ingress?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The field is set in the WHIP handle but we need to broadcast it to all the subscribers. It is not the best place that the client sdk doesn't need to know this, but I can't find a better way to put the internal property so put it here. Do you have a suggestion place?

Copy link
Copy Markdown
Contributor

@boks1971 boks1971 Sep 8, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ah got it, sorry my bad, yeah this needs to be known to subscribers, let me think

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we add a mode here so that it gets carried with track info? TrackInfo also goes to client and clients need not know about it, but I feel keeping it at track level is a bit better and we can make it an enum so that it is not a separate field.

Something like ONE_SPATIAL_LAYER_PER_STREAM_NO_RTCP_SENDER_REPORT or something like that (sorry, that name is horrible :-) )

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

will look at it

@cnderrauber cnderrauber merged commit 48ed047 into main Sep 9, 2025
5 checks passed
@cnderrauber cnderrauber deleted the whip_notify branch September 9, 2025 05:04
cnderrauber added a commit to livekit/livekit that referenced this pull request Sep 9, 2025
cnderrauber added a commit to livekit/livekit that referenced this pull request Sep 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants