Вы находитесь на странице: 1из 175

ZXC10 BSSB

CDMA2000 Base Station System

Failure Cause Reference(1X)


Version: V8.0.5.100

ZTE CORPORATION
NO. 55, Hi-tech Road South, ShenZhen, P.R.China
Postcode: 518057
Tel: +86-755-26771900
Fax: +86-755-26770801
URL: http://ensupport.zte.com.cn
E-mail: support@zte.com.cn

LEGAL INFORMATION
Copyright 2012 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.
ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.
Users may visit ZTE technical support website http://ensupport.zte.com.cn to inquire related information.
The ultimate right to interpret this product resides in ZTE CORPORATION.

Revision History
Revision No.

Revision Date

Revision Reason

R1.0

2012-10-20

First Edition

Serial Number: SJ-20120828144226-019


Publishing Date: 2012-10-20 (R1.0)

SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

Contents
About This Manual ......................................................................................... I
Chapter 1 Call Failure Causes................................................................... 1-1
1.1 ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_Unspecified ..................... 1-1
1.2 ERR_SPS_RLSA_BSSAP_TE_T3230................................................................. 1-2
1.3 ERR_SPS_RLSA_BSSAP_TE_Tassignment ....................................................... 1-2
1.4 ERR_SPS_RLSA_BSSAP_FchSetup_RcvSccpDisconnect .................................. 1-3
1.5 ERR_SPS_RLSA_BSSAP_FchSetup_RcvMSReleaseOrder................................. 1-4
1.6 ERR_SPS_RLSA_BSSAP_TE_Tfchsetup ........................................................... 1-4
1.7 ERR_SPS_RLSA_BSSAP_TE_T303 .................................................................. 1-5
1.8 ERR_SPS_RLSA_BSSAP_TE_Txxp ................................................................... 1-6
1.9 ERR_SPS_RLSA_BSSAP_DB_GetBoardOrIndexNetAddrByLogicAddr ................ 1-7
1.10 ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_CallProcessing............... 1-7
1.11 ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_UserBusy....................... 1-8
1.12 ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_NormalClearing .............. 1-9
1.13 ERR_SPS_RLSA_BSSAP_ByteIndex_IndexInUsed ........................................... 1-9
1.14 ERR_SPS_RLSA_BSSAP_FchSetup_AllLegFail.............................................. 1-10
1.15 ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_NoAnswer.....................1-11
1.16 ERR_SPS_RLSA_BSSAP_Other_ReceiveResetCircuit .....................................1-11
1.17 ERR_SPS_RLSA_BSSAP_FchSetup_SendChannelAssignment_AllBtsFail ....... 1-12
1.18 ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_HandoffSuccessful ....... 1-13
1.19 ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_SemiConcurrentServi
ce .................................................................................................................. 1-14
1.20 ERR_SPS_RLSA_BSSAP_MsgPara_Origination_InvalidServiceOption............. 1-14
1.21 ERR_SPS_RLSA_BSSAP_HashOpr_AddItem_SccpId2CallRef ........................ 1-15
1.22 ERR_SPS_RLSA_BSSAP_Other_Get97DMTMsParaFail ................................. 1-15
1.23 ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_EquipmentFailure ......... 1-16
1.24 ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_AuthenticationFailur
e.................................................................................................................... 1-16
1.25 ERR_SPS_RLSA_BSSAP_FchSetup_AllLegAreRemoved ............................... 1-17
1.26 ERR_SPS_RLSA_BSSAP_Other_SpcfSelectTableBad .................................... 1-17
1.27 ERR_SPS_RLSA_BSSAP_Other_RTDOutofRange ......................................... 1-18
1.28 ERR_SPS_RLSA_BSSAP_MultiSP_InvalidMSCOfficeId .................................. 1-19
1.29 ERR_SPS_RLSA_BSSAP_MultiSP_MSCOfficeUnavailable ............................. 1-19
1.30 ERR_SPS_RLSA_BSSAP_MultiSP_A1fAssignReq_InvalidMSCOfficeId ........... 1-20
I
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

1.31 ERR_SPS_RLSA_BSSAP_MsgPara_MSRejectOrder ...................................... 1-20


1.32 ERR_SPS_RLSA_BSSAP_Other_Encode_A1MsgInBSC ................................. 1-21
1.33 ERR_SPS_RLSA_BSSAP_Other_Encode_UmpMsgInBSC .............................. 1-21
1.34 ERR_SPS_RLSA_BSSAP_Other_Decode_UmpMsgInBSC.............................. 1-21
1.35 ERR_SPS_RLSA_BSSAP_TE_Ta1_4 ............................................................. 1-22
1.36 ERR_SPS_RLSA_BSSAP_PoorPilot............................................................... 1-22
1.37 ERR_SPS_RLSA_BSSAP_FchSetup_SendPCHMsg_AllBtsFail ....................... 1-22
1.38 ERR_SPS_RLSA_BSSAP_DB_GetLinkInfo..................................................... 1-23
1.39 ERR_SPS_RLSA_BSSAP_DB_GetValidCarrier ............................................... 1-23
1.40 ERR_SPS_RLSA_BSSAP_DB_GetOPBySysIdCellIdCrId................................. 1-23
1.41 ERR_SPS_RLSA_DSPM_CLH_TimerExpired_Twaitorder ................................ 1-23
1.42 ERR_SPS_RLSA_BSSAP_Other_DifferenceInFwdOrRevRC ........................... 1-24
1.43 ERR_SPS_RLSA_DSPM_CLH_OtherReason_SNFailure................................. 1-25
1.44 ERR_SPS_RLSA_DSPM_CLH_TimerExpired_Tpcfinfol3 ................................. 1-25
1.45 ERR_SPS_RLSA_DSPM_SCHH_TimerExpired_Tfschbstreq ........................... 1-26
1.46 ERR_SPS_RLSA_DSPM_CLH_OtherReason_PDSNDenied_Reason_Unspe
cified.............................................................................................................. 1-27
1.47 ERR_SPS_RLSA_DSPM_CLH_OtherReason_Ta8setup.................................. 1-27
1.48 ERR_SPS_RLSA_DSPM_CLH_OtherReason_PDSNDenied_Reason_Admini
stratively_Pohibited......................................................................................... 1-28
1.49 ERR_SPS_RLSA_DSPM_CLH_OtherReason_PCFDenied_PDSN_Resource
_Unavailable .................................................................................................. 1-29
1.50 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnUmrSCHRequestM
sg_FCHNotExisted ......................................................................................... 1-29
1.51 ERR_SPS_RLSA_DSPM_SCHH_ResNotSatisfied_SCHHOnFwdAllBurstRes
ponse_NoCommitedCell ................................................................................. 1-30
1.52 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnAcrBSCAddChann
elItemAck_AddChannelItemFailed ................................................................... 1-31
1.53 SDM_Activate_Fail_AcquirePreambleFail_Normal............................................ 1-32
1.54 SDM_Activate_Fail_AcquirePreambleFail_NoRevFrm ...................................... 1-32
1.55 SDM_Find_Fail_WaitConfigVTCTimeout ......................................................... 1-33
1.56 SDM_Find_Fail_WaitConfigRLPTimeout.......................................................... 1-34
1.57 SDM_Link_Fail_RSCHLegLinkFail .................................................................. 1-34
1.58 SDM_Activate_Fail_InitVocoderFail ................................................................. 1-35
1.59 SDM_OprVocoder_Fail_WaitStartVocoderCodingAckTimeOut .......................... 1-35
1.60 SDM_Activate_Fail_MsgParaFail .................................................................... 1-36
1.61 DBS_STASTIC_FWDFCHCE_REVCE_LACK.................................................. 1-36
1.62 DBS_STASTIC_FWDFCHCE_LACK ............................................................... 1-37

II
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

1.63 DBS_STAT_WALSHCODE_LACK .................................................................. 1-37


1.64 DBS_STAT_UID_LACK .................................................................................. 1-38
1.65 DBS_STAT_NO_RESOURCE_LACK .............................................................. 1-38
1.66 FCH_NUMBER_TWO .................................................................................... 1-39
1.67 ARRIVE_TIME_ERROR ................................................................................. 1-39
1.68 NO_SYSTEM_TIME ....................................................................................... 1-40
1.69 NO_AVAILABLE_REV_CE ............................................................................. 1-40
1.70 FO_NOT_ENOUGH ....................................................................................... 1-41
1.71 CE_NOT_ENOUGH ....................................................................................... 1-41
1.72 WALSHCODE_NOT_ENOUGH ...................................................................... 1-41
1.73 BEFORE_CPS ............................................................................................... 1-42
1.74 UIDWIDTH_NOT_ENOUGH ........................................................................... 1-42
1.75 RS_NOT_EXIST ............................................................................................ 1-43
1.76 ALLOCATE_UID_ERROR .............................................................................. 1-43
1.77 BSC_CICFROMMSC_ERR............................................................................. 1-44
1.78 HO_STAT_SERVICE_FORBID........................................................................ 1-44
1.79 ERR_SPS_RLSA_RCM_DBAccFail_FCHResourceAllocate ............................. 1-44
1.80 ERR_SPS_RLSA_RCM_PCALL_OtherReason_CEC_REMOVEREQ ............... 1-45
1.81 ERR_SPS_RLSA_RCM_FCH_TimerExpired_TconnExpired ............................. 1-46
1.82 ERR_SPS_RLSA_RCM_FSCH_FunCallFail_AddChannelFail........................... 1-47
1.83 ERR_SPS_RLSA_RCM_FSCH_TimerExpired_TfschNotifyExpired ................... 1-47
1.84 ERR_SPS_RLSA_RCM_FCH_OtherReason_MRequestAbisConnect_SameTi
meCellInSameGroupInDiffSetupFlow............................................................... 1-48
1.85 ERR_SPS_RLSA_RCM_PMAIN_FunCallFail_MainEntry_MAbisdMsgDispatc
h.................................................................................................................... 1-48
1.86 ERR_SPS_RLSA_RCM_FCH_OtherReason_MRequestAbisConnect_Service
Restrict .......................................................................................................... 1-49
1.87 ERR_SPS_RLSA_RCM_FSCH_FunCallFail_BurstRequest_ConnInSetup......... 1-50
1.88 ERR_SPS_RLSA_RCM_RSCH_FunCallFail_BurstRequest_SaveToGrouped
CellInfoSet_CellNumIsZero ............................................................................. 1-50
1.89 ERR_SPS_RLSA_RCM_PCALL_RecvUnexptMsg_atTchStatusInSemiSoft_A
bisdfBurstCommit ........................................................................................... 1-51
1.90 ERR_SPS_RLSA_RCM_RSCH_FunCallFail_AddChannelFail .......................... 1-51
1.91 ERR_SPS_RLSA_RCM_RSCH_FunCallFail_BurstCommit_GetConnRecordB
yGroupId........................................................................................................ 1-52
1.92 BSC_NO_CIC ................................................................................................ 1-52
1.93 POWER_NOT_ENOUGH ............................................................................... 1-53
1.94 BSC_NO_SE ................................................................................................. 1-54

III
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

1.95 BSC_NO_VE ................................................................................................. 1-54


1.96 BSC_NO_IWF................................................................................................ 1-55
1.97 BSC_DSPM_NO_INSTANCE ......................................................................... 1-55
1.98 BSC_NO_RTPPORT...................................................................................... 1-56
1.99 BSC_NO_VALID_RMP................................................................................... 1-57
1.100 ERR_SPS_RLSA_RCM_FCH_FunCallFail_HandlerAbisdfConnectAck_MCS
HConstructAmdfFCHSetup ............................................................................. 1-57
1.101 ERR_SPS_RLSA_RCM_PCALL_FunCallFail_MHandlerTCHfTSSetup_MHa
ndlerAbisdfBTSSetup...................................................................................... 1-58
1.102 ERR_SPS_RLSA_RCM_FCH_MsgParaIncorrect_HandleAbisdfConnectAck
_SoftHandoffLegNoInvalid............................................................................... 1-59
1.103 ERR_SPS_RLSA_RCM_PCALL_FunCallFail_MHandlerAbisdfBTSSetup_M
CDHSaveToCommonData .............................................................................. 1-59
1.104 ERR_CES_RLSA_CEC_CALLHNDL_FCH_SETUP_CE_IN_USED................. 1-60
1.105 ERR_CES_RLSA_CEC_CALLHNDL_FCH_SETUP_RCV_CEM_REJECT ...... 1-61
1.106 ERR_CES_RLSA_CEC_CALLMAIN_FCH_SETUP_CREATE_PROCESS....... 1-62
1.107 ERR_CES_RLSA_CEC_CALLMAIN_FCH_SETUP_OUTPUT_MSG_TO_CA
LLHNDL......................................................................................................... 1-62
1.108 ERR_CES_RLSA_CEC_CALLHNDL_FCH_SETUP_RCV_CEM_RSP_TIME
R_OUT .......................................................................................................... 1-63
1.109 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_POINTER_NU
LL.................................................................................................................. 1-64
1.110 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_HANDOFF_T
YPE............................................................................................................... 1-64
1.111 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_SECTOR_NU
M................................................................................................................... 1-65
1.112 ERR_CES_RLSA_CEC_CALLHNDL_FCH_SETUP_PARAM_FWD_RC.......... 1-66
1.113 ERR_CES_RLSA_CEC_CALLHNDL_FCH_SETUP_PARAM_REV_RC .......... 1-66
1.114 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_SECTOR_I
D ................................................................................................................... 1-67
1.115 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_SECTOR_ISN
OT_ACTIVE ................................................................................................... 1-68
1.116 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_EARLIESTPN
OFFSET ........................................................................................................ 1-69
1.117 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_WALSH_INDE
X ................................................................................................................... 1-69
1.118 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_CE_INDEX ....... 1-70
1.119 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_FRAME_OFF
SET ............................................................................................................... 1-71

IV
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

1.120 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_CHANNEL_P
OWER ........................................................................................................... 1-71
1.121 ERR_CES_RLSA_CEC_CALLHNDL_FCH_SETUP_PARAM_REV_FCH_G
ATING ........................................................................................................... 1-72
1.122 ERR_CES_RLSA_CEC_CALLHNDL_DCCH_SETUP_PARAM_REV_PILOT
_GATING....................................................................................................... 1-73
1.123 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_FPC_PUNC_
MODE ........................................................................................................... 1-74
1.124 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_FPC_GAIN ....... 1-74
1.125 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_FPC_STEP_S
IZE ................................................................................................................ 1-75
1.126 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_RPC_PUNC_
MODE ........................................................................................................... 1-76
1.127 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_REV_PC_SET
POINT ........................................................................................................... 1-77
1.128 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_REV_PC_PAT
TERN ............................................................................................................ 1-77
1.129 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_TRAFFIC_FR
AME_TYPE.................................................................................................... 1-78
1.130 CEMERROR_CALLHNDL_TCH_SETUP_PARAM_DEST_IP_ADRR_INVAL
ID .................................................................................................................. 1-79
1.131 CEMERROR_CALLHNDL_TCH_SETUP_PARAM_DSCP_PRIIS_INVALI
D ................................................................................................................... 1-80
1.132 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_CEMCTRL_NULL ........... 1-80
1.133 ERR_SPS_RLSA_BSSAP_SccpDisconnect_Connectref_Incompat_Inf_In_N
SDUs............................................................................................................. 1-81
1.134 ERR_SPS_RLSA_BSSAP_SccpDisconnect_End_User_Failure ...................... 1-81
1.135 ERR_SPS_RLSA_BSSAP_TgtBSC_FunCallFail_FCHAndDCCH_AbisdrCon
nectProccess_AbisdrConnectMsgProccess...................................................... 1-82
1.136 ERR_SPS_RLSA_BSSAP_TgtBSC_Other_CheckIfCellFitToSetup_HOReqC
ellIsExisted..................................................................................................... 1-82
1.137 ERR_SPS_RLSA_BSSAP_TgtBSC_Other_ReqReleaseingCellIsNotExiste
d.................................................................................................................... 1-82
1.138 ERR_SPS_RLSA_BSSAP_PTTSetup_ServiceNotify_UserInHigherPrioritySe
rvice .............................................................................................................. 1-83
1.139 ERR_SPS_RLSA_BSSAP_PTTSetup_A9dfPTTPage_UserInHigherPriorit
y.................................................................................................................... 1-83

Chapter 2 Call Drop Causes ...................................................................... 2-1


2.1 ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvOrgnInSessionState .......................... 2-1
2.2 ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvRegInSessionState_Others ............... 2-1
V
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

2.3 ERR_SPS_RLSA_BSSAP_HandShake_TimeOut ................................................ 2-2


2.4 ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvRegInAssignState_PowerOn ............. 2-2
2.5 ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvRegInAssignState_PowerDown ......... 2-3
2.6 ERR_SPS_RLSA_BSSAP_UnexptMsg_UmaRegistration..................................... 2-3
2.7 ERR_SPS_RLSA_DSPM_HOH_OtherReason_AbisdHandShakeFailure............... 2-4
2.8 ERR_SPS_RLSA_DSPM_CLH_OtherReason_PCFEquipmentFailure................... 2-4
2.9 ERR_SPS_RLSA_DSPM_CLH_OtherReason_Thandshakerecv........................... 2-5
2.10 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHReleaseRSCHbyLegF
ail_ReleaseRschExistSDMLegFailure ................................................................ 2-6
2.11 SDM_Link_Fail_RevNoFrm ............................................................................... 2-6
2.12 SDM_Link_Fail_RevTooManyBadFrm ............................................................... 2-7
2.13 SDM_Link_Fail_FwdA2pNoFrm ........................................................................ 2-7
2.14 SDM_Link_Fail_FwdA2pTooManyErrEncodeFrm ............................................... 2-8
2.15 ERR_SPS_RLSA_RCM_PMAIN_FunCallFail_MainEntry_GetCallProc ................ 2-9
2.16 ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvOrgnInHardHOAdd.......................... 2-9
2.17 ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvPageRspInHardHOAdd ................... 2-9

Chapter 3 Call Release Causes ................................................................. 3-1


3.1 ERR_SPS_RLSA_DSPM_CLH_OtherReason_MSNormalRelease........................ 3-1
3.2 ERR_SPS_RLSA_DSPM_CLH_OtherReason_MSPowerDown............................. 3-1
3.3 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnUmrSCHRequestMs
g_ReleasebyMSDTXTime ................................................................................. 3-2
3.4 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnAbarSCHRemoveIn
dication_RSCHReleasebySDMOtherReason...................................................... 3-2
3.5 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHPNDropIndication_Rele
asebyHOH ....................................................................................................... 3-3
3.6 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnAbisdrBurstRelease
_RSCHExistedCellReleasebyRCM .................................................................... 3-3
3.7 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHRelease_ReleasebyCL
H ..................................................................................................................... 3-4
3.8 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnAbarSCHRemoveIn
dication_RSCHReleasebySDMOtherReason...................................................... 3-4
3.9 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnAbarSCHRemoveIn
dication_FSCHReleasebySDMDuration ............................................................. 3-5
3.10 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHFSCHHandoff_HardH
andoff .............................................................................................................. 3-5
3.11 ERR_SPS_RLSA_DSPM_SCHH_TimerExpired_Tfschdrop ................................ 3-6
3.12 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnTfschdroppending_
ReleasebyTDropPending .................................................................................. 3-6

VI
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

3.13 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnAbisdrBurstReleas
e_FSCHExistedCellReleasebyRCM................................................................... 3-7
3.14 ERR_SPS_RLSA_DSPM_CLH_OtherReason_MSGoingIntoDormant ................. 3-7
3.15 ERR_SPS_RLSA_DSPM_CLH_OtherReason_PCFNormalRelease .................... 3-7
3.16 ERR_SPS_RLSA_DSPM_CLH_OtherReason_SDMLinkFailure_toDormant ........ 3-8
3.17 ERR_SPS_RLSA_DSPM_HOH_FunCallFail_HOHOnA7rTarRemReq_CLHRl
sInd ................................................................................................................. 3-9
3.18 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnA7rBurstRelease_
FSCHExistedCellReleasebyRCM .................................................................... 3-10
3.19 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnA7rBurstRelease_
RSCHExistedCellReleasebyRCM .................................................................... 3-10
3.20 SDM_Find_Fail_NoFCHLeg.............................................................................3-11
3.21 ERR_SPS_RLSA_RCM_RSCH_OtherReason_Release_RSCH ........................3-11
3.22 ERR_SPS_RLSA_RCM_RSCH_OtherReason_Release_FSCH........................ 3-12
3.23 ERR_SPS_RLSA_RCM_SCHCOMM_TimerExpired_Tsch................................ 3-12
3.24 ERR_SPS_RLSA_RCM_SCHCOMM_TimerExpired_Tbstcomb ........................ 3-12
3.25 ERR_SPS_RLSA_RCM_RSCH_FunCallFail_RevSCHSetupFail....................... 3-13
3.26 ERR_SPS_RLSA_RCM_FSCH_FunCallFail_FwdSCHSetupFail....................... 3-14
3.27 ERR_SPS_RLSA_RCM_RSCH_FunCallFail_BurstCommit_STATUS_Remov
edSCH........................................................................................................... 3-15
3.28 ERR_SPS_RLSA_RCM_RSCH_StateIncorrect_CellNotFoundInRevSCHReso
urceExtension ................................................................................................ 3-15
3.29 ERR_SPS_RLSA_RCM_PCALL_TimerExpired_Tconfigtch .............................. 3-16
3.30 ERR_SPS_RLSA_RCM_FSCH_OtherReason_EndOfDuration ......................... 3-16

Chapter 4 Handoff Failure Causes............................................................ 4-1


4.1 ERR_SPS_RLSA_BSSAP_TgtBSC_FunCallFail_TargetBSCHandlerEntry_A7
HOReqMsgProccessForHOWith1X.................................................................... 4-1
4.2 ERR_SPS_RLSA_BSSAP_Other_ReceiveResetCircuit........................................ 4-1
4.3 ERR_SPS_RLSA_BSSAP_TgtBSC_Other_TargetBSCHandler_A7fHandoffRe
questProccess_RecievedA7HOReqWhenSemiHO ............................................. 4-2
4.4 ERR_SPS_RLSA_BSSAP_Other_SBSSRFailure................................................. 4-3
4.5 ERR_SPS_RLSA_BSSAP_DB_GetPeerCellDiscriminator .................................... 4-3
4.6 ERR_SPS_RLSA_BSSAP_UnexptMsg_TSendAssignmentMsgNotInValidStat
e...................................................................................................................... 4-3
4.7 ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvSBSSAckNotInSetupState................. 4-4
4.8 ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvSBSSAck_bTbssapRlcReqOut .......... 4-4
4.9 ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvAvrHORequiredSBSSRInV5Syste
m..................................................................................................................... 4-4

VII
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

4.10 ERR_SPS_RLSA_BSSAP_UnexptMsg_TargetRemovalReqInSBSSRCallSetu
p...................................................................................................................... 4-5
4.11 ERR_SPS_RLSA_BSSAP_UnexptMsg_TbssapRlcReqNotInSetupState.............. 4-5
4.12 ERR_SPS_RLSA_BSSAP_MsgPara_SBSSRRequestAck_atCellInfoIsInvalid...... 4-5
4.13 ERR_SPS_RLSA_BSSAP_MsgPara_SBSSRRequestAck_ServiceTypeIsNot
Matched........................................................................................................... 4-6
4.14 ERR_SPS_RLSA_BSSAP_TE_TbssapRlcReq .................................................. 4-6
4.15 ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_A7HandoffRequestReceive
d...................................................................................................................... 4-6
4.16 ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_A7DropTargetReceived ........... 4-7
4.17 ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_A3DropReceived ..................... 4-7
4.18 ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_TwaitRlcExpired ...................... 4-7
4.19 ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_TwaitDrpTgtExpired................. 4-8
4.20 ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_RecvRlcReqWhenSoftHOA
dd.................................................................................................................... 4-8
4.21 ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_RecvRlcReqWhenSoftHODr
op.................................................................................................................... 4-8
4.22 ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_RecvRlcReqWhenSemiHOA
dd.................................................................................................................... 4-9
4.23 ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_RecvRlcReqWhenSCHExis
t....................................................................................................................... 4-9
4.24 ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_WrongChannelItemState.......... 4-9
4.25 ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_UnexpectedRlcState.............. 4-10
4.26 ERR_SPS_RLSA_BSSAP_HODrop_A1RequiredReject_OAMIntervention ........ 4-10
4.27 ERR_SPS_RLSA_BSSAP_HODrop_A1RequiredReject_EquipmentFailure ....... 4-10
4.28 ERR_SPS_RLSA_BSSAP_HODrop_A1RequiredReject_NoRadioResourceAv
ailable.............................................................................................................4-11
4.29 ERR_SPS_RLSA_BSSAP_HODrop_A1RequiredReject_RTRUnavailable ..........4-11
4.30 ERR_SPS_RLSA_BSSAP_HODrop_A1RequiredReject_BSNotEquipped...........4-11
4.31 ERR_SPS_RLSA_BSSAP_HODrop_A1RequiredReject_HandoffBlocked...........4-11
4.32 ERR_SPS_RLSA_BSSAP_HODrop_A1RequiredReject_RTAUnavailable ......... 4-12
4.33 ERR_SPS_RLSA_BSSAP_HODrop_A1RequiredReject_TimeOut..................... 4-12
4.34 ERR_SPS_RLSA_BSSAP_HODrop_A1RequiredReject_Unspecified ................ 4-12
4.35 SOFTADD_CELL_ERROR ............................................................................. 4-13
4.36 ERR_SPS_RLSA_DSPM_HOH_TimerExpired_SoftHOThocompletion .............. 4-13
4.37 ERR_SPS_RLSA_DSPM_HOH_TimerExpired_Thoreq .................................... 4-14
4.38 ERR_SPS_RLSA_DSPM_HOH_ResNotSatisfied_HOHOnUmrCFSearchRep
ort.................................................................................................................. 4-15
4.39 ERR_SPS_RLSA_DSPM_HOH_TimerExpired_SemiSoftHOThocompletion ...... 4-16
VIII
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

4.40 ERR_SPS_RLSA_DSPM_HOH_ResNotSatisfied_HOHOnA7rHOReqAck ......... 4-16


4.41 ERR_SPS_RLSA_DSPM_HOH_ResourceAllocFail_GetHandoffProc ................ 4-17
4.42 ERR_SPS_RLSA_DSPM_CLH_OtherReason_SDMSetISLPFailure.................. 4-19
4.43 ERR_SPS_RLSA_DSPM_HOH_FunCallFail_HOHOnDBSHOProcACK_PNS
ConstructFrmDBS .......................................................................................... 4-20
4.44 ERR_SPS_RLSA_DSPM_HOH_TimerExpired_Thocompletion ......................... 4-20
4.45 HO_STAT_DESTBSC_IS_HIRS_DATASOFTHO ............................................. 4-21
4.46 HO_STAT_PILOT_NOT_LOCALBSS .............................................................. 4-21
4.47 HO_Func_GetTargetFromPreCell_ERR ........................................................... 4-22
4.48 SOME_CELL_FAIL......................................................................................... 4-22
4.49 CELL_IS_ERROR .......................................................................................... 4-22
4.50 HO_STAT_PILOT_LIMITED ............................................................................ 4-23
4.51 ERR_SPS_RLSA_RCM_FCH_OtherReason_MRequestAbisConnect_Specifi
edCellIsReleasing........................................................................................... 4-23
4.52 ERR_SPS_RLSA_RCM_PCALL_RecvUnexptMsg_atTchStatusInSemiSoft_A
bisdfBurstRequest .......................................................................................... 4-24
4.53 HO_STAT_PILOT_IS_OTHER_UNLNKBSS .................................................... 4-24
4.54 HO_STAT_PILOT_NO_SAME_FREQ ............................................................. 4-25
4.55 HO_STAT_CARRIER_PWR_OVERLOAD ....................................................... 4-25
4.56 HO_STAT_CARRIER_STATE_MBLOCK ......................................................... 4-26
4.57 HO_STAT_CARRIER_STATE_RFE_BROKEN ................................................ 4-26
4.58 HO_STAT_CARRIER_STATE_RFE_LOWPOWER .......................................... 4-26
4.59 HO_STAT_CARRIER_STATE_BDS_DISCONNECT ........................................ 4-27
4.60 HO_STAT_CARRIER_STATE_RFE_POWERDOWN ....................................... 4-27
4.61 HO_STAT_CARRIER_RESOURCE_RESERVED ............................................ 4-27
4.62 HO_STAT_CARRIER_LIMITED ...................................................................... 4-28
4.63 HO_STAT_CARRIER_NO_CE........................................................................ 4-28
4.64 HO_STAT_CARRIER_NO_5KCE.................................................................... 4-29
4.65 HO_STAT_PILOT_IS_NOT_NEIGHBOR ......................................................... 4-29
4.66 BSC_NO_SE ................................................................................................. 4-30
4.67 BSC_NO_VE ................................................................................................. 4-30
4.68 BSC_NO_IWF................................................................................................ 4-31
4.69 BSC_DSPM_NO_INSTANCE ......................................................................... 4-31
4.70 BSC_NO_RTPPORT...................................................................................... 4-32
4.71 BSC_NO_VALID_RMP................................................................................... 4-33
4.72 HO_STAT_CARRIER_NO_CE_LICENSE........................................................ 4-33
4.73 HO_NoPilotAvailable_ERR ............................................................................. 4-34

