> 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/network.md). # Network Networking is a critical section of the system that is sometimes overlooked. An adequate network will avoid problems like congestion or disconnection. ### Network Redundancy TelcoBridges recommends the use of 2 Gigabytes Ethernet Switches for a [Tmedia](https://telcobridges.com/media-gateways/products/tmedia-gateways/) system. ### VoIP Network The VoIP network are secured interfaces that are use to send signaling and data packets over Ip networks (i.e. Sip, Sigtran, RTP). They are considered secured because it is not possible to control the [Tmedia](https://telcobridges.com/media-gateways/products/tmedia-gateways/) through those interfaces. TelcoBridges provides 2 VoIP ports on all its [VoIP Gateway](https://telcobridges.com/learning/session-border-controller/voip-gateway/) models. A different subnet is required for each VoIP interface. The obvious use of the 2 VoIP ports is to connect one port with a private network and the other to the public network. A second application of the 2 VoIP ports are to connect to your providers using 2 different networks. Here is an example of VoIP network redundancy with a [TMG3200](https://telcobridges.com/media-gateways/products/tmedia-gateways/tmg3200/) ![TMG3200 VoIP Network Redundancy](https://docs.telcobridges.com/w/images/a/a4/Ha_2_Voip_Networks.png) If one of the network is down (because of a switch or cable malfunction), the other network can still reach the providers as seen in the next example ![TMG3200 VoIP Network Redundancy With Network Failure](https://docs.telcobridges.com/w/images/8/8d/Ha_Voip_Network_Fail.png) ### Control Network The Control network is only available for the [TMG7800](https://telcobridges.com/media-gateways/products/tmedia-gateways/tmg7800/) model. The control network allows the [TMG-CONTROL](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/concepts/tctrl/README.md) to manage the [TMG7800](https://telcobridges.com/media-gateways/products/tmedia-gateways/tmg7800/) Telecom units. Each TMG7800 units contains 2 control network interfaces labeled ETH0 and ETH1 respectively. The control network should be on private subnets to avoid lost of packets between the [TMG7800](https://telcobridges.com/media-gateways/products/tmedia-gateways/tmg7800/) units. Which is why TelcoBridges recommends the use of 2 Ethernet switches one for interfaces. Here is an example of the TMG7800 control network. ![TMG7800 Control Network](https://docs.telcobridges.com/w/images/a/af/Ha_Control_Network.png) As shown in the next example, the system remains operational even if there is a network failure ![TMG7800 Control Network With Network Failure](https://docs.telcobridges.com/w/images/e/e0/Ha_Control_Network_Fail.png) The control network requires a maximum of 100Mbps and needs to support Broadcast, ARP and ICMPs. ### TMS Network The TMS network is only available for the [TMG7800](https://telcobridges.com/media-gateways/products/tmedia-gateways/tmg7800/) model. It allows a TMG7800 system to bridge call legs between TMG7800 Telecom Units. It is possible to connect 2 TMG7800 Telecom Units together using RJ45 shielded CAT7 Ethernet cross-over cables. For more than 2 TMG7800 Telecom Units, the TMG7800 system requires a TMG7800-TMS. Each TMG7800 Telecom Units are supplied with 2 TMS interfaces. TelcoBridges recommends to always connect both TMS network ports to protect against failure. Redundant TMS network connection with 2 TMG7800 Telecom units ![TMG7800 TMS Network Back to Back](https://docs.telcobridges.com/w/images/0/00/TMS_back2back.png) Redundant TMG7800-TMS for system larger than 2 TMG7800 Telecom units ![TMG7800 TMS Network With TMG7800-TMS](https://docs.telcobridges.com/w/images/1/12/Ha_TMS_Network_With_TMG7800-TMS.png) Even if one of the TMG7800-TMS fails, the TMG7800 system can still have a connection between its units as shown in the next example ![TMG7800 TMS Network With TMG7800-TMS With Failure](https://docs.telcobridges.com/w/images/b/b4/Ha_TMS_Network_With_TMG7800-TMS_Failure.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/telecom-references/sip-and-voip/network.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.