Manual - Call Analysis Description

Seven.
Five
Call Analysis Description
Manual
SwissQual AG
Main Office: Allmendweg 8, 4528 Zuchwil, Switzerland
Reception: +41 32 686 6565
Fax: +41 32 686 6566
Email: support@swissqual.com
Web: http://www.swissqual.com
Document Information
Document Title Manual – Call Analysis Description
Document Number 16-100-200510
Version Date Comment

1.0 30.10.2002 Initial Version, based on NQDI Release 2.8.1
1.1 14.03.2003 Updated for Release 2.9.2
1.2 22.07.2003 Small layout modifications
1.3 01.10.2003 Some minor changes for Release 3.0.4
1.4 20.01.2004 Include UMTS sampled data
2.0 06.04.2005 Include UMTS and partly CDMA
12.04.2006 Updated for Release 9.3.
Copyright 2000-2006 SwissQual AG. All rights reserved.
No part of this publication may be copied, distributed, transmitted, transcribed, stored in a retrieval system, or translated into any
human or computer language without the prior written permission of SwissQual AG.
SwissQual has made every effort to ensure that eventual instructions contained in the document are adequate and free of errors and
omissions. SwissQual will, if necessary, explain issues, which may not be covered by the documents. SwissQual’s liability for any errors
in the documents is limited to the correction of errors and the aforementioned advisory services.
DISCLAIMER: Every effort has been made to ensure the accuracy and completeness in the preparation of this document. However,
should any errors or omissions come to the attention of the user, please contact SwissQual AG. The content of this document is subject
Manual – Call Analysis Description 2/25

SwissQual AG Web: http://www.swissqual.com Support: support@swissqual.com
to change without prior notice due to improvement in product performance or function.

Contents
1. Introduction ............................................................................................................ 5
2. How to Use the Call Analysis Feature ..................................................................... 6
2.1. Settings ........................................................................................................... 6
2.2. Call Analysis Options......................................................................................... 6
2.3. Threshold Values.............................................................................................. 7
2.3.1. Speech Quality............................................................................................... 7
2.3.2. Signal Strength and Quality ............................................................................. 7
2.4. ‘Recalculate’ Button ........................................................................................11
3. Description of the CallAnalysis Table ................................................................... 12
4. Description of the ‘Code’ and ‘CodeDescription’ Fields........................................ 17
4.1. Introduction....................................................................................................17
4.2. Code Description .............................................................................................17
5. Reporting ............................................................................................................... 25
Figures
Fig. 1. Settings Dialog Box ................................................................................................ 6
Fig. 2. The dialog for GSM related thresholds ................................................................... 7
Fig. 3. The dialog for UMTS related thresholds ................................................................. 8
Fig. 4. The dialog for CDMA related thresholds ................................................................. 9
Fig. 5. The dialog for the iDEN receive level threshold ................................................... 10
Fig. 6. The dialog for the IS-136 RxLev threshold .......................................................... 10
Fig. 7. Progress Bar during Call Analysis (only visible if it takes more time) ................. 11
Fig. 8. Call Analysis Report Example ............................................................................... 25
Tables
Tab 1. CallAnalysis Table ................................................................................................. 12
Tab 2. Call Code Description............................................................................................ 17

1. Introduction
This document describes a feature called ‘Call Analysis’ that is implemented in
NQDI as an option. The ‘Call Analysis’ feature consists of different SQL scripts
and a Excel Report. The scripts are used to analyse the call sequence, the radio
coverage and some other parameters of every call. As a result, these scripts will
generate a detailed description of each call sequence to assist users to group the
causes of call problems into more detailed sub-groups. The script considers UMTS
and GSM calls in detail, CDMA calls only with regards of the radio coverage and
other technologies supported by the measurement system only with regards of the
speech quality.
The ‘CallAnalysis’ feature consists of the following parts:

§ a table ‘CallAnalysis’ that contains all the results
§ a stored procedure ‘spCallAnalysis’ that scans one call session to collect
the relevant information. This procedure must run once for every call.
§ a stored procedure ‘spCallAnalysisCode’ that calculates the Call Analysis
Code for all calls. The results are based on the results of the stored
procedure ‘spCallAnalysis’.
§ A graphical user interface to configure the call analysis feature (Menu:
Configuration – Call Analysis)
§ A new Report called ‘CallAnalysis.XLS’ (Reports – Voice –
CallAnalysis)

2. How to Use the Call Analysis Feature
2.1. Settings
Typically, the Call Analysis Scanner should be started after every import
procedure. This will be done automatically if you do the following configuration
(Menu ‘Configuration – Call Analysis’):
Fig. 1. Settings Dialog Box
2.2. Call Analysis Options

