Network & devices
What Muxvox needs, and what to do when Wi-Fi fights back.
Muxvox runs entirely on your local network. That makes it fast and private — and it means the network is the one thing that can get in the way. This page is the honest manual.
Requirements, complete list
- Phones and the Mac on the same local network, able to reach each other (see isolation, below).
- UDP port 7443 open between devices — this carries the encrypted audio. No inbound internet access is needed, ever.
- Bonjour/mDNS for automatic discovery — optional: when multicast is blocked, connect by the address Muxvox Desktop shows.
- Internet access is needed only for downloads, updates and paid-plan checks (with a week of offline grace). Meetings themselves survive a full internet outage — your meeting app permitting.
Supported devices
- Mac — macOS 13 or later, Apple silicon and Intel. Windows is on the roadmap, honestly not started.
- iPhone — the current Muxvox app from the App Store; echo cancellation built in and always on. Bluetooth headsets that force call-mode audio (HFP) are not supported yet — wired headphones, AirPods in music mode, or the phone itself all work.
- Android — the current app from Google Play; echo-cancellation toggle in Settings. On Android 16 the app asks for the new local-network permission — say yes, or the desktop stays invisible.
- Per session: up to 2 phones on Personal, up to 16 on Team. “Check the room” covers the first four phones.
“My phone can’t find the desktop”
Nine times out of ten: client isolation — a network setting, common on guest and office Wi-Fi, that blocks devices from seeing each other. Both devices are online; they just can't talk.
- Check both devices are on the same network — not one on guest Wi-Fi and one on corporate, not the Mac on Ethernet with a different VLAN.
- Try connect-by-address: Muxvox Desktop shows its address under the session name; enter it on the phone under Settings → Connect by address.
- Still nothing? The network blocks device-to-device traffic entirely. Two ways out: ask IT to allow peer traffic on the meeting-room SSID (UDP 7443 + mDNS), or make your own room network — a phone's hotspot with the Mac joined to it works fine for a meeting.
For IT departments
- Allow device-to-device UDP on port 7443 within the meeting-room SSID/VLAN, plus mDNS (UDP 5353) for discovery.
- No inbound rules, no cloud relay, no VPN considerations: audio never leaves the local network and is DTLS-encrypted on it. See the security overview.
- Outbound HTTPS to
api.muxvox.iofrom the Mac only (not phones), for license checks and updates. Blocking it does not stop meetings; paid features ride a cached entitlement with a week of grace.