UDP and TCP port
Port 5060: SIP
Port 5060 is SIP, the signalling that sets up a VoIP call, over UDP or TCP. Port 5061 is SIP inside TLS. The audio itself flows separately, over RTP.
- A call is set up with INVITE, ringing, 200 OK and ACK.
Check port 5060 on Linux
Put the server's name or address in place of HOST.
ss -ulnp 'sport = :5060'- On the server: is a program listening on UDP port 5060, and which? How to read ss.
tcpdump -ni any udp port 5060- On either end: the datagrams to and from UDP port 5060. With UDP this is the sure test, since nothing is acknowledged. How to read tcpdump.
nmap -sU -p 5060 HOST- From outside: a UDP scan of port 5060. No answer reads open|filtered: UDP does not say which. How to read nmap.
ss -tlnp 'sport = :5060'- On the server: is a program listening on TCP port 5060, on which address, and which program? How to read ss.
nc -zv HOST 5060- From a client: does a TCP connection to port 5060 open, get refused, or time out? How to read nc.
tcpdump -ni any tcp port 5060- On either end: the packets to and from TCP port 5060, as they cross the card. How to read tcpdump.
nmap -p 5060 HOST- From outside: is TCP port 5060 open, closed or filtered? How to read nmap.
What runs on it
- SIP
- The signaling that sets up a VoIP call on port 5060: INVITE, ringing, 200 OK, ACK — then the audio flows separately over RTP.
- UDP
- Independent datagrams with ports and nothing else: no connection, no acknowledgement, no retries.