RRN 06661 HANDLE SIGNALLING CONNECTION CONTROL PART NODE

JYMED916

Message Triggering Condition

Response in case of successful execution on operator request of one of the following commands:
CRN 03307 CREATE-SCCP-NODE
CRN 03298 MODIFY-SCCP-NODE
CRN 03308 REMOVE-SCCP-NODE
CRN 03309 DISPLAY-SCCP-NODE

Report Layout

 SWA-ORJ-SCCP ORJ
    (A).......................                   (B).................
                                 (C)........................... (D) (E)
    -----------------------------------------------------------------
        (1)
        LOGNET     : (2).............
        DPC        : (3).....
        DPC        : (4).............
        UDTCAP     : (5)..... & (6).....
        XUDTCAP    : (7)..... & (8).....
        LUDTCAP    : (9)..... & (10)....
        SEGMSG     : (11)....
        CREDIT     : (12)
        HOPCNT     : (13)
        ARTGCONG   : (14).
        OPCCHECK   : (15).
        DGTPNOD    : (16)............
        HIGHUSER   : (17)............
        VERSION    : (18)....
        PROTOCOL   : (19)
        DETAIL     : (20)
        CONTROL    : (21).. & (22) & (23) & (24) & (25)
        (26)
        NODE IDENTITY :(27)
          LOGNET           DPC                       EXCHNAME         VERSION
          ====================================================================
(previous line continue on next line)
        (28)
          (29)............ (30).... / (31).......... (32)............ (33)....
        NODE INFORMATION :
          PROTOCOL   : (34)
          CREDIT     : (35)
          UDTCAP     : (36).... & (37)....
          XUDTCAP    : (38).... & (39)....
          LUDTCAP    : (40).... & (41)....
          SEGMSG     : (42).
          ARTGCONG   : (43)....
          OPCCHECK   : (44)....
          HOPCNT     : (45)
          MGMT       : (46).
          USEDBY     :(47)
                       (48)............
                       (49)............
                       (50)............
                       (51)............
                       (52)............
                       (53)............
                       (54)............
                       (55)............
          DGTPNOD    : (56)............
          DIGIT PREPARATION INFORMATION :(57)
            DGTPATYP :  (58)....
            TNBRPL   :  (59)....
            TNTRADDR :  (60)....
            TTRLTYP  :  (61)....
            TENCOD   :  (62)....
            TRTGIND  :  (63)....
            TGLBTIND :  (64)....
            TGTDGTS  :  (65).......................
            PREPTYP  :  (66)....
            APPLPNT  :  (67)....
            NBRDGTS  :  (68)....
            DIGITBUF :  (69).......................
            NNBRPL   :  (70)....
            NNTRADDR :  (71)....
            NRTGIND  :  (72)....
            NGLBTIND :  (73)....
            APPTRDIG :  (74)....
            NENCOD   :  (75)....
            NTRLTYP  :  (76)....
        -------------------------------------------------------------(77)
        -------------------------------------------------------------(78)
                                                      DGTP USED
        LOGNET           SPLIT PC       PROT VERSION  NOD   BY  CREDIT MGMT
        ===================================================================(79)
        (80)............ (81)............ (82) (83)....  (84)    (85) (86)(87)
        ERROR INFORMATION :(88)
        (89)
          (90)............
          (91)............
          (92)............
          (93)............
          (94)............
          (95)............
          (96)............
          (97)............
  REPORT REFERENCE NUMBER = 6661

Parameter Identification