Run Call Analysis script automatically after import:
If you check this box, then the Call Analysis Process runs automatically when the
import has finished. This means, that first the stored procedure ‘sqCallAnalysis’
will be started for every call that was newly inserted into the database. Once this
process has finished, the application will run the stored procedure
‘sqCallAnalysisCode’ to calculate the Code and the Code Description.
It is highly recommended to check Run Call Analysis script automatically after

import when the call analysis is used. If the calculation is done after the import it
takes about 10 – 15 seconds for each call.
Once the calls are processed with the procedure ‘sqCallAnalysis’ all relevant data
has been entered into the database (table CallAnalysis) and the recalculation can be
made. With these data the and with respect to the given thresholds (see below) the
code is calculated in the procedure ‘sqCallAnalysisCode’.
Copy the code description to the session comment field:

By checking this option, the code description text is automatically copied to the
comment field of a session. This gives the user the possibility to see the code
description during the analysis of a call.

Copy roaming info to the description field:
By checking this option, the roaming info is automatically added to the description
field of that call.
2.3. Threshold Values

There are two types of threshold values. There are Coverage values for each
technology and the speech quality threshold for all technologies.
2.3.1. Speech Quality

The speech threshold is to set in the MOS scale (1-5). If a speech test yields an LQ
value below the set threshold the call contains a ‘Bad sample’. If the percentage of
bad samples exceeds the threshold set in the dialog the call is a ‘Bad Call’. The
default value for bad sample is 2.5 and the percentage for a bad call is 15%.
2.3.2. Signal Strength and Quality

The calculation of signal strength and quality takes three technology into account
GSM, UMTS and CDMA. All three have different indicators that are evaluated. This
evaluation takes place only if the call is failed or dropped. The signal is not assessed
for completed calls. If the threshold values are exceeded or the measurements fall
below the threshold respectively, the description of the code is enhanced e.g. by
adding ‘High RxQual’ or ‘Low RxLev’.
Fig. 2. The dialog for GSM related thresholds
RxQual Threshold (average of the last 8 RxQualSub values)

If the average of the last 8 RxQualSub values is above the threshold entered into
this field then we are talking about a ‘high RxQual’. Default: 5.0
RxLev Threshold in dBm (average of the last 8 RxLevSub or BCCH RxLev

values)

If the average of the last 8 RxLevSub or BCCH RxLev values is less than the
threshold entered into this field, then we are talking about a ‘Low RxLev’ situation.
Default: -95 dBm.
Fig. 3. The dialog for UMTS related thresholds
BLER Threshold (average of the last 4 BLER values)

If the average of the last 4 BLER values is less than the threshold entered into this
field then we are talking about a ‘high BLERl’. Default: 30.0
Total Ec/Io Threshold in dB (average of the last 8 aggregated Ec/Io

values)
If the average of the last 8 aggregated Ec/Io values is less than the threshold
entered into this field, then we are talking about a ‘Low Total Ec/Io' situation.
Default: -10 dB.
UE Rx Power Threshold in dBm (average of the last 8 UE Rx Power values)

If the average of the last 8 UE Rx Power values is less than the threshold entered
into this field, then we are talking about a ‘Low UE Rx Power’ situation. Default: -
95 dBm.

Fig. 4. The dialog for CDMA related thresholds
FER Threshold (average of the last 4 BLER values)

If the average of the last 4 BLER values is less than the threshold entered into this
field then we are talking about a ‘High FER’. Default: 30.0
Total Ec/Io Threshold in dB (average of the last 8 aggregated Ec/Io

values)
If the average of the last 8 aggregated Ec/Io values is less than the threshold
entered into this field, then we are talking about a ‘Low Total Ec/Io' situation.
Default: -10 dB.
AGC Threshold in dBm (average of the last 8 UE Rx Power values)

If the average of the last 8 UE Rx Power values is less than the threshold entered
into this field, then we are talking about a ‘Low AGC’ situation.
Default: -95 dBm.
The threshold values can be changed at any time. To apply them only push the
recalculation button.

Fig. 5. The dialog for the iDEN receive level threshold
RxLev Threshold in dBm (average of the last 8 UE Rx Power values)

If the average of the last 8 Rx Power values is less than the threshold entered into
this field, then we are talking about a ‘Low iDEN RxLev’ situation.
Default: -95 dBm.
Fig. 6. The dialog for the IS-136 RxLev threshold

RxLev Threshold in dBm (average of the last 8 Rx Power values)
If the average of the last 8 Rx Power values is less than the threshold entered into
this field, then we are talking about a ‘Low IS-136 RxLev’ situation.
Default: -95 dBm.
2.4. ‘Recalculate’ Button

This ‘Recalculate’ Button is used to run to call analysis for all calls that are not
already analysed or to recalculate to new code according to changes made in the
threshold values.
During the refresh, the dialog box shows a progress bar and the button
‘Recalculate’ changes to a ‘Cancel’ button.
Fig. 7. Progress Bar during Call Analysis (only visible if it takes more time)
Please note the following:

