ZXC10 BSSB (V8.0.1.9) Call Failure Reason and Call Drop Explanation (1x)

ZXC10 BSSB
CDMA 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: doc@zte.com.cn
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
Your evaluation
of this
documentation
Fair
Average
Poor
Bad
N/A
Accessibility:
(Contents, Index, Headings, Numbering, Glossary)
Good
Fair
Average
Poor
Bad
N/A
Intelligibility:
(Language, Vocabulary, Readability & Clarity, Technical Accuracy, Content)
Good
Fair
Average
Poor
Bad
N/A
Please check the suggestions which you feel can improve this documentation:
Your
suggestions for
improvement of
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_PowerO
n ...................................................................................... 11
ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvRegInAssignState_PowerD
own................................................................................... 11
ERR_SPS_RLSA_BSSAP_TgtBSC_FunCallFail__TargetBSCHandlerE
ntry__A7HOReqMsgProccessForHOWith1X .............................. 12
ERR_SPS_RLSA_BSSAP_Other_ReceiveResetCircuit.................. 12
ERR_SPS_RLSA_BSSAP_FchSetup_SendChannelAssignment_AllBts
Fail ................................................................................... 13
ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_HandoffSucces
sful ................................................................................... 14
ERR_SPS_RLSA_BSSAP_TgtBSC_Other__TargetBSCHandler_A7fHa
ndoffRequestProccess__RecievedA7HOReqWhenSemiHO........... 14
ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_SemiConcurren
tService ............................................................................. 15
ERR_SPS_RLSA_BSSAP_MsgPara_Origination_InvalidServiceOptio
n ...................................................................................... 15
ERR_SPS_RLSA_BSSAP_HashOpr_AddItem_SccpId2CallRef ...... 16
ERR_SPS_RLSA_BSSAP_Other_Get97DMTMsParaFail................ 16
ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_EquipmentFailu
re ..................................................................................... 17
ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_Authentication
Failure ............................................................................... 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_SCHHOnUmrSCHRequ
estMsg_ReleasebyMSDTXTime .............................................. 23
ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnAbarSCHRem
oveIndication_RSCHReleasebySDMDTXTime............................ 23
ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHPNDropIndicatio
n_ReleasebyHOH................................................................. 24
ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnAbisdrBurstR
elease_RSCHExistedCellReleasebyRCM ................................... 24
ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHRelease_Releas
ebyCLH.............................................................................. 25
oveIndication_RSCHReleasebySDMOtherReason ...................... 25
oveIndication_FSCHReleasebySDMDuration............................. 26
ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHFSCHHandoff_H
ardHandoff ......................................................................... 26
ERR_SPS_RLSA_DSPM_SCHH_TimerExpired_Tfschdrop ............ 27
ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnTfschdroppen
ding_ReleasebyTDropPending ............................................... 27
ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnAbisdrBurstR
elease_FSCHExistedCellReleasebyRCM ................................... 28
ERR_SPS_RLSA_DSPM_CLH_OtherReason_PCFEquipmentFailure 28
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_HOHOnUmrCFSearc
hReport ............................................................................. 32
ERR_SPS_RLSA_DSPM_HOH_OtherReason_AbisdHandShakeFailur
e ...................................................................................... 32
ERR_SPS_RLSA_DSPM_SCHH_TimerExpired_Tfschbstreq.......... 33
ERR_SPS_RLSA_DSPM_CLH_OtherReason_PDSNDenied_Reason_U
nspecified .......................................................................... 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_SemiSoftHOThocomple
tion................................................................................... 36
ERR_SPS_RLSA_DSPM_HOH_ResNotSatisfied_HOHOnA7rHOReqAc
k ...................................................................................... 37
ERR_SPS_RLSA_DSPM_CLH_OtherReason_PDSNDenied_Reason_A
dministratively_Pohibited ..................................................... 38
ERR_SPS_RLSA_DSPM_CLH_OtherReason_PCFDenied_PDSN_Reso
urce_Unavailable ................................................................ 38
ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHReleaseRSCHby
LegFail_ReleaseRschExistSDMLegFailure................................. 39
ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnUmrSCHRequ
estMsg_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_R
emovedSCH ....................................................................... 73
ERR_SPS_RLSA_RCM_RSCH_StateIncorrect_CellNotFoundInRevSC
HResourceExtension ............................................................ 73
ERR_SPS_RLSA_RCM_FSCH_OtherReason_EndOfDuration ........ 74
ERR_SPS_RLSA_RCM_FCH_OtherReason_MRequestAbisConnect_S
pecifiedCellIsReleasing......................................................... 74
ERR_SPS_RLSA_RCM_FSCH_TimerExpired_TfschNotifyExpired .. 75
ERR_SPS_RLSA_RCM_PCALL_RecvUnexptMsg_atTchStatusInSemi
Soft_AbisdfBurstRequest...................................................... 75
ERR_SPS_RLSA_RCM_PCALL_TimerExpired_Tconfigtch............. 76
ERR_SPS_RLSA_RCM_RSCH_FunCallFail_BurstRequest_ConnInSet
up .................................................................................... 76
ERR_SPS_RLSA_RCM_FCH_OtherReason_MRequestAbisConnect_S
ameTimeCellInSameGroupInDiffSetupFlow ............................. 77
ERR_SPS_RLSA_RCM_PMAIN_FunCallFail_MainEntry_MAbisdMsgDi
spatch ............................................................................... 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
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:
TABLE 1 CHAPTER SUMM ARY
Chapter
Summary
Chapter 1 BSSAP
related Failures
Describes the Failure analysis and

troubleshooting for failures related to
BSSAP
Chapter 2 DSPM related

Failures

troubleshooting for failures related to
DSPM
Chapter 3 SDM related

Failures

troubleshooting for failures related to SDM
Confidential and Proprietary Information of ZTE CORPORATION
Chapter
Summary
Chapter 4 DBS related

Failures

troubleshooting for failures related to DBS
Chapter 5 RCM related

Failures

troubleshooting for failures related to RCM
Chapter 6 CES related

Failures

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
Typographical
Conventions
ZTE documents employ the following typographical conventions.

TABLE 2 TYPOGRAPHICAL CONVENTIONS
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, dropdown 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.
ii
About this Manual
Mouse
Operation
Conventions
TABLE 3 MOUSE OPERATION CONVENTIONS
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.
Customer
Support
Documentation
Support
If you have problems, questions, comments, or suggestions

regarding
your
product,
contact
us
by
e-mail
at
support@zte.com.cn. 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 doc@zte.com.cn; 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.
iii
iv
Chapter
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_FchSetu
p_ClearCommand_Unspecified
TABLE 4 ERR_SPS_RLS A_BSS AP_FCHSETUP_CLEARCOMMAND_
UNSPECIFIED
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_ClearComman
d_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
ERR_SPS_RLSA_BSSAP_TE_T323
0
TABLE 5 ERR_SPS_RLS A_BSS AP_TE_T3230
Failure Name
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_Tass
ignment
TABLE 6 ERR_SPS_RLS A_BSS AP_TE_TASSIGNMENT
Failure
Name
ERR_SPS_RLSA_BSSAP_TE_Tassignment
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.
Failure
Cause
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
1. Check the setting of the timer Tassignment on
CMP,the default value is 6000 (6 seconds).
Possible
Solution
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
p_RcvSccpDisconnect
TABLE 7 ERR_SPS_RLS A_BSS AP_FCHSETUP_RCVSCCPDISCONNECT
Failure
Name
ERR_SPS_RLSA_BSSAP_FchSetup_RcvSccpDisconnect
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.
Failure
Cause
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
1. Check the state of the signaling point on CMP with
database probe to see if it is 0
Possible
Solution
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.
p_RcvMSReleaseOrder
TABLE 8 ERR_SPS_RLS A_BSS AP_FCHSETUP_RCVMSRELEASEORDER
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_Tfch
setup
TABLE 9 ERR_SPS_RLS A_BSS AP_TE_TFCHSETUP
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
1. Check the lifecycle of the predefined timer Tfchsetup,
if it expires too soon, change the default value to 5000.
Possible
Solution
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.
T A B L E 1 0 E R R _ S P S _ R L S A _ B S S AP _ T E _ T 3 0 3
Failure
Name
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 A B L E 1 1 E R R _ S P S _ R L S A _ B S S AP _ T E _ 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.
ERR_SPS_RLSA_BSSAP_DB_Get
BoardOrIndexNetAddrByLogicAddr
T A B L E 1 2 E R R _ S P S _ R L S A _ B S S AP _ D B _ G E T B O A R D O R I N D E X N E T A D D R
BYLOGICADDR
Failure
Name
ERR_SPS_RLSA_BSSAP_DB_GetBoardOrIndexNetAddrBy
LogicAddr
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.
p_ClearCommand_UserBusy
T A B L E 1 3 E R R _ S P S _ R L S A _ B S S AP _ F C H S E T U P _ C L E A R C O M M A N D _
USERBUSY
Failure
Name
ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_UserBu
sy
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:
Possible
Solution
Called users are busy
p_ClearCommand_NormalClearing
NORM ALCLEARING
Failure
Name
ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_Normal
Clearing
Failure
Cause
When a call is setup, BSC receives the ClearCommand

indicates it is a normal release.
Failure
Analysis
Likely cause:
Possible
Solution
release initiated at MSC side
ERR_SPS_RLSA_BSSAP_ByteInde
x_IndexInUsed
T A B L E 1 5 E R R _ S P S _ R L S A _ B S S AP _ B Y T E I N D E X _ I N D E X I N U S E D
Failure
Name
Failure
Cause
ERR_SPS_RLSA_BSSAP_ByteIndex_IndexInUsed
When a call is setup, BSSAP module detects that the
instance number is in use in instance number
distribution.
Failure
Analysis
Likely cause:
Possible
Solution
Check abnormal probe
BSSAP module records a wrong instance number
p_AllLegFail
T A B L E 1 6 E R R _ S P S _ R L S A _ B S S AP _ F C H S E T U P _ A L L L E G F A I L
Failure
Name
Failure
Cause
ERR_SPS_RLSA_BSSAP_FchSetup_AllLegFail
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.
Most likely cause:
1.CE resource shortage, CE resource is in wrong state
Failure
Analysis
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
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
Possible
Solution
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
Trouble
shootin
g
Make sure the software versions run on BSC and BTS are
the same.
p_ClearCommand_NoAnswer
NO ANSWER
Failure
Name
ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_NoAn
swer
Failure
Cause
When a call is setup, BSC receives the ClearCommand

indicates it rings without answer. This is normal.
Failure
Analysis
Likely cause:
Possible
Solution
This is normal
Nobody answers the release initiated by MSC
ERR_SPS_RLSA_BSSAP_UnexptM
sg_RcvOrgnInSessionState
T A B L E 1 8 E R R _ S P S _ R L S A _ B S S AP _ U N E X P T M S G _ R C V O R G N I N
SESSIONSTATE
Failure
Name
ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvOrgnInSessionSt
ate
Failure
Cause
During call status, the call establishment message is

