RRN 01659 DISPLAY/MODIFY N7 PARAMETERS (UNSUCCESSFUL)

YEAPD926

Message Triggering Condition

Response in case of successful result of the execution, on operator request, of one of the following MMC-commands:
CRN 00234 MODIFY-N7PARAM
CRN 00235 DISPLAY-N7PARAM

Report Layout

 SWA-ORJ-MTP
    (A).......................                   (B).................
                                 (C)........................... (D) (E)
    -----------------------------------------------------------------
        OPERATOR INPUT:
         (2)..... (3).... (4)..  &(5).. (6) (7) (8) (9) (10) (11)..
         OWNNAME  = (12)............
         TSTPAT   = (13). & (14).
         CONTROL  = (15).... & (16) & (17) & (18) & (19)
        -----------------------------------------------------------------------
        ERROR:
               (21) (22)
        (23)
  REPORT REFERENCE NUMBER = 1659

Parameter Identification

Par. No. Meaning Remarks
(A) Command name
(B) Main execution result
(C) Result part type
(D) Result part number
(E) Continuation indicator
(2) Parameter identifier
BCEVPERD = broadcast event period in sec&
msec
BCEVRATE = nbr of broadcast allowed per
period
BCSTRATE = broadcasting rate of messages
CHANGE to enable forced modification of
pointcodes
CONTROL = command control
DETAIL = level of detail to be displayed
LOGNET = logical network
MOPCAPPL = multiple own pointcode
application
MTPTIM = message transfer part timer
MTUP = mtup implementation used
NBRLKACT = nbr of links(%) that must be
active before phase1 of restart
procedure
NBRTRA = nbr of TRAs that must be active
before phase1 of restart
NMRECOV = network management recovery
option
NOTRA = indication of whether all routes
from which no TRAs was received
should be considered as available
or unavailable
OPC = ownpoint code
OPCIND = indicates for which set of OPCs
the routeset is valid
PACERATE = pacing rate used for broadcasting
messages
PTFPRATE = max nbr of preventive TFPs sent
per sec from STP
RMBCDUR = broadcast message duration in sec
and msec
RMBCRATE = max nbr of route management
messages sent/sec
RSTRATE = nbr of RST messages sent per sec
RUPURATE = max nbr of received UPU messages
SNDPTFP = indicate if preventive TFPs to be
sent once or twice
SUPURATE = max nbr of UPU messages sent per
second
TSTPATL = testpattern length
XLISTTIM = timer for X-list (ANSI only)
(3) Timer identifier
SLTTIM1A& link congestion status onset
timer
SLTTIM1I& restarting SP ,waiting TRW
SLTTIM2A& link congestion status abatement
timer
SLTTIM2I& min dur of unavailability for
full restart
TIMX & local inhibit test timer
TIMY & remote inhibit test timer
TIM1 & delay to avoid missequencing on
CO
TIM1D & wait on ackn of the signalling
link test me ssage
TIM10 & waiting for forced uninhibit
TIM10B & waiting for inhibit acknowledge
TIM11 & wait starting routeset congestion
test
TIM12 & delay to avoid oscillation on
initial alignment failure
&linkrestart
TIM13 & delay to avoid oscillation on
initial alignment failure and
link restart
TIM14 & timer at restarting STPwaiting
for links to become available
TIM15 & timer at restarting STP waiting
to receive all TRA messages
TIM16 & timer at restart of STP waiting
to broadcast TRA msgs and restart
remaining traffic
TIM17 & timer at STP adjacent to
restarting STP waiting to restart
traffic routed through adj STP
TIM18A & delay to avoid misseq on
CO(delayed lines)
TIM18I & adjacent to restarting SP,waiting
TRW
TIM19A & waiting for CO acknowledge
TIM19I & started when TRA sent in response
to unexpected TRA or TRW
TIM2 & waiting for CO acknowledge
TIM2D & periodic send of signalling link
test message
TIM20A & time controlled diversion
TIM20I & limit sending TFPS and TFAs in
response to TRW or TRA
TIM21A & waiting for CB acknowledge 1st
TIM21I & false link congestion detection
timer
TIM22A & waiting for CB acknowledge 2nd
TIM22I & link oscillation timer-procA
TIM23A & delay to avoid misseq on
controlled routing
TIM23I & min dur of unavailability for
full restart
TIM24A & repeat TFR once by response
method
TIM25A & failed link craft referral timer
TIM26A & waiting for repeat local inhibit
test
TIM28A & waiting to repeat remote inhibit
test
TIM29A & timer at restarting SP waiting
for the links to become available
TIM3 & time controlled diversion
TIM3D & waiting to repeat routeset test
TIM30A & restarting SP started after
T22A,waiting for the links to
become available
TIM31A & waiting to repeat remote inhibit
test
TIM32A & timer at restarting SP waiting
for the
TIM4 & waiting for CB acknoeledge(1st)
TIM4D & wait to repeat routeset test on
low priority
TIM5 & waiting for CB acknoeledge(2nd)
TIM5D & transfer restricted timer
TIM6 & delay to avoid misseq on
controlled routing
TIM6D & waiting for uninhibit acknowledge
(4) Timer value seconds
(5) Timer value milliseconds
(6) Display detail
ALL all info
COMMON MTP system parameters
EXCHOPC exchange name and originating
point code of the own exchange
MTPTIM MTP level 3 timers
SCHED schedule request
(7) Argument type depending on parameter
& COMMON MTP system parameters
& EXCHOPC exchange name and originating
point code of the own exchange
& MTPTIM MTP level 3 timers
ACTIVE OPC is not ORJ deactivated
ALLAVAIL consider all available routes(dir
+ indir)
AVLBL availability of all routes from
which no TRA was received
CAPCODE capability code point code
DEACTIVE OPC is ORJ deactivated
DISABLED mtup disabled
ENABLE mtup enable
MTUPFENA mtup full enabled
MTUPRENA mtup redu enabled
MT16LK more than 16 links
MT4096TK more than 4096 trunks
NETRES network restored point code
NORM normal point code
ONCE TFPs to be sent once
OPCSET1 first set of OPCs
OPCSET2 second set of OPCs
OPCSET3 third set of OPCs
OPCSET4 fourth set of OPCs
OPCSET5 fifth set of OPCs
OPCSET6 sixth set of OPCs
OPCSET7 seventh set of OPCs
REMOVE removel of pointcode from the
logical network
RENUMBER renumbered pointcode
SNDRST sending of routeset test messages
SNDTRA sending of traffic restart
allowed signal
TWICE TFPs to be sent twice
UNAVLBL unavailability of all routes from
which no TRA was received
(8) Display detail
& COMMON MTP system parameters
& EXCHOPC exchange name and originating
point code of the own exchange
& MTPTIM MTP level 3 timers
(9) Logical network name in ASCII form
(10) split point code point code in split
(11) Hexadecimal originating point code point code in hex
(12) Exchange name in ASCII form
(13) Test pattern 1 SLTM test pattern
(14) Test pattern 2 SLTM test pattern
(15) Command control
SCHED schedule request
(16) Month 1 to 12
(17) Day 1 to 31
(18) Hour 0 to 23
(19) Minute 0 to 59
(21) Comments on the executtion result/error indication
(22) Comments on the execution /error indication
(23) Faulty parameter identity

