> 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/server-and-os-administration/submitting-an-issue-to-telcobridges-support.md). # Submitting an Issue to TelcoBridges Support 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](https://telcobridges.com/media-gateways/products/tmedia-gateways/tmg800/), [TMG3200](https://telcobridges.com/media-gateways/products/tmedia-gateways/tmg3200/), [TMP6400](https://telcobridges.com/products/development-platforms-tdev/tmp6400-tdev-voip-gateway-development-platform/), 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](https://github.com/telcobridges-main/tmedia-wiki/tree/main/tmedia/operations/troubleshooting-toolpack/README.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](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/sip-voip/troubleshooting/README.md) * [TBReport](https://github.com/telcobridges-main/tmedia-wiki/tree/main/tmedia/operations/tbreport/README.md) * [Call Trace](https://telcobridges.com/learning/sip-trunking/how-to-read-a-sip-trace/) * [Low-level signalling trace](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/signalling/tbsigtrace-signaling-trace-capture-tool/README.md) * [VoIP capture](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/sip-voip/voip-ethernet-capture/README.md) * [FreeSBC VoIP Ethernet capture](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/sip-voip/voip-ethernet-capture-on-a-prosbc/README.md) * [Recording](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/concepts/target-recording/README.md) * [Applications logs](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/concepts/how-to-troubleshoot-call-routing/README.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>(https://support.telcobridges.com)](https://prosbcdocs.telcobridges.com/tmedia-documentation/server-and-os-administration/https:/support.telcobridges.com>\(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 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.) --- # 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/server-and-os-administration/submitting-an-issue-to-telcobridges-support.md?ask=&goal= ``` `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.