IX
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

4.74 ERR_SPS_RLSA_RCM_FCH_FunCallFail_HandlerAbisdfConnectAck_MCS
HConstructAmdfFCHSetup ............................................................................. 4-34
4.75 ERR_SPS_RLSA_RCM_PCALL_FunCallFail_MHandlerTCHfTSSetup_MHan
dlerAbisdfBTSSetup ....................................................................................... 4-35
4.76 ERR_SPS_RLSA_RCM_FCH_MsgParaIncorrect_HandleAbisdfConnectAck_
SoftHandoffLegNoInvalid ................................................................................ 4-36
4.77 ERR_SPS_RLSA_RCM_PCALL_FunCallFail_MHandlerAbisdfBTSSetup_MC
DHSaveToCommonData................................................................................. 4-36
4.78 ERR_CES_RLSA_CEC_CALLHANDLER_V_ChannelType_Error ..................... 4-37

Chapter 5 Registration Failure Causes .................................................... 5-1


5.1 ERR_SPS_RLSA_BSSAP_Reg_Reject_Congestion ............................................ 5-1
5.2 ERR_SPS_RLSA_BSSAP_Reg_Reject_IllegalMs................................................ 5-1
5.3 ERR_SPS_RLSA_BSSAP_Reg_Reject_NetworkFailure....................................... 5-2
5.4 ERR_SPS_RLSA_BSSAP_Reg_Reject_RoamingNotAllowed............................... 5-2
5.5 ERR_SPS_RLSA_BSSAP_Reg_Reject_Other..................................................... 5-3
5.6 ERR_SPS_RLSA_BSSAP_SccpDisconnect_Release_In_Progress ...................... 5-3
5.7 ERR_SPS_RLSA_BSSAP_Reg_Reject_MinImsiUnknown.................................... 5-4

Chapter 6 Other Failure Causes................................................................ 6-1


6.1 ERR_SPS_RLSA_BSSAP_DiscardMsg_SmsNumOvld ........................................ 6-1
6.2 ERR_SPS_RLSA_BSSAP_MsgPara_A1fPACAUpdate_SBSSRInvalidProcess ..... 6-1
6.3 ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_A7BurstRequestReceived.......... 6-1
6.4 ERR_SPS_RLSA_DSPM_CLH_OtherReason_OVERLOAD ................................. 6-2
6.5 INPUT_PARA_ERROR ...................................................................................... 6-2

Glossary .......................................................................................................... I

X
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

About This Manual


Purpose
This manual provides information about the ZXC10 BSSB failure cause reference for the
1X service.

Intended Audience
This manual is intended for:
l
l

Network management engineers


Maintenance engineers

Prerequisite Skill and Knowledge


To use this document effectively, users should have a general understanding of wireless
telecommunications technologies. Familiarity with the following is helpful:
l
l

ZXC10 BSSB Base Station System


CDMA signaling flow

What Is in This Manual


This manual contains the following chapters:
Chapter

Summary

Chapter 1, Call Failure

Describes the causes of call failures and the handling measures.

Causes
Chapter 2, Call Drop
Causes
Chapter 3, Call Release
Causes
Chapter 4, Handoff
Failure Causes
Chapter 5, Registration
Failure Causes
Chapter 6, Other Failure
Causes

Describes the causes of call drop failures and the handling measures.

Describes the causes of call release failures and the handling measures.

Describes the causes of handoff failures and the handling measures.

Describes the causes of registration failures and the handling measures.

Describes the causes of other failures and the handling measures.

Related Documentation
The following documentation is related to this manual:
l

ZXC10 BSSB (V8.0.3.500) CDMA2000 Base Station System Failure Cause


Reference(DO)
I

SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

ZXC10 BSSB (V8.0.3.500) CDMA2000 Base Station System Failure Cause


Reference(PTT)

II
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

Chapter 1

Call Failure Causes


1.1 ERR_SPS_RLSA_BSSAP_FchSetup_ClearComma
nd_Unspecified
Failure Name

ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_Unspecified

Failure Cause

During call setup, the MSC sends a ClearCommand message to release the
call. The cause is unknown.

Failure Analysis

A non-standard cause value in A-interface protocol is carried in the


Cause of ClearCommand.

The cause carried in ClearCommand is Cause_A_CallProcessing. The


cause value carried in Layer 3 is 0x1f. This cause value corresponds to
the BSC internal cause value (ERR_SPS_RLSA_BSSAP_FchSetup_Cl
earCommand_Unspecified). This failure may be caused by an error on
the MSC, such as timer timeout, and access failure.

Possible Solution

It is acceptable if the problem occurs occasionally. If the problem occurs


frequently, check the fault probe and take measures after identifying the
cause.

ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_Unspecified

MSCClearCommand

ClearCommandCauseA

ClearCommandCauseCause_A_CallProcessing
Layer30x1fBSC
ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_Unsp
ecified

1-1
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

ZXC10 BSSB Failure Cause Reference(1X)

1.2 ERR_SPS_RLSA_BSSAP_TE_T3230
Failure Name

ERR_SPS_RLSA_BSSAP_TE_T3230

Failure Analysis

During call setup, the BSSAP sends a CMServiceRequest or


PagingResponse message to the MSC but fails to receive a returned
SccpConnect message before T3230 expires.

Possible Solution

1. Verify that No.7 signaling links are stable.


2. If the failure is caused by heavy traffic, add more signaling links.

ERR_SPS_RLSA_BSSAP_TE_T3230

BSSAPMSCCMServiceRequestPagingResponse
SccpConnectT3230

1.
2.

1.3 ERR_SPS_RLSA_BSSAP_TE_Tassignment
Failure Name
Failure Analysis

ERR_SPS_RLSA_BSSAP_TE_Tassignment
When a mobile station originates a call or is called, the BSSAP sends an
EV_S_AvfServiceAssignment message to the Data Service Management
Platform (DSMP), but fails to receive an EV_S_AvrAssignmentComplete
message or EV_S_AvrAssignmentFailure message from the DSMP before
timer Tassignment expires.
The possible failure causes are as follows:
1. Timer Tassignment expires too early.
2. The DSMP is configured with too many instances (more than the
number of DSMP instances that can be supported).
3. DSMP CPU utilization is too high.
4. SDM activation expires.

Handling Measure

1. Verify that the setting of timer Tassignment on CMP is correct. The


default value is 6000 (6 seconds).
2. Verify that the number of DSMP instances in the association between
RMP and DSMP is within the allowed range. Different DSMP versions
support different numbers of instances.
3. If DSMP CPU utilization is too high, add more DSMP modules.
4. If SDM activation expires, the media stream between SDU and CHM
may be different, or the clock between BSC and BTS is different. Verify
that the optical fiber connections at media plane and the SDU daughter
cards are correct.
1-2

SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

Chapter 1 Call Failure Causes

ERR_SPS_RLSA_BSSAP_TE_Tassignment

BSSAPDSMPEV_S_AvfServiceAssignment
DSMPEV_S_AvrAssignmentCompleteEV_S_AvrAssignmentFailureBSSAP
Tassignment:

Tassignment

DSMPDSMP

DSMPCPU

SDM

1.

CMPTassignment6000 6

2.

RMPDSMPDSMP
DSMP

3.

DSMPCPUDSMP

4.

SDMSDUCHMBSC
BTS
SDU

1.4 ERR_SPS_RLSA_BSSAP_FchSetup_RcvSccpDis
connect
Failure Name

ERR_SPS_RLSA_BSSAP_FchSetup_RcvSccpDisconnect

Failure Analysis

When a mobile station originates a call or is called, it sends a


CMServiceRequest or PagingResponse message to the MSC and receives
a SccpDisconnect message, indicating that the SCCP connection failed to
be established or exceptionally removed.
The possible failure causes are as follows:

Possible Solution

No.7 signaling links are unstable or in the wrong state.

The SSN is in the wrong state.

The mobile station did not assign numbers correctly on the MSC side.

The cell CI is different from the CI on the MSC side.

1. Use a database probe to verify that the signaling point state on the
CMP is 0.
2. Verify that the BSC and the MSC are configured with local and peer
SSNs (0, 1, and 254).
3. Verify that the IMSI and ESN of the mobile station distribute numbers
correctly on the MSC side.
4. Verify that the cell CI in the call origination message CMServiceRequest
is configured correctly on the MSC side.

1-3
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

ZXC10 BSSB Failure Cause Reference(1X)

ERR_SPS_RLSA_BSSAP_FchSetup_RcvSccpDisconnect

MSCCMServiceRequestPagingResponse
SccpDisconnectSCCP

SSN

MSC

CIMSCCI

1.

CMP0

2. BSCMSCSSN01254
3.

IMSIESNMSC

4.

CMServiceRequestCIMSC

1.5 ERR_SPS_RLSA_BSSAP_FchSetup_RcvMSRelea
seOrder
Failure Name

ERR_SPS_RLSA_BSSAP_FchSetup_RcvMSReleaseOrder

Failure Analysis

When a call is set up, the mobile station initiates a release on the control
channel.

Possible Solution

No troubleshooting is required.

ERR_SPS_RLSA_BSSAP_FchSetup_RcvMSReleaseOrder

1.6 ERR_SPS_RLSA_BSSAP_TE_Tfchsetup
Failure Name

ERR_SPS_RLSA_BSSAP_TE_Tfchsetup

Failure Cause

Timer Tfchsetup expires.

1-4
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

Chapter 1 Call Failure Causes

Failure Analysis

When a call is set up, the timer Tfchsetup on CMP expires. The BSC
sends an AbisdfBTSSetup message 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 possible failure causes are as follows:
l

Timer Tfchsetup expires too soon. The default value is 5000 (5


seconds).

Possible Solution

Fails to establish fundamental channel on BTS.

CCM CPU usage is too high.

1. Check the lifecycle of the predefined timer Tfchsetup. If it expires too


soon, change the setting to the default value of 5000.
2. Verify that there are enough CE and FO resources on the BTS.
3. If CCM CPU usage is too high, adjust the CCM CPU overload threshold,
or decrease the antenna transmission power to reduce users.

ERR_SPS_RLSA_BSSAP_TE_Tfchsetup

Tfchsetup

BSCBTSAbisdfBTSSetup
BTS
AbisdrBTSSetupAckCMPTfchsetup

Tfchsetup50005

BTS

CCMCPU

1.

Tfchsetup
5000

2.

BTSCEFO

3. CCMCPUCCMCPU

1.7 ERR_SPS_RLSA_BSSAP_TE_T303
Failure Name

ERR_SPS_RLSA_BSSAP_TE_T303

Failure Cause

Timer T303 expires.

1-5
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

ZXC10 BSSB Failure Cause Reference(1X)

Failure Analysis

When a mobile station originates a call or is called, it sends a


CMServiceRequest or PagingResponse message to the MSC. If no returned
AssignmentRequest message from MSC is received, the T303 timer on
the CMP will expire.
The possible failure causes are as follows:

Possible Solution

The T303 timer expires too soon.

The MSC side has a problem in call processing.

1. Verify that the timer T303 on the CMP is set to the default value 6000
(6 seconds).
2. T303 indicates that the MSC side has a problem in processing the call.
Use MSC tools to locate the failure causes.

ERR_SPS_RLSA_BSSAP_TE_T303

T303

MSCCMServiceRequestPagingResponse
MSCAssignmentRequest
CMPT303

T303

MSC

1.

CMPT30360006

2. MSCMSCT303MSC
MSC

1.8 ERR_SPS_RLSA_BSSAP_TE_Txxp
Failure Name

ERR_SPS_RLSA_BSSAP_TE_Txxp

Failure Cause

Timer Txxp expires.

Failure Analysis

1. After receiving an assignment complete message, the CallHandler


process sends an A1rAssignmentComplete message to the
MSCe. If the Ap interface is supported, timer Txxp waits for an
A1pfBearerUpdateRequest message from the MSCe.
2. The A1pfBearerUpdateRequest message from the MSCe is not
received before timer Txxp expires. The Txxp timer expires too soon.
3. The MSCe side has a problem in call processing.

Handling Measure

1. Check the setting of timer Txxp on the CMP. The default value is 6
seconds.
2. Locate the call failure causes on the MSCe side.

1-6
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

Chapter 1 Call Failure Causes

ERR_SPS_RLSA_BSSAP_TE_Txxp

Txxp

CallHandlerMSCe
A1rAssignmentCompletApTxxp
MSCeA1pfBearerUpdateRequest

TxxpMSCeA1pfBearerUpdateRequest
Txxp

MSCe

1.

CMPTxxp6

2. MSCeTxxpMSCe
MSCe

1.9 ERR_SPS_RLSA_BSSAP_DB_GetBoardOrIndexNe
tAddrByLogicAddr
Failure Name

ERR_SPS_RLSA_BSSAP_DB_GetBoardOrIndexNetAddrByLogicAddr

Failure Cause

Failure to retrieve the board network address based on the logical board
address.

Failure Analysis

When the BSC sends messages to the BTS, it invokes the database
interface to retrieve the BTS address. If it fails to invoke, the failure cause
will be reported.

Handling Measure

Verify that the Abis interface is stable.

ERR_SPS_RLSA_BSSAP_DB_GetBoardOrIndexNetAddrByLogicAddr

BSCBTSBTS

AbisAbis

1.10 ERR_SPS_RLSA_BSSAP_FchSetup_ClearComma
nd_CallProcessing
Failure Name

ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_CallProcessing

1-7
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

ZXC10 BSSB Failure Cause Reference(1X)

Failure Cause

When a call is set up, the BSC receives a ClearCommand message from
the MSC.

Failure Analysis

1. It is caused by the ClearCommand message from CallProcessing


(0x09).
2. A fault occurs in the MSC.

Handling Measure

Because ClearCommand is considered as a normal process, the cause


needs to be located on the MSC side. Normally, no troubleshooting is
required.

ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_CallProcessing

MSC

MSCCallProcessing(0x09)
ClearCommand

MSC

MSC

1.11 ERR_SPS_RLSA_BSSAP_FchSetup_ClearComma
nd_UserBusy
Failure Name

ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_UserBusy

Failure Cause

When a call is set up, the BSC receives a ClearCommand message sent
from the MSC, and the cause value in the CauseLayer3 field carried by
this message is 0x11, which indicates that the called user is busy. This
is a normal release.

Failure Analysis

The possible failure cause is that the called user is busy.

Handling Measure

No troubleshooting is required.

ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_UserBusy

BSCMSCClearCommand
CauseLayer30x11,

1-8
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

Chapter 1 Call Failure Causes

1.12 ERR_SPS_RLSA_BSSAP_FchSetup_ClearComma
nd_NormalClearing
Failure Name

ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_NormalClearing

Failure Cause

When a call is set up, the BSC receives a ClearCommand message sent
from the MSC, and the cause value in the CauseLayer3 field carried by this
message is 0x10, which indicates it is a normal release.

Failure Analysis

The possible failure cause is as follows: the release is initiated on the MSC
side.

Handling Measure

No troubleshooting is required.

ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_NormalClearing

BSCMSCClearCommand
CauseLayer30x10

MSC

1.13 ERR_SPS_RLSA_BSSAP_ByteIndex_IndexInUsed
Failure Name

ERR_SPS_RLSA_BSSAP_ByteIndex_IndexInUsed

Failure Cause

When a call is set up, the BSSAP module detects that the instance number
is used during instance number distribution.

Failure Analysis

The BSSAP module recorded a wrong instance number.

Possible Solution

It is acceptable if the problem occurs occasionally. If the problem occurs


frequently, check the fault probe and take measures after identifying the
cause.

ERR_SPS_RLSA_BSSAP_ByteIndex_IndexInUsed

BSSAP

BSSAP

1-9
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

ZXC10 BSSB Failure Cause Reference(1X)

1.14 ERR_SPS_RLSA_BSSAP_FchSetup_AllLegFail
Failure Name
Failure Cause

ERR_SPS_RLSA_BSSAP_FchSetup_AllLegFail
When a call is set up, the BSC sends an AbisdfBTSSetup message to the
BTS to request the BTS to establish a fundamental channel. However,
all the cells in the AbisdrBTSSetupAck returned by the BTS fail to be
established.

Failure Analysis

Possible Solution

CE resource shortage, CE resource is in the wrong state.

Walsh code shortage.

FO shortage.

UID is in the wrong state or the media plane link is incorrect.

Carrier is in wrong state.

1. The exact failure causes can be found in the AbisdrBTSSetupAck


message:
l

0x5101 indicates forward fundamental channel CE shortage.

0x5102 indicates fundamental channel reverse CE shortage.

0x5103 indicates fundamental channel forward shortage and


reverse CE shortage.

0x5105 indicates WalshCode shortage.

0x5106 indicates that the 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 plane link with a database probe.
5. Check the group number of CE on the CHM.
6. Verify that the software versions operating on the BSC and BTS are
the same.

ERR_SPS_RLSA_BSSAP_FchSetup_AllLegFail

BSCBTSAbisdfBTSSetupBTS
BTSAbisdrBTSSetupAck

CECE

WASH

FO

UID

1-10
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

Chapter 1 Call Failure Causes

1. AbisdrBTSSetupAck

2.

0x5101CE

0x5102CE

0x5103CE

0x5105WalshCode

0x5106UID

CE

3.

4.

UID

5.

CHMCE

6.

BSCBTS

1.15 ERR_SPS_RLSA_BSSAP_FchSetup_ClearComma
nd_NoAnswer
Failure Name

ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_NoAnswer

Failure Cause

When a call is set up, the BSC receives a ClearCommand message sent
from the MSC, and the cause value in the CauseLayer3 field carried by this
message is 0x13, which indicates it rings without an answer. This is normal.

Failure Analysis

The possible failure cause is as follows: Nobody answers the release


initiated by the MSC.

Handling Measure

No troubleshooting is required.

ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_NoAnswer

BSCMSCClearCommand
CauseLayer30x13

MSC

1.16 ERR_SPS_RLSA_BSSAP_Other_ReceiveResetC
ircuit
Failure Name

ERR_SPS_RLSA_BSSAP_Other_ReceiveResetCircuit

Failure Cause

When a call is being established or a call is being established after hard


handoff, the circuit reset message sent from the MSC is received.

1-11
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

ZXC10 BSSB Failure Cause Reference(1X)

Failure Analysis

Handling Measure

The CIC state on the MSC side and that on the BSC side are different.

The CIC code on the MSC side and that on the BSC side are different.

1. Verify that the CIC state on the MSC side and that on the BSC side
are consistent.
2. Verify that the PCM codes on both the MSC and BSC sides are
consistent with the E1 cable.

Further

Contact MSC maintenance personnel for troubleshooting.

Troubleshooting

ERR_SPS_RLSA_BSSAP_Other_ReceiveResetCircuit

MSC

MSCBSCCIC

MSCBSCCIC

1.

MSCBSCCIC

2.

MSCBSCPCME1

3.

MSC

1.17 ERR_SPS_RLSA_BSSAP_FchSetup_SendChanne
lAssignment_AllBtsFail
Failure Name

ERR_SPS_RLSA_BSSAP_FchSetup_SendChannelAssignment_AllBtsFail

Failure Cause

When a call is set up, the Extended Channel Assignment Message to all
BTS fails to be sent.

Failure Analysis

In ECAM/CAM message creation, no established cell is found.

In ECAM/CAM message creation, the retrieval of power parameters


from database fails.

Fails to retrieve the system ID/subsystem ID in accordance with PN


when sending the ECAM message.

There are coding errors when sending the ECAM message.


Fails to retrieve the interface board (ABPM/HGM) address from the
database when sending the ECAM message.

If there are cross-BSC assignments, the possible cause is failure to


retrieve the address of the BSC interconnection interface board.

1-12
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

Chapter 1 Call Failure Causes

Possible Solution

1. Check more detailed information by checking the fault probe.


2. Check version compatibility.

ERR_SPS_RLSA_BSSAP_FchSetup_SendChannelAssignment_AllBtsFail

BTSExtended Channel Assignment Message

ECAM/CAM

ECAM/CAM

ECAMPN/

ECAM

ECAMabpm/hgm

BSCBSC

1.

2.

1.18 ERR_SPS_RLSA_BSSAP_FchSetup_ClearComma
nd_HandoffSuccessful
Failure Name
Failure Cause

ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_HandoffSuccessful
When a call is being set up or during a call, if a ClearCommand message
sent from the MSC is received, the cause value carried in ClearCommand is
"hard handoff is successful".

Failure Analysis

1. If the hard handoff flow is successful, a Clear Command message will


be received from the MSC.
2. This failure should not occur when a call is being set up.

Handling Measure

If the failure occurs when a call is being set up, contact MSC maintenance
personnel for troubleshooting.

ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_HandoffSuccessful
MSCClearCommandClearCommand

MSCClear Command

1-13

SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

ZXC10 BSSB Failure Cause Reference(1X)

MSC

1.19 ERR_SPS_RLSA_BSSAP_FchSetup_ClearComma
nd_SemiConcurrentService
Failure Name

ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_SemiConcurrent
Service

Failure Cause

When a call is set up, during the forward fundamental channel establishment,
the ClearCommand message sent from the MSC is received, and 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. The
MSC sends a ClearCommand message to request the MS to enter Dormant
state.

Handling Measure

This failure is acceptable if it occurs infrequently. If the failure occurs


frequently, contact MSC maintenance personnel for troubleshooting.

ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_SemiConcurrentSer
vice

MSCClearCommand
ClearCommand

MSCClearCommandMSDormant

MSC

1.20 ERR_SPS_RLSA_BSSAP_MsgPara_Origination_I
nvalidServiceOption
Failure Name

ERR_SPS_RLSA_BSSAP_MsgPara_Origination_InvalidServiceOption

Failure Cause

The Service Option (SO) carried in the call origination message is invalid.

Failure Analysis

Terminal cause. The SO carried in the call origination message is invalid


(not the SO defined in the protocol).

Handling Measure

Determine what the SO is in the call origination message and if the terminal
is old or faulty.

ERR_SPS_RLSA_BSSAP_MsgPara_Origination_InvalidServiceOption
1-14

SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

Chapter 1 Call Failure Causes

SO

SOSOSO

SO

1.21 ERR_SPS_RLSA_BSSAP_HashOpr_AddItem_S
ccpId2CallRef
Failure Name

ERR_SPS_RLSA_BSSAP_HashOpr_AddItem_SccpId2CallRef

Failure Cause

When an SCCP connection number is added into the HASH entry of the
call reference number, the Hash operation fails.

Failure Analysis

Hash is probably hung up.

Handling Measure

Check the fault probe and take measures after identifying the cause.

ERR_SPS_RLSA_BSSAP_HashOpr_AddItem_SccpId2CallRef

SCCPHASHHash

Hash

1.22 ERR_SPS_RLSA_BSSAP_Other_Get97DMTMsPar
aFail
Failure Name

ERR_SPS_RLSA_BSSAP_Other_Get97DMTMsParaFail

Failure Cause

The 97D test fails to obtain the MSID of the terminated call.

Failure Analysis

The interface between modules is faulty.

Handling Measure

Save fault probe information and contact the local ZTE office.

ERR_SPS_RLSA_BSSAP_Other_Get97DMTMsParaFail

97DMSId

1-15
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

ZXC10 BSSB Failure Cause Reference(1X)

1.23 ERR_SPS_RLSA_BSSAP_FchSetup_ClearComm
and_EquipmentFailure
Failure Name

ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_EquipmentFailure

Failure Cause

When a call is set up, the MSC sends a ClearCommand message to release
the call, and the failure cause is equipment failure.

Failure Analysis

The MSC has an internal problem, and contact MSC maintenance personnel
for troubleshooting.

Possible Solution

It is acceptable if the problem occurs occasionally. If the problem occurs


frequently, check the fault probe and take measures after identifying the
cause.

ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_EquipmentFailure

MSCClearCommand

MSCMSC

1.24 ERR_SPS_RLSA_BSSAP_FchSetup_ClearComma
nd_AuthenticationFailure
Failure Name

ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_AuthenticationFai
lure

Failure Cause

When a call is set up, the MSC sends a ClearCommand message to release
the call due to authentication failure.

Failure Analysis

The terminal is invalid.

Handling Measure

Contact MSC maintenance personnel for troubleshooting.

ERR_SPS_RLSA_BSSAP_FchSetup_ClearCommand_AuthenticationFailu
re

MSCClearCommand

MSC

1-16
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

Chapter 1 Call Failure Causes

1.25 ERR_SPS_RLSA_BSSAP_FchSetup_AllLegAreR
emoved
Failure Name

ERR_SPS_RLSA_BSSAP_FchSetup_AllLegAreRemoved

Failure Cause

During call setup, the channel board detects that the RCM sends an
EV_S_AbisdrTargetRemovalRequest message to the BSSAP to release the
call. After receiving the message, the BSSAP releases the call.

Failure Analysis

Possible Solution

Timer Tassingment is set to over 6 seconds.

Transmission at the Abisc port is unstable.

The clock is wrong.

The IC of the channel board has a problem.

1. Check the timer setting.


2. Check the Abisc port transmission.
3. Check the BTS clock.
4. Check the IC of the channel board.

ERR_SPS_RLSA_BSSAP_FchSetup_AllLegAreRemoved

RCMRCM
BSSAPEV_S_AbisdrTargetRemovalRequestBSSAP

Tassingment6

Abis

1.

2.

Abis

3.

BTS

4.

1.26 ERR_SPS_RLSA_BSSAP_Other_SpcfSelectTabl
eBad
Failure Name

ERR_SPS_RLSA_BSSAP_Other_SpcfSelectTableBad

Failure Cause

During data service setup, SPCF is not detected in the normal state.

Failure Analysis

The PCF configuration is incomplete.

No RP link is available.

No UPCF is available.

1-17
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

ZXC10 BSSB Failure Cause Reference(1X)

Possible Solution

1. Verify that the PCF configuration is normal.


2. Verify that the network communication between the PCF and PDSN is
normal and the PDSN is operating properly.
3. Verify that the UPCF board is operating properly.

ERR_SPS_RLSA_BSSAP_Other_SpcfSelectTableBad

SPCF

PCF

RP

UPCF

1.

PCF

2.

PCFPDSNPDSN

3.

UPCF

1.27 ERR_SPS_RLSA_BSSAP_Other_RTDOutofRange
Failure Name

ERR_SPS_RLSA_BSSAP_Other_RTDOutofRange

Failure Cause

During call setup, the mobile station is beyond the RTD distance limit of
the cell.

Failure Analysis

Handling Measure

The possible causes are as follows:


l

The distance between the MS and the BTS is out of the specified range.

The RTD configuration in the cell parameters is unreasonable.

If the mobility restriction function is enabled, ignore the problem; otherwise,


adjust the RTD distance limit parameters on the OMC.

ERR_SPS_RLSA_BSSAP_Other_RTDOutofRange

RTD

1.

2.

RTD

OMC
RTD

1-18
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

Chapter 1 Call Failure Causes

1.28 ERR_SPS_RLSA_BSSAP_MultiSP_InvalidMSCOff
iceId
Failure Name

ERR_SPS_RLSA_BSSAP_MultiSP_InvalidMSCOfficeId

Failure Cause

The network has multiple signaling points, and the correct office direction
number fails to be selected.

Failure Analysis

1. The data service paging response cannot select the correct office
direction number.
2. The voice originating call and paging response, data service originating
call, and other service paging and paging response cannot select the
correct office direction number.

Handling Measure

1. Verify that the office direction selection switch for data paging response
(DataPagingRspOfficeIdSelect) is set correctly.
2. Verify that the selection switch for common office direction
(CallOfficeIdSelect) is set correctly.

ERR_SPS_RLSA_BSSAP_MultiSP_InvalidMSCOfficeId

1. DataPagingRspOfficeIdSelect

2.

CallOfficeIdSelect

1.29 ERR_SPS_RLSA_BSSAP_MultiSP_MSCOfficeU
navailable
Failure Name

ERR_SPS_RLSA_BSSAP_MultiSP_MSCOfficeUnavailable

Failure Cause

The network has multiple signaling points. The state of the selected office
direction is abnormal and results in call failure.

Failure Analysis
Handling Measure

The abnormal office direction state results in call failure.


Verify that the signaling link configuration and the physical link in the office
direction are normal.

ERR_SPS_RLSA_BSSAP_MultiSP_MSCOfficeUnavailable
1-19

SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

ZXC10 BSSB Failure Cause Reference(1X)

