> 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/sip-and-voip/ip-network/gateway-port.md).

# Gateway Port

This page explains the Gateway Port concept in Telcobridges system, also known as TBX\_GW\_PORT, TbxGwPort or Toolpack [System Id](https://prosbcdocs.telcobridges.com/tmedia-documentation/products/tmedia/features-and-solutions/features/redundancy-and-high-availability/system-id).

The Gateway Port is a UDP port use to control the Tmedia units (Do not confuse the UDP gateway port with the IP gateway address). TelcoBridges strongly recommends that this setting be left at its default value: 12358.

Tmedia units on the same UDP gateway port will be automatically detected by any application using the TBX host library on the same UDP gateway port.

Different UDP gateway ports can be useful for the segmentation of application development from deployments that are both configured to operate on the same physical network and IP subnet. Make certain that all applications are configured to use the same values.

![TBX GW PORT](https://docs.telcobridges.com/w/images/7/79/TBX_GW_PORT.png)

To modify the Gateway Port of a TMedia Unit, Telnet the Telecommunication IP of the unit (not the embedded Linux host's IP in case of TMG product), and use the following command:

*set\_boot*

Press 'enter' to leave current value for all parameters, except when asked for the 'gateway port' value.


---

# 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/telecom-references/sip-and-voip/ip-network/gateway-port.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.