Evaluation

Key Parameter Contents / Meaning Action
1 2 3
(21) A REMOTE EXCHANGE STILL USES THE ASSOCIATED NETWORK A
(21) ANSI POINTCODE VALUE OUT OF RANGE . . . . . . . . A
(21) ANSI POINTCODE 00 XX XX FORMAT NOT ALLOWED . . . . A
(21) BCEVRATE/BCEVPERD > 1 EVENT PER SECOND . . . . . . A
(21) CHANGE NOT ALLOWED WHEN ADDING A POINTCODE . . . . A
(21) CHANGE NOT ALLOWED WHEN REMOVING A POINTCODE . . . A
(21) COMBINED LOCAL TAX IS SPECIFIED . . . . . . . . . A
(21) COMMAND ABORTED . . . . . . . . . . . . . . . . . A
(21) DB ACCESS ERROR . . . . . . . . . . . . . . . . . B
(21) DB INCONSISTENCY . . . . . . . . . . . . . . . . . B
(21) DUT SOT ERROR . . . . . . . . . . . . . . . . . . B
(21) DUT TRANS ERROR . . . . . . . . . . . . . . . . . B
(21) ITU POINTCODE VALUE OUT OF RANGE . . . . . . . . . A
(21) LAST OPC CANNOT BE SET TO NULL . . . . . . . . . . A
(21) MODIFY NOT ALLOWED FOR CAPCODE . . . . . . . . . . A
(21) MOPCAPPL ONLY ALLOWED WHEN A NEW OPC IS ADDED . . A
(21) NAME EXISTS AS A NON CONCERNED AREANAME . . . . . A
(21) NAME EXISTS AS AN OWN EXCHNAME . . . . . . . . . . A
(21) NETWORK NOT EXISTING . . . . . . . . . . . . . . . A
(21) NETWORK STILL USED BY REMOTE EXCHANGE(S) . . . . . A
(21) NETWORK STILL USED BY REMOTE EXCHANGE(S) . . . . . A
(21) NO ACTION PERFORMED : PC IS ALREADY REMOVED . . . A
(21) NO ADDITION WHEN NWRR IS ACTIVE . . . . . . . . . A
(21) NO SPACE IN THE EXCHANGE TABLE (R-N74EXCH) . . . . A
(21) NORMAL PC TO BE CREATED FIRST IN THE NETWORK . . . A
(21) OWN POINT CODE FOR OPCSET1 DOES NOT EXIST . . . . A
(21) PC EXISTS AS DEST . . . . . . . . . . . . . . . . A
(21) POINTCODE ALREADY EXISTS . . . . . . . . . . . . . A
(21) SNTM NOT READY ( PLEASE RETRY ) . . . . . . . . . B
(21) SNTM TIMER EXPIRED ( PLEASE RETRY ) . . . . . . . B
(21) SNTM UPDATE FAILURE ( PLEASE RETRY ) . . . . . . . B
(21) STILL TAX CENTER SPECIFIED . . . . . . . . . . . . A
(21) SW ERROR - RESULT INFO NOT ADJUGED . . . . . . . . B
(21) TERMINATE ORJ . . . . . . . . . . . . . . . . . . A
(22) ALL MOPC MUST BE NULL TO REMOVE NORMAL PC . . . . A
(22) APPLICATION CAN NOT BE FOUND . . . . . . . . . . . A
(22) APPLICATION IS NOT UNIQUE . . . . . . . . . . . . A
(22) CLEAR APPLICATIONS FOR OTHER OPCIND VALUES . . . . A
(22) COMMON EXCHANGE NAME EXISTS,NO NEED OF NEWNWME . . A
(22) COMMON OWNNAME EXISTS-NEWNAME NOT REQUIRED . . . . A
(22) CREATE OPC FOR NORMAL APPLICATION FIRST . . . . . A
(22) DEFINE OWNNAME WHILE CREATING 1st POINT CODE IN LOGNET A
(22) GIVEN NATIONAL SSF VALUE IS NOT ALLOWED . . . . . A
(22) GIVEN OPCIND AND OPC ARE INCONSISTENT . . . . . . A
(22) IMITATED NODE CAN NOT BE FOUND . . . . . . . . . . A
(22) IMITATION OF PC NOT ALLOWED . . . . . . . . . . . A
(22) INPUT LOGNET IS FIRST IN EXCHANGE PROVIDE OWNNAME A
(22) INPUT MOPCAPPL MISMATCH WITH EXISTING MOPCAPPL . . A
(22) LINK NOT IN DEACTIVATED STATE . . . . . . . . . . A
(22) LOGNET=ALL NOT ALLOWED FOR UNIQUE OWNNAME . . . . A
(22) MODIFY NOT ALLOWED WHEN NETWORK RESTORATION ACTIVE A
(22) MOPCAPPL AND OPCIND MUST BE DEFINED WHILE ADDING PC A
(22) MOPCAPPL MUST BE UNIQUE . . . . . . . . . . . . . A
(22) MOPCAPPL ONLY FOR NEW PC . . . . . . . . . . . . . A
(22) NO ACTION ON POINT CODE . . . . . . . . . . . . . A
(22) NO ACTION PC ALREADY REMOVED . . . . . . . . . . . A
(22) NO DATA FOUND . . . . . . . . . . . . . . . . . . A
(22) NO IMITATED NODE . . . . . . . . . . . . . . . . . A
(22) NO MODIFICATIONS WHILE NWRR ACTIVE . . . . . . . . A
(22) NO MORE LINK ON CCM . . . . . . . . . . . . . . . A
(22) OPCIND MUST BE SPECIFIED . . . . . . . . . . . . . A
(22) OPCIND VALUE CAN NOT BE ASSIGNED . . . . . . . . . A
(22) OWNNAME MUST BE UNIQUE . . . . . . . . . . . . . . A
(22) OWNNAME NAME MUST BE COMMON FOR ALL LOGNETS . . . A
(22) OWNNAME REQUIRED ONLY DURING CREATION OF FIRST POINT CODE A
(22) REMOTE EXCHANGES STILL EXIST . . . . . . . . . . . A
(22) REMOVE NOT ALLOWED WHEN NWRR IS ACTIVE . . . . . . A
(22) REMOVE OF PC NOT ALLOWED WHEN SCREENING IS DEFINED A
(22) RENUMPC MUST BE PRESENT TO REMOVE NORMAL PC . . . A
(22) RESTORED PC NOT TO BE REMOVED WHEN NWRR IS ACTIVE A
(22) TO ADD FIRST POINTCODE IN LOGNET PROVIDE UNIQUE OWNNAME A
(22) UNEXPECTED INDEX VALUE IN LINK DEFINITION TABLE . A
(22) UNEXPECTED VALUE IN LINK TRANSLATION TABLE . . . . A
(22) UNIQUE OWNNAME IS REQUIRED . . . . . . . . . . . . A

