> 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/configuration/web-portal-3-3/cdr/radius/enabling-radius.md).

# Toolpack: Enabling and Configuring RADIUS

> **Applies to:** Tmedia 3.0, 3.2, 3.3

This article describes how to enable and configure a TMG system to capture Call Detail Records ([CDR](https://tmediadocs.telcobridges.com/telecom-references/cdr-and-statistics/cdr)s), using a [RADIUS](/other-pages/operations/radius.md) server.

***Enabling RADIUS***

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

![EnableCdr 0](https://docs.telcobridges.com/w/images/3/31/EnableCdr_0.png)

2- Verify that the box **Use CDR behavior** is checked.

![700 px](https://docs.telcobridges.com/w/images/2/28/EnableRadius_0a.png)

3- Configure the CDR behavior in the **CDR Options** section:

* **Enable periodic CDR update** will add one entry in the CDR per **Periodic CDR update time**, in minutes.
* Select one of the **RADIUS CDR** mode from the **CDR Mode** :
  * **Text CDR only**: Will store the CDRs in a flat file. See [Text CDR](https://tmediadocs.telcobridges.com/telecom-references/cdr-and-statistics/text-call-detail-records)
  * **RADIUS CDR only**: Will send the CDR to an external RADIUS Server. See [Radius CDR](/other-pages/operations/radius.md)
  * **Text and RADIUS CDR**: Will store the CDRs in a flat file and send the CDR to an external RADIUS Server.
  * **RADIUS CDR with Text CDR Fallback**: Will send the CDR to an external RADIUS Server and if the RADIUS server cannot handle the load of CDRs, they will be stored in a flat file.
* Click **Save** to save your changes.

4- Verify that the **Gateway configuration was successfully updated.** message appears.

![EnableCdr 3](https://docs.telcobridges.com/w/images/2/21/EnableCdr_3.png)

**Path**

```
/configurations/@[configuration_name]/gateways/@[gateway_name]
```

**Parameters (text)**

```
/configurations/@[configuration_name]/gateways/@[gateway_name]
cdr_system_id                 = 5448
routing_script                = "default_routing_script"
translate_privacy_information = false
use_cdr_behavior              = true

/configurations/@[configuration_name]/gateways/@[gateway_name]/advanced_parameters
enable_call_recording            = false
forward_connected_number         = false
forward_redirecting_number       = true
forward_redirection_number       = true
forward_ss7_raw_message_bytes    = true
forward_user_to_user_information = true
route_retry_mode                 = "Call Alerted"
route_retry_relay_progress_msgs  = true
route_retry_timeout              = "10 seconds"

/configurations/@[configuration_name]/gateways/@[gateway_name]/advanced_parameters/call_recording_options
called                                = ""
calling                               = ""
incoming_nap                          = "(Any)"
outgoing_nap                          = "(Any)"
record_all_legs_of_a_call_to_one_file = false
termination_name                      = ""

/configurations/@[configuration_name]/gateways/@[gateway_name]/cdr_options
cdr_mode                   = "RADIUS CDR only"
enable_periodic_cdr_update = false
periodic_cdr_update_time   = "0 minute"
reverse_cdr_call_origin    = false

/configurations/@[configuration_name]/gateways/@[gateway_name]/sip_privacy_options
use_alternate_anonymous_address = false
```

**Parameters (json)**

```
{
  "advanced_parameters" : {
    "call_recording_options" : {
      "called" : "",
      "calling" : "",
      "incoming_nap" : "(Any)",
      "outgoing_nap" : "(Any)",
      "record_all_legs_of_a_call_to_one_file" : false,
      "termination_name" : ""
    },
    "enable_call_recording" : false,
    "forward_connected_number" : false,
    "forward_redirecting_number" : true,
    "forward_redirection_number" : true,
    "forward_ss7_raw_message_bytes" : true,
    "forward_user_to_user_information" : true,
    "route_retry_mode" : "Call Alerted",
    "route_retry_relay_progress_msgs" : true,
    "route_retry_timeout" : "10 seconds"
  },
  "cdr_options" : {
    "cdr_mode" : "RADIUS CDR only",
    "enable_periodic_cdr_update" : false,
    "periodic_cdr_update_time" : "0 minute",
    "reverse_cdr_call_origin" : false
  },
  "cdr_system_id" : 5448,
  "routing_script" : "default_routing_script",
  "sip_privacy_options" : {
    "use_alternate_anonymous_address" : false
  },
  "translate_privacy_information" : false,
  "use_cdr_behavior" : true
}
```


---

# 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/configuration/web-portal-3-3/cdr/radius/enabling-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.