> 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/server-and-os-administration/hardware-networking.md). # Hardware:Networking Networking is a critical section of the system that is sometimes overlooked. An adequate network will avoid problems like congestion or disconnection. ### Ethernet Network TelcoBridges recommends the following when setting up a Ethernet network: * The entire network should be running at 1 Gb/s (all Ethernet switches, Ethernet cards and Ethernet cables). * Use 2 Managed Ethernet Switches. * Use different subnet for each control network and each voip network. * Use VLAN from the Managed Switches to separate traffic (1 VLAN for the control network, 1 VLAN for the voip network per Ethernet switch). **Warning** [Ip teaming or Ip bonding](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/sip-voip/voip-bonding/README.md) is not recommended. A host with Ip teaming configure will not be able to control [Tdev](https://telcobridges.com/products/development-platforms-tdev/) devices. #### Control Network The control network is the Ethernet network used by Toolpack to control the Toolpack applications and the [Tdev](https://telcobridges.com/products/development-platforms-tdev/) hardware products. TelcoBridges provides 2 control ports on all its [Tdev](https://telcobridges.com/products/development-platforms-tdev/) (except TMP800). The redundancy of the control network is done by using 2 independent network (1 for each control ports). **Recommended Setup** Here is a schematic of the recommended control network connection for a high availability system: ![Control Network Ha connection](https://docs.telcobridges.com/w/images/3/3a/Control_Network_Ha_connection.png) #### Voip Network The voip network are secured interfaces that are use to send signaling and data over Ip networks (i.e. Sip, Sigtran). They are considered secured because it is not possible to control the [Tdev](https://telcobridges.com/products/development-platforms-tdev/) through those interfaces. TelcoBridges provides 2 voip ports on all its [Tdev](https://telcobridges.com/products/development-platforms-tdev/) products (except TMP800). The redundancy of the voip network is done by using 2 independent network (1 for each voip ports). **Recommended Setup** Here is a schematic of the recommended voip network connection for a high availability system: ![Voip Network Ha connection](https://docs.telcobridges.com/w/images/5/5d/Voip_Network_Ha_connection.png) ### TMS Network The TMS network is use to connect the multiple [TMP6400](https://telcobridges.com/products/development-platforms-tdev/tmp6400-tdev-voip-gateway-development-platform/) or [TMP7900](https://telcobridges.com/products/development-platforms-tdev/tmp6400-tdev-voip-gateway-development-platform/) telecom units together. It allows a [TMP6400](https://telcobridges.com/products/development-platforms-tdev/tmp6400-tdev-voip-gateway-development-platform/) to bridges an incoming call leg to another [TMP6400](https://telcobridges.com/products/development-platforms-tdev/tmp6400-tdev-voip-gateway-development-platform/) using the TMS network instead of wasting tdm or voip resources to connect. It is possible to expand a system from 2016 non-blocking bridges (1 TMP6400) up to 32768 non-blocking bridges (16 TMP6400) with the TMS network. The TMS network redundancy is achieved by using 2 TMS1600 and connecting each TMP6400 to both TMS1600. The TMP6400 has 2 TMS port called (TMS-1 and TMS-2). The TMS connection requires a very specific type of cable see [installation guides section 2.6 (Connecting the TMP6400s to the TMS1600)for more info](https://docs.telcobridges.com/w/images/5/56/TMP6400_Installation_Guide_Issue2.2.pdf) **Recommended Setup** Here is a schematic of the recommended TMS network connection for a high availability system: ![Tms Network Ha connection](https://docs.telcobridges.com/w/images/5/50/Tms_Network_Ha_connection.png) --- # 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/tmedia-documentation/server-and-os-administration/hardware-networking.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.