# Adding RADIUS Server(s)

These instructions are used to add a RADIUS accounting server or a RADIUS authorization server target to the configuration.

Call Detail Records (CDR) 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.

<figure><img src="https://docs.telcobridges.com/w/images/1/1a/Select_radius_config.png" alt=""><figcaption></figcaption></figure>

\
2- In the Editing RADIUS client configuration page, select Create new RADIUS server

<figure><img src="https://docs.telcobridges.com/w/images/a/af/AddRadiusServers_0.png" alt=""><figcaption></figcaption></figure>

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://prosbcdocs.telcobridges.com/configuration-details/configuration-by-web-portal-category/call-detail-records-cdr) and Authorization for [Authorization and Authentication](https://docs.telcobridges.com/wiki/Toolpack:Call_Routes_Settings_B#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://docs.telcobridges.com/wiki/CDR_redundancy)

<figure><img src="https://docs.telcobridges.com/w/images/b/bb/Creating_new_radius_server.png" alt=""><figcaption></figcaption></figure>

\
4- You can configure multiple RADIUS servers to provide redundancy protection for RADIUS servers. Each entry can have different settings.

<figure><img src="https://docs.telcobridges.com/w/images/e/e2/AddRadiusServers_2.png" alt=""><figcaption></figcaption></figure>

### List of Parameters

<details>

<summary>Parameter: Name</summary>

The Name parameter must be entered in when creating a new object, during Web Portal configuration. The name of an object is a character string used by the Web Portal to identify that structure.

</details>

<details>

<summary>Parameter: Server IP address</summary>

IP address of the RADIUS server.

</details>

<details>

<summary>Parameter: Server UDP port</summary>

UDP port used for communications. Typically for accounting servers, ports 1813 or 1646 are used. For authorization ports 1812 or 16456 are used.<br>

</details>

<details>

<summary>Parameter: Server type</summary>

Accounting or authorization

</details>

<details>

<summary>Parameter: Server secret</summary>

Server's secret phrase.

</details>

<details>

<summary>Parameter: Public IP address</summary>

IP address that will be set in the NAS-IP-Address attribute when present. This is used when the RADIUS client is behind a NAT. Leave empty to use the source IP address instead.

</details>

<details>

<summary>Parameter: Timeout</summary>

Timeout in milliseconds (ms) for requests to this server.

</details>

<details>

<summary>Parameter: Retries</summary>

Number of retries for requests to the server.

</details>

<details>

<summary>Parameter: Associated server</summary>

Associated radius server. In case of failure, both servers will switchover.

</details>

<details>

<summary>Parameter: Use polling (Status-Server)</summary>

If this server can be polled using the Status-Server message

</details>

<details>

<summary>Parameter: Polling delay</summary>

The time to wait in milliseconds (ms) before polling the server.

</details>

<details>

<summary>Parameter: Packet Network: Type of Service</summary>

Value to store in the TOS (Type Of Service) field of the IP header of RTP packets.\
The most recent usage of this field is a six-bit Differentiated Services Code Point (DSCP) and a two-bit Explicit Congestion Notification (ECN).\
![](https://3811773442-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiK3TemJSDhHz3xNMOvvk%2Fuploads%2Fc5eKFtga26Vsnykb1hbP%2FScreenshot%202024-12-05%20at%2010.37.21%E2%80%AFPM.png?alt=media\&token=a1d7fb01-c8d8-484d-86b5-b62cc20e3c77)

For example, if a TOS value of 144 is used, the DSCP tag will be 36 (if ECN field is not used). Some examples:

TOS       Value DSCP Value&#x20;

0                    0&#x20;

32                  8&#x20;

40                 10&#x20;

56                 14&#x20;

72                 18&#x20;

88                 22&#x20;

96                24&#x20;

112                28&#x20;

136               34&#x20;

144               36&#x20;

152                38&#x20;

160               40&#x20;

184                 46&#x20;

192               48&#x20;

224               56&#x20;

DSCP <=> IP Precedence Conversion Table

DSCP Name                       DS Field Value (Dec)                            IP Precedence (Description)&#x20;

CS0                                                      0                                                           0: Best Effort&#x20;

CS1, AF11-13                                 8,10,12,14                                                        1: Priority&#x20;

CS2, AF21-23                             16,18,20,22 2:                                                 Immediate&#x20;

CS3, AF31-33                              24,26,28,30                    3: Flash - mainly used for voice signaling&#x20;

CS4, AF41-43                              32,34,36,38                                              4: Flash Override&#x20;

CS5,EF                                             40,46                                 5: Critical - mainly used for voice RTP&#x20;

CS6                                                       48                                                 6: Internetwork Control&#x20;

CS7                                                        56                                                    7: Network Control&#x20;

</details>


---

# Agent Instructions: 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:

```
GET https://prosbcdocs.telcobridges.com/configuration-details/configuration-by-web-portal-category/call-detail-records-cdr/radius-cdrs/adding-radius-server-s.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.