> 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/ss7-and-signalling/mtp3/route-alarms.md). # Route Alarms The alarm (event) notification message is received by the host application when a [MTP3](/telecom-references/ss7-and-signalling/mtp3.md) route is reporting an error. General explanation of the field of event notification route alarm: * The **Route handle** field specifies the handle of the MTP3 route instance *** * The **Alarm** field indicates an alarm that can be reported at the route level. The following values are allowed: | Route Alarm | Description | | ------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | DPC pause | Reported when a concerned point code becomes inaccessible. | | DPC resume | Reported when a concerned point code becomes accessible. | | DPC network congested | Reported when a concerned point code becomes congested at level priority. The congestion can be at the local link due to congestion used to transport data towards the destination or due to congestion at intermediate nodes in the network. | | DPC network congestion stopped | Reported when a concerned point code is out of congestion. | | Restart begin | Reported by MTP3 to its users when our point code is restarting. | | Restart end | Reported by MTP3 to its users when our point code finishes the restarting procedure. | | Drop message | Concerned DPC drop message (SP routing). | | Remote user unavailable | Concerned DPC remote user unavailable. | | Restricted | Concerned DPC restricted. | *** * The **Cause** field specifies the alarm supplemental value according to alarm type --- # 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/ss7-and-signalling/mtp3/route-alarms.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.