> 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/voice-and-media/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](https://telcobridges.com/learning/sip-trunking/how-to-read-a-sip-trace/).

###

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](https://github.com/telcobridges-main/tmedia-wiki/tree/main/tmedia/configuration/web-portal-2-9-troubleshooting/README.md#target-recording)

###

Capture SIP/RTP traffic

This is used to capture the T.38 or passthrough traffic. See [VoIP Capture](https://github.com/telcobridges-main/tmedia-wiki/tree/main/tmedia/configuration/web-portal-2-9-troubleshooting/README.md#voip-ethernet-capture)

###

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](https://github.com/telcobridges-main/tmedia-wiki/tree/main/tmedia/operations/tbreport/README.md)

With version 2.8 and below: [Application Log Files](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/concepts/how-to-troubleshoot-call-routing/README.md#using-the-application-log-files)


---

# 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/telecom-references/voice-and-media/how-to-troubleshoot-fax-calls.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.