mumble-voip/mumble

Add an option to selectively allow UDP in either sending or receiving

Open

#5,517 opened on Jan 23, 2022

View on GitHub
 (3 comments) (1 reaction) (0 assignees)C++ (1,062 forks)batch import
clientfeature-requestgood first issue

Repository metrics

Stars
 (5,642 stars)
PR merge metrics
 (Avg merge 6d) (7 merged PRs in 30d)

Description

Context

#4881

I'm operating a worldwide server and there are unique connectivity issue in different regions. I want to ensure that users have best voice quality while under connection budget, and that involves different settings for different regions.

Description

I need to have individual switches that controls the inbound and outbound UDP connections.

Mumble component

Client

OS-specific?

No

Additional information

There might be ways to automatically detect this but I have seen the connection detail of a few users having issue and the UDP packet statistics does not show large drops. Having individual switches helps make the situation more manageable.

Or it's better if we can let server decide this via the IP address of the user or other measures.

Contributor guide

Research direction
Investigate the existing UDP toggle logic in the Mumble client codebase (likely in Mumble.proto or related audio files) and identify where send and receive UDP settings could be separated. Look for existing configuration options (e.g., in Settings.h) and how they affect the UDP component. Propose a design for independent switches and consider UI changes in the settings dialog.
Tech stack
None
Domain
desktop
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
GitC++
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30