1.30 ERR_SPS_RLSA_BSSAP_MultiSP_A1fAssignR
eq_InvalidMSCOfficeId
Failure Name

ERR_SPS_RLSA_BSSAP_MultiSP_A1fAssignReq_InvalidMSCOfficeId

Failure Cause

The network has multiple signaling points. The office direction number in
the A1fAssignmentRequest message is wrong.

Failure Analysis

The internal flow is abnormal.

Handling Measure

Save the signaling track, service observation, and fault probe, and contact
the R&D personnel for troubleshooting.

ERR_SPS_RLSA_BSSAP_MultiSP_A1fAssignReq_InvalidMSCOfficeId

A1fAssignmentRequest

1.31 ERR_SPS_RLSA_BSSAP_MsgPara_MSRejectOr
der
Failure Name

ERR_SPS_RLSA_BSSAP_MsgPara_MSRejectOrder

Failure Cause

During call setup, the terminal refuses the forward message from the BSC.

Failure Analysis

If the user is called while preparing to dial at the fixed station, the
terminal will refuse the ECAM/CAM messages.

Possible Solution

Some terminals refuse the service negotiation messages.

Make analysis from signaling in other situations.

The occasional occurrence of the above is normal. If the problem occurs


frequently, check the fault probe and take measures after identifying the
cause.

ERR_SPS_RLSA_BSSAP_MsgPara_MSRejectOrder

1-20

SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

Chapter 1 Call Failure Causes

ECAM/CAM

1.32 ERR_SPS_RLSA_BSSAP_Other_Encode_A1Ms
gInBSC
Failure Name

ERR_SPS_RLSA_BSSAP_Other_Encode_A1MsgInBSC

Failure Cause

Message coding failure of the A interface.

Failure Analysis

The coding failure is caused by incorrect A interface message type, format,


and length.

Handling Measure

The failure is caused by incorrect A interface message. It is acceptable if


the problem occurs occasionally. If the problem occurs frequently, contact the
R&D personnel for troubleshooting.

1.33 ERR_SPS_RLSA_BSSAP_Other_Encode_UmpMs
gInBSC
Failure Name

ERR_SPS_RLSA_BSSAP_Other_Encode_UmpMsgInBSC

Failure Cause

Air interface message coding failure.

Failure Analysis

The coding failure may result from an error in the type, assignment mode,
format or length of the air interface message.

Handling Measure

The failure results from multiple factors. Contact MSC maintenance


personnel for troubleshooting.

1.34 ERR_SPS_RLSA_BSSAP_Other_Decode_UmpMs
gInBSC
Failure Name

ERR_SPS_RLSA_BSSAP_Other_Decode_UmpMsgInBSC

Failure Cause

Air interface message decoding failure.


1-21

SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

ZXC10 BSSB Failure Cause Reference(1X)

Failure Analysis

The decoding failure may result from an error in the type, format or length of
the air interface message.

Handling Measure

The failure results from an incorrect air interface message. If the failure
occurs occasionally, no troubleshooting is required.
If the failure occurs frequently, contact terminal maintenance personnel for
troubleshooting.

1.35 ERR_SPS_RLSA_BSSAP_TE_Ta1_4
Failure Name

ERR_SPS_RLSA_BSSAP_TE_Ta1_4

Failure Cause

The Ta1_4 timer expires.

Failure Analysis

After an A1rReset message is sent to the MSC, the MSC does not respond
before the Ta1_4 timer expires. The A1rReset message is retransmitted 30
times at most, and then the system enters the normal operating status.

Handling Measure

The failure results from A interface link disconnection. If it occurs


occasionally, it is normal.
If it occurs frequently, check the status of the link connecting the MSC.

1.36 ERR_SPS_RLSA_BSSAP_PoorPilot
Failure Name

ERR_SPS_RLSA_BSSAP_PoorPilot

Failure Cause

The pilot strength is weak when the MS makes a call.

Failure Analysis

When the Reject Weak Pilot switch is enabled, the system will report the
exception if the pilot strength carried in the originating call message is lower
than the threshold set in the OMC.

Handling Measure

Verify that the setting of the threshold is reasonable. If the exception occurs
frequently, check the local signal or contact the local ZTE office.

1.37 ERR_SPS_RLSA_BSSAP_FchSetup_SendPCHM
sg_AllBtsFail
Failure Name

ERR_SPS_RLSA_BSSAP_FchSetup_SendPCHMsg_AllBtsFail

Failure Cause

The paging channel message fails to be transmitted.

Failure Analysis

The failure may result from intermittent bit error bursts over the Abis link.

Handling Measure

Check the Abis link. If it is abnormal, contact the local ZTE office.

1-22
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

Chapter 1 Call Failure Causes

1.38 ERR_SPS_RLSA_BSSAP_DB_GetLinkInfo
Failure Name

ERR_SPS_RLSA_BSSAP_DB_GetLinkInfo

Failure Cause

A failure occurs when the database EV_D_S_GetLinkAndLacNumByModule_V interface is invoked to get the signaling link message.

Failure Analysis

The database is abnormal or a version mismatch occurs.

Handling Measure

Verify that the RMP and CMP versions are matched.

1.39 ERR_SPS_RLSA_BSSAP_DB_GetValidCarrier
Failure Name

ERR_SPS_RLSA_BSSAP_DB_GetValidCarrier

Failure Cause

The configured carrier ID of the first carrier fails to be obtained.

Failure Analysis

The database is abnormal or the configuration is incorrect.

Handling Measure

Verify that the carrier configuration is correct.

1.40 ERR_SPS_RLSA_BSSAP_DB_GetOPBySysIdC
ellIdCrId
Failure Name

ERR_SPS_RLSA_BSSAP_DB_GetOPBySysIdCellIdCrId

Failure Cause

An exception occurs when the database is invoked to get the OP value.

Failure Analysis

The database is abnormal.

Handling Measure

Contact technical personnel of the database.

1.41 ERR_SPS_RLSA_DSPM_CLH_TimerExpired_Tw
aitorder
Failure Name

ERR_SPS_RLSA_DSPM_CLH_TimerExpired_Twaitorder

Failure Cause

When an MS originates a call or is called, after successfully entering the


traffic channel and capturing the prefix, the air-interface traffic channel
signaling handshake expires.

Failure Analysis

Poor radio condition results in air-interface handshake message loss. It


is acceptable if this failure occurs occasionally.

If frame number checking is enabled, the BTS and the BSC have
different clocks.

Other causes: such as bit errors.


1-23

SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

ZXC10 BSSB Failure Cause Reference(1X)

Possible Solution

1. Verify that the transmission power of the cell is normal.


2. Ensure the version compatibility and proper operation of the CHM and
SDU boards.
3. If the failure occurs frequently, check whether the problem is caused
by a single base station, all base stations under an ABPM), or the
whole BSC.
4. After locating the fault, disable the frame number checking on the faulty
BTS. If the situation improves, it indicates that the problem is caused by
different BTS and BSC clocks. Verify that the GPS and clock are normal,
and the GCM boards on the BTS and BSC sides operate properly.
5. Ensure correct versions and proper operation of the ABPM, DTB, and
DSM interface boards.

ERR_SPS_RLSA_DSPM_CLH_TimerExpired_Twaitorder

MS

BTSBSC

1.

2.

CHMSDU

3.

ABPMBSC

4.

BTS
BTSBSC
GPSBTSBSCGCM

5.

ABPMDTBDSM

1.42 ERR_SPS_RLSA_BSSAP_Other_DifferenceInFw
dOrRevRC
Failure Name
Failure Cause

ERR_SPS_RLSA_BSSAP_Other_DifferenceInFwdOrRevRC
During a call test, the forward RC handoff judgment and reverse RC handoff
judgment of the fundamental channel are different.

Failure Analysis

The RC that is configured for the call test and its SO do not match.

1-24
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

Chapter 1 Call Failure Causes

Handling Measure

Modify the RC to be an available RC of the corresponding SO. If you are not


clear about the mapping between SOs and RCs, contact ZTE Corporation
for analysis.

1.43 ERR_SPS_RLSA_DSPM_CLH_OtherReason_SNF
ailure
Failure Name

ERR_SPS_RLSA_DSPM_CLH_OtherReason_SNFailure

Failure Cause

When an MS originates a call or is called, after entering the traffic channel,


the service negotiation between the base station and the MS fails.

Failure Analysis

The possible failure causes are as follows:


1. Poor radio condition causes air-interface negotiation message missing.
It is acceptable if this failure occurs occasionally.
2. The VTC operating mode configured on the BSS has a problem.

Handling Measure

1. Verify that the forward power of the cell is normal.


2. If the negotiation failure occurs frequently on the mobile stations of a
specific model, verify that the VTC operating mode configured on the
BSS is correct (default setting: 8K+EVRC).

Further

If the problem persists, capture the call failure signaling and contact the

Troubleshooting

local ZTE office.

ERR_SPS_RLSA_DSPM_CLH_OtherReason_SNFailure

MSMS

BSSVTC

1.

2. BSSVTC
8K+EVRC
3.

4.

1.44 ERR_SPS_RLSA_DSPM_CLH_TimerExpired_Tp
cfinfol3
Failure Name

ERR_SPS_RLSA_DSPM_CLH_TimerExpired_Tpcfinfol3

1-25
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

ZXC10 BSSB Failure Cause Reference(1X)

Failure Cause

During data service call setup, after the A8 link is established, the DSPM
sends an Abaf_PCFInfoL3 message to the SDM, but fails to receive a
response in Tpcfinfol3 (3s), and timer Tpcfinfol3 expires.

Failure Analysis

Possible Solution

Timer Tpcfinfol3 has a problem in setting.

The corresponding SDU operates improperly.

1. Verify that the setting of timer Tpcfinfol3 on the DSMP board is correct
(default value: 3 s).
2. Verify that the corresponding SDU operates properly, and there is no
abnormal reset or switchover.
3. Ensure correct version and proper operation of the SDU.

ERR_SPS_RLSA_DSPM_CLH_TimerExpired_Tpcfinfol3

A8DSPMSDMAbaf_PCFInfoL3
Tpcfinfol33 sTpcfinfol3

Tpcfinfol3

SDU

1. DSMPTpcfinfol33 s
2.

SDU

3.

SDU

1.45 ERR_SPS_RLSA_DSPM_SCHH_TimerExpired_T
fschbstreq
Failure Name
Failure Cause

ERR_SPS_RLSA_DSPM_SCHH_TimerExpired_Tfschbstreq
In FSCH establishment, after the BSC sends a BurstRequest message,
the BurstResponse message from the BTS is not received, and timer
Tfschbstreq expires.

Failure Analysis

The message is lost at the Abis interface. It is acceptable if the problem


occurs occasionally.

Possible Solution

1. Verify that the setting of timer Tfschbstreq is correct (500 ms).


2. Verify that the message is not lost.
3. Ensure correct versions and proper operation of the CCM, ABPM, DTB,
and DSM boards.

ERR_SPS_RLSA_DSPM_SCHH_TimerExpired_Tfschbstreq

FSCHBSCBurstRequestTfschbstreq
BTSBurstResponse

1-26
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

Chapter 1 Call Failure Causes

Abis

1.

Tfschbstreq500 ms

2.

3. CCMABPMDTBDSM

1.46 ERR_SPS_RLSA_DSPM_CLH_OtherReason_PD
SNDenied_Reason_Unspecified
Failure Name

ERR_SPS_RLSA_DSPM_CLH_OtherReason_PDSNDenied_Reason_Uns
pecified

Failure Cause

During data service call setup, the A8 link setup fails. When the cause value
that the PDSN brings to the DSPM is 0x80, the failure cause is reported by
the DSPM.

Failure Analysis

The possible failure causes are as follows:


1. The A10 link setup fails.
2. The corresponding PCF operates improperly. There is abnormal reset
or switchover.

Handling Measure

1. Verify that the A10 link is successfully established.


2. Verify that the corresponding PCF operates properly, and there is no
abnormal reset or switchover.

ERR_SPS_RLSA_DSPM_CLH_OtherReason_PDSNDenied_Reason_Un
specified

A8PDSNDSPM
0x80DSPM

A10

PCF

A10

1.47 ERR_SPS_RLSA_DSPM_CLH_OtherReason_Ta8
setup
Failure Name

ERR_SPS_RLSA_DSPM_CLH_OtherReason_Ta8setup

Failure Cause

During data service call setup, the A8 link establishment expires: The
DSPM sends an A9SetupA8 message to the PCF, but fails to receive a reply
message in Ta8setup (3 s).
1-27

SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

ZXC10 BSSB Failure Cause Reference(1X)

Failure Analysis

Possible Solution

In the OMC, the PCF IP address configuration has a problem.

The physical link is broken.

The corresponding PCF is faulty.

1. Verify that the setting of the Ta8setup timer (default value is 3 s) on


the DSMP board is correct.
2. Verify that the PCF IP address configuration in the OMC is correct and
the physical link is normal.
3. Verify that the corresponding PCF operates properly and there is no
abnormal reset or switchover.

ERR_SPS_RLSA_DSPM_CLH_OtherReason_Ta8setup

A8DSPMA9SetupA8
PCFTa8setup3 s

OMCPCF IP

PCF

1. DSMPTa8setup3 s
2.

OMCPCF IP

3.

PCF

1.48 ERR_SPS_RLSA_DSPM_CLH_OtherReason_PDS
NDenied_Reason_Administratively_Pohibited
Failure Name

ERR_SPS_RLSA_DSPM_CLH_OtherReason _PDSNDenied_Reason_
Administratively_Pohibited

Failure Cause

During data service call setup, the A8 link setup fails when the cause value
that the PDSN brings to the DSPM is 0x81, and the failure cause is reported
by the DSPM.

Failure Analysis

The possible failure causes are as follows:


1. The A10 link setup fails.
2. The corresponding PCF operates improperly. There is abnormal reset
or switchover.

Handling Measure

1. Verify that the A10 link is successfully established.


2. Verify that the corresponding PCF operates properly, and there is no
abnormal reset or switchover.

1-28
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

Chapter 1 Call Failure Causes

ERR_SPS_RLSA_DSPM_CLH_OtherReason _PDSNDenied_Reason_Ad
ministratively_Pohibited

A8PDSNDSPM
0x81DSPM

A10

PCF

A10

1.49 ERR_SPS_RLSA_DSPM_CLH_OtherReason_PCF
Denied_PDSN_Resource_Unavailable
Failure Name

ERR_SPS_RLSA_DSPM_CLH_OtherReason_PCFDenied_PDSN_Resour
ce_Unavailable

Failure Cause

During data service call setup, the A8 link setup fails. The cause value that
the PCF brings to the DSPM is that the PDSN resource is unavailable.

Failure Analysis

The possible failure causes are as follows:


1. The A10 link setup fails.
2. The PDSN is faulty.

Handling Measure

1. Verify that the A10 link is successfully established.


2. Verify that the corresponding PDSN operates properly, and there is
no abnormal reset or switchover.

ERR_SPS_RLSA_DSPM_CLH_OtherReason_PCFDenied_PDSN_Resour
ce_Unavailable

A8PCFDSPM
PDSN

A10

PDSN

1.

A10

2.

PDSN

1.50 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SC
HHOnUmrSCHRequestMsg_FCHNotExisted
Failure Name

ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnUmrSCHReques
tMsg_FCHNotExisted
1-29

SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

ZXC10 BSSB Failure Cause Reference(1X)

Failure Cause

The data service fundamental channel receives a message from the SCH
for setup.

Failure Analysis

The possible failure cause is as follows: The call origination flow has not
finished.

Handling Measure

It is acceptable if the problem occurs occasionally. If the problem occurs


frequently, contact the local office of ZTE Corporation.

ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnUmrSCHReques
tMsg_FCHNotExisted

1.51 ERR_SPS_RLSA_DSPM_SCHH_ResNotSatisfied_
SCHHOnFwdAllBurstResponse_NoCommitedCell
Failure Name

ERR_SPS_RLSA_DSPM_SCHH_ResNotSatisfied_SCHHOnFwdAllBurstR
esponse_NoCommitedCell

Failure Cause

When the BSC applies for establishment of a forward supplementary


channel, there is no successful cell in the BTS response.

Failure Analysis

Shortage of BTS resources, such as CE, power, Walsh code, and UID.

Handling Measure

Analyze the current traffic of this BTS and check the occupancy of all
resources. If the occupancy state accords with traffic capacity, the resource
shortage is the failure cause of setting up the supplementary channel. If the
occupancy state is greatly different from the traffic capacity,
1. Verify that this BTS operates properly and the version is correct.
2. Verify that the resources are not blocked and the resource state is
correct.
3. If the above are normal, maybe the resources such as CE, power,
Walsh code, and UID are occupied by other requests.

ERR_SPS_RLSA_DSPM_SCHH_ResNotSatisfied_SCHHOnFwdAllBurstR
esponse_NoCommitedCell

BSCBTS

BTSCEWalshUID

1-30
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

Chapter 1 Call Failure Causes

BTS

1.

BTS

2.

3.

4.

1.52 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_S
CHHOnAcrBSCAddChannelItemAck_AddChannel
ItemFailed
Failure Name

ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnAcrBSCAddCha
nnelItemAck_AddChannelItemFailed

Failure Cause

Adding the forward supplementary channel table fails.

Failure Analysis

1. Failure value 1: The entered parameters are incorrect.


2. Failure value 2: The channel table is not created.
3. Failure value 3: No ENTRY space is available.
4. Failure value 4: No BLOCK space is available.
5. Failure value 5: No ENTRY space is available.
6. Failure value 6: The keyword for adding the channel table is too long.
7. Failure value 7: The number of UIDs is inconsistent with that in the
multicast group.

Handling Measure

1. Verify that the ABPM and IBBE boards are normal.


2. Obtain more details by querying the fault probe.

ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnAcrBSCAddCha
nnelItemAck_AddChannelItemFailed

ENTRY3

BLOCK4

COLLISION5

UID7

1.

ABPMIBBE

2.

1-31
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

ZXC10 BSSB Failure Cause Reference(1X)

1.53 SDM_Activate_Fail_AcquirePreambleFail_Normal
Failure Name
Failure Analysis

SDM_Activate_Fail_AcquirePreambleFail_Normal
The MS capture fails; The BSC has not received Preamble sent by the MS
before timeout, but Idle frames can be received. There are many reasons for
this fault. Any problem in the system can cause failure in MS capture, such
as wrong CHM version, inconsistency in parameters for the MS and those
of the base station, long code error, inconsistent RC, and PN offset error.

Possible Solution

1. Check the CHM version.


2. Check the failure cause submitted to the fault probe.
3. Verify that there are residual forward CEs in the RB_FWDCE list.
4. Verify that the channel board does not block CE.

SDM_Activate_Fail_AcquirePreambleFail_Normal

BSCPreamble
Idle
CHM
RCPN

1.

CHM

2.

3.

RB_FWDCECE

4.

CE

1.54 SDM_Activate_Fail_AcquirePreambleFail_NoRe
vFrm
Failure Name

SDM_Activate_Fail_AcquirePreambleFail_NoRevFrm

Failure Analysis

The BSC cannot receive the reverse traffic frame sent by the BTS before
the timer expires. There are many possible causes:

Possible Solution

The link for the Abis media flow is blocked.

The channel list is incorrectly added on either the BTS or the BSC.

1. Verify that the Abis link is not disconnected.


2. Verify that the addition of channel list (the BSC and BTS sides) in
signaling tracing is successful.
3. Verify that no CE is suspended on the CHM board.

SDM_Activate_Fail_AcquirePreambleFail_NoRevFrm

1-32
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

Chapter 1 Call Failure Causes

BTSBSC
BSCBTS

Abis

BTSBSC

1.

Abis

2.

BSCBTS

3.

CHMCE

1.55 SDM_Find_Fail_WaitConfigVTCTimeout
Failure Name

SDM_Find_Fail_WaitConfigVTCTimeout

Failure Cause

After SDM activation, the SDM does not receive the EV_S_AbafStartVocoderCoding message sent by the DSPM before the timer expires.

Failure Analysis

The possible causes are as follows:


1. Service negotiation between Layer 3 and the MS fails and Layer 3 does
not receive a confirmation message from the MS. Detailed reasons vary:
l

The MS does not receive the confirmation message on the BS side,


so it does not return a confirmation message to the BS.

The MS has received a confirmation message on the BS side, but it


does not return the confirmation to the BS.

The fault may also be caused by inconsistent parameters between


the MS and the BS side (such as RC inconsistency), which results
in the MS unable to detect the confirmation message on the base
station.

2. Abnormal Layer 3 process. After successful negotiation with the MS,


the EV_S_AbafStartVocoderCoding message is not sent to the SDM.
Handling Measure

1. Verify that there is a handshake message (EV_S_UmfBSOrder or


EV_S_UmrMSOrder) of the traffic channel.
2. If neither messages exists, the reason might be inconsistent parameters
on the MS and BS sides. Check the versions of the MS and BS sides.
3. If the handshake is normal, check whether the signaling has an
EV_S_AbafStartVocoderCoding message; if no, the DSPM has not
sent a message.

SDM_Find_Fail_WaitConfigVTCTimeout

1-33
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

ZXC10 BSSB Failure Cause Reference(1X)

SDMDSPMSDM
EV_S_AbafStartVocoderCoding
l

BS
BSBS
BSBSRC

EV_S_AbafStartVocoderCodingSDM

1.

EV_S_UmfBSOrder
EV_S_UmrMSOrder

2.

MSBSMS
BS

3.

EV_S_AbafStartVocoderCoding
DSPM

1.56 SDM_Find_Fail_WaitConfigRLPTimeout
Failure Name

SDM_Find_Fail_WaitConfigRLPTimeout

Failure Analysis

When waiting for an EV_S_AbafPCFInfoL3 message sent by Layer 3 after


successful data service SDM activation, the message is not received before
the timer expires.

Handling Measure

1. Verify that the PCF is correctly configured.


2. Verify that the UPCF board operates properly.

SDM_Find_Fail_WaitConfigRLPTimeout

SDMEV_S_AbafPCFInfoL3

1.57 SDM_Link_Fail_RSCHLegLinkFail
Failure Name

SDM_Link_Fail_RSCHLegLinkFail

Failure Analysis

The RSCH leg does not receive the frames sent from the reverse channel
in 18 s.

Handling Measure

1. Check the signaling and verify that the CHM has released the leg.
2. Verify that the reverse link has no problem.
3. Check CHM statistics for frame receiving and sending.
1-34

SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

Chapter 1 Call Failure Causes

SDM_Link_Fail_RSCHLegLinkFail

18 s

1.

CHM

2.

3.

CHM

1.58 SDM_Activate_Fail_InitVocoderFail
Failure Name

SDM_Activate_Fail_InitVocoderFail

Failure Cause

The SDM fails to send an initialized Vocoder message.

Failure Analysis

The CPU utilization of the SDU board is too high.

The bottom level has a problem.

Handling Measure

1. If the SDU board utilization ratio is too high, add an additional new
board.
2. If the SDU board is normal but the fault persists, contact the local ZTE
office.

SDM_Activate_Fail_InitVocoderFail

SDMSDUCPU

1.

SDUSDU

2.

SDU

1.59 SDM_OprVocoder_Fail_WaitStartVocoderCodin
gAckTimeOut
Failure Name

SDM_OprVocoder_Fail_WaitStartVocoderCodingAckTimeOut

Failure Cause

The SDM cannot receive an ACK message from the VTC after sending a
startVocoderCoding message to the VTC.

Failure Analysis

The startVocoderCoding message or the ACK message is lost among


boards.

Handling Measure

Contact engineers at local ZTE office.

SDM_OprVocoder_Fail_WaitStartVocoderCodingAckTimeOut

1-35
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

ZXC10 BSSB Failure Cause Reference(1X)

SDMVTCstartVocoderCodingVTCACK
startVocoderCoding
ACK

1.60 SDM_Activate_Fail_MsgParaFail
Failure Name

SDM_Activate_Fail_MsgParaFail

Failure Cause

The SDM receives a AbafActivateSDM message sent by Layer 3, but the


parameter(s) in the message are incorrect.

Handling Measure

Check the SDM fault probe message to locate the wrong parameter(s).
Check the AbafActivateSDM message in signaling tracing to locate the
fault and determine whether Layer 3 is incorrectly written or it is an SDM
process problem.

SDM_Activate_Fail_MsgParaFail

SDMAbafActivateSDM

SDM
AbafActivateSDMSDM

1.61 DBS_STASTIC_FWDFCHCE_REVCE_LACK
Failure Name

DBS_STASTIC_FWDFCHCE_REVCE_LACK

Failure Cause

When the MS originates a call or is called, the basic channel fails to be set
up due to inadequate forward or reverse CEs.

Failure Analysis

The forward and reverse CE resources are inadequate.

Possible Solution

1. Check the failure cause submitted in the fault probe.


2. Verify that there are residual forward CEs in the RB_FWDCE list,
meaning the CEs with status position of 0 (INDEX is 0-31).
3. Verify that there are residual reverse CEs in the RB_REVCE list,
meaning the CEs with status position of 0 (INDEX is 64-95).
4. Verify that the channel board does not block the CE.

DBS_STASTIC_FWDFCHCE_REVCE_LACK

MSCE

1-36

SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

Chapter 1 Call Failure Causes

CE

1.

2.

RB_FWDCECE0CE
INDEX0~31

3.

RB_REVCECE0CE
INDEX64~95

4.

CE

1.62 DBS_STASTIC_FWDFCHCE_LACK
Failure Name

DBS_STASTIC_FWDFCHCE_LACK

Failure Cause

When the MS originates a call or is called, the basic channel fails to be set
up due to inadequate forward CEs on the 5K channel board.

Failure Analysis

The forward CEs on the 5K channel board are inadequate.

Possible Solution

1. Check the failure causes submitted in the fault probe.


2. Verify that there are residual forward CEs in the RB_FWDCE list.
3. Verify that the channel board does not block the CE.

DBS_STASTIC_FWDFCHCE_LACK

MS5KCE

CE

1.

2.

RB_FWDCECE

3.

CE

1.63 DBS_STAT_WALSHCODE_LACK
Failure Name

DBS_STAT_WALSHCODE_LACK

Failure Cause

When the MS originates a call or is called, resource distribution fails due to


WALSH CODE distribution failure when the basic channel is being set up.

Failure Analysis

No WALSH CODE is available under the carrier.

Possible Solution

1. Check the failure causes submitted in the fault probe.


2. Use the probe to check whether there is free resource in WALSH CODE.

DBS_STAT_WALSHCODE_LACK
1-37

SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

ZXC10 BSSB Failure Cause Reference(1X)

MSWALSHCODE

WALSHCODE

1.

2.

WALSHCODE

1.64 DBS_STAT_UID_LACK
Failure Name

DBS_STAT_UID_LACK

Failure Cause

When the MS originates a call or is called, resource distribution fails due


to UID distribution failure when the basic channel is being set up by the
IP platform.

Failure Analysis

There is no available broadband under the sector or failure occurs in


bandwidth distribution.

Possible Solution

1. Check the failure causes submitted in the fault probe.


2. Use the probe to check whether the LeftBandWidth field in the R_UID
list is larger than 9.

DBS_STAT_UID_LACK
MSIPUID

1.

2.

R_UIDLeftBandWidth9

1.65 DBS_STAT_NO_RESOURCE_LACK
Failure Name

DBS_STAT_NO_RESOURCE_LACK

Failure Cause

The failure is not caused by inadequate resource.

Failure Analysis

This is the default error code of database resource distribution. It indicates


a data error or parameter error in a list in the system.

Possible Solution

Check the failure causes submitted in the fault probe.

DBS_STAT_NO_RESOURCE_LACK

1-38
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

Chapter 1 Call Failure Causes

1.66 FCH_NUMBER_TWO
Failure Name

FCH_NUMBER_TWO

Failure Cause

When a supplementary channel is being set up, the subscriber has two
basic data channels.

Failure Analysis

The subscriber is in semi soft handoff status.

Possible Solution

1. As it is stipulated, setting up a supplementary channel is not permitted


when the subscriber is in semi soft handoff status. The BTS resource
distribution error has no influence.
2. Check the DSPM and RCM to solve the problem of originating the
supplementary channel setup in semi soft handoff status.

FCH_NUMBER_TWO

1.

BTS

2.

DSPMRCM

1.67 ARRIVE_TIME_ERROR
Failure Name

ARRIVE_TIME_ERROR

Failure Cause

During supplementary channel confirmation, there is not enough time to


configure the channel board before the supplementary channel start time.

Failure Analysis

Possible Solution

The link delay on the Abis port is too long.

The clocks of the BTS and the BSC are inconsistent.

1. Solve the clock problem of the BTS and the BSC.


2. Optimize the link delay on the Abis port.

ARRIVE_TIME_ERROR

1-39
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

