> 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/redundancy-and-high-availability.md). # Redundancy and High Availability (Click here for ProSBC High Availability and 1+1) This page describes the TelcoBridges [VoIP Gateway](https://telcobridges.com/learning/session-border-controller/voip-gateway/) high availability features. TelcoBridges' products are designed with the following two goals in mind: 1. Recover from a system failure and minimize the system down-time and network instability, as much as possible. This is achieved with fault tolerance and redundancy designed into the very architecture of the product. 2. Keep active calls open after a fail-over, whenever possible. ### TelcoBridges High Availability and Redundancy TelcoBridges high availability and redundancy is comprised of a collection of features. These features enable customers to add as many HA and redundancy fdeatures to their systems as required. To learn more about high availability and redundancy, see: * [TMG800 datasheet](https://telcobridges.com/products-tmedia-voip-gateways-tmg800-datasheet/) * [TMG3200 datasheet](https://telcobridges.com/products-tmedia-voip-gateways-tmg3200-tmg3200-datasheet/) * [TMG7800 datasheet](https://telcobridges.com/products-tmedia-voip-gateways-tmg7800-datasheet/) ### Definitions The following is a list of terms that are used in the description of high availability features: * [Active Calls](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/misc/active-calls/README.md) * [Active/Standby](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/misc/active-standby/README.md) * [Load Sharing](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/misc/load-sharing/README.md) * [Master/Slave](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/misc/master-slave/README.md) * [Primary/Secondary](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/misc/primary-secondary/README.md) * [Resynchronization](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/misc/resynchronization/README.md) * [Switchover](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/misc/switchover/README.md) * [Switchover Period](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/misc/switchover-period/README.md) * [Transient Calls](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/misc/transient-calls/README.md) ### TMG800 Features * [Power Supply](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/misc/power-supply/README.md) * [VoIP Network](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/sip-voip/network/README.md#voip-network) * [Clocking](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/transmission/clocking/README.md) * [Signaling Protocols](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/signalling/software-signaling-protocols/README.md#tmg800-tmg3200-series) ### TMG3200 Features * [Power Supply](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/misc/power-supply/README.md) * [VoIP Network](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/sip-voip/network/README.md#voip-network) * [OC3/STM-1 Interface](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/transmission/tdm-interfaces/README.md#stm-1oc-3) * [Clocking](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/transmission/clocking/README.md) * [Signaling Protocols](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/signalling/software-signaling-protocols/README.md#tmg800-tmg3200-series) ### TMG7800 Features * [Power Supply](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/misc/power-supply/README.md) * [Network](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/sip-voip/network/README.md) * [VoIP Network](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/sip-voip/network/README.md#voip-network) * [Control Network](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/sip-voip/network/README.md#control-network) * [TMS Network](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/sip-voip/network/README.md#tms-network) * [Tdm Interfaces](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/transmission/tdm-interfaces/README.md) * [Clocking](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/transmission/clocking/README.md) * [Signaling Protocols](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/signalling/software-signaling-protocols/README.md#tmg7800) * [TMG-CONTROL](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/misc/software-tctrl/README.md) * [Host redundancy](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/misc/hosts/README.md) * [Hard Disks](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/misc/hosts/README.md#hard-disk) --- # 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/redundancy-and-high-availability.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.