> 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/ss7-and-signalling/software-signaling-protocols.md).

# Software:Signaling Protocols

The most recent signaling protocols have inherent redundancy and high availability features. For the other signaling protocols, there are still way to improve service availability.

### TMG800 / TMG3200 Series

#### [SS7](https://telcobridges.com/media-gateways/solutions/signaling/migrating-ss7-sigtran/)

TelcoBridges recommends to use 2 timeslots as MTP2 links on different line interface. This will protect against [E1/T1](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/transmission/t1-e1-and-j1-interfaces/README.md) or [DS3](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/ds3-interfaces/README.md) failure. Also, the [TMG3200-DS3](http://www.telcobridges.com/en/tmg3200.aspx) and [TMG3200-STM1](http://www.telcobridges.com/en/tmg3200.aspx) have 2 signaling ports that can be configure as MTP2 links.

The following example shows the redundancy of [MTP2](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/mtp2/README.md) links.

![TMG3200 MTP2 Redundancy Setup](https://docs.telcobridges.com/w/images/4/46/Ha_TMG3200_MTP2.png)

The [SS7](https://telcobridges.com/media-gateways/solutions/signaling/migrating-ss7-sigtran/) network is still available even if 1 link goes down.

![TMG3200 MTP2 Redundancy Setup With Link Down](https://docs.telcobridges.com/w/images/1/1c/Ha_TMG3200_MTP2_Link_Down.png)

#### [SIGTRAN](https://telcobridges.com/media-gateways/solutions/signaling/migrating-ss7-sigtran/)

[SIGTRAN](https://telcobridges.com/media-gateways/solutions/signaling/migrating-ss7-sigtran/) supports multiple destination addresses and peers to create redundancy.

The following example shows how [M2UA](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/sigtran-m2ua/README.md) can take advantage of the [Tmedia](https://telcobridges.com/media-gateways/products/tmedia-gateways/) dual VoIP interfaces to create a redundant system (Note: [M2PA](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/m2pa/README.md) and [M3UA](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/m3ua/README.md) have similar features).

![TMG3200 M2UA Redundancy Setup](https://docs.telcobridges.com/w/images/b/b1/Ha_TMG3200_M2UA.png)

The [M2UA](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/sigtran-m2ua/README.md) system is still operational even if there is a network failure.

![TMG3200 M2UA Redundancy Setup](https://docs.telcobridges.com/w/images/6/63/Ha_TMG3200_M2UA_Network_fail.png)

The [M2UA](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/sigtran-m2ua/README.md) system is still operational even if a [M2UA](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/sigtran-m2ua/README.md) peer goes down.

![Power Distribution Recommended Setup](https://docs.telcobridges.com/w/images/5/5b/Ha_TMG3200_M2UA_Peer_fail.png)

### TMG7800

#### CAS/ISDN/SIP

With [TMG7800](https://telcobridges.com/media-gateways/products/tmedia-gateways/tmg7800/) system composed of multiple telecom units, it is recommended to spread the TDM connections between the providers between the telecom units.

The next example shows 2 TMG7800 Telecom units connected to 2 providers with ISDN stacks load shared between them (CAS and SIP can be configured in a similar fashion):

![TMG7800 TDM Interfaces Load Sharing](https://docs.telcobridges.com/w/images/6/69/Ha_TMG7800_TDM_Load_Share.png)

Even if a telecom units fails, all the providers will be accessible through other unit:

![TMG7800 TDM Interfaces Load Sharing With Telecom Unit Failure](https://docs.telcobridges.com/w/images/7/70/Ha_TMG7800_TDM_Load_Share_Fail.png)

#### SS7

TelcoBridges [SS7](https://telcobridges.com/media-gateways/solutions/signaling/migrating-ss7-sigtran/) stack has a multitude of redundancy mechanism that can fortify a [TMG7800](https://telcobridges.com/media-gateways/products/tmedia-gateways/tmg7800/) system against failure.

* [MTP2](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/mtp2/README.md) Link Redundancy
* [MTP3](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/mtp3/README.md) Layer is shared between multiple telecom units
* [ISUP](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/isup/README.md) Layer Redundancy

With the TMG7800, it is recommended to configure the [Tmedia](https://telcobridges.com/media-gateways/products/tmedia-gateways/) system with at least 2 [MTP2](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/mtp2/README.md) links each on different telecom units and 2 [ISUP](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/isup/README.md) each one stack on different TMG7800 telecom units.

In the following example, the system [SS7](https://telcobridges.com/media-gateways/solutions/signaling/migrating-ss7-sigtran/) will still be operational whether a link, stack or [TMG7800](https://telcobridges.com/media-gateways/products/tmedia-gateways/tmg7800/) telecom units failure.

![TMG7800 Recommended SS7 Network Configuration](https://docs.telcobridges.com/w/images/b/bb/Ha_TMG7800_SS7_Network.png)

#### SIGTRAN

The [TMG7800](https://telcobridges.com/media-gateways/products/tmedia-gateways/tmg7800/) can really create a fully redundant [SIGTRAN](https://telcobridges.com/media-gateways/solutions/signaling/migrating-ss7-sigtran/) system, it supports multiple destination addresses, multiple peers.

The following example shows a [SIGTRAN](https://telcobridges.com/media-gateways/solutions/signaling/migrating-ss7-sigtran/) system with 2 [MTP2](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/mtp2/README.md) links, 2 [M2UA](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/sigtran-m2ua/README.md) links and 2 [M2UA](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/sigtran-m2ua/README.md) peers (Note: [M2PA](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/m2pa/README.md) and [M3UA](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/m3ua/README.md) have similar features).

![TMG7800 M2UA Redundancy Setup](https://docs.telcobridges.com/w/images/f/f5/Ha_TMG7800_M2UA.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/ss7-and-signalling/software-signaling-protocols.md?ask=<question>&goal=<endgoal>
```

`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.
