Manage
Security and Compliance
Edited
Everything you need to know for Pleneo network setting.
Everything to provision before a Pleneo room is installed. Give it to whoever approves network changes.
Download
Switch ports
Device | PoE |
|---|---|
RoomHub | PoE (802.3af) |
RoomVision | PoE (802.3af) |
RoomVision XL | PoE+ (802.3at) |
RoomDesign Ceiling | PoE 8 W, or PoE+ 22 W for higher output |
Sonia Amp | PoE+ (802.3at) |
All devices are powered over Ethernet. No mains outlet at the device.
802.1X: supported on the Pleneo device hub, EAP-TLS.
Addressing
The Pleneo device hub has two isolated ports, no bridging. LAN 1 carries control and internet. LAN 2 carries audio and video.
DHCP: enabled by default on all ports.
Link-local fallback: on both ports, 169.254.x.x/16, when no DHCP server answers.
Static: addresses can be set per port on the device, in the web interface.
VLAN: segmentation is supported on both device hub ports. LAN 1 and LAN 2 are intended for separate, segmented networks.
Firewall rules
LAN 1
# | Direction | Source → Destination | Port |
|---|---|---|---|
1 | In | Admin computer → Pleneo device hub | TCP 443 |
2 | In | Pleneo devices → Pleneo device hub | UDP 19153 |
3 | In | PTZ cameras → Pleneo device hub | UDP 45 |
4 | Out | Pleneo device hub → Pleneo Cloud | TCP 443 |
5 | Out | Pleneo device hub → Pleneo devices | TCP 443, TCP 19150–19152 |
6 | Out | Pleneo device hub → third-party devices | TCP 45, TCP 2202 |
7 | Out | Pleneo device hub → PTZ cameras | UDP 52381 |
Rules 1 and 4 are TLS 1.2+. Rules 2, 3, 5, 6, and 7 are control traffic that never leaves the local network. DHCP (UDP 67 and 68) needs no rule.
LAN 2
Purpose | Multicast group | Port |
|---|---|---|
Clock (PTP) | 224.0.1.129–132 | UDP 319, 320 |
Audio flows | 239.69.0.0/16, 239.255.0.0/16 | UDP 5004, 4321 |
Discovery | 224.0.0.251, 239.255.255.255 | UDP 5353, 9875 |
Permit these groups rather than all multicast.
Media network setup
Real-time audio is multicast, bidirectional UDP on dynamic ports, local only. LAN 2 needs a managed switch.
IGMP snooping enabled, with forwarding of unregistered multicast disabled.
One IGMP querier on the VLAN, on a switch near the root of the topology. Only one.
IGMPv2 or later; IGMPv3 falls back to v2.
Gigabit throughout, with non-blocking fabric on busy switches.
Energy-efficient Ethernet disabled, as it adds delay variation and disturbs clocking.
Network audio integration
Where the room joins a wider networked audio system, a PTP clock (IEEE 1588-2008) also runs on LAN 2: default profile, domain 0, sensitive to delay variation.
Priority marking: clock 46 (EF) in the highest-priority queue, audio 34 (AF41), all other traffic 0 (BE). Switches must apply layer-3 DiffServ QoS, not layer-2 CoS.
Some audio devices mark clock 56 (CS7) and audio 46 (EF) instead. Confirm the values in use before writing the QoS policy.
Internet
Rule 4 only. Needed for remote management, monitoring, and firmware updates, not for the room to work.
Allow by domain, not by IP. Request the current domain list from Pleneo Support.
The connection must not be filtered or intercepted. Pleneo Cloud uses HTTPS only.
No inbound connection from the internet is required. No public IP on any device.
Security and data
All audio, video, and meeting content stays local. AI processing is done on the Pleneo device hub.
Pleneo Cloud receives only statistics on device health, status, and usage analytics.
Pleneo Cloud is hosted on Microsoft Azure. Pleneo holds and complies with SOC 2 Type 2, ISO/IEC 27001, and ISO/IEC 42001.
Access is role-based, and all access is logged.
Rooms run fully without internet access, including in air-gapped environments.