1. You cannot start the call analysis process during an import procedure.
2. You cannot terminate the application while a call analysis procedure is
running.
3. You cannot import data while a call analysis procedure is running.
4. You should not create a call analysis report before this process is finished.
5. Scanning a call will take approx 10…15 seconds per call. However, this has
to be done only once (typically after import). If you change threshold
values, there is no need to rescan each call. Therefore it can be that the
‘Recalculate’ procedure is very fast (< 1 second, depending on the
amount of data) or it can take more time (if it is necessary to scan call
data)!

3. Description of the CallAnalysis Table
This chapter contains a description of most of the fields of the table
‘CallAnalysis’. This table contains one row per call session. Most of the parameters
are calculated and refreshed by running the stored procedure ‘sqCallAnalysis’.
The fields ‘Code’ and ‘CodeDescription’ are calculated by the stored procedure
‘sqCallAnalysisCode’
Tab 1. CallAnalysis Table
Fieldname Type Description

sessionId int Link to Sessions.sessionId
FileId int Link to FileList.FileId
NetworkId int Link to NetworkInfo.NetworkId
PosId int Link to Positions.PosId
callType Varchar(5) M->L or L->M
callDir Varchar(5) A->B or B-> A
callStatus Varchar(50) ‘Completed’, ‘Failed’, ‘Dropped’ or ‘System Release’
setupTime real Time between ‘Dial’ and ‘Connect’ taken from
CallSession.SetupTime
callCause Varchar(300) Last received Cause value from CC:DISCONNECT
message. Value taken from CallSession.CallCause
callTerminationType Varchar(100) Call termination code based on Seven.Five Statue
machine. Taken from Callsession.CallTermination
valid smallint Flag indicating if this session is valid or not
retryTerminationType Varchar(100) Unused
technology varchar (50) Technolog(ies) used in the call
band varchar (50) Frequency band
Roaming varchar (50) ‘Yes’ for roaming ‘No’ for not roaming
NetIds int Number of different NetIDs in that session
callDuration int Time between ‘Dial’ and Call end. Value taken from
table ‘Markers’ where we calculate the difference
between the ‘Dial’ Event and the ‘CallTerminated’
Event
callStartTimeStamp datetime Time stamp of the ‘Dial’ Event
callEndTimeStamp datetime Time stamp of the ‘CallTerminated’ Event
EndTechnology varchar (50) Technology at the end of the call
Layer3Messages int 0 for no layer 3 messages in entire session 1 for at
least on message
SgnChnReq datetime Timestamp of the first Channel Request
SgnChnAss datetime Timestamp of the first IMM_ASS message
alertTimeStamp datetime Timestamp of the first Alert message
connAckTimeStamp datetime Timestamp of the first CONN_ACK message
callSetupEndTimeStamp dateTime Timestamp indicating the end of a call set up. It is
either the timestamp of the CON_ACK message in
successful case or the timestamp of the call
termination an unsuccessful case
CallDisconnectTimeStamp datetime Timestamp of the time when the call is disconnected
StartTechnology varchar (50) Technology at the beginning of the call
avgRxQual real Average RxQualSub of the last 8 Layer1 messages
before the end of the call

avgRxLev real Average RxLevSub of the last 8 Layer1 messages
avgTA real Average TA of the last 8 Layer1 messages before the
end of the call
avgMsTxPwr real Average TxPwr of the last 8 Layer1 messages before
the end of the call
AvgBCCHRxLev real Average BCCH_RxLev of the last 8 Layer1 messages
before the end the call
numOfRadioValues int Number of averaged values. Equal or less than 8.
LastRadioTimeStamp datetime Timestamp of the last Layer1 message in this session
avgScanRxLev real Unused
numOfScanValues real Unused
lastScanTimeStamp datetime Unused
numBetterNeighbors int Number of Neighbours with stronger BCCH
numBetterScannedGSM int Number of better scanned channels
NumUlSamples Int Number of Uplink voice samples in this session
NumDlSamples Int Number of Downlink voice samples in this session
NumBadSamples Int Number of Samples below bad call threshold
percentage Real Percentage of bad samples in a call to qualify for a
bad call
badcall Varchar 10 ‘Yes’ for bad call ‘No’ for not bad call
avgLQ Real Average LQ
numBetterNeighbors, int
numChnReq int Number of Channel Requests in this session. Here we
only count these messages where we found an
IMM_ASS message with a corresponding random
code!
numCMServiceRequest int Number of CMServiceRequests in this session
numCMServiceReject int Number of CMServiceRejects in this session
numpageResponse int Number of Paging Responses in this session
numImmASS int Number of IMM_ASS in this session
numImmAssRej int Number of IMM_ASS_REJ in this session
numSetup int Number of SETUP in this session
numCallProceding int Number of Call Proceeding in this session
numAssCmd int Number of ASS_CMD in this session
numAssCmpl int Number of ASS_CMPL in this session
numAssFail int Number of ASS_FAIL in this session
numProgress int Number of PROGRESS in this session
numAlerting int Number of ALERTING in this session
numConn int Number of CONNECT in this session
numConnAck int Number of CONN_ACK in this session
numChnRelCallSetup int Number of Channel Releases for the call setup in this
session
numLURequest int Number of LU Request in this session
numLUAccept int Number of LU Accept in this session
numLUReject int Number of LU Reject in this session
numDisconnect int Number of DISCONNECT in this session
numRelease int Number of RELEASE in this session
numRelCmpl int Number of REL_CMPL in this session
numChnRel int Number of Channel Release in this session
numDCCH2GTrial int Number of KPI 15700 measurements
numDCCH2GSuccess int Number of successful KPI 15700 measurements
numTCHTrial int Number of KPI 15600 / 15800 measurements

