> 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/telecom-references/protocols/radius-accounting-authentication-redundancy.md). # Radius Accounting Authentication Redundancy With version 2.7, Toolpack fully supports redundancy on Radius authentication and accounting. Short for AUTH/ACCT in the below description. ### Multiple Radius Servers Toolpack Radius AUTH/ACCT can be provisioned with several Radius servers (not only two). Each Radius client processing AUTH and ACCT are flexibly configurable by: * Use polling (Status-Server) * Requests timeout and number of retries ### Current(Primary) Radius AUTH/ACCT server selection * If polling is enabled, the selected "Current" server will be the first that responds to the polling requests. All other servers in the list will be flagged as "online" or "offline" depending whether it responses to the polling. * If polling is disabled, the server is selected in a round robin order, the first being tested successfully is the "Current". All other servers in the list will be flagged as "online" or "offline" depending whether it responses to requests within the timeout and retries. ### Radius AUTH/ACCT switch-over Let's take this scenario to explain the Radius AUTH/ACCT switchover feature: * We have servers **A** and **B**, both 'online', and server **A** is 'Current'. * Request W　is sent to server **A**. * Request X，R,Z are in the queue sent to server **A**. * Server **A** doesn't respond to Request W. In consequence, server **A** is qualified as 'offline' and server B is elected as 'Current'. * Request W is then sent to server **B**. * All new requests M,Y,Q will be sent to server **B**. * The Request X which is in queue to **A**, will be sent to **A**. If A is still qualified as 'offline'. It will be then sent to **B**. * If server **A** is back qualified as "online". It will process the request X. * The requests R,Z in queue will be processed same as X. ### Configuration * [Web Portal v3.2: RADIUS Authorization and Authentication configuration](https://github.com/telcobridges-main/tmedia-wiki/tree/main/tmedia/configuration/tmedia-tdev-and-tsig-web-portal-3-2-call-route-settings/README.md#tabradius-authorization-and-authentication) * [Web Portal v3.1: RADIUS Authorization and Authentication configuration](https://github.com/telcobridges-main/tmedia-wiki/tree/main/tmedia/configuration/freesbc-prosbc-web-portal-3-1-call-routes-settings/README.md#tabradius-authorization-and-authentication) * [Web Portal v3.0: RADIUS Authorization and Authentication configuration](https://github.com/telcobridges-main/tmedia-wiki/tree/main/tmedia/configuration/freesbc-web-portal-3-0-call-routes-settings/README.md#radius-authorization-and-authentication) \- \[Web Portal v2.10: RADIUS Authorization and Authentication configuration]\(/tmedia/configuration/tmedia-tdev-and-tsig-web-portal-2-10-call-routes-settings#radius-authorization-and-authentication) - \[Web Portal v2.9: RADIUS Authorization and Authentication configuration]\(/tmedia/configuration/web-portal-2-9-call-routes-settings#radius-authorization-and-authentication) - \[Web Portal v2.8: RADIUS Authorization and Authentication configuration]\(/tmedia/configuration/web-portal-2-8-call-routes-settings#radius-authorization-and-authentication) - \[Web Portal v2.7: RADIUS Authorization and Authentication configuration]\(/tmedia/configuration/tmedia-tsig-and-tdev-web-portal-2-7-tutorial-guide#radius-authorization-and-authentication) --- # 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/telecom-references/protocols/radius-accounting-authentication-redundancy.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.