received.
Failure
Analysis
Possible
Solution
Likely cause:
When users originate call, and the process does not
release the message, the call fails.
otherwise, further analysis is needed.
sg_RcvRegInAssignState_Others
T A B L E 1 9 E R R _ S P S _ R L S A _ B S S AP _ U N E X P T M S G _
RCVREGINASSIGNSTATE_OTHERS
Failure
Name
ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvRegInAssignState_O
thers
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

ERR_SPS_RLSA_BSSAP_HandSh
ake_TimeOut
T A B L E 2 0 E R R _ S P S _ R L S A _ B S S AP _ H A N D S H A K E _ T I M E O U 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
Further
Trouble
shootin
g
10
1. Check handset state

2. Check the foreground mp board of BSC
3. check timer setting
Check the running of DSPM module
sg_RcvRegInAssignState_PowerOn
RCVREGINASSIGNSTATE_POWERON
Failure
Name
ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvRegInAssignStat
e_PowerOn
Failure
Cause
power on registration message is received during a call
Failure
Analysis
Possible
Solution
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.
sg_RcvRegInAssignState_PowerDo
wn
RCVREGINASSIGNSTATE_POWERDOWN
Failure
Name
ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvRegInAssignStat
e_PowerDown
Failure
Cause
power off registration message is received during a call
Failure
Analysis
Possible
Solution
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.
depending on the terminal processing flow
11
ERR_SPS_RLSA_BSSAP_TgtBSC_
FunCallFail__TargetBSCHandlerEntr
y__A7HOReqMsgProccessForHOWi
th1X
T A B L E 2 3 E R R _ S P S _ R L S A _ B S S AP _ T G T B S C _ F U N C A L L F A I L _ _
T A R G E T B S C H A N D L E R E N T R Y _ _ A7 H O R E Q M S G P R O C C E S S F O R H O W I T H 1 X
Failure
Name
ERR_SPS_RLSA_BSSAP_TgtBSC_FunCallFail__TargetBSC
HandlerEntry__A7HOReqMsgProccessForHOWith1X
Failure
Cause
The target BSC interconnects with the Hirs BSC. The

handoff request processing is abnormal.
Failure
Analysis
Possible
Solution
1.The number of cell is greater than the maximum

number of cell that a call occupies
2. Neighbor cell is not configured.
1. Check interconnection configurations
2. If the PN configuration of neighbor cell is reasonable
or not
ERR_SPS_RLSA_BSSAP_Other_R
eceiveResetCircuit
T A B L E 2 4 E R R _ S P S _ R L S A _ B S S 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
Failure
Cause
Failure
Analysis
Possible
Solution
Further
Trouble
shootin
g
12
ERR_SPS_RLSA_BSSAP_Other_ReceiveResetCircuit
When a call or a hard handoff adding is being
established, the circuit reset message sent from MSC is
received.
1. CIC state at MSC side and BSC side is different
2. CIC coding at MSC side and BSC side is different
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
Cooperate with MSC side to find out the cause
p_SendChannelAssignment_AllBtsF
ail
T A B L E 2 5 E R R _ S P S _ R L S A _ B S S AP _ F C H S E T U P _ S E N D C H A N N E L
ASSIGNMENT_ALLBTSFAIL
Failure
Name
ERR_SPS_RLSA_BSSAP_FchSetup_SendChannelAssignm
ent_AllBtsFail
Failure
Cause
When a call is setup, fail to send the Extended Channel

Assignment Message to all BTS
1. In ECAM/CAMmessage creation, no established cell is
found
2. In ECAM/CAMmessage creation, fail to retrieve power
parameters from database
Failure
Analysis
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 etc
address 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
13
p_ClearCommand_HandoffSuccessf
ul
HANDOFFSUCCESSFUL
Failure
Name
RR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_Hando
ffSuccessful
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
Possible
Solution
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
If the failure occurs when a call is being setup, cooperate
with MSC side for troubleshooting.
ERR_SPS_RLSA_BSSAP_TgtBSC_
Other__TargetBSCHandler_A7fHan
doffRequestProccess__RecievedA7
HOReqWhenSemiHO
T A B L E 2 7 E R R _ S P S _ R L S A _ B S S AP _ T G T B S C _ O T H E R _ _
TARGETBSCHANDLER_ A7FHANDOFFREQUESTPROCCESS__RECIEVED A7HOR
EQWHENSEMIHO
14
Failure
Name
ERR_SPS_RLSA_BSSAP_TgtBSC_Other_TargetBSCHandl
er_A7fHandoffRequestProccess_RecievedA7HOReqWhen
SemiHO
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

otherwise, check the BSC at source side.
p_ClearCommand_SemiConcurrent
Service
SEMICONCURRENTSERVICE
Failure
Name
ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_Semi
ConcurrentService
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 A B L E 2 9 E R R _ S P S _ R L S A _ B S S AP _ M S G P A R A _ O R I G I N A T I O N _
INVALIDSERVICEOPTION
Failure
Name
ERR_SPS_RLSA_BSSAP_MsgPara_Origination_InvalidSer
viceOption
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.
15
ERR_SPS_RLSA_BSSAP_HashOpr
_AddItem_SccpId2CallRef
T A B L E 3 0 E R R _ S P S _ R L S A _ B S S AP _ H A S H O P R _ A D D I T E M _
SCCPID2CALLREF
Failure
Name
ERR_SPS_RLSA_BSSAP_HashOpr_AddItem_SccpId2Call
Ref
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_G
et97DMTMsParaFail
T A B L E 3 1 E R R _ S P S _ R L S A _ B S S AP _ O T H E R _ G E T 9 7 D M T M S P A R A F A I L
16
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.
p_ClearCommand_EquipmentFailur
e
EQUIPMENTFAILURE
Failure
Name
ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_Equip
mentFailure
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

otherwise, cooperate with MSC side to find out the cause
p_ClearCommand_AuthenticationFai
lure
AUTHENTICATIONFAILURE
Failure
Name
ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_Auth
enticationFailure
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
17
18
Chapter
DSPM Related Failures

This chapter introduces and describes failures related to DSMP
and also discusses about possible troubleshooting methods.
ERR_SPS_RLSA_DSPM_CLH_Oth
erReason_MSNormalRelease
TABLE 34 ERR_SPS_RLSA_DSPM_CLH_OTHERREASON_
MSNORM ALRELEASE
Failure
Name
ERR_SPS_RLSA_DSPM_CLH_OtherReason_MSNormalRel
ease
Failure
Cause
Normal call release autonomously initiated by handset
Failure
Analysis
Normal release
Possible
Solution
Normal release
19
ERR_SPS_RLSA_DSPM_CLH_Tim
erExpired_Twaitorder
TABLE 35 ERR_SPS_RLSA_DSPM_CLH_TIMEREXPIRED_TWAITORDER
Failure
Name
Failure
Cause
ERR_SPS_RLSA_DSPM_CLH_TimerExpired_Twaitorder
When MS originates a call or be called,after successfully
entering traffic channel and capturing the prefix, airinterface traffic channel signaling handshake expires.
Most likely causes:
Failure
Analysis
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.
1. Check transmission power of the cell
2. Check the version compatibility and running of CHM
and SDU board
Possible
Solution
Further
Trouble
shootin
g
20
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
Check the versions and running of ABPM, DTB and DSM
Chapter 2 DSPM Related Failures
erReason_SNFailure
TABLE 36 ERR_SPS_RLSA_DSPM_CLH_OTHERREASON_SNFAILURE
Failure
Name
Failure
Cause
ERR_SPS_RLSA_DSPM_CLH_OtherReason_SNFailure
When MS originates a call or be called, after entering
traffic channel, the service negotiation between base
station and MS fails
Most likely cause:
Failure
Analysis
1. Poor radio condition causes air-interface negotiation

occasionally.
2. VTC working mode setting in BSS has a problem
1. Check the forward power of the cell
Possible
Solution
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
Trouble
shootin
g
If the problem remains, capture the call failure signaling

