> 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-accounting-authentication-association.md).
# Radius Accounting Authentication Association
With version 2.7.31+, Toolpack has the Associated server field in the RADIUS Client configuration page:
**Link accounting and authentication together logically**
This allows to specify that whenever one of the two associated server is the Current one, then the other one should also be set as the current one.
So both servers have to be the 'current' at the same time.
**Sends Acct/Auth requests to the same physical RADIUS server**
The association resolves a problem when you would have two physical RADIUS servers, each server hosts an accounting and authorization server, and you have a limitation on the Radius server to run the primary accounting and authentication on the same server (identical IP).
### A specific scenario
There are 2 Radius AUTH servers provisioned (IPerbill & IPeradius) and 2 Radius ACCT servers provisioned (the same IPerbill & IPeradius)
So there are 3 different possibilities for switchover:
1. Toolpack will work with IPerbill as master for ACCT and AUTH
2. In case of external failure Toolpack will switchover both stacks ACCT and AUTH to IPeradius
3. In some specific cases of external failures Toolpack will switchover only one stack, so we will have AUTH to IPerbill and ACCT to IPeradius:
* Either: AUTH to IPerbill and ACCT to IPeradius
* Or: ACCT to IPerbill and AUTH to IPeradius
In this case, associating the accounting and authentication to the same IP will prevent occurrence of scenario 3.
### Configuration
* [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#radius-authorization-and-authentication)
* [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#radius-authorization-and-authentication)
* [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#radius-authorization-and-authentication)
* 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.
---
# 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-accounting-authentication-association.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.