> 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/appendices/appendix-a-glossary/glossary-toolpack/glossary-tboamapp/glossary-tbtoolpack-service/system-id.md).

# System Id

The System Id, also called TBX\_GW\_PORT or TbxGwPort, uniquely identifies a system and lets multiple systems coexist on the same IP network.

The SystemId is a *unique id* representing an entire system. This field is also known as the [TBX\_GW\_PORT](/appendices/appendix-a-glossary/glossary-toolpack/glossary-tboamapp/glossary-tbtoolpack-service/system-id/gateway-port.md) or [TbxGwPort](/appendices/appendix-a-glossary/glossary-toolpack/glossary-tboamapp/glossary-tbtoolpack-service/system-id/gateway-port.md).

It allows multiple system to co-exist on the same IP network.

It is also used as http port on localhost to access TBToolpack WebPortal.(ie: [http://localhost:12358](http://localhost:12358/))

The SystemId is also the [TBX\_GW\_PORT](/appendices/appendix-a-glossary/glossary-toolpack/glossary-tboamapp/glossary-tbtoolpack-service/system-id/gateway-port.md) UDP port use to control the Tmedia units.

```
Range: 12358-12458
Default: 12358 (TelcoBridges strongly recommends that this setting be left at its default value)
```

All TBToolpack installations part of the same system must use the same SystemId.


---

# 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/appendices/appendix-a-glossary/glossary-toolpack/glossary-tboamapp/glossary-tbtoolpack-service/system-id.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.