> 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/hidden-pages/support-srtp-encoding-and-decoding/modifying-media-relay-profile-settings/parameter-codecs-selection-mode.md).

# Parameter: Codecs selection mode

This controls which codecs are offered to call legs:

* All codecs: Keep all codecs in the SDPs, including those only known by one of the two legs. This may force a call to use transcoding if one of the call legs selects a codec unknown by the other.
* Compatible codecs only: Keep only codecs known by the two call legs. This ensures low-delay relay mode can be used. Fallback to transcoding mode will still occur if no compatible codecs exist between the two call legs.
* Active codec only: Keep only the active codec, which prevent any of the two legs to change codec later during the call.


---

# 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/hidden-pages/support-srtp-encoding-and-decoding/modifying-media-relay-profile-settings/parameter-codecs-selection-mode.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.
