RRN 06653 HANDLE SIGNALLING CONNECTION CONTROL PART ENTITY

JYL4D915

Message Triggering Condition

Response in case of successful/unsuccessful execution on operator request of one of the following commands:
CRN 03303 CREATE-SCCP-ENTITY
CRN 03304 MODIFY-SCCP-ENTITY
CRN 03305 REMOVE-SCCP-ENTITY
CRN 03306 DISPLAY-SCCP-ENTITY

Report Layout

 SWA-ORJ-SCCP ORJ
    (A).......................                   (B).................
                                 (C)........................... (D) (E)
    -----------------------------------------------------------------
        (1)
        ES       :  (2).............
        NEWES    :  (3).............
        PATED       (4)
        LDSHACT  :  (5)...
        METHOD   :  (6).....
        MANDISTR :  (7).............
        RTGIND   :  (8).... & (9).... & (10)... & (11)...
        PRIO     :  (12) & (13) & (14) & (15)
        VALSSN   :  (16). & (17). & (18). & (19).
        DUPLIND  :  (20). & (21). & (22). & (23).
        MATEIND  :  (24). & (25). & (26). & (27).
        ACCESS   :  (28).... & (29).... & (30).... & (31)....
        CONSECT  :  (32). & (33). & (34). & (35).
        SSNMAP   :  (36)............ & (37)............
                    (38)............ & (39)............
        DGTPENT  :  (40)............ & (41)............
                    (42)............ & (43)............
        REMNODE     (44)
        LOGNET           DPC
        =================================(45)
        (46)............ (47).... (48)............
        (49)......  (50).... & (51)....
        OTHERLN  :  (52)............
        OTHERDPC :(53) (54).... (55)............
        VERSION  :  (56).... & (57).... & (58).... & (59)....
        SEGMSG   :  (60).... & (61).... & (62).... & (63)....
        CREDIT   :  (64) & (65) & (66) & (67)
        HOPCNT   :  (68) & (69) & (70) & (71)
        ARTGCONG :  (72). & (73). & (74). & (75).
        OPCCHECK :  (76). & (77). & (78). & (79).
        DGTPNOD  :  (80)............ & (81)............
                    (82)............ & (83)............
        SCCPUSER :  (84)............
                    (85)............
                    (86)............
                    (87)............
        OTHERUSR :  (88)............
        PROTOCOL :  (89)
        DETAIL   :  (90)
        CONTROL  :  (91).. & (92) & (93) & (94) & (95)
        ------------------------------------------------------------
        ERROR INFORMATION :(96)
        (97) (98)
          (99)............
          (100)...........
          (101)...........
          (102)...........
          (103)...........
          (104)...........
          (105)...........
          (106)...........
         (107)
  REPORT REFERENCE NUMBER = 6653

