Contact us Book a demo
Guide · Network admins

Network Configuration Guide

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

Network configuration details

Servers, ports, and protocols

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

# Address Port Protocol Direction
1deskmanagement.azurewebsites.net443HTTPSOutbound
2eusfuncapp01.azurewebsites.net443HTTPSOutbound
3north-america.pool.ntp.org123NTPOutbound
4eushub01.azure-devices.net443HTTPSOutbound
5eushub01.azure-devices.net8883MQTTOutbound
Communication flow

What happens at boot

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

Diagram of the six-step Desk Sign communication flow: power on, connect to Embrava Cloud, pull config from Function App, sync time via NTP, register with IoT Hub, then sync bookings via MQTT.
  1. The Desk Sign is powered on for the first time.
  2. 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.azurewebsites.net/ on port 443 (TCP).
  3. The Desk Sign then pulls down its configuration from its home Function App using a REST API at https://eusfuncapp01.azurewebsites.net/ on port 443 (TCP).
  4. The Desk Sign then determines its current time using public time server north-america.pool.ntp.org on port 123 (UDP).
  5. 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://eushub01.azure-devices.net on port 443 (TCP).
  6. Once the Desk Sign receives its configuration, it begins to synchronize bookings with its configured desk by communicating with the IoT Hub at eushub01.azure-devices.net using the MQTT protocol on port 8883 (TCP).