An application can receive status indications through asynchronous notification or polling. A status indication is sent to all applications when the corresponding network status changes. The following table describes the status indications:
Status indication |
Description |
StatPaused |
Delivery to the specified destination point code is not currently possible. This can mean that there is no route configured for the destination point code or that all routes to that point code are currently unavailable. |
StatResumed |
Occurs initially or after a StatPaused indication when one or more routes to a particular destination point code become available. |
StatCongested |
Delivery to the destination SP failed due to network congestion at some point along the route. The user part or application must reduce traffic to that destination. |
StatCongestionEnds |
Occurs after a StatCongested indication when network congestion has abated. |
StatUsrUnavail |
Message was delivered to the remote M3UA layer, but no application was registered to receive data with the service information octet (SIO) contained in the message. For example, data was sent with an SIO indicating an ISUP message, but there was no ISUP application running at the destination. The remote M3UA layer discards the message. |
StatPrimary |
Local M3UA is the primary node in a redundant configuration. |
StatBackup |
Local M3UA is the backup node in a redundant configuration. |
StatStandAlone |
M3UA is not in a redundant configuration. |