> 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/troubleshooting-and-support/troubleshooting-tips-and-actions/configuring-call-trace.md).

# Configuring Call Trace

Call Trace is a diagnostic tool that traces the path a call takes through ProSBC, reporting routing decisions and other details of the call path.

Call Trace is a diagnostic tool that is designed to trace the path a call takes through a system, and to provide information about numerous aspects of the call path, such as:

* The routing decision
* The outgoing call
* Subsequent outgoing calls, in the case of a route retry
* Parameters selected for a SIP SDP
* The SIP Call-id
* The trunk and timeslot chosen for TDM protocols
* The termination result code, and more.

A call path is shown as separate call legs, distinguishing the incoming portion with other portions of a call. Calls may be filtered by called number, calling number, Network Access Point (NAP), time of day range, protocol and direction.

Call trace enables a default of 10,000 call legs to be stored in the system and to be viewed using the Web Portal. This value can be increased from the Call Trace application configuration parameters.

1- Select Applications in the navigation menu.

<figure><img src="https://docs.telcobridges.com/w/images/0/02/EnableCallTrace_B_0.png" alt=""><figcaption></figcaption></figure>

\
2- Select the tbuctwriter application

<figure><img src="https://docs.telcobridges.com/w/images/d/d8/ConfigureCallTrace_B_0.png" alt=""><figcaption></figcaption></figure>

\
3- Click Application Parameters

<figure><img src="https://docs.telcobridges.com/w/images/c/ce/ConfigureCallTrace_B_1.png" alt=""><figcaption></figcaption></figure>

\
4- Configure the Trace Level and other associated trace parameters.

* Click Save

<figure><img src="https://docs.telcobridges.com/w/images/9/98/ConfigureCallTrace_B_2.png" alt=""><figcaption></figcaption></figure>

### List of Parameters

* [Trace Level](/configuration-details/configuration-parameters-all.md#parameter-call-trace-trace-level)
* [Maximum compressed directory size](/configuration-details/configuration-parameters-all.md#parameter-call-trace-maximum-compressed-directory-size)
* [Maximum file size](/configuration-details/configuration-parameters-all.md#parameter-maximum-file-size)
* [Maximum call legs](/configuration-details/configuration-parameters-all.md#parameter-maximum-call-legs)
* [Consulted legs recall](/configuration-details/configuration-parameters-all.md#parameter-consulted-legs-recall)


---

# 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/troubleshooting-and-support/troubleshooting-tips-and-actions/configuring-call-trace.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.