SWA-#7 MTP
(A).....................
-------------------------------------------------------------------------
N7 MTP
N7 MSU DISCARD REPORT / N7 MEASUREMENTS FIRST AND INTERVAL REPORTING
INFO: (1)..... REPORT PERIOD: (2):(3) - (4):(5)
OWN IDENTIFICATION: (6)............. NW: (7)...
----------------#----------------#--------#---#-----#-----#-----
ADJACENT NW LINK SLC Q 752 EVENT NBR
DESTINATION SET MSU
----------------#----------------#--------#---#-----#-----#-----
---------------------------------#----------------#--------#---#-----
-----
ADJACENT DESTINATION NW LINK SLC EVENT
NBR
CLLI PC SET
MSU
----------------=----------------#----------------#--------#---#-----
-----
(20)............ (21) (22)............ (23).... (24) (25) (26)(27).
(28)............ (29)............ (30)............ (31).... (32) (33)
(35).
EVENT + MEANING
------+----------------------------------------------------
(37) (38)................................................
REPORT REFERENCE NUMBER = 6039
| Par. No. | Meaning | Remarks |
|---|---|---|
| (A) | Message type | |
| (1) | Header information | |
| NO INFO | no information available | |
| OVERFLOW | overflow | |
| OVERLOAD | overload, events lost | |
| (2) | Time stamp start period | in hours |
| (3) | Time stamp start period | in minutes |
| (4) | Time stamp stop period | in hours |
| (5) | Time stamp stop period | in minutes |
| (6) | Own identification | exchange name or split codex |
| (7) | Own network | |
| (20) | Adjacent Destination can be either: | - exchange name, in ASCII form
- splitted destination point code |
| (21) | Adjacent Destination can be either: | - exchange name, in ASCII form
- splitted destination point code |
| (22) | Adjacent destination network | |
| (23) | Linkset | |
| (24) | Signalling link code | |
| (25) | ITU-measurement counter impacted 5.10 5.5 5.9 |
Message discard due to distribution error Message discard due to routing error Message discard due to discrimination error(unknown SSF) |
| (26) | Reason for discard | |
| (27) | Nbr MSUs discarded | |
| (28) | Adjacent Destination can be either: | - exchange name, in ASCII form
- splitted destination point code |
| (29) | Adjacent Destination can be either: | - exchange name, in ASCII form
- splitted destination point code |
| (30) | Adjacent destination network | |
| (31) | Linkset | |
| (32) | Signalling link code | |
| (33) | Reason for discard | |
| (35) | Nbr MSUs discarded | |
| (37) | Reason for discard | |
| (38) | Reason event description |
| Key Parameter | Contents / Meaning | Action | ||
|---|---|---|---|---|
| 1 | 2 | 3 | ||
| (38) | INTERNAL BUFFERR OVERFLOW . . . . . . . . . . . . | A | ||
| (38) | INVALID LI . . . . . . . . . . . . . . . . . . . . | A | ||
| (38) | MSU ROUTED TO OOS LINK, ROUTING TABLE ERROR . . . | A | ||
| (38) | NO MTUP DESTINATION LCE FOUND . . . . . . . . . . | A | ||
| (38) | NO SCCP DESTINATION LCE FOUND . . . . . . . . . . | A | ||
| (38) | NO TAX DESTINATION LCE FOUND . . . . . . . . . . . | A | ||
| (38) | NO TUP OR ISUP DESTINATION LCE FOUND FOR THIS CIC | A | ||
| (38) | NOT ENOUGH RESOURCES . . . . . . . . . . . . . . . | A | ||
| (38) | OPC = OWN POINT CODE, MESSAGE IN LOOP . . . . . . | A | ||
| (38) | OUTGOING LINKSET = INCOMING LINKSET, MESSAGE IN LOOP | A | ||
| (38) | OWN EXCHANGE IS NOT STP FOR THIS SSF . . . . . . . | A | ||
| (38) | ROUTING TABLE ERROR DETECTED . . . . . . . . . . . | A | ||
| (38) | SNM SCREENING VIOLATION . . . . . . . . . . . . . | A | ||
| (38) | SSF NOT SUPPORTED BY INCOMING LINKSET . . . . . . | A | ||
| (38) | STP FOR MAINTENANCE MESSAGE(SI=1) . . . . . . . . | A | ||
| (38) | UNALLOCATED H1H0 FOR MANAGEMENT MESSAGE(SI=0) . . | A | ||
| (38) | UNAUTHORISED USE OF STP . . . . . . . . . . . . . | A | ||
| (38) | UNKNOWN DPC . . . . . . . . . . . . . . . . . . . | A | ||
| (38) | UNKNOWN MAINTENANCE MESSAGE(SI=1) . . . . . . . . | A | ||
| (38) | UNKNOWN OPC . . . . . . . . . . . . . . . . . . . | A | ||
| (38) | UNKNOWN SIO . . . . . . . . . . . . . . . . . . . | A | ||
| Action | Meaning |
|---|---|
| A | The given result data can be taken as information only or special fault clearing might be necessary. In the latter case, refer to the document FAULT REPORTING PROCEDURES which is part of the Customer Documentation Guide. |