Actions

SCCP:Error Performance Report: Difference between revisions

(initial content)
 
(fixed error)
 
(2 intermediate revisions by the same user not shown)
Line 1: Line 1:
The performance report error (event) notification message is received by the host application when a SCCP is reporting a performance error.
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:
General explanation of the error event notification fields in the performance report:
*The '''SCCP handle field''' specifies the handle of the SCCP instance.
*The '''SCCP handle field''' specifies the handle of the SCCP instance.


Line 12: Line 12:


{| class="wikitable" border="1"
{| class="wikitable" border="1"
|+ SCCP event and cause LSAP alarm under CATEGORY_PROTOCOL
|+ '''SCCP event and cause LSAP alarm under CATEGORY_PROTOCOL'''
! width="150" style="background:#efefef;" |Cause
! width="150" style="background:#efefef;" |Cause
! width="200" style="background:#efefef;" |Report parameters used
! width="200" style="background:#efefef;" |Report parameters used
! width="200" style="background:#efefef;" |Description
! width="200" style="background:#efefef;" |Description
|-
|-
| Protocol bind-fail|| Unknown||Bind with service provider failed
| Unknown || None|| Unknown
|-
|-
| Protocol bind-fail|| Unknown||Bind with service provider failed
| No Translation - bad address (RTF_NTBADADDR)||
*un32NetworkId
*ProtocolVariant
*Called Address
*Calling Address
||Routing failure - No translation for address of such nature
|-
|-
| Protocol bind-fail|| Unknown||Bind with service provider failed
| No translation - specific address (RTF_NTSPECADDR)||
*un32NetworkId
*Protocol Variant
*Called Address
*Calling Address
||Routing failure - No translation for this specific address
|-
|-
| Protocol bind-fail|| Unknown||Bind with service provider failed
| Network failure (RTF_NETWORK_FAIL)||
*un32NetworkId
*ProtocolVariant
*Calling Address
||Routing failure - Network failure (point code not available)
|-
|-
| Protocol bind-fail|| Unknown||Bind with service provider failed
| 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
|}
|}
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.




Line 178: Line 101:
General explanation of the Report-specific information parameters:
General explanation of the Report-specific information parameters:


*The network identifier parameter (un32NetworkId) specifies the ID of the network.
*The '''Network identifier''' parameter specifies the ID of the network
 
*The '''Called address''' parameter specifies the called party address. See the Entity explanation in [[SCCP:GTT Address Map Configuration|GTT Address Map Configuration]]
-          The called address parameter (CalledAddress) specifies the called party address. See Entity explanation in section 7.2.1.7 08D0C9EA79F9BACE118C8200AA004BA90B02000000080000000E0000005F005200650066003100320035003500320030003100310033000000  GTT Address Map Configuration 08D0C9EA79F9BACE118C8200AA004BA90B02000000080000000E0000005F005200650066003100320035003500320030003100310033000000 .
*The '''Calling address''' parameter specifies the calling party address. See the Entity explanation in [[SCCP:GTT Address Map Configuration|GTT Address Map Configuration]]
 
*The '''Destination point code''' parameter ([[DPC]]) specifies the point code of the node where the route is terminating
-          The calling address parameter (CallingAddress) specifies the calling party address. See Entity explanation in section 7.2.1.7 08D0C9EA79F9BACE118C8200AA004BA90B02000000080000000E0000005F005200650066003100320035003500320030003100310033000000  GTT Address Map Configuration 08D0C9EA79F9BACE118C8200AA004BA90B02000000080000000E0000005F005200650066003100320035003500320030003100310033000000 .
*The '''Protocol variant''' parameter specifies the SCCP protocol variant. See the SCCP protocol variant table in [[Toolpack:Create a SCCP 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 destination point code parameter (Dpc) specifies the point code of the node where the route is terminating.
*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.
-          The protocol variant parameter (ProtocolVariant) specifies the SCCP protocol variant. See Table 73 - SCCP protocol variant 08D0C9EA79F9BACE118C8200AA004BA90B02000000080000000E0000005F005200650066003100320034003200310034003700330039000000 .
 
-          The subsystem number parameter (un32SSN) specifies a subsystem number. See Table 79 - SCCP SSN value to identify SCCP user 08D0C9EA79F9BACE118C8200AA004BA90B02000000080000000E0000005F005200650066003100320034003200340032003200330036000000 .
 
-          The segmentation reference parameter (un32SegmentationRef) specifies the SCCP segmentation local reference number.
 
-          The congestion level parameter (un32CongestionLvl) specifies the remote SCCP congestion level (reception of SSC). Value is in range 0 to 7.

Latest revision as of 13:52, 8 September 2009

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
  • 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 SCCP 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.
Retrieved from "https://docs.telcobridges.com/w/index.php?title=SCCP:Error_Performance_Report&oldid=2623"