Parameter Identification

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 header for input parameters
(2) ES mnemonic Entity set mnemonic
(3) New ES mnemonic New Entity set mnemonic
(4) PATED indication PATED indication
(5) LDSHACT loadsharing action
CREDEF CREDEF
REMOVE REMOVE
(6) Loadsharing METHOD loadsharing method
ENRICHED enriched loadsharing
NORM normal loadsharing
(7) Loadsharing MANDISTR loadsharing manual distribution
(8) Routing indicator 1 routing indicator 1
RTGGLBT routing on global title
RTGPC routing on pointcode
(9) Routing indicator 2 routing indicator 2
RTGGLBT routing on global title
RTGPC routing on pointcode
(10) Routing indicator 3 routing indicator 3
RTGGLBT routing on global title
RTGPC routing on point code
(11) Routing indicator 4 routing indicator 4
RTGGLBT routing on global title
RTGPC routing on pointcode
(12) Prioriry 1 priority 1
(13) Prioriry 2 priority 2
(14) Prioriry 3 priority 3
(15) Prioriry 4 priority 4
(16) Validate SSN 1 validate subsystem number 1
(17) Validate SSN 2 validate subsystem number 2
(18) Validate SSN 3 validate subsystem number 3
(19) Validate SSN 4 validate subsystem number 4
(20) Duplicates indicator 1 duplicates indicator 1
(21) Duplicates indicator 2 duplicates indicator 2
(22) Duplicates indicator 3 duplicates indicator 3
(23) Duplicates indicator 4 duplicates indicator 4
(24) Mates indicator 1 mates indicator 1
(25) Mates indicator 2 mates indicaotr 2
(26) Mates indicator 3 mates indicator 3
(27) Mates indicator 4 mates indicator 4
(28) Access type 1 access type 1
ETEFCTRL end to end flow control
LBLFCTRL link to link flowcontrol
(29) Access type 2 access type 2
ETEFCTRL end to end flow control
LBLFCTRL link to link flow control
(30) Access type 3 access type 3
ETEFCTRL end to end flow control
LBLFCTRL link to link flow control
(31) Access type 4 access type 4
ETEFCTRL end to end flow control
LBLFCTRL link to link flow control
(32) Connection section 1 connection section 1
(33) Connection section 2 connection section 2
(34) Connection section 3 connection section 3
(35) Connection section 4 connection section 4
(36) SSNMAP link 1 subsystem number map link 1
translated via relation R_SSNMAP
(37) SSNMAP link 2 subsystem number map link 2
translated vis relation R_SSNMAP
(38) SSNMAP link 3 subsystem number map link 3
translated via relation R_SSNMAP
(39) SSNMAP link 4 subsystem number map link 4
translated via relation R_SSNMAP
(40) Link ENT1-Digit Prep. link to digit preparation
translated via relation
R_DST_MNEM
(41) Link ENT2-Digit Prep. link to digit preparation
translated via relation
R_DST_MNEM
(42) Link ENT3-Digit Prep. link to digit preparation
translated via relation
R_DST_MNEM
(43) Link ENT4-Digit Prep. link to digit preparation
translated via relation
R_DST_MNEM
(44) Remove Node remove node indication
(45) DPC suppression destination pointcode suppression
(46) LOGical NETwork logical network translated via
relation R_N7LNMNEM
(47) Hex form of PC hexadecimal form of pointcode
(48) MNEMONIC for DPC Exchange name in ASCII form or
destination point code in
splitted form. Note: Splitted
point code value (1 up to 4
decimal digit strings separated
by 1 space character) depends on
the network/sub-service field: .
if point code is international
(SSF = 0 - 7) then it has the
following 14 bit structure: - bit
0->2:world geographical zone
identification (0-7), - bit
3->10:area identification within
world geographical zone(0-255), -
bit 11->14:signalling point
identification within
geographical area (0-7), . if
point code is national (SSF = 8 -
15), then 14 bit structure
depends on the national
administration requirements.
(49) Node capability type
LUDTCAP :
UDTCAP :
XUDTCAP :
node capability type long unitdata message capability unit data message capability extended unitdata message
capability
(50) Message hndl capabilility message handle capability
ALLOW allow capability
PROHIBIT message prohibited
REQ request capability
(51) Message return capability message return capability
NORETCAP no message return capability
RETCAP message return capability
(52) Other Lognet other logical network translated
via relation R_N7LNMNEM
(53) Other DPC suppression other destination pointcode
suppression
(54) Hex form of other DPC hexadecimal form of other
destination poiint code
(55) MNEMONIC for other DPC mnemonic for other destination
point code
(56) Version 1 version 1
ANSI88 SCCP ANSI88
ANSI92 SCCP ANSI92
ANSI96 SCCP ANSI96
BLUEBOOK SCCP BLUEBOOK
REDBOOK SCCP REDBOOK
WHITE93 SCCP WHITE93
WHITE96 SCCP WHITE96
(57) Version 2 version 2
ANSI88 SCCP ANSI88
ANSI92 SCCP ANSI92
ANSI96 SCCP ANSI96
BLUEBOOK SCCP BLUEBOOK
REDBOOK SCCP REDBOOK
WHITE93 SCCP WHITE93
WHITE96 SCCP WHITE96
(58) Version 3 version 3
ANSI88 SCCP ANSI88
ANSI92 SCCP ANSI92
ANSI96 SCCP ANSI96
BLUEBOOK SCCP BLUEBOOK
REDBOOK SCCP REDBOOK
WHITE93 SCCP WHITE93
WHITE96 SCCP WHITE96
(59) Version 4 version 4
ANSI88 SCCP WHITE96
ANSI92 SCCP ANSI92
ANSI96 SCCP ANSI96
BLUEBOOK SCCP BLUEBOOK
REDBOOK SCCP REDBOOK
WHITE93 SCCP WHITE93
WHITE96 SCCP WHITE96
(60) Segment. allowance 1 segmentation allowance 1
(61) Segment. allowance 2 segmentation allowance 2
(62) Segment. allowance 3 segmentation allowance 3
(63) Segment. allowance 4 segmentation allownace 4
(64) Credit 1 credit 1
(65) Credit 2 credit 2
(66) Credit 3 credit 3
(67) Credit 4 credit 4
(68) Hop counter 1 hop counter 1
(69) Hop counter 2 hop counter 2
(70) Hop counter 3 hop counter 3
(71) Hop counter 4 hop counter 4
(72) Alt. rout. on cong. 1 alternate routing on congestion 1
(73) Alt. rout. on cong. 2 alternate routing on congestion 2
(74) Alt. rout. on cong. 3 alternate routing on congestion 3
(75) Alt. rout. on cong. 4 alternate routing on congestion 4
(76) OPC check 1 own point code check 1
(77) OPC check 2 own point code check 2
(78) OPC check 3 own point code check 3
(79) OPC check 4 own point code check 4
(80) Link Node1-Digit prep. link to digit preparation 1
translated via relation
R_DST_MNEM
(81) Link Node2-Digit prep. link to digit preparation 2
translated via relation
R_DST_MNEM
(82) Link Node3-Digit prep. link to digit preparation 3
translated via relation
R_DST_MNEM
(83) Link Node4-Digit prep. link to digit preparation 4
translated via relation
R_DST_MNEM
(84) SCCPUSER 1, SSN subsystem number of SCCPUSER 1
see SI190
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
(85) SCCPUSER 2, SSN
see param (84)
subsystem number of SCCPUSER 2
see SI190
(86) SCCPUSER 3, SSN
see param (84)
subsystem number of SCCPUSER 3
see SI190
(87) SCCPUSER 4, SSN
see param (84)
subsystem number of SCCPUSER 4
see SI190
(88) Other SCCPUSER, SSN
see param (84)
subsystem number of other
SCCPUSER see SI190
(89) Protocol protocol
(90) Detail report detail
(91) Input control type input control type
(92) Scheduled month scheduled month
(93) Scheduled day scheduled day
(94) Scheduled hour scheduled hour
(95) Scheduled minutes scheduled minutes
(96) Error header error header
(97) Error message error message
(98) Hex form of PC hexadecimal form of pointcode
(99) High Layer User1 id. high layer user1 identity
translated via relation
R_SUCH_MNE
(100) High Layer User2 id. high layer user2 identity
translated via relation
R_SUCH_MNE
(101) High Layer User3 id. high layer user3 identity
translated via relation
R_SUCH_MNE
(102) High Layer User4 id. high layer user4 identity
translated via relation
R_SUCH_MNE
(103) High Layer User5 id. high layer user5 identity
translated via relation
R_SUCH_MNE
(104) High Layer User6 id. high layer user6 identity
translated via relation
R_SUCH_MNE
(105) High Layer User7 id. high layer user7 identity
translated via relation
R_SUCH_MNE
(106) High Layer User8 id. high layer user8 identity
translated via relation
R_SUCH_MNE
(107) Error item indication error item indication

