Connectivity Between The Plixus Gateway And The Central
Unit
The Plixus Gateway has to communicate with the Central Unit. The dataflows below need to be made
possible:
IP Source
Destination
Protocol / Service
Additional information
Gateway IP
address(*)
Central Unit (Plixus AE-R/MME
or Confidea WAP G4)
TCP port 9012 (http)
REST API for meeting control
(*) The Gateway IP address can be either a WAN port connection (DHCP) or a LAN port connection (DHCP).
Plixus Gateway And Central Unit Configuration
The requirements regarding the configuration of the Gateway and Plixus Central Unit within the client IT
network are as follows:
Plixus Gateway
Plixus Central Unit or G4 WAP
Type of device
Linux (Debian 10 based)
Embedded Linux device
Network connection type
WAN port (DHCP)(*)
LAN port (DHCP)(*)(**)
Static IP address
Additional devices that need
connectivity to these devices
-
All clients who need access to the Confero 360
interface, which is required for meeting management
(min. for starting a meeting).
Camera tracking solutions (for active speakers
through the API).
(*) You need a DHCP server for every port use. If both WAN and LAN are used, two DHCP
servers are needed. The Client-Identifier that is sent to the DHCP server is equal to the MAC
address of the port.
The MAC address of the WAN port can be found on the label of
the Plixus Gateway
.
The MAC address of the LAN port is equal to the MAC addres of
the WAN port + 1.
(**) The IP address of the port connected with the Central Unit must be in the same range as
the Central Unit.
IT CONSIDERATIONS
26
