> 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/voice-and-media/umts.md).

# UMTS

Universal Mobile Telecommunications System (UMTS) refers to one of the standards used for 3G mobile phone networks. It is based in part on the work of the 3rd Generation Partnership Project (3GPP. It is closely related to the standards used in the development of GSM networks.

### TelcoBridges and UMTS

TelcoBridges supports UMTS networks through its [Tmedia](https://prosbcdocs.telcobridges.com/tmedia-documentation/products/tmedia/tmedia) media gateways and Tdev [value-added services](https://prosbcdocs.telcobridges.com/tmedia-documentation/products/tmedia/features-and-solutions/solutions/value-added-services) (VAS) development platforms. These support the [signaling protocols](/telecom-references/ss7-and-signalling/ss7/signaling-protocols.md) and [voice codecs](/telecom-references/voice-and-media/voice-codecs.md) that are used in the context of UMTS networks.

As of July 2009, the [Tmonitor](https://prosbcdocs.telcobridges.com/tmedia-documentation/products/tmonitor/tmonitor) series of devices for [network monitoring](https://prosbcdocs.telcobridges.com/tmedia-documentation/products/tmedia/features-and-solutions/features/network-monitoring), [lawful intercept](https://prosbcdocs.telcobridges.com/tmedia-documentation/configuration/web-portal-3-3/lawful-intercept) and [location-based services](https://prosbcdocs.telcobridges.com/tmedia-documentation/products/tmedia/features-and-solutions/solutions/location-based-services) does not currently support UMTS/3G networks. However, they do support 2G and 2.5G (also known as GPRS/EDGE) networks.

### References

* [Wikipedia article](http://en.wikipedia.org/wiki/Universal_Mobile_Telecommunications_System)


---

# 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/telecom-references/voice-and-media/umts.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.
