> For the complete documentation index, see [llms.txt](https://kb.hostednetwork.com.au/support/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.hostednetwork.com.au/support/services/voice-over-ip-voip/technical-references/sip-trunk-requirements-ports-protocols-and-codecs.md). # SIP Trunk Requirements: Ports, Protocols, and Codecs This article outlines the essential requirements for SIP trunks #### Network Ports: * **SIP Signaling (Port 5060):** This port is crucial for establishing, managing, and terminating SIP calls. All SIP communication between your PBX and the Hosted Network SIP trunk uses UDP (User Datagram Protocol) on port 5060. * **RTP Media (Ports 10000-20000):** Real-time Transport Protocol (RTP) carries the actual voice data during a call. SIP trunking typically utilizes a range of UDP ports between 10000 and 20000 for sending and receiving RTP media streams. #### Network Protocols: * **UDP (User Datagram Protocol):** SIP trunking relies on UDP for both SIP signaling (port 5060) and RTP media streams (ports 10000-20000) #### Supported Codecs: Codecs (coder/decoder) compress and decompress voice data for efficient transmission over the internet. Our SIP trunk supports various codecs, * **G.711** * **G.729** --- # 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://kb.hostednetwork.com.au/support/services/voice-over-ip-voip/technical-references/sip-trunk-requirements-ports-protocols-and-codecs.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.