| CRN 03552 | DISPLAY-SCCP-STATUS |
| CRN 03551 | MODIFY-SCCP-STATUS |
SWA-SUBSEC SCCP
(A)....................... (B).................
(C)........................... (D) (E)
-----------------------------------------------------------------
SCCP ORJ AREA
OPERATOR INPUT :(1)
DEST (2) (3)..... (4)............. & (5).............
SSN1 : (6).............
FSSP1 (7)
SSN2 : (8).............
FSSP2 (9)
SSN3 : (10)............
FSSP3 (11)
SSN4 : (12)............
FSSP4 (13)
SSN5 : (14)............
FSSP5 (15)
STATCHG : (16)....
STATVIEW : (17)....
ES : (18)............
DPC (19) (20).... (21)............
LOGNET : (22)............
SCCPUSER : (23)............
CONTROL : (24).. & (25) & (26) & (27) & (28) &
----------------------------------------------------------------(29)
(30)
ES STATUS
-------------------------(31)
ES SPLIT PC LOGNET STATUS
-----------------------------------------------------------(32)
ES SSN STATUS
------------------------------------------(33)
(34)............ (35).......... (36)............
(37) (38)............ (39)....
UNAV1 = Put unavailable by operator
UNAV2 = Put unavailable by subsystem
UNAV3 = No CE of the subsystem available (40)
SPLIT PC LOGNET STATUS ALARMTYP
---------------------------------------------------(41)
SPLIT PC LOGNET SSN STATUS ALARMTYP
--------------------------------------------------------------------(42)
SSN STATUS ALARMTYP
----------------------------------(43)
(44) (45).......... (46)............ (47)............ (48).... (49)....
--------------------------------------------------------------------(50)
ERROR INFORMATION :(51)
(52)
(53)
REPORT REFERENCE NUMBER = 8516
| Par. No. | Meaning | Remarks |
|---|---|---|
| (A) | Command name | |
| (B) | Main execution result | |
| (C) | Result part type | |
| (D) | Result part number | |
| (E) | Continuation indicator | |
| (1) | Header for input parms or suppress | |
| (2) | Indication (:) or suppress possibility | |
| (3) | Destination point code | in hexadecimal form |
| (4) | Destination : exchange name or splitted point code | The splitted point code value (1
to 4 decimal digit strings separated by 1 space character) depends on the logical network field |
| (5) | Destination logical network field | |
| (6) | Sub-system number 1: sub-system mnemonic) | |
| ALL | all possibilities | |
| AUTHCENTRE | authentication centre | |
| BSSAP | base station sub-system
application part | |
| BSSOMAP | base station sub-system O&M part | |
| EIR | equipment identity register | |
| HLR | home location register | |
| INALSSF | ALCATEL service switching
function (IN) | |
| INERSCF | ERICSSON service control function
(IN) | |
| INERSSF | ERICSSON service switching
function (IN) | |
| ISUP | ISDN user part | |
| MAP | mobile application part | |
| MSC | mobile service centre | |
| MUP | mobile user part | |
| OMAP | operation and maintenance
administration part | |
| OMUP | operation and maintenance user
part | |
| Q3L4TO7 | Q3 level interface 4 to 7 (TMN) | |
| SCCPX25 | signalling connection control
part X25 link | |
| SCMG | signalling connection part
management | |
| SSNABS | absentee | |
| SSNIVPN | individual virtual private
numbering | |
| TAXAP | taxation application part | |
| UNCHG | unchanged | |
| UNKNOWN | unknown number | |
| USBS | user signalling bearer service | |
| VLR | visitor location register | |
| (7) | Forced sub-system prohibited 1 : text string indication or suppression | |
| FORCED SSP | if applicable | |
| (8) | Sub-system number 2: sub-system mnemonic)
see param (6) | |
| (9) | Forced sub-system prohibited 2 : text string indication or suppression | |
| FORCED SSP | if applicable | |
| (10) | Sub-system number 3: sub-system mnemonic)
see param (6) | |
| (11) | Forced sub-system prohibited 3 : text string indication or suppression | |
| FORCED SSP | if applicable | |
| (12) | Sub-system number 4: sub-system mnemonic)
see param (6) | |
| (13) | Forced sub-system prohibited 4 : text string indication or suppression | |
| FORCED SSP | if applicable | |
| (14) | Sub-system number 5: sub-system mnemonic)
see param (6) | |
| (15) | Forced sub-system prohibited 5 : text string indication or suppression | |
| FORCED SSP | if applicable | |
| (16) | Sub-system/Node status change indicator | |
| (17) | Entity Set/Entity/SCCP user/Node/sub-system status view parameter | |
| (18) | Entity Set mnemonic | |
| (19) | Indication (:) or suppress possibility | |
| (20) | Destination point code | in hexadecimal form |
| (21) | Destination : exchange name or splitted point code | The splitted point code value : 1
to 4 decimal digit strings separated by 1 space character, depends on the logical network field |
| (22) | Destination logical network field | |
| (23) | Sub-system mnemonic
see param (6) | |
| (24) | Control parameter | |
| (25) | Control parameter : scheduled month | |
| (26) | Control parameter : scheduled day | |
| (27) | Control parameter : scheduled hour | |
| (28) | Control parameter : scheduled minutes | |
| (29) | Separator or suppression value | |
| (30) | Header or suppression value | |
| (31) | Header or suppression value | |
| (32) | Header or suppression value | |
| (33) | Header or suppression value | |
| (34) | Entity Set mnemonic | |
| (35) | Destination : split point code | 1 to 4 decimal digit strings
separated by 1 space character, depends on the logical network field |
| (36) | Destination logical network mnemonic | |
| (37) | Sub-system mnemonic suppression | |
| (38) | Sub-system mnemonic
see param (6) | |
| (39) | Sub-system status | |
| (40) | Unavailable statuse types | |
| (41) | Header or suppression value | |
| (42) | Header or suppression value | |
| (43) | Header or suppression value | |
| (44) | Empty parameter | |
| (45) | Destination : split point code | 1 to 4 decimal digit strings
separated by 1 space character, depends on the logical network field |
| (46) | Destination logical network mnemonic | |
| (47) | Sub-system mnemonic
see param (6) | |
| (48) | Sub-system status | |
| (49) | Sub-system alarm type | |
| (50) | Separator or suppression value | |
| (51) | Error info header suppression field | |
| (52) | Comments on the execution result/error indication | |
| (53) | Error parameter indication |
| Key Parameter | Contents / Meaning | Action | ||
|---|---|---|---|---|
| 1 | 2 | 3 | ||
| (52) | COMMAND EXECUTION CANCELLED BY OPERATOR . . . . . | A | ||
| (52) | DESTINATION ALREADY EXISTS . . . . . . . . . . . . | B | ||
| (52) | DESTINATION DOES NOT EXIST . . . . . . . . . . . . | B | ||
| (52) | DESTINATION IS UNKNOWN . . . . . . . . . . . . . . | B | ||
| (52) | GIVEN SSTUSE IS THE SAME AS PREVIOUSLY DEFINED . . | B | ||
| (52) | NETWORK IS UNKNOWN . . . . . . . . . . . . . . . . | B | ||
| (52) | NO ENTITY DEFINED FOR LOCAL SUBSYSTEM . . . . . . | A | ||
| (52) | NO ENTITY DEFINED FOR REMOTE NODE . . . . . . . . | A | ||
| (52) | NO INFO FOUND . . . . . . . . . . . . . . . . . . | A | ||
| (52) | NO MANAGEABLE SUBSYSTEMS EXIST FOR THE SPECIFIED NODE | B | ||
| (52) | NO MANAGEMENT DEFINED FOR NODE . . . . . . . . . . | B | ||
| (52) | NO MANAGEMENT DEFINED FOR SUBSYSTEM . . . . . . . | B | ||
| (52) | NO SUBSYSTEM EXISTS . . . . . . . . . . . . . . . | B | ||
| (52) | NO SUBSYSTEM EXISTS WITH THE GIVEN STATUS . . . . | B | ||
| (52) | THE CURRENT SUBSYSTEM STATUS IS THE SAME AS REQUIRED | B | ||
| (52) | THE STATUS OF REMOTE NODE IS NOT UNEQUIPPED . . . | B | ||
| (52) | WRONG DESTINATION POINT CODE GIVEN . . . . . . . . | B | ||
| Action | Meaning |
|---|---|
| A | The error message is given in case of any consistency check failure. It contains the necessary information to allow the operator to identify the problem. Check input data ; If the input data is not correct, then enter the MMC-command again with adapted data. If applicable, see the additional error information related to the invalid input parameter. See also Restrictions part of the corresponding MMC-command. If the input data is correct, then the given result data can be taken as an information only and special fault clearing might be necessary. In that case, see fault reporting procedures. |
| B | The result data is given as an error message, when an inconsistent data is detected during the check of the operation, which is specified by the specific input parameters, whether is valid and in conflict with the existing data. Check the involved input parameter, correct and enter the MMC-command again. |