and contact the ZTE office
erReason_MSPowerDown
TABLE 37 ERR_SPS_RLSA_DSPM_CLH_OTHERREASON_MSPOWERDOWN
Failure
Name
ERR_SPS_RLSA_DSPM_CLH_OtherReason_MSPowerDow
n
Failure
Cause
Call release initiated by handset power off
Failure
Analysis
Normal release
Possible
Solution
Normal release
21
ERR_SPS_RLSA_DSPM_CLH_Tim
erExpired_Tpcfinfol3
TABLE 38 ERR_SPS_RLSA_DSPM_CLH_TIMEREXPIRED_TPCFINFOL3
Failure
Name
Failure
Cause
Failure
Analysis
ERR_SPS_RLSA_DSPM_CLH_TimerExpired_Tpcfinfol3
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
Most likely cause:
1. Tpcfinfol3timer setting has a problem
2. corresponding SDU runs abnormally
1. If the setting of Tpcfinfol3timer on DSMP board is
correct (default value is 3s
Possible
Solution
Further
Trouble
shootin
g
22
2. Check the corresponding SDU when the problem

occurs. Make sure if there is abnormal reset or
switchover.
Check the version and running status of SDU
ERR_SPS_RLSA_DSPM_SCHH_Ot
herReason_SCHHOnUmrSCHRequ
estMsg_ReleasebyMSDTXTime
TABLE 39 ERR_SPS_RLSA_DSPM_SCHH_OTHERREASON_
SCHHONUMRSCHREQUESTMSG_RELEASEBYMSDTXTIME
Failure
Name
ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnUm
rSCHRequestMsg_ReleasebyMSDTXTime
Failure
Cause
RSCH DTXTime release initiated by handset
Failure
Analysis
Normal release
Possible
Solution
Normal release
herReason_SCHHOnAbarSCHRem
oveIndication_RSCHReleasebySDM
DTXTime
SCHHON ABARSCHREMOVEINDICATION_RSCHRELEASEBYSDMDTXTIME
Failure
Name
ERR_SPS_RLSA_DSPM_SCHH_OtherReason
_SCHHOnAbarSCHRemoveIndication_RSCHReleasebySD
MDTXTime
Failure
Cause
RSCH DTXTime release initiated by SDM
Failure
Analysis
Normal release
Possible
Solution
Normal release
23
herReason_SCHHPNDropIndication
_ReleasebyHOH
SCHHPNDROPINDICATION_RELEASEBYHOH
Failure
Name
ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHPNDro
pIndication_ReleasebyHOH
Failure
Cause
SCH release triggered by soft Hand Off remove on

fundamental channel
Failure
Analysis
Normal release
Possible
Solution
Normal release
herReason_SCHHOnAbisdrBurstRel
ease_RSCHExistedCellReleasebyR
CM
SCHHON ABISDRBURSTRELEASE_RSCHEXISTEDCELLRELEASEBYRCM
24
Failure
Name
ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnAbi
sdrBurstRelease_RSCHExistedCellReleasebyRCM
Failure
Cause
RSCH release initiated at BTS side
Failure
Analysis
Normal release
Possible
Solution
Normal release
herReason_SCHHRelease_Release
byCLH
SCHHRELEASE_RELEASEBYCLH
Failure
Name
ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHReleas
e_ReleasebyCLH
Failure
Cause
SCH release triggered by call release
Failure
Analysis
Normal release
Possible
Solution
Normal release
oveIndication_RSCHReleasebySDM
OtherReason
SCHHON ABARSCHREMOVEINDICATION_RSCHRELEASEBYSDMOTHERREASO
N
Failure
Name
ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnAba
rSCHRemoveIndication_
RSCHReleasebySDMOtherReason
Failure
Cause
SDM initiate RSCHOther causes release
Failure
Analysis
Normal release
Possible
Solution
Normal release
25
oveIndication_FSCHReleasebySDM
Duration
SCHHON ABARSCHREMOVEINDICATION_FSCHRELEASEBYSDMDURATION
Failure
Name
ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnAba
rSCHRemoveIndication_FSCHReleasebySDMDuration
Failure
Cause
When the SCH dispatch timer is timeout, SDM initiates

FSCH release
Failure
Analysis
Normal release
Possible
Solution
Normal release
herReason_SCHHFSCHHandoff_Ha
rdHandoff
SCHHFSCHHANDOFF_HARDHANDOFF
Failure
Name
Failure
Cause
26
ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHFSCH
Handoff_HardHandoff
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
ERR_SPS_RLSA_DSPM_SCHH_Ti
merExpired_Tfschdrop
TABLE 47 ERR_SPS_RLSA_DSPM_SCHH_TIMEREXPIRED_TFSCHDROP
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
herReason_SCHHOnTfschdroppend
ing_ReleasebyTDropPending
SCHHONTFSCHDROPPENDING_RELEASEBYTDROPPENDING
Failure
Name
ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnTfs
chdroppending_ReleasebyTDropPending
Failure
Cause
release caused by FSCH due to timeout
Failure
Analysis
Normal release
Possible
Solution
Normal release
27
herReason_SCHHOnAbisdrBurstRel
ease_FSCHExistedCellReleasebyR
CM
SCHHON ABISDRBURSTRELEASE_FSCHEXISTEDCELLRELEASEBYRCM
Failure
Name
ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnAbi
sdrBurstRelease_FSCHExistedCellReleasebyRCM
Failure
Cause
FSCH release initiated at BTS side
Failure
Analysis
Normal release
Possible
Solution
Normal release
erReason_PCFEquipmentFailure
PCFEQUIPMENTFAILURE
Failure
Name
ERR_SPS_RLSA_DSPM_CLH_OtherReason_PCFEquipmen
tFailure
Failure
Cause
abnormal call release initiated by PCF
Failure
Analysis
Possible
Solution
Further
Trouble
shootin
g
28
Most likely cause:

1. corresponding PCFruns abnormally
2. A10 link establishing fails
1. Check the IMSI, HI and DI carried by
A9SetupA8message
2. When checking the handoff,A10 link establishing fails
Check the version and running of PCF board
erReason_MSGoingIntoDormant
MSGOINGINTODORM ANT
Failure
Name
ERR_SPS_RLSA_DSPM_CLH_OtherReason_MSGoingInto
Dormant
Failure
Cause
In data service, the call release autonomously initiated

by handset
Failure
Analysis
Normal release
Possible
Solution
Normal release
erReason_PCFNormalRelease
PCFNORM ALRELEASE
Failure
Name
ERR_SPS_RLSA_DSPM_CLH_OtherReason_PCFNormalRel
ease
Failure
Cause
In data service, the normal call release initiated by PCF
Failure
Analysis
Normal release
Possible
Solution
Normal release
29
ERR_SPS_RLSA_DSPM_HOH_Tim
erExpired_SoftHOThocompletion
TABLE 53 ERR_SPS_RLSA_DSPM_HOH_TIMEREXPIRED_
SOFTHOTHOCOMPLETION
Failure
Name
ERR_SPS_RLSA_DSPM_HOH_TimerExpired_SoftHOThoco
mpletion
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
Most likely cause:
Failure
Analysis
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
Further
Trouble
shootin
g
30
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
erExpired_Thoreq
TABLE 54 ERR_SPS_RLSA_DSPM_HOH_TIMEREXPIRED_THOREQ
Failure
Name
ERR_SPS_RLSA_DSPM_HOH_TimerExpired_Thoreq
Failure
Cause
handoff request response expires

Most likely cause:
1. Abis\A3A7 interface link is faulty
Failure
Analysis
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
1. Check the setting of Thoreqtimer on DSMP board
default value is 5s
Possible
Solution
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
Trouble
shootin
g
Check the version and running of CCM board
31
ERR_SPS_RLSA_DSPM_HOH_Res
NotSatisfied_HOHOnUmrCFSearch
Report
TABLE 55 ERR_SPS_RLSA_DSPM_HOH_RESNOTSATISFIED_
HOHONUMRCFSEARCHREPORT
Failure
Name
ERR_SPS_RLSA_DSPM_HOH_ResNotSatisfied_HOHOnUm
rCFSearchReport
Failure
Cause
In semi-soft handoffs, the handoff at target side fails.

Most likely cause:
Failure
Analysis
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
Trouble
shootin
g
ERR_SPS_RLSA_DSPM_HOH_Oth
erReason_AbisdHandShakeFailure
TABLE 56 ERR_SPS_RLSA_DSPM_HOH_OTHERREASON_
ABISDHANDS HAKEF AILURE
Failure
Name
ERR_SPS_RLSA_DSPM_HOH_OtherReason_AbisdHandSh
akeFailure
Failure
Cause
During a call, handshake between DSPM and RCM fails. A

call release is initiated
Most likely cause:
Failure
Analysis
Possible
Solution
32
1.The RCM, ABPM correspond to BTS run abnormally

2. the setting of Tphysicaltimer on DSMP board has a
problem
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.
Further
Trouble
shootin
g
Check the versions and running status of CCM and ABPM
ERR_SPS_RLSA_DSPM_SCHH_Ti
merExpired_Tfschbstreq
TABLE 57 ERR_SPS_RLSA_DSPM_SCHH_TIMEREXPIRED_TFSCHBSTREQ
Failure
Name
Failure
Cause
Failure
Analysis
Possible
Solution
Further
Trouble
shootin
g
ERR_SPS_RLSA_DSPM_SCHH_TimerExpired_Tfschbstreq
In FSCH establishment, after BSC sending the
BurstRequestmessage, Tfschbstreqtimer expires and the
BurstResponsemessage from BTS is not received.
Most likely cause:
Message is missing at Abis interface. It is acceptable if
this problem occurs occasionally.
1. Check Tfschbstreqtimer setting500ms
2. Make sure if the message is missing or not
Check the versions and running status of CCM, ABPM,
DTB and DSM
33
erReason_PDSNDenied_Reason_U
nspecified
TABLE 58 ERR_SPS_RLSA_DSPM_CLH_OTHERREASON_PDSNDENIED_
REASON_UNSPECIFIED
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.
Most likely cause:
Failure
Analysis
Possible
Solution
1. A10link establishing fails

2. Check the corresponding PCF when the problem
occurs, Make sure if there is abnormal reset or
switchover.
check A10link to see if it is successfully established
erReason_OVERLOAD
TABLE 59 ERR_SPS_RLSA_DSPM_CLH_OTHERREASON_OVERLO AD
34
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
Trouble
shootin
g
Add DSMP board
erReason_Ta8setup
TABLE 60 ERR_SPS_RLSA_DSPM_CLH_OTHERREASON_TA8SETUP
Failure
Name
Failure
Cause
ERR_SPS_RLSA_DSPM_CLH_OtherReason_Ta8setup
establishing expires: DSPM sends the
A9SetupA8message to PCF, no reply message is
received in Ta8setup3s
Most likely cause:
Failure
Analysis
1.In OMC,PCF IP address configuration has problem

2.Physical link breaks
3.corresponding PCF is faulty
1.If the setting of Ta8setup timer default value is 3s
on DSMP board is correct or not
Possible
Solution
2. Check the PCF IP address configuration in OMC and

the physical link
occurs, Make sure if there is abnormal reset or
switchover.
erReason_Tshakehandrecv
TSHAKEHANDRECV
Failure
Name
ERR_SPS_RLSA_DSPM_CLH_OtherReason_Tshakehandre
cv
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.
Most likely cause:
Failure
Analysis
Possible
Solution
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.
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.
35
erExpired_SemiSoftHOThocompletio
n
TABLE 62 ERR_SPS_RLSA_DSPM_HOH_TIMEREXPIRED_
SEMISOFTHOTHOCOMPLETION
Failure
Name
ERR_SPS_RLSA_DSPM_HOH_TimerExpired_SemiSoftHOT
hocompletion
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.
Most likely cause:
Failure
Analysis
1. Poor radio condition causes air-interface handshake

occasionally.
2. If frame number checking is enabled, BTS and BSC
have different clocks
3. Other causes: e.g. bit error
Possible
Solution
Further
Trouble
shootin
g
36
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.
ERR_SPS_RLSA_DSPM_HOH_Res
NotSatisfied_HOHOnA7rHOReqAck
TABLE 63 ERR_SPS_RLSA_DSPM_HOH_RESNOTSATISFIED_
HOHON A7RHOREQ ACK
Failure
Name
ERR_SPS_RLSA_DSPM_HOH_ResNotSatisfied_HOHOnA7r
HOReqAck
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
1.Check Abis\A3A7 interface link
Possible
Solution
Further
Trouble
shootin
g
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
Check the version and running of CCM board
37
erReason_PDSNDenied_Reason_A
dministratively_Pohibited
TABLE 64 ERR_SPS_RLSA_DSPM_CLH_OTHERREASON_PDSNDENIED_
REASON_ ADMINISTRATIVELY_POHIBITED
Failure
Name
Failure
Cause
ERR_SPS_RLSA_DSPM_CLH_OtherReason
_PDSNDenied_Reason_Administratively_Pohibited
establishing fails, when the cause value PDSN brings to
DSPM is 0x81, the failure cause reported by DSPM.
Most likely cause:
Failure
Analysis
Possible
Solution
1. A10 link establishing fails

switchover.
check A10 link to see if it is successfully established
erReason_PCFDenied_PDSN_Reso
urce_Unavailable
TABLE 65 ERR_SPS_RLSA_DSPM_CLH_OTHERREASON_PCFDENIED_
PDSN_RESOURCE_UNAV AILABLE
Failure
Name
ERR_SPS_RLSA_DSPM_CLH_OtherReason_PCFDenied_P
DSN_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
1. Check A10 link to see if is successful established
Possible
Solution
38
2. Check the corresponding PDSN when the problem

switchover.
herReason_SCHHReleaseRSCHbyL
egFail_ReleaseRschExistSDMLegFa
ilure
SCHHRELEASERSCHBYLEGFAIL_RELEASERSCHEXISTSDMLEGFAILURE
Failure
Name
ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHReleas
eRSCHbyLegFail_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:
Possible
Solution
Check Abis interface
SDM has no reverse frames
herReason_SCHHOnUmrSCHRequ
estMsg_FCHNotExisted
SCHHONUMRSCHREQUESTMSG_FCHNOTEXISTED
Failure
Name
ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnUm
rSCHRequestMsg_FCHNotExisted
Failure
Cause
Data service fundamental channel receives a message

from SCH for setup.
Failure
Analysis
Most likely cause:
Possible
Solution
This failure is acceptable
call origination flow does not complete
39
40
Chapter
SDM Related Failures

This chapter introduces and describes call failures related to
SDM and also discusses about possible troubleshooting methods.
SDM_Activate_Fail_AcquirePreambl
eFail_Normal
TABLE 68 SDM_ACTIV ATE_FAIL_ ACQUIREPREAMBLEFAIL_NORM AL
Failure
Name
SDM_Activate_Fail_AcquirePreambleFail_Normal
Mobile establishing fails; BSC has not received Preamble
sent by the mobile before timeout, but Idle frame can be
received.
Failure
Cause
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.
1. Check CHM version
Possible
Solution
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.
41
SDM_Activate_Fail_AcquirePreambl
eFail_NoRevFrm
TABLE 69 SDM_ACTIV ATE_FAIL_ ACQUIREPREAMBLEFAIL_NOREVFRM
Failure
Name
SDM_Activate_Fail_AcquirePreambleFail_NoRevFrm
Mobile connection establishment fails; BSC has not
received reverse traffic frame sent by BTS before timer
is timeout.
Failure
Cause
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.
1. Check if Abis link is disconnected.
Possible
Solution
2.Check if adding channel list (BSC and BTS side) in

signaling tracing is successful
3. Check if there are CE suspended in CHM
42
Chapter 3 SDM Related Failures
SDM_Find_Fail_WaitConfigVTCTim
eout
TABLE 70 SDM_FIND_FAIL_W AITCONFIGVTCTIMEOUT
Failure
Name
SDM_Find_Fail_WaitConfigVTCTimeout
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:
Failure
Cause
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.
1.Check if there are handshake messages
EV_S_UmfBSOrder and EV_S_UmrMSOrder of traffic
channel
Possible
Solution
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.
43
SDM_Link_Fail_RevNoFrm
TABLE 71 SDM_LINK_FAIL_REVNOFRM
Failure
Name
SDM_Link_Fail_RevNoFrm
Link failure. SDM can not receive traffic frame sent from
BTS during a period (default time is 18s).
Failure
Cause
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_RevTooManyBadFr
m
TABLE 72 SDM_LINK_FAIL_REVTOOM ANYBADFRM
Failure
Name
SDM_Link_Fail_RevTooManyBadFrm
Link failure. SDM receives from BTS side almost all error
frame during a period (default time is 18s).
Failure
Cause
Possible
Solution
44
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.
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.
SDM_Link_Fail_FwdA2pNoFrm
TABLE 73 SDM_LINK_FAIL_FWD A2PNOFRM
Failure
Name
SDM_Link_Fail_FwdA2pNoFrm
SDM can not receive traffic frame sent from MGW during
a period (default time is 18s)
Failure
Cause
Possible
Solution
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.
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_WaitConfigRLPTim
eout
TABLE 74 SDM_FIND_FAIL_W AITCONFIGRLPTIMEOUT
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.
45
SDM_Link_Fail_RSCHLegLinkFail
TABLE 75 SDM_LINK_FAIL_RSCHLEGLINKFAIL
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_FwdA2pTooManyEr
rEncodeFrm
TABLE 76 SDM_LINK_FAIL_FWD A2PTOOM ANYERRENCODEFRM
Failure
Name
SDM_Link_Fail_FwdA2pTooManyErrEncodeFrm
Inadequate good frame is received from MGW within
18s. Possible reasons are:
Failure
Cause
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
46
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.
SDM_Activate_Fail_InitVocoderFail
TABLE 77 SDM_ACTIV ATE_FAIL_INITVOCODERFAIL
Failure
Name
Failure
Cause
Possible
Solution
SDM_Activate_Fail_InitVocoderFail
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.
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_WaitStartVo
coderCodingAckTimeOut
TABLE 78 SDM_OPRVOCODER_FAIL_W AITSTARTVOCODERCODINGACK
TIMEOUT
Failure
Name
SDM_OprVocoder_Fail_WaitStartVocoderCodingAckTime
Out
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.
47
SDM_Find_Fail_NoFCHLeg
TABLE 79 SDM_FIND_FAIL_NOFCHLEG
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
TABLE 80 SDM_ACTIV ATE_FAIL_MSGP ARAF AIL
48
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.
Chapter
DBS Related Failures

This chapter introduces and describes call failures related to DBS
DBS_STASTIC_FWDFCHCE_REVC
E_LACK
TABLE 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.
Check failure reason submitted in abnormality probe.
Possible
Solution
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.
49
DBS_STASTIC_FWDFCHCE_LACK
TABLE 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_LAC
K
TABLE 83 DBS_STASTIC_W ALSHCODE_LACK
Failure
Name
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
50
DBS_STASTIC_WALSHCODE_LACK
1. Check failure reasons submitted in abnormality probe.

2. Check if there is free resource in WALSHCODE using
probe.
Chapter 4 DBS Related Failures
DBS_STASTIC_UID_LACK
TABLE 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_L
ACK
TABLE 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.
51
FCH_NUMBER_TWO
TABLE 86 FCH_NUMBER_TWO
Failure
Name
FCH_NUMBER_TWO
Failure
Cause
While supplementary channel is being set up, subscriber

has two basic data channels.
Failure
Analysis
Main reason for this failure is:
Possible
Solution
Further
Trouble
shootin
g
subscriber is under semi soft handoff status

As it is stipulated, setting up supplementary channel is
not permitted when subscriber is under semi soft handoff
status. BTS resource distribution return error will not be
influenced.
Ask DSPM and RCM to solve the problem of originating
supplementary channel setup in semi soft handoff status.
ARRIVE_TIME_ERROR
T A B L E 8 7 AR R I V E _ T I M E _ E R R O R
Failure
Name
Failure
Cause
Failure
Analysis
52
ARRIVE_TIME_ERROR
Channel board is too late to be configured in the period
before supplementary channel starts during
supplementary channel confirmation.
The main reasons for this failure are:
1. Link delay on Abis port is too long.
2. Clocks of BTS and BSC are different.
Possible
Solution
Solve clock problem of BTS and BSC.
Further
Trouble
shootin
g
Optimize link delay on Abis port
NO_SYSTEM_TIME
TABLE 88 NO_SYSTEM_TIME
Failure
Name
NO_SYSTEM_TIME
Failure
Cause
CCM DBS has no system time during reserving

supplementary channel resource.
Failure
Analysis
HIRS platform probably does not send system time to

CCM because of instantaneous CHM failure. IP platform
SCS does not send system time to DBS.
Possible
Solution
It usually appears during system reset.
INPUT_PARA_ERROR
TABLE 89 INPUT_P AR A_ ERROR
Failure
Name
INPUT_PARA_ERROR
Failure
Cause
Input parameter error

Failure
Analysis
HIRS platform probably does not send system time to

CCM because of instantaneous CHM failure. IP platform
SCS does not send system time to DBS.
Possible
Solution
It usually appears during system reset.
53
POWER_NOT_ENOUGH
TABLE 90 POWER_NOT_ENOUGH
Failure
Name
POWER_NOT_ENOUGH
Failure
Cause
Inadequate power
Carrier power surpasses threshold for supplementary
channel setup;
Failure
Analysis
Residual power is not able to set up a forward

supplementary channel with a rate of over 2X;
Subscriber radio condition is relatively poor; the required
power surpasses the maximum transmission power of
supplementary channel set by OMC.
Possible
Solution
Increase capacity
SOFTADD_CELL_ERROR
TABLE 91 SOFT ADD_CELL_ERROR
Failure
Name
Failure
Cause
SOFTADD_CELL_ERROR
Continuous transmission or softer add for reverse
supplementary channel, cell of DBS given by RCM has
error.
Failure
Analysis
Possible
Solution
54
1. Lost of release message may cause this abnormality,

but the possibility is comparatively small;
2. When basic channel undergoes handoff, as BSC
handoff is completed early, setup application for
supplementary channel reaches BTS before BTS basic
channel handoff completes, which is caused by flow; the
possibility is comparatively large.
Changing flow is suggested. Supplementary channel
module of DSPM makes SCH setup application after FCH
module handoff is finished.
NO_AVAILABLE_REV_CE
T A B L E 9 2 N O _ AV A I L A B L E _ R E V _ C E
Failure
Name
NO_AVAILABLE_REV_CE
Failure
Cause
No available reverse CE when setting up reverse

supplementary channel.
Failure
Analysis
The main reason for this failure is inadequate CE
Possible
Solution
Increase capacity
FO_NOT_ENOUGH
TABLE 93 FO_NOT_ENOUGH
Failure
Name
FO_NOT_ENOUGH
Failure
Cause
No available frame offset when setting up reverse

complementary channel.
Failure
Analysis
Possible
Solution
Inadequate frame offset; because frame offset of reverse

supplementary channel is the same with FCH, maybe
FCH has comparatively more data on the same frame
offset, and reverse supplementary channels have been
set up.
Increase capacity
55
CE_NOT_ENOUGH
TABLE 94 CE_NOT_ENOUGH
Failure
Name
CE_NOT_ENOUGH
Failure
Cause
No forward supplementary channel CE available when

forward supplementary channel is being set up.
Failure
Analysis
Possible
Solution

Too many forward supplementary channels are set up so
that forward supplementary channels CE are insufficient.
Increase capacity
WALSHCODE_NOT_ENOUGH
TABLE 95 WALSHCODE_NOT_ENOUGH
Failure
Name
WALSHCODE_NOT_ENOUGH
Failure
Cause
No Walsh code available when forward supplementary

channel is being set up.
Failure
Analysis
Possible
Solution
56

Too many forward supplementary channels are set up so
that Walsh code is insufficient
Increase capacity
BEFORE_CPS
TABLE 96 BEFORE_CPS
Failure
Name
Failure
Cause
BEFORE_CPS
Application is done too early during process of dispatch
continuous transmission of forward supplementary
channel
Failure
Analysis
Possible
Solution
Check GCM board to confirm there is no alarm
Different system clocks of BTS and BSC.
UIDWIDTH_NOT_ENOUGH
TABLE 97 UIDWIDTH_NOT_ENOUGH
Failure
Name
UIDWIDTH_NOT_ENOUGH
Failure
Cause
UID bandwidth is insufficient during resource distribution

of supplementary channel
Failure
Analysis
The main reason for this failure is:
Possible
Solution
Increase capacity
Insufficient Abis bandwidth
57
RS_NOT_EXIST
TABLE 98 RS_NOT_EXIST
Failure
Name
RS_NOT_EXIST
Failure
Cause
Records to which RS list corresponds is unavailable

during resource distribution of supplementary channel
Failure
Analysis
The main reason for this failure is scheduling algorithm

of supplementary channel; subscriber A of
supplementary channel needs to reserve another
subscriber B of supplementary channel because of
scheduling; however, afterwards subscriber A data FCH
is released and actually FCH no longer exists when
supplementary channel is set up. Therefore, there is no
corresponding record in RS list.
Possible
Solution
Supplementary channel that is reserved at present

cannot be set up because data is released by subscriber.
This is normal situation that does not need settlement.
ALLOCATE_UID_ERROR
TABLE 99 ALLOC ATE_UID_ERROR
58
Failure
Name
ALLOCATE_UID_ERROR
Failure
Cause
UID distribution fails during resource distribution of

supplementary channel.
Failure
Analysis
The main reason for this failure is :
Possible
Solution
Stabilize UID status
Instantaneous UID failure
HO_STAT_PILOT_NO_SAME_FRE
Q
TABLE 100 HO_ST AT_PILOT_NO_S AM E_FREQ
Failure
Name
HO_STAT_PILOT_NO_SAME_FREQ
Failure
Cause
During handoff judge, as there is no suited frequency

under the pilot, target pilot aggregate can not be added.
Failure
Analysis
Possible
Solution
1. For soft handoff, this reason value means there is no

suitable frequency under the pilot; this ought not to
occur, because if there is no suitable carrier, Level Three
should not submit it; if this do occurs, then it is failure.
2. For semi-soft and hard handoff, the carrier with the
smallest transmission power in the first pilot is selected
as the fundamental carrier, therefore for other pilots
there probably is no such carrier, and it is normal to
submit the reason.
For soft handoff, check if frequency for soft handoff is
configured under PN that is to be added.
HO_STAT_CARRIER_PWR_OVER
LOAD
TABLE 101 HO_ST AT_C ARRIER_PWR_OVERLO AD
Failure
Name
HO_STAT_CARRIER_PWR_OVERLOAD
Failure
Cause
Power of the selected carrier is overloaded
Failure
Analysis
Possible
Solution
During handoff judge, the power of the selected carrier is

overloaded. The reason for this failure is:
The carrier has too many subscribers.
Lower the subscriber quantity of every carrier.
59
HO_STAT_CARRIER_STATE_ERR
OR
TABLE 102 HO_ST AT_C ARRIER_STATE_ERROR
Failure
Name
HO_STAT_CARRIER_STATE_ERROR
Failure
Cause
Abnormal status of selected carrier

During handoff judge, power status of the selected
carrier is abnormal. Status field is status in rbcarrier
list on dsmp/cmp, meaning of which is:
Failure
Analysis
Bit1=0/1 Manual unblocking/ manual blocking

Bit2=0/1 Failure unblocking/ failure blocking
Bit3=0/1 RFE_DUP low power alarm unblocking carrier/
RFE_DUP low power alarm blocking carrier
Bit4=0/1 two BDSs are normal
BDSs.
Possible
Solution
Identify any probable broken links between two
Handle differently according to detail situation of

status.
HO_STAT_CARRIER_NO_CE
TABLE 103 HO_ST AT_C ARRIER_NO_CE
60
Failure
Name
HO_STAT_CARRIER_NO_CE
Failure
Cause
There is no CE in the selected carrier.
Failure
Analysis
CE resource to which the carrier corresponds has been

used up or blocked
Possible
Solution
1. Check if there is CE blocked.

2. Decrease subscriber quantity for every carrier.
HO_STAT_CARRIER_NO_5KCE
TABLE 104 HO_ST AT_C ARRIER_NO_5KCE
Failure
Name
HO_STAT_CARRIER_NO_5KCE
Failure
Cause
No 5k channel board CE for selected carrier.
Failure
Analysis
Possible
Solution
5k channel board CE resource to which the carrier

corresponds has been used up or blocked, but there is
15 channel board CE.
1. Check if there is 5k CE blocked.
2. Decrease subscriber quantity for every carrier.
HO_STAT_PILOT_IS_NOT_NEIGH
BOR
TABLE 105 HO_ST AT_PILOT_IS_NOT_NEIGHBOR
Failure
Name
HO_STAT_PILOT_IS_NOT_NEIGHBOR
Failure
Cause
PN is not configured as neighboring cell.
Failure
Analysis
PN is not configured as neighboring cell with active set,

with no record in link cell.
Possible
Solution
Check if PN has been configured in neighboring cell of

the cell.
61
HO_STAT_DESTBSC_IS_HIRS_DA
TASOFTHO
TABLE 106 HO_ST AT_DESTBSC_IS_HIRS_DAT AS OFTHO
Failure
Name
HO_STAT_DESTBSC_IS_HIRS_DATASOFTHO
Failure
Cause
HGM does not support soft handoff within BSC with data
service.
Failure
Analysis
HGM does not support soft handoff within BSC with data
service.
Possible
Solution
IP BSC and HIRS BSC dont support soft handoff within

BSC with data service.
IP BSC and HIRS BSC support soft handoff within BSC
with data service only when IBBE board is used.
HO_STAT_PILOT_NOT_LOCALBS
S
TABLE 107 HO_ST AT_PILOT_NOT_LOC ALBSS
62
Failure
Name
HO_STAT_PILOT_NOT_LOCALBSS
Failure
Cause
PN is not of the BSC.
Failure
Analysis
Remove the other BSC PN while constructing hard

handoff inside BSC
Possible
Solution
Normal flow
HO_STAT_PILOT_IS_OTHER_UNL
NKBSS
TABLE 108 HO_ST AT_PILOT_IS_OTHER_UNLNKBSS
Failure
Name
HO_STAT_PILOT_IS_OTHER_UNLNKBSS
Failure
Cause
HO_STAT_PILOT_IS_OTHER_UNLNKBSS
Failure
Analysis
If pilot is neither in the BSC or in the other

interconnected BSC
Possible
Solution
Check neighboring configuration of the cell.
BSC_NO_CIC
TABLE 109 BSC_NO_CIC
Failure
Name
BSC_NO_CIC
Failure
Cause
System has no CIC (ground circuit) resource available.
Failure
Analysis
No CIC resource available: CIC resource configuration

error, CIC resource status is abnormal or insufficient CIC
resource
1. Check the correctness of ground circuit (CIC)
configuration of port A.
a) Check the correctness of PCM configuration at port A,
and notice it should be the same as PCM NO.
Configuration on MSS side.
b) Check whether trunk configuration is correct and
notice it should be the same as that of time slot on MSS
side.
Possible
Solution
c) Check whether the DT board to which CIC corresponds

