bitlvl
EN

Port 5061 SIP over TLS · TCP

SIP over TLS (SIPS): encrypted signalling. Pair with SRTP for the media or the call content is still in the clear.

Port5061
TransportTCP
ServiceSIP over TLS
CategoryVoIP and real-time media
Rangeregistered (1024–49151)
EncryptedYes, always (TLS or equivalent)
ExposureInternet-facing only with authentication and care

What runs on port 5061

SIP over TLS (SIPS): encrypted signalling. Pair with SRTP for the media or the call content is still in the clear. Microsoft Teams Direct Routing, most SIP trunk providers and modern desk phones support it.

Software that uses it: Asterisk / FreePBX · FreeSWITCH · Kamailio · Teams Direct Routing SBCs · Cisco CUCM

Should port 5061 be open?

Internet-facing only with authentication and care. It can be exposed when the service behind it is authenticated, rate-limited and kept up to date; most deployments are better off behind a VPN, an allow-list or a reverse proxy.

Check port 5061

# on the host: is anything listening, and which process?
ss -ltnp 'sport = :5061'
sudo lsof -i :5061

# from another machine: is it reachable?
nc -zv host 5061
nmap -p 5061 host
curl -v telnet://host:5061      # raw TCP connect test, Ctrl-C to leave

A port that answers from the internet when it should not is the finding; nmap from a machine outside your network (or a VPS) is the honest test, because scans from inside the LAN pass the firewall you are trying to verify.

Allow or block port 5061

# ufw (Ubuntu/Debian)
sudo ufw allow from 10.0.0.0/8 to any port 5061 proto tcp
sudo ufw deny 5061/tcp

# nftables
nft add rule inet filter input ip saddr 10.0.0.0/8 tcp dport 5061 accept
nft add rule inet filter input tcp dport 5061 drop

# iptables (legacy)
iptables -A INPUT -p tcp --dport 5061 -s 10.0.0.0/8 -j ACCEPT
iptables -A INPUT -p tcp --dport 5061 -j DROP

# firewalld
sudo firewall-cmd --permanent --add-rich-rule='rule family=ipv4 source address=10.0.0.0/8 port port=5061 protocol=tcp accept'

Replace 10.0.0.0/8 with the networks that need access. Allowing by source address is the rule that matters; "allow 5061" with no source is just "open".

Related ports

Part of the port number reference. Ports are 16-bit numbers; see also the subnet calculator and the packet decoder, which shows ports inside TCP and UDP headers.

Questions

Is port 5061 TCP or UDP?

TCP. SIP over TLS is a connection-oriented protocol; there is no UDP service on 5061 by default (a scanner reporting UDP 5061 open is usually seeing a filtered port).

Is port 5061 encrypted?

Yes, always (TLS or equivalent). The port number does not make it safe by itself: certificate validation, authentication and patching still decide.

How do I check whether port 5061 is open?

On the server, ss -ltnp (or -lunp for UDP) shows whether something listens on 5061 and which process. From another machine, nc -zv host 5061 or nmap -p 5061 host tests reachability. "Open" in a scan means something answered; a firewall usually makes the port filtered (no answer) rather than closed (RST).

Can SIP over TLS run on a different port?

Yes; the number is a convention, not a requirement. Changing it reduces log noise from scanners but does not add security, and every client, firewall rule and monitoring check then needs the new number. Keep the default unless you have a concrete reason.