> 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/retrieving-call-trace.md).

# Retrieving Call Trace

> **Applies to:** Tmedia 3.0, 3.2, 3.3

**Retrieving calls from memory**

1- Click **Call Trace** in the navigation panel

![RetrievingCallTrace 0](https://docs.telcobridges.com/w/images/7/7e/RetrievingCallTrace_0.png)

2- Set various parameters for call trace, such as

* Time and date range
* Called or calling number
* Network Access Point (NAP)
* Incoming or outgoing calls
* Call Duration, Reason Code

![RetrievingCallTrace 1](https://docs.telcobridges.com/w/images/5/5d/RetrievingCallTrace_1.png)

Once you are satisfied with the filter criteria, click **Apply**

The filter results are displayed.

3-Select a call in the results window to display further information about the call.

![FileAccessingCallTrace 2](https://docs.telcobridges.com/w/images/2/24/FileAccessingCallTrace_2.png)

4- Choose the concerned call entry to view the details.

* Click **Download Audio File**

![FileAccessingCallTrace 3](https://docs.telcobridges.com/w/images/0/0a/FileAccessingCallTrace_3.png)

5- You can choose to export the call trace file as an HTML file.

* Click **Export**

![FileAccessingCallTrace 4](https://docs.telcobridges.com/w/images/a/a6/FileAccessingCallTrace_4.png)

**Retrieving calls from files**

By default, the system stores up to 10,000 call legs in memory. If the call is no longer in memory, it may be retrieved by using information from the uctdata log files. To search for calls that are no longer in memory, do the following:

1- Start [tbx\_cli\_tools\_remote](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/api/how-to-use-tbx-cli-tools-remote-program/README.md)

2- Select tbuctwriter

3- To know which files are available, as well as the start and end time of each file, use the following options:

* 'p' to print all uctdata files on disk

To load a file into memory for viewing with the Web Portal:

* Option 'o' followed by the data filename (uctdata\*)

Use the Web Portal to search for calls using the appropriate filter criteria. The memory will not be overwritten until you restore normal process.

To restore normal process:

* Option ‘c’ to clear memory
* Option ‘l’ to have calls put in memory again

By default the file is located in the following path:

```
/lib/tb/toolpack/setup/12358/3.2/apps/tbuctwriter/uctdata*
```

**Auto refresh of call trace list**

By default, there is no option from the web portal to refresh the page with the call trace list.

If you wish to have this function enabled, please follow the instructions from the freesbc forums : [Auto Refresh for Call Trace](https://forums.freesbc.com/t710-auto-refresh-on-call-trace-web-page)


---

# 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/retrieving-call-trace.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.