is correctly attributed to RMP module.
2. Check whether DT board to which CIC corresponds
operates normally and whether it is of correct version.
3. Check whether E1 physical connection to which CIC
corresponds is correct.
4. Check whether CIC resource is manually blocked in
dynamic management.
5. Check whether CIC resource quantity meets needs for
traffic capacity.
63
BSC_NO_SE
TABLE 110 BSC_NO_SE
Failure
Name
BSC_NO_SE
Failure
Cause
The system does not have available SE resource.
Failure
Analysis
No SE resource available: SDU configuration error, SE

resource status is abnormal or SE resource is
insufficient.
1. Check if 1XSDU board is correctly configured.
2. Check whether SDU board operates normally and
whether its version is correct.
Possible
Solution
3. For the situation that AP interface is embedded in

RTP, checks if SDU virtual address configuration is
correct.
4. Check if the status of daughter card of SDU board and
of INDEX is normal in dynamic management.
5. Check if SE resource quantity meets the needs of
traffic capacity.
BSC_NO_VE
TABLE 111 BSC_NO_VE
Failure
Name
BSC_NO_VE
Failure
Cause
The system has no available VE resource.
Failure
Analysis
No VE resource available: VTC configuration error,

abnormal VE resource status or insufficient VE resource.
1. Check if the resource frame where CIC is configured
correctly with corresponding quantity of VTC boards.
Possible
Solution
2. Check whether VTC board operates normally and

