> 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-allow-audio-transcoding.md).

# Parameter: Allow audio transcoding

{% hint style="warning" %}
**Deprecated.** The `Allow audio transcoding` on/off setting has been replaced by the **Audio Transcoding type** parameter. On current releases, configure *Audio Transcoding type* (below) instead.
{% endhint %}

*Legacy behavior (for reference):* when enabled, `Allow audio transcoding` let the SBC transcode audio when the joined call legs had incompatible codecs, or when IVR functions were required (tone detection, tone play, file play, file record).

### Audio Transcoding type

Selects how the SBC transcodes audio between the two call legs. There are three options:

| Option                         | Behavior                                                                                                                        | Requires                       |
| ------------------------------ | ------------------------------------------------------------------------------------------------------------------------------- | ------------------------------ |
| **Software audio transcoding** | Transcodes G.711 a-law ↔ µ-law.                                                                                                 | A software transcoding license |
| **Hardware audio transcoding** | Transcodes a wider range of codecs — see [Transcoding capabilities](/use-cases/applications/transcoding.md).                    | A physical transcoding device  |
| **None**                       | The SBC does not transcode. A call that would require transcoding (incompatible codecs) is dropped with SIP cause code **488**. | —                              |

**Related:** [Codecs selection mode](/hidden-pages/support-srtp-encoding-and-decoding/modifying-media-relay-profile-settings/parameter-codecs-selection-mode.md) · [Allow low-delay media relay](/configuration-details/configuration-by-use-case/rtp-no-anchoring/parameter-allow-low-delay-media-relay.md) · [Allow other codecs](/hidden-pages/support-srtp-encoding-and-decoding/modifying-media-relay-profile-settings/parameter-allow-other-codecs.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://prosbcdocs.telcobridges.com/hidden-pages/support-srtp-encoding-and-decoding/modifying-media-relay-profile-settings/parameter-allow-audio-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.