Skip to content
AdminKit

SIP (Session Initiation Protocol)

What is SIP (Session Initiation Protocol)?

SIP (Session Initiation Protocol, RFC 3261) is the signalling protocol IP phones, softphones and voice gateways use to register, set up, change and end calls, by default on port 5060 over UDP or TCP and 5061 over TLS. AdminKit's port check does not test SIP ports; its fixed list covers nine other TCP ports.

By AdminKit team, Netbase JSC · Updated

RFC 3261 describes SIP as an application-layer control protocol that can establish, modify and terminate multimedia sessions such as Internet telephony calls. It defines six methods: REGISTER for registering a device’s current contact address, INVITE, ACK and CANCEL for setting up sessions, BYE for ending them, and OPTIONS for asking a server what it supports. SIP messages are text, with a request line and headers much like HTTP, and the same RFC sets the default port at 5060 for UDP, TCP and SCTP and 5061 for TLS. IANA’s port registry lists those numbers as the sip and sips services. Both sit in the User Ports range, not among the 0-1023 well-known ports.

The Wireshark wiki page on SIP describes the usual split: SIP carries the signalling, the session details are negotiated with SDP offers and answers, and the audio or video travels separately, commonly as RTP and RTCP streams. RTSP plays a similar control role for IP camera streams, but it is a separate protocol on its own port, 554.

How does a phone find a SIP server?

RFC 3263 uses DNS to turn a SIP URI into the IP address, port and transport of the next hop to contact, through NAPTR and SRV records. A provider can publish separate SRV records for SIP over UDP, TCP and TLS, so phones do not need the port typed in by hand. The TLS variant wraps the signalling in a normal TLS handshake, the same as HTTPS.

Why does an exposed SIP port matter?

A SIP server or IP-PBX reachable from the internet accepts REGISTER and INVITE requests from anyone who finds it. RFC 3261 section 22 lets the server challenge those requests with Digest authentication, but notes that Digest provides authentication and replay protection only, without integrity or confidentiality, so weak account passwords and unencrypted signalling are the device’s problem to solve. NIST SP 800-58, Security Considerations for Voice Over IP Systems, introduces VoIP, its security challenges and potential countermeasures for them.

AdminKit’s port check scans only the public IP you connect from, after you click to start it, against nine fixed TCP ports; 5060 and 5061 are not among them, so it cannot confirm SIP exposure. SIP is part of AdminKit’s machine protocols cluster; the full AdminKit glossary lists other related terms.

Frequently asked questions

Which ports does SIP use?

RFC 3261 sets the default at 5060 for SIP over UDP, TCP and SCTP and 5061 for SIP over TLS. IANA's port registry lists the same numbers under the service names sip and sips. A server can be configured on any other port, so the number is a convention, not a guarantee.

Does the voice or video travel over SIP?

No. SIP only sets up, changes and ends the session. The two ends describe the media they want in a Session Description Protocol (SDP) body, and the audio or video itself usually travels separately, commonly as RTP streams on other ports.

Does SIP have built-in authentication?

It has an optional one. RFC 3261 section 22 lets a server or proxy challenge a request using HTTP-style Digest authentication, and forbids Basic. Digest gives message authentication and replay protection only, not integrity or confidentiality, so SIP over TLS (port 5061) is needed to protect the signalling itself.

Can AdminKit check whether port 5060 is open on my network?

Not today. AdminKit's port check scans a fixed list of nine TCP ports device makers commonly leave open (Telnet, RTSP, MQTT, Modbus, TR-069 and three web admin ports), and 5060 and 5061 are not in that list.