whether CPU/DSP version is correct.
3. Check if VTC board and INDEX status is normal in
dynamic management.
4. Check whether VE resource quantity meets the needs
of traffic capacity.
64
BSC_NO_IWF
TABLE 112 BSC_NO_IWF
Failure
Name
BSC_NO_IWF
Failure
Cause
The system has unavailable IWF resource.
Failure
Analysis
IWF resource unavailable: IWF configuration error,

abnormal IWF resource status or insufficient IWF
resource
1. Check whether IWFB board is correctly configured;
especially in the situation of not selecting CIC, check if
IWFB boards are configured in resource frame where CIC
is.
Possible
Solution
2. Check whether IWFB board operates normally and

whether CPU/DSP version is correct.
3. Check whether the status of IWFB board and INDEX is
normal in dynamic management.
4. Check whether IWF resource quantity meets the
needs of traffic capacity.
BSC_DSPM_NO_INSTANCE
T A B L E 1 1 3 B S C _ D S P M _ N O _ I N S T AN C E
Failure
Name
BSC_DSPM_NO_INSTANCE
Failure
Cause
The system has unavailable DSPM examples
Failure
Analysis
DSPM examples unavailable: DSPM configuration error,

DSPM status abnormal or insufficient DSPM examples
1. Check if DSPM module is correctly configured, and
whether corresponding quantity of DSPM examples are
configured.
Possible
Solution
2. Check if MP daughter card where DSPM module is

operates normally and whether its version is correct.
3. Check module list in probe view, and check if DSPM is
in normal status.
4. Check if the quantity of DSPM examples meets the
needs of traffic capacity.
65
BSC_NO_RTPPORT
TABLE 114 BSC_NO_RTPPORT
Failure
Name
BSC_NO_RTPPORT
Failure
Cause
The system has unavailable RTPPORT resourceThis

failure reason is submitted only in the situation of
external RTP.
Failure
Analysis
Unavailable RTPPORT resource: configuration error,

abnormal status of RTP port or insufficient RTPPORT
resource.
1. For external RTP situation, check if IPI board and RTP
port are correctly configured.
Possible
Solution
2. Check whether IPI board where RTP port is operates

normally and whether its version is correct.
3. Check if the status of RTPPORT resource is normal
during dynamic management.
4. Check if RTPPORT resource quantity meets the needs
of traffic capacity.
BSC_NO_VALID_RMP
TABLE 115 BSC_NO_V ALID_RMP
Failure
Name
BSC_NO_VALID_RMP
Failure
Cause
The system has unavailable RMP module.
Failure
Analysis
Unavailable RMP module: RMP module configuration

error or abnormal RMP status.
1. Check whether RMP module is correctly configured in
the system.
Possible
Solution
2. Check whether MP daughter card where RMP module

is operates normally and whether its version is correct.
3. Check module list in probe view, and to check if RMP
module status is normal.
66
Chapter
RCM Related Failures

This chapter introduces and describes call failures related to RCM
ERR_SPS_RLSA_RCM_DBAccFail_
FCHResourceAllocate
T A B L E 1 1 6 E R R _ S P S _ R L S A_ R C M _ D B A C C F A I L _ F C H R E S O U R C E A L L O C A T E
Failure
Name
ERR_SPS_RLSA_RCM_DBAccFail_FCHResourceAllocate
Failure
Cause
When MS is called or calling, during FCH setting up, it

