> 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/operations-and-support/troubleshooting/signaling-call-flow/call-trace.md).
# Call Trace
Call trace (uct) was created to trace the callflow from an incoming call through the Tmedia system. It enables viewing of the incoming call, the routing decision, outgoing calls, other outgoing calls if there is route retry, the parameters selected for SIP SDP, the SIP Call-id, the trunk and timeslot chosen for TDM protocols, the termination result code, and more.
It stores information for long periods of time and search for calls in history. The last 10,000 call legs (default size) can be seen directly in the web portal. Older logs can be loaded and viewed on the same system, or exported to other systems. Once a specific call has been consulted, it will remain in memory for a longer period of time, so that it can be consulted later on.\
Calls to view can be filtered according to called number, calling number, Network Access Point (NAP), time of day range, protocol and direction.
### Features
* Troubleshooting call flows
* Download audio from recorded calls
* Terminate suspicious calls
#### Filter parameters
* [Filter parameters reference guide](https://tmediadocs.telcobridges.com/telecom-references/developer-reference/routing-scripts/filter-parameters-reference-guide)
### Configuration
* [Tmedia Call Trace v3.2](/configuration/web-portal-previous/web-portal-3-2/troubleshooting/troubleshooting.md#call-trace)
* [Tmedia Call Trace v3.0](/other-pages/troubleshooting/tmedia-tdev-and-tsig-web-portal-3-0-troubleshooting.md#call-trace)
* [ProSBC Call Trace](https://prosbcdocs.telcobridges.com/troubleshooting-and-support/troubleshooting-tips-and-actions/configuring-call-trace)
Click here for other versions
* [Tmedia Call Trace v2.10](/configuration/web-portal-previous/web-portal-2-10/tmedia-tdev-and-tsig-web-portal-2-10-troubleshooting.md#call-trace)
* [Tmedia Call Trace v2.9](/configuration/web-portal-previous/web-portal-2-9/web-portal-2-9-troubleshooting.md#call-trace)
* Tsbc Call Trace v2.10: documentation is no longer published. Contact [technical support](/operations-and-support/support/contacting-telcobridges-technical-support.md) if you need it.
---
# 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/operations-and-support/troubleshooting/signaling-call-flow/call-trace.md?ask=&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.