Member Avatar for Dean_5

What it says on the tin.
I'm looking for a good voice/chat server I can run on a RasPi 3 running Raspbian Jessie. TeamSpeak is Intel only as best I can tell.
EDIT: Dangit. Every single time I jump on this forum thinking "These guys will know, but let me do a little bit more research first while I write this question..." Apparently Mumble's server Murmur can run on RasPi. nvm

  • 2 Contributors
  • 1 Reply
  • 402 Views
  • 12 Hours Discussion Span
  • Latest Post Latest Post by rproffitt

Dani AI

Generated

Good spot, — Murmur is the usual lightweight, low-latency choice for a Raspberry Pi host and it covers both Win32 and *nix clients. Below are concise, practical points that fill some common gaps people hit when putting Mumble on a Pi, plus a couple of alternatives to consider. Also note ’s moderation tip: marking the thread answered helps future searchers.

Start-up and reliability

  • Use the distribution server package (the server binary is commonly called murmurd; packages are often named mumble-server or murmur) or build a newer Mumble if the repo is old. On Raspbian Jessie the service is managed by systemd.
  • Edit the server config file (commonly murmur.ini or mumble-server.ini) to set server name, listening port and connection limits. Reserve a static LAN IP or a DHCP reservation for the Pi, and forward port 64738 (UDP; TCP also if configured) on the router for external clients.

Practical troubleshooting checklist

  • Can’t connect from outside? Verify a local client on the same LAN first to rule out server problems. Then check router NAT/port-forwarding for 64738 and any host-based firewall on the Pi.
  • Poor audio or high CPU? Choose the Opus codec if available and lower per-user bandwidth/quality in the server config; monitor CPU with top to see if encoding is saturating the Pi.
  • Preserve identity: back up the server identity/cert file before upgrades so user registrations and server identity survive reinstalls.
  • Recording/logging is not a core server feature; use a client-side bot or separate recorder if persistent recording is needed.

When Murmur is not enough
SIP servers (Asterisk, FreeSWITCH) add phone/bridging features but are heavier and require SIP clients. WebRTC solutions (Jitsi) provide browser access but use more CPU and bandwidth. For a small, low-latency voice server on a Pi, Murmur is typically the best first choice. Mark the thread answered once the setup is confirmed so others find the solution quickly.

Member Avatar for rproffitt

Just a small thing. Try to mark your answered posts answered if can.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.