> 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/protocols/proving-emergency.md). # Proving Emergency Before an MTP2 link can be considered as active, both sides of the connection needs to go through a handshake to ensure the ready state of each peer and to test the quality of the physical transport layer (e.g., the [timeslot](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/transmission/timeslot/README.md)(s)). This handshaking action involves different MSU exchanged between both MTP2 layers. Two different handshaking methods are available for an MTP2 link: normal and emergency. In both cases, the MTP2 link is considered activated if no errors are detected during the proving period. The "emergency" mode is used to test the link minimally and to bring it up as quickly as possible. Therefore, it has the smallest proving period timer. The typical value is 500 milliseconds (0.5 seconds) for ITU and 600 milliseconds (0.6 seconds) for ANSI. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://prosbcdocs.telcobridges.com/telecom-references/protocols/proving-emergency.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.