Communication flows
Overview of the communication flows between Sennheiser devices and DeviceHub.
The connection to DeviceHub is disabled by default on the
Sennheiser devices in order limit the attack surfaces of a device in a factory
default state.
Below you can find relevant information for understanding the communication flows between devices and Sennheiser DeviceHub.

Sennheiser DeviceHub utilizes Microsoft Azure IoT Hub for connections established by the Sennheiser devices. The following network protocols and ports are required for the Sennheiser cloud connectivity over the device control network.
All device communication over HTTPS and MQTT is secured with TLS
1.2 or higher.
| IPv4 | Port | Protocol | Service / FQDN |
|---|---|---|---|
| Device Enrollment Service | 443 | HTTPS | api.cloud.sennheiser.com |
| Azure IoT Hub, EMEA (Europe, Middle East and Africa) | 443 | MQTT over WebSockets |
iot-sennheiser-prod-emea.azure-devices.net |
| Azure IoT Hub, APAC (Asia and Pacific regions) | 443 | MQTT over WebSockets |
iot-sennheiser-prod-apac.azure-devices.net |
| Azure IoT Hub, AMER (Americas) | 443 | MQTT over WebSockets |
iot-sennheiser-prod-amer.azure-devices.net |
| Firmware Update Service | 443 | HTTPS | updates.sennheiser.com |
| Network Time Synchronization | 123 | NTP | Default: time.cloudflare.com, time.nist.gov |
| Domain Name Service | 53 | DNS | User configurable |
