> 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/products/tmedia/tmg7800.md).

# TMG7800

Front view of a TMG7800 VoIP gateway cluster

The TMG7800 VoIP gateway meets your system requirements by providing you with up to 131,072 universal voice ports (32,768 per cluster) and a flexibility to switch between TDM and IP. This capability is enhanced by being able to support a vast selection of signaling protocols, such as SS7, ISDN PRI, SIGTRAN, SIP, SIP-I/SIP-T and H.248, as well as a wide range of media processing codecs across a mix of T1/E1, DS3 and OC3/STM-1 interfaces, all within the same system.

The TelcoBridges Tmedia TMG7800 high availability system says it all. This multi-unit VoIP gateway is scalable and 100% redundant ensuring an infallible carrier-grade network. Leveraging redundant integrated VoIP gateway controllers, the TMG7800 delivers core network applications such as VoIP gateway, TDM switching, VoIP hairpinning with [transcoding](https://prosbcdocs.telcobridges.com/telecom-references/voice-and-media/transcoding), with advanced [call routing](https://prosbcdocs.telcobridges.com/telecom-references/developer-reference/routing-scripts/call-routing) and fax over IP. The TMG7800 can also host additional third-party applications such as softswitches and session border controllers locally, further answering the need for device consolidation and convergence. With separate chipsets for media processing and separate processors for call routing and signaling, the TMG7800 VoIP gateway provides full low-latency non-blocking capability for up to 32,768 channels per cluster. Up to 4 clusters can be included within a single TMG7800 system creating a 131,072 channels non-blocking switch.

The TMG7800 VoIP gateway provides the ultimate in flexibility, easily scaling to a fully configured capacity of 1024 T1/E1, 48 DS3 or 16 OC3/STM-1 interfaces per cluster as service uptake increases, with the ability to mix and match different interface types.

A TMG7800 system consists of four (4) distinct hardware devices:

* TMG7800-CTRL: This is the system's controller. It performs call handling, call routing, CDR collection, and system configuration management. The TMG7800-CTRL also presents the system's Web Portal for OAM\&P. The TMG7800-CTRL supports redundancy. The TMG7800-CTRL can be installed on a virtual machine, VMware or KVM system (like Proxmox).
* TMG7800-TE or -DS3 or -STM1: These are the gateway units that form the TMG7800 system. These gateway units provide the T1, E1, DS3 and/or OC3/STM-1 links and VoIP port capacity required to deliver the desired voice channel capacity. The TMG7800 gateway units are controlled by the TMG7800-CTRL controllers.
* TMG7800-TMS: This device is optional. The TMG7800-TMS is a non-blocking media switch that enables port to port switching between the TMG7800 gateway units of the same cluster. The TMG7800-TMS uses an any-to-any TDM switching fabric to minimize delay and maximize voice quality (unlike other technologies that use a packet technology that introduces delay). The TMG7800-TMS can switch a call terminating on any TMG7800 gateway unit to any other TMG7800 gateway unit of the cluster. This is particularly useful when the TMG7800 system needs to provide TDM switching services. The TMG7800-TMS also supports redundancy.

#### Characteristics

* 3 to 22U VoIP gateway per cluster
* 256 to 32,768 VoIP channels per cluster
* 16 to 1024 T1/E1 or 1 to 48 DS3 or 1 to 16 OC3/STM1 per cluster
* Up to 4 clusters within a single system
* Redundant AC or DC power supplies

#### Available configurations

* TMG7800-CTRL, (VoIP server)
* TMG7800-TE16, (16 x T1/E1, 512 x VoIP)
* TMG7800-TE32, (32 x T1/E1, 1024 x VoIP)
* TMG7800-TE48, (48 x T1/E1, 1536 x VoIP)
* TMG7800-TE64, (64 x T1/E1, 2048 x VoIP)
* TMG7800-DS31, (1 x DS3, 672 x VoIP)
* TMG7800-DS32, (2 x DS3, 1344 x VoIP)
* TMG7800-DS33, (3 x DS3, 2016 x VoIP)
* TMG7800-STM1, (1 x STM1, 2048 x VoIP)
* TMG7800-TMS, (media switching fabric)

Each configuration is available with redundant AC or DC power.

See [TMG7800 web site](https://telcobridges.com/media-gateways/products/tmedia-gateways/tmg7800/) to learn more about this product.

### References

* [TMG7800 Datasheet](/tmedia-documentation/operations-and-support/support/datasheets.md)
* [TMG7800 Installation Guide](/tmedia-documentation/products/tmedia/installation/product-installation.md#tmedia)
* [Regulatory compliance](/tmedia-documentation/operations-and-support/support/other/regulatory-compliance.md)


---

# 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://prosbcdocs.telcobridges.com/tmedia-documentation/products/tmedia/tmg7800.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.