numTCHSuccess int Number of successful KPI 15600 / 15800
measurements
LastHoTimeStamp datetime Timestamp of the last Handover before session end
LastHoType Varchar Type of the last Handover before end of the session
(ASS_CMD, ASS_CMPL, ASS_FAIL, HO_CMD,
HO_CMPL, HO_FAIL)
LastHoCause Varchar RR Cause value of the Last HO
avgRLT real Unused
numOfRLTValues int Unused
LastRLTTimeStamp datetime Unused
configCall tinyint Indicates if this was a configuration call (to start or to
stop a scenario)
NumReestablishmentRequests tinyint Number of Call Reestablishment Requests
disconDirection Direction of the DISCON message (U=Uplink,
D=Downlink)
disconClass Class value of the Disconnect message
disconCause Varchar Cause value of the Disconnect message
disconLocation Location value of the Disconnect message
code Varchar(255) See Chapter ‘CallAnalysis Code’
noL3Duration Indicates for how many seconds there were no layer3
messages received from the mobile station (in 10 sec
steps)
codeDescription Varchar See Chapter ‘CallAnalysis Code’
NoService Smallint Indicates the number of occurrences of situations
where the mobile reported to be in SCAN mode,
means out of service
Initializing smallint
LastAssTimeStamp datetime Timestamp of the last ASSIGNMENT message
(ASS_CMD, ASS_CMPL, ASS_FAIL)
LastAssMsg Varchar Type of the last ASSIGNMENT message (ASS_CMD,
ASS_CMPL, ASS_FAIL)
LastAssCause Varchar Cause value of the last ASSIGNMENT message
CRRandomCode Char(2) Random code of the IMM_ASS message that
corresponds to the Random code of the Channel
Request message
RRCConnReqTimeStamp datetime Number of Connection Request by UMTS
RRCConnSetupTimeStamp datetime Number of Connection Setup by UMTS
numMMTrial int Number of completed Connection Setup by UMTS
numMMSuccess int Number of Radio Bearer Setup
avgBLER Real Average BLER of the last 4 messages before the end
the call
avgTotEcIo real Average aggregated Ec/Io of the last 8 messages
avgUETxPwr real Average UE TxPower of the last 8 messages before
the end the call
avgUERxPwr real Average UE RxPower of the last 8 messages before
the end the call
numOfWCDMARadioValues int Number of WCDMAAGC values used
LastWCDMARadioTimeStamp datetime Timestamp of the last WCDMAAGC message used
numBetterMonitored int Unused
numBetterDetected int Unused
numBetterScannedUMTS int Unused
numRRCConnReq int Unused

numUMTSpageResponse int Unused
numRRCConnSetup int Number of RRC Connection Setup messages in the
call
numRRCConnRej int Number of RRC Connection Reject messages in the
call
numRBSetup int Number of Radio Bearer Setup messages in the call
numRBSetupCompl int Number of Radio Bearer Setup Complete messages in
the call
numRBSetupFail int Number of Radio Bearer Setup Failure messages in
the call
numRRCConnRelCallSetup Int Unused
numRRCConnRel int Number of RRC Connection Release messages in the
call
numDCCH3GTrial int Number of KPI 16000 measurements
numDCCH3GSuccess int Number of successful KPI 16000 measurements
numRABTrial Int Unused
numRABSuccess Int unused
LastUMTSHoTimeStamp datetime Timestamp of last IRAT Handover
LastUMTSHoType varchar(100) Type of last IRAT Handover
LastUMTSCause Varchar(100) Unused
numGMMMessages Int Number of GMM messages in the call
Int Number of SMS messages in the call
numSMSMessages
numMMMessages int Number of MM messages in the call
RLCexp int 1 if RLC expired in call 0 if not
avgCDMAFER real Average FER of the last 2 messages before the end
the call
avgCDMATotEcIo real Average aggregated Ec/Io of the last 8 messages
avgCDMATxPwr real Average TxPower of the last 8 messages before the
end the call
avgCDMAAGC real Average AGC of the last 8 messages before the end
the call
numOfCDMARadioValues int Number of FingerInfo values used
LastCDMARadioTimeStamp datetime Timestamp of the last FingerInfo message
numCDMAOriginationMsg int Number of Origination messages in the call
numCDMAPageResponse int Number of Page Response messages in the call
numCDMAServiceConnect int Number of Service Connect messages in the call
numCDMAServiceConnectCmpl int Number of Service Connect Complete messages in the
call
numCDMAChnAssMsg int Number of Channel Assignment Messages in the call
numCDMAInitState int Unused
numCDMAOriginationState int Unused
numCDMAPageResponseState int Unused
numCDMARegistrationState int Unused
numCDMAAuthenticationState int Unused
numCDMAWaitForOrderState int Unused
numCDMAWaitForAnswerState int Unused
numCDMAConversationState int Unsued
numCDMAReleaseOrder int Number of Release Order messages in the call
avgTDMABER real Average BER of the last 8 layer 1messages before the
end the call
avgTDMARxLev real Average RxLev of the last 8 MsgIS136Report
messages before the end the call