ZXC10 BSSB Failure Cause Reference(1X)

Abis

BTSBSC

1.

BTSBSC

2.

Abis

1.68 NO_SYSTEM_TIME
Failure Name

NO_SYSTEM_TIME

Failure Cause

When the supplementary channel resources are being reserved, the CCM
DBS has no system time.

Failure Analysis

The HIRS platform does not send the system time to the CCM because
of instantaneous CHM failure.

l
Possible Solution

The IP platform SCS does not send the system time to the DBS.

Locate the failure cause by checking the fault probe, and then troubleshoot
accordingly.

NO_SYSTEM_TIME

CCM DBS

HIRSCHMCCM

IPSCSDBS

1.69 NO_AVAILABLE_REV_CE
Failure Name

NO_AVAILABLE_REV_CE

Failure Cause

When a reverse supplementary channel is being set up, no reverse CE


is available.

Failure Analysis

CE resources are inadequate.

Handling Measure

Expand the capacity.

NO_AVAILABLE_REV_CE

CE

CE

1-40

SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

Chapter 1 Call Failure Causes

1.70 FO_NOT_ENOUGH
Failure Name

FO_NOT_ENOUGH

Failure Cause

When a reverse complementary channel is being set up, no frame offset


is available.

Failure Analysis

The possible failure causes are as follows:


1. Inadequate frame offset because the frame offset of the reverse
supplementary channel is the same as the FCH.
2. The FCH has more data on the same frame offset, and reverse
supplementary channels have been set up.

Handling Measure

Expand the capacity.

FO_NOT_ENOUGH

FCH
FCH

1.71 CE_NOT_ENOUGH
Failure Name

CE_NOT_ENOUGH

Failure Cause

No forward supplementary channel CE is available when a forward


supplementary channel is being set up.

Failure Analysis

Too many forward supplementary channels are set up and forward


supplementary channel CEs are insufficient.

Possible Solution

Capacity expansion is required.

CE_NOT_ENOUGH

CE

CE

1.72 WALSHCODE_NOT_ENOUGH
Failure Name

WALSHCODE_NOT_ENOUGH

1-41
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

ZXC10 BSSB Failure Cause Reference(1X)

Failure Cause

No Walsh code is available when a forward supplementary channel is being


set up.

Failure Analysis

Too many forward supplementary channels are set up and the Walsh code
is insufficient.

Possible Solution

Capacity expansion is required.

WALSHCODE_NOT_ENOUGH

Walsh

Walsh

1.73 BEFORE_CPS
Failure Name

BEFORE_CPS

Failure Cause

Application for forward supplementary channels is too early during the


process of scheduling and continuous transmission.

Failure Analysis

The possible failure cause is as follows: The system clocks of the BTS
and the BSC are inconsistent.

Handling Measure

Verify that the GCM board has no alarm.

BEFORE_CPS

BTSBSC

GCM

1.74 UIDWIDTH_NOT_ENOUGH
Failure Name

UIDWIDTH_NOT_ENOUGH

Failure Cause

UID bandwidth is insufficient during resource distribution of supplementary


channels.

Failure Analysis

Abis bandwidth is insufficient.

Possible Solution

Capacity expansion is required.

UIDWIDTH_NOT_ENOUGH
1-42

SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

Chapter 1 Call Failure Causes

UID

Abis

1.75 RS_NOT_EXIST
Failure Name

RS_NOT_EXIST

Failure Cause

Records to which the RS list corresponds are unavailable during resource


distribution of supplementary channels.

Failure Analysis

This failure is caused by the scheduling algorithm of supplementary


channels.

Handling Measure

No troubleshooting is required.

RS_NOT_EXIST

RS

A
BAFCH
FCHRS

1.76 ALLOCATE_UID_ERROR
Failure Name

ALLOCATE_UID_ERROR

Failure Cause

UID distribution fails during resource distribution of supplementary channels.

Failure Analysis

Instantaneous UID failure.

Possible Solution

Stabilize the UID status.

ALLOCATE_UID_ERROR

UID

UID

UID

1-43
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

ZXC10 BSSB Failure Cause Reference(1X)

1.77 BSC_CICFROMMSC_ERR

BSC_CICFROMMSC_ERR

AMSCCIC

MSCCICBSC

Failure Name

BSC_CICFROMMSC_ERR

Failure Cause

The CIC that is assigned by the MSC to the A interface is incorrect.

Failure Analysis

The CIC that is assigned by the MSC is not available on the BSC side.

Handling Measure

Check the A interface configuration.

1.78 HO_STAT_SERVICE_FORBID
Failure Name

HO_STAT_SERVICE_FORBID

Failure Cause

A service forbids the call to access the carrier.

Failure Analysis

During call access, the data service forbids it to access the voice carrier or
the voice service forbids it to access the data carrier.

Handling Measure

For voice service, check switch 78 and the attribute of the carrier to be
accessed. For data service, check switch 80 and the attribute of the carrier
to be accessed.

1.79 ERR_SPS_RLSA_RCM_DBAccFail_FCHResour
ceAllocate
Failure Name

ERR_SPS_RLSA_RCM_DBAccFail_FCHResourceAllocate

Failure Cause

When the MS originates a call or is called, it fails to invoke the database


interface resource during FCH setup.

Failure Analysis

Input parameter mistake of the database.

CE resource is not enough or abnormal.

Walsh codes are not enough.

FO is not enough.

UID is not enough.

1-44
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

Chapter 1 Call Failure Causes

Possible Solution

1. Check the failure cause in the EV_S_AbisdrBTSSeupAck message


reported in signal tracing.
l

0x5064: forward channel CE is not enough.

0x5065: reverse CE is not enough.

0x5066: forward channel CE and reverse CE are not enough.

2. After confirming the failure cause, verify that the CHM board is normal
(the chip-set and CE are normal).
3. If the CHM and CCM are normal, it is possible that the resource is
hung up.

ERR_SPS_RLSA_RCM_DBAccFail_FCHResourceAllocate

MS

CE

Walsh

FO

UID

1.

EV_S_AbisdrBTSSeupAck

2.

0x5064CE

0x5065CE

0x5066CE

CE

3.

CHMCCM

1.80 ERR_SPS_RLSA_RCM_PCALL_OtherReason_C
EC_REMOVEREQ
Failure Name
Failure Analysis

ERR_SPS_RLSA_RCM_PCALL_OtherReason_CEC_REMOVEREQ
During the call process, the CHM board requests to release the current
call after detecting no frame in the forward channel (the default time is 6
s), meaning the CHM does not receive the SDU forward frame, and the
procedure is released. The possible failure causes are as follows:
l

The IP or MAC value is invalid.

Invalid Key value results in searching table address error.

The channel table position is invalid.

The SDM does not set up a leg.

The DSP on the VTC board has a problem.

1-45
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

ZXC10 BSSB Failure Cause Reference(1X)

Possible Solution

1. Verify that the SDM has set up a leg.


2. Verify that the IP and MAC values are correct.
3. If this problem occurs frequently, the probable cause is that the DSP
has a problem.

ERR_SPS_RLSA_RCM_PCALL_OtherReason_CEC_REMOVEREQ
6 s
CHM6sSDU

IPMAC

Key

SDM

VTCDSP

1.

SDM

2.

IPMAC

3.

DSP

1.81 ERR_SPS_RLSA_RCM_FCH_TimerExpired_Tco
nnExpired
Failure Name

ERR_SPS_RLSA_RCM_FCH_TimerExpired_TconnExpired

Failure Analysis

During call setup, the Abis interface timer expires when resources are being
set up. This starts the call release procedure and results in call failure.
The timer is triggered after the BTS assigns the radio resource and service
address and informs the BSC. If a BSC Ack message is not received before
the timer expires, the BTS starts the release procedure.
The reason for the BTS not receiving the Ack message is link and message
blocking and wrong message contents on the BTS.

Possible Solution

1. Verify that the Abis link is normal.


2. Verify that the parameters (such as cell information in tAbisConnectInfo)
in the AbisdrConnect message carried by the BTS to the BSC are
correct.

ERR_SPS_RLSA_RCM_FCH_TimerExpired_TconnExpired

1-46
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

Chapter 1 Call Failure Causes

Abis

Tconnb4 sBTS
BSCBSCAck
BTS
BTSAckBTS

1.
2.

Abis
BTSBSCAbisdrConnect
AbisdfBTSSetuptAbisConnectInfo

1.82 ERR_SPS_RLSA_RCM_FSCH_FunCallFail_AddC
hannelFail
Failure Name

ERR_SPS_RLSA_RCM_FSCH_FunCallFail_AddChannelFail

Failure Analysis

During call setup, this failure occurs when the IP platform BTS adds a
channel table. The possible reason is that too many channel tables are
added at one time.

Handling Measure

1. If the problem occurs in ordinary voice, verify that the channel table
is not hung up.
2. If the problem occurs during data service procedure, it is normal.
3. If no call adds many channel tables at one time (ordinary voice), it
indicates that the resource is hung up. Contact the local ZTE office.

ERR_SPS_RLSA_RCM_FSCH_FunCallFail_AddChannelFail
IPBTS

1.

2.

1.83 ERR_SPS_RLSA_RCM_FSCH_TimerExpired_Tfsc
hNotifyExpired
Failure Name

ERR_SPS_RLSA_RCM_FSCH_TimerExpired_TfschNotifyExpired
1-47

SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

ZXC10 BSSB Failure Cause Reference(1X)

Failure Cause

During data service, the timer expires before the notification message of
database resource reservation is received.

Handling Measure

Verify that the voice traffic is not too heavy. If this case occurs frequently,
contact the local ZTE office.

ERR_SPS_RLSA_RCM_FSCH_TimerExpired_TfschNotifyExpired

1.

2.

1.84 ERR_SPS_RLSA_RCM_FCH_OtherReason_MRe
questAbisConnect_SameTimeCellInSameGroupIn
DiffSetupFlow
Failure Name

ERR_SPS_RLSA_RCM_FCH_OtherReason_MRequestAbisConnect_Sam
eTimeCellInSameGroupInDiffSetupFlow

Failure Analysis

During a call, multiple cells in the same leg are not allowed to set up FCHs
in multiple procedures. This results in resource setup failure.

Possible Solution

It is normal. The cause is code limitation.

ERR_SPS_RLSA_RCM_FCH_OtherReason_MRequestAbisConnect_Sam
eTimeCellInSameGroupInDiffSetupFlow

FCH

1.85 ERR_SPS_RLSA_RCM_PMAIN_FunCallFail_Main
Entry_MAbisdMsgDispatch
Failure Name

ERR_SPS_RLSA_RCM_PMAIN_FunCallFail_MainEntry_MAbisdMsgD
ispatch

Failure Analysis

During call setup, the main RCM process fails to forward messages to the
Handler process.
l

All subprocesses of the RCM are busy.

The RCM has no idle Handler process.


1-48

SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

Chapter 1 Call Failure Causes

Possible Solution

If the number of calls at one time is more than the upper limit of process
quantity, the failure is normal (upper limits: HIRS CCM is 300, BDM is
75, and IP CCM is 600). If the number of calls is fewer and this problem
occurs, the probable cause is that the OSS has changed the upper limit of
processes. In this case, contact the local ZTE office.

ERR_SPS_RLSA_RCM_PMAIN_FunCallFail_MainEntry_MAbisdMsgD
ispatch

RCMHandler

RCM

RCMHandler

HIRS CCM 300BDM 75IP CCM 600


OSS

1.86 ERR_SPS_RLSA_RCM_FCH_OtherReason_MReq
uestAbisConnect_ServiceRestrict
Failure Name

ERR_SPS_RLSA_RCM_FCH_OtherReason_MRequestAbisConnect_Ser
viceRestrict

Failure Analysis

During handoff, because the service type for handoff is among the restricted
service of the destination cell, the cell handoff fails. The service types
include voice, data, PTT enhanced calls, and private calls.

Handling Measure

In OMC configuration management, cancel the service restriction on the


cell node.

ERR_SPS_RLSA_RCM_FCH_OtherReason_MRequestAbisConnect_Ser
viceRestrict

PTT

1-49
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

ZXC10 BSSB Failure Cause Reference(1X)

1.87 ERR_SPS_RLSA_RCM_FSCH_FunCallFail_Burst
Request_ConnInSetup
Failure Name
Failure Analysis

ERR_SPS_RLSA_RCM_FSCH_FunCallFail_BurstRequest_ConnInSetup
During forward supplementary channel setup, there is another concurrent
setup flow, causing the channel setup failure.

Handling Measure

Finish setting up the previous scheduling before starting the next one.

ERR_SPS_RLSA_RCM_FSCH_FunCallFail_BurstRequest_ConnInSetup

1.88 ERR_SPS_RLSA_RCM_RSCH_FunCallFail_Burst
Request_SaveToGroupedCellInfoSet_CellNumIsZ
ero
Failure Name

ERR_SPS_RLSA_RCM_RSCH_FunCallFail_BurstRequest_SaveToGroup
edCellInfoSet_CellNumIsZero

Failure Analysis

During reverse supplementary channel setup, no valid cell information is


available, causing the channel setup failure.

Handling Measure

In setting up the reverse supplementary channel, the cells corresponding


to the CIs specified in the BurstRequest message do not exist, that is, the
cells are invalid. If the failure occurs frequently, contact the local office
of ZTE Corporation.

ERR_SPS_RLSA_RCM_RSCH_FunCallFail_BurstRequest_SaveToGroup
edCellInfoSet_CellNumIsZero

BurstRequestCI

1-50
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

Chapter 1 Call Failure Causes

1.89 ERR_SPS_RLSA_RCM_PCALL_RecvUnexptMsg_
atTchStatusInSemiSoft_AbisdfBurstCommit
Failure Name

ERR_SPS_RLSA_RCM_PCALL_RecvUnexptMsg_atTchStatusInSemiSoft
_AbisdfBurstCommit

Failure Analysis

During the semi-soft handoff, supplementary channel setup is rejected.

Handling Measure

No troubleshooting is required.

ERR_SPS_RLSA_RCM_PCALL_RecvUnexptMsg_atTchStatusInSemiSoft
_AbisdfBurstCommit

1.90 ERR_SPS_RLSA_RCM_RSCH_FunCallFail_AddC
hannelFail
Failure Name

ERR_SPS_RLSA_RCM_RSCH_FunCallFail_AddChannelFail

Failure Analysis

During call setup, adding a channel table on the BTS side fails. The
probable cause is that a large number of channel tables are being added
at the same time. The problem normally occurs during the data service
supplementary channel setup process. If the problem occurs for the voice
service, the probable cause is that the channel table is suspended.

Handling Measure

1. If the problem occurs during data services, it is normal.


2. If the problem occurs during common voice services, and the problem
is not caused by adding a large number of channel tables at the same
time, then the cause is that the resources are suspended. In this case,
contact the local office of ZTE Corporation.

ERR_SPS_RLSA_RCM_RSCH_FunCallFail_AddChannelFail
IPBTS

1.

2.

1-51
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

ZXC10 BSSB Failure Cause Reference(1X)

1.91 ERR_SPS_RLSA_RCM_RSCH_FunCallFail_Burst
Commit_GetConnRecordByGroupId
Failure Name

ERR_SPS_RLSA_RCM_RSCH_FunCallFail_BurstCommit_GetConnRe
cordByGroupId

Failure Analysis

In the case of data service, after the BurstCommit message is received,


the corresponding leg fails to be found, causing the failure in setting up
the supplementary channel. The cause is that the message is received
after timeout, and the leg has been released. The Abis interface delay may
cause the problem.

Handling Measure

If the problem occurs during data services, it is normal.

ERR_SPS_RLSA_RCM_RSCH_FunCallFail_BurstCommit_GetConnRe
cordByGroupId

BurstCommit
Abis

1.92 BSC_NO_CIC
Failure Name

BSC_NO_CIC

Failure Cause

No CIC (ground circuit) resource is available in the system.

Failure Analysis

No CIC resource available: CIC resource configuration error, CIC resource


status is abnormal or insufficient CIC resource.

Possible Solution

1. Verify that the ground circuit (CIC) configuration of port A is correct.


l

Verify that the PCM configuration at port A is consistent with the


PCM No. configuration on the MSS.

Verify that the trunk configuration is consistent with the timeslot


configuration on the MSS.

Verify that the DT board to which the CIC corresponds is correctly


attributed to the RMP module.

2. Verify that the DT board to which the CIC corresponds operates properly
and its version is correct.
3. Verify that the E1 physical connection to which the CIC corresponds is
correct.
4. Verify that the CIC resource is manually blocked in dynamic
management.

1-52
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

Chapter 1 Call Failure Causes

5. Verify that the CIC resource quantity meets the requirements of traffic
capacity.

BSC_NO_CIC

CIC

CICCICCICCIC

1.

ACIC
l

APCMPCM

PCM

CICDTRMP

2.

CICDT

3.

CICE1

4.

CIC

5.

CIC

1.93 POWER_NOT_ENOUGH
Failure Name

POWER_NOT_ENOUGH

Failure Cause

Inadequate power.

Failure Analysis

Carrier power surpasses the threshold for supplementary channel


setup.

Residual power is unable to set up a forward supplementary channel


with a rate of over 2X.

Subscriber radio condition is relatively poor, and the required power


surpasses the maximum transmission power of the supplementary
channel set by the OMC.

Possible Solution

Capacity expansion is required.

POWER_NOT_ENOUGH

2X

OMC

1-53
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

ZXC10 BSSB Failure Cause Reference(1X)

1.94 BSC_NO_SE
Failure Name

BSC_NO_SE

Failure Cause

No SE resource is available in the system.

Failure Analysis

No SE resource available: SDU configuration error, SE resource status is


abnormal, or SE resource is insufficient.

Possible Solution

1. Verify that the 1XSDU board is correctly configured.


2. Verify that the SDU board operates properly and its version is correct.
3. If the AP interface is installed in the RTP, verify that the SDU virtual
address configuration is correct.
4. Verify that the status of the daughter card of the SDU board and of
INDEX is normal in dynamic management.
5. Verify that the SE resource quantity meets the requirements of traffic
capacity.

BSC_NO_SE

SE

SESDUSESE

1.

1XSDU

2.

SDU

3.

APRTPSDU

4.

SDUINDEX

5.

SE

1.95 BSC_NO_VE
Failure Name

BSC_NO_VE

Failure Cause

No VE resource is available in the system.

Failure Analysis

No VE resource available: VTC configuration error, abnormal VE resource


status, or insufficient VE resource.

Possible Solution

1. Verify that the resource frame where the CIC is located is configured
correctly with corresponding quantity of VTC boards.
2. Verify that the VTC board operates properly and the CPU/DSP version
is correct.
3. Verify that the VTC board and INDEX status is normal in dynamic
management.
4. Verify that the VE resource quantity meets the requirements of traffic
capacity.

1-54
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

Chapter 1 Call Failure Causes

BSC_NO_VE

VE

VEVTCVEVE

1.

CICVTC

2.

VTCCPU/DSP

3.

VTCINDEX

4.

VE

1.96 BSC_NO_IWF
Failure Name

BSC_NO_IWF

Failure Cause

No IWF resource is available in the system.

Failure Analysis

IWF resource unavailable: IWF configuration error, abnormal IWF resource


status, or insufficient IWF resource.

Handling Measure

1. Verify that the IWFB board is correctly configured, especially in the


case that the CIC is not selected.
2. Verify that the IWFB board operates properly and the CPU/DSP version
is correct.
3. Verify that the status of the IWFB board and INDEX is normal in
dynamic management.
4. Verify that the IWF resource quantity meets the requirements of traffic
capacity.

BSC_NO_IWF

IWF

IWFIWFIWFIWF

1.

IWFBCIC
CICIWFB

2.

IWFBCPU/DSP

3.

IWFBINDEX

4.

IWF

1.97 BSC_DSPM_NO_INSTANCE
Failure Name

BSC_DSPM_NO_INSTANCE

Failure Cause

No DSPM example is available in the system.

1-55
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

ZXC10 BSSB Failure Cause Reference(1X)

Failure Analysis

DSPM example unavailable: DSPM configuration error, DSPM status


abnormal, or insufficient DSPM examples.

Possible Solution

1. Verify that the DSPM module is correctly configured, and a proper


quantity of DSPM examples is configured.
2. Verify that the MP daughter card where the DSPM module is located
operates properly and its version is correct.
3. Check the module list in the probe view, and verify that the DSPM is in
normal status.
4. Verify that the quantity of DSPM examples meet the requirements of
traffic capacity.

BSC_DSPM_NO_INSTANCE

DSPM

DSPMDSPMDSPMDSPM

1.

DSPMDSPM

2.

DSPMMP

3.

DSPM

4.

DSPM

1.98 BSC_NO_RTPPORT
Failure Name

BSC_NO_RTPPORT

Failure Cause

No RTPPORT resource is available in the system. This failure cause is


submitted only in the case of external RTP.

Failure Analysis

Unavailable RTPPORT resource: configuration error, abnormal status of


RTP port, or insufficient RTPPORT resource.

Handling Measure

1. In the case of external RTP, verify that the IPI board and RTP port are
correctly configured.
2. Verify that the IPI board where RTP port is located operates properly
and its version is correct.
3. Verify that the status of RTPPORT resource is normal during dynamic
management.
4. Verify that the RTPPORT resource quantity meets the requirements of
traffic capacity.

BSC_NO_RTPPORT

RTPPORTRTP
1-56

SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

Chapter 1 Call Failure Causes

RTPPORTRTPRTPPORT

1. RTPIPIRTP
2.

RTPIPI

3.

RTPPORT

4.

RTPPORT

1.99 BSC_NO_VALID_RMP
Failure Name

BSC_NO_VALID_RMP

Failure Cause

No RMP module is available in the system.

Failure Analysis

Unavailable RMP module: RMP module configuration error, or abnormal


RMP status.

Possible Solution

1. Verify that the RMP module is correctly configured in the system.


2. Verify that the MP daughter card where the RMP module is located
operates properly and its version is correct.
3. Check the module list in the probe view, and verify that the RMP module
status is normal.

BSC_NO_VALID_RMP

RMP

RMPRMPRMP

1.

RMP

2.

RMPMP

3.

RMP

1.100 ERR_SPS_RLSA_RCM_FCH_FunCallFail_Han
dlerAbisdfConnectAck_MCSHConstructAmdfFC
HSetup
Failure Name

ERR_SPS_RLSA_RCM_FCH_FunCallFail_HandlerAbisdfConnectAck_MC
SHConstructAmdfFCHSetup

Failure Analysis

During call setup or handoff, when channel resources are configured, an


error occurs in the construction of the channel resource configuration
message. The problem normally occurs on the cell where a control channel
is not configured.
1-57

SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

ZXC10 BSSB Failure Cause Reference(1X)

Handling Measure

On the OMC configuration management, verify that the control channel is


configured for the cell (sector) with the problem.
If the control channel is not configured, configure the control channel and
synchronize data.
If the control channel is configured, contact the local ZTE office.

ERR_SPS_RLSA_RCM_FCH_FunCallFail_HandlerAbisdfConnectAck_MC
SHConstructAmdfFCHSetup

OMC

1.101 ERR_SPS_RLSA_RCM_PCALL_FunCallFail_MH
andlerTCHfTSSetup_MHandlerAbisdfBTSSetup
Failure Name

ERR_SPS_RLSA_RCM_PCALL_FunCallFail_MHandlerTCHfTSSetup_
MHandlerAbisdfBTSSetup

Failure Analysis

During call setup or handoff, an error occurs in handling the call setup or
handoff message .

Handling Measure

1. In the case that the BTS is in graceful degradation mode, when the BTS
receives the call setup or handoff message from the BSC, the BTS
reports the failure message. It is a normal case.
2. The RCM does not support concurrent setup flows. If the RCM receives
another call setup or handoff message during the leg setup process, the
RCM reports the failure message. If the problem occurs occasionally,
no troubleshooting is required.
3. If the BSSAP or DSPM handoff type is incorrect, the failure message is
also reported. If the problem occurs occasionally, no troubleshooting
is required.

ERR_SPS_RLSA_RCM_PCALL_FunCallFail_MHandlerTCHfTSSetup_
MHandlerAbisdfBTSSetup

1-58
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

Chapter 1 Call Failure Causes

1.

BSC

2. RCM

3. BSSAPDSPM

1.102 ERR_SPS_RLSA_RCM_FCH_MsgParaIncorrect
_HandleAbisdfConnectAck_SoftHandoffLegNoIn
valid
Failure Name

ERR_SPS_RLSA_RCM_FCH_MsgParaIncorrect_HandleAbisdfConnectAc
k_SoftHandoffLegNoInvalid

Failure Analysis

During call setup or handoff process, the leg number leg in the
AbisdfConnectAck message exceeds the maximum allowed value. A call
supports up to 12 legs. If the leg number exceeds 12, a call failure may
be caused.

Handling Measure

If the problem occurs frequently, contact the local representative office of


ZTE Corporation.

ERR_SPS_RLSA_RCM_FCH_MsgParaIncorrect_HandleAbisdfConnectAc
k_SoftHandoffLegNoInvalid

AbisdfConnectAck

1212

1.103 ERR_SPS_RLSA_RCM_PCALL_FunCallFail_MHa
ndlerAbisdfBTSSetup_MCDHSaveToCommonData
Failure Name

ERR_SPS_RLSA_RCM_PCALL_FunCallFail_MHandlerAbisdfBTSSetup_
MCDHSaveToCommonData

Failure Analysis

An error occurs in saving data during call setup or handoff handling.


1. The handoff type in the call setup or handoff message is incorrect.
2. The CI and frequency point in call setup or handoff message are
incorrect, so the carrier cannot be found based on the CI and frequency
point.

1-59
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

ZXC10 BSSB Failure Cause Reference(1X)

Handling Measure

If the a few such problems occur, ignore them. If a lot of such problems
occur, contact the local office of ZTE Corporation.

ERR_SPS_RLSA_RCM_PCALL_FunCallFail_MHandlerAbisdfBTSSetup_
MCDHSaveToCommonData

1.

2.

CICI

1.104 ERR_CES_RLSA_CEC_CALLHNDL_FCH_SETUP
_CE_IN_USED
Failure Name

ERR_CES_RLSA_CEC_CALLHNDL_FCH_SETUP_CE_IN_USED

Failure Cause

During FCH setup, the CE is hung up and results in FCH channel setup
failure.

Failure Analysis

The CPU usage ratio of the CHM board is too high.

An UB alarm exists in the CHM board.

SDH transmission at the BTS side is not stable.

Too many CSM daughter cards installed on a single CHM board


(IP-BTS supports 6, and HIRS BTS supports 4 chipsets).

Possible Solution

The CES code is abnormal, and the resource is not released.

The upper level is abnormal and the release is not started.

1. If the CPU usage ratio is too high, block some CSM daughter cards.
2. Check the SDH transmission.
3. Check the clock module.
4. Allocate some control channels to other boards.
5. If the problem persists, reset the CHM.

ERR_CES_RLSA_CEC_CALLHNDL_FCH_SETUP_CE_IN_USED

CESCE

CPU

UB

IP6HIRS4

CES

1-60

SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

Chapter 1 Call Failure Causes

1.

CPU

2.

3.

4.

5.

CHM

1.105 ERR_CES_RLSA_CEC_CALLHNDL_FCH_SET
UP_RCV_CEM_REJECT
Failure Name

ERR_CES_RLSA_CEC_CALLHNDL_FCH_SETUP_RCV_CEM_REJECT

Failure Cause

During FCH setup, after the CEC layer sends the FCH setup message
to the CEM layer, the CEM layer rejects the message, causing the FCH
setup failure.

Failure Analysis

The CPU usage of the CHM is too high.

UB alarms exist on the CHM.

There is a problem with the CHM clock.

There is a problem with the CES code, and the resources are not
released.

l
Possible Solution

There is an upper-layer problem, and the resources are not released.

1. If the CPU usage of the CHM is too high, block some daughter cards.
2. Check the clock module.
3. Assign specific control channels to the other boards.
4. If the measures above do not work, reset the CHM.

ERR_CES_RLSA_CEC_CALLHNDL_FCH_SETUP_RCV_CEM_REJECT

CECCEMCEM

CPU

UB

CES

1.

CPU

2.

3.

4.

CHM

1-61
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

ZXC10 BSSB Failure Cause Reference(1X)

1.106 ERR_CES_RLSA_CEC_CALLMAIN_FCH_SETU
P_CREATE_PROCESS
Failure Name

ERR_CES_RLSA_CEC_CALLMAIN_FCH_SETUP_CREATE_PROCESS

Failure Cause

When FCH channel is in set up, process establishment fails.

Failure Analysis

Error occurs when calling the V_OutputBySrc function.

The version is incorrect.

Possible Solution

1. Solve the lower level problem.


2. Block the faulty CHM board.

