> 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/operations-and-support/troubleshooting/software/troubleshooting-toolpack/submitting-an-issue.md).

# How To Submit A Problem

When submitting a problem, your ability to provide relevant information about your system will greatly help the TelcoBridges support team in its efforts to bring to you a quick resolution.

### Required information: System configuration

Please provide the following required information:

**Description of the issue**

* Describe the issue and clearly as possible and with as much details possible.
* Describe the steps or context in which the issues was experienced.
* Provide steps to reproduce the issue, if possible.
* Tracking number (If one was already provided to you by TelcoBridges TB Support)

**System information**

* Type of TelcoBridges hardware device(s) (ex. [TMG800](/tmedia-documentation/products/tmedia/tmg800.md), [TMG3200](/tmedia-documentation/products/tmedia/tmg3200.md), TMP6400, etc.)
* Serial numbers of TelcoBridges hardware units (ex. TBxxxxxxx)
* Topology diagram
* Call flow diagram (Direction of calls)
* IP network and connectivity diagram

**System configuration / set-up**

* Configuration summary (ex. SIP to SS7, MGC + H.248, ISDN Monitoring, etc.).
  * Provide the system configuration (see [Configuration backup](/tmedia-documentation/operations-and-support/troubleshooting/software/troubleshooting-toolpack.md#system-configuration-backup)).
* Software release number (ex. 2.10.8)

**Troubleshooting capture**\
For troubleshooting, the TelcoBridges support team may require additional traces from the system. See [Troubleshooting](/tmedia-documentation/operations-and-support/troubleshooting/how-to/troubleshooting.md)

* [TBReport](/tmedia-documentation/configuration/web-portal-3-3/troubleshooting/tbreport/tbreport.md)
* [Call Trace](/tmedia-documentation/operations-and-support/troubleshooting/signaling-call-flow/call-trace.md)
* [Low-level signalling trace](/tmedia-documentation/operations-and-support/troubleshooting/how-to/tbsigtrace-signaling-trace-capture-tool.md)
* [VoIP capture](/tmedia-documentation/operations-and-support/troubleshooting/how-to/voip-ethernet-capture.md)
* [FreeSBC VoIP Ethernet capture](/tmedia-documentation/operations-and-support/troubleshooting/rtp-codecs-tones/voip-ethernet-capture-freesbc.md)
* [Recording](https://prosbcdocs.telcobridges.com/telecom-references/voice-and-media/target-recording)
* [Applications logs](/tmedia-documentation/operations-and-support/troubleshooting/how-to/how-to-troubleshoot-call-routing.md#using-the-applications-log-files)

### Logging the issue in TBsupport tracking system

Once you have gathered all of the information required above, please log it in the TBsupport tracking system (bugzilla) here:\
<https://support.telcobridges.com>\
This will assign to you a tracking number to follow the progress of the issue. Your account e-mail will receive an update on each comment that is logged.\
If you do not have a TBsupport tracking system account, please request one at <support@telcobridges.com> at the same time as sending the information for the issue.

### Providing remote access to your system

If you choose to provide TelcoBridges with remote access to your system for the purpose of issue analysis and resolution, please provide the connection Information (SSH, Join.me, VPN, GoToMeeting, etc.)

## In this section

* [Troubleshooting Toolpack](/tmedia-documentation/operations-and-support/troubleshooting/software/troubleshooting-toolpack/submitting-an-issue/troubleshooting-toolpack.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://prosbcdocs.telcobridges.com/tmedia-documentation/operations-and-support/troubleshooting/software/troubleshooting-toolpack/submitting-an-issue.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.