RRN 06933 ROUTING ADMINISTRATION: HANDLE SPC

GSPK8F04

Message Triggering Condition

Response in case of successful / unsuccessful result of the execution, on operator request, of the following MMC-commands:
CRN 06228 DISPLAY-SPC

Report Layout

 SWA-ORJ-SPC COMMND HDLR
    (A).......................                   (B).................
                                 (C)........................... (D) (E)
    -----------------------------------------------------------------
      (1)...................
      ERROR POINT   =    (2)........
      ERROR MESSAGE =    (3)..............
      ERROR MESSAGE =    (4)..............
      SPCID            STATE    PCE&TN       LAN       PCE&TN     LAN
      --------------------------------------------------------------(5)
      (6)............ (7)....  (8).. (9).   (10).  (11). (12)   (13)
  REPORT REFERENCE NUMBER = 6933

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) Comments on the execution result see Evaluation
(2) Error point see Evaluation
(3) Error Message see Evaluation
(4) Additional error message see Evaluation
(5) SUPPRESSL
(6) Semi-permanent connection identity
(7) State of connection
(8) Incoming physical control element identity
(9) Terminal number principal terminal number
(10) Incoming PCM ID
(11) Outgoing physical control element identity outgoing PCE identity
(12) outgoing terminal number principal terminal number
(13) Outgoing PCM ID

Evaluation

