> 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/other-pages/fax-and-media/accessing-codec-and-tone-detection-profiles-and-validating-settings.md).

# Accessing Codec and Tone Detection Profiles and Validating Settings

#### ***Applies to version(s): v2.8.***

You must access your system's default sound codec and tone detection profiles, to validate whether or not they are correctly set.

To do so:

1- Click **Profiles** in the navigation panel

![SipProfile 0](https://docs.telcobridges.com/w/images/e/e8/SipProfile_0.png)

2- Select the default configuration (or the custom configuration you will be using)

![SipProfile 1](https://docs.telcobridges.com/w/images/c/cd/SipProfile_1.png)

3- Click SIP to access the SIP profiles.

![SipProfile 2](https://docs.telcobridges.com/w/images/4/48/SipProfile_2.png)

4- Validate the configuration:

* Select an appropriate **DTMF relay scheme** from the list

![SipProfile 3](https://docs.telcobridges.com/w/images/9/9f/SipProfile_3.png)

4- Click **"<<"** to add a scheme

* Click **Save**

![SipProfile 4](https://docs.telcobridges.com/w/images/b/b9/SipProfile_4.png)

***IMPORTANT!*** The configuration will not be saved if the text box designed to contain the session definition protocol (SDP) is left empty. The SDP must be written as directed in the [session description protocol page.](/other-pages/fax-and-media/profile-sdp-description.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/other-pages/fax-and-media/accessing-codec-and-tone-detection-profiles-and-validating-settings.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.