fails to apply for data base interface allocation resource.
The possible reasons are:
1. Input parameter mistake of using database
Failure
Analysis
2. CE resource is not enough or abnormal.

3. Walsh is not enough
4. FO is not enough
5. UID is not enough
1. Check failure reason in EV_S_AbisdrBTSSeupAck
message reported in signal tracing
0x5064: forward channel CE is not enough
0x5065: Reverse CE is not enough
Possible
Solution
0x5066: forward channel and reverse CE are all not

enough
2. After confirming failure reason, check if CHM board is
abnormal ( chipset and CE are normal or not)
3. If CHM and CCM are normal, it is possible that
resource hung up, big problem.
67
ERR_SPS_RLSA_RCM_PCALL_Ot
herReason_CEC_REMOVEREQ
T A B L E 1 1 7 E R R _ S P S _ R L S A_ R C M _ P C A L L _ O T H E R R E A S O N _ C E C _
REMOVEREQ
Failure
Name
ERR_SPS_RLSA_RCM_PCALL_OtherReason_CEC_REMOV
EREQ
The failure reason is: during call procedure, CHM board
requests to release current call after detecting no frame
in forward channel (The default time is 6s). That is CHM
does not receive SDU forward frame, then it will release
procedure. The possible reasons :
Failure
Cause
1.IP or MAC value is invalid

2.Key invalid value leads to searching table address
mistake
3.Channel table invalid position
4.SDM does not set up leg
5.The related DSP problem in VTC board
1.Check if there is SDM leg set up information in signal
Possible
Solution
68
2.Check IP and MAC value

3. If this problem occurs frequently, maybe DSP
problem.
Chapter 5 RCM Related Failures
ERR_SPS_RLSA_RCM_FCH_Timer
Expired_TconnExpired
T A B L E 1 1 8 E R R _ S P S _ R L S A_ R C M _ F C H _ T I M E R E X P I R E D _ T C O N N E X P I R E D
Failure
Name
Failure
Cause
ERR_SPS_RLSA_RCM_FCH_TimerExpired_TconnExpired
During call setup, when resource is set up, Abis interface
timer expires and leads to call release procedure, and
call failure happens. This timer is 4S. The radio resource
and service address in BTS side will tell BSC side to
trigger, if BSC Ack message is not received before
timeout, then BTS side will start release procedure. The
reason for BTS side not to receive Ack message also
maybe due to content mistake in BTS side message,
except for link and message block.
1.Check if Abis link is normal
Possible
Solution
2. Check parameter in AbisdrConnect message carried

by BTS side to BSC (mainly compared with
AbisdfBTSSetup), mainly important parameter are: cell
information in tAbisConnectInfo.
ERR_SPS_RLSA_RCM_RSCH_Oth
erReason_Release_RSCH
T A B L E 1 1 9 E R R _ S P S _ R L S A_ R C M _ R S C H _ O T H E R R E A S O N _ R E L E A S E _
RSCH
Failure
Name
ERR_SPS_RLSA_RCM_RSCH_OtherReason_Release_RSC
H
Failure
Cause
Release reverse SCH channel: Reverse SCH channel

release notified by database message.
Possible
Solution
Normal condition, no need for solution
69
ERR_SPS_RLSA_RCM_RSCH_Oth
erReason_Release_FSCH
T A B L E 1 2 0 E R R _ S P S _ R L S A_ R C M _ R S C H _ O T H E R R E A S O N _ R E L E A S E _
FSCH
Failure
Name
ERR_SPS_RLSA_RCM_RSCH_OtherReason_Release_FSC
H
Failure
Cause
Release forward SCH channel: forward SCH channel

release notified by database message.
Possible
Solution
ERR_SPS_RLSA_RCM_FSCH_Fun
CallFail_AddChannelFail
T A B L E 1 2 1 E R R _ S P S _ R L S A_ R C M _ F S C H _ F U N C A L L F A I L _
ADDCHANNELFAIL
Failure
Name
Failure
Cause
ERR_SPS_RLSA_RCM_FSCH_FunCallFail_AddChannelFail
During call setup, this failure occurs when IP platform
BTS adds channel table. The possible reason is that too
many channel tables are added at one time. Usually it
happens during data SCH channel setup.
If it happens in ordinary voice, the reason maybe
channel table hung up.
Possible
Solution
70
If it happens during data service procedure, it is normal

condition.
If one call does not add channel table at one time
(ordinary voice), that is resource hung up, please
contact ZTE local agent.
ERR_SPS_RLSA_RCM_SCHCOM
M_TimerExpired_Tsch
T A B L E 1 2 2 E R R _ S P S _ R L S A_ R C M _ S C H C O M M _ T I M E R E X P I R E D _ T S C H
Failure
Name
Failure
Cause
Possible
Solution
ERR_SPS_RLSA_RCM_SCHCOMM_TimerExpired_Tsch
During data service procedure, after SCH resource setup,
database configuration timer expires, waiting for the
acknowledgement.
Check if voice traffic is too heavy
ERR_SPS_RLSA_RCM_SCHCOM
M_TimerExpired_Tbstcomb
T A B L E 1 2 3 E R R _ S P S _ R L S A_ R C M _ S C H C O M M _ T I M E R E X P I R E D _ T B S T C O M B
Failure
Name
Failure
Cause
ERR_SPS_RLSA_RCM_SCHCOMM_TimerExpired_Tbstcom
b
During data service, BTS side SCH channel resource
allocation is finished, waiting for BSC side confirm, BSC
side confirm message timeout. following are the possible
reasons:
1.Confirm message lost
2. After BTS side allocates SCH channel resource, the
parameter in reply message to BSC side is wrong.
1.Check if Abis link is normal
Possible
Solution
2. Check if the parameter of AbisdrBurstResponse

message carried by BTS side to BSC side is corrected
(mainly compared with AbisdfBurstRequest); mainly, the
important parameter is the cell information.
71
ERR_SPS_RLSA_RCM_RSCH_Fun
CallFail_RevSCHSetupFail
T A B L E 1 2 4 E R R _ S P S _ R L S A_ R C M _ R S C H _ F U N C A L L F A I L _
REVSCHSETUPFAIL
Failure
Name
Failure
Cause
ERR_SPS_RLSA_RCM_RSCH_FunCallFail_RevSCHSetupF
ail
During data service, when SCH channel is setup and
database is in allocation, CHM board configuration fails
and reverse SCH channel is released. The reasons are
the following.
1.CHM board configuration message lost
2.CE of SCH in CHM is hung up
3. If there is no resource hung up in CHM, it is possible
that database has mistake in idle CE queue maintenance
1.Check if the CPU of CHM is in overload status
Possible
Solution
2.Check if CHM has CE hung up

3.Check OMC database probe, confirm if there is mistake
in CE idle queue of database maintenance
ERR_SPS_RLSA_RCM_FSCH_Fun
CallFail_FwdSCHSetupFail
T A B L E 1 2 5 E R R _ S P S _ R L S A_ R C M _ F S C H _ F U N C A L L F A I L _
FWDSCHSETUPFAIL
Failure
Name
Failure
Cause
ERR_SPS_RLSA_RCM_FSCH_FunCallFail_FwdSCHSetupF
ail
and forward SCH channel is released. The reasons are
the following.
Possible
Solution
72

CallFail_BurstCommit_STATUS_Re
movedSCH
T A B L E 1 2 6 E R R _ S P S _ R L S A_ R C M _ R S C H _ F U N C A L L F A I L _ B U R S T C O M M I T _
ST ATUS_REMOVEDSCH
Failure
Name
ERR_SPS_RLSA_RCM_RSCH_FunCallFail_BurstCommit_S
TATUS_RemovedSCH
Failure
Cause
The cell number is 0, or connection status is

STATUS_RemovedSCH
Possible
Solution

ERR_SPS_RLSA_RCM_RSCH_Stat
eIncorrect_CellNotFoundInRevSCH
ResourceExtension
T A B L E 1 2 7 E R R _ S P S _ R L S A_ R C M _ R S C H _ S T A T E I N C O R R E C T _
CELLNOTFOUNDINREVSCHRESOURCEEXTENSION
Failure
Name
ERR_SPS_RLSA_RCM_RSCH_StateIncorrect_CellNotFoun
dInRevSCHResourceExtension
Failure
Cause
During data service, after SCH set up and when user

transmits data continuously, there is new added cell.
This case is softer handoff add in transmission. It is
normal condition.
Possible
Solution
73
ERR_SPS_RLSA_RCM_FSCH_Oth
erReason_EndOfDuration
T A B L E 1 2 8 E R R _ S P S _ R L S A_ R C M _ F S C H _ O T H E R R E A S O N _
ENDOFDURATION
Failure
Name
ERR_SPS_RLSA_RCM_FSCH_OtherReason_EndOfDuratio
n
Failure
Cause
During data service and continuous transmission, the

database initiates reverse SCH channel release.
Possible
Solution
ERR_SPS_RLSA_RCM_FCH_Other
Reason_MRequestAbisConnect_Sp
ecifiedCellIsReleasing
T A B L E 1 2 9 E R R _ S P S _ R L S A_ R C M _ F C H _ O T H E R R E A S O N _
MREQUESTABISCONNECT_SPECIFIEDCELLISRELEASING
74
Failure
Name
ERR_SPS_RLSA_RCM_FCH_OtherReason_MRequestAbisC
onnect_SpecifiedCellIsReleasing
Failure
Cause
During soft or softer handoff, when the cell which has set
up leg is released and at the same time one leg is going
to be added, the handoff fails as the process does not
support both release and set up leg at the same time.
Possible
Solution
If handoff happens frequently, handoff has been started

when the release has not been finished; it is possible to
meet this case. It is normal condition; if there is no
handoff and an ordinary call meets this kind of failure, it
is possible that the internal processing is stopped.
Contact the ZTE local agent.
ERR_SPS_RLSA_RCM_FSCH_Tim
erExpired_TfschNotifyExpired
T A B L E 1 3 0 E R R _ S P S _ R L S A_ R C M _ F S C H _ T I M E R E X P I R E D _
TFSCHNOTIFYEXPIRED
Failure
Name
ERR_SPS_RLSA_RCM_FSCH_TimerExpired_TfschNotifyEx
pired
Failure
Cause
During data service, when there is a timeout waiting for

database resource reserved report message.
Possible
Solution
Check if voice traffic is too heavy. If this case occurs

frequently, please contact ZTE local agent.
ERR_SPS_RLSA_RCM_PCALL_Re
cvUnexptMsg_atTchStatusInSemiSo
ft_AbisdfBurstRequest
T A B L E 1 3 1 E R R _ S P S _ R L S A_ R C M _ P C A L L _ R E C V U N E X P T M S G _
ATTCHSTATUSINSEMISOFT_ABISDFBURSTREQUEST
Failure
Name
ERR_SPS_RLSA_RCM_PCALL_RecvUnexptMsg_atTchStat
usInSemiSoft_AbisdfBurstRequest
Failure
Cause
During data service and softer handoff procedure, when

