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 UCS​

The following services are provided by UCS. Open these ports on the firewalls towards UCS: the communication is initiated by IP phones, users, telephone operators, external information systems, etc.

PortProtocolServiceUsesPurpose
22tcpSSHadministratorsadministration
53udpDNSIP phonesXML services on IP phones
67udpDHCPIP phonesIP address allocation
69udpTFTPIP phonesprovisioning
80tcpHTTPadministrators, operators, IP phonesredirect to HTTPS
123udpNTPIP phonestime synchronization
443tcpHTTPSadministrators, operators, IP phonesmanagement, use of telephony
514udpSyslogIP phoneslogging
3478udpSTUN/ICEWeb softphonesNAT detection
5060udpSIPIP phones, PBX trunkscall signalling
5061tcpSIP/TLSIP phones, PBX trunkscall signalling
5090udpSIPSBC, recording interface (SIPREC)SIPREC call recording
10000-20000udpRTP/SRTPIP and SW phones, PSTN and PBX trunksvoice and video transmission
30000-30999udpRTPSBC, recording interface (SIPREC)SIPREC call recording

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 UCS​

The following services are used by UCS. Open these ports on the firewalls from UCS: UCS initiates the communication towards phones, telephone operators, external information systems, Microsoft Active Directory, etc.

PortProtocolServiceTarget systemPurpose
53udpDNSDNS of the company (e.g. AD) or on the InternetOS update
80tcpHTTPInternetOS update
88tcp, udpKerberosMicrosoft Active Directoryuser authentication (SSO)
123udpNTPCompany's NTP (eg AD) or on the Internettime synchronization
443tcpHTTPSinformation systems, Internetintegration, OS update
514udpSyslogLog server (eg Kibana/Logstash etc.)logging
636tcpLDAPSMicrosoft Active Directoryuser synchronisation
5060udpSIPIP phones, PBX trunkscall signalling
10000-20000udpRTP/SRTPIP phones, PSTN and PBX trunksvoice and video transmission