ERR_CES_RLSA_CEC_CALLMAIN_FCH_SETUP_CREATE_PROCESS

V_Create

1.

2.

1.107 ERR_CES_RLSA_CEC_CALLMAIN_FCH_SETUP
_OUTPUT_MSG_TO_CALLHNDL
Failure Name

ERR_CES_RLSA_CEC_CALLMAIN_FCH_SETUP_OUTPUT_MSG_TO_
CALLHNDL

Failure Cause

In the case of FCH setup, the CallMain process fails to send message to the
Callhandler process.

Failure Analysis

Handling Measure

The possible causes may be as follows:


l

Error occurs when calling the V_OutputBySrc function.

Version error.

1. Solve the bottom-layer problem.


2. Block the channel board with the problem.

ERR_CES_RLSA_CEC_CALLMAIN_FCH_SETUP_OUTPUT_MSG_TO_
CALLHNDL

CallMainCallhandler

V_OutputBySrc

1-62

SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

Chapter 1 Call Failure Causes

1.

2.

1.108 ERR_CES_RLSA_CEC_CALLHNDL_FCH_SETU
P_RCV_CEM_RSP_TIMER_OUT
Failure Name

ERR_CES_RLSA_CEC_CALLHNDL_FCH_SETUP_RCV_CEM_RSP_TI
MER_OUT

Failure Cause

During FCH setup, after the CEC layer sends the FCH setup message
to the CEM layer, the CEM layer response times out, causing the FCH
setup failure.

Failure Analysis

The possible causes may be as follows:


l

The CPU ultilization of the CHM is too high.

There exist UB alarms on the CHM.

There is a problem with the CHM clock.

There is a problem with the CES code, and the resources are not
released.

l
Handling Measure

There is an upper-layer problem, and the resources are not released.

1. If the CPU ultilization of the CHM is too high, block some daughter cards.
2. Check the clock module.
3. Assign specific control channels to the other boards.
4. If the above measures do not work, reset the CHM.

ERR_CES_RLSA_CEC_CALLHNDL_FCH_SETUP_RCV_CEM_RSP_TI
MER_OUT

CECCEMCEM

CPU

UB

CES

1.

CPU

2.

3.

4.

CHM

1-63
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

ZXC10 BSSB Failure Cause Reference(1X)

1.109 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP
_PARAM_POINTER_NULL
Failure Name

ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_POINTER
_NULL

Failure Cause

During FCH setup, the structure pointer is a null pointer in the CES
verification channel setup command, causing the FCH channel setup failure.

Failure Analysis

Handling Measure

The possible causes may be as follows:


l

The CHM version and CCM version do not match.

A CES error occurs.

An upper-layer error occurs.

1. Make the CHM version and the CCM version consistent.


2. Soft reset the CHM.
3. If the above measures do not work, reset the CCM.

ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_POINTER
_NULL

CES

CHMCCM

CES

1.

2.

CHM

3.

CCM

1.110 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP
_PARAM_HANDOFF_TYPE
Failure Name

ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_HANDOFF
_TYPE

Failure Cause

During FCH setup, the handoff type is incorrect in the CES verification
channel setup command, causing the FCH channel setup failure.

Failure Analysis

The possible causes may be as follows:


l

The CHM version and CCM version do not match.

A CES error occurs.

An upper-layer error occurs.

1-64
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

Chapter 1 Call Failure Causes

Handling Measure

1. Make the CHM version and the CCM version consistent.


2. Soft reset the CHM.
3. If the above measures do not work, reset the CCM.

ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_HANDOFF
_TYPE

CES

CHMCCM

CES

1.

2.

CHM

3.

CCM

1.111 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP
_PARAM_SECTOR_NUM
Failure Name

ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_SECTOR_N
UM

Failure Cause

During FCH setup, the number of sectors is incorrect in the CES verification
channel setup command, causing the FCH channel setup failure.

Failure Analysis

Handling Measure

The possible causes may be as follows:


l

The CHM version and CCM version do not match.

A CES error occurs.

An upper-layer error occurs.

1. Make the CHM version and the CCM version consistent.


2. Soft reset the CHM.
3. If the above measures do not work, reset the CCM.

ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_SECTOR_N
UM

CES

1-65
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

ZXC10 BSSB Failure Cause Reference(1X)

CHMCCM

CES

1.

2.

CHM

3.

CCM

1.112 ERR_CES_RLSA_CEC_CALLHNDL_FCH_SETUP
_PARAM_FWD_RC
Failure Name

ERR_CES_RLSA_CEC_CALLHNDL_FCH_SETUP_PARAM_FWD_RC

Failure Cause

During FCH setup, the forward channel RC type is incorrect in the CES
verification channel setup command, causing the FCH setup failure.

Failure Analysis

Handling Measure

The possible causes may be as follows:


l

The CHM version and CCM version do not match.

A CES error occurs.

An upper-layer error occurs.

1. Make the CHM version and the CCM version consistent.


2. Soft reset the CHM.
3. If the above measures do not work, reset the CCM.

ERR_CES_RLSA_CEC_CALLHNDL_FCH_SETUP_PARAM_FWD_RC

CESRC

CHMCCM

CES

1.

2.

CHM

3.

CCM

1.113 ERR_CES_RLSA_CEC_CALLHNDL_FCH_SETUP
_PARAM_REV_RC
Failure Name

ERR_CES_RLSA_CEC_CALLHNDL_FCH_SETUP_PARAM_REV_RC
1-66

SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

Chapter 1 Call Failure Causes

Failure Cause

During FCH setup, the reverse channel RC type is incorrect in the CES
verification channel setup command, causing the FCH setup failure.

Failure Analysis

The possible causes may be as follows:


l

Handling Measure

The CHM version and CCM version do not match.

A CES error occurs.

An upper-layer error occurs.

1. Make the CHM version and the CCM version consistent.


2. Soft reset the CHM.
3. If the above measures do not work, reset the CCM.

ERR_CES_RLSA_CEC_CALLHNDL_FCH_SETUP_PARAM_REV_RC

CESRC

CHMCCM

CES

1.

2.

CHM

3.

CCM

1.114 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETU
P_PARAM_SECTOR_ID
Failure Name

ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_SECTOR_ID

Failure Cause

During FCH setup, the sector ID is incorrect in the CES verification channel
setup command, causing the FCH channel setup failure.

Failure Analysis

Handling Measure

The possible causes may be as follows:


l

The CHM version and CCM version do not match.

A CES error occurs.

An upper-layer error occurs.

1. Make the CHM version and the CCM version consistent.


2. Soft reset the CHM.
3. If the above measures do not work, reset the CCM.

ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_SECTOR_ID

CESID

1-67

SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

ZXC10 BSSB Failure Cause Reference(1X)

CHMCCM

CES

1.

2.

CHM

3.

CCM

1.115 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP
_PARAM_SECTOR_ISNOT_ACTIVE
Failure Name

ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_SECTOR_I
SNOT_ACTIVE

Failure Cause

During FCH setup, the sector is not activated in the CES verification channel
setup command, causing the FCH channel setup failure.

Failure Analysis

Handling Measure

The possible causes may be as follows:


l

The CHM version and CCM version do not match.

A CES error occurs.

An upper-layer error occurs.

1. Make the CHM version and the CCM version consistent.


2. Soft reset the CHM.
3. If the above measures do not work, reset the CCM.

ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_SECTOR_I
SNOT_ACTIVE

CES

CHMCCM

CES

1.

2.

CHM

3.

CCM

1-68
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

Chapter 1 Call Failure Causes

1.116 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP
_PARAM_EARLIESTPNOFFSET
Failure Name

ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_EARLIEST
PNOFFSET

Failure Cause

During FCH setup, EPN is incorrect in the CES verification channel setup
command, causing the FCH channel setup failure.

Failure Analysis

Handling Measure

The possible causes may be as follows:


l

The CHM version and CCM version do not match.

A CES error occurs.

An upper-layer error occurs.

1. Make the CHM version and the CCM version consistent.


2. Soft reset the CHM.
3. If the above measures do not work, reset the CCM.

ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_EARLIEST
PNOFFSET

CESEPN

CHMCCM

CES

1.

2.

CHM

3.

CCM

1.117 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP
_PARAM_WALSH_INDEX
Failure Name

ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_WALSH_
INDEX

Failure Cause

During FCH setup, the WALSH code is incorrect in the CES verification
channel setup command, causing the FCH channel setup failure.

Failure Analysis

The possible causes may be as follows:


l

The CHM version and CCM version do not match.

A CES error occurs.

An upper-layer error occurs.

1-69
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

ZXC10 BSSB Failure Cause Reference(1X)

Handling Measure

1. Make the CHM version and the CCM version consistent.


2. Soft reset the CHM.
3. If the above measures do not work, reset the CCM.

ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_WALSH_
INDEX

CESWalsh

CHMCCM

CES

1.

2.

CHM

3.

CCM

1.118 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SET
UP_PARAM_CE_INDEX
Failure Name

ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_CE_INDEX

Failure Cause

During FCH setup, CEIndex is incorrect in the CES verification channel


setup command, causing the FCH channel setup failure.

Failure Analysis

Handling Measure

The possible causes may be as follows:


l

The CHM version and CCM version do not match.

A CES error occurs.

An upper-layer error occurs.

1. Make the CHM version and the CCM version consistent.


2. Soft reset the CHM.
3. If the above measures do not work, reset the CCM.

ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_CE_INDEX

CESCEIndex

CHMCCM

CES

1-70
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

Chapter 1 Call Failure Causes

1.

2.

CHM

3.

CCM

1.119 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP
_PARAM_FRAME_OFFSET
Failure Name

ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_FRAME_O
FFSET

Failure Cause

During FCH setup, the frame offset is incorrect in the CES verification
channel setup command, causing the FCH channel setup failure.

Failure Analysis

Handling Measure

The possible causes may be as follows:


l

The CHM version and CCM version do not match.

A CES error occurs.

An upper-layer error occurs.

1. Make the CHM version and the CCM version consistent.


2. Soft reset the CHM.
3. If the above measures do not work, reset the CCM.

ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_FRAME_O
FFSET

CES

CHMCCM

CES

1.

2.

CHM

3.

CCM

1.120 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP
_PARAM_CHANNEL_POWER
Failure Name

ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_CHANNE
L_POWER

1-71
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

ZXC10 BSSB Failure Cause Reference(1X)

Failure Cause

During FCH setup, channel power is incorrect in the CES verification


channel setup command, causing the FCH channel setup failure.

Failure Analysis

The possible causes may be as follows:


l

Handling Measure

The CHM version and CCM version do not match.

A CES error occurs.

An upper-layer error occurs.

1. Make the CHM version and the CCM version consistent.


2. Soft reset the CHM.
3. If the above measures do not work, reset the CCM.

ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_CHANNE
L_POWER

CES

CHMCCM

CES

1.

2.

CHM

3.

CCM

1.121 ERR_CES_RLSA_CEC_CALLHNDL_FCH_SETUP
_PARAM_REV_FCH_GATING
Failure Name

ERR_CES_RLSA_CEC_CALLHNDL_FCH_SETUP_PARAM_REV_FC
H_GATING

Failure Cause

During FCH setup, the reverse FCH gating mode is incorrect in the CES
verification channel setup command, causing the FCH setup failure.

Failure Analysis

Handling Measure

The possible causes may be as follows:


l

The CHM version and CCM version do not match.

A CES error occurs.

An upper-layer error occurs.

1. Make the CHM version and the CCM version consistent.


2. Soft reset the CHM.
3. If the above measures do not work, reset the CCM.

1-72
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

Chapter 1 Call Failure Causes

ERR_CES_RLSA_CEC_CALLHNDL_FCH_SETUP_PARAM_REV_FC
H_GATING

CESFCH

CHMCCM

CES

1.

2.

CHM

3.

CCM

1.122 ERR_CES_RLSA_CEC_CALLHNDL_DCCH_SET
UP_PARAM_REV_PILOT_GATING
Failure Name

ERR_CES_RLSA_CEC_CALLHNDL_DCCH_SETUP_PARAM_REV_P
ILOT_GATING

Failure Cause

During FCH setup, the reverse pilot channel gating mode is incorrect in the
CES verification channel setup command, causing the FCH setup failure.

Failure Analysis

The possible causes may be as follows:


l

Handling Measure

The CHM version and CCM version do not match.

A CES error occurs.

An upper-layer error occurs.

1. Make the CHM version and the CCM version consistent.


2. Soft reset the CHM.
3. If the above measures do not work, reset the CCM.

ERR_CES_RLSA_CEC_CALLHNDL_DCCH_SETUP_PARAM_REV_P
ILOT_GATING

CES

CHMCCM

CES

1.

2.

CHM

3.

CCM

1-73
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

ZXC10 BSSB Failure Cause Reference(1X)

1.123 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP
_PARAM_FPC_PUNC_MODE
Failure Name

ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_FPC_PU
NC_MODE

Failure Cause

During basic channel setup, the forward power control mode is incorrect in
the CES verification channel setup command, causing the failure in setting
up the basic channel.

Failure Analysis

Handling Measure

The CHM version and CCM version do not match.

A CES error occurs.

An upper-layer error occurs.

1. Make the CHM version and the CCM version consistent.


2. Soft reset the CHM.
3. If the above measures do not work, reset the CCM.

ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_FPC_PU
NC_MODE

CES

CHMCCM

CES

1.

2.

CHM

3.

CCM

1.124 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SET
UP_PARAM_FPC_GAIN
Failure Name
Failure Cause

ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_FPC_GAIN
During basic channel setup, the forward power control gain is incorrect in
the CES verification channel setup command, causing the failure in setting
up the basic channel.

Failure Analysis

The possible causes may be as follows:


l

The CHM version and CCM version do not match.

A CES error occurs.

An upper-layer error occurs.

1-74
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

Chapter 1 Call Failure Causes

Handling Measure

1. Make the CHM version and the CCM version consistent.


2. Soft reset the CHM.
3. If the above measures do not work, reset the CCM.

ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_FPC_GAIN

CES

CHMCCM

CES

1.

2.

CHM

3.

CCM

1.125 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP
_PARAM_FPC_STEP_SIZE
Failure Name

ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_FPC_STE
P_SIZE

Failure Cause

During basic channel setup, the forward power control setp is incorrect in
the CES verification channel setup command, causing the failure in setting
up the basic channel.

Failure Analysis

Handling Measure

The possible causes may be as follows:


l

The CHM version and CCM version do not match.

A CES error occurs.

An upper-layer error occurs.

1. Make the CHM version and the CCM version consistent.


2. Soft reset the CHM.
3. If the above measures do not work, reset the CCM.

ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_FPC_STE
P_SIZE

CES

1-75
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

ZXC10 BSSB Failure Cause Reference(1X)

CHMCCM

CES

1.

2.

CHM

3.

CCM

1.126 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP
_PARAM_RPC_PUNC_MODE
Failure Name

ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_RPC_PU
NC_MODE

Failure Cause

During basic channel setup, the reverse power control mode is incorrect in
the CES verification channel setup command, causing the failure in setting
up the basic channel.

Failure Analysis

Handling Measure

The possible causes may be as follows:


l

The CHM version and CCM version do not match.

A CES error occurs.

An upper-layer error occurs.

1. Make the CHM version and the CCM version consistent.


2. Soft reset the CHM.
3. If the above measures do not work, reset the CCM.

ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_RPC_PU
NC_MODE

CES

CHMCCM

CES

1.

2.

CHM

3.

CCM

1-76
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

Chapter 1 Call Failure Causes

1.127 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETU
P_PARAM_REV_PC_SETPOINT
Failure Name

ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_REV_PC_
SETPOINT

Failure Cause

During basic channel setup, the reverse out loop setting values are incorrect
in the CES verification channel setup command, causing the failure in
setting up the basic channel.

Failure Analysis

Handling Measure

The possible causes may be as follows:


l

The CHM version and CCM version do not match.

A CES error occurs.

An upper-layer error occurs.

1. Make the CHM version and the CCM version consistent.


2. Soft reset the CHM.
3. If the above measures do not work, reset the CCM.

ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_REV_PC_
SETPOINT

CES
(SetPoint)

CHMCCM

CES

1.

2.

CHM

3.

CCM

1.128 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP
_PARAM_REV_PC_PATTERN
Failure Name

ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_REV_PC
_PATTERN

Failure Cause

During basic channel setup, the reverse power control mode is incorrect in
the CES verification channel setup command, causing the failure in setting
up the basic channel.

1-77
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

ZXC10 BSSB Failure Cause Reference(1X)

Failure Analysis

Handling Measure

The possible causes may be as follows:


l

The CHM version and CCM version do not match.

A CES error occurs.

An upper-layer error occurs.

1. Make the CHM version and the CCM version consistent.


2. Soft reset the CHM.
3. If the above measures do not work, reset the CCM.

ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_REV_PC
_PATTERN

CES

CHMCCM

CES

1.

2.

CHM

3.

CCM

1.129 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP
_PARAM_TRAFFIC_FRAME_TYPE
Failure Name

ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_TRAFFIC_
FRAME_TYPE

Failure Cause

During FCH setup, the frame type is incorrect in the CES verification
channel setup command, causing the FCH channel setup failure.

Failure Analysis

Handling Measure

The possible causes may be as follows:


l

The CHM version and CCM version do not match.

A CES error occurs.

An upper-layer error occurs.

1. Make the CHM version and the CCM version consistent.


2. Implement soft reset for the CHM.
3. If the above measures do not work, reset the CCM.

1-78
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

Chapter 1 Call Failure Causes

ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_PARAM_TRAFFIC_
FRAME_TYPE

CES

CHMCCM

CES

1.

2.

CHM

3.

CCM

1.130 CEMERROR_CALLHNDL_TCH_SETUP_PARAM_
DEST_IP_ADRR_INVALID
Failure Name

CEMERROR_CALLHNDL_TCH_SETUP_PARAM_DEST_IP_ADRR_INVA
LID

Failure Cause

During FCH setup, the destination IP address carried in the CES channel
setup verification command is incorrect, causing the FCH setup failure.

Failure Analysis

The possible failure causes are as follows:


l

Handling Measure

The CHM version and CCH version do not match.

A CES error occurs.

An upper-layer error occurs.

1. Make the CHM version and CCM version consistent.


2. Implement soft reset for the CHM.
3. If the above measures do not work, reset the CCM.

CEMERROR_CALLHNDL_TCH_SETUP_PARAM_DEST_IP_ADRR_INVA
LID

CESIP

CHMCCM

CES

1.

2.

CHM

3.

CCM

1-79
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

ZXC10 BSSB Failure Cause Reference(1X)

1.131 CEMERROR_CALLHNDL_TCH_SETUP_PARAM
_DSCP_PRIIS_INVALID
Failure Name

CEMERROR_CALLHNDL_TCH_SETUP_PARAM_DSCP_PRIIS_INVALID

Failure Cause

During FCH setup, the DSCP priority carried in the CES channel setup
verification command is incorrect, causing the FCH setup failure.

Failure Analysis

The possible failure causes are as follows:


l

Handling Measure

The CHM version and CCH version do not match.

A CES error occurs.

An upper-layer error occurs.

1. Make the CHM version and CCH version consistent.


2. Implement soft reset for the CHM.
3. If the above measures do not work, reset the CCM.

CEMERROR_CALLHNDL_TCH_SETUP_PARAM_DSCP_PRIIS_INVALID
CESDSCP

CHMCCM

CES

1.

2.

CHM

3.

CCM

1.132 ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP
_CEMCTRL_NULL
Failure Name

ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_CEMCTRL_NULL

Failure Cause

During FCH setup, the pointer to the class CEMCTRL object fails to be
obtained, causing the FCH setup failure.

Failure Analysis

There is a problem with the CES code.

Handling Measure

1. Implement soft reset for the CHM.


2. If the above measure does not work, reset the CHM.

ERR_CES_RLSA_CEC_CALLHNDL_TCH_SETUP_CEMCTRL_NULL

1-80
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

Chapter 1 Call Failure Causes

CEMCTRL

CES

1.

CHM

2.

CHM

1.133 ERR_SPS_RLSA_BSSAP_SccpDisconnect_Con
nectref_Incompat_Inf_In_NSDUs
Failure Name

ERR_SPS_RLSA_BSSAP_SccpDisconnect_Connectref_Incompat_Inf_In_
NSDUs

Failure Cause

SCCPDISConnect occurs, with the cause Disconnect_Access_congestion(1A).

Failure Analysis

The cause of SCCPDISConnect is Disconnect_Access_congestion(1A).

Handling Measure

On the MSC, trace the SCCP signaling of the user and check the specific
failure cause. The cause is usually an authentication failure, which is
resulted from illegal users.

1.134 ERR_SPS_RLSA_BSSAP_SccpDisconnect_End
_User_Failure
Failure Name

ERR_SPS_RLSA_BSSAP_SccpDisconnect_End_User_Failure

Failure Cause

SCCPDISConnect occurs, with the cause Disconnect_Normal_condition(13). The SCCPDISConnect is caused by a user.

Failure Analysis

During registration, the SCCP link is released by the MSC. This is usually
caused by a user that is not provisioned or by an illegal user.

Handling Measure

On the MSC, trace the SCCP signaling of the user to find the specific
failure cause.

1-81
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

ZXC10 BSSB Failure Cause Reference(1X)

1.135 ERR_SPS_RLSA_BSSAP_TgtBSC_FunCallFail_
FCHAndDCCH_AbisdrConnectProccess_AbisdrCo
nnectMsgProccess
Failure Name

ERR_SPS_RLSA_BSSAP_TgtBSC_FunCallFail_FCHAndDCCH_Abisdr
ConnectProccess_AbisdrConnectMsgProccess

Failure Cause

The target of the inter-BSC soft handoff receives the AbisdrConnect


message processing error.

Failure Analysis

After the AbisdrConnect message is received, abnormalities occur. For


example, the creation of corresponding cells is stopped (if the A7fDropTarget
message is received following the A7HandoffRequest message), or leg
allocation fails.

Handling Measure

If only a few such faults occur, this is normal, and no handling measure
needs to be taken.

1.136 ERR_SPS_RLSA_BSSAP_TgtBSC_Other_CheckI
fCellFitToSetup_HOReqCellIsExisted
Failure Name

ERR_SPS_RLSA_BSSAP_TgtBSC_Other_CheckIfCellFitToSetup_HOR
eqCellIsExisted

Failure Cause

The cell requested by the target of the inter-BSC soft handoff already exists.

Failure Analysis

The release flow of the target is not completed owing to such cause as link
delay, while the source initiates the next handoff request.

Handling Measure

If only a few such faults occur, this is normal, and no handling measure
needs to be taken. If a large number of such faults occur, obtain the
abnormal probe and contact ZTE Corporation for analysis.

1.137 ERR_SPS_RLSA_BSSAP_TgtBSC_Other_ReqRe
leaseingCellIsNotExisted
Failure Name

ERR_SPS_RLSA_BSSAP_TgtBSC_Other_ReqReleaseingCellIsNotExi
sted

Failure Cause

The cell that the target wants to release in the inter-BSC soft handoff does
not exist.

1-82
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

Chapter 1 Call Failure Causes

Failure Analysis

Owing to an internal cause of the target or a cause of the BTS, the cell has
already been released, but the source still requests to release the cell; or
the release message of the source carries an incorrect cell.

Handling Measure

If only a few such faults occur, this is normal, and no handling measure
needs to be taken. If a large number of such faults occur, obtain the
abnormal probe and contact ZTE Corporation for analysis.

1.138 ERR_SPS_RLSA_BSSAP_PTTSetup_ServiceNot
ify_UserInHigherPriorityService
Failure Name

ERR_SPS_RLSA_BSSAP_PTTSetup_ServiceNotify_UserInHigherPriority
Service

Failure Cause

A request of the PTT traditional group call is received, and the current call is
preempted.

Failure Analysis

The preemption request of a PTT traditional group call is received.

Handling Measure

It is a normal case. On the PHR, you can set not allow voice to be
preempted.

1.139 ERR_SPS_RLSA_BSSAP_PTTSetup_A9dfPTTPa
ge_UserInHigherPriority
Failure Name

ERR_SPS_RLSA_BSSAP_PTTSetup_A9dfPTTPage_UserInHigherPriority

Failure Cause

A PTT call request is received, and the current call is preempted by the
PTT call.

Failure Analysis

A PTT call preemption request is received.

Handling Measure

It is a normal case. On the PHR, you can set not allow voice to be
preempted.

1-83
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

ZXC10 BSSB Failure Cause Reference(1X)

This page intentionally left blank.

1-84
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

Chapter 2

Call Drop Causes


2.1 ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvOrgnIn
SessionState
Failure Name

ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvOrgnInSessionState

Failure Cause

In call status, a call origination message is received.

Failure Analysis

The possible failure cause is as follows: When the user originates a call and
the process does not release the message, the call fails.

Handling Measure

It is acceptable if the problem occurs occasionally, otherwise, further


analysis is needed.

ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvOrgnInSessionState

2.2 ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvRegInSe
ssionState_Others
Failure Name

ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvRegInAssignState_Others

Failure Cause

During a call, a registration message is received, such as timing register.

Failure Analysis

During a call, other registration messages are received, besides power


on and off registration messages.

Handling Measure

If the problem occurs occasionally, it is normal. If the problems occurs


frequently, check the fault probe and take measures after identifying the
cause.

ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvRegInAssignState_Others

2-1

SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

ZXC10 BSSB Failure Cause Reference(1X)

2.3 ERR_SPS_RLSA_BSSAP_HandShake_TimeOut
Failure Name

ERR_SPS_RLSA_BSSAP_HandShake_TimeOut

Failure Cause

Handshake times out between BSSAP and DSPM.

Failure Analysis

After entering the session state, timer times out while waiting for DSPM
handshaking message.

Possible Solution

1. Check the terminal call state.


2. Verify that the MP board is normal at BSC front-end.
3. Verify that the timeout duration is normal.
4. Verify that the DSPM module operates properly.

ERR_SPS_RLSA_BSSAP_HandShake_TimeOut

BSSAPDSPM

DSPM

1.

2.

BSCMP

3.

4.

DSPM

2.4 ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvRegIn
AssignState_PowerOn
Failure Name

ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvRegInAssignState_PowerOn

Failure Cause

Power-on registration message is received during a call.

Failure Analysis

The battery is removed during a call, and the MS is powered on and


registers before the process is released.
Battery runs out during a call, and the MS is powered on and registers
before the process is released.

Handling Measure

It is acceptable if the problem occurs occasionally. If the problem occurs


frequently, check the fault probe and take measures after identifying the
cause.

ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvRegInAssignState_PowerOn
2-2

SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

Chapter 2 Call Drop Causes

2.5 ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvRegInAs
signState_PowerDown
Failure Name

ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvRegInAssignState_PowerD
own

Failure Cause

Power-off registration message is received during a call.

Failure Analysis

The user originates a Power OFF while the process does not release
and the call fails.

The user on a call presses the power off button and this is the user
personal action.

Handling Measure

Depending on the terminal processing flow.

ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvRegInAssignState_PowerD
own

2.6 ERR_SPS_RLSA_BSSAP_UnexptMsg_UmaRegistr
ation
Failure Name

ERR_SPS_RLSA_BSSAP_UnexptMsg_UmaRegistration

Failure Cause

A UmaRegistration message is received during the call.

Failure Analysis

Some MSs receive the registration message when making calls.

Handling Measure

If the exception rarely occurs, it is unnecessary to handle. If it occurs


frequently, contact the local representative office of ZTE Corporation.

2-3
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

ZXC10 BSSB Failure Cause Reference(1X)

2.7 ERR_SPS_RLSA_DSPM_HOH_OtherReason_Abisd
HandShakeFailure
Failure Name

ERR_SPS_RLSA_DSPM_HOH_OtherReason_AbisdHandShakeFailure

Failure Cause

During a call, the handshake failure between DSPM and RCM originates
call release.

Failure Analysis

Possible Solution

The RCM and ABPM relevant to the BTS are operating improperly.

The setting for timer Tphysical on the DSMP board is wrong.

1. Verify that the setting for timer Tphysical on the DSMP board is correct
(default 2 minutes).
2. Verify that the RCM and ABPM relevant to the BTS are operating
normally and no abnormal reset or changeover occurs.
3. Verify that the versions of CCM and ABPM boards are correct and
operating properly.

ERR_SPS_RLSA_DSPM_HOH_OtherReason_AbisdHandShakeFailure

DSPMRCM

BTSRCMABPM

DSMPTphysical

1. DSMPTphysical2
2.

BTSRCMABPM

3.

CCMABPM

2.8 ERR_SPS_RLSA_DSPM_CLH_OtherReason_PCF
EquipmentFailure
Failure Name

ERR_SPS_RLSA_DSPM_CLH_OtherReason_PCFEquipmentFailure

Failure Cause

Abnormal call release initiated by PCF.

Failure Analysis

Corresponding PCF runs abnormally.

A10 link establishment fails.

Possible Solution

