> 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/other-pages/operations/radius.md).
# RADIUS
RADIUS on TelcoBridges systems: authentication, authorisation and accounting, including CDR export and support for multiple RADIUS servers.
Remote Authentication Dial In User Service, more popularly known as RADIUS, is used by telecom service providers for the purpose of authenticating, authorizing, and accounting (AAA) for the use of services by subscribers. A RADIUS server is an application server that provides this functionality. It can take as input as well as output [Call detail record](https://prosbcdocs.telcobridges.com/telecom-references/cdr-and-statistics/cdr) (CDR) data.
### TelcoBridges and RADIUS
Starting with release v2.3 of Toolpack, explicit support for the accounting function of RADIUS is now offered. Previously, Toolpack stored [Call detail record](https://prosbcdocs.telcobridges.com/telecom-references/cdr-and-statistics/cdr) (CDR) data in a local database. Starting with Toolpack v2.3, CDR data is stored on a dedicated, external server running an implementation of the RADIUS standard. Configuration of the location of the RADIUS server is performed through the Toolpack web portal.
Starting with release v2.6 of Toolpack, multiple RADIUS servers can now be configured for backup purposes.
Starting with release v2.7 of Toolpack, calls can now be validated through a RADIUS server with authentication and authorization. The RADIUS server may also change routing parameters for calls.
#### Prerequisites
In order to enable RADIUS functionality in Toolpack, you must have a RADIUS server already up and running. It is highly recommended that the RADIUS server software being running on a separate machine from the one running the Toolpack software. Before configuring Toolpack, you will need the IP address of the RADIUS server(s). You will need to specify a ‘secret key’ which will authenticate the Toolpack server so that it can send accounting, authentication and authorization data and to the RADIUS server and the RADIUS server will accept it.
#### Accounting
* [Web Portal v3.2: RADIUS configuration](/tmedia-documentation/configuration/web-portal-previous/web-portal-3-2/cdr/cdr-settings.md)
* [Web Portal v3.0: RADIUS configuration](/tmedia-documentation/other-pages/cdr-and-billing/tmedia-tdev-and-tsig-web-portal-3-0-call-detail-record-cdr.md)
Click here for other versions
* [Web Portal v2.10: RADIUS configuration](/tmedia-documentation/configuration/web-portal-previous/web-portal-2-10/tmedia-tdev-and-tsig-web-portal-2-10-call-detail-record-cdr.md)
* [Web Portal v2.9: RADIUS configuration](/tmedia-documentation/configuration/web-portal-previous/web-portal-2-9/web-portal-2-9-call-detail-record-cdr.md)
* [Web Portal v2.7: RADIUS configuration](/tmedia-documentation/other-pages/radius-and-authentication/configuring-radius.md)
* Web Portal v2.8, Web Portal v2.6 and Toolpack v2.5 and earlier: documentation is no longer published. Contact [technical support](/tmedia-documentation/operations-and-support/support/contacting-telcobridges-technical-support.md) if you need it.
#### Authorization/Authentication
* [Web Portal v3.2: RADIUS Authorization and Authentication configuration](/tmedia-documentation/configuration/web-portal-previous/web-portal-3-2/call-route/call-routes-settings.md)
* [Web Portal v3.0: RADIUS Authorization and Authentication configuration](/tmedia-documentation/other-pages/call-routing-routes-and-naps/tmedia-tdev-and-tsig-web-portal-3-0-call-routes-settings.md#radius-authorization-and-authentication)
Click here for other versions
* [Web Portal v2.10: RADIUS Authorization and Authentication configuration](/tmedia-documentation/configuration/web-portal-previous/web-portal-2-10/tmedia-tdev-and-tsig-web-portal-2-10-call-routes-settings.md)
* [Web Portal v2.9: RADIUS Authorization and Authentication configuration](/tmedia-documentation/configuration/web-portal-previous/web-portal-2-9/web-portal-2-9-call-routes-settings.md)
* Web Portal v2.8 and earlier: documentation is no longer published. Contact [technical support](/tmedia-documentation/operations-and-support/support/contacting-telcobridges-technical-support.md) if you need it.
### Authorization
If a Radius authorization server is configured, the call authorization is done externally (using the Radius protocol). The acceptance or refusal of the call is then returned into a routing script for further processing. Refer to [Radius authorization](https://prosbcdocs.telcobridges.com/telecom-references/developer-reference/routing-scripts) for more details.
### RADIUS Redundancy and Association
* [Radius Accounting and Authentication Redundancy](/tmedia-documentation/other-pages/operations/radius-accounting-authentication-redundancy.md)
* [Radius Accounting and Authentication Association](/tmedia-documentation/other-pages/operations/radius-accounting-authentication-association.md)
### Toolpack to RADIUS CDR attributes remapping
When Toolpack sends *Access-Request* messages to a RADIUS server, some specific attributes are included in the message. These attributes have been improved through Toolpack releases to better meet accounting services requirements.
**RADIUS CDR attributes list**
* [Toolpack v3.0 and higher](/tmedia-documentation/other-pages/radius-and-authentication/toolpack-radius-cdr-attributes.md)
Click here for other versions
* Toolpack v2.10 and earlier: documentation is no longer published. Contact [technical support](/tmedia-documentation/operations-and-support/support/contacting-telcobridges-technical-support.md) if you need it.
### Dealing with incoherent CDR entries
When using Text CDR and during a switchover, some CDR entries may be on different systems.
The following guide lines provide information on how to deal with these corner cases:
[Incoherent CDR during switchover](/tmedia-documentation/operations-and-support/troubleshooting/how-to/incoherent-cdr-during-switchover.md)
### References
* [FreeRadius Configuration for Accounting](https://prosbcdocs.telcobridges.com/)
* [Radius status in TMG web portal](/tmedia-documentation/other-pages/cdr-radius-and-applications/status-menus-radius.md)
* [Radius Wikipedia article](http://en.wikipedia.org/wiki/RADIUS)
* [Link to RFC 2866 – Radius Accounting](http://www.ietf.org/rfc/rfc2866.txt)
* [FreeRADIUS website](http://www.freeradius.net)
---
# 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://prosbcdocs.telcobridges.com/tmedia-documentation/other-pages/operations/radius.md?ask=&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.