> 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/parameter-reference/cdr.md).

# CDR and billing parameters

Call detail records, billing and RADIUS. 11 parameters.

## A

| Parameter                 | Description                                         |
| ------------------------- | --------------------------------------------------- |
| **Additional dictionary** | Additional RADIUS dictionary for custom attributes. |

## C

| Parameter               | Description                                                                                                       |
| ----------------------- | ----------------------------------------------------------------------------------------------------------------- |
| **CDR format (end)**    | Format of the text CDR record written at the time the call is terminated.                                         |
| **CDR format (start)**  | Format of the text CDR record written only at the time the call is answered.                                      |
| **CDR format (update)** | Format of the text CDR log written periodically during call if the CDR option Enable periodic CDR update is used. |
| **CDR log file path**   | Path of the CDR log file.                                                                                         |

## M

| Parameter                                     | Description                                                                         |
| --------------------------------------------- | ----------------------------------------------------------------------------------- |
| **Max total size of gzipped CDR logs**        | Maximum total size (in bytes) of all gzipped log file segments on disk.             |
| **Maximum accounting concurrent records**     | Maximum number of simultaneous accounting records to be sent to RADIUS servers.     |
| **Maximum authorization concurrent requests** | Maximum number of simultaneous authorization requests to be sent to RADIUS servers. |
| **Maximum CDR log file segment size**         | The maximum size of one log-file segment.                                           |

## R

| Parameter                     | Description                                                      |
| ----------------------------- | ---------------------------------------------------------------- |
| **Rotation delay in seconds** | Delay, in seconds, at which the log file is rotated and gzipped. |

## T

| Parameter             | Description                 |
| --------------------- | --------------------------- |
| **Test Generate CDR** | Create a CDR for this call. |


---

# 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/telecom-references/parameter-reference/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.