> 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/how-to/how-to-debug-voip.md). # How to debug VoIP The VoIP ports can be used for SIP, RTP and Sigtran (M2PA, M2UA or M3UA). Here are different way sto debug: * Setting the VoIP address. Follow the Web portal [Configuring Ip Interfaces](/tmedia-documentation/other-pages/other/configuring-ip-interfaces.md). * Verifying the IP address configured From the web portal: ``` Status -> Adapters -> voip0 (or any other interface) ``` From the command lines: Access to the Tmedia unit using SSH. Access the telecom baseboard of the Tmedia using telnet ``` telnet 172.31.1.1 ``` ``` ifconfig -a ``` * Pinging a remote device from the VoIP ports Access to the Tmedia unit using SSH. Access the telecom baseboard of the Tmedia using telnet ``` telnet 172.31.1.1 ``` Ping the remote unit by specifying the local VoIP port to use. For example, if the IP address of the local VoIP port is 68.67.49.147 and the remote is 208.94.105.1 : ``` ping -B 68.67.49.147 208.94.105.1 ``` * [VoIP ethernet capture](/tmedia-documentation/operations-and-support/troubleshooting/how-to/voip-ethernet-capture.md) * [SBC VoIP Ethernet Capture](/tmedia-documentation/operations-and-support/troubleshooting/rtp-codecs-tones/voip-ethernet-capture-freesbc.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/how-to/how-to-debug-voip.md?ask=&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.