the SCH channel setup message is received.
Possible
Solution
During softer handoff procedure, SCH channel setup

message is rejected. This is a normal failure.
75
ERR_SPS_RLSA_RCM_PCALL_Ti
merExpired_Tconfigtch
T A B L E 1 3 2 E R R _ S P S _ R L S A_ R C M _ P C A L L _ T I M E R E X P I R E D _ T C O N F I G T C H
Failure
Name
Failure
Cause
ERR_SPS_RLSA_RCM_PCALL_TimerExpired_Tconfigtch
and SCH channel is released. the following are the
reasons:
Possible
Solution

CallFail_BurstRequest_ConnInSetup
T A B L E 1 3 3 E R R _ S P S _ R L S A_ R C M _ R S C H _ F U N C A L L F A I L _
BURSTREQUEST_CONNINSETUP
76
Failure
Name
ERR_SPS_RLSA_RCM_RSCH_FunCallFail_BurstRequest_C
onnInSetup
Failure
Cause
During data service, SCH channel is requested to setup

several times
Possible
Solution
It belongs to abnormal probe report, to avoid parallel

request for many times.
ERR_SPS_RLSA_RCM_FCH_Other
Reason_MRequestAbisConnect_Sa
meTimeCellInSameGroupInDiffSetu
pFlow
T A B L E 1 3 4 E R R _ S P S _ R L S A_ R C M _ F C H _ O T H E R R E A S O N _
MREQUESTABISCONNECT_SAMETIMECELLINS AMEGROUPINDIFFSETUPFLOW
Failure
Name
ERR_SPS_RLSA_RCM_FCH_OtherReason_MRequestAbisC
onnect_SameTimeCellInSameGroupInDiffSetupFlow
Failure
Cause
During the call, several cells which can not support the
same leg want to set up FCH. This leads to resource
setup failure according to the principle.
Possible
Solution
Normal condition. Belongs to code limitation
ERR_SPS_RLSA_RCM_PMAIN_Fu
nCallFail_MainEntry_MAbisdMsgDis
patch
T A B L E 1 3 5 E R R _ S P S _ R L S A_ R C M _ P M A I N _ F U N C A L L F A I L _ M A I N E N T R Y _
M ABISDMSGDISPATCH
Failure
Name
ERR_SPS_RLSA_RCM_PMAIN_FunCallFail_MainEntry_MA
bisdMsgDispatch
Failure
Cause
During call setup, RCM main processing fails to send

message to Handler processing. The reason is all subprocessing are in busy status; RCM has no idle Handler
processing.
Possible
Solution
When this failure happens, if the call number is more

than processing limitation, then it is normal condition
( limitation: Hirs CCM 300,BDM 75,IP CCM 600); If a few
of calls also meet this failure, it is possible that OSS has
changed the processing limitation value, please contact
with ZTE local agent.
77
78
Chapter
CES Related Failures

This chapter introduces and describes call failures related to CES
ERR_CES_RLSA_CEC_CALLHNDL
_FCH_SETUP_CE_IN_USED
T A B L E 1 3 6 E R R _ C E S _ R L S A_ C E C _ C A L L H N D L _ F C H _ S E T U P _ C E _
IN_USED
Failure
Name
ERR_CES_RLSA_CEC_CALLHNDL_FCH_SETUP_CE_IN_US
ED
Failure
Cause
When FCH channel is in established, there is CE hung up

and this leads to FCH channel establishment failure
Following are the reasons.
1.CHM board CPU usage ratio is too high
2.UB alarm in CHM board
Failure
Analysis
3.BTS SDH transmission is not stable

4.Too many sub-cards in CHM board, ( at present ALL IP
supports 6, HIRS supports 4 chipsets)
5.CES code is abnormal, the resource is not released
6.The upper level is abnormal and the release is not
started
1.If CPU usage ratio is too high, block some sub-cards
Possible
Solution
2.Check SDH
3.Allocate some control channels to other board
4.If the problem is still not solved, reset CHM
79
_FCH_SETUP_RCV_CEM_REJECT
T A B L E 1 3 7 E R R _ C E S _ R L S A_ C E C _ C A L L H N D L _ F C H _ S E T U P _ R C V _
CEM_REJECT
Failure
Name
ERR_CES_RLSA_CEC_CALLHNDL_FCH_SETUP_RCV_CEM
_REJECT
Failure
Cause
When FCH channel is in establishment, CEC receives

CEM rejection message and this leads to FCH channel
establishment failure
Following are the reasons
Failure
Analysis
1.Internal transmission message failure

2.CE type is not compatible
3.Mission initialization failure
1.Check if there is UB alarm
Possible
Solution
2.Check CHM board CPU

3.Check CES with probe
4.Check board version
5.Block the problem chipset
_FCH_SETUP_CEMCTRL_NULL
T A B L E 1 3 8 E R R _ C E S _ R L S A_ C E C _ C A L L H N D L _ F C H _ S E T U P _
CEMCTRL_NULL
Failure
Name
ERR_CES_RLSA_CEC_CALLHNDL_FCH_SETUP_CEMCTRL
_NULL
Failure
Cause
When FCH channel is in establishment, the objective

probe is empty
Following are the reasons:
Failure
Analysis
1.The objective probe of one chipset CEMCTRL which is

acquired by control management is empty
2.Chipset serial number is not correct
Possible
Solution
80
1.Check if chipset configuration accord with the reality

2.Block problem chipset
Chapter 6 CES Related Failures
ERR_CES_RLSA_CEC_CALLMAIN
_FCH_SETUP_CREATE_PROCES
S
T A B L E 1 3 9 E R R _ C E S _ R L S A_ C E C _ C A L L M A I N _ F C H _ S E T U P _
CRE ATE_PROCESS
Failure
Name
ERR_CES_RLSA_CEC_CALLMAIN_FCH_SETUP_CREATE_P
ROCESS
Failure
Cause
When FCH channel is in setup, process establishment

fails.
Failure
Analysis
Possible
Solution
Following are the reasons:

1.Dispatch V_Create function mistake
2.Check board version
1.Solve the lower level problem
2.Block the problem CHM board
81
82
Tables
Table 1 Chapter Summary ...................................................i
Table 2 Typographical Conventions ...................................... ii
Table 3 Mouse Operation Conventions ................................. iii
Table 4 ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_
Unspecified........................................................................1
Table 5 ERR_SPS_RLSA_BSSAP_TE_T3230 ...........................2
Table 6 ERR_SPS_RLSA_BSSAP_TE_Tassignment...................2
Table 7 ERR_SPS_RLSA_BSSAP_FchSetup_RcvSccpDisconnect 3
Table 8 ERR_SPS_RLSA_BSSAP_FchSetup_RcvMSReleaseOrder4
Table 9 ERR_SPS_RLSA_BSSAP_TE_Tfchsetup.......................4
Table 10 ERR_SPS_RLSA_BSSAP_TE_T303 ...........................5
Table 11 ERR_SPS_RLSA_BSSAP_TE_Txxp............................5
Table 12 ERR_SPS_RLSA_BSSAP_DB_GetBoardOrIndexNetAddr
ByLogicAddr ......................................................................6
UserBusy ..........................................................................6
NormalClearing ..................................................................7
Table 15 ERR_SPS_RLSA_BSSAP_ByteIndex_IndexInUsed ......7
Table 16 ERR_SPS_RLSA_BSSAP_FchSetup_AllLegFail ............8
NoAnswer..........................................................................9
Table 18 ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvOrgnIn
SessionState......................................................................9
Table 19 ERR_SPS_RLSA_BSSAP_UnexptMsg_
RcvRegInAssignState_Others ............................................. 10
Table 20 ERR_SPS_RLSA_BSSAP_HandShake_TimeOut ........ 10
RcvRegInAssignState_PowerOn .......................................... 11
RcvRegInAssignState_PowerDown ...................................... 11
Table 23 ERR_SPS_RLSA_BSSAP_TgtBSC_FunCallFail__
TargetBSCHandlerEntry__A7HOReqMsgProccessForHOWith1X. 12
83
Table 24 ERR_SPS_RLSA_BSSAP_Other_ReceiveResetCircuit . 12
Table 25 ERR_SPS_RLSA_BSSAP_FchSetup_SendChannel
Assignment_AllBtsFail ....................................................... 13
HandoffSuccessful ............................................................ 14
Table 27 ERR_SPS_RLSA_BSSAP_TgtBSC_Other__
TargetBSCHandler_A7fHandoffRequestProccess__RecievedA7HO
ReqWhenSemiHO ............................................................. 14
SemiConcurrentService ..................................................... 15
Table 29 ERR_SPS_RLSA_BSSAP_MsgPara_Origination_
InvalidServiceOption ......................................................... 15
Table 30 ERR_SPS_RLSA_BSSAP_HashOpr_AddItem_
SccpId2CallRef................................................................. 16
Table 31 ERR_SPS_RLSA_BSSAP_Other_Get97DMTMsParaFail16
EquipmentFailure ............................................................. 17
AuthenticationFailure ........................................................ 17
Table 34 ERR_SPS_RLSA_DSPM_CLH_OtherReason_
MSNormalRelease............................................................. 19
Table 35 ERR_SPS_RLSA_DSPM_CLH_TimerExpired_Twaitorder
..................................................................................... 20
Table 36 ERR_SPS_RLSA_DSPM_CLH_OtherReason_SNFailure
..................................................................................... 21
Table 37
ERR_SPS_RLSA_DSPM_CLH_OtherReason_MSPowerDown ..... 21
Table 38 ERR_SPS_RLSA_DSPM_CLH_TimerExpired_Tpcfinfol3
..................................................................................... 22
Table 39 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_
SCHHOnUmrSCHRequestMsg_ReleasebyMSDTXTime ............. 23
SCHHOnAbarSCHRemoveIndication_RSCHReleasebySDMDTXTim
e.................................................................................... 23
SCHHPNDropIndication_ReleasebyHOH................................ 24
SCHHOnAbisdrBurstRelease_RSCHExistedCellReleasebyRCM... 24
SCHHRelease_ReleasebyCLH.............................................. 25
SCHHOnAbarSCHRemoveIndication_RSCHReleasebySDMOtherRe
ason ............................................................................... 25
84
Tables
SCHHOnAbarSCHRemoveIndication_FSCHReleasebySDMDuration
..................................................................................... 26
SCHHFSCHHandoff_HardHandoff ........................................ 26
Table 47 ERR_SPS_RLSA_DSPM_SCHH_TimerExpired_Tfschdrop
..................................................................................... 27
SCHHOnTfschdroppending_ReleasebyTDropPending .............. 27
SCHHOnAbisdrBurstRelease_FSCHExistedCellReleasebyRCM ... 28
PCFEquipmentFailure ........................................................ 28
MSGoingIntoDormant........................................................ 29
PCFNormalRelease............................................................ 29
Table 53 ERR_SPS_RLSA_DSPM_HOH_TimerExpired_
SoftHOThocompletion ....................................................... 30
Table 54 ERR_SPS_RLSA_DSPM_HOH_TimerExpired_Thoreq . 31
Table 55 ERR_SPS_RLSA_DSPM_HOH_ResNotSatisfied_
HOHOnUmrCFSearchReport ............................................... 32
Table 56 ERR_SPS_RLSA_DSPM_HOH_OtherReason_
AbisdHandShakeFailure ..................................................... 32
Table 57
ERR_SPS_RLSA_DSPM_SCHH_TimerExpired_Tfschbstreq ....... 33
Table 58
Reason_Unspecified .......................................................... 34
Table 59 ERR_SPS_RLSA_DSPM_CLH_OtherReason_OVERLOAD
..................................................................................... 34
Table 60 ERR_SPS_RLSA_DSPM_CLH_OtherReason_Ta8setup 35
Tshakehandrecv ............................................................... 35
Table 62 ERR_SPS_RLSA_DSPM_HOH_TimerExpired_
SemiSoftHOThocompletion................................................. 36
Table 63 ERR_SPS_RLSA_DSPM_HOH_ResNotSatisfied_
HOHOnA7rHOReqAck ........................................................ 37
Table 64
Reason_Administratively_Pohibited ..................................... 38
Table 65 ERR_SPS_RLSA_DSPM_CLH_OtherReason_PCFDenied_
PDSN_Resource_Unavailable .............................................. 38
85
SCHHReleaseRSCHbyLegFail_ReleaseRschExistSDMLegFailure 39
SCHHOnUmrSCHRequestMsg_FCHNotExisted ....................... 39
Table 68 SDM_Activate_Fail_AcquirePreambleFail_Normal ..... 41
Table 69 SDM_Activate_Fail_AcquirePreambleFail_NoRevFrm 42
Table 70 SDM_Find_Fail_WaitConfigVTCTimeout .................. 43
Table 71 SDM_Link_Fail_RevNoFrm ................................... 44
Table 72 SDM_Link_Fail_RevTooManyBadFrm...................... 44
Table 73 SDM_Link_Fail_FwdA2pNoFrm.............................. 45
Table 74 SDM_Find_Fail_WaitConfigRLPTimeout .................. 45
Table 75 SDM_Link_Fail_RSCHLegLinkFail ........................... 46
Table 76 SDM_Link_Fail_FwdA2pTooManyErrEncodeFrm ....... 46
Table 77 SDM_Activate_Fail_InitVocoderFail........................ 47
Table 78 SDM_OprVocoder_Fail_WaitStartVocoderCodingAck
TimeOut.......................................................................... 47
Table 79 SDM_Find_Fail_NoFCHLeg ................................... 48
Table 80 SDM_Activate_Fail_MsgParaFail ............................ 48
Table 81 DBS_STASTIC_FWDFCHCE_REVCE_LACK ............... 49
Table 82 DBS_STASTIC_FWDFCHCE_LACK.......................... 50
Table 83 DBS_STASTIC_WALSHCODE_LACK ....................... 50
Table 84 DBS_STASTIC_UID_LACK .................................... 51
Table 85 DBS_STASTIC_NO_RESOURCE_LACK .................... 51
Table 86 FCH_NUMBER_TWO ............................................ 52
Table 87 ARRIVE_TIME_ERROR ......................................... 52
Table 88 NO_SYSTEM_TIME .............................................. 53
Table 89 INPUT_PARA_ERROR........................................... 53
Table 90 POWER_NOT_ENOUGH ........................................ 54
Table 91 SOFTADD_CELL_ERROR ...................................... 54
Table 92 NO_AVAILABLE_REV_CE...................................... 55
Table 93 FO_NOT_ENOUGH .............................................. 55
Table 94 CE_NOT_ENOUGH .............................................. 56
Table 95 WALSHCODE_NOT_ENOUGH ................................ 56
Table 96 BEFORE_CPS ..................................................... 57
Table 97 UIDWIDTH_NOT_ENOUGH ................................... 57
Table 98 RS_NOT_EXIST .................................................. 58
Table 99 ALLOCATE_UID_ERROR ....................................... 58
86
Tables
Table 100 HO_STAT_PILOT_NO_SAME_FREQ ...................... 59