Par. No. Meaning Remarks
(A) Command name
(B) Main execution result
(C) Result part type
FINAL RESULT The report is a final result.
Interim result or result parts
were sent before.
INTERIM RESULT The report is only an interim
result. A final result will
follow.
MEASUREMENT RESULT The report is a measurement
protocol.
RESPONSE TO COMMAND ACTIVATE Used in the area of traffic
measurement.
RESPONSE TO JOB EXECUTION Used in the area of traffic
measurement.
RESULT PART The result must be split into
different result parts. The
different result parts are
numbred from 1 onwards. The sign
(M_CH_SIGN) indicates if another
result part will be sent
(E_CH_PART), or if it is the last
part (E_CH_LAST).
TEST RESULT The report is a test result, e.g.
for line testing.
(D) Result part number
(E) Continuation indicator
(1) Header for input parms the header for input parameters
(2) LOGical NETwork the logical network to which the
node belongs translated via
relation R_N7LNMNEM
(3) NODE in HEX form destination point code of the
node in hexadecimal form
(4) SPLIT form/EXCHNAME 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.
(5) UDT message hndl capability whether the exchange can handle
UDT messages
ALLOW node has unit data allow
capability
PROHIBIT node prohibits unit data messages
REQ node has unit data request
capability
(6) UDT message return capability whether the exchange can return
UDT messages
NORETCAP node has no unit data return
capability
RETCAP node has unit data return
capability
(7) XUDT message hndl capability whether the exchange can handle
XUDT messages
ALLOW node has extended uit data allow
capability
PROHIBIT node prohibits extended unit data
messages
REQ node has extended unit data
request capability
(8) XUDT message hndl capability whether the exchange can return
XUDT messages
NORETCAP node has no extended unit data
return capability
RETCAP node has extended unit data
return capability
(9) LUDT message hndl capability whether the exchange can handle
LUDT messages
ALLOW node allows long unit data
messages
PROHIBIT node prohibits long unit data
messages
REQ node has long unit data request
capability
(10) LUDT message hndl capability whether the exchange can return
LUDT messages
NORETCAP node has no long unit data return
capability
RETCAP node has long unit data return
capability
(11) Message segmentation message segmentation indicator
FALSE segmentation of messages is not
allowed
TRUE segmentation of messages is
allowed
(12) Credit value maximum window exchange can
handle
(13) Hop counter
(14) Alternate rout. cong. alternate routing on congestion
indicator
FALSE alternate routing on congestion
is not present
TRUE alternate routing on congestion
is present
(15) Own Point Code check whether the exchange can change
its own point code
FALSE node cannot change its own point
code
TRUE node can change its own point
code
(16) Link to Digit Prep. link to digit preparation
translated via relation
R_DGTPMNEM
(17) ID of High Layer User higher layer user identity
translated via relation
R_SUCH_MNE
(18) SCCP NODE VERSION version of SCCP used
ALL all SCCP versions
ANSI88 SCCP version ANSI88
ANSI92 SCCP version ANSI92
ANSI96 SCCP version ANSI96
BLUEBOOK SCCP Bluebook
REDBOOK SCCP Redbook
WHITE93 SCCP White93
WHITE96 SCCP version White96
(19) Protocol (ITU/ANSI) whether ITU or ANSI protocol
protocol is used
ALL all protocols
ANSI protocol is ANSI
ITU protocol is ITU
(20) Report detailization
COMPRESS report type is compress
LONG report type is long
SHORT report type is short
(21) Input control type
CANCEL command cancelled
SCHED command scheduled
(22) Scheduled month
(23) Scheduled day
(24) Scheduled hour
(25) Scheduled minutes
(26) Action header
CREATED DATA :
NEW DATA :
created data is displayed new data is displayed
NO INFO FOUND
NODE INFORMATION :
OLD DATA :
REMOVED DATA :
no information is found node information is displayed old data is displayed removed data is displayed
(27) NODE identity header header for node information
(28) NODE identity suppress node identity header
(29) LOGical NETwork logical network to which node
belongs translated via relation
R_N7LNMNEM
(30) NODE in HEX form destination point code of node in
hexadecimal from
(31) SPLIT form splitted point code of node
(32) SCCP EXCHNAME exchange name of node
(33) SCCP NODE VERSION version of SCCP used by node
ANSI88 SCCP version ANSI88
ANSI92 SCCP version ANSI92
ANSI96 SCCP version ANSI96
BLUEBOOK SCCP version Bluebook
REDBOOK SCCP version Redbook
WHITE93 SCCP version White93
WHITE96 SCCP version White96
(34) Protocol (ITU/ANSI) whether ITU or ANSI protocol is
used by node
ANSI protocol is ANSI
ITU protocol is ITU
(35) Credit value maximum window node can handle
(36) UDT message hndl capability whether exchange can handle UDT
messages
ALLOW node has unit data allow
capability
PROHIBIT node prohibits unit data messages
REQ node has unit data request
capability
(37) UDT message return capability whether exchange can return UDT
messages
NORETCAP node has no unit data return
capability
RETCAP node has unit data return
capability
(38) XUDT message hndl capability whether exchange can handle XUDT
messages
ALLOW node has extended unitdata allow
capability
PROHIBIT node prohibits extended unitdata
messages
REQ node has extended unitdata
request capability
(39) XUDT message hndl capability whether exchange can return XUDT
messages
NORETCAP node has no extended unitdata
return capability
RETCAP node has extended unitdata return
capability
(40) LUDT message hndl capability whether exchange can handle LUDT
messages
ALLOW node allows long unitdata
messages
PROHIBIT node prohibits long unitdata
messages
REQ node has long unitdata request
capability
(41) LUDT message hndl capability whether exchange can return LUDT
messages
NORETCAP node has no long unitdata return
capability
RETCAP node has long unitdata return
capability
(42) Message segmentation message segmentation indicator
FALSE segmentation of messages is not
allowed
TRUE segmentation of messages is
allowed
(43) Alternate rout. cong. alternate routing on congestion
indicator
FALSE alternate routing on congestion
is not present
TRUE alternate routing on congestion
is present
(44) Own Point Code check whether exchange can change its
own point code
FALSE node cannot change its own point
code
TRUE node can change its own point
code
(45) Hop counter hop counter
(46) Management link
(47) Used by User header
(48) Used by User1 higher layer user identity 1
translated via relation
R_SUCH_MNE
(49) Used by User2 higher layer user identity 2
translated via relation
R_SUCH_MNE
(50) Used by User3 higher layer user identity 3
translated via relation
R_SUCH_MNE
(51) Used by User4 higher layer user identity 4
translated via relation
R_SUCH_MNE
(52) Used by User5 higher layer user identity 5
translated via relation
R_SUCH_MNE
(53) Used by User6 higher layer user identity 6
translated via relation
R_SUCH_MNE
(54) Used by User7 higher layer user identity 7
translated via relation
R_SUCH_MNE
(55) Used by User8 higher layer user identity 8
translated via relation
R_SUCH_MNE
(56) Link to Digit Prep. link to digit preparation
translated via relation
R_DGTPMNEM
(57) Digit preparation header or suppression
(58) Digit preparation address type digit preparation address type
CD called party address
CG calling party address
RESP responding address
(59) Triggering numbering plan triggering numbering plan
E163/164 E163/164 numbering plan
E210/211 E210/211 numbering plan
E212 E212 numbering plan
E214 E214 numbering plan
F69 F69 numbering plan
GENERIC generic numbering plan
NWSPEC network specific numbering plan
UNKNOWN numbering plan unknown
X121 X121 numbering plan
(60) Triggering nature of address triggering nature of address, see
SI 174
ADD add
ALL all natures of address
CHANGE change
INTAL international
NAT national
NATADDR nature of address
NOTAPPL NR_ABD not applicable
number of abbreviated dialling
NTWKSPEC network specification
REMOVE remove
SUBSC subscriber
UNCHG unchanged
UNKNOWN unknown
(61) Triggering translation type triggering translation type
(62) Triggering encoding scheme triggering encoding scheme
EVEN even encoding scheme
NATSPEC national specific encoding scheme
ODD odd encoding scheme
UNKNOWN unknown encoding scheme
(63) Triggering routing indicator triggering routing indicator
RTGGLBT routing on global title
RTGPC routing on point code
(64) Triggering global title indicator triggering global title indicator
ANSI1 global title indicator - ANSI1
ANSI2 global title indicator - ANSI2
ANSI3 global title indicator - ANSI3
ANSI4 global title indicator - ANSI4
ITU1 global title indicator - ITU1
ITU2 global title indicator - ITU2
ITU3 global title indicator - ITU3
ITU4 global title indicator - ITU4
(65) Triggering global title digits triggering global title digits
(66) Digit preparation type digit preparation type
ADD digit preparation type is
addition
CHANGE digit preparation type is change
(67) Application point application point
(68) Number of digits number of digits
(69) Digits buffer digits buffer
(70) New numbering plan new numbering plan
E163/164 E163/164 numbering plan
E210/211 E210/211 numbering plan
E212 E212 numbering plan
E214 E214 numbering plan
F69 F69 numbering plan
GENERIC generic numbering plan
NWSPEC network specific numbering plan
UNKNOWN unknown numbering plan
X121 X121 numbering plan
(71) New nature of address
see param (60)
new nature of address, see SI 174
(72) New routing indicator new routing indicator
RTGGLBT routing on global title
RTGPC routing on point code
(73) New global title indicator new global title indicator
ANSI1 global title indicator - ANSI1
ANSI2 global title indicator - ANSI2
ANSI3 global title indicator - ANSI3
ANSI4 global title indicator - ANSI4
ITU1 global title indicator - ITU1
ITU2 global title indicator - ITU2
ITU3 global title indicator - ITU3
ITU4 global title indicator - ITU4
(74) Application point for triggering digits application point for triggering
digits
(75) New encoding scheme new encoding scheme
EVEN even encoding scheme
NATSPEC national specific encoding scheme
ODD odd encoding scheme
UNKNOWN unknown encoding scheme
(76) New translation type new translation type
(77) Separator suppression
(78) Separator suppression
(79) Header for compressed report
(80) Lognet for compressed report lognet for compressed report
translated via relation
R_N7LNMNEM
(81) Split PC for compressed report split point code for compressed
report
(82) Protocol for compressed report protocol for compressed report
ANSI protocol used is ANSI
ITU protocol used is ITU
(83) Version for compressed report version for compressed report
ANSI88 SCCP version ANSI88
ANSI92 SCCP version ANSI92
ANSI96 SCCP version ANSI96
BLUEBOOK SCCP version Bluebook
REDBOOK SCCP version Redbook
WHITE93 SCCP version White93
WHITE96 SCCP version White96
(84) Digit preparation used indication digit preparation indicator
N digit preparation is not used
Y digit preapration is used
(85) Used by a high layer user indication higher layer user indication
N not used by higher layer
Y used by higher layer
(86) Credit for compressed report credit for compressed report
(87) Management indication
(88) Error info header
(89) Error info
(90) High Layer User1 id. higher layer userid 1 translated
via relation R_SUCH_MNE
(91) High Layer User2 id. higher layer userid 2 translated
via relation R_SUCH_MNE
(92) High Layer User3 id. higher layer userid 3 translated
via relation R_SUCH_MNE
(93) High Layer User4 id. higher layer userid 4 translated
via relation R_SUCH_MNE
(94) High Layer User5 id. higher layer userid 5 translated
via relation R_SUCH_MNE
(95) High Layer User6 id. higher layer userid 6 translated
via relation R_SUCH_MNE
(96) High Layer User7 id. higher layer userid 7 translated
via relation R_SUCH_MNE
(97) High Layer User8 id. higher layer userid 8 translated
via relation R_SUCH_MNE