Evaluation

Key Parameter Contents / Meaning Action
1 2 3
(97) ENTITY DOES NOT EXIST . . . . . . . . . . . . . . A01
(97) ENTITY SET IS IN USE BY GLOBAL TITLE . . . . . . . A01
(97) ENTITY SET IS IN USE BY TRANSLATION TYPE . . . . . A01
(97) ENTITY TO THE SPECIFIED NODE/USER ALREADY EXISTS . A01
(97) IT IS NOT ALLOWED TO CHANGE PATED INDICATION . . . A01
(97) IT IS NOT ALLOWED TO HAVE ALL MESSAGE TYPES PROHIBITED A01
(97) MANDISTR DOES NOT CORRESPOND TO NUMBER OF ENTITIES A01
(97) MANDISTR DOES NOT CORRESPOND TO NUMBER OF ENTITIES. A DEFAULT DISTRIBUTION WILL BE CREATED A01
(97) MNEMONIC GIVEN FOR ES DOES NOT EXIST . . . . . . . A01
(97) MNEMONIC GIVEN FOR NEWES ALREADY EXISTS . . . . . A01
(97) MNEMONIC GIVEN FOR SSNMAP DOES NOT EXIST . . . . . A01
(97) MORE THAN ONE ENTITY TO THE SAME NODE/USER SPECIFIED A01
(97) NETWORK IS UNKNOWN . . . . . . . . . . . . . . . . A01
(97) NO LOADSHARING EXISTS . . . . . . . . . . . . . . A01
(97) NO OTHERUSR EXISTS . . . . . . . . . . . . . . . . A02
(97) NO SCCPUSER EXISTS . . . . . . . . . . . . . . . . A02
(97) NO VERSION EXISTS FOR CURRENT PROTOCOL . . . . . . A01
(97) NODE ALREADY EXISTS . . . . . . . . . . . . . . . A01
(97) NODE ATTRIBUTES CAN NOT BE CHANGED USING THIS COMMAND A01
(97) NODE DOES NOT EXIST . . . . . . . . . . . . . . . A01
(97) NODE IS IN USE BY ENTITY . . . . . . . . . . . . . A02
(97) NODE IS IN USE BY FOLLOWING HIGH LAYER USERS : . . A01
(97) NODE IS IN USE BY MANAGEMENT . . . . . . . . . . . A01
(97) NOT ALLOWED MNEMONIC GIVEN FOR ES . . . . . . . . A01
(97) NOT ALLOWED MNEMONIC GIVEN FOR SSNMAP . . . . . . A01
(97) NUMBER OF ENTITIES DOES NOT ALLOW LOADSHARING LOADSHARING REQUEST IGNORED A01
(97) NUMBER OF ENTITIES EXCEEDS ALLOWED MAXIMUM . . . . A01
(97) OTHER NODE DOES NOT EXIST . . . . . . . . . . . . A01
(97) OWN POINT CODE CAN NOT BE USED TO DEFINE A NON-TERMINATING DESTINATION A01
(97) THE DESTINATION WITH THIS DPC IS UNKNOWN : . . . . A01
(97) THERE ARE NO ENTITIES WITH THE SAME PRIORITY ANYMORE : THE EXISTING LOADSHARING WILL BE REMOVED A01
(97) TWO GROUPS OF ENTITIES WITH THE SAME PRIORITY IN EACH ONE OF THEM ARE NOT ALLOWED FOR ITU A01
(97) WHEN ONE MESSAGE TYPE IS REQUIRED, OTHERS SHOULD BE PROHIBITED A01
(97) WRONG DESTINATION POINT CODE GIVEN . . . . . . . . A01
(107) ERROR INFORMATION CORRESPONDS TO THE ENTITY NUMBER FOUR A01
(107) ERROR INFORMATION CORRESPONDS TO THE ENTITY NUMBER ONE A01
(107) ERROR INFORMATION CORRESPONDS TO THE ENTITY NUMBER THREE A01
(107) ERROR INFORMATION CORRESPONDS TO THE ENTITY NUMBER TWO A01
(107) ERROR INFORMATION CORRESPONDS TO THE NODE NUMBER FOUR A02
(107) ERROR INFORMATION CORRESPONDS TO THE NODE NUMBER ONE A02
(107) ERROR INFORMATION CORRESPONDS TO THE NODE NUMBER THREE A02
(107) ERROR INFORMATION CORRESPONDS TO THE NODE NUMBER TWO A02

Action Description

Action Meaning
A01 Check input data. If the input is correct, then the given data can be considered as information only or special fault clearing may be necessary. If the input data is incorrect, correct your input and repeat the MMC-command.
A02 Inconsistencies in the system require special fault clearing. Refer to the document FAULT REPORTING PROCEDURES which is part Customer Documentation Guide.