> 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/telecom-concepts/how-to-troubleshoot-call-routing.md). # How to Troubleshoot Call Routing To debug calls, different methods can be used: ### Using the Call Detail Records This can be done in the configuration database, using RADIUS or in text files. See [Call Detail Records (CDR)](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/concepts/call-detail-record/README.md) ### Using the Call Trace Tool 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 Call Trace](https://telcobridges.com/learning/sip-trunking/how-to-read-a-sip-trace/). ### Using the web portal status ``` Status -> NAP -> Edit ``` You can see how many instantaneous calls incoming, outgoing, in the last hour, in the last 24 hours, etc. ### Using the applications log files Brief details on the application: * **gateway** application is for high-level call routing, like called number, Network Access Points, routing scripts, regular expressions. * **toolpack\_engine** handles the protocols (SS7, SIP, ISDN, CAS, Sigtran, etc.) and media (RTP, TDM, tones, etc) * **toolpack\_sys\_manager** handles the configuration of the system * **tboamapp** controls the startup of the applications and system upgrades * **tbstreamserver** is used for playing and recording files; by default this application is not started. See How to Start Stream Server * **tblogtrace** are low-level logs coming from the Telecom platform * **tbsnmpagent/tbsnmpmux** allows SNMP queries to unit * **tbuctwriter** captures call traces #### Change an Application log trace level You can change the trace level of the application here: ``` Applications-> [Application name] -> Advanced parameters -> Default Trace Level -> Save ``` And then activate the new configuration. Trace level 3 for \*\*gateway \*\*and **toolpack\_engine** application will give most of the required information. For a more detailed walk-through see: [How to change an application's trace level](https://github.com/telcobridges-main/tmedia-wiki/tree/main/tmedia/operations/how-to-lower-the-trace-level-on-an-application/README.md) #### Get log files from web portal ``` Maintenance -> Logs -> Select filename -> 2000 lines -> select Read ``` #### Get the log files from the server You can get the files directly from the server running Toolpack. Connect sFTP (for example using Winscp or filezilla) to the management port of the unit and get the files at this location: ``` /lib/tb/toolpack/setup/12358/3.1/apps/ ``` ### Using the signaling traces You can get the signaling traces (SS7, ISDN and SIP) using the tbsigtrace program: [using tbsigtrace](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/signalling/tbsigtrace-signaling-trace-capture-tool/README.md) ### Using the Toolpack programs backdoor tool You can access to the toolpack applications directly by using the tbx\_cli\_tools\_remote application. This application allows full control over any Toolpack application. This allows for example to view real time calls going through the Toolpack Engine. Select this to learn [How to use tbx cli tools remote program](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/api/how-to-use-tbx-cli-tools-remote-program/README.md). Typical errors: 404 not found --- # 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/telecom-concepts/how-to-troubleshoot-call-routing.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.