NETWORK
CONFIGURATION GUIDE

Network Configuration
Details

The purpose of this section is to provide the US Census Bureau network team with the servers, ports and protocols that need to be enabled through their network infrastructure to allow the Embrava Desk Sign to successfully communicate with their Embrava Device Management System (DMS).

The following section illustrates the order in which these servers are accessed by the Desk Sign.

Communication Flow

The purpose of this section is to illustrate the steps the Desk Sign utilizes to boot up and display the availability of a workspace.

#

Description

1

The Desk Sign will automatically connect to the Embrava Cloud requesting its home Function App and IoT Hub using a REST API at https://deskmanagement.azure-api.net/ on port 443 (TCP)

2

The Desk Sign then pulls down its configuration from its home Function App using a REST API at    https://eaufuncapp01.azurewebsites.net/ on port 443 (TCP).

3

The Desk Sign then determines its current time using public time server north-america.pool.ntp.org on port 123 (UDP).

4

The Desk Sign then attempts registration with the IoT Hub endpoint received from the Embrava Cloud in Step 2. This is done using a REST API at https://eauhub01.azure-devices.net on port 443 (TCP).

5

Once the Desk Sign receives its configuration, it begins to synchronize bookings with its configured desk by communicating with the IoT Hub at eauhub01.azure-devices.net using the MQTT protocol on port 8883 (TCP).

6

The Desk Sign will download an updated firmware package when it is instructed to via the DMS Admin Portal. This is done securely at https://raw.githubusercontent.com on port 443