> 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/radius-status.md).

# Radius Status

\*\*\*Applies to version(s): v2.9, v2.10, v3.0, v3.2\*\*\*

This article illustrates how to verify the Radius servers using the Status menu and the Navigation panel.

## Status menu

1- Click **Status** in the navigation panel.

![Status 0](https://docs.telcobridges.com/w/images/5/53/Status_0.png)

2- Click the **RADIUS** tab.

![TabRadius 0](https://docs.telcobridges.com/w/images/4/4c/TabRadius_0.png)

3- The Radius server list is displayed.

* Select a Radius server.

![StatusRadius 0](https://docs.telcobridges.com/w/images/8/8a/StatusRadius_0.png)

The current status of the Radius server is displayed.

![StatusRadius 1](https://docs.telcobridges.com/w/images/e/eb/StatusRadius_1.png)

## Navigation panel

1- Click **RADIUS** from the navigation panel.

![StatusRadius 2](https://docs.telcobridges.com/w/images/3/34/StatusRadius_2.png)

2- Click the **Status** tab.

![StatusRadius 3](https://docs.telcobridges.com/w/images/0/03/StatusRadius_3.png)

3- Select a Radius server.

![StatusRadius 4](https://docs.telcobridges.com/w/images/3/34/StatusRadius_4.png)

**Address**

* The IP address and the UDP port of the Radius server.

**Type**

* Authorization for Authorization and Authentication. Accounting for CDRs.

**Availability**

* **Up:** Got a response
* **Down:** Got a request response timeout
* **Unknown:** Did not try to send request yet

**State**

* **Current:** Preferred server to send packet if last Availability was Up
* **Active:** Can be used as a server to send information
* **Inactive:** Not used

**Other parameters**

* \*\*Request cnt: \*\* Number of requests that were sent
* \*\*Retransmission cnt: \*\* Number of retransmissions to this Radius server
* \*\*Request failure cnt: \*\* Number of requests that could not be sent
* \*\*Response cnt: \*\* Number of responses received from this Radius server
* \*\*Timeout cnt: \*\* Number of times the Requests timed out

**Client Status**

* **Acct pending records:** Current number of pending accounting records (sent but not acknowledged yet)
* **Acct queued records:** Current number of queued accounting records (waiting to be sent)
* **Acct instant record cnt:** Number of accounting records that were instantaneously sent to a server without being queued
* **Acct queued record cnt:** Number of accounting records that were queued before being sent
* **Acct overflow record cnt:** Number of accounting records that were discarded because the queue was full
* **Acct unanswered record cnt:** Number of accounting records that were discarded because no servers acknowledged them
* **Acct lost record cnt:** Number of accounting records that were lost either because they didn't fit in a queue or no servers response received for them

The current status of the Radius server is displayed and the state can be changed.

![StatusRadius 1](https://docs.telcobridges.com/w/images/e/eb/StatusRadius_1.png)

**Path**

```
/configurations/@[configuration_name]/gateways/@[gateway_name]/status
```


---

# 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/radius-status.md?ask=<question>&goal=<endgoal>
```

`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.