> For the complete documentation index, see [llms.txt](https://tmediadocs.telcobridges.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tmediadocs.telcobridges.com/products/tmedia/features-and-solutions/features/redundancy-and-high-availability/software-signaling-stack-ss7.md).

# Software:Signaling Stack:SS7

[SS7](https://tmediadocs.telcobridges.com/telecom-references/ss7-and-signalling/ss7) has intrinsic high availability features. TelcoBridges [MTP3](https://tmediadocs.telcobridges.com/telecom-references/ss7-and-signalling/mtp3) stack is responsible for most of the redundancy and [Load Sharing](/products/tmedia/features-and-solutions/features/redundancy-and-high-availability/load-sharing.md) feature of SS7.

TelcoBridges [SS7](https://tmediadocs.telcobridges.com/telecom-references/ss7-and-signalling/ss7) stack has a multitude of redundancy mechanism that can fortify a [TMG7800](/products/tmedia/tmg7800.md) system against failure.

* [MTP2](https://tmediadocs.telcobridges.com/telecom-references/ss7-and-signalling/mtp2) Link Redundancy
* [MTP3](https://tmediadocs.telcobridges.com/telecom-references/ss7-and-signalling/mtp3) Layer is shared between multiple telecom units
* [ISUP](https://tmediadocs.telcobridges.com/telecom-references/ss7-and-signalling/isup) Layer Redundancy

The [MTP3](https://tmediadocs.telcobridges.com/telecom-references/ss7-and-signalling/mtp3) stack is distributed through all the Tdev hardware of the system and will [load share](/products/tmedia/features-and-solutions/features/redundancy-and-high-availability/load-sharing.md) the traffic through the [MTP3](https://tmediadocs.telcobridges.com/telecom-references/ss7-and-signalling/mtp3) linksets and [MTP2](https://tmediadocs.telcobridges.com/telecom-references/ss7-and-signalling/mtp2) links.To improve reliability of the system, TelcoBridges recommend to add [MTP2](https://tmediadocs.telcobridges.com/telecom-references/ss7-and-signalling/mtp2) links from different Tdev devices to a [MTP3](https://tmediadocs.telcobridges.com/telecom-references/ss7-and-signalling/mtp3) linksets. If a unit is lost, the [MTP3](https://tmediadocs.telcobridges.com/telecom-references/ss7-and-signalling/mtp3) linksets will still be available to use.

Here is an example:

![High availability SS7 Network example](https://docs.telcobridges.com/w/images/c/c9/HA_Tdev_SS7_Network.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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://tmediadocs.telcobridges.com/products/tmedia/features-and-solutions/features/redundancy-and-high-availability/software-signaling-stack-ss7.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.