Key Parameter Contents / Meaning Action
1 2 3
(1) BOTH SIDES ARE BUSY, WHEN THEY BECOME FREE THE SPC WILL BE SETUP A
(1) INCOMING SIDE IS BUSY, WHEN IT BECOMES FREE THE SPC WILL BE SETUP A
(1) OUTGOING SIDE IS BUSY, WHEN IT BECOMES FREE THE SPC WILL BE SETUP A
(1) PROBLEM LIST . . . . . . . . . . . . . . . . . . . B
(1) PROCESS COMPLETE: NO SPC FOUND WITH ECHO CANCELLER (I/C SIDE) C
(1) PROCESS COMPLETE: NO SPC FOUND WITH ECHO CANCELLER (O/G SIDE) C
(1) PROCESS COMPLETE: NO SPC FOUND WITH ECHO CANCELLER ON BOTH SIDES C
(1) PROCESS COMPLETE:NO SPC FOUND WITH I/C ECHO CANC. FOR THAT RTE-ID C
(1) PROCESS COMPLETE:NO SPC FOUND WITH O/C ECHO CANC. FOR THAT RTE-ID C
(1) PROCESS COMPLETE:NO SPC WITH ECHO CANC. (ON BOTH SIDE) ON THAT CE C
(1) PROCESS COMPLETE:NO SPC WITH ECHO CANC. (ON BOTH) IN THAT RTE-ID C
(1) PROCESS COMPLETE:NO SPC WITH ECHO CANC. (ON I/C SIDE) FOR THAT CE C
(1) PROCESS COMPLETE:NO SPC WITH ECHO CANC. (ON O/G SIDE) FOR THAT CE C
(1) PROCESSING COMPLETE: NO NAIL-UP CONNECTIONS FOUND C
(1) PROCESSING COMPLETE: NO NAIL-UP CONNECTIONS FOUND FOR THAT CE C
(1) PROCESSING COMPLETE: NO NAIL-UP CONNECTIONS FOUND FOR THAT RTE-ID C
(1) PROCESSING COMPLETE: NO SEMIPERM CONNECTIONS FOUND FOR THAT CE C
(1) PROCESSING COMPLETE: NO SEMIPERMANENT CONNECTIONS FOUND C
(1) PROCESSING COMPLETE: NO SPC FOUND FOR THAT RTE-ID C
(1) PROCESSING COMPLETE: NO SPCSIGN FOUND . . . . . . C
(1) PROCESSING COMPLETE: NO SPCSIGN FOUND FOR THAT CE C
(1) PROCESSING COMPLETE: NO SPCSIGN FOUND FOR THAT RTE-ID C
(2) CONSISTENCY ERROR . . . . . . . . . . . . . . . . D
(3) CAS TRK ALREADY SEIZED . . . . . . . . . . . . . . C
(3) CE NOT FOUND . . . . . . . . . . . . . . . . . . . C
(3) CONFLICT FOR THIS TYPE OF CONNECTION . . . . . . . C
(3) DATABASE ERROR . . . . . . . . . . . . . . . . . . D
(3) DATABASE INCONSISTENCY . . . . . . . . . . . . . . D
(3) DUT SCHEDULING NOT ACKNOWLEDGED . . . . . . . . . D
(3) DUT UNSCHEDULING NOT ACKNOWLEDGED . . . . . . . . D
(3) EQUIPMENT NUMBER REPLICATION . . . . . . . . . . . C
(3) GIVEN TN NOT FOR TELEPHONIC USE . . . . . . . . . C
(3) ILLEGAL CE . . . . . . . . . . . . . . . . . . . . C
(3) ILLEGAL ROUTE-ID . . . . . . . . . . . . . . . . . C
(3) INCOMING CE NOT EXISTING . . . . . . . . . . . . . C
(3) INCOMING LINE ASSIGNED FOR SPC . . . . . . . . . . C
(3) INCOMING TN NOT FOR TELEPHONIC USE . . . . . . . . C
(3) INCOMING TN OUT OF RANGE FOR EVEN CE . . . . . . . C
(3) INCOMING TN OUT OF RANGE FOR ODD CE . . . . . . . C
(3) INVALID BASIC ACCESS TN . . . . . . . . . . . . . C
(3) ISDN TRK FREE . . . . . . . . . . . . . . . . . . C
(3) LEN EN TRANSLATION NOT OK . . . . . . . . . . . . D
(3) LINE ALREADY LINKED . . . . . . . . . . . . . . . C
(3) LINE ASSIGNED TO A DIRECTORY NBR . . . . . . . . . C
(3) LINE TN NOT EQUIPED . . . . . . . . . . . . . . . C
(3) MULTISLOT CONN NOT ALLOWED . . . . . . . . . . . . C
(3) NAIL-UP CONN NOT EXISTING . . . . . . . . . . . . C
(3) NBR OF ORG TNS ARE NOT EQUAL TO MULTISLOT NBR . . C
(3) NBR OF OUTGOING TNS ARE NOT EQUAL TO MULTISLOT NBR C
(3) OUTGOING CE NOT EXISTING . . . . . . . . . . . . . C
(3) OUTGOING LINE ASSIGNED FOR SPC . . . . . . . . . . C
(3) OUTGOING TN NOT FOR TELEPHONIC USE . . . . . . . . C
(3) OUTGOING TN OUT OF RANGE FOR EVEN CE . . . . . . . C
(3) OUTGOING TN OUT OF RANGE FOR ODD CE . . . . . . . C
(3) PROBLEM IN INCOMING SIDE, SPC DATA IS MODIFIED SUCCESSFULLY C
(3) PROBLEM IN OUTGOING SIDE, SPC DATA IS MODIFIED SUCCESSFULLY C
(3) PROBLEMS IN BOTH SIDES, SPC DATA IS MODIFIED SUCCESSFULLY C
(3) REATTEMPT TO ESTABLISH CONNECTION WILL BE DONE IN 15 MINS C
(3) REPLICATED TNS IN THE ORG MULTISLOT . . . . . . . C
(3) REPLICATED TNS IN THE OUTGOING MULTISLOT . . . . . C
(3) SOFTWARE ERROR . . . . . . . . . . . . . . . . . . D
(3) TEMP OR PERD MULTISLOT SPC EXISTS . . . . . . . . C
(3) TEMP OR PERD SPC ALREADY EXISTS . . . . . . . . . C
(3) TEMP/PER SPC NOT ALLOWED ON NOTASS TN . . . . . . C
(3) THE B-CHANNEL IS MISSING FOR THE BASIC ACCESS . . C
(3) THE TRK HAS TO BE ISUP OR TUP . . . . . . . . . . C
(3) TIMER EXPIRED . . . . . . . . . . . . . . . . . . D
(3) TN OUT OF RANGE FOR THAT CE . . . . . . . . . . . C
(3) TRK ALREADY LINKED . . . . . . . . . . . . . . . . C
(3) TRK ASSIGNED TO A TRUNKGROUP . . . . . . . . . . . C
(3) TRK BELONGS TO A TRUNKGROUP . . . . . . . . . . . C
(3) TRK IS ALREADY USED . . . . . . . . . . . . . . . C
(3) TRK TN NOT EQUIPED (R_STATE) . . . . . . . . . . . C
(3) TRUNK-ID EN TRANSLATION NOT OK . . . . . . . . . . C
(4) ACTIVE DAY NOT ALLOWED FOR A TEMPORAL LINK . . . . C
(4) APPLICATION PROCESS COULD NOT BE CREATED . . . . . D
(4) BEARER CAPABILITY MUST BE UNRESTRICTED DIGITAL . . C
(4) CONFIRMATION IS REQUESTED . . . . . . . . . . . . C
(4) CONTINUOUS SETUP IS NOT ALLOWED FOR PERIODICAL LINK C
(4) DURATION TOO LONG FOR A TEMPORAL LINK . . . . . . C
(4) DURATION TOO SHORT . . . . . . . . . . . . . . . . C
(4) ILLEGAL ROUTE-ID . . . . . . . . . . . . . . . . . C
(4) INCOMING SIDE INVOLVED IN AN INDEFINITE LINK . . . C
(4) INCOMING TRUNK INVOLVED IN ORA/RANSTLE . . . . . . C
(4) INDEFINITE NAILUP ALREADY EXISTS . . . . . . . . . C
(4) INVALID DAY . . . . . . . . . . . . . . . . . . . C
(4) INVALID HOUR . . . . . . . . . . . . . . . . . . . C
(4) INVALID MINUTE . . . . . . . . . . . . . . . . . . C
(4) INVALID MONTH . . . . . . . . . . . . . . . . . . C
(4) INVALID SPC-ID . . . . . . . . . . . . . . . . . . C
(4) INVALID START DATE . . . . . . . . . . . . . . . . C
(4) INVALID START TIME . . . . . . . . . . . . . . . . C
(4) INVALID STOP DATE . . . . . . . . . . . . . . . . C
(4) NUMBER OF SPCS AND PARAMTERS DO NOT MATCH . . . . C
(4) ONLY TEMP. OR PERD. SPCS CAN BE MODIFIED . . . . . C
(4) OUTGOING SIDE INVOLVED IN AN INDEFINITE LINK . . . C
(4) OUTGOING TRUNK INVOLVED IN ORA/RANSTLE . . . . . . C
(4) OVERLAP WITH AN EXISTING PERIODICAL LINK . . . . . C
(4) OVERLAP WITH AN EXISTING TEMPORAL LINK . . . . . . C
(4) SPC-ID ALREADY EXISTS . . . . . . . . . . . . . . C
(4) START AND STOP TIME INCONSISTENCY . . . . . . . . C
(4) TEMP. SPC HAS TO BOOKED WITHIN 30 DAYS . . . . . . C
(4) TIME OVERLAPS WITH AN EXISTING LINK . . . . . . . C
(4) TIMEOUT UNKNOWN TIMER . . . . . . . . . . . . . . D

Action Description

Action Meaning
A If one of the terminal equipments (incoming or outgoing) or both of them are involved in a switching connection, the semi-permanent connection will be established whenever the terminal equipment(s) become free,
B See also error point (parameter 2), error message (parameter 3) and additional error information (parameter 4) to identify the problem and continue with the necessary action.
C Check the input data and repeat the MMC-command.
D Repeat the command after some time. If the result is still unsuccessful , special fault clearing will be necessary. See fault reporting procedures.