> 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/configuring-radius.md).

# Configuring RADIUS

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

This article describes how to configure a TMG system to communicate with RADIUS servers. RADIUS requests will be sent from the TMG management port (mgmt0) or from the Virtual IP Interfaces (if they are configured).

1- Select **RADIUS** from the navigation panel.

![Radius Config left panel](https://docs.telcobridges.com/w/images/3/3b/Radius_Config_left_panel.jpg)

2- The **Editing RADIUS client configuration** page provides some general parameters that can be modified:

* **Timezone** will use the local timezone or the GMT timezone in the RADIUS attributes
* **Time format** describes how to display the time in human readable format in the RADIUS attributes. This is based on the [strftime function](http://php.net/manual/en/function.strftime.php)
* In Advanced Parameters you have:
  * **Maximum accounting concurrent records** is the maximum number of simultaneous accounting records to be sent to the RADIUS servers. This improves the RADIUS performance of the system: it allows the RADIUS client to deal with servers that have high latency relative to the number of request/responses per second to be achieved. Default value is 10 records.
  * **Maximum accounting queued records** is the maximum number of accounting records to queue when the maximum number of pending records has been reached. When the maximum number of queued messages is reached, CDR records will be dropped. To prevent this, make sure the system supports [CDR redundancy](/products/tmedia/features-and-solutions/features/redundancy-and-high-availability/toolpack-cdr-redundancy.md). Default value is 12000 records.
  * **Maximum authorization concurrent requests** is the maximum number of simultaneous authorization requests to be sent to the RADIUS servers. This improves the RADIUS performance of the system: it allows the RADIUS client to deal with servers that have high latency relative to the number of request/responses per second to be achieved. Default value is 200 requests.
  * **Maximum authorization queued requests** is the maximum number of authorization requests to queue when the maximum number of pending requests has been reached. When the maximum number of queued messages is reached, authorization requests will be dropped. Default value is 12000 requests.
  * **Additional dictionary** is an additional dictionary that provides the definition of custom RADIUS attributes.
  * Click **Save** to save your changes.

![RADIUS client config 2 7](https://docs.telcobridges.com/w/images/a/a5/RADIUS-client-config-2_7.PNG)


---

# 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/configuring-radius.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.