SCCP:Error Performance Report

From TBwiki
Revision as of 10:13, 8 September 2009 by Ktrueman (Talk | contribs)
Jump to: navigation, search

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 field of event notification error 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
Protocol bind-fail Unknown Bind with service provider failed
Protocol bind-fail Unknown Bind with service provider failed
Protocol bind-fail Unknown Bind with service provider failed
Protocol bind-fail Unknown Bind with service provider failed
Protocol bind-fail Unknown Bind with service provider failed

Table SEQ Table \* ARABIC 96 - SCCP cause under error performance report

Cause

TB640_SS7_SCCP_REPORT_ERR_PERF_CAUSE_...

Used Report parameters

Description

UNKNOW

None

Unknown.

RTF_NTBADADDR

- un32NetworkId

- ProtocolVariant

- Called Address

- Calling Address

Routing failure - No translation for address of such nature.

RTF_NTSPECADDR

- un32NetworkId

- ProtocolVariant

- Called Address

- Calling Address

Routing failure - No translation for this specific address.

RTF_NETWORK_FAIL

- un32NetworkId

- ProtocolVariant

- Calling Address

Routing failure - Network failure (point code not available).

RTF_NETWORK_CONGESTION

- un32NetworkId

- ProtocolVariant

- Dpc

- Calling Address

Routing failure - Network congestion.

RTF_SUBSYSTEM_FAILURE

- un32NetworkId

- ProtocolVariant

Routing failure - Subsystem failure (unavailable).

RTF_SUBSYSTEM_CONGESTION

- un32NetworkId

- ProtocolVariant

- Calling Address

Routing failure - Subsystem congestion.

RTF_UNEQUIPPED

- un32NetworkId

- ProtocolVariant

Routing failure - Unequipped user (subsystem).

REASSEMBLY_OUTSEQ

- un32NetworkId

- ProtocolVariant

- Calling Address

- un32CongestionLvl

Reassembly error - Segment received out of sequence.

HOP_VIOLATION

- un32NetworkId

- ProtocolVariant

- Called Address

- Calling Address

Hop counter violation ( XUDT(S) / LUDT(S) ).

SEGFAIL_TOO_LARGE

- un32NetworkId

- ProtocolVariant

Message too large for segmentation.

SSC_RECV

- un32NetworkId

- ProtocolVariant

- Dpc

- un32CongestionLvl

SCCP / Subsystem congested message 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
  • The Calling address parameter specifies the calling party address. See the Entity explanation in GTT Address Map Configuration
  • The Destination point code parameter (DPC) 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 SSCP network
  • 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.
Personal tools