Evaluation

Key Parameter Contents / Meaning Action
1 2 3
(89) DESTINATION IS UNKNOWN . . . . . . . . . . . . . . B01
(89) IT IS NOT ALLOWED TO HAVE ALL MESSAGE TYPES PROHIBITED B01
(89) NETWORK IS UNKNOWN . . . . . . . . . . . . . . . . B01
(89) NO VERSION EXISTS FOR CURRENT PROTOCOL . . . . . . B01
(89) NODE ALREADY EXISTS . . . . . . . . . . . . . . . B01
(89) NODE DOES NOT EXIST . . . . . . . . . . . . . . . B01
(89) NODE IS IN USE BY ENTITY . . . . . . . . . . . . . B02
(89) NODE IS IN USE BY FOLLOWING HIGH LAYER USERS : . . B02
(89) NODE IS IN USE BY MANAGEMENT . . . . . . . . . . . B02
(89) OTHER NODE DOES NOT EXIST . . . . . . . . . . . . B01
(89) OWN POINT CODE CAN NOT BE USED TO DEFINE A NON-TERMINATING DESTINATION B01
(89) WHEN ONE MESSAGE TYPE IS REQUIRED, OTHERS SHOULD BE PROHIBITED B01
(89) WRONG DPC GIVEN . . . . . . . . . . . . . . . . . B01

Action Description

Action Meaning
B01 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.
B02 Inconsistencies in the system require special fault clearing. Refer to the document FAULT REPORTING PROCEDURES which is part Customer Documentation Guide.