this post was submitted on 08 Nov 2023
2 points (100.0% liked)
Home Networking
11 readers
1 users here now
A community to help people learn, install, set up or troubleshoot their home network equipment and solutions.
Rules
- Please stay on topic.
- Please use the search function to look for keywords related to what you want to ask before posting since most common issues have been answered.
- No Ads. This community is for support and discussion. Ads and self promotion are not welcome here.
- No product reviews or announcements. If you have a question about a product, be specific about what you want to know.
- Be civil. Don't be a jerk. Not being a jerk is surprisingly easy.
- No URL shorteners. URL shorteners tend to hide the real use of a link. For this reason, please use normal links, even if they're long.
- No affiliate links.
- No gatekeeping. With profession shall come professionalism. Extend help without judging others for their ignorance. The same goes for downvoting of comments or posts for "stupid questions" or not being as knowledgeable as others.
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
All your equipment and connections are so incredibly overkill for "audio only calls" that I wouldn't bother looking for any problems there. Maybe there is some program or docker container that is running wild and maxxing out you Mac's CPU to 100%. Maybe a really bad microphone or headset. Otherwise, your setup won't even blink at an audio only teams call. We're talking <1% usage across all systems for audio communications.
It's also hard to suspect a 2 Gbps fiber connection as the culprit.
I'd try a different microphone and headset, or a different connection to them (Bluetooth or USB or even Ethernet/ VOIP). I'd suspect Bluetooth as the possible problem if in use.
I just wouldn't even suspect your Mac or network is the issue, or if it is the network, it'll be so far up into the Internet chain that you cannot fix it yourself.