MTP3:Route Alarms
From TBwiki
The alarm (event) notification message is received by the host application when a MTP3 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