avgTDMATxLev real Average TxLev of the last 8 MsgIS136Report
messages before the end the call
avgTDMATA real Average TA of the last 8 MsgIS136Report messages
numOfTDMARadioValues int Number of MsgIS136Report values used
LastTDMARadioTimeStamp datetime Timestamp of the last MsgIS136Report message
numTDMAOriginationMsg int unused
numTDMADigitalTrafficDesignation int unused
avgiDENRRSSI real Average RxLev of the last 8 MobileStatus messages
numOfiDENRadioValues int Number of MobileStatus values used
LastiDENRadioTimeStamp datetime Timestamp of the last MobileStatus message
numiDENTchRequest int unused
numiDENTchAllocation int unused
FailedRegistration Int 1 if there was an unsuccessful registration in UMTS

4. Description of the ‘Code’ and ‘CodeDescription’
Fields
4.1. Introduction
Based on the values in the callAnalysis table, there are two fields that are
calculated later: the call analysis code and the call analysis code description.
The code and the code description are calculated by running the stored procedure
‘sqCallAnalysisCode’. The code field is expressed as a string like ‘C3.01’
whereas:
‘C’ = Shortcut for ‘Code’

first number = indication of call status
(1 = Completed, 2 = Dropped, 3 = Failed, 9 = others)
second number = Subcode describing more details
4.2. Code Description

The codeDescription files decode the Code files into Text. Following a table as a
summary of all codes we support in release 9.0:
Tab 2. Call Code Description
Priority Code CodeDescription Description

