> 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/solutions/tandem-switching.md). # Tandem switching Tandem switching consists of non-customer-facing switches that are configured to route traffic amongst themselves or to other switches for such purposes as capitalizing on cheap international long-distance, etc. ### TelcoBridges and Tandem switching TelcoBridges' [Tmedia](/products/tmedia/tmedia.md) and Tdev devices can act as Class 4 switches, providing tandem switching among Class 5 devices at the local level. They offer a very cost-effective approach to building out footprint, consolidating call volumes. Tdev and Tmedia devices are distinguished by high levels of customizability and faster turnaround on adding new features. The included Toolpack development software also allows operators to write and implement critical features that are unique to their business. Tdev and Tmedia devices also provide much flexibility, enabling operators to mix and match interface and signaling protocols, including [SS7](https://tmediadocs.telcobridges.com/telecom-references/ss7-and-signalling/ss7), [ISDN](https://tmediadocs.telcobridges.com/telecom-references/ss7-and-signalling/isdn), [CAS R2](https://tmediadocs.telcobridges.com/telecom-references/ss7-and-signalling/cas), [SIP](https://tmediadocs.telcobridges.com/telecom-references/sip-and-voip/sip), and [SIGTRAN](https://tmediadocs.telcobridges.com/telecom-references/ss7-and-signalling/sigtran) in the same box, with no need for additional dedicated hardware. Finally, they offer cost-conscious operators a platform that is recognized as a leader in energy efficiency and green operation. ### References * [Wikipedia article](http://en.wikipedia.org/wiki/Class_4_telephone_switch) --- # 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/solutions/tandem-switching.md?ask=&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.