Spectera Base Station
In order to use the Spectera Base Station device in a network, certain ports must be enabled (especially for the organization/enterprise firewall) for communication between software and devices.
Port requirements
| Address | Port | Protocol | Type | Service | Usage |
|---|---|---|---|---|---|
| Device Outbound | |||||
| ANY | 443 | HTTPS (TCP) | Unicast | Spectera Base Station API | Device Communication to Clients |
| sennheiseruserinsights.matomo.cloud
cdn.matomo.cloud |
443 | HTTPS (TCP) | Unicast | Sennheiser User Insights | Analytics of usage and operational data |
| my.nalpeiron.com | 80 | HTTPS (TCP) | Unicast | Sennheiser License Server | Activation of devices |
| ANY (see list of NTP servers) | 123 | NTP | Unicast | NTP Time Sever | Synchronize system time |
| 224.0.0.251 | 5353 | mDNS (UDP) | Multicast | mDNS, DNS-SD | (optional - if desired) Device/Service Discovery |
| ANY (see list of Dante® ports) | |||||
| Device Inbound | |||||
| ANY | 443 | HTTPS (TCP) | Unicast | Spectera Base Station API | Device Communication from Clients |
| ANY (see list of Dante® ports) | Dante® audio and control data | ||||
NTP servers
To correctly operate with licenses and certificates, the Spectera Base Station needs a correct system time. The device will use the well-established NTP mechanism from the IP protocol stack to synchronize clock between a time server in a network and the client inside the device.
Currently for an IT administrator or system integrator it is not possible to manually configure a dedicated NTP server to be used by the Spectera Base Station. Being able to configure a dedicated NTP server manually is a planned feature for an upcoming release.
- If a time server configuration has been provided via DHCP or manually, it tries to connect and sync to that time server first.
- Otherwise the device is trying to access any server of following list of time server pools worldwide publicly available.
- pool.ntp.org
- time.nist.gov
- time.aws.com
- time.cloudflare.com