1. Verify that the IMSI, HI and DI carried by A9SetupA8 message are


correct.
2. Check if A10 link establishment failed when the handoff failed.
3. Check the version and operation of the PCF board.

2-4
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

Chapter 2 Call Drop Causes

ERR_SPS_RLSA_DSPM_CLH_OtherReason_PCFEquipmentFailure

PCF

PCF

A10

1.

A9SetupA8IMSIHIDI

2.

A10

3.

PCF

2.9 ERR_SPS_RLSA_DSPM_CLH_OtherReason_Than
dshakerecv
Failure Name

ERR_SPS_RLSA_DSPM_CLH_OtherReason_Thandshakerecv

Failure Cause

During a call, there is a handshake between the DSPM, SDU and BSSAP.
When there is no reply message, timer Trecv expires and the SPS releases
the call.

Failure Analysis

The DSPM does not receive a reply message from the SDM when it
sends two handshake messages to the SDM in 5 minutes.

The DSPM does not receive a reply message from the BSSAP when it
sends two handshake messages to the SDM in 5 minutes.

Possible Solution

1. Verify that the setting of the Trecv timer (default value is 5 minutes) on
the DSMP board is correct.
2. Check the corresponding CMP when the problem occurs. Verify that the
SDU operates properly and there is no abnormal reset or switchover.

ERR_SPS_RLSA_DSPM_CLH_OtherReason_Thandshakerecv

DSPMSDUBSSAPTrecv

DSPM5SDM2SDM

DSPM5SDM2BSSAP

1. DSMPTrecv5
2.

CMPSDU

2-5
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

ZXC10 BSSB Failure Cause Reference(1X)

2.10 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_S
CHHReleaseRSCHbyLegFail_ReleaseRschExistS
DMLegFailure
Failure Name

ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHReleaseRSCHbyLe
gFail_ReleaseRschExistSDMLegFailure

Failure Cause

The DSPM receives the LegLinkFailure report from SDM. If RSCH is not
partly soft handoff and the released cell, then the SDM notify different cells.
The failure is reported by DSPM.

Failure Analysis

The possible failure cause is as follows: SDM has no reverse frames.

Handling Measure

Check Abis interface.

ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHReleaseRSCHbyLe
gFail_ReleaseRschExistSDMLegFailure

DSPMSDMLegLinkFailureRSCH
SDMDSPM

SDM

Abis

2.11 SDM_Link_Fail_RevNoFrm
Failure Name

SDM_Link_Fail_RevNoFrm

Failure Analysis

Link failure. The SDM cannot receive traffic frames sent from the BTS
during a period (default time is 18 s).
Reasons for this failure vary, for example, Abis link problem and CHM
dispatching problem, which are subject to different situations.
The call is released when the failure is reported.

Possible Solution

Verify that the Abis link is not broken.

SDM_Link_Fail_RevNoFrm

SDM18 sBTS

AbistCHM

Abis

2-6
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

Chapter 2 Call Drop Causes

2.12 SDM_Link_Fail_RevTooManyBadFrm
Failure Name

SDM_Link_Fail_RevTooManyBadFrm

Failure Analysis

Link failure. The SDM receives almost all error frames from the BTS side
during receiving period (default time is 18 s).
The reasons for this failure may vary. The reason may be characterized as
normal or abnormal reasons depending upon the actual situation.
For example:
l

If the reverse radio link is very bad, the problem will be reported. This
is a normal release.

During a calling process, MS releases itself spontaneously for some


reason, while BS does not receive release message of the mobile.
After a while, an error is reported. This is a kind of abnormal release.

Inconsistent parameters setting between the MS and BS side and PN


offset error will cause this failure. This is another kind of abnormal
release.

Possible Solution

1. Check MS and BS side parameters (PN offset, version).


2. If all the parameters are consistent, MS releases itself spontaneously
and this release is a normal release.

SDM_Link_Fail_RevTooManyBadFrm
SDMBTS
18 s

BS

BSPN

1.

MSBSPN

2.

MS

2.13 SDM_Link_Fail_FwdA2pNoFrm
Failure Name

SDM_Link_Fail_FwdA2pNoFrm

Failure Cause

SDM cannot receive traffic frame sent from MGW during a period (default
time is 18 s).

2-7
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

ZXC10 BSSB Failure Cause Reference(1X)

Failure Analysis

Reasons for this fault vary, for example, net cable on Ap port has a problem,
MGW process problem (not sending frame), which is subject to actual
situation. While submitting this fault, calling will be released.

Handling Measure

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_Link_Fail_FwdA2pNoFrm

SDMMGW18 s
ApMGW

ApBSCMGW
MGW

2.14 SDM_Link_Fail_FwdA2pTooManyErrEncodeFrm
Failure Name

SDM_Link_Fail_FwdA2pTooManyErrEncodeFrm

Failure Cause

Frames without errors received from Media Gateway (MGW) within 18 s


are not sufficient.

Failure Analysis

1. Problem occur during MGW frame sending, i.e. not send frame to SDM.
2. Problem occurs in Ap port link during call; the possibility is relatively
small.
3. SDM process error.

Handling Measure

1. Verify that the Ap port link is normal.


2. If it is not disconnected link, it is normal situation; please contact
engineers at the office.

SDM_Link_Fail_FwdA2pTooManyErrEncodeFrm

18 sSDMMGW

MGWSDM

Ap

SDM

1.

Ap

2.

2-8
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

Chapter 2 Call Drop Causes

2.15 ERR_SPS_RLSA_RCM_PMAIN_FunCallFail_Main
Entry_GetCallProc
Failure Name

ERR_SPS_RLSA_RCM_PMAIN_FunCallFail_MainEntry_GetCallProc

Failure Analysis

During supplementary channel setup handling, searching for the handling


process fails. The cause may be that the call has been released or the call
reference number in the BurstRequest is incorrect.

Handling Measure

If the a few such problems occur, ignore them. If a lot of such problems
occur, contact the local office of ZTE Corporation.

ERR_SPS_RLSA_RCM_PMAIN_FunCallFail_MainEntry_GetCallProc

BurstRequest

2.16 ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvOrgnI
nHardHOAdd
Failure Name
Failure Cause

ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvOrgnInHardHOAdd
During the hard handoff process, a call originating message is received
from the terminal.

Failure Analysis

Before the process is released, another call originating message is received


from the terminal. If the battery of the terminal is removed and then
re-installed, and the terminal initiates a call again, the fault occurs.

Handling Measure

Such faults seldom occur, and therefore no handling measure is required.

2.17 ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvPage
RspInHardHOAdd
Failure Name

ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvPageRspInHardHOAdd

Failure Cause

During the hard handoff process, a paging response message is received


from the terminal.

2-9
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

ZXC10 BSSB Failure Cause Reference(1X)

Failure Analysis

Before the process is released, another paging response message is


received from the terminal. If the battery of the terminal is removed and
then re-installed, and the terminal becomes the called party again, the fault
occurs.

Handling Measure

Such faults seldom occur, and therefore no handling measure is required.

2-10
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

Chapter 3

Call Release Causes


3.1 ERR_SPS_RLSA_DSPM_CLH_OtherReason_MSN
ormalRelease
Failure Name

ERR_SPS_RLSA_DSPM_CLH_OtherReason_MSNormalRelease

Failure Cause

Normal call release is automatically initiated by a mobile station.

Failure Analysis

Normal release.

Handling Measure

Normal release.

ERR_SPS_RLSA_DSPM_CLH_OtherReason_MSNormalRelease

3.2 ERR_SPS_RLSA_DSPM_CLH_OtherReason_MSP
owerDown
Failure Name

ERR_SPS_RLSA_DSPM_CLH_OtherReason_MSPowerDown

Failure Cause

Call release is initiated by mobile station power-off.

Failure Analysis

Normal release.

Handling Measure

Normal release.

ERR_SPS_RLSA_DSPM_CLH_OtherReason_MSPowerDown

3-1
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

ZXC10 BSSB Failure Cause Reference(1X)

3.3 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCH
HOnUmrSCHRequestMsg_ReleasebyMSDTXTime
Failure Name

ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnUmrSCHReq
uestMsg_ReleasebyMSDTXTime

Failure Cause

RSCH DTXTime release is initiated by mobile station.

Failure Analysis

Normal release.

Handling Measure

Normal release.

ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnUmrSCHReques
tMsg_ReleasebyMSDTXTime

RSCHDTXTime

3.4 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCH
HOnAbarSCHRemoveIndication_RSCHReleaseby
SDMOtherReason
Failure Name

ERR_SPS_RLSA_DSPM_SCHH_OtherReason _SCHHOnAbarSCHRemo
veIndication_RSCHReleasebySDMDTXTime

Failure Cause

RSCH DTXTime release initiated by SDM.

Failure Analysis

Normal release.

Handling Measure

Normal release.

ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnAbarSCHRemov
eIndication_RSCHReleasebySDMOtherReason

SDMRSCH

3-2
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

Chapter 3 Call Release Causes

3.5 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCH
HPNDropIndication_ReleasebyHOH
Failure Name

ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHPNDropIndication_
ReleasebyHOH

Failure Cause

SCH release triggered by soft handoff on the fundamental channel.

Failure Analysis

Normal release.

Handling Measure

Normal release.

ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHPNDropIndication_
ReleasebyHOH

SCH

3.6 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SC
HHOnAbisdrBurstRelease_RSCHExistedCellRele
asebyRCM
Failure Name

ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnAbisdrBurstRele
ase_RSCHExistedCellReleasebyRCM

Failure Cause

RSCH release initiated at BTS side.

Failure Analysis

Normal release.

Handling Measure

Normal release.

ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnAbisdrBurstRele
ase_RSCHExistedCellReleasebyRCM

BTSRSCH

3-3
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

ZXC10 BSSB Failure Cause Reference(1X)

3.7 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCH
HRelease_ReleasebyCLH
Failure Name

ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHRelease_Release
byCLH

Failure Cause

SCH release triggered by call release.

Failure Analysis

Normal release.

Handling Measure

Normal release.

ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHRelease_Releaseb
yCLH

SCH

3.8 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCH
HOnAbarSCHRemoveIndication_RSCHReleaseby
SDMOtherReason
Failure Name

ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnAbarSCHRemov
eIndication_ RSCHReleasebySDMOtherReason

Failure Cause

SDM initiates RSCH other causes release.

Failure Analysis

Normal release.

Handling Measure

Normal release.

ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnAbarSCHRemov
eIndication_ RSCHReleasebySDMOtherReason

SDMRSCH

3-4
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

Chapter 3 Call Release Causes

3.9 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCH
HOnAbarSCHRemoveIndication_FSCHReleaseby
SDMDuration
Failure Name

ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnAbarSCHRemov
eIndication_FSCHReleasebySDMDuration

Failure Cause

When the SCH dispatch timer is timeout, SDM initiates FSCH release.

Failure Analysis

Normal release.

Handling Measure

Normal release.

ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnAbarSCHRemov
eIndication_FSCHReleasebySDMDuration

SCHSDMFSCH

3.10 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_S
CHHFSCHHandoff_HardHandoff
Failure Name

ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHFSCHHandoff_H
ardHandoff

Failure Cause

SCH forward judges that a hard HO is to be done, hence there is a SCH


release.

Failure Analysis

Normal release.

Handling Measure

Normal release.

ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHFSCHHandoff_Har
dHandoff

SCHSCH

3-5
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

ZXC10 BSSB Failure Cause Reference(1X)

3.11 ERR_SPS_RLSA_DSPM_SCHH_TimerExpired_Tf
schdrop
Failure Name

ERR_SPS_RLSA_DSPM_SCHH_TimerExpired_Tfschdrop

Failure Cause

Release caused by FSCH due to timeout.

Failure Analysis

Normal release.

Handling Measure

Normal release.

ERR_SPS_RLSA_DSPM_SCHH_TimerExpired_Tfschdrop

FSCH

3.12 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SC
HHOnTfschdroppending_ReleasebyTDropPending
Failure Name

ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnTfschdroppendin
g_ReleasebyTDropPending

Failure Cause

Release caused by FSCH due to timeout.

Failure Analysis

Normal release.

Handling Measure

Normal release.

ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnTfschdroppendin
g_ReleasebyTDropPending

FSCH

3-6
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

Chapter 3 Call Release Causes

3.13 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_S
CHHOnAbisdrBurstRelease_FSCHExistedCellRele
asebyRCM
Failure Name

ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnAbisdrBurstRele
ase_FSCHExistedCellReleasebyRCM

Failure Cause

FSCH release initiated at BTS side.

Failure Analysis

Normal release.

Handling Measure

Normal release.

ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnAbisdrBurstRele
ase_FSCHExistedCellReleasebyRCM

BTSFSCH

3.14 ERR_SPS_RLSA_DSPM_CLH_OtherReason_MS
GoingIntoDormant
Failure Name

ERR_SPS_RLSA_DSPM_CLH_OtherReason_MSGoingIntoDormant

Failure Cause

In data service, the call release is autonomously initiated by a mobile station.

Failure Analysis

Normal release.

Handling Measure

Normal release.

ERR_SPS_RLSA_DSPM_CLH_OtherReason_MSGoingIntoDormant

3.15 ERR_SPS_RLSA_DSPM_CLH_OtherReason_PCF
NormalRelease
Failure Name

ERR_SPS_RLSA_DSPM_CLH_OtherReason_PCFNormalRelease
3-7

SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

ZXC10 BSSB Failure Cause Reference(1X)

Failure Cause

In data service, the normal call release initiated by PCF.

Failure Analysis

Normal release.

Handling Measure

Normal release.

ERR_SPS_RLSA_DSPM_CLH_OtherReason_PCFNormalRelease

PCF

3.16 ERR_SPS_RLSA_DSPM_CLH_OtherReason_SDM
LinkFailure_toDormant
Failure Name

ERR_SPS_RLSA_DSPM_CLH_OtherReason_SDMLinkFailure_toDormant

Failure Cause

Data service air interface link fails. During a specific time, SDM receives
error frames or no frames from BTS (the default duration is 18 s) and
releases to the Dormant status.

Failure Analysis

This failure may be caused by a lot of reasons, be it normal or abnormal. If


the fault is reported due to the really poor reverse air link, this situation is of
normal release. But not all the situations are normal, many of which may
be of hidden system problems. For example, in the call process, the MS
releases itself but BS does not receive the MS release information. The fault
will be reported later and it is necessary to check out the reason. Different
parameters set in MS and BS may cause the fault, so will the PN offset error.

Handling Measure

1. Check the parameters in both MS and BS (PN offset and version).


2. If the parameters are identical and MS releases itself, it is normal .
3. Optimize network coverage.

ERR_SPS_RLSA_DSPM_CLH_OtherReason_SDMLinkFailure_toDormant
SDMBTS
18 sDormant

3-8
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

Chapter 3 Call Release Causes

BS

BSPN

1.

MSBSPN

2.

MS

3.

3.17 ERR_SPS_RLSA_DSPM_HOH_FunCallFail_HOHO
nA7rTarRemReq_CLHRlsInd
Failure Name

ERR_SPS_RLSA_DSPM_HOH_FunCallFail_HOHOnA7rTarRemReq_CL
HRlsInd

Failure Cause

During inter-BSC soft handoff, the target BSC detects fault, hence initiating
a soft handoff remove.

Failure Analysis

Handling Measure

The signal is weak, so the target initiates the release.

The A3 link is abnormal, so the target initiates the release.

1. Check the signal strength.


2. If IBBE boards are used for interconnection, verify that the IBBE boards
and the Ethernet cable are well connected.
3. If HGM boards are used for interconnection, verify that the HGM boards
and the E1 cable are properly connected.
4. Verify that the media link on the target side is normal.

ERR_SPS_RLSA_DSPM_HOH_FunCallFail_HOHOnA7rTarRemReq_CL
HRlsInd

BSCBSC
l

A3

3-9
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

ZXC10 BSSB Failure Cause Reference(1X)

1.

2. IBBEIBBE

3. HGMHGME1

4.

3.18 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_S
CHHOnA7rBurstRelease_FSCHExistedCellReleas
ebyRCM
Failure Name

ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnA7rBurstRelease
_FSCHExistedCellReleasebyRCM

Failure Cause

In the case of BSC interconnection, the target side initiates the release of
the forward supplementary channel.

Failure Analysis

The scheduling time expires, so it is a normal release.

Handling Measure

It is a normal case, so no solution is needed.

ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnA7rBurstRelease
_FSCHExistedCellReleasebyRCM

BSC

3.19 ERR_SPS_RLSA_DSPM_SCHH_OtherReason_S
CHHOnA7rBurstRelease_RSCHExistedCellReleas
ebyRCM
Failure Name

ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnA7rBurstRelease
_RSCHExistedCellReleasebyRCM

Failure Cause

In the case of BSC interconnection, the target side initiates the release of
the reverse supplementary channel.

Failure Analysis

The scheduling time expires, so it is a normal release.

Handling Measure

It is a normal case, so no solution is needed.

3-10
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

Chapter 3 Call Release Causes

ERR_SPS_RLSA_DSPM_SCHH_OtherReason_SCHHOnA7rBurstRelease
_RSCHExistedCellReleasebyRCM

BSC

3.20 SDM_Find_Fail_NoFCHLeg
Failure Name

SDM_Find_Fail_NoFCHLeg

Failure Cause

When SDM receives AbafSDMDropLeg message sent by Layer 3, no leg is


found for SDM to remove. Possible reason is message maintained by SDM
is different from that of Level Three.

Handling Measure

Check signaling to find out whether Layer 3 has noticed SDM to add this
leg; if it has, then the problem lies in SDM, if not then it lies in Layer 3.
Find the cause by signaling trace.

SDM_Find_Fail_NoFCHLeg

SDMAbafSDMDropLegSDM
SDM

SDMSDM

3.21 ERR_SPS_RLSA_RCM_RSCH_OtherReason_Rele
ase_RSCH
Failure Name

ERR_SPS_RLSA_RCM_RSCH_OtherReason_Release_RSCH

Failure Cause

Release R-SCH channel: R-SCH channel release notified by database


message.

Handling Measure

Normal status.

ERR_SPS_RLSA_RCM_RSCH_OtherReason_Release_RSCH

3-11
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

ZXC10 BSSB Failure Cause Reference(1X)

3.22 ERR_SPS_RLSA_RCM_RSCH_OtherReason_R
elease_FSCH
Failure Name

ERR_SPS_RLSA_RCM_RSCH_OtherReason_Release_FSCH

Failure Cause

Release forward SCH channel: forward SCH channel release notified by


database message.

Handling Measure

Normal status

ERR_SPS_RLSA_RCM_RSCH_OtherReason_Release_FSCH

3.23 ERR_SPS_RLSA_RCM_SCHCOMM_TimerExpire
d_Tsch
Failure Name

ERR_SPS_RLSA_RCM_SCHCOMM_TimerExpired_Tsch

Failure Cause

During data service procedure, after SCHresource setup, database


configuration timer expires, waiting for the acknowledgement.

Handling Measure

Verify that the voice traffic is not too heavy.

ERR_SPS_RLSA_RCM_SCHCOMM_TimerExpired_Tsch

3.24 ERR_SPS_RLSA_RCM_SCHCOMM_TimerExpir
ed_Tbstcomb
Failure Name

ERR_SPS_RLSA_RCM_SCHCOMM_TimerExpired_Tbstcomb

Failure Cause

During data service, BTS side SCH channel resource allocation is finished,
waiting for BSC side confirm, BSC side confirm message timeout

Failure Analysis

Confirm message lost.

After BTS side allocates SCH channel resource, the parameter in reply
message to BSC side is wrong.

3-12
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

Chapter 3 Call Release Causes

Handling Measure

1. Verify that the Abis link is normal.


2. Verify that 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.

ERR_SPS_RLSA_RCM_SCHCOMM_TimerExpired_Tbstcomb

BTSBSC
BSC

BTSBSC

1.

Abis

2.

BTSBSCAbisdrBurstResponse
AbisdfBurstRequest

3.25 ERR_SPS_RLSA_RCM_RSCH_FunCallFail_Rev
SCHSetupFail
Failure Name

ERR_SPS_RLSA_RCM_RSCH_FunCallFail_RevSCHSetupFail

Failure Cause

During data service, when an SCH channel is being set up, the database
resource is allocated, but the CHM board fails to be configured, and the
reverse SCH channel is released.

Failure Analysis

The CHM board configuration message is lost.

A CE of an SCH in the CHM is hung up.

If there is no resource hung up in the CHM, the database may have a


mistake in idle CE queue of database maintenance.

Handling Measure

1. Verify that the CPU of the CHM is not overloaded.


2. Verify that the CHM has no CE hung up.
3. Check the OMC database probe to verify that there is no mistake in idle
CE queue of database maintenance.

3-13
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

ZXC10 BSSB Failure Cause Reference(1X)

ERR_SPS_RLSA_RCM_RSCH_FunCallFail_RevSCHSetupFail

CHMSCHCE

CHMCE

1.

CHMCPU

2.

CHMCE

3.

CE

3.26 ERR_SPS_RLSA_RCM_FSCH_FunCallFail_Fwd
SCHSetupFail
Failure Name

ERR_SPS_RLSA_RCM_FSCH_FunCallFail_FwdSCHSetupFail

Failure Cause

During data service, when an channel is being set up and database is in


allocation, CHM board configuration fails and forward SCH channel is
released.

Failure Analysis

CHM board configuration message lost.

CE of SCH in CHM is hung up.

If there is no resource hung up in CHM, it is possible that database has


mistake in idle CE queue maintenance.

Handling Measure

1. Verify that the CPU of the CHM is not overloaded.


2. Verify that the CHM has no 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_FunCallFail_FwdSCHSetupFail

CHMSCHCE

CHMCE

1.

CHMCPU

2.

CHMCE

3.

CE

3-14
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

Chapter 3 Call Release Causes

3.27 ERR_SPS_RLSA_RCM_RSCH_FunCallFail_Burst
Commit_STATUS_RemovedSCH
Failure Name

ERR_SPS_RLSA_RCM_RSCH_FunCallFail_BurstCommit_STATUS_Re
movedSCH

Failure Analysis

The cell number is 0, or connection status is STATUS_RemovedSCH

Handling Measure

1. Verify that the CPU of the CHM is not overloaded.


2. Verify that the CHM has no hung up.
3. Check the database probe, and verify that there is no mistake in CE idle
queue of database maintenance.

ERR_SPS_RLSA_RCM_RSCH_FunCallFail_BurstCommit_STATUS_Re
movedSCH

0STATUS_RemovedSCH

1.

CHMCPU

2.

CHMCE

3.

CE

3.28 ERR_SPS_RLSA_RCM_RSCH_StateIncorrect_Cel
lNotFoundInRevSCHResourceExtension
Failure Name

ERR_SPS_RLSA_RCM_RSCH_StateIncorrect_CellNotFoundInRevSCH
ResourceExtension

Failure Cause

During data service, after SCH set up and when user transmits data
continuously, there is a newly added cell. This case is softer handoff add in
transmission. It is normal condition.

Handling Measure

Normal status.

ERR_SPS_RLSA_RCM_RSCH_StateIncorrect_CellNotFoundInRevSCH
ResourceExtension

3-15
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

ZXC10 BSSB Failure Cause Reference(1X)

3.29 ERR_SPS_RLSA_RCM_PCALL_TimerExpired_Tc
onfigtch
Failure Name
Failure Analysis

ERR_SPS_RLSA_RCM_PCALL_TimerExpired_Tconfigtch
During data service, when an SCH channel is being set up and database
is in allocation, CHM board configuration fails and forward SCH channel is
released. The possible failure causes are as follows:
l

CHM board configuration message is lost.

CE of SCH in CHM is hung up.

If there is no resource hung up in CHM, it is possible that database has


a mistake in idle CE queue maintenance.

Possible Solution

1. Verify that the CPU of the CHM is not overloaded.


2. Verify that the CHM has no CE hung up.
3. Check OMC database probe, confirm if there is mistake in CE idle
queue of database maintenance.

ERR_SPS_RLSA_RCM_PCALL_TimerExpired_Tconfigtch

CHMCE

CHMCE

1.

CHMCPU

2.

CHMCE

3.

OMCCE

3.30 ERR_SPS_RLSA_RCM_FSCH_OtherReason_End
OfDuration
Failure Name

ERR_SPS_RLSA_RCM_FSCH_OtherReason_EndOfDuration

Failure Analysis

The database notification message initiates the forward supplementary


channel release.

Handling Measure

It is a normal case, so no solution is needed.

ERR_SPS_RLSA_RCM_FSCH_OtherReason_EndOfDuration

3-16

SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

Chapter 4

Handoff Failure Causes


4.1 ERR_SPS_RLSA_BSSAP_TgtBSC_FunCallFail_Ta
rgetBSCHandlerEntry_A7HOReqMsgProccessFor
HOWith1X
Failure Name

ERR_SPS_RLSA_BSSAP_TgtBSC_FunCallFail__TargetBSCHandlerEntry
__A7HOReqMsgProccessForHOWith1X

Failure Cause

The target BSC interconnects with the HIRS BSC. The handoff request
processing is abnormal.

Failure Analysis

The number of cells is greater than the maximum number of cells that
a call occupies.

l
Handling Measure

The neighbor cell is not configured.

1. Check interconnection configurations.


2. Verify that the PN configuration of the neighbor cell is correct.

ERR_SPS_RLSA_BSSAP_TgtBSC_FunCallFail_TargetBSCHandlerEntry_
A7HOReqMsgProccessForHOWith1X

BSCHirs BSC

1.

2.

PN

4.2 ERR_SPS_RLSA_BSSAP_Other_ReceiveResetC
ircuit
Failure Name

ERR_SPS_RLSA_BSSAP_Other_ReceiveResetCircuit

Failure Cause

When a call is being established or a call is being established after hard


handoff, the circuit reset message sent from the MSC is received.

4-1
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

ZXC10 BSSB Failure Cause Reference(1X)

Failure Analysis

Handling Measure

The CIC state on the MSC side and that on the BSC side are different.

The CIC code on the MSC side and that on the BSC side are different.

1. Verify that the CIC state on the MSC side and that on the BSC side
are consistent.
2. Verify that the PCM codes on both the MSC and BSC sides are
consistent with the E1 cable.

Further

Contact MSC maintenance personnel for troubleshooting.

Troubleshooting

ERR_SPS_RLSA_BSSAP_Other_ReceiveResetCircuit

MSC

MSCBSCCIC

MSCBSCCIC

1.

MSCBSCCIC

2.

MSCBSCPCME1

3.

MSC

4.3 ERR_SPS_RLSA_BSSAP_TgtBSC_Other_TargetB
SCHandler_A7fHandoffRequestProccess_Recieve
dA7HOReqWhenSemiHO
Failure Name

ERR_SPS_RLSA_BSSAP_TgtBSC_Other_TargetBSCHandler_A7fHandoff
RequestProccess_RecievedA7HOReqWhenSemiHO

Failure Cause

In semi-soft handoff, A7 Handoff Requestmessage will be discarded if it


is received.

Failure Analysis
Handling Measure

Source side initiates a new handoff before semi-soft handoff flow completes.
It is acceptable if the problem occurs occasionally, otherwise, check the
BSC at source side.

ERR_SPS_RLSA_BSSAP_TgtBSC_Other_TargetBSCHandler_A7fHandoff
RequestProccess _RecievedA7HOReqWhenSemiHO

A7 Handoff Request

BSC

4-2
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

Chapter 4 Handoff Failure Causes

4.4 ERR_SPS_RLSA_BSSAP_Other_SBSSRFailure
Failure Name

ERR_SPS_RLSA_BSSAP_Other_SBSSRFailure

Failure Cause

A failure occurs during a transition, and the target side is expected to send a
transition failure message.

Failure Analysis

A failure occurs during a transition due to multiple reasons, and the target
side is expected to send a transition failure message.

Handling Measure

Some BTSs may report the failure cause. If the failure occurs frequently,
contact the local ZTE office.

4.5 ERR_SPS_RLSA_BSSAP_DB_GetPeerCellDiscri
minator
Failure Name

ERR_SPS_RLSA_BSSAP_DB_GetPeerCellDiscriminator

Failure Cause

The BSC fails to obtain the cell discrimination type of the peer BSC in a
non-network interconnection handoff from the database according to the
office No. of the interconnected BS.

Failure Analysis

The database is abnormal or the peer BSC does not support the
non-network interconnection.

Handling Measure

Check the configuration.

4.6 ERR_SPS_RLSA_BSSAP_UnexptMsg_TSendAssig
nmentMsgNotInValidState
Failure Name

ERR_SPS_RLSA_BSSAP_UnexptMsg_TSendAssignmentMsgNotInValidState

Failure Cause

The MS receives a TSendAssignmentMsg timeout message when it is in an


incorrect state.

Failure Analysis

The MS receives a TSendAssignmentMsg timeout message when it is neither


