Home
Knowledge Base
Central hub for information, resources, and guides with further content on the product and/or service.
Cloud connectivity guide
This document provides AV /IT professionals with step-by-step guidance on enabling cloud connectivity for the TeamConnect Bar (TC Bar) and preparing it for integration with Sennheiser DeviceHub, Sennheiser's cloud-based device management platform.
Preparing the TC Bar for cloud connectivity
To enable cloud connectivity for TC Bar devices, ensure the latest firmware is installed and configure the necessary network settings and outbound ports as specified.
Required outbound ports (DeviceHub)
Sennheiser DeviceHub relies on Microsoft Azure IoT Hub for connections established by the TC Bars.

Knowledge Base
Central hub for information, resources, and guides with further content on the product and/or service.
- FAQ
  The most frequent questions and answers summarized in a chapter.
- Cloud connectivity guide
  This document provides AV /IT professionals with step-by-step guidance on enabling cloud connectivity for the TeamConnect Bar (TC Bar) and preparing it for integration with Sennheiser DeviceHub, Sennheiser's cloud-based device management platform.
  - Preparing the TC Bar for cloud connectivity
    To enable cloud connectivity for TC Bar devices, ensure the latest firmware is installed and configure the necessary network settings and outbound ports as specified.
    - Network modes
      This chapter outlines the network communication options for TC Bars S and M, including Single Domain, Dual Domain, and Split Modes, along with guidance for configuration.
    - Required outbound ports (DeviceHub)
      Sennheiser DeviceHub relies on Microsoft Azure IoT Hub for connections established by the TC Bars.
    - Optional ports (Control Cockpit)
      Enable specific firewall ports to perform firmware updates of the TC Bar using Sennheiser Control Cockpit software.
    - Installing the firmware
      Follow these steps to install the firmware for the TC Bar using Sennheiser Control Cockpit on Windows, ensuring to remove any previous firmware versions to avoid conflicts.
  - Known Issues
    This document outlines known issues and pitfalls related to firmware, time synchronization, third-party access, and provides supportive links for troubleshooting TC Bars.
- Security white paper
  This document aims to provide information about the security and data privacy of DeviceHub to facilitate the onboarding in our customers’ IT environments.

Required outbound ports (DeviceHub)

Sennheiser DeviceHub relies on Microsoft Azure IoT Hub for connections established by the TC Bars.

The following network protocols and ports are required for the Sennheiser cloud connectivity over the TC Bar control network.


IPv4	Port	Protocol	Service / FQDN	Service Tag
_{52.166.23.94 (EMEA) 104.211.55.78 (AMER) 20.239.51.210 (APAC)}	₄₄₃	_HTTPS	_{Device Enrollment Service} _{api.cloud.sennheiser.com}	_N/A
_Dynamic*	₄₄₃	_{MQTT over WebSockets}	_{IoT Region EMEA} _{iot-senn heiser-prod-emea.azure-devices.net}	_{AzureIoTHub.WestEurope}
_Dynamic*	₄₄₃	_{MQTT over WebSockets}	_{IoT Region APAC} _{iot-sennheiser-prod-apac.azure-devices.net}	_{AzureIoTHub.EastAsia}
_Dynamic*	₄₄₃	_{MQTT over WebSockets}	_{IoT Region AMER} _{iot-sennheiser-prod-amer.azure-devices.net}	_{AzureIoTHub.EastUS}

_{All device communication is secured with current TLS/SSL.}

*Dynamic IPv4:

The IP addresses of Azure IoT Hubs are dynamic and may change without prior notice.

Use FQDNs (fully qualified domain names) if supported by your firewall or
check the Microsoft Azure Service Tags to retrieve the current IP ranges by searching for the specified Service Tag:
- Download the complete Service-Tags list from www.microsoft.com/download.
- In the downloaded .json file, search for the Service Tag corresponding to your IoT Hub region. If you are unsure or operating in multiple regions, you may enable all three IoT Hub regions.

Currently, only direct connection (MQTT; port 443) is supported. The connection type "behind HTTPS proxy" is not supported by the TC Bar. The URLs provided are for reference only.

Important: IPv6 connectivity is not yet supported. Devices must use IPv4 for all outbound communication. This is particularly relevant for environments where IPv6 is common, such as mobile networks (e.g., SG). Please ensure your network allows IPv4 traffic for the required ports and domains.