Add description, images, menus and links to your mega menu
A column with no settings can be used as a spacer
Link to your collections, sales and even external links
Add up to five columns
Add description, images, menus and links to your mega menu
A column with no settings can be used as a spacer
Link to your collections, sales and even external links
Add up to five columns
September 08, 2026 2 min read
Technical networking requirements, recommendations, and port reference for troubleshooting Juke Audio multi-room wireless audio systems.
Technical reference document for the Juke Audio wireless multi-room audio system, covering networking requirements and recommendations for reliable operation with AirPlay and Spotify, plus a full listing of ports used by the device.
This document serves as a resource for technical persons debugging network issues related to the Juke and the various services it provides (i.e. AirPlay and Spotify). It also states explicit requirements and recommendations for optimal networking configurations to ensure the Juke operates as intended on the network.
| Requirement | Rationale |
|---|---|
| Router must have multicasting enabled | Juke relies on multicast traffic to communicate with other Jukes and allow other devices to discover its services. |
| Router must have mDNS enabled | The service discovery protocols Juke employs rely on mDNS. Disabling this would prevent juke.local and various sources from being discovered. |
| Router must not block unknown multicast addresses | Juke uses a few nonstandard multicast addresses which may be considered unknown. |
| Devices must be on same subnet | Juke uses multicast traffic to advertise service availability and communicate with other Jukes. Multicast traffic is usually not routed across subnets, so the Juke must be on the same network as devices streaming to it. |
| Recommendation | Rationale |
|---|---|
| Network switches should have IGMP snooping disabled | IGMP snooping offers the benefit of optimizing which interface multicast traffic is sent to, but it also opens the opportunity for multicast traffic to be filtered or blocked. |
| The 2.4 and 5 GHz Wi-Fi should not share the same SSID | There have been past issues with Jukes not connecting properly to networks whose 2.4 and 5 GHz bands share the same SSID. |
| Port Number | Type | Protocol | Used By |
|---|---|---|---|
| 80 | TCP | HTTP (RFC 2616) | AirPlay |
| 443 | TCP | HTTPS | AirPlay |
| 554 | UDP / TCP | RTSP (RFC 2326) | AirPlay |
| 1900 | UDP | SSDP | Bonjour |
| 3689 | TCP | DAAP | AirPlay |
| 4999 | TCP | SSH (RFC 4253) | Juke SSH Port |
| 5001-5004 | TCP | — | Juke AirPlay Service Request Port |
| 6001-6004 | TCP | — | Juke Spotify HTTP Server Port |
| 5297 | TCP | — | Bonjour |
| 5298 | TCP / UDP | — | Bonjour |
| 5350 | UDP | NAT Port Mapping Protocol | Bonjour |
| 5351 | UDP | NAT Port Mapping Protocol | Bonjour |
| 5353 | UDP (multicast) | MDNS (RFC 3927) | AirPlay / Bonjour |
| 10000 | UDP (multicast) | Multi-Juke Discovery Port | Juke Multi-Juke |
| 10001 | TCP | Multi-Juke Client Port | Juke Multi-Juke |
| 38124-38127 | UDP | Client Audio Receive Port | Juke Multi-Juke |
| 49159 | UDP (multicast) | MDNS (Windows) | AirPlay / Bonjour |
| 49163 | UDP (multicast) | MDNS (Windows) | AirPlay / Bonjour |
Sign up to get the latest on sales, new releases and more …