> For the complete documentation index, see [llms.txt](https://prosbcdocs.telcobridges.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://prosbcdocs.telcobridges.com/telecom-references/sip-and-voip/ip-network/tls.md).

# TLS

Transport Layer Security (TLS) in VoIP: the handshake, how it secures SIP signalling, and how TLS profiles are configured on TelcoBridges systems.

Transport Layer Security (TLS) is a cryptographic protocol designed to provide communications security over a computer network. ![TLS Handshake](https://docs.telcobridges.com/w/images/6/6c/Tls_connection_handshake.png)

### TelcoBridges and TLS

TLS allows TelcoBridges' SBC to secure SIP signaling messages over networks.

#### Supported TLS RFCs

TLS 1.2

* [RFC 5246](https://www.rfc-editor.org/rfc/rfc5246.html)

### Configuration

| SBC                                                                                                                                   |
| ------------------------------------------------------------------------------------------------------------------------------------- |
| \*[v3.1: SIP TLS Configuration](https://prosbcdocs.telcobridges.com/tmedia-documentation/configuration/web-portal-3-3/protocol-stack) |

### References

* [Transport Layer Security](https://en.wikipedia.org/wiki/Transport_Layer_Security)
* [RFC 5246](https://www.rfc-editor.org/rfc/rfc5246.html)
* [SSL Certificate explained](http://www.steves-internet-guide.com/ssl-certificates-explained/)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://prosbcdocs.telcobridges.com/telecom-references/sip-and-voip/ip-network/tls.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.