> 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/tcap-alarms.md).

# TCAP Alarms

### Alarm

The alarm (event) notification message is received by the [TCAP](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/tcap/README.md) service user when TCAP is reporting an error.

General explanation of the fields of previous structure:

* The **TCAP handle field** specifies the handle of the TCAP instance

***

* The **Category field** indicates the category of the alarm. Possible values:

| Alarm category | Description                            |
| -------------- | -------------------------------------- |
| None           | No category                            |
| Protocol       | Protocol related alarms                |
| Interface      | Interface related alarms               |
| Internal       | Internal software error related alarms |
| Resources      | System resources related alarms        |

***

* The **Event field** specifies the event that caused the alarm.

| Alarm Event               | Description                       |
| ------------------------- | --------------------------------- |
| None                      | No event                          |
| Invalid UI event          | Invalid upper interface event     |
| Invalid LI event          | Invalid lower interface event     |
| Invalid event             | Invalid network message           |
| Invalid timer event       | Invalid timer expiration event    |
| Invalid MI event          | Invalid layer manager event       |
| Bind failure              | Bind with service provider failed |
| Message allocation failed | Message allocation failed         |
| Duplicate invoke ID       | Duplicate invoke ID               |
| Mandatory missing         | Mandatory element is missing      |
| Unexpected RX message     | Received unexpected message       |
| Unknown RX message        | Received unknown message          |
| Invalid dialog ID         | Invalid dialog ID                 |
| Unrecognized invoke ID    | Unrecognized invoke ID            |
| Allocation dialog failure | Dialog allocation failed          |
| Hash failure              | Hash table operation failed       |
| Max configuration         | Reached configuration limit       |
| Invalid component         | Invalid component                 |

***

* The **Cause field** specifies the cause of the alarm.

| Alarm Cause                  | Description                             |
| ---------------------------- | --------------------------------------- |
| Unknown                      | No cause                                |
| Invalid SAP                  | Invalid SAP                             |
| Invalid SP                   | Invalid service provider (out-of-range) |
| Invalid SU                   | Invalid service user (out-of-range)     |
| Protocol not active          | Protocol layer is not active            |
| Interface version            | Invalid interface version               |
| Unbound                      | SAP unbound                             |
| Dialog allocation failed     | Dialog allocation failed                |
| Invoke allocation failed     | Invoke allocation failed                |
| User-part association failed | User-part association failed            |
| SP SAP association failure   | Interface association failed            |
| Decoding failure             | Message decoding problem                |

### Userpart Alarm

An alarm (event) notification message is received by the TCAP service user when a TCAP userpart is reporting an error.

* The **TCAP handle** field specifies the handle of the TCAP instance.
* The **TCAP Userpart handle** field specifies the handle of the TCAP Userpart instance.
* The **Category** field indicates the category of the Userpart alarm. Possible values: see the 'TCAP alarm category' table in [TCAP Alarms](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/tcap-alarms/README.md).
* The **Event** field specifies the event that cause the Userpart alarm. Possible values: see the 'TCAP alarm event' table in [TCAP Alarms](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/tcap-alarms/README.md).
* The **Cause** field specifies the cause of the Userpart alarm. Possible values: see the 'TCAP alarm cause' table in [TCAP Alarms](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/tcap-alarms/README.md).


---

# 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/tcap-alarms.md?ask=<question>&goal=<endgoal>
```

`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.