in the S_HardHOAdd_Setup nor in the S_HardHOAdd_AllocationResource
state. The MS may go into another state due to a system allocation failure or
other reasons when receiving the TSendAssignmentMsg timeout message.

Handling Measure

If the failure rarely occurs, it is unnecessary to handle. If the failure occurs


frequently, contact the ZTE engineer.

4-3
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

ZXC10 BSSB Failure Cause Reference(1X)

4.7 ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvSBSSAc
kNotInSetupState
Failure Name

ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvSBSSAckNotInSetupState

Failure Cause

The MS receives an SBSSAck message when it is not in the Setup State.

Failure Analysis

The MS may go into another state due to a system allocation failure or other
reasons when receiving the SBSSAck message.

Handling Measure

If the failure rarely occurs, it is unnecessary to handle. If the failure occurs


frequently, contact the ZTE engineer.

4.8 ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvSBSSA
ck_bTbssapRlcReqOut
Failure Name

ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvSBSSAck_bTbssapRlcReqOut

Failure Cause

An SBSSRelocationRequestAck message is received after TbssapRlcReq


expires.

Failure Analysis

The trg progress at the target side does not respond in time, or the link is
broken.

Handling Measure

If the failure rarely occurs, it is unnecessary to handle. If the failure occurs


frequently, contact the ZTE engineer.

4.9 ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvAvrHOR
equiredSBSSRInV5System
Failure Name

ERR_SPS_RLSA_BSSAP_UnexptMsg_RcvAvrHORequiredSBSSRInV5System

Failure Cause

The V5 system receives a transition hard handoff request.

Failure Analysis

After receiving a transition hard handoff request, the V5 system returns it


directly without performing transition processing.

Handling Measure

If the failure rarely occurs, it is unnecessary to handle. If the failure occurs


frequently, contact the ZTE engineer.

4-4
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

Chapter 4 Handoff Failure Causes

4.10 ERR_SPS_RLSA_BSSAP_UnexptMsg_TargetRem
ovalReqInSBSSRCallSetup
Failure Name

ERR_SPS_RLSA_BSSAP_UnexptMsg_TargetRemovalReqInSBSSRCallSetup

Failure Cause

The MS receives an AbisdrTargetRemovalReq message when it is in the


CallSetup state.

Failure Analysis

The state changes due to some reason, for example, a resource allocation
failure.

Handling Measure

If the failure rarely occurs, it is unnecessary to handle. If the failure occurs


frequently, contact the ZTE engineer.

4.11 ERR_SPS_RLSA_BSSAP_UnexptMsg_TbssapRlc
ReqNotInSetupState
Failure Name

ERR_SPS_RLSA_BSSAP_UnexptMsg_TbssapRlcReqNotInSetupState

Failure Cause

The MS receives a TbssapRlcReq timeout message when it is in an


incorrect state.

Failure Analysis

The MS is not in the S_HardHOAdd_Setup state when the timer expires.

Handling Measure

If the exception occurs occasionally, it is unnecessary to handle.

4.12 ERR_SPS_RLSA_BSSAP_MsgPara_SBSSRReque
stAck_atCellInfoIsInvalid
Failure Name

ERR_SPS_RLSA_BSSAP_MsgPara_SBSSRReque stAck_atCellInfoIsInvalid

Failure Cause

The cell ID (CI) carried by the SBSSRRequestAck message does not


contain the CI that the handoff request message carries.

Failure Analysis

The failure may result from a CI configuration error or acute signal


fluctuation.

Handling Measure

If the failure rarely occurs, it is unnecessary to handle. If the failure occurs


frequently, contact the ZTE engineer.

4-5
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

ZXC10 BSSB Failure Cause Reference(1X)

4.13 ERR_SPS_RLSA_BSSAP_MsgPara_SBSSRReque
stAck_ServiceTypeIsNotMatched
Failure Name

ERR_SPS_RLSA_BSSAP_MsgPara_SBSSRRequestAck_ServiceTypeIsNotMatched

Failure Cause

The service type carried in SBSSRRequestAck is inconsistent with that


in the MSC.

Failure Analysis

Concurrence is not supported for A interface transition. The failure occurs


when the service type of the target progress is inconsistent with that of
the MSC.

Handling Measure

If the failure rarely occurs, it is unnecessary to handle. If the failure occurs


frequently, contact the ZTE engineer.

4.14 ERR_SPS_RLSA_BSSAP_TE_TbssapRlcReq
Failure Name

ERR_SPS_RLSA_BSSAP_TE_TbssapRlcReq

Failure Cause

The relocation timer expires.

Failure Analysis

No response is received after a relocation message is sent.

Handling Measure

If the failure rarely occurs, it is unnecessary to handle. If the failure occurs


frequently, contact the ZTE engineer.

4.15 ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_A
7HandoffRequestReceived
Failure Name

ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_A7HandoffRequestReceived

Failure Cause

The target side receives a handoff request from the serving side when it
does not finish the current non-network interconnection handoff.

Failure Analysis

A message loss occurs during the handoff or a processing exception occurs


on the serving side.

Handling Measure

If the failure occurs occasionally, it is unnecessary to handle. If it occurs


frequently, contact the ZTE engineer.

4-6
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

Chapter 4 Handoff Failure Causes

4.16 ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_
A7DropTargetReceived
Failure Name
Failure Cause

ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_A7DropTargetReceived
The target side receives a handoff drop request from the serving side when
it has not finished the current non-network interconnection handoff.

Failure Analysis

A message loss occurs during the handoff or a processing exception occurs


on the serving side.

Handling Measure

If the failure occurs occasionally, it is unnecessary to handle. If it occurs


frequently, contact the ZTE engineer.

4.17 ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_A
3DropReceived
Failure Name

ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_A3DropReceived

Failure Cause

The target side receives a leg elimination request from the serving side
when it has not finished the current non-network interconnection handoff.

Failure Analysis

A message loss occurs during the handoff or a processing exception occurs


on the serving side.

Handling Measure

If the failure occurs occasionally, it is unnecessary to handle. If it occurs


frequently, contact the ZTE engineer.

4.18 ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_T
waitRlcExpired
Failure Name
Failure Cause

ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_TwaitRlcExpired
The soft handoff progress at the target side does not receive the
EV_S_SBSSRelocationComplete message in the timer duration after
sending an EV_S_SBSSRelocationRequestAck message to the hard
handoff progress during a non-network interconnection handoff.

Failure Analysis

The message is lost or a processing exception occurs on the hard handoff


progress at the target side during the handoff.

Handling Measure

If the failure occurs occasionally, it is unnecessary to handle. If it occurs


frequently, contact the ZTE engineer.

4-7
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

ZXC10 BSSB Failure Cause Reference(1X)

4.19 ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_T
waitDrpTgtExpired
Failure Name
Failure Cause

ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_TwaitDrpTgtExpired
The soft handoff progress at the target side does not receive the
A7DropTaregt message from the serving side in the timer duration after
receiving an EV_S_SBSSRelocationComplete message from the hard
handoff progress at the target side during a non-network interconnection
handoff.

Failure Analysis

The A7DropTaregt message is lost or a processing exception occurs on the


progress at the serving side.

Handling Measure

It is unnecessary to handle. If it occurs frequently, however, report to ZTE


Corporation for analysis.

4.20 ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_R
ecvRlcReqWhenSoftHOAdd
Failure Name

ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_RecvRlcReqWhenSoftHOAdd

Failure Cause

A non-network interconnection handoff request from the serving side is


received in a soft handoff.

Failure Analysis

The failure may result from a message loss or a processing exception at


the serving side.

Handling Measure

If it occurs occasionally, it is unnecessary to handle. If it occurs frequently,


contact the ZTE engineer.

4.21 ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_Re
cvRlcReqWhenSoftHODrop
Failure Name

ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_RecvRlcReqWhenSoftHODrop

Failure Cause

A non-network interconnection handoff request from the serving side is


received in a soft handoff drop.

Failure Analysis

The failure may result from a message loss or a processing exception at


the serving side.

4-8
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

Chapter 4 Handoff Failure Causes

Handling Measure

If it occurs occasionally, it is unnecessary to handle. If it occurs frequently,


contact the ZTE engineer.

4.22 ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_R
ecvRlcReqWhenSemiHOAdd
Failure Name

ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_RecvRlcReqWhenSemiHOAdd

Failure Cause

A non-network interconnection handoff request from the serving side is


received in a semi-soft handoff.

Failure Analysis

The failure may result from a message loss or a processing exception at


the serving side.

Handling Measure

Contact ZTE Corporation for analysis.

4.23 ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_R
ecvRlcReqWhenSCHExist
Failure Name

ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_RecvRlcReqWhenSCHExist

Failure Cause

The supplemental channel still exists when a non-network interconnection


handoff request is received.

Failure Analysis

A processing exception occurs.

Handling Measure

Contact ZTE Corporation for analysis.

4.24 ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_
WrongChannelItemState
Failure Name

ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_WrongChannelItemState

Failure Cause

After receiving a non-network interconnection handoff, the system finds that


the channel table is in an unexpected state and reject the handoff.

Failure Analysis

The message for adding channel tables is lost.

Handling Measure

It is unnecessary to handle.

4-9
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

ZXC10 BSSB Failure Cause Reference(1X)

4.25 ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_U
nexpectedRlcState
Failure Name
Failure Cause

ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_UnexpectedRlcState
A message that is not expected to be received in the current state is
received during a non-network interconnection handoff.

Failure Analysis

The failure results from a message loss.

Handling Measure

If it occurs occasionally, it is unnecessary to handle. If it occurs frequently,


contact the ZTE engineer.

4.26 ERR_SPS_RLSA_BSSAP_HODrop_A1RequiredR
eject_OAMIntervention
Failure Name

ERR_SPS_RLSA_BSSAP_HODrop_A1RequiredReject_OAMIntervention

Failure Cause

The outgoing hard handoff process is interrupted by the background of the


switch and hence the process is terminated.

Failure Analysis

The outgoing hard handoff process is interrupted by the background of the


switch and hence the process is terminated.

Handling Measure

Contact ZTE Corporation for analysis.

4.27 ERR_SPS_RLSA_BSSAP_HODrop_A1RequiredRe
ject_EquipmentFailure
Failure Name

ERR_SPS_RLSA_BSSAP_HODrop_A1RequiredReject_EquipmentFailure

Failure Cause

During the outgoing hard handoff process, an internal processing error


occurs on the switch.

Failure Analysis

During the outgoing hard handoff process, an internal processing error


occurs on the switch.

Handling Measure

Contact ZTE Corporation for analysis.

4-10
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

Chapter 4 Handoff Failure Causes

4.28 ERR_SPS_RLSA_BSSAP_HODrop_A1RequiredRe
ject_NoRadioResourceAvailable
Failure Name

ERR_SPS_RLSA_BSSAP_HODrop_A1RequiredReject_NoRadioResource
Available

Failure Cause

During the outgoing hard handoff process, no radio resource is available.

Failure Analysis

Target-side resource setup fails.

Handling Measure

Capture the target-side handoff signaling, and contact ZTE Corporation


for analysis.

4.29 ERR_SPS_RLSA_BSSAP_HODrop_A1Required
Reject_RTRUnavailable
Failure Name

ERR_SPS_RLSA_BSSAP_HODrop_A1RequiredReject_RTRUnavailable

Failure Cause

During the outgoing hard handoff process, the required terrestrial circuit
resources are unavailable.

Failure Analysis

The terrestrial circuit resources are restricted.

Handling Measure

Contact ZTE Corporation for analysis.

4.30 ERR_SPS_RLSA_BSSAP_HODrop_A1Required
Reject_BSNotEquipped
Failure Name
Failure Cause

ERR_SPS_RLSA_BSSAP_HODrop_A1RequiredReject_BSNotEquipped
During the outgoing hard handoff process, there is a problem with the status
of the target BS.

Failure Analysis

There is a problem with the status of the target BS.

Handling Measure

Contact ZTE Corporation for analysis.

4.31 ERR_SPS_RLSA_BSSAP_HODrop_A1Required
Reject_HandoffBlocked
Failure Name

ERR_SPS_RLSA_BSSAP_HODrop_A1RequiredReject_HandoffBlocked

Failure Cause

The outgoing hard handoff is rejected by the switch.


4-11

SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

ZXC10 BSSB Failure Cause Reference(1X)

Failure Analysis

The outgoing hard handoff is rejected by the switch.

Handling Measure

Contact ZTE Corporation for analysis.

4.32 ERR_SPS_RLSA_BSSAP_HODrop_A1Required
Reject_RTAUnavailable
Failure Name

ERR_SPS_RLSA_BSSAP_HODrop_A1RequiredReject_RTAUnavailable

Failure Cause

During the outgoing hard handoff process, the required coding/rate are
unavailable.

Failure Analysis

The coding/rate are unavailable

Handling Measure

Contact ZTE Corporation for analysis.

4.33 ERR_SPS_RLSA_BSSAP_HODrop_A1RequiredRe
ject_TimeOut
Failure Name

ERR_SPS_RLSA_BSSAP_HODrop_A1RequiredReject_TimeOut

Failure Cause

During the outgoing hard handoff process, the handoff timer of the switch
times out.

Failure Analysis
Handling Measure

The setup of the target times out.


Capture the handoff signaling on the target of the hard handoff, and contact
ZTE Corporation for analysis.

4.34 ERR_SPS_RLSA_BSSAP_HODrop_A1RequiredR
eject_Unspecified
Failure Name

ERR_SPS_RLSA_BSSAP_HODrop_A1RequiredReject_Unspecified

Failure Cause

The outgoing hard handoff process is released by the switch.

Failure Analysis

There is a problem with the internal flow of the switch.

Handling Measure

Contact ZTE Corporation for analysis.

4-12
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

Chapter 4 Handoff Failure Causes

4.35 SOFTADD_CELL_ERROR
Failure Name

SOFTADD_CELL_ERROR

Failure Cause

Continuous transmission or softer add for reverse supplementary channel,


cell of DBS given by RCM has error.

Failure Analysis

The possible failure causes are as follows:


l

Lost of release message may cause this fault, but the possibility is
comparatively small.

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.

Handling Measure

Changing flow is suggested. Supplementary channel module of DSPM


makes SCH setup application after FCH module handoff is finished.

SOFTADD_CELL_ERROR

RCMDBS

BSC
BTSBTS

DSPMFCHSCH

4.36 ERR_SPS_RLSA_DSPM_HOH_TimerExpired_Soft
HOThocompletion
Failure Name

ERR_SPS_RLSA_DSPM_HOH_TimerExpired_SoftHOThocompletion

Failure Cause

In soft handoffs, the base station sends a handoff indication (HDM). A


Handoff Completes Message (HCM) is not received from the MS after
Thocompletion (default value is 5 s) expires.

Failure Analysis

Poor radio condition causes the air-interface handshake message to be


missing. It is acceptable if this failure occurs occasionally.

BTS clock is inconsistent with BSC clock when frame number checking
is enabled.

Transmission bit error.

4-13
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

ZXC10 BSSB Failure Cause Reference(1X)

Possible Solution

1. Verify that the setting of Thocompletion timer on DSMP board is correct


(default value is 5 s).
2. Check the transmission power of handoff target cell.
3. Check handoff target BTS board and calls under this BTS.
4. Check the versions and operation of ABPM, DTB and DSM.

ERR_SPS_RLSA_DSPM_HOH_TimerExpired_SoftHOThocompletion

HDMThocompletion5 s
MSHCM

BTSBSC

1. DSMPThocompletion5 s
2.

3.

BTSBTS

4.

ABPMDTBDSM

4.37 ERR_SPS_RLSA_DSPM_HOH_TimerExpired_T
horeq
Failure Name

ERR_SPS_RLSA_DSPM_HOH_TimerExpired_Thoreq

Failure Cause

Handoff request response expires.

Failure Analysis

The possible failure causes are as follows:


1. Abis/A3A7 interface link is faulty.
2. Handoff target BTS board runs abnormally.
3. Carrier is faulty.
4. Channel board is faulty.
5. Inter BSC handoff, the A3A7 interface boards (HGM) of the two BSC
run abnormally.

Handling Measure

1. Check the setting of Thoreqtimer on DSMP board (default value is 5s).


2. Check Abis/A3A7 interface link.
3. Check the handoff target BTS board, carrier state and channel board (if
chip is normal, and if CE is blocked).
4. Inter BSC handoff: Check the A3, A7 interface boards (HGM) of the
two BSC and physical links.

Further

Check the version and operation of CCM board.

Troubleshooting

4-14
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

Chapter 4 Handoff Failure Causes

ERR_SPS_RLSA_DSPM_HOH_TimerExpired_Thoreq

Abis/A3A7

BTS

BSCBSCA3A7HGM

1.

DSMPThoreq5 s

2.

Abis/A3A7

3. BTS
CE
4. BSCBSCA3A7HGM

5.

CCM

4.38 ERR_SPS_RLSA_DSPM_HOH_ResNotSatisfied_H
OHOnUmrCFSearchReport
Failure Name

ERR_SPS_RLSA_DSPM_HOH_ResNotSatisfied_HOHOnUmrCFSearc
hReport

Failure Cause

In semi-soft handoff, the handoff at target side fails.

Failure Analysis

The possible failure causes are as follows:


l

Poor radio condition causes air-interface message missing. It is


acceptable if this failure occurs occasionally.

l
Further

Radio condition is poor, target carrier signal is too weak.

Check the versions and operation of ABPM, DTB and DSM.

Troubleshooting
Handling Measure

Check target carrier signal strength.

ERR_SPS_RLSA_DSPM_HOH_ResNotSatisfied_HOHOnUmrCFSearchR
eport

1.

2. ABPMDTBDSM
4-15
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

ZXC10 BSSB Failure Cause Reference(1X)

4.39 ERR_SPS_RLSA_DSPM_HOH_TimerExpired_Sem
iSoftHOThocompletion
Failure Name

ERR_SPS_RLSA_DSPM_HOH_TimerExpired_SemiSoftHOThocompletion

Failure Cause

In semi-handoffs, the base station sends a handoff indication (HDM). If the


MS handoff completes message (HCM) is not received when Thocompletion
(default value is 5 s) expires, the handoff will expire.

Failure Analysis

The possible failure causes are as follows:


l

Poor radio condition causes air-interface handshake message to be


missing. It is acceptable if this failure occurs occasionally.

If frame number checking is enabled, BTS and BSC have different


clocks.

l
Handling Measure

Transmission bit error.

1. Verify that the setting of the Thocompletion timer of the DSMP board is
correct (default value 5 s).
2. Check the handoff target cell transmission power.
3. Check the handoff target BTS board to see whether the call origination
under this BTS is normal or not.

Further

Check the versions and operation of ABPM, DTB and DSM.

Troubleshooting

ERR_SPS_RLSA_DSPM_HOH_TimerExpired_SemiSoftHOThocompletion

HDMThocompletion5 s
MSHCM

BTSBSC

1. DSMPThocompletion5 s
2.

3.

BTSBTS

4. ABPMDTBDSM

4.40 ERR_SPS_RLSA_DSPM_HOH_ResNotSatisfied
_HOHOnA7rHOReqAck
Failure Name

ERR_SPS_RLSA_DSPM_HOH_ResNotSatisfied_HOHOnA7rHOReqAck

Failure Cause

Handoff request is rejected by target side.


4-16

SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

Chapter 4 Handoff Failure Causes

Failure Analysis

Handling Measure

The possible failure causes are as follows:


l

Resource at target BTS/BSC side has problem.

Flow has problem.

1. Check Abis/A3A7 interface link.


2. Check the handoff target BTS board, carrier state and channel board
(Verify that the chip is normal and CE is not blocked).
3. Inter BSC handoff: Check the A3A7 interface board (HGM) of the two
BSC and the physical link.

Further

Check the version and operation of CCM board.

Troubleshooting

ERR_SPS_RLSA_DSPM_HOH_ResNotSatisfied_HOHOnA7rHOReqAck

BTS/BSC

1.

Abis/A3A7

2. BTS
CE
3. BSCBSCA3A7HGM

4.

CCM

4.41 ERR_SPS_RLSA_DSPM_HOH_ResourceAllocFai
l_GetHandoffProc
Failure Name

ERR_SPS_RLSA_DSPM_HOH_ResourceAllocFail_GetHandoffProc

Failure Cause

In the process of handoff, the database assignment resource adjusted by


Layer 3 fails.

Failure Analysis

The selected carrier frequency state is wrong, relevant macro value:


HO_STAT_CARRIER_STATE_ERROR (0x00004A03).

The selected carrier frequency is a pseudo pilot, relevant macro value:


HO_STAT_CARRIER_BEACON (0x00004A04).

The selected carrier frequency has no CE resource, relevant macro

The selected carrier frequency has no 5KCE resource, relevant macro

value: HO_STAT_CARRIER_NO_CE (0x00004A05).


value: HO_STAT_CARRIER_NO_CE (0x00004A06).
l

The selected carrier frequency does not match FO, relevant macro
value: HO_STAT_CARRIER_FO_NOT_MATCH (0x00004A07).

4-17
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

ZXC10 BSSB Failure Cause Reference(1X)

The selected carrier frequency does not match the pilot, relevant macro
value: HO_STAT_PILOT_NO_SAME_FREQ (0x00004A08).

All carrier frequencies are unable to be used, relevant macro value:


HO_STAT_PILOT_ALLCARRIER_NOT_AVAILABLE (0x00004A09).

All carrier frequencies have no FO, relevant macro value:


HO_STAT_PILOT_ALLCARRIER_NO_FO (0x00004A0A).

The pilot does not belong to this BSC, relevant macro value:
HO_STAT_PILOT_NOT_LOCALBSS (0x00004A0B).

Pilot home is unclear, not configuring neighbor cell, relevant macro

BSC is not interconnected, relevant macro value: HO_STAT_PILOT_IS

value: HO_STAT_PILOT_IS_NOT_NEIGHBOR (0x00004A0C).


_OTHER_UNLNKBSS (0x00004A0D).
l

Target BSC does not support PTT relevant macro value:

Support data service and soft-handoff between IP and HIRS, relevant

HO_STAT_DESTBSC_NOT_SUPPORT_PTT (0x00004A0E).
macro value: HO_STAT_DESTBSC_IS_HIRS_DATASOFTHO
(0x00004A0F).
l

Interconnection state is wrong, relevant macro value:


HO_STAT_DESTBSC_LINKSTATUS_ERROR (0x00004A10).

Cell modes are wrong, relevant macro value: HO_STAT_PILOT_CELL


MODE_DIFFERENT (0x00004A11).

Possible Solution

1. Check specific information by detecting the fault probe.


2. Check the current carrier frequency state.
3. Check the current neighbor cell configuration.

ERR_SPS_RLSA_DSPM_HOH_ResourceAllocFail_GetHandoffProc

HO_STAT_CARRIER_STATE_ERROR0x00004A03

HO_STAT_CARRIER_BEACON
0x00004A04

CEHO_STAT_CARRIER_NO_CE
0x00004A05

5KCEHO_STAT_CARRIER_NO_CE
0x00004A06

FOHO_STAT_CARRIER_FO_NOT_MATCH0x00004A07

HO_STAT_PILOT_NO_SAME_FREQ
0x00004A08

HO_STAT_PILOT_ALLCARRIER_NOT_AVAILABLE0x00004A09

4-18
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

Chapter 4 Handoff Failure Causes

FOHO_STAT_PILOT_ALLCARRIER_NO_FO0x00004A0A

BSCHO_STAT_PILOT_NOT_LOCALBSS
0x00004A0B

HO_STAT_PILOT_IS_NOT_NEIGHBOR0x00004A0C

BSCHO_STAT_PILOT_IS_OTHER_UNLNKBSS
0x00004A0D

BSCPTTHO_STAT_DESTBSC_NOT_SUPPORT_PTT0x00004A0E

IPHIRSBSC
HO_STAT_DESTBSC_IS_HIRS_DATASOFTHO0x00004A0F

HO_STAT_DESTBSC_LINKSTATUS_ERROR0x00004A10

HO_STAT_PILOT_CELLMODE_DIFFERENT0x00004A11

1.

2.

3.

4.42 ERR_SPS_RLSA_DSPM_CLH_OtherReason_SDM
SetISLPFailure
Failure Name

ERR_SPS_RLSA_DSPM_CLH_OtherReason_SDMSetISLPFailure

Failure Cause

When the military network in encrypted or the telecommunication media is


under transparent transmission, SDM fails to configure ISLP protocol.

Failure Analysis

When the conversation gets encrypted, SDM fails to inform VTC to enable
the ISLP protocol.

Handling Measure

Verify that the VTC version is normal.

ERR_SPS_RLSA_DSPM_CLH_OtherReason_SDMSetISLPFailure

SDMISLP

SDMVTCISLP

VTC

4-19
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

ZXC10 BSSB Failure Cause Reference(1X)

4.43 ERR_SPS_RLSA_DSPM_HOH_FunCallFail_HOHO
nDBSHOProcACK_PNSConstructFrmDBS
Failure Name

ERR_SPS_RLSA_DSPM_HOH_FunCallFail_HOHOnDBSHOProcACK_PN
SConstructFrmDBS

Failure Cause

Error occurs when obtaining new active set during handoff.

Failure Analysis

The database internal status is incorrect.

Obtaining CCM, ABPM or HGM address of the new cell fails.

Obtaining the frame type of the new cell fails.

Obtaining the IBBE address fails.

Handling Measure

1. Verify that the CCM, ABPM, HGM, and IBBE boards are normal.
2. Verify that the A7 link is normal.
3. Verify that the cell node configuration in OMC is correct.

ERR_SPS_RLSA_DSPM_HOH_FunCallFail_HOHOnDBSHOProcACK_PN
SConstructFrmDBS

CCMABPMHGM

IBBE

1.

CCMABPMHGMIBBE

2.

A7

3.

4.44 ERR_SPS_RLSA_DSPM_HOH_TimerExpired_T
hocompletion
Failure Name

ERR_SPS_RLSA_DSPM_HOH_TimerExpired_Thocompletion

Failure Cause

Handoff times out.

Failure Analysis

The radio environment is poor, causing the handoff indication message


of the forward air interface to be lost.

The radio environment is poor, causing the handoff complete message


of the reverse air interface to be lost.

Handling Measure

Check the carrier signal strength. If the problem rarely occurs, it is normal.

4-20
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

Chapter 4 Handoff Failure Causes

ERR_SPS_RLSA_DSPM_HOH_TimerExpired_Thocompletion

4.45 HO_STAT_DESTBSC_IS_HIRS_DATASOFTHO
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.

Handling Measure

Use an IBBE board so that IP BSC and HIRS BSC support soft handoff
within BSC with data service.

HO_STAT_DESTBSC_IS_HIRS_DATASOFTHO

HGMbsc

HGMbsc

IP BSCHIRS BSCBSCIP BSCIP BSC


IBBEBSC

4.46 HO_STAT_PILOT_NOT_LOCALBSS
Failure Name

HO_STAT_PILOT_NOT_LOCALBSS

Failure Cause

PN does not belong to the BSC.

Failure Analysis

Remove the other BSC PN while performing the hard handoff on the BSC.

Possible Solution

Normal flow.

HO_STAT_PILOT_NOT_LOCALBSS

PNBSC

BSCBSC PN

4-21
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

ZXC10 BSSB Failure Cause Reference(1X)

4.47 HO_Func_GetTargetFromPreCell_ERR
Failure Name

HO_Func_GetTargetFromPreCell_ERR

Failure Cause

The candidate frequency in the active set and the preferred neighbor cell fail
to be obtained during a blind handoff.

Failure Analysis

The candidate frequency in the active set and the preferred neighbor cell fail
to be obtained during a blind handoff.

Handling Measure

Check the handoff parameters.

4.48 SOME_CELL_FAIL
Failure Name

SOME_CELL_FAIL

Failure Cause

In the case of forward supplementary channel soft handoff, the handoff


of specific cells fails.

Failure Analysis

Handling Measure

The resources are insufficient.

The power is insufficient.

The Ec/Io is insufficient.

Check the CE resource status on the BTS side and the carrier power
overload status.

SOME_CELL_FAIL

Ec/Io

BTSCE

4.49 CELL_IS_ERROR
Failure Name

CELL_IS_ERROR

Failure Cause

In the F-SCH soft handoff mode, the number of cells that re-transmit
application requests is smaller than the number of current cells.

Failure Analysis

In the F-SCH soft handoff mode, the number of cells that re-transmit
application requests is smaller than the number of current cells.

Handling Measure

Verify that the pilot strength of the user active set decreases sharply. If such
problems frequently occur, contact the local office of ZTE.

CELL_IS_ERROR
4-22

SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

Chapter 4 Handoff Failure Causes

4.50 HO_STAT_PILOT_LIMITED
Failure Name

HO_STAT_PILOT_LIMITED

Failure Cause

During assignment to soft handoff mode, leg setup is forbidden in the cell
that has satisfying resources due to the limit of this mode.

