02 cn34042en33gln0 troubleshooting tools dx200docshare01.docshare.tips/files/30106/301061423.pdf ·...
TRANSCRIPT
1 © Nokia Siemens Networks CN34042EN33GLN0
Troubleshooting Tools in DX200 Platform
2 © Nokia Siemens Networks CN34042EN33GLN0
Objective
After this module, the student should know:
The SCN troubleshooting tools available in the DX200 platform How to use QA Logging macro for first phase data collection
3 © Nokia Siemens Networks CN34042EN33GLN0
REPORT TO THE USER
SUPER-VISION
SYSTEM
FAULTLOCATINGSYSTEM
RECOVERYSYSTEM
ALARMSYSTEM
Maintenance System
4 © Nokia Siemens Networks CN34042EN33GLN0
ZA ... ALARM SYSTEM ADMINISTRATION
ZAB BLOCKED ALARMS HANDLINGZAC ALARM CANCELLINGZAE ERROR RATIO COUNTER HANDLINGZAH ALARM HISTORY HANDLINGZAL LAMP PANEL HANDLINGZAO ALARM OPERATING INSTRUCTION HANDLINGZAP ALARM PARAMETERS HANDLINGZAR ALARM SYSTEM RULEBASE HANDLINGZAT ALARM PRINTING HANDLING
Alarm system user interface
5 © Nokia Siemens Networks CN34042EN33GLN0
Notices* DisturbancesNotices and Disturbances are additional information about the situation in the exchange. Notices and disturbances do not require actions from the user. * One star alarmsShould be fixed during normal maintenance hours.** Two star alarmsShould be fixed as soon as possible.*** Three star alarmsIndicate a serious situation and require immediate action.
Five Alarm Classes
6 © Nokia Siemens Networks CN34042EN33GLN0
AHP
AHO
t
Alarm
Alarm
Alarm
Alarm
Alarm
No alarm
5 Alarms
Alarms at One Instance of Time
7 © Nokia Siemens Networks CN34042EN33GLN0
MSS01 BSU-0 SWITCH 2004-08-06 15:37:51.71
** ALARM BSU-0 1B001-02 IC2_SS
(0039) 2186 CALL CONTROL ANALYSIS MISSING
02 0002 00 07 04 59 19 D0 00 00 00 00 00 00 00
MSS01 BSU-0 SWITCH 2004-08-06 15:38:45.22
** ALARM BSU-0 1B001-02 IC2_SS
(0040) 2186 CALL CONTROL ANALYSIS MISSING
02 0002 00 07 04 51 98 D0 00 00 00 00 00 00 00
MSS01 BSU-0 SWITCH 2004-08-09 11:41:13.07
** ALARM BSU AIF_SS
(0055) 3200 UNKNOWN RNC
222 03 0002
Alarm printout examples
8 © Nokia Siemens Networks CN34042EN33GLN0
Alarm Print-Out
RECOVERY ACTION
SOURCE SYSTEM
ALARM OBJECTSOURCE COMPUTER
PRINT OUT TYPEOBJECT COORDINATES
ALARM TYPE
ALARM CLASS
CONSECUTIVE NUMBER
ALARM NUMBERSUPPLEMENTARY INFORMATION FIELD
ALARM NAME
SOURCE PROCESS
DATE TIME
MSS01 SIGU-0 SWITCH 2004-08-11 11:08:45.42
** ALARM SIGU-0 1B001-00 IC9_SX
(0033) 2186 CALL CONTROL ANALYSIS MISSING
03 0002 00 08 00 00 07 0E 00 00 00 00
9 © Nokia Siemens Networks CN34042EN33GLN0
ZUD ... DIAGNOSTICS HANDLING
ZUDU START UNIT TEST/PARTIAL UNIT TESTZUDD START I/O DEVICE TESTZUDI INTERROGATE PARTIAL UNIT TESTSZUDL LIST FAULTY UNITS/PROCESSOR UNITSZUDQ INTERROGATE CURRENT TESTSZUDS STOP CURRENT TEST
Diagnostic MML
10 © Nokia Siemens Networks CN34042EN33GLN0
MSCi MSS01 2004-09-09 16:51:28
DIAGNOSTIC REPORT
CLAB-4 1B001-06
PARTIAL DIAGNOSIS CLAB
DIAGNOSTIC PROGRAM 005F
DIAGNOSIS 3998
3998 DIAGNOSIS EXECUTED - UNIT NOT OK
Diagnostic Printout Example
11 © Nokia Siemens Networks CN34042EN33GLN0
Logical fileLogical fileRead / write
ReadRead
DATA
Why Logical File?
Logical files buffer data between a network element and the end-user.
This is a good way to connect multiple users with only one source.
ALL I/O devices are hidden from the application. Therefore, it does not matter whether they are available or out of line.
12 © Nokia Siemens Networks CN34042EN33GLN0
DIAGNOS An output logical file for all hardware diagnostic programs. Receives detailed data from the ongoing test and the results
GSMME1PR A GSM specific report file All currently active subscriber trace information is available via this logical file
OBSFAILA Collects failed call information from call control software when observation is active
Logical files used in troubleshooting
13 © Nokia Siemens Networks CN34042EN33GLN0
Output Clear Codes reporting
ZTUT:CLR;
LOADING PROGRAM VERSION 14.17-0
SIGNALLING RING SPEECH CLEAR CODE0 0 235 000H NORMAL END OF THE CALL 1 3 1 005H B-SUBSCRIBER BUSY 2 0 0 00DH CALL TERMINATED BY OPER
22 7 1 015H NORMAL UNSPECIFIED 0 0 1 024H MAX DUR OF CALL EXCEEDED 1 0 0 304H B-LINE OUT OF SERVICE
89 0 0 30AH A ONHOOK DURING SET UP 51 143 0 30BH A ONHOOK DUR_WAIT ANSWER 1 0 0 603H NO RESPONSE FROM CO-PROC 4 0 0 706H CALL INTER REG ANALYSIS 3 0 0 80FH CIRCUIT CONGESTION
491 0 0 812H MAP FAILURE 2 1 1 B13H RADIO IF FAILURE
END OF REPORT
14 © Nokia Siemens Networks CN34042EN33GLN0
Clear Code groups
Clear codes has been divided into four main classes:
000H - 3FFH: normal clearing400H - 7FFH: internal congestion800H - BFFH: external congestion C00H - FFFH: subscriber errors
The first main class 'normal clearing' (000H – 3FFH) consists of clear codes which have not been caused by an error in the exchange or by subscriber error, but which nevertheless leads to clearing of a call or to an interruption in call set-up.The second main class, 'internal congestion' (400H - 7FFH) consists of cases in which a call or call set-up is interrupted because of an error in the exchange. This group contains clear codes related mainly to file management and to communication between program blocks and different units of the exchange.The third main class, 'external congestion' (800H -BFFH) includes all the cases in which a call or call set-up is interrupted because of an error outside the exchange. This group consists mainly of clear codes related to inter-exchange signalling.The fourth main class, 'subscriber error' (C00H - FFFH) includes the cases in which a call or call set-up is interrupted by a subscriber's error or by a failure in the subscriber's equipment or by faulty subscriber signalling
15 © Nokia Siemens Networks CN34042EN33GLN0
DX 200 MSC KL 2001-10-12 16:00:35
TRAFFIC MEASUREMENT REPORT TRACGRA CGRSOURCE: STU-1 OUTPUT INTERVAL: 60 MIN SAMPLE DATE: 2001-10-12 16:00:00
NCGR CGR CRTS DIR AVECR TC(%) CC CALLS ACCEP ANSW SFAIL IFAIL EFAIL ERLANGS
ECMFAST 187 26 IN 26.0 - - 36 21 18 0 15 0 0.5 OUT 26.0 0.0 0 0 0 0 0 0 0 0.0FAXMO 191 24 IN 22.7 - - 108 58 37 0 0 50 1.0 OUT 22.7 0.0 0 46 44 37 0 0 2 0.8BSC01 310 636 IN 635.0 - - 10569 9236 6115 159 60 1114 130.3 OUT 635.0 0.0 0 6883 6550 4915 0 2 331 129.4BSC02 320 427 IN 426.0 - - 8284 7071 5000 98 40 1075 97.5 OUT 426.0 0.0 0 5451 5056 3913 2 4 389 96.5Name & Nbr. of the CGR
Circuits in CGRper direction
avg. available(WO-EX) circuits
Time (TC) and total (CC) calls congested.Calculation based on time (%) where no circuit in CGR is available during period total amount of call attempts with no circuit available
CALLS : All call attemptsACCEP: Call attempts cleared normal,
but never reached a “conversation” state
ANSW: All answered calls
SFAIL: Failed by Subscriber errorIFAIL : Failed by exchange internal errorEFAIL : Failed by trunk circuit
Circuit Group Measurements Example
16 © Nokia Siemens Networks CN34042EN33GLN0
MSCi MSS01 2004-09-09 17:43:02
MSC OBSERVATION REPORT FROM STU-0
REPORTING TIME : 2004-09-09 17:43:02.61
REPORT NUMBER : 000230
TRACED IMSI : 222039900000020
TRACE REFERENCE : 00001
OMC ID :
TRACE TYPE : ALL, BASIC, UNPRIOR
TRACE TYPE USED : ALL, BASIC, UNPRIOR
START TIME : 2004-09-09 17:42:46.99
END TIME : 2004-09-09 17:43:02.15
RECORDING ENTITY : 39269000080
REPORT REASON : EVENT
INVOKING EVENT : SUBS(A)
CALL ID : 0179H-017AH-4004H-4131H-00DCH-00H-00DCH-00H
CALL START : 2004-09-09 17:42:46.99 CALL PHASE : RELEASE
SIGNALLING COMPLETE : 2004-09-09 17:42:50.98 STAT STATE : IDLE
ANSWER : 2004-09-09 17:42:53.10 CLEAR CODE : 0000H
CHARGING END : 2004-09-09 17:43:02.15 CLEAR INFO : AIF_SS 0001H 0B2EH
PAGING TIME : 1870 CLEAR PART : SUB A
EXT CLEAR CODE : 0010H SIGNALLING : MS CC
Trace example 1/3
17 © Nokia Siemens Networks CN34042EN33GLN0
MGW TRACE : OK
EXTERNAL FORWARDING COUNTER : 0
CALLING NUMBER : I 392695550020
CALLED NUMBER : N 2695550018
OUT PULSED NUMBER : I 392695550018
CONNECTED NUMBER : I 392695550018
ROAMING NUMBER : N 2698000163
ADDRESS NUMBER : U 2695550018
IP TRUNK : NOT USED IP TRUNK
OBJECT SUBSCRIBER A (TRACED) SUBSCRIBER B
IMSI : 222039900000020 222039900000018
IMEI :
Trace example 2/3
18 © Nokia Siemens Networks CN34042EN33GLN0
Trace example 3/3
RADIO SYSTEM : UMTS UMTS
CGR/BSC/PCM-TSL : / / - / / -
MCC/MNC : 222 /03 222 /03
LAC/CI/CELL BAND : 00932/00932/ 00932/00932/
RNC ID : 00002 00002
MGW INDEX : 0 0
MGW NAME : MGW2 MGW2
BNC CHAR : AAL2 AAL2
UPD INDEX/NAME : 0 /UPD0 0 /UPD0
TDM TERMID :
CHANNEL RATE : FR / HFR1 / FR / HFR1 /
SPEECH VERSION : FR3 FR3
PRIORITY : 3 3
MS CLASSMARK :
ECHO CANCELLING PARAMETERS
RECEIVED IEC / OEC : INCLUDED / INCLUDED
SENT IEC / OEC : INCLUDED / INCLUDED
END OF REPORT
19 © Nokia Siemens Networks CN34042EN33GLN0
2
CATEGORY Test mobile created in the HLR
Test digit analysis tree with analysisorTest attribute analysis created
TEST ACTIVITYYCH-MML
START TESTYCS-MML
TEST CATEGORY 4
Testing number analysis
20 © Nokia Siemens Networks CN34042EN33GLN0
CATEGORY Test mobile created in the HLR
TEST HUNTINGYC-MML
START TESTYCS-MML
TEST CATEGORY 4
TE TIME SLOT IN TEST STATE
Testing number analysis
21 © Nokia Siemens Networks CN34042EN33GLN0
X
B3 2M
Typical problem
and solution
2M
X
Loop Transmission
22 © Nokia Siemens Networks CN34042EN33GLN0
MMDIREActive BLCODE
LFILES
ASWDIRMMLLOG 20040912.00
20040911.0020040910.0020040909.00
MML LOG
23 © Nokia Siemens Networks CN34042EN33GLN0
MML command log
ZIGO:2006-01-26,10-00,2006-01-26,10-30:USERID=SYSTEM::;
LOADING PROGRAM VERSION 4.8-0/* MSS_880091 MSCi SYSTEM 2006-01-26 10:09:42 */AHP::NR=:2006-01-26,09-00-00:;/* 3 SESSION=00008 USERID=SYSTEM 2006-01-26 10:03:20 *//* 4 AHP::NR=:2006-01-26,09-00-00:; *//* 4c COMMAND EXECUTED *//* 4c SESSION=00008 USERID=SYSTEM 2006-01-26 10:03:20 */USI:COMP;/* 3 SESSION=00008 USERID=SYSTEM 2006-01-26 10:07:44 *//* 4 USI:COMP; *//* 4c COMMAND EXECUTED *//* 4c SESSION=00008 USERID=SYSTEM 2006-01-26 10:07:44 */NEL;/* 3 SESSION=00008 USERID=SYSTEM 2006-01-26 10:07:50 *//* 4 NEL; *//* 4c COMMAND EXECUTED *//* 4c SESSION=00008 USERID=SYSTEM 2006-01-26 10:07:50 */IGO:2006-01-26,10-00,2006-01-26,10-30:USERID=SYSTEM::;/* 3 SESSION=00008 USERID=SYSTEM 2006-01-26 10:09:42 */COMMAND EXECUTED
24 © Nokia Siemens Networks CN34042EN33GLN0
DX200 SERVICE TERMINAL MAIN LEVEL COMMANDS:
? ..... MENU / HELP I .. .. GENERAL INFORMATIONA ..... ANALYZER L ..... EXTENSION HANDLINGB ..... DEFINE ENVIRONMENT O ..... OPERATING SYSTEM COMMANDSC ..... COMMAND LANGUAGE UTILITIES R ..... REMOTE DEBUGGER HANDLINGD ..... MEMORY AND I/O HANDLING S ..... SYSTEM MONITORING COMMANDSE ..... EXIT DEBUGGER SESSION T ..... TERMINAL HANDLING
EXTENSIONS:
G ..... COMPUTER LOG HANDLER (DEF) U ..... RECOVERY DEBUGGER
M ..... MASS MEMORY HANDLING
INITIAL NAME: 00BE 0000 00 CURRENT NAME: 00BE 0000 00
00-MAN>
Service Terminal
25 © Nokia Siemens Networks CN34042EN33GLN0
BSUBSUCMCM
CCSU / SIGU
CCSU / SIGU
HLR
VLR
PSTN
Traffic Flow in the MSC/MSS
26 © Nokia Siemens Networks CN34042EN33GLN0
QA LoggingFirst phase data collection macro
27 © Nokia Siemens Networks CN34042EN33GLN0
QA Logging – Introduction
When abnormal situation occurs in customer networkProblem reported to NSNSome obligatory information need to be collected for troubleshooting
In the first phase of troubleshooting, we required information about: Detailed case description SW versions Generic configuration data from involved network elements
Based on collected information technical support engineer should be able to determine the nature of the problem Configuration error SW defect HW failure
28 © Nokia Siemens Networks CN34042EN33GLN0
QA Logging – Faster troubleshooting
Provide essential information to get troubleshooting immediately to right direction without any extra delays due to unnecessary info requests
In later troubleshooting phase some extra SW monitoring or configuration data might be needed, which is requested by a new information request.
29 © Nokia Siemens Networks CN34042EN33GLN0
QA Logging – Description
QA logging macro is made to execute this first phase data collection
Macro is divided in two parts: questioning and data collection.
Questioning part is first executed to define the case description Predefined problem areas (Call failures, unit restarts, site connectivity,…) If user cannot immediately answer to some questions, answers should be found
out before continuing to avoid unnecessary info requests. Generic data collection for unidentified problems
Data collection based on given answers.
30 © Nokia Siemens Networks CN34042EN33GLN0
Preliminary actions
Use always latest QAL version available, getting by send e-mail:To : [email protected]: QAL_UPDATE
QA logging macro is made for HIT toolHIT must be installed in user’s Windows PCHIT 2.10-x or higher is requiredDevice connection for all involved network elements
need to be defined in HIT
QA logging include the following files which must be included in same local directory in user’s PC QAL_START.hit (macro file for execution) QAL_FUNC.tel ( function library) QAL.ini (logic for questioning phase)
QAL 2.1-3 MSS.zip
31 © Nokia Siemens Networks CN34042EN33GLN0
Execution
Start HIT tools and define device connection, if not exist yet Open QAL_START.HIT and press start button
32 © Nokia Siemens Networks CN34042EN33GLN0
Select Problem area to start questioning phase
Questioning based on selected problem area, answer correctly to all questions
Execution
Full data collection is not for first phase data collection. It should be run only when requested by NSN.
33 © Nokia Siemens Networks CN34042EN33GLN0
Execution
Select execution mode, single or multi-tasking mode
Select network element for data collection , execution start after devices are selected
34 © Nokia Siemens Networks CN34042EN33GLN0
Results
Results are collected in case specific directories under execution directory. There are subdirectories for all NE from where data was collected Directory format: /QAL_<date>_<time>/
/QAL_<date>_<time>/<element name>/
Log files must be zipped to decrease size. Usually less than 1Mbits even several elements included.
Example: /QAL_2009-12-02_13-44-27/…QAL_2009-12-02_13-44-27.ZIP
NOTE! It is mandatory to include QA logging results in every problem case before it’s escalated to level 3 in Resolve.
35 © Nokia Siemens Networks CN34042EN33GLN0
QA_LOGGING creates unique case specific directory under execution directory. Under case directory there are subdirectories for all network elements from where data was collected.
Result
36 © Nokia Siemens Networks CN34042EN33GLN0
Appendix
37 © Nokia Siemens Networks CN34042EN33GLN0
Find your VTP/VDU
ZQNS;
MSCi MSS_880091 2006-05-20 14:28:31 PAGE 1
SYSTEM USERNAME USER USER MML SESSIONSYSTEM I/O-DEVICE NUMBER
990095 MSC02 SYSTEM 880091 MSC02 OMU-VTP17 TU 00602SYSTEM 880091 MSC02 OMU-VTP19 QN 00612SYSTEM 880091 MSC02 OMU-VTP21 US 00607
COMMAND EXECUTED
38 © Nokia Siemens Networks CN34042EN33GLN0
Connect DIAGNOS logical file to your VTP
If you want the diagnostics output to appear on you screen then connect logical file to your VTP/VDU
ZIIS:,OMU:DIAGNOS,::DEV=VTP-19:;
LOGICAL FILE MODIFIED:
SYSTEM = MSS_880091 UNIT = OMU
PAGE 1LOG LOG SPARE PHYSICAL OBJ SYSTEM UNIT DEVICE/FILE FILE FILE FILE IND NAME NAME LOGICALNBR NAME & CLASS MODE NAME FILE
5B DIAGNOS P 1 MSS_880091 OMU LPT-12 MSS_880091 OMU VDU-53 MSS_880091 OMU VTP-19
39 © Nokia Siemens Networks CN34042EN33GLN0
Start diagnostics
Change Computer Unit state to TE-EX…
ZUSC:SIGU,2:TE;
Then start diagnostics…
ZUDU:SIGU,2;
40 © Nokia Siemens Networks CN34042EN33GLN0
Diagnostics output
Press enter several times to get partial and total diagnostics report on your screen
MSCi MSS_880091 2006-01-26 11:55:33
DIAGNOSTIC REPORT
SIGU-2 1B002-00
PARTIAL DIAGNOSIS TOTALDIAGNOSTIC PROGRAM 0000DIAGNOSIS 3999
3999 TOTAL DIAGNOSIS EXECUTED - UNIT OK
END OF REPORT
If you didn’t connect the logical file to your VTP/VDU then you can always check diagnostics result from history (see next page)…
41 © Nokia Siemens Networks CN34042EN33GLN0
Diagnostics history
ZUDH:SIGU,2::;
MSCi MSS_880091 2006-01-26 11:35:43
DIAGNOSTIC REPORT HISTORYUNIT = SIGU-2 REPORT-CLASS = ALL DATE = 2006-01-26 TIME = 00:00:00
MSCi MSS_880091 2006-01-26 10:42:11PARTIAL DIAGNOSIS EXECUTED SIGU-2 POWER
MSCi MSS_880091 2006-01-26 10:42:35PARTIAL DIAGNOSIS EXECUTED SIGU-2 CPU
MSCi MSS_880091 2006-01-26 10:42:35PARTIAL DIAGNOSIS EXECUTED SIGU-2 RAM
MSCi MSS_880091 2006-01-26 10:42:40PARTIAL DIAGNOSIS EXECUTED SIGU-2 SYSB
MSCi MSS_880091 2006-01-26 10:42:40
DIAGNOSTIC REPORT
SIGU-2
PARTIAL DIAGNOSIS TOTALDIAGNOSTIC PROGRAM 0000DIAGNOSIS 3999
3999 TOTAL DIAGNOSIS EXECUTED - UNIT OK
END OF REPORT
42 © Nokia Siemens Networks CN34042EN33GLN0
Set trace on Nokia Clear Code
ZIIS:,OMU:OBSFAILA,::DEV=VTP-19:;ZTOF:S,:005:; (trace for B-Subscriber busy: 0005H)
SIGNALLING COMPLETE : 2006-01-26 16:11:08.21 STAT STATE : IDLEANSWER : CLEAR CODE : 0005HCHARGING END : CLEAR INFO : AIF_SS 0003H 0B2FHPAGING TIME : 1280 CLEAR PART : SUB BEXT CLEAR CODE : 0011H SIGNALLING : MS CC
Check details in NED…
Clear Code
Additional information fields
43 © Nokia Siemens Networks CN34042EN33GLN0
Connect logical file OBSFAILA to physical file on disk1. Create new directory for the physical file on both disks
ZIWL:,OMU:WSB,DEF::PHYFILES,,,XY:;
2. Create physical file (OBSFAILALOG.TXT) on both disks
ZIWC:,OMU:WSB,DEF:PHYFILES,:OBSFAILALOG,TXT,999999,XY:;
(One CC observation needs about 2490 bytes. File size "999999" gives space for about 400 CC observations)
3. Link physical (as a ring file) file to logical file (OBSFAILA)
ZIII:,OMU:OBSFAILA,B:,PHYFILES,:OBSFAILALOG,TXT,,RF:;
4. Set logical file to write to both disks
ZIIS:,OMU:OBSFAILA,::DEV=WDU-SB:;
5. Set path to read file from system disk
ZIWY:S:UNIT=OMU,PATH=-PHYFILES,DRIVE=WDU-S;
6. Output physical file in ASCII format
ZIBT:WDU,S,OBSFAILALOG,TXT,,,,A,;
44 © Nokia Siemens Networks CN34042EN33GLN0
Fast Subscriber Trace for ongoing calls onlyMCJ:IMSI=460100000000104::TYPE=D:;
MSCi MSS04 2008-05-20 15:05:45
SEARCH CALL PATH
LEG TYPE : ORIGINAL LEG CALL ID : 0004H-0000000BH-4004H-4131H-0003H-00H-4131H-0005H-00HORIG CALL ID :CALL START : 2008-05-20 15:05:24 TARGET : MSC /SCALLFSIGN COMP : 2008-05-20 15:05:28 CALL TYPE : INTERNAL ANSWER : 2008-05-20 15:05:29 CALL PHASE : CONVERSATION CHAR END : ....-..-.. ..:..:.. STAT STATE : AB SEIZEDLAST MESSAGE : 2008-05-20 15:05:29 D5C8CLEAR CODE : UNIT ID : BSU -001
CALLING NUMBER : I 8622301000006 CALLED NUMBER : I 8612301000104 OUTPULSED NUMBER : I 8612301000104 CONNECTED NUMBER : I 8612301000104 FORWARDED TO : ROAMING NUMBER : N 42300100006 ADDRESS NUMBER : U 12301000104
OBJECT SUBSCRIBER A SUBSCRIBER BTRACING REF/TYPE : / 00001/ALL EVENTSIMSI : 460200000000006 460100000000104 IMEI : RADIO SYSTEM : GSM GSMCGR/PCM-TSL/STATE : 00531/2048-04/R 00531/2048-05/RBICC CIRCUITNET :
SPC : CIC :
MGW : VMGW31 VMGW31BNC CHAR : TDM TDMTDMTERMID : 00001-04 00001-05TERMID :
45 © Nokia Siemens Networks CN34042EN33GLN0
Fast Subscriber Trace for ongoing calls only(Cont.)CNTL TYPE/INDEX : BSU /00001 BSU /00001MCC/MNC : 460 /30 460 /30 BSC/LAC/CI : 00003/00300/00301 00003/00300/00301RNC : NAME/INTRA CI : BTS301 /00000 BTS301 /00000LOCATION NUMBER : USED CODEC : G711 A G711 A CHANNEL RATE : FR /FR /FR FRP /FR /FRSPEECH VERSION : FR1 FR1LSA : USED CHANNEL CODINGS : PRIOR/CATEG : /ORDINARY /ORDINARYMS CLASSMARK : 3 3 MS UMTS CAPABILITY : IN CATEGORY KEY : CAMEL CALL ADDRESS : CAMEL REF NUMBER : CTM TT CAPABLE : NO NOTEST CALL CATEGORY : PAGING TIME : 01170 msBACK/FORW : / HO LINK : ROAM LINK : 0005INTERCONNECTING TDM : - -ANCHOR IC TDM : -
ECHO CANCELLING PARAMETERSRECEIVED IEC / OEC : INCLUDED / INCLUDEDSENT IEC / OEC : INCLUDED / INCLUDEDIEC STATE / OEC STATE : /
ICC-PID 4131H/0134H/0003H/00H SSI-PID / / / SSO-PID / / / AIFI-PID 4131H/0132H/002EH/00H AIFO-PID 4131H/0132H/002FH/00H OCC-PID 4131H/0136H/0005H/00H CFO-PID / / / CTH1-PID / / / CTH2-PID / / /
COMMAND EXECUTED
46 © Nokia Siemens Networks CN34042EN33GLN0
Detailed Subscriber TraceZIIS:,OMU:GSMME1PR,::DEV=VTP-19:;ZMWC:MSISDN=460100000000104:REF=1,:;
MSCi MSS04 2008-05-20 15:14:36MSC OBSERVATION REPORT FROM OMU-0
REPORTING TIME : 2008-05-20 15:14:36.97
REPORT NUMBER : 000029RECORDING ENTITY : 8642300100
REPORT REASON : EVENTINVOKING EVENT : FAIL
CALL ID : 0008H-00000010H-4004H-4131H-0006H-00H-4131H-0009H-00H
CALL START : 2008-05-20 15:14:24.22 CALL PHASE : RELEASESIGNALLING COMPLETE : STAT STATE : IDLE
ANSWER : CLEAR CODE : 0874HCHARGING END : CLEAR INFO : URQPRB 0E01H 0000H
PAGING TIME : CLEAR PART : SYSTEMEXT CLEAR CODE : SIGNALLING : -
MGW TRACE : OK
EXTERNAL FORWARDING COUNTER : 0
47 © Nokia Siemens Networks CN34042EN33GLN0
CALLING NUMBER : I 8612301000104 CALLED NUMBER : N 1022301000006 OUT PULSED NUMBER : CONNECTED NUMBER : ROAMING NUMBER : ADDRESS NUMBER : U 1022301000006 BIWF ADDRESS A : 8632300300
DESTINATION: 14
SUBDEST ROUTE RESULT38 2100 0874H
OBJECT SUBSCRIBER A SUBSCRIBER B IMSI : 460100000000104 IMEI : RADIO SYSTEM : GSM -CGR/BSC/PCM-TSL : 0531/0003/2048-08 / / -MCC/MNC : 460 /30 / LAC/CI/CELL BAND : 00300/00301/ / /MGW INDEX : 0MGW NAME : VMGW31BNC CHAR : TDMTDM TERMID : 1-8 NORMAL CTX ID : 524694USED CODEC : G711 ACHANNEL RATE : FRP / FR / FR / / SPEECH VERSION : FR1 PRIORITY : MS CLASSMARK : 3 DUAL BANDCTM TT CAPABILITY : NO
END OF REPORT
48 © Nokia Siemens Networks CN34042EN33GLN0
Test calls
Test calls are done for two purposes:
test analysis - to test defined analyses
test hunting - to force-route a call on a certain circuit that is put in the TE state.
Test calls
Test analyses Test hunting (forced routing)
49 © Nokia Siemens Networks CN34042EN33GLN0
Flow of test calls
Test origin
matched
Normal cellTest cell
Test mobile
Test phone
Normal cell
Not test mobileTest mobile or
not test mobile
Normal trunk
Test trunk
Normal trunk
Not test phone
Test phone or
not test phone
Test case
definition
A) Test analysis
B) Test hunting
C) Test analysis and
Test Hunting
Normal traffic
Own MSCExchange
No
Yes
0 test origin = normal cell
1 test origin = normal incoming circuit
2 test origin = test cell
3 test origin = incoming test circuit
4 test origin = test origin received in subscriber signalling
5 test origin = test origin received in incoming circuit signalling
4 02
1
3
5
50 © Nokia Siemens Networks CN34042EN33GLN0
BSU
CM
CCSU
24
13215
33215
1) Check CM state – ZUSI:CM,:; e.g. CM,0 WO-EX
2) Connect service terminal - ZDDS:CM, 0:; ( 1 in case CM,1 is working).
3) ZOQA:W,C=32154) ZOQ:70
Message Monitoring
51 © Nokia Siemens Networks CN34042EN33GLN0
Monitoring attribute resultsAnalysis tree Charging origin Analysed digits
Analysis type TMR TON
Type of Number in Messages:
not_exist 0not_allowed 1unknown 2reserved 3unknown_numb 4international 5national 6net_specific 7subscriber 8abbreviated 9dedicated_pad A
Numbering Plan in Messages:
not_exist 0not_allowed 1unknown 2reserved 3unknown_plan 4isdn_teleph 5data 6telex 7nation_stand 8private 9
TMR255 do_not_care_c Do not care 10 khz3_1_c 3.1 kHz audio 9 kb64_pre_c 64 kbit/s preferred 8 kb64_unres_c 64 kbit/s unrestricted 6 kb1920_unres_c Reserved for 1920 kbit/s unrestricted 5 kb1536_unres_c Reserved for 1536 kbit/s unrestricted 4 speech_c Speech 3 kb384_unres_c Reserved for 384 kbit/s unrestricted 2 kb2_64_unres_c Reserved for 2 x 64 kbit/s unrestricted 1 sv_1_sv_2_c Alternate 64 kbit/s unrestricted (service 1)/ speech (service 2) 0 sv_2_sv_1_c Alternate speech (service 2)/ 64 kbit/s unrestricted (service 1)
MONITORING TIME: 2004-03-28 11:22:27.74
RECEIVED BY: 0070 0000 00
MONITORED MESSAGE: 0053 4532 0134 0113 00 19 0000 3215 0041
00 00 02 00 00 00 00 00 00 00 FF FF FF 06 04 09 0A 09 09 03 06 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 FF 04 06 00 64 00 00 00 00 00 00 00