> 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/how-to/how-to-troubleshoot-fax-calls.md).

# How to troubleshoot Fax Calls

To troubleshoot Fax calls, these are the recommended steps:

* Capture Call Trace
* Capture recording (wav file)
* Capture SIP/RTP traffic
* Capture TBReport

### Call Trace

Call Trace was created to trace the callflow from any incoming call through the Tmedia system. It allows to see the incoming call, outgoing calls, TDM channel, SIP SDP and more. This can be accessed from the Web Portal. You can create a filter to see call information. See [Using Unique call trace](/operations-and-support/troubleshooting/signaling-call-flow/call-trace.md).

###

Capture Recording

This process records the media data in a wav file that can be listened to or replayed as a T.30 Fax stream. See [Target Recording](/configuration/web-portal-3-3/troubleshooting.md)

###

Capture SIP/RTP traffic

This is used to capture the T.38 or passthrough traffic. See [VoIP Capture](/configuration/web-portal-3-3/troubleshooting.md)

###

Capture Application logs

This is used to see if any errors or special cases found in the application logs. With version 2.9 or later, see [Capture a TBReport log](/configuration/web-portal-3-3/troubleshooting/tbreport/tbreport.md)

With version 2.8 and below: [Application Log Files](/operations-and-support/troubleshooting/how-to/how-to-troubleshoot-call-routing.md)


---

# 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/how-to/how-to-troubleshoot-fax-calls.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.