> 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/transmission-and-lines/tms-network-synchronization.md).

# TMS Network Synchronization

The "Synchronous TMS network" option available under "Clocking->Advanced Parameters" section allows modification of the clocking selection behavior. See following screen capture:

![Synchronous tms network](https://docs.telcobridges.com/w/images/2/21/Synchronous_tms_network.png)

* When the option is selected, the system will synchronize all units of a TMS Network on a single clock source base on clock references list.
* When the option is unselected, the system will synchronize each TMedia units individually with the TDM Network base on clock references list. The TMS will synchronize on a single clock source base on clock references list. The TMedia and TMS clock sources could be different then TMS will work in asynchronous mode. See following diagrams:

### Synchronous TMS network mode

![Synchronous tms network clock distribution](https://docs.telcobridges.com/w/images/0/04/Synchronous_tms_network_clock_distribution.png)

### Asynchronous TMS network mode

![Asynchronous tms network clock distribution](https://docs.telcobridges.com/w/images/0/09/Asynchronous_tms_network_clock_distribution.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 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/transmission-and-lines/tms-network-synchronization.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.