Configuration calls are call made to configure,
start or stop a scenario. These calls are not
taken into account.
C0.00 Config Call This was a configuration call. Either to
start or to terminate a scenario.
Completed Calls. The criterions for a completed
call are: successful call setup and successful
termination of the call
C1.00 Completed, (Disconnect Cause value) Normal completed call
C1.10 Completed, Bad Call (Disconnect Cause value) Normal completed call with a
percentage of bad samples above the
threshold
C1.11 Completed, Bad Samples (Disconnect Cause Normal completed call with at least
value) one bad sample (l.LQ <
@BadSampleThreshold)
C1.99 Completed, others All other completed calls
Dropped Calls. The criterions for Dropped calls
are: not completed calls and successful call
setup and unsuccessful call termination
C2.00 Dropped, bad coverage - HO_CMPL Dropped Call in bad coverage area
but successful Handovers detected.
(avgRxLev <= @poorRxLev OR
avgBCCHRxLev <= @poorRxLev )
C2.02 Dropped, Call Re-established Dropped but successful reestablished
(disconDirection = 'U' and
NumReestablishmentRequests
> 0)
C2.03 Dropped, Call Reestablishment attempt Dropped and Call reestablishment
attmept
(NumReestablishmentRequests > 0)
C2.05 Dropped, No Service/Scanning Dropped call where at least one time
No Service or Scanning occurred
(NoService > 0 or Initializing > 0)
C2.06 Dropped, Only Successful Handover Dropped call where the last Handover
was successful (lastHoType =
‘HO_CMPL’)
C2.07 Dropped, No Handover Dropped call where no Handover
occurred (lastHoType <> 'HO_FAIL'
AND lastHoType <> 'HO_CMPL' AND
lastHoType <> 'HO_CMD')
C2.10 Dropped, Disconnect sent (Disconnect Cause Dropped call and disconnect sent by
value) called party
(disconDirection = 'U' and
callDir = 'B->A')
C2.11 Dropped, Disconnect received (Disconnect Dropped call and disconnect received
Cause value) (disconDirection = 'D' )
C2.12 Dropped, Disconnect sent by calling party Dropped call and disconnect received
(Disconnect Cause value) (disconDirection = 'U' and
callDir = 'A->B')
C2.20 Dropped, Channel Release received Dropped call and Channel Release
received
(numChnRel > 0)
C2.21 Dropped, RRCConnectionRelease received Dropped call call and RRCConnection
Release received
(numRRCConnRel > 0 )
C2.30 Dropped, Failed Handover (causeValue) Dropped call with last Handover failed
(lastHoType = 'HO_FAIL')
C2.31 Dropped, Handover uncompleted Dropped call with last Handover
uncompleted (lastHoType =
'HO_CMD')
C2.32 Dropped, Failed Assignment (causeValue) Dropped call with last Assignment
failed (lastHoType = 'ASS_FAIL')
C2.33 Dropped, Assignment uncompleted Dropped calls with uncompleted
Assignment (lastHoType =
'ASS_CMD')
C2.34 Dropped, Failed IRAT-Handover Dropped call with failed IRAT
Handover (lastUMTSHoType =
'HO_IRAT_FAIL')
C2.40 Dropped, Radio Link Timeout Dropped call with Radio Link Timeout
(RLCExp > 0) (This comment can be
added to other descriptions without
applying the code)
C2.41 Dropped, High RxQual Dropped call with average of the last
8 RxQual messages over threshold
(avgRxQual >= @poorRxQual) (This
comment can be added to other
descriptions without applying the
code)
C2.42 Dropped, Low RxLev Dropped call with average of the last
8 RxLev messages below threshold
avgBCCHRxLev <= @poorRxLev)
(This comment can be added to other
code)
C2.43 Dropped, High BLER' Dropped call with average of the last
4 BLERmessages above threshold
(avgBLER >= @BLERThreshold) (This
code)
C2.44 Dropped, Low Total Ec/Io Dropped call with average of the last
8 aggregated Ec/Io messages below
threshold (avgTotEcIo <=
@UEEcIoThreshold) (This comment
can be added to other descriptions
without applying the code)
C2.45 Dropped, Low UE Rx Power Dropped call with average of the last
8 UE RxPower messages below
threshold (avgUERxPwr <=
@UERxLevThreshold) (This comment
C2.46 Dropped, High FER Dropped call with average of the last
2 FER messages above threshold
(avgCDMAFER <=
@CDMAFERThreshold) (This comment
C2.47 Dropped, Low Total Ec/Io Dropped call with average of the last
8 aggregated Ec/Io messages below
threshold (avgCDMATotEcIo <=
@CDMAECIOThreshold) (This
code)
C2.48 Dropped, Low AGC Dropped call with average of the last
8 AGC messages below threshold
(avgCDMAAGC <=
@CDMAAGCThreshold) (This
code)
C2.49 Dropped, Low IS-136 RxLev Dropped call with average of the last
(avgTDMARxLev <=
@TDMARxLevThreshold) (This
code)
C2.50 Dropped, Low iDEN RxLev Dropped call with average of the last
(avgiDENRRSSI <=
@iDENRxLevThreshold) (This
code)
C2.98 Dropped, Layer 3 Gaps/ No Layer3 Messages Dropped call with no or missing Layer
3 Messages (Layer3Messages = 0 or
noL3Duration <= @noL3Duration)
C2.99 Dropped, Others All other dropped calls
Failed calls. The criterions for failed calls are:
not completed calls and not dropped calls and
dial command sent to the device (mobile or
fixed device)
C3.00 Failed, Scanning Failed call with phone sending at least
once the message ‘scanning’
(Initializing > 0) and there was no
progress detected
C3.01 Failed, No Service Failed call where the no service
message occured (NoService > 0)
C3.10 Failed, Disconnect sent by Called Party Failed call with Disconnect sent by
(Disconnect Cause value) called party (disconDirection = 'U' and
callDir <> 'A->B')
C3.11 Failed, B-Side not reached (Disconnect Cause Failed call where call was connected
value) to wrong party (numconn > 0)
C3.12 Failed, No Answer (Disconnect Cause value) Failed call where disconnect was after
the alering (numAlerting > 0)
C3.13 Failed, Disconnect sent after Progress Failed call where disconnect was after
(Disconnect Cause value) progress (numProgess > 0)
C3.14 Failed, Disconnect sent by Calling Party Failed call where disconnect was sent
(Disconnect Cause value) by calling party (Dial Timeout)
C3.15 Failed, Disconnect received by Called Party Failed call where disconnect was
after Alerting (Disconnect Cause value) received by called party after Alerting
(callDir <> 'A->B' and numAlerting >
0)(Dial Timeout)
C3.16 Failed, Disconnect received by Called Party Failed call where disconnect was
(Disconnect Cause value) received by called party (callDir <>
'A->B')(Dial Timeout)
C3.17 Failed, Disconnect received by Calling Party Failed call where disconnect was
after Alerting (Disconnect Cause value) received by calling party after Alerting
(numAlerting > 0)
C3.18 Failed, Disconnect received by Calling Party Failed call where disconnect was
(Disconnect Cause value) received by calling party (NumAlerting
= 0)
C3.19 Failed, Disconnect not determined (Disconnect Failed call where is not closer
Cause value) determined (numDisconnect > 0)
C3.20 Failed, Service Reject Failed call where service was rejected
and the connection released
(numCMServiceReject > 0)
C3.21 Failed, Release after Alerting Failed call where a release occurred
after alering (numAlerting > 0)
C3.22 Failed, Release after Progress Failed call where a release occurred
after progress (numProgress > 0)
C3.23 Failed, Release after Service Request Failed call where a release occurred
after page response
(numCMServiceRequest > 0)
C3.24 Failed, Release after Page Response Failed call where a release occurred

after service request
(numPageResponse > 0)
C3.25 Failed, Release Received by Calling Party Failed call where a the calling party
received a release before any
progress
C3.26 Failed, Release Received by Called Party Failed call where a the called party
received a release before any
progress (callDir <> 'A->B')
C3.30 Failed, No Progress after Alerting Failed call where there was no
progress after alerting (numAlerting >
0)
C3.31 Failed, Stop with Progress Failed call where there was no
progress after progress (numProgress
> 0)
C3.32 Failed, No Progress after TCH assignment Failed call where there was no
progress after TCH assignment
(numTCHSuccess > 0 or
numRABSuccess > 0)
C3.33 Failed, No Progress after Call Failed call where there was no
Confirmed/Proceeding progress after Confirmed/Proceeding
(numCallProceding > 0)
C3.34 Failed, No Progress after Setup Failed call where there was no
progress after Setup (numSetup > 0)
C3.35 Failed, No Progress after Service Request/Page Failed call where there was no
Response progress after Service Request/Page
Response (numPageResponse +
numCMServiceRequest) > 0
C3.36 Failed, No Service Request/Page Response Failed call where there was no Service
Request/Page Response
(numPageResponse +
numCMServiceRequest) = 0
C3.37 Failed, No Progress after DCCH assignment Failed call where there was no
progress after DCCH assignment
((numDCCH2GSuccess > 0 or
numDCCH3GSuccess > 0) or
(numImmAss > 0))
C3.38 Failed, No IMM_ASS for this Random Code Failed call where there was no
immediate assignment was found for
the random code in the channel
request (CRRandomCode = '' AND
numChnReq > 0 )
C3.39 Failed, No DCCH Request Failed call where there was no DCCH
request of the calling party was
detected (numDCCH2GTrial = 0 or
numDCCH3GTrial = 0) and
NumImmAss = 0 and Technology in
('GSM','UMTS','GSM /UMTS') and
callDir = 'A->B')
C3.40 Failed, Radio Link Timeout Failed call where a Radio Link
Timeout occured
C3.41 Failed, TCH assignment Failed Failed call where the TCH assignment
failed (numTCHTrial> 0 or
numRABTrial > 0)
C3.42 Failed, Service Reject Failed call where service was rejected
and the connection not released
(numCMServiceReject > 0)
C3.43 Failed, DCCH Failed / Rejected Failed call where the DCCH
assignment failed or was rejected
(numDCCH2GTrial> 0 or
numDCCH3GTrial > 0)
C3.44 Failed, Registration failed Failed call where an Registration
attempt failed (FailedRegistration >
0)
C3.50 Failed, No Setup -> Location Updating Failed call where there is no call set
up trial is detected but a Location
Updating Process is found
(NumLuRequest + numLuAccept +
NumLuReject) > 0)
C3.51 Failed, No Setup -> RA Updating Failed call where there is no call set
up trial is detected but a Routing Area
Updating Process is found
(NumGMMmessages > 0)
C3.52 Failed, No Setup -> SMS Failed call where there is no call set
up trial is detected but a SMS process
is found (NumSMSmessages > 0)
C3.53 Failed, Called Party was active Failed B-> A call where the called
mobile was in other activities
((numGMMMessages +
numMMMessages +
numSMSMessages) > 0 or
(NumLuRequest + numLuAccept +
NumLuReject) > 0 )
C3.54 Failed, Called Party not reached Failed B-> A call where the mobile did
not react
C3.60 Failed, No Progress after Service Connect Failed call where there was no
Complete progress after Service Connect
Complete
(numCDMAServiceConnectCmpl) > 0)
C3.61 Failed, No Service Connect Failed call where there was Service
Connect message
((numCDMAServiceConnect) =0 and
(numCDMAPageResponse +
numCDMAOriginationMsg) > 0)
C3.62 Failed, No Progress after CDMA Origination Failed call where there was no
/Page Response progress after sending the Origination
or Page Response message
((numCDMAPageResponse +
numCDMAOriginationMsg) > 0)
C3.63 Failed, No Origination /Page Response Failed call where there was no
Origination or Page Response
message ((numCDMAPageResponse
+ numCDMAOriginationMsg) = 0)
Scanning Failed call with phone sending at least
once the message ‘scanning’
(Initializing > 0) (This comment is
applying any code)
High RxQual Failed call with average of the last 8
RxQual messages over threshold
(avgRxQual >= @poorRxQual) (This
comment is added to other
descriptions without applying any
code)
Low RxLev Failed call with average of the last 8
RxLev messages below threshold
avgBCCHRxLev <= @poorRxLev)
(This comment is added to other
code)
High BLER' Failed call with average of the last 4
BLERmessages above threshold
(avgBLER >= @BLERThreshold) (This
code)
Low Total Ec/Io Failed call with average of the last 8
aggregated Ec/Io messages below
threshold (avgTotEcIo <=
@UEEcIoThreshold) (This comment is
applying any code)
Low UE Rx Power Failed call with average of the last 8
UE RxPower messages below
threshold (avgUERxPwr <=
@UERxLevThreshold) (This comment
is added to other descriptions without
applying any code)
High FER Failed call with average of the last 2
FER messages above threshold
(avgCDMAFER <=
@CDMAFERThreshold) (This comment
is added to other descriptions without
applying any code)
Low Total Ec/Io Failed call with average of the last 8
aggregated Ec/Io messages below
threshold (avgCDMATotEcIo <=
@CDMAECIOThreshold) (This
code)
Low AGC Failed call with average of the last 8
AGC messages below threshold
(avgCDMAAGC <=
@CDMAAGCThreshold) (This
code)
Low IS-136 RxLev Failed call with average of the last 8
(avgTDMARxLev <=
@TDMARxLevThreshold) (This
code)
Low iDEN RxLev Failed call with average of the last 8
(avgiDENRRSSI <=
@iDENRxLevThreshold) (This
code)
Calling Party: (CallCause) Failed call where the calling party
determined a particular call cause
(callDir = 'B->A') (This comment is
applying any code)
C3.98 Failed, No Layer 3 Messages/ Layer3 Gaps Failed call with no or missing Layer 3
Messages (Layer3Messages = 0 or
noL3Duration <= @noL3Duration)
C3.99 Failed, others All other failed calls

