> 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/unified-communications.md). # Unified communications Unified Communications (UC) is a catch-all term referring to the integration of various modes of communication, including real-time and non-real-time, within one or more applications that provide a consistent interface. According to Wikipedia, one of the aspects of UC is that it "allows an individual to send a message on one medium and receive on another." (see References below). ### TelcoBridges and Unified Communications TelcoBridges' Tmedia and Tdev devices support the development of UC applications. For example, a TelcoBridges partner has developed an application that routes SMS messages to the GoogleTalk chat service and back. ### References [Wikipedia article](http://en.wikipedia.org/wiki/Unified_communications) --- # 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/unified-communications.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.