> For the complete documentation index, see [llms.txt](https://tmediadocs.telcobridges.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tmediadocs.telcobridges.com/products/tmedia/features-and-solutions/features/redundancy-and-high-availability/software-cdr.md).

# Software:CDR

The [CDRs](https://tmediadocs.telcobridges.com/telecom-references/cdr-and-statistics/cdr) are another critical section of a system. Toolpack can generate 2 types of [CDRs](https://tmediadocs.telcobridges.com/telecom-references/cdr-and-statistics/cdr): [RADIUS](/other-pages/operations/radius.md) and [text based CDRs](https://tmediadocs.telcobridges.com/telecom-references/cdr-and-statistics/text-call-detail-records).

#### [RADIUS](/other-pages/operations/radius.md)

Starting with version 2.6, Toolpack can send [CDR](https://tmediadocs.telcobridges.com/telecom-references/cdr-and-statistics/cdr) to multiple [RADIUS](/other-pages/operations/radius.md) servers. Accounting requests will be sent to the first server until it stops responding. Once this happens, Toolpack will send the requests to the second server.

#### [Text Based CDRs](https://tmediadocs.telcobridges.com/telecom-references/cdr-and-statistics/text-call-detail-records)

Only the [active](/products/tmedia/features-and-solutions/features/redundancy-and-high-availability/active-standby.md) instance of the [gateway](https://tmediadocs.telcobridges.com/telecom-references/parameter-reference/gateway) application will write the [CDR](https://tmediadocs.telcobridges.com/telecom-references/cdr-and-statistics/cdr) information locally on the host. When there is a [switchover](/products/tmedia/features-and-solutions/features/redundancy-and-high-availability/switchover.md) the newly [active](/products/tmedia/features-and-solutions/features/redundancy-and-high-availability/active-standby.md) [gateway](https://tmediadocs.telcobridges.com/telecom-references/parameter-reference/gateway) application will write the [CDR](https://tmediadocs.telcobridges.com/telecom-references/cdr-and-statistics/cdr) locally on its host. To gathered all the [CDR](https://tmediadocs.telcobridges.com/telecom-references/cdr-and-statistics/cdr) information, it is important to read the [CDR](https://tmediadocs.telcobridges.com/telecom-references/cdr-and-statistics/cdr) from both hosts.


---

# 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://tmediadocs.telcobridges.com/products/tmedia/features-and-solutions/features/redundancy-and-high-availability/software-cdr.md?ask=<question>&goal=<user_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.