TLS (Transport Layer Security)
TLS encrypts and authenticates the connection between a SIP client and server, protecting signaling from eavesdropping and tampering. It is the secure transport option in SIP.
Published 8 November 2026 · 1 min read · By SpaGreen Creative
Short answer
TLS is the cryptographic protocol, currently defined in RFC 8446, that encrypts and authenticates a TCP connection, used in SIP to protect signaling between a client and the next hop.
TLS is the same protocol that secures HTTPS. In SIP it wraps the TCP connection between a client and a server so that every message is encrypted and cannot be altered in transit. RFC 3261 section 26 recommends it as the transport-layer protection for SIP, and the current version of the protocol is TLS 1.3, defined in RFC 8446.
When a softphone connects over TLS, the server presents a certificate. The client checks that a trusted certificate authority issued it and that it matches the server's name. This step is what prevents an attacker from pretending to be the server and collecting credentials. A client that skips the check gains encryption but not authentication, which is why strict clients refuse self-signed certificates.
TLS protects signaling only, and only on one hop. Audio travels separately over RTP and needs SRTP for encryption. The next server in the path may or may not use TLS onward.
The default port for SIP over TLS is 5061. In SIPdia, choose TLS in the Transport field. The server must present a certificate from a public certificate authority; self-signed certificates are rejected. If your PBX cannot offer one, use UDP or TCP over a VPN instead.
Sources and further reading
- RFC 8446: The Transport Layer Security (TLS) Protocol Version 1.3www.rfc-editor.org
- RFC 3261: SIP: Session Initiation Protocol, Section 26 Security Considerationswww.rfc-editor.org
This article is published by SpaGreen Creative, the maker of SIPdia. Product names mentioned belong to their owners. Where it describes other software, treat the steps as general guidance and check the official documentation linked above.