5. Reporting
Once the call analysis process is finished, you can create a more detailed report by
selecting the report ‘Voice – CallAnalysis’. This will create an excel report where
all calls are grouped by Operator, Call Status and Code Description. The field
Technology can be applied to distinguish between different Technologies.
Fig. 8. Call Analysis Report Example


Manual - Call Analysis Description

Diunggah oleh

Informasi Dokumen

Deskripsi Asli:

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

Manual - Call Analysis Description

Diunggah oleh

Hak Cipta:

Format Tersedia

Seven.

Version Date Comment

Manual – Call Analysis Description 2/25

Manual – Call Analysis Description 3/25

Manual – Call Analysis Description 4/25

The ‘CallAnalysis’ feature consists of the following parts:

Manual – Call Analysis Description 5/25

Fig. 1. Settings Dialog Box

2.2. Call Analysis Options

It is highly recommended to check Run Call Analysis script automatically after

Copy the code description to the session comment field:

Manual – Call Analysis Description 6/25

2.3. Threshold Values

2.3.1. Speech Quality

2.3.2. Signal Strength and Quality

Fig. 2. The dialog for GSM related thresholds

RxQual Threshold (average of the last 8 RxQualSub values)

RxLev Threshold in dBm (average of the last 8 RxLevSub or BCCH RxLev

Manual – Call Analysis Description 7/25

Fig. 3. The dialog for UMTS related thresholds

BLER Threshold (average of the last 4 BLER values)

Total Ec/Io Threshold in dB (average of the last 8 aggregated Ec/Io

UE Rx Power Threshold in dBm (average of the last 8 UE Rx Power values)

Manual – Call Analysis Description 8/25

FER Threshold (average of the last 4 BLER values)

Total Ec/Io Threshold in dB (average of the last 8 aggregated Ec/Io

AGC Threshold in dBm (average of the last 8 UE Rx Power values)

Manual – Call Analysis Description 9/25

RxLev Threshold in dBm (average of the last 8 UE Rx Power values)

Fig. 6. The dialog for the IS-136 RxLev threshold

Manual – Call Analysis Description 10/25

2.4. ‘Recalculate’ Button

Please note the following:

Manual – Call Analysis Description 11/25

Tab 1. CallAnalysis Table

Fieldname Type Description

Manual – Call Analysis Description 12/25

Manual – Call Analysis Description 13/25

Manual – Call Analysis Description 14/25

Manual – Call Analysis Description 15/25

Manual – Call Analysis Description 16/25

‘C’ = Shortcut for ‘Code’

4.2. Code Description

Tab 2. Call Code Description

Priority Code CodeDescription Description

Manual – Call Analysis Description 20/25

Manual – Call Analysis Description 24/25

Fig. 8. Call Analysis Report Example

Manual – Call Analysis Description 25/25

Anda mungkin juga menyukai