Skip to main content

Communication

List of ports that are required for UCS to run properly.

For functional auto-provisioning, you need to set Option 66 (TFTP server name) on the DHCP server

warning

DHCP Option 66 must be of type String/Text

Services provided by the exchange

The following services are provided by UCS. On the firewalls, permutations are therefore set up on UCS, communication is initiated by IP telephones, users, telephone operators, external parties IS, etc.

PortProtocolComm. initiation directionServiceUsesPurpose
22tcp* -> IP UCSSSHadministratorsadministration
53udp* -> IP UCSDNSIP phonesXML services on IP phones
67udp* -> IP UCSDHCPIP phonesIP address allocation
69udp* -> IP UCSTFTPIP phonesprovisioning
80tcp* -> IP UCSHTTPadministrators, operators, IP phonesredirect to HTTPS
123udp* -> IP UCSNTPIP phonestime synchronization
443tcp* -> IP UCSHTTPSadministrators, operators, IP phonesmanagement, use of telephony
514udp* -> IP UCSSyslogIP phoneslogging in
3478udp* -> IP UCSSTUN/ICEWeb SoftphonesNAT detection
5060udp* -> IP UCSSIPIP phones, PBX trunkscall joining
5061tcp* -> IP UCSSIP/TLSIP phones, PBX trunkscall joining
10000-20000udp* -> IP UCSRTPIP and SW phones, PSTN and PBX trunksvoice and video transmission

Observability stack (internal)

The observability stack (Grafana, Loki, Tempo, Prometheus, OpenTelemetry Collector) is installed automatically with UCS — see Observability. These services listen on all interfaces but are typically used over localhost. If you ship telemetry between hosts (e.g. an agent on one node pushing to a central collector elsewhere), open the relevant OTLP ports on the firewall.

PortProtocolServicePurpose
3030tcpGrafanaWeb UI under /grafana/ (direct; usually proxied through Traefik on :443)
3100tcpLokiHTTP API — log ingestion and query
3200tcpTempoHTTP API — trace query
4317tcpotelcol-contribOTLP gRPC — telemetry ingestion from applications
4318tcpotelcol-contribOTLP HTTP — telemetry ingestion from applications
4319tcpTempoOTLP gRPC — trace ingestion from the collector
9091tcpPrometheusHTTP API — metrics query and OTLP remote-write receiver

External clients (web pages, mobile apps) can push telemetry over HTTPS through Traefik on port 443, at the path /otel/v1/{traces,metrics,logs} — Traefik strips the /otel prefix and forwards to the local collector.

Services used by the exchange

The following services are used by UCS. On the firewalls, permutations are therefore set up from UCS, communication is initiated by UCS towards telephones, telephone operators, to external IS, to Microsoft Active Directory, etc.

PortProtocolComm. initiation directionServiceTarget SystemPurpose
53udpIP UCS -> *DNSDNS of the company (e.g. AD) or on the InternetOS update
80tcpIP UCS -> *HTTPInternetOS update
123udpIP UCS -> *NTPCompany's NTP (eg AD) or on the Internettime synchronization
443tcpIP UCS -> *HTTPSinformation systems, Internetintegration, OS update
514udpIP UCS -> *SyslogLog server (eg Kibana/Logstash etc.)logging in
5060udpIP UCS -> *SIPIP phones, PBX trunkscall joining
10000-20000udpIP UCS -> *RTPIP phones, PSTN and PBX trunksvoice and video transmission