> For the complete documentation index, see [llms.txt](https://tmediadocs.telcobridges.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tmediadocs.telcobridges.com/telecom-references/voice-and-media/support-srtp-encoding-and-decoding.md).

# Support sRTP encoding and decoding

sRTP encoding and decoding on FreeSBC and ProSBC: terminating encrypted media at the network boundary and relaying it as plain RTP inside. SBC 3.1.

> **Applies to:** SBC 3.1

FreeSBC/ProSBC supports the encoding and decoding of sRTP. This enables the SBC to be on the boundary of a private network where RTP is unencrypted, and to relay the RTP to a "public" network where encryption is required. This is typically done when encryption cannot be used end-to-end.

To learn about SIP stack configuration, refer to [FreeSBC/ProSBC Web Portal 3.1: Protocol Stacks](https://tmediadocs.telcobridges.com/configuration/web-portal-3-3/protocol-stack).

The setting for sRTP (RTP Security mode) is configured using the RTP Security Mode parameter, described here: [Profile Page, Media Relay-RTP Security Mode parameter](https://tmediadocs.telcobridges.com/other-pages/other/modifying-media-relay-profile-settings).

### References

* [Information on sRTP relay](/telecom-references/voice-and-media/srtp-relay-support-for-encrypted-sip-interconnections.md)


---

# 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://tmediadocs.telcobridges.com/telecom-references/voice-and-media/support-srtp-encoding-and-decoding.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.