Failure Analysis

The failure cause depends on the value of switch 96, as described in the
following:
l

When switch 96 is set to 0, all strong legs are set up and leg setup
is forbidden in the cell with weak signals although it has satisfying
resources.

When switch 96 is set to 1, leg setup is performed in the reference cell


only. Therefore, the non-reference cell cannot set up legs although it
has satisfying resources.

When switch 96 is set to 2, strong legs with equivalent strength are set
up. In this mode, leg setup is forbidden in the cell with weak signals
although it has satisfying resources.

Handling Measure

Check switch 96, absolute threshold of weak pilot ECIO, differential


threshold of weak pilot ECIO and pilot strength of the cell where the failure
occurs.

4.51 ERR_SPS_RLSA_RCM_FCH_OtherReason_MReq
uestAbisConnect_SpecifiedCellIsReleasing
Failure Name

ERR_SPS_RLSA_RCM_FCH_OtherReason_MRequestAbisConnect_Spec
ifiedCellIsReleasing

Failure Analysis

1. During soft or softer handoff, if handoff happens frequently, handoff has


been started when the release has not been completeed, the problem
may occur.
2. If the problem occurs during normal calls while no handoff is performed,
it is possible that the internal processing is stopped.

Possible Solution

It is acceptable if the problem occurs occasionally. If the problem occurs


frequently, check the fault probe and take measures after identifying the
cause.
4-23

SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

ZXC10 BSSB Failure Cause Reference(1X)

ERR_SPS_RLSA_RCM_FCH_OtherReason_MRequestAbisConnect_Spec
ifiedCellIsReleasing

1.

2.

4.52 ERR_SPS_RLSA_RCM_PCALL_RecvUnexptMsg_
atTchStatusInSemiSoft_AbisdfBurstRequest
Failure Name

ERR_SPS_RLSA_RCM_PCALL_RecvUnexptMsg_atTchStatusInSemiSoft
_AbisdfBurstRequest

Failure Analysis

During half-soft handoff of data service, if the supplementary channel setup


message is received, the SCH setup message is refused. Failure caused by
this reason is normal.

Possible Solution

It is acceptable if the failure occurs occasionally. If the failure occurs


frequently, contact the local office of ZTE Corporation.

ERR_SPS_RLSA_RCM_PCALL_RecvUnexptMsg_atTchStatusInSemiSoft
_AbisdfBurstRequest

SCH

4.53 HO_STAT_PILOT_IS_OTHER_UNLNKBSS
Failure Name

HO_STAT_PILOT_IS_OTHER_UNLNKBSS

Failure Cause

Pilot is neither in the BSC nor in the other interconnected BSC.

Failure Analysis

The MS is in the critical cell and reports that the pilot number is not under
this BSC and not interconnected.

Possible Solution

Check the neighboring configuration of the cell.

HO_STAT_PILOT_IS_OTHER_UNLNKBSS
4-24

SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

Chapter 4 Handoff Failure Causes

BSCBSC

BSCBSC

4.54 HO_STAT_PILOT_NO_SAME_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 cannot be added.

Failure Analysis

For soft handoff, this reason means there is no suitable frequency


under the pilot; this should not occur. Because if there is no suitable
carrier, Layer 3 should not submit it; if this does occur, it is an error.

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 is probably no such carrier, and
it is normal to submit the reason.

Possible Solution

For soft handoff, verify that the frequency for soft handoff is configured
under PN that is to be added.

HO_STAT_PILOT_NO_SAME_FREQ

PN

4.55 HO_STAT_CARRIER_PWR_OVERLOAD
Failure Name

HO_STAT_CARRIER_PWR_OVERLOAD

Failure Cause

Power of the selected carrier is overloaded.

Failure Analysis

During handoff judge, the power of the selected carrier is overloaded. The
reason for this failure is: The carrier has too many subscribers.

Possible Solution

Decrease the subscriber quantity of every carrier.

4-25
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

ZXC10 BSSB Failure Cause Reference(1X)

HO_STAT_CARRIER_PWR_OVERLOAD

4.56 HO_STAT_CARRIER_STATE_MBLOCK
Failure Name

HO_STAT_CARRIER_STATE_MBLOCK

Failure Cause

The selected carrier frequency is manually blocked.

Failure Analysis

The carrier frequency is manually blocked, so it is unavailable.

Handling Measure

Unblock the carrier frequency.

4.57 HO_STAT_CARRIER_STATE_RFE_BROKEN
Failure Name

HO_STAT_CARRIER_STATE_RFE_BROKEN

Failure Cause

The radio frequency of the carrier is faulty.

Failure Analysis

The radio frequency of the carrier is faulty, so the carrier status is abnormal.

Possible Solution

Check the radio frequency configuration of the carrier.

HO_STAT_CARRIER_STATE_RFE_BROKEN

4.58 HO_STAT_CARRIER_STATE_RFE_LOWPOWER
Failure Name

HO_STAT_CARRIER_STATE_RFE_LOWPOWER

Failure Cause

The power of the carrier is low.

Failure Analysis

The power of the carrier is low, so the carrier status is abnormal.

Possible Solution

Increase the radio frequency power of the carrier.

HO_STAT_CARRIER_STATE_RFE_LOWPOWER
4-26

SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

Chapter 4 Handoff Failure Causes

4.59 HO_STAT_CARRIER_STATE_BDS_DISCONNECT
Failure Name

HO_STAT_CARRIER_STATE_BDS_DISCONNECT

Failure Cause

The Abis link is abnormal.

Failure Analysis

The link between the BSC and BTS is broken.

Possible Solution

Check the Abis link.

HO_STAT_CARRIER_STATE_BDS_DISCONNECT

Abis

BSCBTS

Abis

4.60 HO_STAT_CARRIER_STATE_RFE_POWERDOWN
Failure Name

HO_STAT_CARRIER_STATE_RFE_POWERDOWN

Failure Cause

Power amplifier is disabled in case of dynamic power consumption.

Failure Analysis

Power amplifier is disabled in case of dynamic power consumption.

Possible Solution

Check the dynamic power consumption configuration.

HO_STAT_CARRIER_STATE_RFE_POWERDOWN

4.61 HO_STAT_CARRIER_RESOURCE_RESERVED
Failure Name

HO_STAT_CARRIER_RESOURCE_RESERVED

Failure Cause

The reserved resources cause the carrier frequency to be unavailable.

4-27
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

ZXC10 BSSB Failure Cause Reference(1X)

Failure Analysis

Particular power or Walsh code resources of the carrier frequency are


reserved for voice or data services, causing the carrier frequency to be
unavailable.

Possible Solution

Check the reserved resource parameter configuration of the carrier


frequency.

HO_STAT_CARRIER_RESOURCE_RESERVED

Walshcode

4.62 HO_STAT_CARRIER_LIMITED
Failure Name

HO_STAT_CARRIER_LIMITED

Failure Cause

The service on the carrier frequency is restricted.

Failure Analysis

Service based on carrier frequency function. In the fixed allocation mode, in


accordance with the service attributes of the carrier frequency, the carrier
frequency can only be used for the PTT service or non-PTT service.

Possible Solution

Check the configuration of the service based on carrier function.

HO_STAT_CARRIER_LIMITED

PTTPTT

4.63 HO_STAT_CARRIER_NO_CE
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. Verify that there is no CE blocked.


2. Decrease the subscriber quantity for every carrier.

4-28
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

Chapter 4 Handoff Failure Causes

HO_STAT_CARRIER_NO_CE

CE

CE

1.

CE

2.

4.64 HO_STAT_CARRIER_NO_5KCE
Failure Name

HO_STAT_CARRIER_NO_5KCE

Failure Cause

No 5K channel board CE for selected carrier.

Failure Analysis

The CE is exhausted or blocked in the 5K channel board that corresponds


to the carrier.

Possible Solution

1. Verify that there is no 5K CE blocked.


2. Decrease the subscriber quantity for every carrier.

HO_STAT_CARRIER_NO_5KCE

5KCE

5KCE15CE

1.

5K CE

2.

4.65 HO_STAT_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


linkcell.

Possible Solution

Verify that PN has been configured in the neighboring cell.

HO_STAT_PILOT_IS_NOT_NEIGHBOR

PN

PNlinkcell

PN

4-29
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

ZXC10 BSSB Failure Cause Reference(1X)

4.66 BSC_NO_SE
Failure Name

BSC_NO_SE

Failure Cause

No SE resource is available in the system.

Failure Analysis

No SE resource available: SDU configuration error, SE resource status is


abnormal, or SE resource is insufficient.

Possible Solution

1. Verify that the 1XSDU board is correctly configured.


2. Verify that the SDU board operates properly and its version is correct.
3. If the AP interface is installed in the RTP, verify that the SDU virtual
address configuration is correct.
4. Verify that the status of the daughter card of the SDU board and of
INDEX is normal in dynamic management.
5. Verify that the SE resource quantity meets the requirements of traffic
capacity.

BSC_NO_SE

SE

SESDUSESE

1.

1XSDU

2.

SDU

3.

APRTPSDU

4.

SDUINDEX

5.

SE

4.67 BSC_NO_VE
Failure Name

BSC_NO_VE

Failure Cause

No VE resource is available in the system.

Failure Analysis

No VE resource available: VTC configuration error, abnormal VE resource


status, or insufficient VE resource.

Possible Solution

1. Verify that the resource frame where the CIC is located is configured
correctly with corresponding quantity of VTC boards.
2. Verify that the VTC board operates properly and the CPU/DSP version
is correct.
3. Verify that the VTC board and INDEX status is normal in dynamic
management.
4. Verify that the VE resource quantity meets the requirements of traffic
capacity.

4-30
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

Chapter 4 Handoff Failure Causes

BSC_NO_VE

VE

VEVTCVEVE

1.

CICVTC

2.

VTCCPU/DSP

3.

VTCINDEX

4.

VE

4.68 BSC_NO_IWF
Failure Name

BSC_NO_IWF

Failure Cause

No IWF resource is available in the system.

Failure Analysis

IWF resource unavailable: IWF configuration error, abnormal IWF resource


status, or insufficient IWF resource.

Handling Measure

1. Verify that the IWFB board is correctly configured, especially in the


case that the CIC is not selected.
2. Verify that the IWFB board operates properly and the CPU/DSP version
is correct.
3. Verify that the status of the IWFB board and INDEX is normal in
dynamic management.
4. Verify that the IWF resource quantity meets the requirements of traffic
capacity.

BSC_NO_IWF

IWF

IWFIWFIWFIWF

1.

IWFBCIC
CICIWFB

2.

IWFBCPU/DSP

3.

IWFBINDEX

4.

IWF

4.69 BSC_DSPM_NO_INSTANCE
Failure Name

BSC_DSPM_NO_INSTANCE

Failure Cause

No DSPM example is available in the system.

4-31
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

ZXC10 BSSB Failure Cause Reference(1X)

Failure Analysis

DSPM example unavailable: DSPM configuration error, DSPM status


abnormal, or insufficient DSPM examples.

Possible Solution

1. Verify that the DSPM module is correctly configured, and a proper


quantity of DSPM examples is configured.
2. Verify that the MP daughter card where the DSPM module is located
operates properly and its version is correct.
3. Check the module list in the probe view, and verify that the DSPM is in
normal status.
4. Verify that the quantity of DSPM examples meet the requirements of
traffic capacity.

BSC_DSPM_NO_INSTANCE

DSPM

DSPMDSPMDSPMDSPM

1.

DSPMDSPM

2.

DSPMMP

3.

DSPM

4.

DSPM

4.70 BSC_NO_RTPPORT
Failure Name

BSC_NO_RTPPORT

Failure Cause

No RTPPORT resource is available in the system. This failure cause is


submitted only in the case of external RTP.

Failure Analysis

Unavailable RTPPORT resource: configuration error, abnormal status of


RTP port, or insufficient RTPPORT resource.

Handling Measure

1. In the case of external RTP, verify that the IPI board and RTP port are
correctly configured.
2. Verify that the IPI board where RTP port is located operates properly
and its version is correct.
3. Verify that the status of RTPPORT resource is normal during dynamic
management.
4. Verify that the RTPPORT resource quantity meets the requirements of
traffic capacity.

BSC_NO_RTPPORT

RTPPORTRTP
4-32

SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

Chapter 4 Handoff Failure Causes

RTPPORTRTPRTPPORT

1. RTPIPIRTP
2.

RTPIPI

3.

RTPPORT

4.

RTPPORT

4.71 BSC_NO_VALID_RMP
Failure Name

BSC_NO_VALID_RMP

Failure Cause

No RMP module is available in the system.

Failure Analysis

Unavailable RMP module: RMP module configuration error, or abnormal


RMP status.

Possible Solution

1. Verify that the RMP module is correctly configured in the system.


2. Verify that the MP daughter card where the RMP module is located
operates properly and its version is correct.
3. Check the module list in the probe view, and verify that the RMP module
status is normal.

BSC_NO_VALID_RMP

RMP

RMPRMPRMP

1.

RMP

2.

RMPMP

3.

RMP

4.72 HO_STAT_CARRIER_NO_CE_LICENSE
Failure Name

HO_STAT_CARRIER_NO_CE_LICENSE

Failure Cause

The selected carrier frequency has no authorized 1x CE.

Failure Analysis

The authorized 1x CE relevant to this carrier frequency has been consumed


or blocked.

Handling Measure

1. Verify that the CE_LICENSE is not blocked.


2. Decrease the subscribers' number under this BTS.

HO_STAT_CARRIER_NO_CE_LICENSE
4-33

SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

ZXC10 BSSB Failure Cause Reference(1X)

1X CE

BTS1X CE

1.

CE_LICENSE

2.

BTS

4.73 HO_NoPilotAvailable_ERR
Failure Name

HO_NoPilotAvailable_ERR

Failure Cause

No pilot is available in handoff decision.

Failure Analysis

During handoff decision, no pilot is available in the constructed pilot set.

Handling Measure

Trace signaling of handoff decision, and further analyze FailReason of each


cell.

HO_NoPilotAvailable_ERR

FailReason

4.74 ERR_SPS_RLSA_RCM_FCH_FunCallFail_Handler
AbisdfConnectAck_MCSHConstructAmdfFCHSet
up
Failure Name

ERR_SPS_RLSA_RCM_FCH_FunCallFail_HandlerAbisdfConnectAck_MC
SHConstructAmdfFCHSetup

Failure Analysis

During call setup or handoff, when channel resources are configured, an


error occurs in the construction of the channel resource configuration
message. The problem normally occurs on the cell where a control channel
is not configured.

Handling Measure

On the OMC configuration management, verify that the control channel is


configured for the cell (sector) with the problem.
If the control channel is not configured, configure the control channel and
synchronize data.
If the control channel is configured, contact the local ZTE office.

4-34
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

Chapter 4 Handoff Failure Causes

ERR_SPS_RLSA_RCM_FCH_FunCallFail_HandlerAbisdfConnectAck_MC
SHConstructAmdfFCHSetup

OMC

4.75 ERR_SPS_RLSA_RCM_PCALL_FunCallFail_MHa
ndlerTCHfTSSetup_MHandlerAbisdfBTSSetup
Failure Name

ERR_SPS_RLSA_RCM_PCALL_FunCallFail_MHandlerTCHfTSSetup_
MHandlerAbisdfBTSSetup

Failure Analysis

During call setup or handoff, an error occurs in handling the call setup or
handoff message .

Handling Measure

1. In the case that the BTS is in graceful degradation mode, when the BTS
receives the call setup or handoff message from the BSC, the BTS
reports the failure message. It is a normal case.
2. The RCM does not support concurrent setup flows. If the RCM receives
another call setup or handoff message during the leg setup process, the
RCM reports the failure message. If the problem occurs occasionally,
no troubleshooting is required.
3. If the BSSAP or DSPM handoff type is incorrect, the failure message is
also reported. If the problem occurs occasionally, no troubleshooting
is required.

ERR_SPS_RLSA_RCM_PCALL_FunCallFail_MHandlerTCHfTSSetup_
MHandlerAbisdfBTSSetup

1.

BSC

2. RCM

3. BSSAPDSPM

4-35
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

ZXC10 BSSB Failure Cause Reference(1X)

4.76 ERR_SPS_RLSA_RCM_FCH_MsgParaIncorrect_H
andleAbisdfConnectAck_SoftHandoffLegNoInvalid
Failure Name

ERR_SPS_RLSA_RCM_FCH_MsgParaIncorrect_HandleAbisdfConnectAc
k_SoftHandoffLegNoInvalid

Failure Analysis

During call setup or handoff process, the leg number leg in the
AbisdfConnectAck message exceeds the maximum allowed value. A call
supports up to 12 legs. If the leg number exceeds 12, a call failure may
be caused.

Handling Measure

If the problem occurs frequently, contact the local representative office of


ZTE Corporation.

ERR_SPS_RLSA_RCM_FCH_MsgParaIncorrect_HandleAbisdfConnectAc
k_SoftHandoffLegNoInvalid

AbisdfConnectAck

1212

4.77 ERR_SPS_RLSA_RCM_PCALL_FunCallFail_MHa
ndlerAbisdfBTSSetup_MCDHSaveToCommonData
Failure Name

ERR_SPS_RLSA_RCM_PCALL_FunCallFail_MHandlerAbisdfBTSSetup_
MCDHSaveToCommonData

Failure Analysis

An error occurs in saving data during call setup or handoff handling.


1. The handoff type in the call setup or handoff message is incorrect.
2. The CI and frequency point in call setup or handoff message are
incorrect, so the carrier cannot be found based on the CI and frequency
point.

Handling Measure

If the a few such problems occur, ignore them. If a lot of such problems
occur, contact the local office of ZTE Corporation.

ERR_SPS_RLSA_RCM_PCALL_FunCallFail_MHandlerAbisdfBTSSetup_
MCDHSaveToCommonData

4-36
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

Chapter 4 Handoff Failure Causes

1.

2.

CICI

4.78 ERR_CES_RLSA_CEC_CALLHANDLER_V_Chan
nelType_Error
Failure Name

ERR_CES_RLSA_CEC_CALLHANDLER_V_ChannelType_Error

Failure Cause

In the case of soft handoff, during FCH setup, the incorrect channel type
causes the FCH setup failure.

Failure Analysis

The possible causes may be as follows:


1. The CHM version and CCM version do not match.
2. A CES error occurs.
3. An upper-layer error occurs.

Handling Measure

1. Make the CHM version and the CCM version consistent.


2. Soft reset the CHM.
3. If the above measures do not work, reset the CCM.

ERR_CES_RLSA_CEC_CALLHANDLER_V_ChannelType_Error

CHMCCM

CES

1.

2.

CHM

3.

CCM

4-37
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

ZXC10 BSSB Failure Cause Reference(1X)

This page intentionally left blank.

4-38
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

Chapter 5

Registration Failure Causes


5.1 ERR_SPS_RLSA_BSSAP_Reg_Reject_Congestion
Failure Name

ERR_SPS_RLSA_BSSAP_Reg_Reject_Congestion

Failure Cause

Registration fails due to congestion on the network side.

Failure Analysis

The MSC rejects the registration due to congestion.

Handling Measure

If the problem occurs occasionally, it is normal. If it occurs frequently, verify


that the corresponding modules on the switch side are normal.

ERR_SPS_RLSA_BSSAP_Reg_Reject_Congestion

MSC

5.2 ERR_SPS_RLSA_BSSAP_Reg_Reject_IllegalMs
Failure Name

ERR_SPS_RLSA_BSSAP_Reg_Reject_IllegalMs

Failure Cause

Registration fails due to invalid IMSI.

Failure Analysis

The cause of the invalid IMSI may be:


1. The IMSI is all zeros.
2. The UIM card has been cloned.

Handling Measure

Determine whether to block illegal mobile phones according to the actual


situation.

ERR_SPS_RLSA_BSSAP_Reg_Reject_IllegalMs

IMSI

IMSI
l

IMSI0

UIM
5-1

SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

ZXC10 BSSB Failure Cause Reference(1X)

5.3 ERR_SPS_RLSA_BSSAP_Reg_Reject_NetworkF
ailure
Failure Name

ERR_SPS_RLSA_BSSAP_Reg_Reject_NetworkFailure

Failure Cause

Registration fails due to network failure.

Failure Analysis

The IMSI information is not found in VLR/HLR, hence causing the


registration failure.

Handling Measure

It is a normal case. Trace it and find the IMSI information on the MSC side.

ERR_SPS_RLSA_BSSAP_Reg_Reject_NetworkFailure

VLR/HLRIMSI

MSCIMSI

5.4 ERR_SPS_RLSA_BSSAP_Reg_Reject_RoamingNo
tAllowed
Failure Name

ERR_SPS_RLSA_BSSAP_Reg_Reject_RoamingNotAllowed

Failure Cause

Registration fails due to lack of roaming rights.

Failure Analysis

During registration, when the system wants to find the IMSI information in
VLR/HLR, it finds that the user is roaming in another place and the user has
no roaming rights. Hence, the registration fails.

Handling Measure

The user has no roaming rights; therefore, it is normal that the problem
is reported.

ERR_SPS_RLSA_BSSAP_Reg_Reject_RoamingNotAllowed

VLR/HLRIMSI

1.

2.

5-2
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

Chapter 5 Registration Failure Causes

5.5 ERR_SPS_RLSA_BSSAP_Reg_Reject_Other
Failure Name

ERR_SPS_RLSA_BSSAP_Reg_Reject_Other

Failure Cause

Registration fails due to other unknown causes.

Failure Analysis

The registration fails due to a cause other than network congestion, invalid
IMSI, network failure and no roaming rights.

Handling Measure

If such problems rarely occur, it is normal. If a lot of such problems occur,


contact the local office of ZTE Corporation.

ERR_SPS_RLSA_BSSAP_Reg_Reject_Other

1.

2.

5.6 ERR_SPS_RLSA_BSSAP_SccpDisconnect_Releas
e_In_Progress
Failure Name

ERR_SPS_RLSA_BSSAP_SccpDisconnect_Release_In_Progress

Failure Cause

SCCP receives the repeated registration request from the same user,
causing the registration failure.

Failure Analysis

Certain MSs sends registration requests frequently, causing the registration


failure.

Handling Measure

If such problems rarely occur, it is normal. If a lot of such problems occur,


contact the local office of ZTE Corporation.

ERR_SPS_RLSA_BSSAP_SccpDisconnect_Release_In_Progress

SCCP

1.

2.

5-3
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

ZXC10 BSSB Failure Cause Reference(1X)

5.7 ERR_SPS_RLSA_BSSAP_Reg_Reject_MinImsiU
nknown
Failure Name

ERR_SPS_RLSA_BSSAP_Reg_Reject_MinImsiUnknown

Failure Cause

The MS whose number is not allocated on the HLR initiated a registration, and
the registration fails.

Failure Analysis

The number of the MS that initiates a registration is not allocated on the HLR.

Handling Measure

The problem rarely occurs. If this occurs, contact the ZTE local office or the
R&D personnel.

5-4
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

Chapter 6

Other Failure Causes


6.1 ERR_SPS_RLSA_BSSAP_DiscardMsg_SmsNum
Ovld
Failure Name

ERR_SPS_RLSA_BSSAP_DiscardMsg_SmsNumOvld

Failure Cause

Excess SMS messages are received.

Failure Analysis

When receiving a large quantity of forward SMS messages in a short period


of time, the system automatically discards the messages that exceed the
threshold and reports the exception.

Handling Measure

Verify that the setting of the SMS overload threshold is reasonable and no
exception occurs during an SMS peak.

6.2 ERR_SPS_RLSA_BSSAP_MsgPara_A1fPACAUpda
te_SBSSRInvalidProcess
Failure Name

ERR_SPS_RLSA_BSSAP_MsgPara_A1fPACAUpdate_SBSSRInvalidProcess

Failure Cause

The update fails due to the absence of the serving side.

Failure Analysis

The PACA update fails when the MS transits to the target side completely.

Handling Measure

If the failure occurs occasionally, it is unnecessary to handle. If the failure


occurs frequently, contact the ZTE engineer.

6.3 ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_A7
BurstRequestReceived
Failure Name

ERR_SPS_RLSA_BSSAP_TgtBSC_Other_RLC_A7BurstRequestReceived

Failure Cause

The target side receives a supplemental channel setup request from the
serving side when it does not finish the current non-network interconnection
handoff.

6-1
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

ZXC10 BSSB Failure Cause Reference(1X)

Failure Analysis

A message loss occurs during the handoff or a processing exception occurs


on the serving side.

Handling Measure

If the failure occurs occasionally, it is unnecessary to handle. If it occurs


frequently, contact the ZTE engineer.

6.4 ERR_SPS_RLSA_DSPM_CLH_OtherReason_OVE
RLOAD
Failure Name

ERR_SPS_RLSA_DSPM_CLH_OtherReason_OVERLOAD

Failure Cause

DSMP board CPU overloads.

Failure Analysis

DSMP board CPU overloads.

Handling Measure

Add another DSMP board.

ERR_SPS_RLSA_DSPM_CLH_OtherReason_OVERLOAD

DSMPCPU

DSMPCPU

DSMP

6.5 INPUT_PARA_ERROR
Failure Name

INPUT_PARA_ERROR

Failure Cause

Input parameter error.

Failure Analysis

It is normally displayed during system reset. The possible failure causes


are as follows:

Possible Solution

The confirmed rate is higher than that of the system reserves.

The dispatching duration is out of the allowed range.

The Walsh code is different from that allocated.

Check the fault probe and take measures accordingly after identifying the
cause.

INPUT_PARA_ERROR

6-2
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

Chapter 6 Other Failure Causes

Walsh

6-3
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

ZXC10 BSSB Failure Cause Reference(1X)

This page intentionally left blank.

6-4
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

Glossary
ABPM
- ABis Processing Module
- Abis
ACK
- ACKnowledgement
-
Abis
- Abis Interface between BSC and BTS
- BSCBTS
BDM
- Baseband Digital Module
BDM is a board in a micro-BTS, the functions of BDM are same as BDS in a
macro-BTS.
-
BS
- Base Station
-
BSC
- Base Station Controller
-
BSSAP
- Base Station System Application Part
-
BTS
- Base Transceiver Station
-
CCM
- Communication Control Module
-
CE
- Channel Element
-
CES
- Channel Element Subsystem
-

I
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

ZXC10 BSSB Failure Cause Reference(1X)

CHM
- Channel Processing Module
It completes forward modulation and reverse demodulation for baseband data of
the cdma2000-1X physical channel. As a concept corresponding to RF, baseband
refers to the signal before carrier modulation or after carrier demodulation.
-
CIC
- Circuit Identification Code
-
CMP
- Calling Main Processor
-
CPU
- Central Processing Unit
-
CSM
- Central Switching Module
-
DSM
- Data Service Module
Implements the Abis interface function between the IP BDS and the IP BSC, and
provides the conversion of IP packets into the E1/T1 signals that are suitable for
remote transmission before the signals are transmitted to the remote station.
-
DSMP
- Data Service Management Platform
-
DSP
- Digital Signal Processor
-
DTB
- Digital Trunk Board
-
ESN
- Electronic Serial Number
-
FO
- Frame Offset
-
II
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

Glossary

HGM
- HIRS GateWay Module
- HIRS
HIRS
- High-speed Interconnect Router Subsystem
-
HLR
- Home Location Register
-
IBBE
- Interface of BSC and BSC by Ethernet
- EthernetBSC
IMSI
- International Mobile Subscriber Identity
-
MGW
- Media Gateway
-
MS
- Mobile Station
-
MSC
- Mobile Switching Center
-
MSCe
- Mobile Switching Center emulator
-
OMC
- Operation & Maintenance Center
-
PCF
- Packet Control Function
PCF is a board which is responsible for the data selection between multiple
reverse traffic channels and data distribution from a forward traffic channel to
multiple cells/sectors during soft handoff.
-
PCM
- Pulse Code Modulation
-

III
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

ZXC10 BSSB Failure Cause Reference(1X)

PDSN
- Packet Data Service Node
-
R-SCH
- Reverse Supplemental Channel
-
RC
- Radio Configuration
-
RCM
- Radio Control Module
-
RMP
- Resource Main Processor
-
SCCP
- Signaling Connection Control Part
-
SCCP
- Signaling Connection Control Part
-
SCH
- Supplemental Channel
-
SDH
- Synchronous Digital Hierarchy
-
SDM
- Supervisory Division Multiplexing Board
-
SDU
- Selection and Distribution Unit
-
SDU
- Service Data Unit
-
SO
- Service Option
-

IV
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

Glossary

SSN
- Sub-System Number
-
UID
- User IDentifier
-
VLR
- Visitor Location Register
-
VTC
- Voice Transcoder Card
-

V
SJ-20120828144226-019|2012-10-20 (R1.0)

ZTE Proprietary and Confidential

Вам также может понравиться