Action Description

Action Meaning
A The result data is given as an error message, when 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 input data : - when the concerned exchange name is changed, the new name may not already exist as: a own or remote exchange name, a non concerned area name. - the operator has the intention of adding a point code to the own exchange, if no point code is already mentioned for that network and that OPCIND, and if the input is different from the null value. - if the parameter MOPCAPPL is defined /= NORM, that indicates the creation of the new set of the own point codes. Free OPCIND value must be allocated for the new set of own point codes.
  • OPCSTAT may be defined in which case the given value is taken for

active or deactive pointcode. Otherwise, STP default is used. - when a concerned point code for the corresponding network already existed and no null value was given, the existing point code will be modified, in case no remote exchange is using this network. - if, by specifying a concerned point code an old point code for the corresponding network must exist and will be changed without any restrictions. - if the input of the point code was the null value, the operator wants to remove the point code defined for the specified network and having specific OPCIND value. In that case : a point code for this network already exists in the own exchange, at least one point code in the own exchange must remain, no remote exchange may use the associated network for the OPCSET1, - when MTP parameters are changed, an entry must be found in the system table containing the parameters necessary for the proper functioning of the N7 (R_N7l3_PAR ). - if the pointcode for the taxation network is concerned and the own exchange is a combined exchange (i.e. the regristration centre resides in the charging exchange) then R_PAROTAX7.D_NORM_RC contains the old pointcode and consequently the old pointcode must be replaced by the new pointcode (only normal in a local tax combined exchange because normal and alternative may not be switched). Correct the input data and enter the MMC-command again. See also invalid parameter identity (parameter 26). If the input data is correct, the given result data can be taken as information only and it is quite possible that, commands to be entered previous to the command, are forgotten. In that case, enter the necessary MMC-commands first.

B Repeat the command after some time. If the result is still unsuccessful, special fault clearing will be necessary. See fault reporting procedures. Refer to the document FAULT REPORTING PROCEDURES which is part of the Customer Documentation Guide.