> 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/radius-and-authentication/adding-a-custom-radius-dictionary.md).

# Adding a Custom RADIUS Dictionary

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

This page describes how to add a custom RADIUS dictionary to use vendor-specific RADIUS attributes.

**Note:** The format of a RADIUS dictionary is based on the following article: [| Linux Man Page: Radius Dictionary](http://linux.die.net/man/5/dictionary)

1- Select **File Db** from the navigation panel.

![FileDB 0 B](https://docs.telcobridges.com/w/images/a/a5/FileDB_0_B.png)

2- In the **RADIUS dictionaries** section, click **Import new RADIUS dictionary**.

![RADIUS file db dictionary 2 7](https://docs.telcobridges.com/w/images/0/04/RADIUS-file-db-dictionary-2_7.PNG)

3- Click the **Browse...** button to select the RADIUS dictionary to add. When the file is selected, click **Import**.

![RADIUS file db dictionary import 2 7](https://docs.telcobridges.com/w/images/e/e5/RADIUS-file-db-dictionary-import-2_7.PNG)

4- Verify that the **File was successfully imported.** message appears.


---

# 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/radius-and-authentication/adding-a-custom-radius-dictionary.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.