BYOD — Bring Your Own Device
Bring Your Own Device
See also: ucc — the conferencing platforms BYOD connects into, and mtr — dedicated room systems as the alternative to BYOD.
BYOD means enabling participants to use personal laptops, tablets, or smartphones to present content or join meetings without relying on a fixed, IT-provisioned endpoint. In modern AV design, BYOD is a baseline expectation — users arrive with their own devices and expect to be on screen and in the call within seconds, regardless of what platform they are running.
Connection Methods
BYOD connectivity falls into three distinct approaches, each with different infrastructure requirements and trade-offs.
Wired Connections
HDMI and USB-C table connections provide the most reliable, lowest-latency path for BYOD. USB-C with DisplayPort Alt Mode or Thunderbolt is the current standard — a single cable delivers video, audio, power, and USB data simultaneously. This is why USB-C connection bars and table connection boxes dominate new installations: one cable makes the laptop a room endpoint, charging it and extending audio/video to the room system in one step.
HDMI remains necessary for older laptops and when USB-C Alt Mode is not available. Table connection boxes (Extron DTP, Crestron HD-TXC, Biamp Devio) mount at the table surface and run structured cabling back to the rack.
Always plan for adapters: USB-C-to-HDMI, USB-C-to-USB-A, and USB-C-to-DisplayPort adapters stored at the table reduce friction for users with legacy ports.
Wireless Screen Sharing
Wireless BYOD eliminates cable management and works from anywhere in the room, at the cost of higher latency and infrastructure requirements.
| System | Ecosystem | Infrastructure Needed | Latency | Notes |
|---|---|---|---|---|
| AirPlay 2 | Apple only | Wi-Fi AP or Apple TV | ~100-200ms | Native on Mac/iPad; no app install |
| Miracast | Windows/Android | Wi-Fi Direct (no AP needed) | ~100-200ms | Built into Windows; variable quality |
| Google Cast | Android/Chrome | Wi-Fi AP + Chromecast | ~200ms | Native on Android/Chrome browser |
| Barco ClickShare | Cross-platform | ClickShare base unit + Wi-Fi | ~50-100ms | Physical button or app; CX series joins meetings |
| Mersive Solstice | Cross-platform | Solstice Pod + Wi-Fi | ~100ms | App required; strong IT management dashboard |
| Crestron AirMedia | Cross-platform | AirMedia receiver + Wi-Fi | ~100-200ms | Integrated with Crestron control systems |
| Extron ShareLink | Cross-platform | ShareLink Pro + Wi-Fi | ~100ms | No app required for basic sharing |
Proprietary systems (ClickShare, Solstice, AirMedia) are the most reliable cross-platform options. Native protocols (AirPlay, Miracast) have uneven quality depending on network environment and firmware.
Network-Based Conferencing (BYOH)
BYOH (Bring Your Own Host) extends BYOD into conferencing: the personal device runs the meeting app (Teams, Zoom, Webex) and the room audio/video hardware connects as USB peripherals. A USB cable from the room camera, microphone bar, and speaker connects to the laptop, making those devices appear as USB webcam, mic, and speaker in the meeting app.
This uses room hardware quality with the user's preferred platform — no room system license required. The downside: every meeting requires the laptop physically present and connected.
BYOD and VLAN Design
BYOD devices must be isolated from AV infrastructure and corporate devices. The standard architecture uses three separate VLANs:
- Corporate VLAN — managed endpoints, printers, servers; no BYOD access
- AV VLAN — Dante, control systems, DSPs, room endpoints; no BYOD access
- BYOD/Guest VLAN — BYOD laptops, phones, tablets; internet access only
Wireless receivers (ClickShare, Solstice, AirMedia) bridge the traffic: the base unit sits in the AV VLAN and has a dedicated Wi-Fi radio in the BYOD/Guest space. NAC enforces VLAN assignment by device identity automatically.
See vlan-configuration-for-av for VLAN design specifics.
Security Considerations
HDCP enforcement — Content from streaming services on a personal laptop is HDCP-protected. HDCP 2.2 must be supported end-to-end through the entire signal chain. Older HDMI switchers that do not pass HDCP 2.2 will blank the image for protected content. See hdcp.
Captive portal friction — Guest VLAN with captive portal breaks AirPlay and Miracast discovery, which rely on mDNS broadcast on the local subnet. If wireless BYOD presentation is required, use a BYOD SSID without a captive portal but with bandwidth limits and client isolation.
Unauthorized sharing — Wireless presentation systems that accept any connection without a PIN can display content from devices in adjacent rooms. ClickShare, Solstice, and AirMedia all support PIN or proximity-based pairing to prevent unintended sharing.
Common Pitfalls
- No adapter plan — A USB-C-only room where half the users have older HDMI laptops will fail constantly. Stock adapters at every table or install multi-port connection boxes with both USB-C and HDMI inputs.
- BYOD on corporate VLAN — Personal devices on the corporate network violate security policy and expose corporate resources. Always route BYOD to an isolated VLAN.
- Wireless presentation and VPN conflicts — VPN clients on BYOD laptops tunnel all traffic off the local network, breaking mDNS discovery for AirPlay and Miracast. Users with active VPN cannot wirelessly present without a proprietary app (ClickShare, Solstice) that routes outside the VPN tunnel.
- Double AEC in BYOH rooms — When the laptop meeting app and the room DSP both run AEC simultaneously, voices get clipped and mutilated. Only one AEC stage per audio path should be active. See aec.
- USB peripheral device conflicts — When a laptop connects via USB to the room camera and speaker bar, those devices appear in the meeting app alongside the built-in webcam and mic. The meeting app may default to built-in devices instead of room hardware. Train users to verify device selection.
- HDCP blocking wireless sharing — Miracast and some AirPlay receivers do not pass HDCP, so content from streaming apps will go black when mirrored wirelessly. Wired connection is required for DRM-protected content.