> 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/parameter-reference/transcoding.md).

# Transcoding parameters

Codecs, vocoders and companding. 6 parameters.

## A

| Parameter                   | Description                                                                                                                                                              |
| --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Allow audio transcoding** | Allow audio codec transcoding when the joined call legs have incompatible codecs, or when IVR functions are required (tone detection, tone play, file play, file record) |
| **Audio Companding**        | Audio companding on this line service (aLaw, uLaw or automatic based on stack variant).                                                                                  |
| **Audio Transcoding Type**  | Transcoding can be used to convert the media encoding type, for example from G.711 to G.729.                                                                             |

## C

| Parameter                 | Description                                                                                                                                        |
| ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- |
| **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. |

## F

| Parameter                                            | Description                                                                                                                                                 |
| ---------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Force Transcoding for Telephony Event Conversion** | This parameter forces the transcoding for telephony event conversion, when one of two joined call legs does not support the telephony event (DTMF RFC2833). |

## P

| Parameter                              | Description                                                                                               |
| -------------------------------------- | --------------------------------------------------------------------------------------------------------- |
| **Packet Network: SSRC randomization** | Enable the randomization of SSRC when the RTP stream is restarted (codec change or other similar reason). |


---

# 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/parameter-reference/transcoding.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.