> 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/tmedia-documentation/configuration/toolpack-adding-radius-server-s.md). # Toolpack: Adding RADIUS Server(s) > **Applies to:** Tmedia 3.0, 3.2, 3.3; SBC 3.1, 3.3 These instructions are used to add a RADIUS accounting server or a RADIUS authorization server target to the configuration. [Call Detail Records (CDR)](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/concepts/call-detail-record/README.md) or Call authorization requests will be sent to these servers. Multiple RADIUS servers can be configured to provide RADIUS redundancy. 1- Select **RADIUS** from the navigation panel. ![Select radius config](https://docs.telcobridges.com/w/images/1/1a/Select_radius_config.png) 2- In the **Editing RADIUS client configuration** page, select **Create new RADIUS server** ![AddRadiusServers 0](https://docs.telcobridges.com/w/images/a/af/AddRadiusServers_0.png) 3- Configure the RADIUS server with these parameters: * **Name** to recognize the server. * **Server IP address** is the IP address of the RADIUS server we want to access. * **Server UDP Port** is the UDP port of the RADIUS server we want to access (default port is 1813 for accounting and 1812 for authorization/authentication) * **Server type** is Accounting for [CDR](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/concepts/call-detail-record/README.md) and Authorization for [Authorization and Authentication](https://github.com/telcobridges-main/tmedia-wiki/tree/main/tmedia/configuration/web-portal-2-9-call-routes-settings/README.md#radius-authorization-and-authentication). * **Server secret** is the passphrase to authenticate the TMG on the RADIUS server. Advanced Parameters: * **Public IP address** is used if the TMG is behind a NAT * **Timeout** is the request timeout in milliseconds for each request to this server. * **Retries** is the number of retries the RADIUS client will try before falling back to other methods. See full details on functionality here: [CDR redundancy](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/toolpack-cdr-redundancy/README.md) ![Creating new radius server](https://docs.telcobridges.com/w/images/b/bb/Creating_new_radius_server.png) 4- You can configure multiple RADIUS servers to provide redundancy protection for RADIUS servers. Each entry can have different settings. ![AddRadiusServers 2](https://docs.telcobridges.com/w/images/e/e2/AddRadiusServers_2.png) **Path** ``` /configurations/@[configuration_name]/radius_servers/@[radius_server] ``` **Parameters (text)** ``` /configurations/@[configuration_name]/radius_servers/@[radius_server] ip_address = "@[address_number]" name = "@[radius_server]" port = @[port_number] secret = "@[secret]" type = "Accounting" /configurations/@[configuration_name]/radius_servers/@[radius_server]/advanced_parameters associated_authorization_server = "" ip_header_tos = 0 polling_delay = "5 seconds" polling_enabled = false public_ip_address = "" retries = 2 timeout = "10 seconds" ``` **Parameters (json)** ``` { "advanced_parameters" : { "associated_authorization_server" : "", "ip_header_tos" : 0, "polling_delay" : "5 seconds", "polling_enabled" : false, "public_ip_address" : "", "retries" : 2, "timeout" : "10 seconds" }, "ip_address" : "@[address_number]", "name" : "@[radius_server]", "port" : @[port_number], "secret" : "@[secret]", "type" : "Accounting" } ``` ### List of Parameters * [Name](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/parameters/name/README.md) * [Server IP address](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/parameters/server-ip-address/README.md) * [Server UDP port](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/parameters/server-udp-port/README.md) * [Server type](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/parameters/server-type/README.md) * [Server secret](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/parameters/server-secret/README.md) Advanced Parameters * [Public IP address](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/parameters/public-ip-address/README.md) * [Timeout](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/parameters/timeout/README.md) * [Retries](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/parameters/retries/README.md) * [Associated server](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/parameters/associated-server/README.md) * [Use polling (Status-Server)](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/parameters/use-polling-status-server/README.md) * [Polling delay](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/parameters/polling-delay/README.md) * [IP Header Type of Service (ToS)](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/parameters/packet-network-type-of-service/README.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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://prosbcdocs.telcobridges.com/tmedia-documentation/configuration/toolpack-adding-radius-server-s.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.