Table 101 HO_STAT_CARRIER_PWR_OVERLOAD.................. 59
Table 102 HO_STAT_CARRIER_STATE_ERROR ..................... 60
Table 103 HO_STAT_CARRIER_NO_CE ............................... 60
Table 104 HO_STAT_CARRIER_NO_5KCE............................ 61
Table 105 HO_STAT_PILOT_IS_NOT_NEIGHBOR .................. 61
Table 106 HO_STAT_DESTBSC_IS_HIRS_DATASOFTHO ........ 62
Table 107 HO_STAT_PILOT_NOT_LOCALBSS ....................... 62
Table 108 HO_STAT_PILOT_IS_OTHER_UNLNKBSS .............. 63
Table 109 BSC_NO_CIC.................................................... 63
Table 110 BSC_NO_SE ..................................................... 64
Table 111 BSC_NO_VE ..................................................... 64
Table 112 BSC_NO_IWF ................................................... 65
Table 113 BSC_DSPM_NO_INSTANCE................................. 65
Table 114 BSC_NO_RTPPORT ............................................ 66
Table 115 BSC_NO_VALID_RMP ........................................ 66
Table 116
ERR_SPS_RLSA_RCM_DBAccFail_FCHResourceAllocate .......... 67
Table 117 ERR_SPS_RLSA_RCM_PCALL_OtherReason_CEC_
REMOVEREQ .................................................................... 68
Table 118
ERR_SPS_RLSA_RCM_FCH_TimerExpired_TconnExpired......... 69
Table 119 ERR_SPS_RLSA_RCM_RSCH_OtherReason_Release_
RSCH.............................................................................. 69
Table 120 ERR_SPS_RLSA_RCM_RSCH_OtherReason_Release_
FSCH .............................................................................. 70
Table 121 ERR_SPS_RLSA_RCM_FSCH_FunCallFail_
AddChannelFail ................................................................ 70
Table 122 ERR_SPS_RLSA_RCM_SCHCOMM_TimerExpired_Tsch
..................................................................................... 71
Table 123
ERR_SPS_RLSA_RCM_SCHCOMM_TimerExpired_Tbstcomb..... 71
Table 124 ERR_SPS_RLSA_RCM_RSCH_FunCallFail_
RevSCHSetupFail.............................................................. 72
Table 125 ERR_SPS_RLSA_RCM_FSCH_FunCallFail_
FwdSCHSetupFail ............................................................. 72
Table 126
ERR_SPS_RLSA_RCM_RSCH_FunCallFail_BurstCommit_
STATUS_RemovedSCH ...................................................... 73
Table 127 ERR_SPS_RLSA_RCM_RSCH_StateIncorrect_
CellNotFoundInRevSCHResourceExtension ........................... 73
87
Table 128 ERR_SPS_RLSA_RCM_FSCH_OtherReason_

EndOfDuration ................................................................. 74
Table 129 ERR_SPS_RLSA_RCM_FCH_OtherReason_
MRequestAbisConnect_SpecifiedCellIsReleasing .................... 74
Table 130 ERR_SPS_RLSA_RCM_FSCH_TimerExpired_
TfschNotifyExpired............................................................ 75
Table 131 ERR_SPS_RLSA_RCM_PCALL_RecvUnexptMsg_
atTchStatusInSemiSoft_AbisdfBurstRequest ......................... 75
Table 132
ERR_SPS_RLSA_RCM_PCALL_TimerExpired_Tconfigtch .......... 76
Table 133 ERR_SPS_RLSA_RCM_RSCH_FunCallFail_
BurstRequest_ConnInSetup ............................................... 76
Table 134 ERR_SPS_RLSA_RCM_FCH_OtherReason_
MRequestAbisConnect_SameTimeCellInSameGroupInDiffSetupFl
ow ................................................................................. 77
Table 135 ERR_SPS_RLSA_RCM_PMAIN_FunCallFail_MainEntry_
MAbisdMsgDispatch .......................................................... 77
Table 136 ERR_CES_RLSA_CEC_CALLHNDL_FCH_SETUP_CE_
IN_USED......................................................................... 79
Table 137 ERR_CES_RLSA_CEC_CALLHNDL_FCH_SETUP_RCV_
CEM_REJECT ................................................................... 80
Table 138 ERR_CES_RLSA_CEC_CALLHNDL_FCH_SETUP_
CEMCTRL_NULL ............................................................... 80
Table 139 ERR_CES_RLSA_CEC_CALLMAIN_FCH_SETUP_
CREATE_PROCESS............................................................ 81
88

ZXC10 BSSB (V8.0.1.9) Call Failure Reason and Call Drop Explanation (1x)

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

ZXC10 BSSB (V8.0.1.9) Call Failure Reason and Call Drop Explanation (1x)

Uploaded by

Copyright:

Available Formats

ZXC10 BSSB

CDMA Base Station System

Call Failure Reason and Call Drop

Reason for Revision

Equipment Installation Date

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

This page is intentionally blank.

About this Manual

Prerequisite Skill and Knowledge

ZXC10 BSSB (V8.0.1.9) (1x) Base Station System

local operating procedures

What is in This Manual

Describes the Failure analysis and

Chapter 2 DSPM related

Describes the Failure analysis and

Chapter 3 SDM related

Describes the Failure analysis and

Confidential and Proprietary Information of ZTE CORPORATION

Chapter 4 DBS related

Describes the Failure analysis and

Chapter 5 RCM related

Describes the Failure analysis and

Chapter 6 CES related

Describes the Failure analysis and

ZXC10 BSSB (V8.0.1.9) CDMA2000 Base Station System

ZTE documents employ the following typographical conventions.

References to other Manuals and documents.

Menus, menu options, function names, input

Keys on the keyboard and buttons on screens

Text that you type, program code, files and

Select one of the parameters that are delimited

Confidential and Proprietary Information of ZTE CORPORATION

About this Manual

TABLE 3 MOUSE OPERATION CONVENTIONS

Refers to clicking the primary mouse button (usually

Refers to quickly clicking the primary mouse button

Refers to clicking the secondary mouse button

Refers to pressing and holding a mouse button and

How to Get in Touch

If you have problems, questions, comments, or suggestions

Confidential and Proprietary Information of ZTE CORPORATION

This page is intentionally blank.

Confidential and Proprietary Information of ZTE CORPORATION

BSSAP Related Failures

When a call is being setup,MSC sends a

1. non-standard cause value in A-interface

It is acceptable if the problem occurs occasionally,

Confidential and Proprietary Information of ZTE CORPORATION

When a call is being setup, after BSSAP sending

1. Check No.7 signaling link,perhaps the link is

Most likely causes:

2. Check if there are too many DSMP instances in the

Confidential and Proprietary Information of ZTE CORPORATION