This document serves as a comprehensive guide that outlines the steps required to integrate Sennheiser devices compatible with SSCv2 (Sennheiser Sound Control Protocol version 2) with the NetSpeek platform.

Prerequisites

Before beginning the integration, confirm the following:

• Your Sennheiser device is powered on and connected to the same network as your NetSpeek Edge VM.
• You have deployed a NetSpeek Edge VM as described here: https://docs.netspeek.ai/netspeek-edge-installation-guide/
  • Note: This integration requires an Edge running software version 1.1 or later.
• Note that this integration guide is intended for Sennheiser devices compatible with the SSCv2 protocol, such as the room systems, microphone devices, and wireless receivers described in Sennheiser’s documentation here: https://docs.cloud.sennheiser.com/en-us/api-docs/api-docs/sscv2-specification-2.3.html
  • Some devices can use either the SSCv1 or SSCv2 protocol depending on their firmware version, whereas others use only v1 or v2 regardless of firmware. See the extended prerequisites below for details about supported devices and determining which integration method to use.
  • This is the v2 page – for v1, see: https://docs.netspeek.ai/device-platform-integration-guides/sennheiser-integration-guide-sound-control-protocol-v1-sscv1/
• This guide assumes the Sennheiser equipment is deployed and operational, and ready for third-party control. Steps to achieve this, such as initial configuration via Sennheiser Control Cockpit, are addressed by Sennheiser and are outside the scope of this guide.

---

Extended Prerequisites – Sennheiser Device Models Supported (SSCv2)

Wireless Receivers:

• EW-DX EM line (firmware versions later than 4.0)

Microphones:

• TCC M

UC Room Video Bars: 

• TC Bar S
• TC Bar M

Extended Prerequisites – Choosing between SSCv1 and SSCv2

Use this SSCv2 guide when the device uses Sennheiser Sound Control Protocol v2, and connectivity is on TCP port 443. Some EW-DX models support either v1 or v2 integrations depending on installed firmware; attempting to configure a v1-based integration for a v2-compatible device, or vice versa, is a common setup problem. See the table and note below for further detail.

Devices	Supports SSCv1	Supports SSCv2
TeamConnect Ceiling 2, SL DW receivers, CHG 2N / 4N / 70N	Yes (Network port UDP 45)	No
EW-DX EM line with firmware < 4.0	Yes (Network port UDP 45)	No
EW-DX EM line with firmware > 4.0	Yes (If legacy API is enabled) (Network port UDP 45)	Yes (If Secure API is enabled in Cockpit) (Network port TCP 443)
TCC M, TC Bar S, TC Bar M	No	Yes (If Secure API is enabled in Cockpit) (Network port TCP 443)

---

Step 1. Enable V2 API: 3rd Party API Access in Control Cockpit

Enabling the Secure API in Control Cockpit is required for SSCv2 only. It is not required for SSCv1.

1. Navigate to the Cockpit’s Devices Tab. Select the Access tab in the Properties panel.
2. Locate the 3rd Party Access panel:
   • To enable V2 API controls:
     • Click Edit 
     • Configure Secure API: Enabled
     • Configure Username: api
       • This username cannot be changed
     • Configure Password:  <your-device-password>
     • Click OK to complete the configuration.

Step 2. Add Device to NetSpeek Room Canvas

Device Provisioning Flow

1. In the NetSpeek Console, navigate to Room Management
2. Select the room you wish to add your Sennheiser Device to
3. Click Launch Room Canvas
4. Click Add device to room
5. Choose your desired Sennheiser SSCv2-compatible device from the manufacturer → device model list.
6. Configure the appropriate values, and in the “Integrations” section, select a previously created NetSpeek Edge VM integration. Ensure that the Edge VM is on a network that can reach the device’s configured IP address.
7. In the configuration panel, enter the following fields:
   • Device IP Address (static/reserved IP, or DHCP)
   • Device Port: 443
   • Device Username: matches the api username described in the prior step
   • Device Password: matches the device password described in the prior step
   • TLS/HTTPS Enabled (Optional)

Verification

Once the relevant settings described above are configured, to validate the integration:

• Select a Sennheiser device in the NetSpeek console, open the Device Actions Tab, and select an available device action. It is generally advisable to test by dispatching a non-intrusive command such as a Get Status.
• On the device, observe the selected action occurring.

---

Troubleshooting

Connection Issues

• Confirm the IP address is correct and routable from the network segment where the NetSpeek Edge VM is deployed.
• Ensure outbound port TCP 443 is not blocked by firewall rules on the machine running your NetSpeek Edge VM. All NetSpeek SSCv2 integrations use TCP 443.
• Confirm Secure API is enabled in Control Cockpit and that the username is api.
• Follow the model-specific setup documentation from Sennheiser for guidance when configuring the device’s connection and network settings.

---

Support

If you run into any issues during onboarding or have questions, contact NetSpeek Support at support@netspeek.com.