nextcloud / nextcloud/spreed

Allow using peer-to-peer for one-on-one video chat

Open
#13,148 1 comment 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement feature: call 📹 feature: signaling 📶 feature: WebRTC 🚡
Dominant language
PHP
Stars
2.2k
Forks
587
Avg merge
17h 55m
Merged PRs (30d)
350

Description

How to use GitHub
  • Please use the 👍 reaction to show that you are interested into the same feature.
  • Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
  • Subscribe to receive notifications on status change and new comments.

Feature request

Which Nextcloud Version are you currently using: (see administration page)
29.0.5

Is your feature request related to a problem? Please describe.
When creating one-on-one video connections with a configured high performance backend plus video bridge (i.e. janus) the video is always routed through the janus bridge even though the clients don't have any additional benefit from that (given that they can connect to each other directly).

Describe the solution you'd like
I'd like to have the option to first try peer-to-peer connections for those one-on-one video chats to keep the bridge load to a minimum and use it only when its necessary for larger conferences.

Jitsi for example uses this technique to keep the server load low.

Describe alternatives you've considered
Depending on the typical load for the server one could just as well disable the janus gateway which would in turn make larger conferences problematic for the clients.

Additional context
I also made this request in the nextcloud-spreed-signaling project where I was redirected here, see https://github.com/strukturag/nextcloud-spreed-signaling/issues/804

Thanks for the attention and NC Talk!

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Review the existing one-on-one call routing and Janus signaling flow, along with the related nextcloud-spreed-signaling issue 804. Determine how a peer-to-peer attempt can be negotiated before bridge use and how fallback should work. Done means one-on-one calls prefer direct connections while larger conferences continue using the bridge.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
audio-video-rtc
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.