> 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/error-performance-report.md).

# Error Performance Report

The performance report error (event) notification message is received by the host application when a SCCP is reporting a performance error.

General explanation of the error event notification fields in the performance report:

* The **SCCP handle field** specifies the handle of the SCCP instance.

***

* The **Cause field** specifies the cause of the error performance report.

**SCCP event and cause LSAP alarm under CATEGORY\_PROTOCOL**

| Cause                                               | Report parameters used                                                  | Description                                                    |
| --------------------------------------------------- | ----------------------------------------------------------------------- | -------------------------------------------------------------- |
| Unknown                                             | None                                                                    | Unknown                                                        |
| No Translation - bad address (RTF\_NTBADADDR)       | \*un32NetworkId \*ProtocolVariant \*Called Address \*Calling Address    | \|Routing failure - No translation for address of such nature  |
| No translation - specific address (RTF\_NTSPECADDR) | \*un32NetworkId \*Protocol Variant \*Called Address \*Calling Address   | \|Routing failure - No translation for this specific address   |
| Network failure (RTF\_NETWORK\_FAIL)                | \*un32NetworkId \*ProtocolVariant \*Calling Address                     | \|Routing failure - Network failure (point code not available) |
| Network congestion (RTF\_NETWORK\_CONGESTION)       | \*un32NetworkId \*ProtocolVariant \*DPC \*Calling Address               | \| Routing failure - Network congestion                        |
| Subsystem failure (RTF\_SUBSYSTEM\_FAILURE)         | \*un32NetworkId \*ProtocolVariant                                       | \|Routing failure - Subsystem failure (unavailable)            |
| System congestion (RTF\_SUBSYSTEM\_CONGESTION)      | \*un32NetworkId \*ProtocolVariant \*Calling Address                     | \|Routing failure - Subsystem congestion                       |
| Routing failure - unequipped user (RTF\_UNEQUIPPED) | \*un32NetworkId \*ProtocolVariant                                       | \|Routing failure - Unequipped user (subsystem).               |
| Reassembly outside of sequence (REASSEMBLY\_OUTSEQ) | \*un32NetworkId \*ProtocolVariant \*Calling Address \*un32CongestionLvl | \|Reassembly error - Segment received out of sequence          |
| Hop violation (HOP\_VIOLATION)                      | \*un32NetworkId \*ProtocolVariant \*Called Address \*Calling Address    | \|Hop counter violation (XUDT(S) / LUDT(S))                    |
| Segment failure - too large (SEGFAIL\_TOO\_LARGE)   | \*un32NetworkId \*ProtocolVariant                                       | \|Message too large for segmentation                           |
| Subsystem congested received (SSC\_RECV)            | \*un32NetworkId \*ProtocolVariant \*DPC \*un32CongestionLvl             | \|SCCP / Subsystem congested message received.                 |
| Subsystem prohibited received (SSP\_RECV)           | \*un32NetworkId \*ProtocolVariant \*DPC \*un32SSN                       | \|Subsystem prohibited message received                        |

### Description of parameters

General explanation of the Report-specific information parameters:

* The **Network identifier** parameter specifies the ID of the network
* The **Called address** parameter specifies the called party address. See the Entity explanation in [GTT Address Map Configuration](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/gtt-address-map-configuration/README.md)
* The **Calling address** parameter specifies the calling party address. See the Entity explanation in [GTT Address Map Configuration](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/gtt-address-map-configuration/README.md)
* The **Destination point code** parameter ([DPC](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/signalling/dpc/README.md)) specifies the point code of the node where the route is terminating
* The **Protocol variant** parameter specifies the SCCP protocol variant. See the SCCP protocol variant table in [Toolpack:Create a SCCP network](https://github.com/telcobridges-main/tmedia-wiki/tree/main/tmedia/configuration/create-a-sccp-network/README.md)
* The **Subsystem number** parameter specifies a subsystem number. See the SCCP SSN value to identify SCCP user table in Toolpack:Create a SCCP route.
* The **Segmentation reference** parameter specifies the SCCP segmentation local reference number
* The **Congestion level** parameter specifies the remote SCCP congestion level (reception of SSC). Value is in range 0 to 7.


---

# 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/error-performance-report.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.