-
ZXC10 BSSBCDMA Base Station System
Call Failure Reason and Call Drop Explanation (1X)
Version 8.0.1.9
ZTE CORPORATION ZTE Plaza, Keji Road South, Hi-Tech Industrial
Park, Nanshan District, Shenzhen, P. R. China 518057 Tel: (86) 755
26771900 800-9830-9830 Fax: (86) 755 26772236 URL:
http://support.zte.com.cn E-mail: [email protected]
-
LEGAL INFORMATION Copyright 2006 ZTE CORPORATION. The contents
of this document are protected by copyright laws and international
treaties. Any reproduction or distribution of this document or any
portion of this document, in any form by any means, without the
prior written consent of ZTE CORPORATION is prohibited.
Additionally, the contents of this document are protected by
contractual confidentiality obligations. All company, brand and
product names are trade or service marks, or registered trade or
service marks, of ZTE CORPORATION or of their respective owners.
This document is provided as is, and all express, implied, or
statutory warranties, representations or conditions are disclaimed,
including without limitation any implied warranty of
merchantability, fitness for a particular purpose, title or
non-infringement. ZTE CORPORATION and its licensors shall not be
liable for damages resulting from the use of or reliance on the
information contained herein. ZTE CORPORATION or its licensors may
have current or pending intellectual property rights or
applications covering the subject matter of this document. Except
as expressly provided in any written license between ZTE
CORPORATION and its licensee, the user of this document shall not
acquire any license to the subject matter herein. The contents of
this document and all policies of ZTE CORPORATION, including
without limitation policies related to support or training are
subject to change without notice.
Revision History
Date Revision No. Serial No. Reason for Revision
06/14/2007 R1.0 sjzl20071307 First edition
-
ZTE CORPORATION Values Your Comments & Suggestions! Your
opinion is of great value and will help us improve the quality of
our product documentation and offer better services to our
customers.
Please fax to: (86) 755-26772236; or mail to Documentation
R&D Department, ZTE CORPORATION, ZTE Plaza, A Wing, Keji Road
South, Hi-Tech Industrial Park, Shenzhen, P. R. China 518057.
Thank you for your cooperation!
Document Name ZXC10 BSSB (V8.0.1.9) Call Failure Reason and Call
Drop Explanation (1x)
Product Version V8.0.1.9 Document Revision Number R1.0
Equipment Installation Date
Presentation: (Introductions, Procedures, Illustrations,
Completeness, Level of Detail, Organization, Appearance)
Good Fair Average Poor Bad N/A
Accessibility: (Contents, Index, Headings, Numbering,
Glossary)
Good Fair Average Poor Bad N/A
Your evaluation of this documentation
Intelligibility: (Language, Vocabulary, Readability &
Clarity, Technical Accuracy, Content)
Good Fair Average Poor Bad N/A
Your suggestions for improvement of this documentation
Please check the suggestions which you feel can improve this
documentation: Improve the overview/introduction Make it more
concise/brief Improve the Contents Add more step-by-step
procedures/tutorials Improve the organization Add more
troubleshooting information Include more figures Make it less
technical Add more examples Add more/better quick reference aids
Add more detail Improve the index Other suggestions
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
# Please feel free to write any comments on an attached
sheet.
If you wish to be contacted regarding your comments, please
complete the following:
Name Company
Postcode Address
Telephone E-mail
-
This page is intentionally blank.
-
Contents
About this
Manual.............................................................
i
Purpose................................................................................
i Intended Audience
................................................................. i
Prerequisite Skill and Knowledge
.............................................. i What is in This
Manual............................................................
i Related
Documentation..........................................................
ii
Conventions.........................................................................
ii How to Get in
Touch.............................................................
iii
Chapter
1..........................................................................1
BSSAP Related Failures
...................................................1
ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_Unspecified...1
ERR_SPS_RLSA_BSSAP_TE_T3230
..........................................2
ERR_SPS_RLSA_BSSAP_TE_Tassignment
.................................2
ERR_SPS_RLSA_BSSAP_FchSetup_RcvSccpDisconnect ...............3
ERR_SPS_RLSA_BSSAP_FchSetup_RcvMSReleaseOrder..............4
ERR_SPS_RLSA_BSSAP_TE_Tfchsetup
.....................................4
ERR_SPS_RLSA_BSSAP_TE_T303............................................5
ERR_SPS_RLSA_BSSAP_TE_Txxp
............................................5
ERR_SPS_RLSA_BSSAP_DB_GetBoardOrIndexNetAddrByLogicAddr..........................................................................................6
ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_UserBusy......6
ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_NormalClearing..........................................................................................7
ERR_SPS_RLSA_BSSAP_ByteIndex_IndexInUsed.......................7
ERR_SPS_RLSA_BSSAP_FchSetup_AllLegFail
............................8
ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_NoAnswer.....9
ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvOrgnInSessionState.......9
ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvRegInAssignState_Others........................................................................................
10 ERR_SPS_RLSA_BSSAP_HandShake_TimeOut......................... 10
ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvRegInAssignState_PowerOn
......................................................................................
11
-
ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvRegInAssignState_PowerDown...................................................................................11
ERR_SPS_RLSA_BSSAP_TgtBSC_FunCallFail__TargetBSCHandlerEntry__A7HOReqMsgProccessForHOWith1X
..............................12
ERR_SPS_RLSA_BSSAP_Other_ReceiveResetCircuit..................12
ERR_SPS_RLSA_BSSAP_FchSetup_SendChannelAssignment_AllBtsFail
...................................................................................13
ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_HandoffSuccessful
...................................................................................14
ERR_SPS_RLSA_BSSAP_TgtBSC_Other__TargetBSCHandler_A7fHandoffRequestProccess__RecievedA7HOReqWhenSemiHO...........14
ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_SemiConcurrentService
.............................................................................15
ERR_SPS_RLSA_BSSAP_MsgPara_Origination_InvalidServiceOption
......................................................................................15
ERR_SPS_RLSA_BSSAP_HashOpr_AddItem_SccpId2CallRef ......16
ERR_SPS_RLSA_BSSAP_Other_Get97DMTMsParaFail................16
ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_EquipmentFailure
.....................................................................................17
ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_AuthenticationFailure
...............................................................................17
Chapter
2........................................................................19
DSPM Related
Failures...................................................19
ERR_SPS_RLSA_DSPM_CLH_OtherReason_MSNormalRelease ....19
ERR_SPS_RLSA_DSPM_CLH_TimerExpired_Twaitorder .............20
ERR_SPS_RLSA_DSPM_CLH_OtherReason_SNFailure................21
ERR_SPS_RLSA_DSPM_CLH_OtherReason_MSPowerDown ........21
ERR_SPS_RLSA_DSPM_CLH_TimerExpired_Tpcfinfol3...............22
ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnUmrSCHRequestMsg_ReleasebyMSDTXTime
..............................................23
ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnAbarSCHRemoveIndication_RSCHReleasebySDMDTXTime............................23
ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHPNDropIndication_ReleasebyHOH.................................................................24
ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnAbisdrBurstRelease_RSCHExistedCellReleasebyRCM
...................................24
ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHRelease_ReleasebyCLH..............................................................................25
ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnAbarSCHRemoveIndication_RSCHReleasebySDMOtherReason
......................25
ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnAbarSCHRemoveIndication_FSCHReleasebySDMDuration.............................26
ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHFSCHHandoff_HardHandoff
.........................................................................26
-
ERR_SPS_RLSA_DSPM_SCHH_TimerExpired_Tfschdrop ............ 27
ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnTfschdroppending_ReleasebyTDropPending
............................................... 27
ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnAbisdrBurstRelease_FSCHExistedCellReleasebyRCM
................................... 28
ERR_SPS_RLSA_DSPM_CLH_OtherReason_PCFEquipmentFailure28
ERR_SPS_RLSA_DSPM_CLH_OtherReason_MSGoingIntoDormant........................................................................................
29 ERR_SPS_RLSA_DSPM_CLH_OtherReason_PCFNormalRelease... 29
ERR_SPS_RLSA_DSPM_HOH_TimerExpired_SoftHOThocompletion........................................................................................
30 ERR_SPS_RLSA_DSPM_HOH_TimerExpired_Thoreq ................. 31
ERR_SPS_RLSA_DSPM_HOH_ResNotSatisfied_HOHOnUmrCFSearchReport
.............................................................................
32 ERR_SPS_RLSA_DSPM_HOH_OtherReason_AbisdHandShakeFailure
......................................................................................
32 ERR_SPS_RLSA_DSPM_SCHH_TimerExpired_Tfschbstreq.......... 33
ERR_SPS_RLSA_DSPM_CLH_OtherReason_PDSNDenied_Reason_Unspecified
..........................................................................
34 ERR_SPS_RLSA_DSPM_CLH_OtherReason_OVERLOAD ............. 34
ERR_SPS_RLSA_DSPM_CLH_OtherReason_Ta8setup................ 35
ERR_SPS_RLSA_DSPM_CLH_OtherReason_Tshakehandrecv ...... 35
ERR_SPS_RLSA_DSPM_HOH_TimerExpired_SemiSoftHOThocompletion...................................................................................
36 ERR_SPS_RLSA_DSPM_HOH_ResNotSatisfied_HOHOnA7rHOReqAck
......................................................................................
37
ERR_SPS_RLSA_DSPM_CLH_OtherReason_PDSNDenied_Reason_Administratively_Pohibited
..................................................... 38
ERR_SPS_RLSA_DSPM_CLH_OtherReason_PCFDenied_PDSN_Resource_Unavailable
................................................................ 38
ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHReleaseRSCHbyLegFail_ReleaseRschExistSDMLegFailure.................................
39
ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnUmrSCHRequestMsg_FCHNotExisted
........................................................ 39
Chapter
3........................................................................41
SDM Related
Failures.....................................................41
SDM_Activate_Fail_AcquirePreambleFail_Normal
..................... 41
SDM_Activate_Fail_AcquirePreambleFail_NoRevFrm................. 42
SDM_Find_Fail_WaitConfigVTCTimeout
.................................. 43
SDM_Link_Fail_RevNoFrm....................................................
44 SDM_Link_Fail_RevTooManyBadFrm
...................................... 44 SDM_Link_Fail_FwdA2pNoFrm
.............................................. 45
SDM_Find_Fail_WaitConfigRLPTimeout...................................
45
-
SDM_Link_Fail_RSCHLegLinkFail
...........................................46
SDM_Link_Fail_FwdA2pTooManyErrEncodeFrm ........................46
SDM_Activate_Fail_InitVocoderFail
........................................47
SDM_OprVocoder_Fail_WaitStartVocoderCodingAckTimeOut......47
SDM_Find_Fail_NoFCHLeg
....................................................48
SDM_Activate_Fail_MsgParaFail.............................................48
Chapter
4........................................................................49
DBS Related
Failures......................................................49
DBS_STASTIC_FWDFCHCE_REVCE_LACK................................49
DBS_STASTIC_FWDFCHCE_LACK
..........................................50
DBS_STASTIC_WALSHCODE_LACK
........................................50
DBS_STASTIC_UID_LACK.....................................................51
DBS_STASTIC_NO_RESOURCE_LACK.....................................51
FCH_NUMBER_TWO.............................................................52
ARRIVE_TIME_ERROR..........................................................52
NO_SYSTEM_TIME...............................................................53
INPUT_PARA_ERROR
...........................................................53
POWER_NOT_ENOUGH.........................................................54
SOFTADD_CELL_ERROR
.......................................................54
NO_AVAILABLE_REV_CE
......................................................55
FO_NOT_ENOUGH
...............................................................55
CE_NOT_ENOUGH
...............................................................56
WALSHCODE_NOT_ENOUGH.................................................56
BEFORE_CPS
......................................................................57
UIDWIDTH_NOT_ENOUGH....................................................57
RS_NOT_EXIST...................................................................58
ALLOCATE_UID_ERROR........................................................58
HO_STAT_PILOT_NO_SAME_FREQ.........................................59
HO_STAT_CARRIER_PWR_OVERLOAD ....................................59
HO_STAT_CARRIER_STATE_ERROR
.......................................60
HO_STAT_CARRIER_NO_CE..................................................60
HO_STAT_CARRIER_NO_5KCE
..............................................61
HO_STAT_PILOT_IS_NOT_NEIGHBOR
....................................61
HO_STAT_DESTBSC_IS_HIRS_DATASOFTHO ..........................62
HO_STAT_PILOT_NOT_LOCALBSS
.........................................62
HO_STAT_PILOT_IS_OTHER_UNLNKBSS ................................63
BSC_NO_CIC......................................................................63
BSC_NO_SE
.......................................................................64
-
BSC_NO_VE.......................................................................
64 BSC_NO_IWF
.....................................................................
65
BSC_DSPM_NO_INSTANCE...................................................
65
BSC_NO_RTPPORT..............................................................
66 BSC_NO_VALID_RMP
.......................................................... 66
Chapter
5........................................................................67
RCM Related
Failures.....................................................67
ERR_SPS_RLSA_RCM_DBAccFail_FCHResourceAllocate............. 67
ERR_SPS_RLSA_RCM_PCALL_OtherReason_CEC_REMOVEREQ .. 68
ERR_SPS_RLSA_RCM_FCH_TimerExpired_TconnExpired ........... 69
ERR_SPS_RLSA_RCM_RSCH_OtherReason_Release_RSCH........ 69
ERR_SPS_RLSA_RCM_RSCH_OtherReason_Release_FSCH ........ 70
ERR_SPS_RLSA_RCM_FSCH_FunCallFail_AddChannelFail .......... 70
ERR_SPS_RLSA_RCM_SCHCOMM_TimerExpired_Tsch .............. 71
ERR_SPS_RLSA_RCM_SCHCOMM_TimerExpired_Tbstcomb ....... 71
ERR_SPS_RLSA_RCM_RSCH_FunCallFail_RevSCHSetupFail ....... 72
ERR_SPS_RLSA_RCM_FSCH_FunCallFail_FwdSCHSetupFail ....... 72
ERR_SPS_RLSA_RCM_RSCH_FunCallFail_BurstCommit_STATUS_RemovedSCH
.......................................................................
73
ERR_SPS_RLSA_RCM_RSCH_StateIncorrect_CellNotFoundInRevSCHResourceExtension............................................................
73 ERR_SPS_RLSA_RCM_FSCH_OtherReason_EndOfDuration ........ 74
ERR_SPS_RLSA_RCM_FCH_OtherReason_MRequestAbisConnect_SpecifiedCellIsReleasing.........................................................
74 ERR_SPS_RLSA_RCM_FSCH_TimerExpired_TfschNotifyExpired .. 75
ERR_SPS_RLSA_RCM_PCALL_RecvUnexptMsg_atTchStatusInSemiSoft_AbisdfBurstRequest......................................................
75 ERR_SPS_RLSA_RCM_PCALL_TimerExpired_Tconfigtch............. 76
ERR_SPS_RLSA_RCM_RSCH_FunCallFail_BurstRequest_ConnInSetup
....................................................................................
76
ERR_SPS_RLSA_RCM_FCH_OtherReason_MRequestAbisConnect_SameTimeCellInSameGroupInDiffSetupFlow
............................. 77
ERR_SPS_RLSA_RCM_PMAIN_FunCallFail_MainEntry_MAbisdMsgDispatch...............................................................................
77
Chapter
6........................................................................79
CES Related
Failures......................................................79
ERR_CES_RLSA_CEC_CALLHNDL_FCH_SETUP_CE_IN_USED ..... 79
ERR_CES_RLSA_CEC_CALLHNDL_FCH_SETUP_RCV_CEM_REJECT........................................................................................
80 ERR_CES_RLSA_CEC_CALLHNDL_FCH_SETUP_CEMCTRL_NULL . 80
-
ERR_CES_RLSA_CEC_CALLMAIN_FCH_SETUP_CREATE_PROCESS........................................................................................81
Tables
.............................................................................83
-
Confidential and Proprietary Information of ZTE CORPORATION
i
About this Manual
Purpose
This Manual provides information about the ZXC10 BSSB (V8.0.1.9)
Call Failure and Call Drop for the (1x) system.
Intended Audience
This document is intended for engineers and technicians who
perform operation activities on the ZXC10 BSSB (V8.0.1.9) (1x) Base
Station System.
Prerequisite Skill and Knowledge
To use this document effectively, users should have a general
understanding of wireless telecommunications technology.
Familiarity with the following is helpful:
ZXC10 BSSB (V8.0.1.9) (1x) Base Station System
local operating procedures
What is in This Manual
This Manual contains the following chapters:
T AB L E 1 C H A P T E R S U M M AR Y
Chapter Summary
Chapter 1 BSSAP related Failures
Describes the Failure analysis and troubleshooting for failures
related to BSSAP
Chapter 2 DSPM related Failures
Describes the Failure analysis and troubleshooting for failures
related to DSPM
Chapter 3 SDM related Failures
Describes the Failure analysis and troubleshooting for failures
related to SDM
-
ZXC10 BSSB (V8.0.1.9) Call Failure Reason and Call Drop
Explanation (1x)
ii Confidential and Proprietary Information of ZTE
CORPORATION
Chapter Summary
Chapter 4 DBS related Failures
Describes the Failure analysis and troubleshooting for failures
related to DBS
Chapter 5 RCM related Failures
Describes the Failure analysis and troubleshooting for failures
related to RCM
Chapter 6 CES related Failures
Describes the Failure analysis and troubleshooting for failures
related to CES
Related Documentation
The following documentation is related to this manual:
ZXC10 BSSB (V8.0.1.9) CDMA2000 Base Station System General
Description.
ZXC10 BSSB (V8.0.1.9) CDMA2000 Base Station System Common
Operation Manual
Conventions
ZTE documents employ the following typographical
conventions.
T AB L E 2 TY P O G R AP H I C AL C O N V E N T I O N S
Typeface Meaning
Italics References to other Manuals and documents.
Quotes Links on screens.
Bold Menus, menu options, function names, input fields, radio
button names, check boxes, drop-down lists, dialog box names,
window names.
CAPS Keys on the keyboard and buttons on screens and company
name.
Constant width Text that you type, program code, files and
directory names, and function names.
[ ] Optional parameters.
{ } Mandatory parameters.
| Select one of the parameters that are delimited by it.
Note: Provides additional information about a certain topic.
Checkpoint: Indicates that a particular step needs to be checked
before proceeding further.
Tip: Indicates a suggestion or hint to make things easier or
more productive for the reader.
Typographical Conventions
-
About this Manual
Confidential and Proprietary Information of ZTE CORPORATION
iii
T AB L E 3 M O U S E OP E R AT I O N C O N V E N T I O N S
Typeface Meaning
Click Refers to clicking the primary mouse button (usually the
left mouse button) once.
Double-click Refers to quickly clicking the primary mouse button
(usually the left mouse button) twice.
Right-click Refers to clicking the secondary mouse button
(usually the right mouse button) once.
Drag Refers to pressing and holding a mouse button and moving
the mouse.
How to Get in Touch
The following sections provide information on how to obtain
support for the documentation and the software.
If you have problems, questions, comments, or suggestions
regarding your product, contact us by e-mail at [email protected].
You can also call our customer support center at (86) 755 26771900
and (86) 800-9830-9830.
ZTE welcomes your comments and suggestions on the quality and
usefulness of this document. For further questions, comments, or
suggestions on the documentation, you can contact us by e-mail at
[email protected]; or you can fax your comments and suggestions to
(86) 755 26772236. You can also browse our website at
http://support.zte.com.cn, which contains various interesting
subjects like documentation, knowledge base, forum and service
request.
Mouse Operation
Conventions
Customer Support
Documentation Support
-
ZXC10 BSSB (V8.0.1.9) Call Failure Reason and Call Drop
Explanation (1x)
iv Confidential and Proprietary Information of ZTE
CORPORATION
This page is intentionally blank.
-
Confidential and Proprietary Information of ZTE CORPORATION
1
C h a p t e r 1
BSSAP Related Failures
This chapter introduces and describes call failures related to
BSSAP and also discusses about possible troubleshooting
methods.
The failure cause, analysis and the possible solutions are
described in tables against each error as shown below.
ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_Unspecified T AB L E 4
ERR_SPS_RLSA_BSSAP_F C H S E T U P _C L E AR C O M M AN D _ U N S P
E C I F I E D
Failure Name
ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_Unspecified
Failure Cause When a call is being setup,MSC sends a
ClearCommand message to release the call. The cause is unknown
Failure analysis
1. non-standard cause value in A-interface protocol are carried
in the Cause of ClearCommand 2. The cause carried in ClearCommand
is Cause_A_CallProcessing. The cause value carried in Layer3 is
0x1f. in this case, change it to the BSC internal cause value
(ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_Unspecified). It is used
a lot at switch side. Such as timer expiration and access failure,
this cause value is filled in.
Possible Solution
It is acceptable if the problem occurs occasionally, otherwise,
cooperate with MSC side to find out the cause
-
ZXC10 BSSB (V8.0.1.9) Call Failure Reason and Call Drop
Explanation (1x)
2 Confidential and Proprietary Information of ZTE
CORPORATION
ERR_SPS_RLSA_BSSAP_TE_T3230 T AB L E 5
ERR_SPS_RLSA_BSSAP_TE_T3230
Failure Name ERR_SPS_RLSA_BSSAP_TE_T3230
Failure Cause When a call is being setup, after BSSAP sending
the CMServiceRequest or PagingResponse message to MSC,if the
SccpConnect message is not received from the opposite side, T3230
expires
Possible solution
1. Check No.7 signaling link,perhaps the link is unstable
2. Traffic is too heavy at present. More signaling links are
needed.
ERR_SPS_RLSA_BSSAP_TE_Tassignment T AB L E 6
ERR_SPS_RLSA_BSSAP_TE_T AS S I G N M E N T
Failure Name
ERR_SPS_RLSA_BSSAP_TE_Tassignment
Failure Cause
When a handset originates a call or be called,BSSAP sends an
EV_S_AvfServiceAssignment message to DSMP,if the
EV_S_AvrAssignmentComplete message or EV_S_AvrAssignmentFailure
message is not received from DSMP,the timer Tassignment
expires.
Most likely causes:
1.timer Tassignment expires too soon
2. DSMP is configured with too many instances (more than the
number of DSMP instance that are supported).
3. DSMP CPU utilization is too high
4. SDM activation expires
Possible Solution
1. Check the setting of the timer Tassignment on CMP,the default
value is 6000 (6 seconds).
2. Check if there are too many DSMP instances in the correlation
of RMP and DSMP (different DSMP version supports different number
of instance).
3. If DSMP CPU utilization is too high, add more modules for
DSMP
4. If SDM activation expires,the media stream between SDU and
CHM may be different, or the clock between BSC and BTS is
different. Check the fiber connections at media plate and the SDU
subcards.
-
Chapter 1 BSSAP Related Failures
Confidential and Proprietary Information of ZTE CORPORATION
3
ERR_SPS_RLSA_BSSAP_FchSetup_RcvSccpDisconnect T AB L E 7
ERR_SPS_RLSA_BSSAP_F C H S E T U P _R C VSC C P D I S C O N N E C
T
Failure Name
ERR_SPS_RLSA_BSSAP_FchSetup_RcvSccpDisconnect
Failure Cause
When a handset originates a call or be called, after sending a
CMServiceRequest or PagingResponse message to
MSC,SccpDisconnectmessage is received,SCCP connection establishing
fails or be removed accidentally.
Most likely causes:
1. No.7 signaling link unstable or link is in wrong state.
2. SSN is in wrong state.
3. handset does not assign numbers correctly at MSC side
4. cell CI is different from the CI at MSC side
Possible Solution
1. Check the state of the signaling point on CMP with database
probe to see if it is 0
2. Check the BSC and MSC side to see if they are configured with
SSN (0, 1, 254) of the local end and the opposite end
3. Make sure if the IMSI and ESN of the handset distributes
numbers correctly at MSC side
4. Make sure the cell CI in the call origination message
CMServiceRequest is configured correctly at MSC side.
-
ZXC10 BSSB (V8.0.1.9) Call Failure Reason and Call Drop
Explanation (1x)
4 Confidential and Proprietary Information of ZTE
CORPORATION
ERR_SPS_RLSA_BSSAP_FchSetup_RcvMSReleaseOrder T AB L E 8
ERR_SPS_RLSA_BSSAP_F C H S E T U P _R C VMSR E L E AS E OR D E
R
Failure Name
ERR_SPS_RLSA_BSSAP_FchSetup_RcvMSReleaseOrder
Failure Cause
When a call is setup, handset initiates the release on control
channel
Possible Solution
No troubleshooting is needed
ERR_SPS_RLSA_BSSAP_TE_Tfchsetup T AB L E 9
ERR_SPS_RLSA_BSSAP_TE_T F C H S E T U P
Failure Name
ERR_SPS_RLSA_BSSAP_TE_Tfchsetup
Failure Cause
Timer Tfchsetup expires
Failure Analysis
When a call is setup, BSC sends an AbisdfBTSSetupmessage to BTS
to request the fundamental channel establishment, but the
AbisdrBTSSetupAck message that indicates fundamental channel
establishing is successful or unsuccessful is not received from
BTS, the timer Tfchsetup on CMP expires.
Most likely causes:
1. Timer Tfchsetup expires too soon, default value should be
5000 (5 seconds).
2. fail to establish fundamental channel on BTS
3. CCM CPU utilization is too high
Possible Solution
1. Check the lifecycle of the predefined timer Tfchsetup, if it
expires too soon, change the default value to 5000.
2. Check if there are enough CE and FO resource on BTS.
3. If CCM CPU utilization is too high, adjust CCM CPU overload
threshold, or decrease antenna transmission power to reduce
users.
-
Chapter 1 BSSAP Related Failures
Confidential and Proprietary Information of ZTE CORPORATION
5
ERR_SPS_RLSA_BSSAP_TE_T303 T AB L E 10 ERR_SPS_RLSA_BSS
AP_TE_T303
Failure Name
ERR_SPS_RLSA_BSSAP_TE_T303
Failure Cause
timer T303 expires
Failure Analysis
When a handset originates a call or be called,after sending a
CMServiceRequest or PagingResponse message to MSC,if
AssignmentRequestmessage is not received, the T303 timer on CMP
will expire.
Most likely causes:
1. T303 timer expires too soon
2. MSC side has problem on call processing
Possible Solution
1.Check the timer T303 on CMP, default value is (6 seconds )
2. Find MSC call failure causes at MSC side. T303 indicates MSC
side has problem to process this call. Use MSC tools to find out
the problem cause.
ERR_SPS_RLSA_BSSAP_TE_Txxp T AB L E 11 ERR_SPS_RLSA_BSS AP_TE_T
X X P
Failure Name
ERR_SPS_RLSA_BSSAP_TE_Txxp
Failure Cause
Timer Txxp expires
Failure Analysis
1. Upon receiving the assignment complete message, CallHandler
process sends an A1rAssignmentCompletmessage to MSCe. If Ap
interface is supported, set the timer Txxp to wait for the
A1pfBearerUpdateRequestmessage from MSCe.
2. If the A1pfBearerUpdateRequestmessage from MSCe is not
received before Txxp expires, Txxp timer expires too soon.
3. MSCe side has problem on call processing
Possible Solution
1. Check the setting of timer Txxp on CMP. The default value is
6 seconds
2. Find the call failure causes at MSCe side. Txxp expiration
indicates MSCe side has problem to process the call. MSCe is needed
to find out the problem cause.
-
ZXC10 BSSB (V8.0.1.9) Call Failure Reason and Call Drop
Explanation (1x)
6 Confidential and Proprietary Information of ZTE
CORPORATION
ERR_SPS_RLSA_BSSAP_DB_GetBoardOrIndexNetAddrByLogicAddr T AB L E
12 ERR_SPS_RLSA_BSS AP_DB_G E T B O AR D OR I N D E X N E TAD D R B
Y LO G I C AD D R
Failure Name
ERR_SPS_RLSA_BSSAP_DB_GetBoardOrIndexNetAddrByLogicAddr
Failure Cause
Fail to retrieve board network address according to board
logical address
Failure Analysis
When BSC sends messages to BTS, it invokes the database
interface to retrieve BTS address. If it fails to invoke, the
failure cause will be reported.
Possible Solution
Check the Abis interface to see if it unstable. Transmission
must be checked.
ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_UserBusy T AB L E 13
ERR_SPS_RLSA_BSS AP_F C H S E T U P _C L E AR C O M M AN D _ U S E
R B U S Y
Failure Name
ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_UserBusy
Failure Cause
When a call is setup,BSC receives the ClearCommand message sent
from MSC, the cause value in the field CauseLayer3 carried by this
message is 0x11, which indicates the called user is busy. This is a
normal release.
Failure Analysis
Likely cause:
Called users are busy
Possible Solution
No troubleshooting is needed
-
Chapter 1 BSSAP Related Failures
Confidential and Proprietary Information of ZTE CORPORATION
7
ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_NormalClearing T AB L E
14 ERR_SPS_RLSA_BSS AP_F C H S E T U P _C L E AR C O M M AN D _ N O
R M AL C L E A R I N G
Failure Name
ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_NormalClearing
Failure Cause
When a call is setup, BSC receives the ClearCommand message sent
from MSC, the cause value in the field CauseLayer3 carried by this
message is 0x10, which indicates it is a normal release.
Failure Analysis
Likely cause:
release initiated at MSC side
Possible Solution
No troubleshooting is needed
ERR_SPS_RLSA_BSSAP_ByteIndex_IndexInUsed T AB L E 15
ERR_SPS_RLSA_BSS AP_B Y T E I N D E X _ IN D E X I N U S E D
Failure Name
ERR_SPS_RLSA_BSSAP_ByteIndex_IndexInUsed
Failure Cause
When a call is setup, BSSAP module detects that the instance
number is in use in instance number distribution.
Failure Analysis
Likely cause:
BSSAP module records a wrong instance number
Possible Solution
Check abnormal probe
-
ZXC10 BSSB (V8.0.1.9) Call Failure Reason and Call Drop
Explanation (1x)
8 Confidential and Proprietary Information of ZTE
CORPORATION
ERR_SPS_RLSA_BSSAP_FchSetup_AllLegFail T AB L E 16
ERR_SPS_RLSA_BSS AP_F C H S E T U P _AL L LE G F AI L
Failure Name
ERR_SPS_RLSA_BSSAP_FchSetup_AllLegFail
Failure Cause
When a call is setup, BSC sends an AbisdfBTSSetupmessage to BTS
to request BTS to establish the fundamental channel. But all the
cells in the AbisdrBTSSetupAck returned by BTS fail to
establish.
Failure Analysis
Most likely cause:
1.CE resource shortage, CE resource is in wrong state
2.WASH code shortage
3. FO shortage
4.UID is in wrong state or media plate link is incorrect
5.Carrier is in wrong state
Possible Solution
1. the exact failure causes can be found from the failure cause
in AbisdrBTSSetupAckmessage:
0x5101 indicates forward fundamental channel CE shortage
0x5102 indicates fundamental channel reverse CE shortage
0x5103 indicates fundamental channel forward shortage and
reverse CE shortage
0x5105 indicates WalshCode shortage
0x5106 indicates UID is incorrect
2. check the state of CE (normal or blocked)
3. check the state of carrier (normal or blocked)
4. Check the UID state or media plate link with database
probe
5.check the group number of CE on CHM
Further Troubleshooting
Make sure the software versions run on BSC and BTS are the
same.
-
Chapter 1 BSSAP Related Failures
Confidential and Proprietary Information of ZTE CORPORATION
9
ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_NoAnswer T AB L E 17
ERR_SPS_RLSA_BSS AP_F C H S E T U P _C L E AR C O M M AN D _ N O AN
S W E R
Failure Name
ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_NoAnswer
Failure Cause
When a call is setup, BSC receives the ClearCommand message sent
from MSC, the cause value in the field CauseLayer3 carried by this
message is 0x13, which indicates it rings without answer. This is
normal.
Failure Analysis
Likely cause:
Nobody answers the release initiated by MSC
Possible Solution
This is normal
ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvOrgnInSessionState T AB L E 18
ERR_SPS_RLSA_BSS AP_U N E X P T M S G _RC V OR G N I N S E S S I O
N ST AT E
Failure Name
ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvOrgnInSessionState
Failure Cause
During call status, the call establishment message is
received.
Failure Analysis
Likely cause:
When users originate call, and the process does not release the
message, the call fails.
Possible Solution
It is acceptable if the problem occurs occasionally, otherwise,
further analysis is needed.
-
ZXC10 BSSB (V8.0.1.9) Call Failure Reason and Call Drop
Explanation (1x)
10 Confidential and Proprietary Information of ZTE
CORPORATION
ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvRegInAssignState_Others T AB L E
19 ERR_SPS_RLSA_BSS AP_U N E X P T M S G _ R C V R E G I N AS S I G
N S T AT E _O T H E R S
Failure Name
ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvRegInAssignState_Others
Failure Cause
During call status, a register message is received. This
register message may be of the other type like the timing
register.
Failure Analysis
During a call, the register message is received other then the
Power ON and Power OFF.
Possible Solution
It is acceptable if the problem occurs occasionally, otherwise,
further analysis is needed.
ERR_SPS_RLSA_BSSAP_HandShake_TimeOut T AB L E 20
ERR_SPS_RLSA_BSS AP_H AN D S H AK E _T I M E OU T
Failure Name
ERR_SPS_RLSA_BSSAP_ShakeHand_TimeOut
Failure Cause
Bssap Dspmhandshake expires
Failure Analysis
When a call is established, the timer that waits for the DSPM
handshake message expires
Possible Solution
1. Check handset state
2. Check the foreground mp board of BSC
3. check timer setting
Further Troubleshooting
Check the running of DSPM module
-
Chapter 1 BSSAP Related Failures
Confidential and Proprietary Information of ZTE CORPORATION
11
ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvRegInAssignState_PowerOn T AB L
E 21 ERR_SPS_RLSA_BSS AP_U N E X P T M S G _ R C V R E G I N AS S I
G N S T AT E _P O W E R ON
Failure Name
ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvRegInAssignState_PowerOn
Failure Cause
power on registration message is received during a call
Failure Analysis
Take off the battery during a call, power on and register before
the process release.
Or battery runs out during a call, power on and registers before
the process release.
Possible Solution
It is acceptable if the problem occurs occasionally, otherwise,
further analysis is needed.
ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvRegInAssignState_PowerDown T AB
L E 22 ERR_SPS_RLSA_BSS AP_U N E X P T M S G _ R C V R E G I N AS S
I G N S T AT E _P O W E R D O W N
Failure Name
ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvRegInAssignState_PowerDown
Failure Cause
power off registration message is received during a call
Failure Analysis
1. The user originates a Power OFF due to which the process does
not release and the call fails.
2. The user in a call presses power off button. This is because
of handset.
Possible Solution
depending on the terminal processing flow
-
ZXC10 BSSB (V8.0.1.9) Call Failure Reason and Call Drop
Explanation (1x)
12 Confidential and Proprietary Information of ZTE
CORPORATION
ERR_SPS_RLSA_BSSAP_TgtBSC_FunCallFail__TargetBSCHandlerEntry__A7HOReqMsgProccessForHOWith1X
T AB L E 23 ERR_SPS_RLSA_BSS AP_T G T BSC_F U N CAL L F AI L __ T
AR G E T BSCH AN D L E R E N T R Y__ A7HOR E Q M S G P R O C C E S
S FO R HOW I T H1X
Failure Name
ERR_SPS_RLSA_BSSAP_TgtBSC_FunCallFail__TargetBSCHandlerEntry__A7HOReqMsgProccessForHOWith1X
Failure Cause
The target BSC interconnects with the Hirs BSC. The handoff
request processing is abnormal.
Failure Analysis
1.The number of cell is greater than the maximum number of cell
that a call occupies
2. Neighbor cell is not configured.
Possible Solution
1. Check interconnection configurations
2. If the PN configuration of neighbor cell is reasonable or
not
ERR_SPS_RLSA_BSSAP_Other_ReceiveResetCircuit T AB L E 24
ERR_SPS_RLSA_BSS AP_O T H E R _R E C E I V E R E S E T C I R C U I
T
Failure Name
ERR_SPS_RLSA_BSSAP_Other_ReceiveResetCircuit
Failure Cause
When a call or a hard handoff adding is being established, the
circuit reset message sent from MSC is received.
Failure Analysis
1. CIC state at MSC side and BSC side is different
2. CIC coding at MSC side and BSC side is different
Possible Solution
1. Check CIC state at MSC side and BSC side
2. Check the PCM number at both sides of MSC and BSC to see if
it is the same as the real E1 wiring
Further Troubleshooting
Cooperate with MSC side to find out the cause
-
Chapter 1 BSSAP Related Failures
Confidential and Proprietary Information of ZTE CORPORATION
13
ERR_SPS_RLSA_BSSAP_FchSetup_SendChannelAssignment_AllBtsFail T
AB L E 25 ERR_SPS_RLSA_BSS AP_F C H S E T U P _S E N D C H AN N E L
AS S I G N M E N T _AL L B T S F AI L
Failure Name
ERR_SPS_RLSA_BSSAP_FchSetup_SendChannelAssignment_AllBtsFail
Failure Cause
When a call is setup, fail to send the Extended Channel
Assignment Message to all BTS
Failure Analysis
1. In ECAM/CAMmessage creation, no established cell is found
2. In ECAM/CAMmessage creation, fail to retrieve power
parameters from database
3. Fail to retrieve system ID/subsystem ID according to PN when
sending the ECAMmessage
4. there are coding errors when sending the ECAMmessage
5. fail to retrieve interface board abpm/hgm and etcaddress from
database when sending the ECAMmessage
6. If there are inter BSC assignments, perhaps fail to retrieve
BSC interconnection interface board address
Possible Solution
1. Check more detailed information by checking abnormal
probe
2. Check version compatibility
-
ZXC10 BSSB (V8.0.1.9) Call Failure Reason and Call Drop
Explanation (1x)
14 Confidential and Proprietary Information of ZTE
CORPORATION
ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_HandoffSuccessful T AB
L E 26 ERR_SPS_RLSA_BSS AP_F C H S E T U P _C L E AR C O M M AN D _
H AN D O F F S U C C E S S F U L
Failure Name
RR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_HandoffSuccessful
Failure Cause
When a call is being setup or during a call, if the ClearCommand
message sent from MSC is received, the cause value carried in
ClearCommand is hard handoff is successful
Failure Analysis
1. If the hard handoff flow is successful, Clear Command message
will be received from MSC.
2. This failure should not occur when a call is being setup
Possible Solution
If the failure occurs when a call is being setup, cooperate with
MSC side for troubleshooting.
ERR_SPS_RLSA_BSSAP_TgtBSC_Other__TargetBSCHandler_A7fHandoffRequestProccess__RecievedA7HOReqWhenSemiHO
T AB L E 27 ERR_SPS_RLSA_BSS AP_T G T BSC_OT H E R __ T AR G E T
BSCH AN D L E R _ A7 F H AN D O F F R E Q U E S T P R O C C E S S
__R E C I E V E D A7HORE Q W H E N S E M IHO
Failure Name
ERR_SPS_RLSA_BSSAP_TgtBSC_Other_TargetBSCHandler_A7fHandoffRequestProccess_RecievedA7HOReqWhenSemiHO
Failure Cause
In semi-soft handoff, A7 Handoff Requestmessage will be
discarded if it is received.
Failure Analysis
Source side initiates a new handoff before semi-soft handoff
flow completes.
Possible Solution
It is acceptable if the problem occurs occasionally, otherwise,
check the BSC at source side.
-
Chapter 1 BSSAP Related Failures
Confidential and Proprietary Information of ZTE CORPORATION
15
ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_SemiConcurrentService T
AB L E 28 ERR_SPS_RLSA_BSS AP_F C H S E T U P _C L E AR C O M M AN
D _ S E M I C O N C U R R E N T S E R V I C E
Failure Name
ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_SemiConcurrentService
Failure Cause
When a call is setup,in the forward fundamental channel
establishemnt, the ClearCommand message sent from MSC is received,
the cause value carried in ClearCommand is pseudo concurrent
service
Failure Analysis
When the data service is started, there is a new voice incoming
call. MSC sends out a ClearCommand to request MS to enter Dormant
state
Possible Solution
This failure is acceptable. If there are a lot of such failures,
cooperate with MSC side to handle the problem.
ERR_SPS_RLSA_BSSAP_MsgPara_Origination_InvalidServiceOption T AB
L E 29 ERR_SPS_RLSA_BSS AP_M S G P AR A_OR I G I N AT I O N _ I N V
AL I D S E R V I C E OP T I O N
Failure Name
ERR_SPS_RLSA_BSSAP_MsgPara_Origination_InvalidServiceOption
Failure Cause
The SO carried in call origination message is invalid
Failure Analysis
Terminal cause. The SO carried in call origination message is
invalid (not the SO defined in the protocol)
Possible Solution
Determine what the SO is in call origination message and if the
terminal is old or faulty.
-
ZXC10 BSSB (V8.0.1.9) Call Failure Reason and Call Drop
Explanation (1x)
16 Confidential and Proprietary Information of ZTE
CORPORATION
ERR_SPS_RLSA_BSSAP_HashOpr_AddItem_SccpId2CallRef T AB L E 30
ERR_SPS_RLSA_BSS AP_H AS H OP R _ AD D I T E M _ S C C P I D 2C AL
L R E F
Failure Name
ERR_SPS_RLSA_BSSAP_HashOpr_AddItem_SccpId2CallRef
Failure Cause
When adding the SCCP connection number into the HASH entry of
call reference number, Hash operation fails.
Failure Analysis
Hash deadlock may occur
Possible Solution
Save the abnormal probe information and contact ZTE office.
ERR_SPS_RLSA_BSSAP_Other_Get97DMTMsParaFail T AB L E 31
ERR_SPS_RLSA_BSS AP_O T H E R _GE T 97DMTM S P AR AF AI L
Failure Name
ERR_SPS_RLSA_BSSAP_Other_Get97DMTMsParaFail
Failure Cause
The 97D parameters fail during call.
Failure Analysis
the interface between modules are faulty
Possible Solution
Save the abnormal probe information and contact ZTE office.
-
Chapter 1 BSSAP Related Failures
Confidential and Proprietary Information of ZTE CORPORATION
17
ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_EquipmentFailure T AB L
E 32 ERR_SPS_RLSA_BSS AP_F C H S E T U P _C L E AR C O M M AN D _ E
Q U I P M E N T F AI L U R E
Failure Name
ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_EquipmentFailure
Failure Cause
When a call is setup,MSC sends out a ClearCommand message to
release the call,the failure cause is device malfunction.
Failure Analysis
cooperate with MSC side to find out the cause
Possible Solution
It is acceptable if the problem occurs occasionally, otherwise,
cooperate with MSC side to find out the cause
ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_AuthenticationFailure T
AB L E 33 ERR_SPS_RLSA_BSS AP_F C H S E T U P _C L E AR C O M M AN
D _ AU T H E N T I C AT I O N F AI L U R E
Failure Name
ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_AuthenticationFailure
Failure Cause
When a call is setup, MSC sends out a ClearCommand message to
release the call because of authentication failure
Failure Analysis
Perhaps terminal is invalid
Possible Solution
Co-operate with MSC side to find out the cause
-
ZXC10 BSSB (V8.0.1.9) Call Failure Reason and Call Drop
Explanation (1x)
18 Confidential and Proprietary Information of ZTE
CORPORATION
This page is intentionally blank.
-
Confidential and Proprietary Information of ZTE CORPORATION
19
C h a p t e r 2
DSPM Related Failures
This chapter introduces and describes failures related to DSMP
and also discusses about possible troubleshooting methods.
The failure cause, analysis and the possible solutions are
described in tables against each error as shown below.
ERR_SPS_RLSA_DSPM_CLH_OtherReason_MSNormalRelease T AB L E 34
ERR_SPS_RLSA_DSPM_CLH_OT H E R R E AS O N _ MSN O R M AL R E L E AS
E
Failure Name
ERR_SPS_RLSA_DSPM_CLH_OtherReason_MSNormalRelease
Failure Cause
Normal call release autonomously initiated by handset
Failure Analysis
Normal release
Possible Solution
Normal release
-
ZXC10 BSSB (V8.0.1.9) Call Failure Reason and Call Drop
Explanation (1x)
20 Confidential and Proprietary Information of ZTE
CORPORATION
ERR_SPS_RLSA_DSPM_CLH_TimerExpired_Twaitorder T AB L E 35
ERR_SPS_RLSA_DSPM_CLH_TI M E R E X P I R E D _T W AI T O R D E
R
Failure Name
ERR_SPS_RLSA_DSPM_CLH_TimerExpired_Twaitorder
Failure Cause
When MS originates a call or be called,after successfully
entering traffic channel and capturing the prefix, air-interface
traffic channel signaling handshake expires.
Failure Analysis
Most likely causes:
1. Poor radio condition results in air-interface handshake
message missing. It is acceptable if this failure occurs
occasionally.
2. If frame number checking is enabled, BTS and BSC have
different clock
3. Other causes: Bit error and etc.
Possible Solution
1. Check transmission power of the cell
2. Check the version compatibility and running of CHM and SDU
board
3. If there are a lot of such failures, determine the problem
effect scope firstly: single base station, all base stations (under
an ABPM) or BSC
4. Once the effect scope is determined, disable the frame number
checking on the faulty BTS. If the situation becomes better, it is
believed that problem occurs because the BTS clock and BSC clock
are different. Check the GPS, clock and the GCM board at BTS side
and BSC side
Further Troubleshooting
Check the versions and running of ABPM, DTB and DSM
-
Chapter 2 DSPM Related Failures
Confidential and Proprietary Information of ZTE CORPORATION
21
ERR_SPS_RLSA_DSPM_CLH_OtherReason_SNFailure T AB L E 36
ERR_SPS_RLSA_DSPM_CLH_OT H E R R E AS O N _SNF AI L U R E
Failure Name
ERR_SPS_RLSA_DSPM_CLH_OtherReason_SNFailure
Failure Cause
When MS originates a call or be called, after entering traffic
channel, the service negotiation between base station and MS
fails
Failure Analysis
Most likely cause:
1. Poor radio condition causes air-interface negotiation message
missing. It is acceptable if this failure occurs occasionally.
2. VTC working mode setting in BSS has a problem
Possible Solution
1. Check the forward power of the cell
2. If the handsets in a certain model always suffer from
negotiation failure, check the VTC working mode setting in BSS
(default setting is 8K+EVRC)
3. Replace several combinations for testing.
Further Troubleshooting
If the problem remains, capture the call failure signaling and
contact the ZTE office
ERR_SPS_RLSA_DSPM_CLH_OtherReason_MSPowerDown T AB L E 37
ERR_SPS_RLSA_DSPM_CLH_OT H E R R E AS O N _MSP O W E R D O W N
Failure Name
ERR_SPS_RLSA_DSPM_CLH_OtherReason_MSPowerDown
Failure Cause
Call release initiated by handset power off
Failure Analysis
Normal release
Possible Solution
Normal release
-
ZXC10 BSSB (V8.0.1.9) Call Failure Reason and Call Drop
Explanation (1x)
22 Confidential and Proprietary Information of ZTE
CORPORATION
ERR_SPS_RLSA_DSPM_CLH_TimerExpired_Tpcfinfol3 T AB L E 38
ERR_SPS_RLSA_DSPM_CLH_TI M E R E X P I R E D _T P C F I N F O L
3
Failure Name
ERR_SPS_RLSA_DSPM_CLH_TimerExpired_Tpcfinfol3
Failure Cause
In data service call establishing stage, after A8 link
establishing, DSPM sends an Abaf_PCFInfoL3message to SDM, no
message is received in Tpcfinfol33s,timer Tpcfinfol3 expires
Failure Analysis
Most likely cause:
1. Tpcfinfol3timer setting has a problem
2. corresponding SDU runs abnormally
Possible Solution
1. If the setting of Tpcfinfol3timer on DSMP board is correct
(default value is 3s 2. Check the corresponding SDU when the
problem occurs. Make sure if there is abnormal reset or
switchover.
Further Troubleshooting
Check the version and running status of SDU
-
Chapter 2 DSPM Related Failures
Confidential and Proprietary Information of ZTE CORPORATION
23
ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnUmrSCHRequestMsg_ReleasebyMSDTXTime
T AB L E 39 ERR_SPS_RLSA_DSPM_SCHH_OT H E R R E AS O N _ SCHHON U M
RSCHR E Q U E S TM S G _R E L E AS E B Y MSDTXTI M E
Failure Name
ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnUmrSCHRequestMsg_ReleasebyMSDTXTime
Failure Cause
RSCH DTXTime release initiated by handset
Failure Analysis
Normal release
Possible Solution
Normal release
ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnAbarSCHRemoveIndication_RSCHReleasebySDMDTXTime
T AB L E 40 ERR_SPS_RLSA_DSPM_SCHH_OT H E R R E AS O N _ SCHHON AB
A R SCHR E M O V EI N D I C AT I O N _RSCHR E L E AS E B Y SDMDTXTI
M E
Failure Name
ERR_SPS_RLSA_DSPM_SCHH_OtherReason
_SCHHOnAbarSCHRemoveIndication_RSCHReleasebySDMDTXTime
Failure Cause
RSCH DTXTime release initiated by SDM
Failure Analysis
Normal release
Possible Solution
Normal release
-
ZXC10 BSSB (V8.0.1.9) Call Failure Reason and Call Drop
Explanation (1x)
24 Confidential and Proprietary Information of ZTE
CORPORATION
ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHPNDropIndication_ReleasebyHOH
T AB L E 41 ERR_SPS_RLSA_DSPM_SCHH_OT H E R R E AS O N _ SCHHPND R
O P I N D I C AT I O N _R E L E AS E B Y HOH
Failure Name
ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHPNDropIndication_ReleasebyHOH
Failure Cause
SCH release triggered by soft Hand Off remove on fundamental
channel
Failure Analysis
Normal release
Possible Solution
Normal release
ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnAbisdrBurstRelease_RSCHExistedCellReleasebyRCM
T AB L E 42 ERR_SPS_RLSA_DSPM_SCHH_OT H E R R E AS O N _ SCHHON AB
I S D R B U R S T R E L E AS E _RSCHE X I S T E D C E L L RE L E AS
E B Y RCM
Failure Name
ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnAbisdrBurstRelease_RSCHExistedCellReleasebyRCM
Failure Cause
RSCH release initiated at BTS side
Failure Analysis
Normal release
Possible Solution
Normal release
-
Chapter 2 DSPM Related Failures
Confidential and Proprietary Information of ZTE CORPORATION
25
ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHRelease_ReleasebyCLH T AB
L E 43 ERR_SPS_RLSA_DSPM_SCHH_OT H E R R E AS O N _ SCHHR E L E AS
E _R E L E AS E B Y CLH
Failure Name
ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHRelease_ReleasebyCLH
Failure Cause
SCH release triggered by call release
Failure Analysis
Normal release
Possible Solution
Normal release
ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnAbarSCHRemoveIndication_RSCHReleasebySDMOtherReason
T AB L E 44 ERR_SPS_RLSA_DSPM_SCHH_OT H E R R E AS O N _ SCHHON AB
A R SCHR E M O V EI N D I C AT I O N _RSCHR E L E AS E B Y SDMOT H
E RR E AS ON
Failure Name
ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnAbarSCHRemoveIndication_
RSCHReleasebySDMOtherReason
Failure Cause
SDM initiate RSCHOther causes release
Failure Analysis
Normal release
Possible Solution
Normal release
-
ZXC10 BSSB (V8.0.1.9) Call Failure Reason and Call Drop
Explanation (1x)
26 Confidential and Proprietary Information of ZTE
CORPORATION
ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnAbarSCHRemoveIndication_FSCHReleasebySDMDuration
T AB L E 45 ERR_SPS_RLSA_DSPM_SCHH_OT H E R R E AS O N _ SCHHON AB
A R SCHR E M O V EI N D I C AT I O N _FSCHR E L E AS E B Y SDMD U R
AT I O N
Failure Name
ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnAbarSCHRemoveIndication_FSCHReleasebySDMDuration
Failure Cause
When the SCH dispatch timer is timeout, SDM initiates FSCH
release
Failure Analysis
Normal release
Possible Solution
Normal release
ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHFSCHHandoff_HardHandoff T
AB L E 46 ERR_SPS_RLSA_DSPM_SCHH_OT H E R R E AS O N _ SCHHFSCHHAN
D O F F _H AR D H AN D O F F
Failure Name
ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHFSCHHandoff_HardHandoff
Failure Cause
SCH forward judges that a hard HO is to be done, hence there is
a SCH release
Failure Analysis
Normal release
Possible Solution
Normal release
-
Chapter 2 DSPM Related Failures
Confidential and Proprietary Information of ZTE CORPORATION
27
ERR_SPS_RLSA_DSPM_SCHH_TimerExpired_Tfschdrop T AB L E 47
ERR_SPS_RLSA_DSPM_SCHH_T I M E R E X P I R E D _T F S C H D R O
P
Failure Name
ERR_SPS_RLSA_DSPM_SCHH_TimerExpired_Tfschdrop
Failure Cause
release caused by FSCH due to timeout
Failure Analysis
Normal release
Possible Solution
Normal release
ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnTfschdroppending_ReleasebyTDropPending
T AB L E 48 ERR_SPS_RLSA_DSPM_SCHH_OT H E R R E AS O N _ SCHHON TF
S C H D R O P P E N D I N G _R E L E AS E B Y TD R O P P E N D I N
G
Failure Name
ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnTfschdroppending_ReleasebyTDropPending
Failure Cause
release caused by FSCH due to timeout
Failure Analysis
Normal release
Possible Solution
Normal release
-
ZXC10 BSSB (V8.0.1.9) Call Failure Reason and Call Drop
Explanation (1x)
28 Confidential and Proprietary Information of ZTE
CORPORATION
ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnAbisdrBurstRelease_FSCHExistedCellReleasebyRCM
T AB L E 49 ERR_SPS_RLSA_DSPM_SCHH_OT H E R R E AS O N _ SCHHON AB
I S D R B U R S T R E L E AS E _FSCHE X I S T E D C E L L RE L E AS
E B Y RCM
Failure Name
ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnAbisdrBurstRelease_FSCHExistedCellReleasebyRCM
Failure Cause
FSCH release initiated at BTS side
Failure Analysis
Normal release
Possible Solution
Normal release
ERR_SPS_RLSA_DSPM_CLH_OtherReason_PCFEquipmentFailure T AB L E
50 ERR_SPS_RLSA_DSPM_CLH_OT H E R R E AS O N _ PCFE Q U I P M E N T
F AI L U R E
Failure Name
ERR_SPS_RLSA_DSPM_CLH_OtherReason_PCFEquipmentFailure
Failure Cause
abnormal call release initiated by PCF
Failure Analysis
Most likely cause:
1. corresponding PCFruns abnormally
2. A10 link establishing fails
Possible Solution
1. Check the IMSI, HI and DI carried by A9SetupA8message
2. When checking the handoff,A10 link establishing fails
Further Troubleshooting
Check the version and running of PCF board
-
Chapter 2 DSPM Related Failures
Confidential and Proprietary Information of ZTE CORPORATION
29
ERR_SPS_RLSA_DSPM_CLH_OtherReason_MSGoingIntoDormant T AB L E 51
ERR_SPS_RLSA_DSPM_CLH_OT H E R R E AS O N _ MSGO I N G I N T O D O
R M AN T
Failure Name
ERR_SPS_RLSA_DSPM_CLH_OtherReason_MSGoingIntoDormant
Failure Cause
In data service, the call release autonomously initiated by
handset
Failure Analysis
Normal release
Possible Solution
Normal release
ERR_SPS_RLSA_DSPM_CLH_OtherReason_PCFNormalRelease T AB L E 52
ERR_SPS_RLSA_DSPM_CLH_OT H E R R E AS O N _ PCFN O R M AL R E L E
AS E
Failure Name
ERR_SPS_RLSA_DSPM_CLH_OtherReason_PCFNormalRelease
Failure Cause
In data service, the normal call release initiated by PCF
Failure Analysis
Normal release
Possible Solution
Normal release
-
ZXC10 BSSB (V8.0.1.9) Call Failure Reason and Call Drop
Explanation (1x)
30 Confidential and Proprietary Information of ZTE
CORPORATION
ERR_SPS_RLSA_DSPM_HOH_TimerExpired_SoftHOThocompletion T AB L E
53 ERR_SPS_RLSA_DSPM_HOH_T I M E R E X P I R E D _ S O F T HOTH O C
O M P L E T I O N
Failure Name
ERR_SPS_RLSA_DSPM_HOH_TimerExpired_SoftHOThocompletion
Failure Cause
In soft handoffs, base station sends out a handoff indication
(HDM). Handoff completes message (HCM) is not received from MS
after Thocompletiondefault value is 5s expires
Failure Analysis
Most likely cause:
1. Poor radio condition causes the air-interface handshake
message missing. It is acceptable if this failure occurs
occasionally.
2.If frame number checking is enabled, BTS clock and BSC clock
are different
3.Other causes:e.g. transmission bit error
Possible Solution
1. The setting of Thocompletion timer on DSMP board is correctly
or notdefault value is 5s 2. Check the transmission power of
handoff target cell
3. Check handoff target BTS board and calls under this BTS
Further Troubleshooting
Check the versions and running of ABPM, DTB and DSM
-
Chapter 2 DSPM Related Failures
Confidential and Proprietary Information of ZTE CORPORATION
31
ERR_SPS_RLSA_DSPM_HOH_TimerExpired_Thoreq T AB L E 54
ERR_SPS_RLSA_DSPM_HOH_T I M E R E X P I R E D _T H O R E Q
Failure Name
ERR_SPS_RLSA_DSPM_HOH_TimerExpired_Thoreq
Failure Cause
handoff request response expires
Failure Analysis
Most likely cause:
1. Abis\A3A7 interface link is faulty
2. Handoff target BTS board runs abnormally
3. carrier is faulty
4. Channel board is faulty
5. Inter BSC handoff, the A3A7 interface boards (HGM) of the two
BSC run abnormally
Possible Solution
1. Check the setting of Thoreqtimer on DSMP boarddefault value
is 5s 2. Check Abis\A3A7 interface link
3. Check the handoff target BTS board, carrier state and channel
board (if chip is normal, and if CE is blocked)
4. Inter BSC handoff: Check the A3A7 interface boards (HGM) of
the two BSC and physical links.
Further Troubleshooting
Check the version and running of CCM board
-
ZXC10 BSSB (V8.0.1.9) Call Failure Reason and Call Drop
Explanation (1x)
32 Confidential and Proprietary Information of ZTE
CORPORATION
ERR_SPS_RLSA_DSPM_HOH_ResNotSatisfied_HOHOnUmrCFSearchReport T
AB L E 55 ERR_SPS_RLSA_DSPM_HOH_R E S N O T S AT I S F I E D _
HOHON U M R CFS E AR C H R E P O R T
Failure Name
ERR_SPS_RLSA_DSPM_HOH_ResNotSatisfied_HOHOnUmrCFSearchReport
Failure Cause
In semi-soft handoffs, the handoff at target side fails.
Failure Analysis
Most likely cause:
1. Poor radio condition causes air-interface message missing. It
is acceptable if this failure occurs occasionally.
2.radio condition is poor, target carrier signal is too weak
Possible Solution
Check target carrier signal strength
Further Troubleshooting
Check the versions and running of ABPM, DTB and DSM
ERR_SPS_RLSA_DSPM_HOH_OtherReason_AbisdHandShakeFailure T AB L E
56 ERR_SPS_RLSA_DSPM_HOH_OT H E R R E AS O N _ AB I S D H AN D S H
AK E F AI L U R E
Failure Name
ERR_SPS_RLSA_DSPM_HOH_OtherReason_AbisdHandShakeFailure
Failure Cause
During a call, handshake between DSPM and RCM fails. A call
release is initiated
Failure Analysis
Most likely cause:
1.The RCM, ABPM correspond to BTS run abnormally
2. the setting of Tphysicaltimer on DSMP board has a problem
Possible Solution
1. The setting of Tphysicaltimer on DSMP board is correct or
notdefault value is 2 minutes 2. Check the RCM of the corresponding
BTS when the problem occurs. If ABPM runs normally or not. Make
sure if there is abnormal reset or switchover.
-
Chapter 2 DSPM Related Failures
Confidential and Proprietary Information of ZTE CORPORATION
33
Further Troubleshooting
Check the versions and running status of CCM and ABPM
ERR_SPS_RLSA_DSPM_SCHH_TimerExpired_Tfschbstreq T AB L E 57
ERR_SPS_RLSA_DSPM_SCHH_T I M E R E X P I R E D _T F S C H B S T R E
Q
Failure Name
ERR_SPS_RLSA_DSPM_SCHH_TimerExpired_Tfschbstreq
Failure Cause
In FSCH establishment, after BSC sending the
BurstRequestmessage, Tfschbstreqtimer expires and the
BurstResponsemessage from BTS is not received.
Failure Analysis
Most likely cause:
Message is missing at Abis interface. It is acceptable if this
problem occurs occasionally.
Possible Solution
1. Check Tfschbstreqtimer setting500ms 2. Make sure if the
message is missing or not
Further Troubleshooting
Check the versions and running status of CCM, ABPM, DTB and
DSM
-
ZXC10 BSSB (V8.0.1.9) Call Failure Reason and Call Drop
Explanation (1x)
34 Confidential and Proprietary Information of ZTE
CORPORATION
ERR_SPS_RLSA_DSPM_CLH_OtherReason_PDSNDenied_Reason_Unspecified
T AB L E 58 ERR_SPS_RLSA_DSPM_CLH_OT H E R R E AS O N _PDSND E N I
E D _ R E AS O N _U N S P E C I F I E D
Failure Name
ERR_SPS_RLSA_DSPM_CLH_OtherReason_PDSNDenied_Reason_Unspecified
Failure Cause
In data service call establishing stage,A8 link establishing
fails, when the cause value PDSN brings to DSPM is 0x80, the
failure cause reported by DSPM.
Failure Analysis
Most likely cause:
1. A10link establishing fails
2. Check the corresponding PCF when the problem occurs, Make
sure if there is abnormal reset or switchover.
Possible Solution
check A10link to see if it is successfully established
ERR_SPS_RLSA_DSPM_CLH_OtherReason_OVERLOAD T AB L E 59
ERR_SPS_RLSA_DSPM_CLH_OT H E R R E AS O N _OVERLO AD
Failure Name
ERR_SPS_RLSA_DSPM_CLH_OtherReason_OVERLOAD
Failure Cause
DSMP board CPU overloads
Failure Analysis
DSMP board CPU overloads
Possible Solution
If the problem is serious, unplug the standby board
Further Troubleshooting
Add DSMP board
-
Chapter 2 DSPM Related Failures
Confidential and Proprietary Information of ZTE CORPORATION
35
ERR_SPS_RLSA_DSPM_CLH_OtherReason_Ta8setup T AB L E 60
ERR_SPS_RLSA_DSPM_CLH_OT H E R R E AS O N _T A8 S E T U P
Failure Name
ERR_SPS_RLSA_DSPM_CLH_OtherReason_Ta8setup
Failure Cause
In data service call establishing stage,A8 link establishing
expires: DSPM sends the A9SetupA8message to PCF, no reply message
is received in Ta8setup3s
Failure Analysis
Most likely cause:
1.In OMC,PCF IP address configuration has problem
2.Physical link breaks
3.corresponding PCF is faulty
Possible Solution
1.If the setting of Ta8setup timer default value is 3son DSMP
board is correct or not
2. Check the PCF IP address configuration in OMC and the
physical link
3. Check the corresponding PCF when the problem occurs, Make
sure if there is abnormal reset or switchover.
ERR_SPS_RLSA_DSPM_CLH_OtherReason_Tshakehandrecv T AB L E 61
ERR_SPS_RLSA_DSPM_CLH_OT H E R R E AS O N _ TS H AK E H AN D R E C
V
Failure Name
ERR_SPS_RLSA_DSPM_CLH_OtherReason_Tshakehandrecv
Failure Cause
During a call, there is a handshake between DSPM, SDU and BSSAP.
When there is no reply message, the Trecv is timeout due to which
the SPS releases the call.
Failure Analysis
Most likely cause:
1. DSPM does not receive the reply message from SDM when it
sends two handshake messages to SDM in 5 minutes.
2. DSPM does not receive the reply message from BSSAP when it
sends two handshake messages to SDM in 5 minutes.
Possible Solution
1. If the setting of Trecv timer (default value is 5 minutes) on
DSMP board is correct or not
2. Check the corresponding CMP when the problem occurs. If SDU
runs normally or not. Make sure if there is abnormal reset or
switchover.
-
ZXC10 BSSB (V8.0.1.9) Call Failure Reason and Call Drop
Explanation (1x)
36 Confidential and Proprietary Information of ZTE
CORPORATION
ERR_SPS_RLSA_DSPM_HOH_TimerExpired_SemiSoftHOThocompletion T AB
L E 62 ERR_SPS_RLSA_DSPM_HOH_T I M E R E X P I R E D _ S E M I S O
F T HOTH O C O M P L E T I O N
Failure Name
ERR_SPS_RLSA_DSPM_HOH_TimerExpired_SemiSoftHOThocompletion
Failure Cause
In semi-handoffs, base station sends out the handoff indication
(HDM), if the MS handoff completes message (HCM) is not received
when Thocompletiondefault value is 5s expires, the handoff will
expire.
Failure Analysis
Most likely cause:
1. Poor radio condition causes air-interface handshake message
missing. It is acceptable if this failure occurs occasionally.
2. If frame number checking is enabled, BTS and BSC have
different clocks
3. Other causes: e.g. bit error
Possible Solution
1.If the setting of Thocompletion timer ob DSMP board is correct
or notdefault value 5s 2.Check the handoff target cell transmission
power
3. Check the handoff target BTS board to see if the call
originations under this BTS are normal or not.
Further Troubleshooting
Check the versions and running of ABPM, DTB and DSM
-
Chapter 2 DSPM Related Failures
Confidential and Proprietary Information of ZTE CORPORATION
37
ERR_SPS_RLSA_DSPM_HOH_ResNotSatisfied_HOHOnA7rHOReqAck T AB L E
63 ERR_SPS_RLSA_DSPM_HOH_R E S N O T S AT I S F I E D _ HOHON A7 R
HOR E Q AC K
Failure Name
ERR_SPS_RLSA_DSPM_HOH_ResNotSatisfied_HOHOnA7rHOReqAck
Failure Cause
Handoff request is rejected by target side
Failure Analysis
Most likely cause:
1. resource at target BTS\BSC side has problem
2.Flow has problem
Possible Solution
1.Check Abis\A3A7 interface link
2. Check the handoff target BTS board, carrier state and channel
board (if the chip is normal and if CE is blocked).
3.Inter BSC handoff:Check the A3A7 interface board (HGM) of the
two BSC and the physical link
Further Troubleshooting
Check the version and running of CCM board
-
ZXC10 BSSB (V8.0.1.9) Call Failure Reason and Call Drop
Explanation (1x)
38 Confidential and Proprietary Information of ZTE
CORPORATION
ERR_SPS_RLSA_DSPM_CLH_OtherReason_PDSNDenied_Reason_Administratively_Pohibited
T AB L E 64 ERR_SPS_RLSA_DSPM_CLH_OT H E R R E AS O N _PDSND E N I
E D _ R E AS O N _ AD M I N I S T R AT I V E L Y _P O H I B I T E
D
Failure Name
ERR_SPS_RLSA_DSPM_CLH_OtherReason
_PDSNDenied_Reason_Administratively_Pohibited
Failure Cause
In data service call establishing stage,A8 link establishing
fails, when the cause value PDSN brings to DSPM is 0x81, the
failure cause reported by DSPM.
Failure Analysis
Most likely cause:
1. A10 link establishing fails
2. Check the corresponding PCF when the problem occurs. Make
sure if there is abnormal reset or switchover.
Possible Solution
check A10 link to see if it is successfully established
ERR_SPS_RLSA_DSPM_CLH_OtherReason_PCFDenied_PDSN_Resource_Unavailable
T AB L E 65 ERR_SPS_RLSA_DSPM_CLH_OT H E R R E AS O N _PCFD E N I E
D _ PDSN_R E S O U R C E _U N AV AI L AB L E
Failure Name
ERR_SPS_RLSA_DSPM_CLH_OtherReason_PCFDenied_PDSN_Resource_Unavailable
Failure Cause
In data service call establishing stage, A8 link establishing
fails. The cause value PCF brings for DSPM. PDSN resource is
unavailable.
Failure Analysis
Most likely cause:
1.A10 link establishing fails
2.PDSN is faulty
Possible Solution
1. Check A10 link to see if is successful established
2. Check the corresponding PDSN when the problem occurs. Make
sure if there is abnormal reset or switchover.
-
Chapter 2 DSPM Related Failures
Confidential and Proprietary Information of ZTE CORPORATION
39
ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHReleaseRSCHbyLegFail_ReleaseRschExistSDMLegFailure
T AB L E 66 ERR_SPS_RLSA_DSPM_SCHH_OT H E R R E AS O N _ SCHHR E L
E AS E RSCH B Y LE GF AI L _R E L E AS E R S C H E X I S TSDML E G
F AI L U R E
Failure Name
ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHReleaseRSCHbyLegFail_ReleaseRschExistSDMLegFailure
Failure Cause
When DSPM receives the LegLinkFailure reported by SDM, if RSCH
is not partly soft handoff and the released cell and SDM notify
different cells, the failure is reported by DSPM.
Failure Analysis
Most likely cause:
SDM has no reverse frames
Possible Solution
Check Abis interface
ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnUmrSCHRequestMsg_FCHNotExisted
T AB L E 67 ERR_SPS_RLSA_DSPM_SCHH_OT H E R R E AS O N _ SCHHON U M
RSCHR E Q U E S TM S G _FCHN O T E X I S T E D
Failure Name
ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnUmrSCHRequestMsg_FCHNotExisted
Failure Cause
Data service fundamental channel receives a message from SCH for
setup.
Failure Analysis
Most likely cause:
call origination flow does not complete
Possible Solution
This failure is acceptable
-
ZXC10 BSSB (V8.0.1.9) Call Failure Reason and Call Drop
Explanation (1x)
40 Confidential and Proprietary Information of ZTE
CORPORATION
This page is intentionally blank.
-
Confidential and Proprietary Information of ZTE CORPORATION
41
C h a p t e r 3
SDM Related Failures
This chapter introduces and describes call failures related to
SDM and also discusses about possible troubleshooting methods.
The failure cause, analysis and the possible solutions are
described in tables against each error as shown below.
SDM_Activate_Fail_AcquirePreambleFail_Normal T AB L E 68 SDM_AC
T I V AT E _F AI L _ AC Q U I R E P R E AM B L E FAI L _N O R M
AL
Failure Name
SDM_Activate_Fail_AcquirePreambleFail_Normal
Failure Cause
Mobile establishing fails; BSC has not received Preamble sent by
the mobile before timeout, but Idle frame can be received.
There are many reasons for this abnormality. Every problem in
the system may cause failure in mobile capturing. For example,
wrong CHM version, parameters for the mobile are inconsistent with
that of base station side, long code error, inconsistent RC and PN
offset error etc.
Possible Solution
1. Check CHM version
2. Check failure reason submitted to abnormality probe
3. Check CE if there is residual forward CE in RB_FWDCE list
4. Check if channel board has blocked CE.
-
ZXC10 BSSB (V8.0.1.9) Call Failure Reason and Call Drop
Explanation (1x)
42 Confidential and Proprietary Information of ZTE
CORPORATION
SDM_Activate_Fail_AcquirePreambleFail_NoRevFrm T AB L E 69
SDM_AC T I V AT E _F AI L _ AC Q U I R E P R E AM B L E FAI L _N O
R E V FR M
Failure Name
SDM_Activate_Fail_AcquirePreambleFail_NoRevFrm
Failure Cause
Mobile connection establishment fails; BSC has not received
reverse traffic frame sent by BTS before timer is timeout.
There are many reasons for BSCs not receiving traffic frame from
BTS. Those with high probability are:
1.Link block for Abis media flow
2.Channel list is wrongly added on either BTS or BSC side,
etc.
Possible Solution
1. Check if Abis link is disconnected.
2.Check if adding channel list (BSC and BTS side) in signaling
tracing is successful
3. Check if there are CE suspended in CHM
-
Chapter 3 SDM Related Failures
Confidential and Proprietary Information of ZTE CORPORATION
43
SDM_Find_Fail_WaitConfigVTCTimeout T AB L E 70 SDM_FI N D _F AI
L _W AI T C O N F I G VTCTI M E O U T
Failure Name
SDM_Find_Fail_WaitConfigVTCTimeout
Failure Cause
After SDM activation, SDM has not received
EV_S_AbafStartVocoderCoding message sent by DSPM before timer is
timeout.
The two possible reasons for this abnormality are:
1. Service negotiation fails between Level Three and mobile and
Level Three does not receive confirmation message of the e mobile.
Detailed reasons vary: for example, the mobile does not receive
confirmation message on BS side, so that it does not return
confirmation message to BS. Or the mobile has received confirmation
message on BS side, but due to some reason it does not return
confirmation to BS. The abnormality may also be caused by
inconsistent parameters between the mobile and BS side (e.g. RC
inconsistent) causing the mobile not to detect confirmation message
on base station side.
2. Abnormal Level Three process. After successful negotiation
with the mobile, it has not sent EV_S_AbafStartVocoderCoding
message to SDM, which can be judged from signaling tracing.
Possible Solution
1.Check if there are handshake messages EV_S_UmfBSOrder and
EV_S_UmrMSOrder of traffic channel
2. If none of these messages exists; the reason might be
inconsistent parameters on MS and BS side. Check the versions of MS
and BS side.
3. If handshake is normal, check if there is
EV_S_AbafStartVocoderCoding message in signaling; if there is no,
DSPM has not sent message.
-
ZXC10 BSSB (V8.0.1.9) Call Failure Reason and Call Drop
Explanation (1x)
44 Confidential and Proprietary Information of ZTE
CORPORATION
SDM_Link_Fail_RevNoFrm T AB L E 71 SDM_LI N K _F AI L _R E V N O
FR M
Failure Name
SDM_Link_Fail_RevNoFrm
Failure Cause
Link failure. SDM can not receive traffic frame sent from BTS
during a period (default time is 18s).
Reasons for this abnormality vary, for example, Abis link
problem and CHM dispatching problem, which is subject to different
situation.
While submitting the abnormality, calling will be released.
Possible Solution
Check if Abis link is disconnected.
SDM_Link_Fail_RevTooManyBadFrm T AB L E 72 SDM_LI N K _F AI L _R
E V TO O M AN Y B AD FR M
Failure Name
SDM_Link_Fail_RevTooManyBadFrm
Failure Cause
Link failure. SDM receives from BTS side almost all error frame
during a period (default time is 18s).
Reasons vary; it might be normal abnormal reasons, which is
subjected to actual situation. For example, while the reverse radio
link is very bad, the abnormality will be submitted. This is normal
release. However, it is not necessarily normal; there probably are
many underlying system problems, e.g. in calling process, due to
certain reason the mobile releases itself spontaneously while BS
does not receive release message of the mobile, so that after a
period abnormality will be submitted. Thus it needs to be checked
why the mobile releases itself spontaneously. Besides, inconsistent
parameters between the mobile and BS side and PN offset error
probably cause the failure.
Possible Solution
1. Check MS and BS side parameters (PN offset, version)
2. If parameters are consistent, then MS releases itself
spontaneously; this is failure within normal range.
-
Chapter 3 SDM Related Failures
Confidential and Proprietary Information of ZTE CORPORATION
45
SDM_Link_Fail_FwdA2pNoFrm T AB L E 73 SDM_LI N K _F AI L _F W D
A2 P N O FR M
Failure Name
SDM_Link_Fail_FwdA2pNoFrm
Failure Cause
SDM can not receive traffic frame sent from MGW during a period
(default time is 18s)
Reasons for this abnormality vary, for example, net cable on Ap
port has problem, MGW process problem (not sending frame), which is
subject to actual situation. While submitting this abnormality,
calling will be released.
Possible Solution
Check net cable on Ap port and check BSC side and MGW side
configuration (for example whether packet quantity is the same), if
problem is not found, then analyze MGW side.
SDM_Find_Fail_WaitConfigRLPTimeout T AB L E 74 SDM_FI N D _F AI
L _W AI T C O N F I G RLPTI M E O U T
Failure Name
SDM_Find_Fail_WaitConfigRLPTimeout
Failure Cause
While waiting for EV_S_AbafPCFInfoL3 message sent by Level Three
after successful digital service SDM activation, timer is timeout
and the message is not received.
Possible Solution
This abnormality is usually caused by handshaking timeout
between Level Three and mobile.
-
ZXC10 BSSB (V8.0.1.9) Call Failure Reason and Call Drop
Explanation (1x)
46 Confidential and Proprietary Information of ZTE
CORPORATION
SDM_Link_Fail_RSCHLegLinkFail T AB L E 75 SDM_LI N K _F AI L
_RSCHL E G L I N K F AI L
Failure Name
SDM_Link_Fail_RSCHLegLinkFail
Failure Cause
Reverse supplementary channel leg does not receive frame from
reverse channel board.
Possible Solution
1. Check signaling and find out if CHM has released the leg.
2. Check if reverse link has problem.
3. Check CHM statistics for frame receiving and sending
SDM_Link_Fail_FwdA2pTooManyErrEncodeFrm T AB L E 76 SDM_LI N K
_F AI L _F W D A2 P TO O M AN Y E R R E N C O D E FR M
Failure Name
SDM_Link_Fail_FwdA2pTooManyErrEncodeFrm
Failure Cause
Inadequate good frame is received from MGW within 18s. Possible
reasons are:
1. Problem occur during MGW frame sending, i.e. not send frame
to SDM.
2 Problem occurs in A p port link during call; the possibility
is relatively small.
3. SDM process error
Possible Solution
1. Check if Ap port link is normal
2. If it is not disconnected link, it is normal situation;
please contact engineers at the office.
-
Chapter 3 SDM Related Failures
Confidential and Proprietary Information of ZTE CORPORATION
47
SDM_Activate_Fail_InitVocoderFail T AB L E 77 SDM_AC T I V AT E
_F AI L _ I N I T V O C O D E R F AI L
Failure Name
SDM_Activate_Fail_InitVocoderFail
Failure Cause
Failure in sending initialized vocoder message, the possible
reasons are: the utilization of CPU of SDU board is too high so
that message cannot be sent out, or problem occurs in the bottom
level.
Possible Solution
1. Check SDU board utilization ratio. If it is too high, adding
board is needed.
2. If SDU board is normal but the failure remains, please
contact engineers at the office.
SDM_OprVocoder_Fail_WaitStartVocoderCodingAckTimeOut T AB L E 78
SDM_OP R V O C O D E R _F AI L _W AI T S T AR T V O C O D E R C O D
I N G AC K T I M E OU T
Failure Name
SDM_OprVocoder_Fail_WaitStartVocoderCodingAckTimeOut
Failure Cause
SDM cannot receive ACK message of VTC after sending
startVocoderCoding message to VTC; possible reason is that message
lost occurs among boards; either startVocoderCoding message or ACK
message is lost.
Possible Solution
Please contact engineers at the office.
-
ZXC10 BSSB (V8.0.1.9) Call Failure Reason and Call Drop
Explanation (1x)
48 Confidential and Proprietary Information of ZTE
CORPORATION
SDM_Find_Fail_NoFCHLeg T AB L E 79 SDM_FI N D _F AI L _N O FCHLE
G
Failure Name
SDM_Find_Fail_NoFCHLeg
Failure Cause
When SDM receives AbafSDMDropLeg message sent by Level Three, no
leg is found for SDM to remove. Possible reason is message
maintained by SDM is different from that of Level Three.
Possible Solution
Check signaling to find out whether Level Three has noticed SDM
to add this leg; if it has, then the problem lies in SDM, if not
then it lies in Level Three.
SDM_Activate_Fail_MsgParaFail T AB L E 80 SDM_AC T I V AT E _F
AI L _M S G P AR AF AI L
Failure Name
SDM_Activate_Fail_MsgParaFail
Failure Cause
SDM receives message sent by Level THREE, but the parameter
inside is incorrect.
Possible Solution
Check SDM abnormality probe message to find which parameter is
wrong. In signaling tracing check AbafActivateSDM message to find
out where the fault is so as to confirm whether Level Three is
wrongly written or it is the SDM process problem.
-
Confidential and Proprietary Information of ZTE CORPORATION
49
C h a p t e r 4
DBS Related Failures
This chapter introduces and describes call failures related to
DBS and also discusses about possible troubleshooting methods.
The failure cause, analysis and the possible solutions are
described in tables against each error as shown below.
DBS_STASTIC_FWDFCHCE_REVCE_LACK T AB L E 81
DBS_STASTIC_FWDFCHCE_REVCE_LACK
Failure Name
DBS_STASTIC_FWDFCHCE_REVCE_LACK
Failure Cause
Failure due to inadequate forward or reverse CE while basic
channel is being set up during MS calling or MSs being called.
Failure Analysis
The reason for the failure is inadequate forward and reverse CE
resource.
Possible Solution
Check failure reason submitted in abnormality probe.
Check if there is residual forward CE in RB_FWDCE list, i.e. the
CE with status position as 0 (INDEX is 0-31), check if there is
residual reverse CE in RB_REVCE list, i.e. the CE with status
position as 0 (INDEX is 64-95) and check if channel board has
blocked CE.
-
ZXC10 BSSB (V8.0.1.9) Call Failure Reason and Call Drop
Explanation (1x)
50 Confidential and Proprietary Information of ZTE
CORPORATION
DBS_STASTIC_FWDFCHCE_LACK T AB L E 82 DBS_STASTIC_FWDFCHCE_L
ACK
Failure Name
DBS_STASTIC_FWDFCHCE_LACK
Failure Cause
Failure due to inadequate reverse CE on 5K channel board while
basic channel is being set up during MS calling or MSs being
called.
Failure Analysis
The reason for this failure is inadequate forward CE
resource.
Possible Solution
1. Check out failure reasons submitted in abnormality probe.
2. Check if there is residual forward CE in RB_FWDCE list.
3. Check if channel board has blocked CE.
DBS_STASTIC_WALSHCODE_LACK T AB L E 83
DBS_STASTIC_WALSHCODE_LACK
Failure Name
DBS_STASTIC_WALSHCODE_LACK
Failure Cause
Resource distribution failure due to WALSHCODE distribution
failure while basic channel is being set up during MS calling or
MSs being called.
Failure Analysis
The reason for this failure is there is no WALSHCODE available
under the carrier.
Possible Solution
1. Check failure reasons submitted in abnormality probe.
2. Check if there is free resource in WALSHCODE using probe.
-
Chapter 4 DBS Related Failures
Confidential and Proprietary Information of ZTE CORPORATION
51
DBS_STASTIC_UID_LACK T AB L E 84 DBS_STASTIC_UID_LACK
Failure Name
DBS_STASTIC_UID_LACK
Failure Cause
Resource distribution failure due to UID distribution failure
while basic channel is being set up by IP platform during MS
calling or MSs is being called.
Failure Analysis
There is no available broadband under the sector or failure
occurs in bandwidth distribution.
Possible Solution
1. Check failure reasons submitted in abnormality probe.
2. Check whether LeftBandWidth field in R_UID list is bigger
than 9 using probe.
DBS_STASTIC_NO_RESOURCE_LACK T AB L E 85
DBS_STASTIC_NO_RESOURCE_LACK
Failure Name
DBS_STASTIC_NO_RESOURCE_LACK
Failure Cause
Reason for the failure that is not because of inadequate
resource
Failure Analysis
This error reason code is default error code distributed by
database resource. Once this code exists, usually data error or
parameter error occurs in some list inside.
Possible Solution
Check failure reasons submitted in abnormality probe.
-
ZXC10 BSSB